Bug 53400 - Crash opening file of fdo#51817
Summary: Crash opening file of fdo#51817
Status: CLOSED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha0+ Master
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-12 10:16 UTC by Julien Nabet
Modified: 2012-09-30 20:09 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
bt + console logs (13.61 KB, text/plain)
2012-08-12 10:16 UTC, Julien Nabet 		Details
autogen.lastrun (767 bytes, text/plain)
2012-08-12 11:02 UTC, Julien Nabet 		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 Julien Nabet 2012-08-12 10:16:43 UTC 
Created attachment 65460 [details]
bt + console logs

Problem description: 
On pc Debian x86-64 (testing updated today) with master sources updated today and a brand new LO profile, I had a crash during opening the file https://bugs.freedesktop.org/attachment.cgi?id=64081

Steps to reproduce:
1. Retrieve https://bugs.freedesktop.org/attachment.cgi?id=64081 file
2. Try to open it

Current behavior:
Crash

Expected behavior:
No crash

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6) Gecko/20100101 Firefox/10.0.6 Iceweasel/10.0.6
Comment 1 Julien Nabet 2012-08-12 11:02:20 UTC 
Created attachment 65462 [details]
autogen.lastrun

I attached autogen.lastrun

gcc (Debian 4.7.1-2) 4.7.1
libc: 2.13-33

java version "1.7.0_03"
OpenJDK Runtime Environment (IcedTea7 2.1.1) (7~u3-2.1.1-1)
OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
Comment 2 Julien Nabet 2012-08-13 20:19:58 UTC 
I don't reproduce this with 3.5.4 Debian package or with 3.6 sources updated today.
I still reproduce it with master sources updated today.
(each test with a brand new LO profile)
Comment 3 bfoman (inactive) 2012-08-14 09:53:47 UTC 
Wouldn't it be better to comment on original bug 51817, where all informations about this attachment are available? I think we cannot afford to open multiple bugs about one attachment.
Comment 4 Korrawit Pruegsanusak 2012-09-29 16:26:57 UTC 
Tested on Windows XP and I got following results.

File did NOT open after finished loading, with no crash, and file locked (have hidden .~lock.$filename file) with:
* build from tinderbox W2008R2@20-With-Symbol-Bytemark-Hosting, pull time 2012-08-14 09:13:01, core:7bfb229230a439c2edb3e8452fe0d3430f9931ce

But NOT reproducible, meaning of no crash and file open well, with:
* official 3.5.3.2, 3.5.7.1, 3.6.2.2
* build from tinderbox Win-x86@6, pull time 2012-09-13 22:49:31, core:9302520ff445d9789859f501b8bd6bc32c300e26

I think this problem is fixed in the meantime, or it's an intermittent problem.
Julien, could you please check again? and mark as WORKSFORME if appropriate. Thanks! :)
Comment 5 Julien Nabet 2012-09-30 20:07:31 UTC 
Korrawit: you were right, no crash now, thank you.

bfoman: symptoms are different. It's the same file but it's just a file, it could have been any file. The important point is symptom.
I don't think we should mix different symptoms (crash during opening/crash when click on the export PDF button) from different env (Linux/Windows) and different version (master sources/3.5.2)