Skip to content

Commit e9f3fc9

Browse files
committed
SME feedback updates
1 parent f936ef8 commit e9f3fc9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

support/developer/dotnet/framework/general/Printing-process-fails-using-WPF-application-Win10.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,19 +16,19 @@ This article discusses a problem in which you can't successfully print large doc
1616

1717
Consider the following scenario:
1818

19-
1. You use a WPF application in Windows 10 to print a range of pages.
19+
1. You use a WPF application in Windows 10 or later to print a range of pages.
2020
1. You run the `XpsDocument` object to process the print job by using `VisualsToXpsDocument`, `DocumentPaginator`, or another method.
2121

2222
In this scenario, the print process fails after you print some pages.
2323

2424
## Cause
2525

26-
When you print pages by using a WPF application in Windows 10, the font information is allocated on a page-by-page basis. If you're using this method to print a range of pages in a runtime, the process may increase memory usage by the operating system.
26+
When you print pages by using a WPF application in Windows 10 or later, the font information is allocated on a page-by-page basis. If you're using this method to print a range of pages in a runtime, the process may increase memory usage by the operating system.
2727

2828
For example, if you're printing more than 8,000 pages, the process may stop because of a temporary increase in memory usage. This error indicates that an `IOException` occurred because of failed access to the font file.
2929

3030
After all the pages finish printing, memory can be freed for allocation.
3131

3232
## Solution
3333

34-
For documents that contain more than 1,000 pages, reduce the number of pages for a print process in a runtime.
34+
To resolve this issue apply the [January 2025 Cumulative Update Preview](/dotnet/framework/release-notes/2025/01-28-january-cumulative-update-preview) or a later update for .NET Framework.

0 commit comments

Comments
 (0)