Issue 59355 - Writer crashes with the attached document
Summary: Writer crashes with the attached document
Status: CLOSED DUPLICATE of issue 56408
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.0.1
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: crash, oooqa
Depends on:
Blocks:
 
Reported: 2005-12-14 14:50 UTC by doko
Modified: 2005-12-20 00:08 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
document showing the crash (28.77 KB, application/vnd.sun.xml.writer)
2005-12-14 14:51 UTC, doko
no flags Details
stack trace (4.87 KB, text/plain)
2005-12-14 14:52 UTC, doko
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description doko 2005-12-14 14:50:18 UTC
Writer crashes with the attached document (the window opens, but the menus don't
get displayed anymore), leaving on the console the message:

*** glibc detected *** double free or corruption (fasttop): 0x081f6978 ***

Seen with the Ubuntu packages based on m143, and the build from ftp.linux.cz,
based on m145.

Workaround: Set MALLOC_CHECK_ to any value, even "2" works, which should abort
the program.

Attaching the strace as well.
Comment 1 doko 2005-12-14 14:51:25 UTC
Created attachment 32397 [details]
document showing the crash
Comment 2 doko 2005-12-14 14:52:47 UTC
Created attachment 32398 [details]
stack trace
Comment 3 michael.ruess 2005-12-14 15:04:31 UTC
Reassigned to ES.
Comment 4 aziem 2005-12-15 04:51:00 UTC
Confirm crash on Linux (Fedora Core 4) with OpenOffice.org 2.0.1rc2, 2.0.0, and
1.1.5.  The crash only occurs with MALLOC_CHECK_= (blank), but the output is
different here:

$ MALLOC_CHECK_= openoffice.org-2.0 crash.sxw
malloc: using debugging hooks
Segmentation fault

BTW, I would be very interested to understand how MALLOC_CHECK_ crashes this way
as I often use =2 to debug OpenOffice.org.  Should I use MALLOC_CHECK_= (blank)?
Comment 5 aziem 2005-12-15 05:05:48 UTC
Sorry, I would like to un-confirm issue because other programs crash with
MALLOC_CHECK_= (blank).
Comment 6 alex.thurgood 2005-12-19 06:40:41 UTC
Hi,

This file doesn't crash 2.0.1 RC5 on my Linux system. Setting to worksforme.

alex
Comment 7 doko 2005-12-19 12:00:27 UTC
sorry to reopen the report. even if it works for you, please add the glibc
version used on your "Linux system".
Comment 8 lohmaier 2005-12-20 00:07:27 UTC
marking duplicate of the other MALLOC_CHECK_ but on ubuntu..

I guess these are related/double.

If not, please reopen.

*** This issue has been marked as a duplicate of 56408 ***
Comment 9 lohmaier 2005-12-20 00:08:35 UTC
closing for now.