Bug 112387 - OutputDevice::OutputDevice() leaks memory
Summary: OutputDevice::OutputDevice() leaks memory
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-14 14:01 UTC by Telesto
Modified: 2017-09-25 08:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
BT & Few screenshots (548.05 KB, application/x-zip-compressed)
2017-09-14 14:02 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-09-14 14:01:02 UTC 
Description:
OutputDevice::OutputDevice() with one invocation

Steps to Reproduce:
1. Start the Instruments.app
2. Choose Memory Leak profile tool
3. Select LibreOffice.app in instdir as target process
4. Click on the record button, LODev is started by the profiling tool
5. Wait for the StartCenter to load.
6. Click on the new Calc document icon to open a blank Clac document.
7. Close the document
8. Stop recording (after the closing is fully processed) 
9. Analyse the profile trace.

Actual Results:  
Memory leak in OutputDevice::OutputDevice()


Expected Results:
Shouldn't leak memory


Reproducible: Always

User Profile Reset: No

Additional Info:
Version: 6.0.0.0.alpha0+
Build ID: e970395c692a5c315914ddf5b43cf01e590345ff
CPU threads: 4; OS: Mac OS X 10.12.4; UI render: default; 
Locale: en-US (en_US.UTF-8); Calc: group



User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Telesto 2017-09-14 14:02:04 UTC 
Created attachment 136242 [details]
BT & Few screenshots
Comment 2 Julien Nabet 2017-09-25 08:01:46 UTC 
Following https://cgit.freedesktop.org/libreoffice/core/commit/?id=eaf7d58ef57daa7580057b38625cd9a96ffe2a43, I think it's fixed now.

Don't hesitate to reopen this one if you can still reproduce this with a build which includes this patch.