Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Word processor crashes when opening file | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | Unknown <non-migrated> | ||||||
Component: | code | Assignee: | philipp.lohmann | ||||||
Status: | CLOSED FIXED | QA Contact: | issues@sw <issues> | ||||||
Severity: | Trivial | ||||||||
Priority: | P2 | CC: | issues | ||||||
Version: | OOo 1.0.1 | Keywords: | oooqa | ||||||
Target Milestone: | --- | ||||||||
Hardware: | PC | ||||||||
OS: | Linux, all | ||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||
Developer Difficulty: | --- | ||||||||
Issue Depends on: | |||||||||
Issue Blocks: | 14053 | ||||||||
Attachments: |
|
Description
Unknown
2003-04-02 02:41:07 UTC
Created attachment 5405 [details]
Word document that crashes the word processor
I reproduced your problem on Linux with OpenOffice1.1beta1 under valgrind. I'll upload the stack traceback next. Thanks! Created attachment 6169 [details]
valgrind stack traceback of ooo1.1beta1 on rh8. Wild pointer in PrintFontManager::getMetrics?
Reassigned to MRU I was not able to reproduce the crash on my RedHat 7.2. But Dan's stack is a kind of evidence... ;-) and this tells us, that it is not to be found in the WinWord filter. MRU->HDU: Can you see from the stack, what the problem might be? psprint... problem does not exist anymore in current version; however i found a side effect which while debugging: this would cause type1 fonts with adjacent afm files not to be recognized. fixed in CWS vcl10 *** Issue 14629 has been marked as a duplicate of this issue. *** verified in vcl10 *** Issue 14919 has been marked as a duplicate of this issue. *** *** Issue 14871 has been marked as a duplicate of this issue. *** *** Issue 14871 has been marked as a duplicate of this issue. *** changes are in 645m4s1, closing issue *** Issue 15489 has been marked as a duplicate of this issue. *** *** Issue 14836 has been marked as a duplicate of this issue. *** Adding keyword 'valgrind', since I seem to recall I needed to use valgrind to track it down. No, really. remove keyword 'valgrind' |