Bug 45027 - LibreOffice Crashes after closing a specific document
Summary: LibreOffice Crashes after closing a specific document
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
3.5.0 RC1
Hardware: Other All
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-21 04:23 UTC by Florian Reisinger
Modified: 2021-12-05 09:52 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
backtrace with symbols (22.99 KB, text/plain)
2012-01-21 05:13 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Reisinger 2012-01-21 04:23:57 UTC
Sorry for the heading...
1) Try out this bug https://bugs.freedesktop.org/show_bug.cgi?id=44216
2) When you have finished checking this bug, close target.odg
3) LibreOffice crashes
LibO 3,5rc 1 Win7x64
Comment 1 Julien Nabet 2012-01-21 05:04:58 UTC
I reproduced it with 3.5 branch and master updated today.

(PC Debian x86-64)
Comment 2 Pedro 2012-01-21 05:11:13 UTC
Confirmed with 3.5.0 RC1 under Windows XP Pro x86 SP3
Comment 3 Julien Nabet 2012-01-21 05:13:52 UTC
Created attachment 55901 [details]
backtrace with symbols

I retrieved a backtrace from master branch updated today.
Comment 4 Thomas Hackert 2012-01-21 06:44:22 UTC
Hello Florian, *,
I can confirm it with LO 3.5.0 RC1 under Debian Testing AMD64 as well ... :( But should the importance not be critical or something, as it crashes LO?
HTH
Thomas.
Comment 5 Florian Reisinger 2012-01-21 08:40:47 UTC
@ Thomas

Year, changed
Comment 6 Jean-Baptiste Faure 2012-01-22 04:31:27 UTC
No crash for me with LO 3.5.0 rc1+ (LibreOffice 3.5.0rc1+ Build ID: 8a44936-8c0b455-b4ea45f-2d9b003-f1edcf6) under Ubuntu 11.10 x86_64

Best regards. JBF
Comment 7 Pedro 2013-01-29 15:56:53 UTC
No crash under Win XP Pro x86 SP3 using LibreOffice 3.6.5.2

This bug seems to be fixed?
Comment 8 Julien Nabet 2013-01-29 21:45:55 UTC
Giving a try after Pedro's comment, I didn't reproduce the problem neither with 3.6 sources updated some days ago and nor with 4.0 sources updated today.
So I put it as WFM.

Florian: if you or someone else reproduce this, don't hesitate to reopen the tracker of course