Issue 21798 - Error displaying in OpenOffice.org 1.1 RC5
Summary: Error displaying in OpenOffice.org 1.1 RC5
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: Other Windows 98
: P2 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@sw
URL:
Keywords: oooqa
: 21799 21800 21801 21802 21803 21804 21805 21806 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-10-28 09:02 UTC by Unknown
Modified: 2004-01-05 17:00 UTC (History)
2 users (show)

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


Attachments
error (111.90 KB, image/jpeg)
2003-12-02 04:30 UTC, Unknown
no flags Details
error for openoffice (111.90 KB, image/jpeg)
2003-12-02 04:31 UTC, Unknown
no flags Details
error for openoffice (111.90 KB, image/jpeg)
2003-12-02 04:31 UTC, Unknown
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2003-10-28 09:02:18 UTC
I usually work with my document using OpenOffice.org 1.1 RC 5 for a long period 
using from day to evening and I also usually open up to 3-4 Openoffice.org 
document for OpenOffice.org Writer and Impress. So I eventually encountered 
this problem where a window pop out and indicated me that there's an internal 
error problem and what I can do is only press OK and the whole OpenOffice.org 
gone. I need to restart and luckily OpenOffice.org provided the Recovery files.

Question:- how i can solve this problem and also is it the OpenOffice.org not 
really compatible with windows 98?(I mentioned about this because my friend is 
using the OpenOffice.org in Windows XP and he told me that he has not 
encountered with this problem before)
Comment 1 utomo99 2003-10-28 10:09:36 UTC
*** Issue 21799 has been marked as a duplicate of this issue. ***
Comment 2 utomo99 2003-10-28 10:09:52 UTC
*** Issue 21800 has been marked as a duplicate of this issue. ***
Comment 3 utomo99 2003-10-28 10:11:03 UTC
*** Issue 21801 has been marked as a duplicate of this issue. ***
Comment 4 utomo99 2003-10-28 10:11:15 UTC
*** Issue 21802 has been marked as a duplicate of this issue. ***
Comment 5 utomo99 2003-10-28 10:11:36 UTC
*** Issue 21803 has been marked as a duplicate of this issue. ***
Comment 6 utomo99 2003-10-28 10:12:30 UTC
*** Issue 21804 has been marked as a duplicate of this issue. ***
Comment 7 utomo99 2003-10-28 10:12:42 UTC
*** Issue 21805 has been marked as a duplicate of this issue. ***
Comment 8 utomo99 2003-10-28 10:12:56 UTC
*** Issue 21806 has been marked as a duplicate of this issue. ***
Comment 9 utomo99 2003-10-28 10:19:25 UTC
Please find the way to reproduce it. 
your report is not enough to investigate the problem. 
and please only hit one time, no need to repeat it many times, until
you create many issue number with same Issue. 


Change the version as reporter description
Comment 10 Rainer Bielefeld 2003-10-28 10:55:11 UTC
He Reporter,

please start and watch your WIN98 program RSRCMTR.EXE. Does your crash
happen when resources are "yellow or less?"

I believe the problem you are talking about is a GDI resources
problem, and then this would be a DUP of issue 15222

Rainer
Comment 11 utomo99 2003-10-28 11:10:54 UTC
reassign issue to owner of selected subcomponent
Comment 12 stefan.baltzer 2003-10-28 13:50:15 UTC
SBA: Based on this description, it is far from clear if we have the
same problem as in issue 15222 ("Enormous System Resources consumption
causes crash"). But to keep an eye on i.e. the system ressources
indeed may give hints what goes wrong. It is true that Win98 and WinXP
"work different" concerning main memory handling, but in general there
should be no different findings on either Windows platform. 

SBA-> ckong333: The guess "Did not occur on a friend's WinXP" does not
get us any further. Best if we had a way to reproduce this. "Working
on a handful of documents throughout a day" is not helpful yet, sorry.

Having a look at the documents _may_ help, for example if there is a
document with 300+ OLE objects or one with huge graphics that pump up
the file size beyond the Systems memory, but these are rare cases.

The crash reporter (does not always come up, I know) would be the best
to make it clear to the developers where in the code the problem
occurs. Of course, only if the report is sent!

By the way: How often do you encounter such a crash? If you worked
like this for a few months and you have ONE crash that you can't
reproduce, it may be too much effort to run after this. There is
already a "nice pile" of crash reports in the database that we CAN adress.

This does not look like a Word processor issue unless there is a clear
 "do this and that with this Writer document to crash." -> Changed
component to "Framwork", Priority to P2 and reassign to Thorsten.
Comment 13 Rainer Bielefeld 2003-11-07 10:09:31 UTC
If I will not see any further action as votes, attachments or
confirmations, I will have to close this issue 2003-11-15 as INVALID.

Rainer
Comment 14 Rainer Bielefeld 2003-11-30 09:37:16 UTC
Closing issue due to reporter's inactivity as INVALID.

Rainer
Comment 15 Unknown 2003-12-02 04:30:47 UTC
Created attachment 11690 [details]
error
Comment 16 Unknown 2003-12-02 04:31:05 UTC
Created attachment 11691 [details]
error for openoffice
Comment 17 Unknown 2003-12-02 04:31:11 UTC
Created attachment 11692 [details]
error for openoffice
Comment 18 Rainer Bielefeld 2004-01-05 17:00:03 UTC
Hi ckong333,

thanks for your attachment (id=11691) and similar, but that will not help us,
because so we do not get any further information.

Closing due to lack of possibility to reproduce.

Rainer