Issue 4233 - Editing imported MS-Word template crashes OpenOffice
Summary: Editing imported MS-Word template crashes OpenOffice
Status: CLOSED DUPLICATE of issue 3360
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 641
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: caolanm
QA Contact: issues@sw
URL: http://www.iki.fi/~busman/OO/kirje-e.dot
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-25 06:29 UTC by Unknown
Modified: 2002-07-26 12:15 UTC (History)
1 user (show)

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

Attachments
Patch: The correct solution (632 bytes, patch)
2002-05-15 15:45 UTC, caolanm 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2002-04-25 06:29:53 UTC 
After importing a MS-Word template I tried to edit it to see how it looked.
Results:
"Main memory shortage. Please quit other applications or close some windows
before continuing."
After that the usual notification what you get when OpenOffice knows it's going
down.
The problem is reproducable and you can get it from the URL above.
Comment 1 matthias.huetsch 2002-04-25 16:43:12 UTC 
Same reason as with issue # 3360, only now with '0x43000000' bytes.
Comment 2 Mathias_Bauer 2002-04-30 08:51:38 UTC 
Memory shortage is most probably forced by MS-Word import, if it
doesn't occur on a regular base.
Comment 3 andreas.martens 2002-05-07 08:39:24 UTC 
Is it a problem of word import?
Comment 4 caolanm 2002-05-07 10:34:56 UTC 
No, I believe that this is an exact duplicate of issue 3360, except
that its a different object type this is unrecognized this time than
the type in that example. In both cases the unrecognized object name
leads to a null object id being set on the constructed ole2 object
which seems to cause confusion later on when its reread. If assigned
to me I'm willing to find the exact problem, but as far as I can tell
the problem lies somewhere in some ole2 code in sfx2/so3/sot
Comment 5 caolanm 2002-05-15 15:45:36 UTC 
Created attachment 1660 [details]
Patch: The correct solution
Comment 6 caolanm 2002-05-15 15:47:15 UTC 
A duplicate.

*** This issue has been marked as a duplicate of 3360 ***
Comment 7 caolanm 2002-07-24 11:19:15 UTC 
Closed, working in SRX643m. Track issue 3360 for future details.
Comment 8 michael.ruess 2002-07-26 12:15:41 UTC 
Works fine with 643m. Fix will be available for OpenOffice 643.