Bug 107234 - CRASH after opening particular spreadsheet
Summary: CRASH after opening particular spreadsheet
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-17 22:39 UTC by Jim
Modified: 2017-05-11 11:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim 2017-04-17 22:39:09 UTC
Description:
Calc CRASH after overlaying web browser (firefox & chrome) for inconsistent period of time (5-10 minutes). Requires resarting Calc and recovery that seems to work.  Also happens if Calc minimized and browser opened.  Using Windows 7 Pro SP1. This has been happening regardless of the LibreOffice version being used, having occurred over the past 6-9 months.   

Steps to Reproduce:
1.close and recover file.
2.open browser and collect info. 
3.try to access Calc, but frozen and browser window block out the view of Calc under the browser when dragged away.
4. Attempt to close calc window results in error dialog with option to force close. 
5. Attempting to open any LibreOffice file requires recovering the Calc file.
  

Actual Results:  
See above. 

Expected Results:
See above. 


Reproducible: Always

User Profile Reset: No

Additional Info:

OS: Windows 7 SP1
OS is 64bit: yes

I've wondered if it could be related to some corrupted data in this particular file, but I'm not sure how to test that.

Minor but aggraving problem since it requires multiple recoveries and loss of data in the spreadsheet during a work session if I don't save the Calc spreadsheet after every data entry.    
Builds ID: LibreOffice 5.2.6.2


User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Comment 1 Xisco Faulí 2017-04-17 23:04:24 UTC Comment hidden (obsolete)
Comment 2 Laurie Lang 2017-05-11 11:30:31 UTC
For some unknown reason, the bug has disappeared.
I have not reset my profile, and have not deliberately changed any settings, but can no longer recreate the behaviour.