Bug 57901 - CRASH when I close a PPT document
Summary: CRASH when I close a PPT document
Status: RESOLVED DUPLICATE of bug 55974
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.0.0.0.alpha1
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
: 56460 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-12-05 04:00 UTC by Maximiliano Castañón
Modified: 2012-12-18 15:04 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
example PPT (377.00 KB, application/vnd.ms-powerpoint)
2012-12-05 04:00 UTC, Maximiliano Castañón
Details
bt with symbols (5.12 KB, text/plain)
2012-12-05 19:03 UTC, Julien Nabet
Details
new Valgrind trace (29.17 KB, application/bzip2)
2012-12-06 19:49 UTC, Julien Nabet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maximiliano Castañón 2012-12-05 04:00:57 UTC
Created attachment 71020 [details]
example PPT

When I close a randomly PPT file LO crash... when I close any other document nothing happens.

I have tested the crash and only happens with PPT files...

it returns

maximi89@Maximi89-HP:~$ /opt/lodev4.0/program/soffice
Warning: failed to read path from javaldx
WARNING: gnome-keyring:: couldn't connect to: /home/maximi89/.cache/keyring-gIhwB6/pkcs11: No existe el fichero o el directorio
*** glibc detected *** /opt/lodev4.0/program/soffice.bin: invalid fastbin entry (free): 0x00000000053c3f50 ***
Comment 1 Julien Nabet 2012-12-05 18:54:48 UTC
Comment on attachment 71020 [details]
example PPT

fix mimetype
Comment 2 Julien Nabet 2012-12-05 19:03:17 UTC
Created attachment 71038 [details]
bt with symbols

On pc Debian x86-64 with master sources updated today (commit 9f417544f83fb5645abd7b74382bede2246c73b8), a clean build and a brand new LO profile, I could reproduce this.
Attached bt (no specific logs on console).
Comment 3 Julien Nabet 2012-12-05 19:09:31 UTC
Maximiliano: thank you a lot! 
Indeed, it corresponds exactly to the bug I had created fdo#56460, https://bugs.freedesktop.org/show_bug.cgi?id=56460. I had put it as Invalid seeing that no one had reproduced it.

Thorsten, Radek: Would any one of you have time for this one?
Comment 4 Julien Nabet 2012-12-05 19:10:46 UTC
*** Bug 56460 has been marked as a duplicate of this bug. ***
Comment 5 Michael Meeks 2012-12-06 11:23:56 UTC
Almost certainly a memory-management / lifecycle nasty. Any chance of a nice valgrind trace from a build with symbols ? [ I know it's slow to build - but -very- helpful ].

Thanks for unwinding all the duplicates !
Comment 6 Julien Nabet 2012-12-06 12:28:23 UTC
Michael: I had put a Valgrind log here: https://bugs.freedesktop.org/attachment.cgi?id=69374&action=edit
but it was more than a month ago, so it must be far less useful by now :(

I build with symbols so I'll try to find some time tonight to retrieve it.
About Valgrind, does http://wiki.documentfoundation.org/BugReport#How_to_get_a_valgrind_log_.28on_Linux.29 sufficient or do you think about specific options for this case? (Valgrind is so long to run that I'd prefer to launch it once a time :-))
Talking about slowness, do you think this may help:
http://nabble.documentfoundation.org/Alternative-complementary-to-Valgrind-with-MemorySanitizer-ThreadSanitizer-LLVM-td4020696.html ?
Comment 7 Julien Nabet 2012-12-06 19:49:34 UTC
Created attachment 71093 [details]
new Valgrind trace

Michael: here is a new Valgrind trace
Comment 8 Julien Nabet 2012-12-06 19:59:17 UTC
Michael: Reading the Valgrind trace + Opengrok/cgit history, I wonder if it could be due to http://cgit.freedesktop.org/libreoffice/core/commit/?id=d2f6a87ac7adb3f60f7eae7c5a8f8a9076b7a75c
Comment 9 Maximiliano Castañón 2012-12-07 15:01:37 UTC
Hi, when I find a but ever when I can I report it, obvious only for Floss projects. ;)
Comment 10 Terrence Enger 2012-12-12 11:55:17 UTC
Deeming this a dup of bug 55974 because of the similarity of the first 20 frames in the backtraces.

*** This bug has been marked as a duplicate of bug 55974 ***