When will XPS issues be fixed?

[wstaelens]

As you have noticed there are many XPS issues out there (most of them related to memory issues and memory leaks, fonts, STA, ...).

Over the last months, years I have seen many of them being moved to "future", "future", "future", "future" without getting proper attention or getting closed. I know that XPS and printing might not be sexy but it is needed as hell.

It is even so bad that Microsoft's own V4 print driver produces XPS jobs that are unable to read in .NET Core because code is not implemented, as @ThomasGoulet73 found out: #6301 and #3546 .

Why is XPS being ignored?
Why does it take literally years before someone fixes some XPS bugs?

@danmoseley what is going on?

• https://github.com/dotnet/wpf/issues?q=xps
• XPS documents memory leak (System.Windows.ContextLayoutManager+LayoutQueue+Request and XpsDocument.GetFixedDocumentSequence()) #6301 ,
• https://www.bing.com/search?q=xps+fixedpage+memory+leak+updatelayout&qs=n&form=QBRE&msbsrank=0_0__0&sp=-1&pq=xps+fixedpage+memory+leak+updatelayout&sc=0-38&sk=&cvid=AB745EF580034F38A1F9310015972FFC
• https://stackoverflow.com/search?q=xps+memory+leak

[olowk]

We are also wandering this. In our latest project with XPS we have many problems with memory leaks and the suggested workarounds like using updatelayout don't seem to work!!

[wstaelens]

dotnet/runtime#78629

will anyone have a look at these top 4? Broken since the first release of .net (core).

dotnet/runtime#51929

#3546

dotnet/runtime#78374

#4000

[ThomasGoulet73]

All these issues are for dotnet/runtime. It's unfortunate that your issues don't seem to get traction there but it doesn't seem like anything can be done in the dotnet/wpf repo.

[wstaelens]

@ThomasGoulet73 guess you didn't check not everything is runtime, some are XPS/WPF/XAML. The fact is that there is a pull request that needs to be tested (code originally added by Kevin Cathcart) but this has effect on XPS/WPF project.

but really nobody seems to give a f#.

#3546

dotnet/runtime#78374 <-- contains the code from Kevin

#4000

[ThomasGoulet73]

The code related to #3546 is in dotnet/runtime so the fix will need to be in dotnet/runtime (Like dotnet/runtime#78374 attempted) with the team that owns the code (Which isn't the WPF team IIRC).

I don't have the whole context for #4000 but it seems like the original question was answered in the issue.

[wstaelens]

@ThomasGoulet73 when working with XPS most of it is in WPF but the root cause is that something from the compression (indeed runtime) is not implemented/ported fully. Everything started from WPF code base, but the issue itself is indeed in runtime, but originated from WPF code base usage. (see example: #3546 (comment) )

regarding #4000
see #4000 (comment) and #4000 (comment)
The problem is that everything when working with XPS documents it needs to be done in the same single STA thread. Somehow you will face the STA thread requirement which is a huge penalty.

[wstaelens]

Any updates? Most of this is in the xaml/wpf area:
dotnet/runtime#78629

[pchaurasia14]

@wstaelens - Unfortunately, none at this time.