Bug 98716 - FILESAVE leads to crash on Windows, Linux working fine
Summary: FILESAVE leads to crash on Windows, Linux working fine
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.0.0.0.alpha0+ Master
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: haveBacktrace
Depends on:
Blocks:
 
Reported: 2016-03-16 21:01 UTC by shiki
Modified: 2016-04-21 15:05 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
WinDbg analyze log (35.14 KB, text/plain)
2016-03-16 21:01 UTC, shiki 		Details
file with which the crash occurs on saving (423.52 KB, application/vnd.oasis.opendocument.spreadsheet)
2016-03-16 21:03 UTC, shiki 		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 shiki 2016-03-16 21:01:41 UTC 
Created attachment 123637 [details]
WinDbg analyze log

When I open a certain ODS file (attached) on Linux and save it, even multiple time, saving works perfectly.

On Windows 7 and 10 however, I had the following issue with aforementioned file:
- saving once takes significantly longer than on Linux on the same hardware
- saving twice kills the patient.

Since I'm new to this, I thought a stacktrace would be useful, I hope I did everything right in the attached WinDbg output.
Comment 1 shiki 2016-03-16 21:03:04 UTC 
Created attachment 123638 [details]
file with which the crash occurs on saving

This file is a rewrite of the free Mahnungs Tool found here:
http://www.software-knowhow.de/neu/shop/mahntool/index.aspx
Comment 2 raal 2016-03-18 22:18:36 UTC 
I can not confirm with Version: 5.2.0.0.alpha0+ (x64)
Build ID: 042f16a19e3d5f884759dae71264433b988df0e6
CPU Threads: 1; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-03-16_10:03:38
saved 5 times without crash.
Comment 3 shiki 2016-03-20 19:24:23 UTC 
This seems to be fixed somewhere in between 5.1 and the current master build (5.2). If it still happens with stable 5.2 I'll re-open the bug. Thanks raal ;)
Comment 4 raal 2016-03-20 19:27:57 UTC 
Thanks for testing, correct status is WFM.