Issue 33011 - crash while loading Particular.DOC
Summary: crash while loading Particular.DOC
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 1.1.1
Hardware: PC All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: crash
Depends on:
Reported: 2004-08-15 22:14 UTC by manyac
Modified: 2014-02-27 14:31 UTC (History)
4 users (show)

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

bzipped tarball with 'bad' Microsoft Word files (644.63 KB, application/x-bzip2)
2004-08-15 22:18 UTC, manyac
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description manyac 2004-08-15 22:14:14 UTC
When I load AUDIO_CD.DOC or VIDEO_CD.DOC, ooffice hangs, and stops consuming CPU
time. When I load SYSCDXXX.DOC, I get the message:

An unrecoverable error has occurred. All modified files have been saved and can
probably be recovered at program restart.

I'm running gentoo-linux, and installed ooffice using the gentoo packaging
system, so the bug could also be in a patch from gentoo.
Comment 1 manyac 2004-08-15 22:18:03 UTC
Created attachment 17149 [details]
bzipped tarball with 'bad' Microsoft Word files
Comment 2 michael.ruess 2004-08-16 08:03:20 UTC
MRU->MM: The three files in the attachment are all Word 6 documents. They seem
to crash due to the same reason. All give the Assertion "Unknown ww6 sprm,
dangerous, report to development".
Comment 3 martin_maher 2004-10-13 14:27:10 UTC
mmaher->jmarmion: Sounds like a corrupt Word file. 
Comment 4 john.marmion 2004-10-15 15:20:25 UTC
Comment 5 john.marmion 2004-11-09 16:39:30 UTC
sunbitter: do you know the origin of the attached 3 word6/95 docs. OOo sees the
same problem in all 3 docs. They all contain 3 (unknown to OOo) SPRM (Single
Property Modifiers). Later there is a conflict of what the document states is
the length of the main document text stream and what length is actually
contained in the document. Saving these docs back to word6/95 format in Word and
the unknown SPRMs and length conflict dissappear and OOo can successfully import
them. Obviously OOo should not fall over while attempting to import these docs
but knowing their origin would help. thanks.    
Comment 6 michael.ruess 2005-01-13 11:52:24 UTC
Set target to OO later, as long as these are Word6/95 documents and the fix is
VERY complicated.
As a workaround, these can be saved as Word97 or newer format.
Comment 7 daniel.rentz 2005-04-19 18:04:21 UTC
Florian, please take over
Comment 8 Mathias_Bauer 2006-08-30 15:30:48 UTC
assigning to hbrinkm
Comment 9 Rainer Bielefeld 2013-12-11 05:32:06 UTC
(a) Trivial Crash?

(b) It seems is not a AOO committer, so Assignee 
     back to list!
(c) Still crashes for me with  
    "Ooo 3.1.1 German WIN7  Home Premium  (64bit) DE [OOO310m19 (Build 9420)]"!	
(d) No longer crashes with sever installation of 
    "OOo 3.3.0 English UI / German locale [OOO330m20 (Build 9567)]" on 
     WIN7  Home Premium  (64bit) DE. 
(e) Somewhere between OOo 3.1.1 to OOo 3.3.0 crash disappeared, behavior 
    changed to "Bug 123830 - Particular.doc fails to open with Error Message"
(f) Has been fixed for AOO 3.3.0, but because of crippled Target Milestone
   selector contents (Bug 123063) I only can select TM = 4.1.0, no correct
   information can be contributed.
(g) Latest confirmation for AOO OOo 3.1.1, but because of incomplete LCo 
    selector (Bug 123063) no correct information can be contributed.
Comment 10 Rainer Bielefeld 2013-12-11 05:35:26 UTC
Fixed due to Comment 9 (d)
Comment 11 liuping 2014-02-27 08:15:28 UTC
Reader Error:This is not WinWord97 file
AOO410m1(Build:9750)  -  Rev. 1570848
Rev.1570848 on windows7
Comment 12 Rainer Bielefeld 2014-02-27 09:43:43 UTC
(In reply to liuping from comment #11)
That error message is not exactly the same as the reported CRASH ;-)

And for the error message see (e)!

So I think we should close this one again.
Comment 13 Oliver-Rainer Wittmann 2014-02-27 14:30:56 UTC
(In reply to Rainer Bielefeld from comment #12)
> (In reply to liuping from comment #11)
> That error message is not exactly the same as the reported CRASH ;-)
> And for the error message see (e)!
> So I think we should close this one again.

I agree
--> resolving this issue as fixed and verified.
--> resetting field Target Milestone to keep this issue out of the list of 'solved issues for 4.1.0'
Comment 14 Oliver-Rainer Wittmann 2014-02-27 14:31:17 UTC