Issue 60388 - WMF file crashes application when saving
Summary: WMF file crashes application when saving
Status: CLOSED DUPLICATE of issue 53922
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: OOo 2.0.1
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: eric.savary
QA Contact: issues@sw
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2006-01-11 23:42 UTC by flofloflo
Modified: 2006-01-13 16:02 UTC (History)
2 users (show)

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


Attachments
WMF file that crashes OO Writer when scaled to small size (8.07 KB, image/x-wmf)
2006-01-11 23:44 UTC, flofloflo
no flags Details
ODT file w/ the wmf in question embedded & resized several times (13.89 KB, application/vnd.sun.xml.writer)
2006-01-13 02:18 UTC, atdsm
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description flofloflo 2006-01-11 23:42:21 UTC
This simple WMF file crashes OO Writer when saving a document that contains it:
http://www.webterminate.com/wmf-crash.wmf 
The problem does not occur when the WMF is scaled to larger proportions (e.g.
200%). When the file is scaled to significantly smaller proportions (e.g. 10%),
OO Writer crashes immediatelly. (Both when resizing by mouse, and when resizing
in the Object properties) This behaviour seems to be affected by vertical
scaling rather than horizontal.
Comment 1 flofloflo 2006-01-11 23:44:20 UTC
Created attachment 33121 [details]
WMF file that crashes OO Writer when scaled to small size
Comment 2 michael.ruess 2006-01-12 06:56:07 UTC
Reassigned to ES.
Comment 3 atdsm 2006-01-12 21:57:24 UTC
Problem does not occur under Windows XP, and thus appears to be confined to
Linux only. Will check Gentoo Linux tonight.
Comment 4 atdsm 2006-01-13 02:17:19 UTC
Cannot confirm - problem does not occur for me using OOo 2.0.1 on Gentoo Linux.

Steps taken:
1) Open a new text document
2) Insert the windows metafile in question via Insert > Picture > From file...
3a) Save as test.odt (Writer did not crash)
3b) Resized the metafile to a small size & saved again (Writer did not crash)

flofloflo -> Can you post exact steps taken to produce the problem?
Comment 5 atdsm 2006-01-13 02:18:46 UTC
Created attachment 33167 [details]
ODT file w/ the wmf in question embedded & resized several times
Comment 6 flofloflo 2006-01-13 11:40:19 UTC
Atdsm, your file crashes my Writer as soon as it's displayed.
Here's what I use: Ubuntu Breezy (5.10) + KDE (Kubuntu), with all current
updates from main, multiverse, universe and restricted. My Openoffice comes from
http://people.ubuntu.com/~doko/OOo2/ and gives as Version: "openoffice.org2-core
2.0.1-0breezy1, Sat Jan 7 01:11:04 UTC 2006"
Maybe I should contact the packager ... (glad it's apparantly not a general OO Bug)
Comment 7 atdsm 2006-01-13 14:26:43 UTC
Yes, I would try contacting the package maintainer. Alternatively, there seem to
be several other issues dealing w/ Ubuntu that suggest checking this bug on the
Ubuntu bugzilla:

http://bugzilla.ubuntu.com/show_bug.cgi?id=18201

Also, this issue may be a duplicate of either issue 55090 or issue 53922.
Comment 8 atdsm 2006-01-13 14:48:44 UTC
Should have stated the proposed workarounds:

a) Install the official OOo 2.0.1 builds from the OOo download page (not the
Ubuntu builds)

or

b) Export MALLOC_CHECK_=2 before running OpenOffice

Please tell me if one of those workarounds solves the problem. If it does, then
I will mark this as a duplicate of issue 53922.
Comment 9 flofloflo 2006-01-13 15:31:14 UTC
I changed /usr/bin/ooffice2 to include 
$ENV{MALLOC_CHECK_} = 2;
before the exec (last line), and it WORKS PERFECTLY. Thanks.
What drawbacks does that solution have?
Comment 10 atdsm 2006-01-13 15:40:50 UTC
It's something to do with memory allocation, although I'm really not sure what
happens behind the scenes with that environment variable. You could post
followup questions to the Ubuntu bug if you wish, or read through issue 53922.

Glad that it works for you, anyway.

Given a solution duplicate to the workaround in issue 53922, I'm marking this as
a duplicate.

*** This issue has been marked as a duplicate of 53922 ***
Comment 11 atdsm 2006-01-13 16:02:24 UTC
Closing...