Download it now!
Bug 62812 - writer_pdf_Export Font GDI handle leaks
Summary: writer_pdf_Export Font GDI handle leaks
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
4.0.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pdf
Depends on:
Blocks: PDF-Export GDI-Limit
  Show dependency treegraph
 
Reported: 2013-03-27 13:50 UTC by flajs.email
Modified: 2018-06-20 02:49 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
GDI view, Font handle are not released ! (93.05 KB, image/png)
2013-03-27 13:50 UTC, flajs.email
Details
attachment with good mimetype (93.05 KB, image/png)
2013-03-27 13:54 UTC, flajs.email
Details

Note You need to log in before you can comment on or make changes to this bug.
Description flajs.email 2013-03-27 13:50:10 UTC
Created attachment 77103 [details]
GDI view, Font handle are not released !

GDI view, Font handle are not released !

Batch conversion from RTF->PDF

after 1700 iteration of converted files are GDI handles fill 
GDI Font object isn't released.

how to reproduce:
1) connection to LO

2) while (i < 1800)
3) open RTF (with arial font, bold font .... etc, multiple file)
4) export to PDF (PDF 1.4 or A)
5) loop
Comment 1 flajs.email 2013-03-27 13:54:11 UTC
Created attachment 77104 [details]
attachment with good mimetype
Comment 2 flajs.email 2013-03-27 13:57:35 UTC
files are closed,
other formats (txt...) ... OK
Comment 3 Joel Madero 2013-03-27 14:05:05 UTC
This is not a critical bug if it exists.

Also what are you using to do your batch conversion? Marking as NEEDINFO as we need more explicit steps on how to reproduce the bug. Please be as explicit as possible when describing steps for a bug, especially slightly more complicated bugs that include batch changes.

Once you provide steps please mark as UNCONFIRMED and we shall try to triage the issue.
Comment 4 flajs.email 2013-03-28 07:39:25 UTC
Simplest  scenario for a reproduction bug:

1) Execute LibreOffice 4.0.1.2 on Windows 7 
2) Create new document in Writer
3) write several words with fonts Arial, Arial Bold, Times New Roman etc

4) Run GDIView - applikaction for monitoring windows objects resources
   DC, Fonts, etc.
   http://www.nirsoft.net/utils/gdi_handles.html

5) Export this document to PDF 
6) Check GDIView (F5 refresh) on soffice.bin process -> Font object growth
7) repeat steps 5,6

It's info OK ?
Comment 5 Buovjaga 2014-10-22 11:59:59 UTC
I did as instructed in comment 4 and observed the font count increase after every PDF export, so I'm setting this as NEW.
Version: 4.4.0.0.alpha1+
Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1
TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33
Comment 6 QA Administrators 2015-12-20 16:15:57 UTC Comment hidden (obsolete)
Comment 7 Julien Nabet 2016-11-06 20:49:38 UTC
Any better with last stable LO version 5.2.2?
Comment 8 Buovjaga 2016-11-09 08:01:31 UTC
(In reply to Julien Nabet from comment #7)
> Any better with last stable LO version 5.2.2?

Still growing.

Win 7 Pro 64-bit Version: 5.3.0.0.alpha1+
Build ID: 63bd9cf4ad268d83677baf99ec509ef67b5de08a
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-11-07_01:55:57
Locale: fi-FI (fi_FI); Calc: group
Comment 9 Xisco Faulí 2017-06-19 09:38:10 UTC
Some fixes have been done to the GDI handles recently.
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
Comment 10 QA Administrators 2018-06-20 02:49:03 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug