Crash related to manufacturing text change events

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
11 years ago
8 years ago

People

(Reporter: aaronlev, Unassigned)

Tracking

({access, crash})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
I see several crash reports related to text change events we create after a timeout. It's puzzling.

Here are two slightly different versions of the crash:
http://crash-stats.mozilla.com/report/index/d4cef263-e825-11dc-ba41-001a4bd43ed6
and
http://crash-stats.mozilla.com/report/index/e2756205-e7b2-11dc-b235-001a4bd43ed6
(Reporter)

Comment 1

11 years ago
Ginn, Evan, Alexander -- any ideas?
(Reporter)

Comment 2

11 years ago
Possibly related to bug 420053.
Just question, could we fire new text event the same time when GetModifiedText() is called? Is it technically possible?
(Reporter)

Comment 4

11 years ago
Alexander, can you explain your idea more? I don't understand it, and I also don't understand the crash. Do you know why it's crashing?
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Is this bug stale?
stacks aren't available anymore, no signature, closing as worksforme (bug 429648 might be related per comment #3)
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.