Bug 91297

Summary: Crash at the opening the file
Product: LibreOffice Reporter: Xavier Léonard <xavier.leonard>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INSUFFICIENTDATA    
Severity: critical CC: erack, miguelangelrv, raal, serval2412
Priority: high    
Version: 4.3.7.2 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: planning
Backtrace

Description Xavier Léonard 2015-05-15 03:51:39 UTC
Created attachment 115613 [details]
planning

Crash at the opening of the join file... There is a lot of Conditional Formatting in this document. I always had some problems with it. So I use Open Office to work with it and it's better... But I prefer to use LibreOffice!
Regards
Comment 1 raal 2015-05-15 05:46:08 UTC
I can confirm crash with LO 4.4.3, win7

Xavier, if possible, please could you follow the instructions provided at this link < https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg > and submit a backtrace? That way a developer can look into the underlying reason of the crash.
Thank you.
Comment 2 Xavier Léonard 2015-05-15 11:58:22 UTC
Created attachment 115622 [details]
Backtrace
Comment 3 m_a_riosv 2015-05-15 20:44:04 UTC
Seems the issue is with the Condition Format, deleting it except for one sheet in ApacheOpenoffice and saving, lets open the file with LibreOffice, you can let it for one sheet and it works.
Comment 4 Julien Nabet 2015-05-22 23:09:49 UTC
On pc Debian x86-64 with master sources updated today, I don't reproduce this.

Windows only bug?
Comment 5 Eike Rathke 2015-09-29 21:06:42 UTC
Could not reproduce with Linux master dbgutil build, 5.0.2 nor 4.4.5 or 4.4.3.
The backtrace indicates a crash under configmgr::writeValueContent() and Calc isn't even involved. Does by chance removing/renaming the user profile help? See https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile
Comment 6 Julien Nabet 2016-05-07 20:18:22 UTC
No feedback since 7 months.
Let's put this one to RESOLVED/INSUFFICIENTDATA.

Xavier: don't hesitate to reopen this tracker if you still reproduce this with last stable version (5.1.2) + brand new profile as Eike suggested.