Issue 9686 - OOo crashes on Win 98 when number of rows specified for table exceeds OOo internal limit
Summary: OOo crashes on Win 98 when number of rows specified for table exceeds OOo int...
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: ui (show other issues)
Version: 643C
Hardware: Other Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: prgmgr
QA Contact: issues@sw
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2002-11-30 02:18 UTC by Unknown
Modified: 2003-09-08 16:56 UTC (History)
2 users (show)

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

Attachments
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-11-30 02:18:00 UTC 
I have openoffice 643C installed on my Windows 98 system.To replicate bug:
1.From start menu select programs,openoffice 643C and then text ducument.
2.Select insert table by selecting the icon on the left side.
3.The dialog box that appears will have 5 in columns and 2 in rows cell.
4.Place the cursor to the right of the 2 in the rows cell and clear it using 
the backspace key.
5.Then rapidly enter twenty ones(11111111111111111111) into the cell.
6.Press the OK button.
7.System crashes and ultimately generates three error messages.
Comment 1 Unknown 2002-11-30 18:59:49 UTC 
I can not duplicate this bug on Win NT 4.0, OOo 643C.

When I did Step 5: enter twenty ones(11111111111111111111) 
into the cell then click on OK button, 
a table with 5 columns and 3276 rows was inserted.
(3276 was the default max values of row).

Even though I enter thirty ones into the cell, 
a table with same size (5*3276) was inserted.
Comment 2 prgmgr 2002-12-01 21:41:22 UTC 
Raj and Wen-chiao, thank you for using and supporting OOo.

OOo did not crash in my test environment.
As Wen-chiao, mentioned OOo limits the number of columns in a table.

Unable to duplicate on Win2K server SP3, OOo 643c.

I think this should become an enhancement request where there the max 
value for the number of columns/rows is set inside the field or a 
dialog pops up when an user decides to run some bounds checking :).

User summary:
SYSTEM CRASHES WHEN HIGH ROW VALUES ARE ENTERED
Comment 3 h.ilter 2002-12-03 12:44:33 UTC 
Reassigned to MRU
Comment 4 prgmgr 2002-12-04 20:07:22 UTC 
Bounds issue.
Comment 5 malte_timmermann 2002-12-19 16:36:49 UTC 
Seems we talked from different things:
You meant bounds checking = behavior of e.g. dialogs, when invalid 
number in dialog is entered.
I meant bounds checking = Using Compuware *BoundsChecker* for 
searching 
memory error.

Please don't send me bugs for dialog behavior or something like that.

Sorry for the confusion.
Comment 6 Joost Andrae 2003-05-26 16:53:09 UTC 
JA: cannot reproduce this
Comment 7 Joost Andrae 2003-05-26 16:53:26 UTC 
JA: closing issue