Closed Bug 145608 Opened 22 years ago Closed 22 years ago

Composer crash when backspacing repeatedly in 'normal' view

Categories

(SeaMonkey :: Composer, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 136165

People

(Reporter: fun, Assigned: mozeditor)

Details

(Keywords: crash, dataloss)

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc3)
Gecko/20020516
BuildID:    2002051606 1.0 branch

Composer crash when backspacing repeatedly in 'normal' view. The second
time, it happened around text I had repeatedly shuffled between various
combinations of bold, italic or <tt> with keypresses.

The file was about 60k of HTML. (The draft of the Mozilla 1.0 faq, to be
precise. "Eating your own dogfood," indeed.)

Reproducible: Sometimes

Steps to Reproduce:
1. Edit a long document for hours.
2. Go to a fiddly bit and backspace repeatedly.

Actual Results:  Crash.

Expected Results:  No crash.

Dataloss (except that I press ctrl+S by spinal reflex every sentence
or so, so I didn't lose much).

This one is annoyingly vague and not easily reproducible, and I
wouldn't even file a bug on it except ... I have two Talkback reports!

TB6450885W
TB6412821Y

These are also the only two crashes I've had in two weeks of using
1.0-branch builds, too.
Keywords: dataloss
Keywords: crash
And a further crash with Composer open (though I was in the browser at the time):

TB6465188Y

Hopefully someone can look these up before they expire from the talkback
database ;-)
If you can find a concrete testcase for this please add it here.  This is 
probably a dup of another bug that I haven't been able to reproduce, and for 
which the talkback logs have not pointed me to anything that looks bad.  But I'll 
check the logs and see.
Assignee: syd → jfrancis
this is a dup of 136165. patch coming there shortly.


*** This bug has been marked as a duplicate of 136165 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.