Closed Bug 263301 Opened 20 years ago Closed 19 years ago

deleting multiple rows from a large table often crashes [@ destroyTimerEvent]

Categories

(Core :: DOM: Editor, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: pbrears, Assigned: mozeditor)

Details

(Keywords: crash, Whiteboard: testcasewanted)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

I've a large document that I can email to a delevleoper but I'd prefer not to
post it publicly. It contains serveral tables with 9 cols and upto 500 rows.
When doing a multiselct delete of 4/5 rows it often crashes. It's not 100%
reporducable. I've managed to get it to happen 10 times this morning but _not_
at the same points in the page.

Reproducible: Sometimes
Steps to Reproduce:
1. Load page into composer (it's on a network share if that matters and it about
406 KB)
2. Select several rows in the table (using mouse and draging)
3. Right click => table delete => Row

Actual Results:  
It launches the feedback agent.

Expected Results:  
delete the rows...

The document that was being edited was a customer's security policy and
therefore I can't upload it here but if a developer wants I can try and fake a
similar format document and see if it can be reporduced without sensitive
information. There should be a number of feedback reports from my email address
caused by this bug.
Can you launch talkback.exe in your components folder and give us the Talkback
IDs here (almost noone can search for your e-mail adress in the TB reports, so
we need the IDs)?
Severity: normal → critical
Summary: deleting multiple rows from a large table often crashes → deleting multiple rows from a large table often crashes
Keywords: stackwanted
TB1170091G, TB1170059Y, TB1169936E, TB1169640Y, TB1169514Q, TB1169177G
All the stacks look like:

0x006f004a
destroyTimerEvent 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 456]
PL_DestroyEvent 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 713]
PL_HandleEvent 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 686]
PL_ProcessPendingEvents 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/plevent.c,
line 612]
nsEventQueueImpl::ProcessPendingEvents 
[d:/BUILDS/tinderbox/Mozilla1.7.3/WINNT_5.0_Clobber/mozilla/xpcom/threads/nsEventQueue.cpp,
line 395]

Paul, any chance you could replace the text in your testcase with dummy text and
attach it to this bug if it still shows the problem?
Keywords: crash
Keywords: stackwanted
Summary: deleting multiple rows from a large table often crashes → deleting multiple rows from a large table often crashes [@ destroyTimerEvent]
Whiteboard: testcasewanted
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Crash Signature: [@ destroyTimerEvent]
You need to log in before you can comment on or make changes to this bug.