We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

WordArt causes exception when converting to fixed-layout XHTML

Hi, I’ve come across an issue when converting Word documents to xhtml.

Could not create the bitmap with the specified parameters. Possible lack of system resources.    at  ?..ctor(Int32 , Int32 , Single , Single , PixelFormat )
   at  ? .(RectangleF , ?? , Int32 , DocumentBase )
   at  ? .(?? , Int32 , Single , DocumentBase )
   at  ? .(   , ICollection`1 )
   at  ? .?? ??  (?? )
   at ?? .( ?  , ?? , Boolean )
   at ?? .(?? , ?? , Boolean )
   at ?? .( ?  , ?? , ??  ,  ? ,     , Boolean )
   at  ? .(?? ,  ?  ,     )
   at ?? .( ?  , Shading , ?? )
   at ?? . ? ??  ( ?  )
   at  ? .( ?  )
   at  ? . ? ??  ( ?  )
   at ?? .(ShapeBase )
   at ?? .(ShapeBase , ?   )
   at ?? .(?   , Boolean )
   at    .(?   )
   at    .(    )
   at    .   ??   ()
   at    .(?   , IList`1 , IList`1 )
   at    .(?   , IList`1 , IList`1 )
   at    .(?   , IList`1 , IList`1 )
   at    .()
   at ?  .?  ??  ( ?  )
   at  ? .(?   )
   at  ? .(?   , ?   )
   at ?  .( ?  ,  ?  )
   at ?  .   ??  ( ?  )
   at  ? . ? ??  ( ?  )
   at Aspose.Words.Document.( ?  )
   at Aspose.Words.Document.(Stream , String , SaveOptions )

Here’s a minimal reproduction document:
WordArt.docx (2.0 MB)

Let me know if you require more details.
Thanks in advance.

Hi @njlgad,

I’m unable to reproduce the issue on my side. Could you specify the following details:

  1. Version of Aspose.Words for .NET
  2. Version of .NET framework
  3. Operating System

Additionally, could you check whether you can reproduce the issue by converting your document to PDF.

Thanks.

Hi @dshvydkiy,

We use Aspose.Words 22.1.0 with the following save options:

new HtmlFixedSaveOptions { SaveFormat = SaveFormat.HtmlFixed, };

I was able to reproduce the problem here: https://products.aspose.app/words/conversion
Screenshot 2022-02-24 at 13.48.41.png (104.8 KB)

I will try the latest version of Apose.Words (22.2.0)

I can confirm that the latest version of Aspose.Words (22.2.0) fixes this issue.

Thanks :slight_smile: