Closed
Bug 282405
Opened 20 years ago
Closed 2 years ago
Crash if window is destroyed while executing onChange [@ g_type_check_instance_is_a]
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: MatsPalmgren_bugz, Unassigned)
Details
(Keywords: crash, testcase)
Crash Data
Attachments
(3 files)
Crash if window is destroyed while executing onChange. STEPS TO REPRODUCE: 1. load attached testcase 2. follow instructions in testcase ACTUAL RESULTS: onChange handler is triggered - alert pops up, crash follows. EXPECTED RESULTS: onChange handler should not be triggered I think. Reproducible: about 50% in the nightly build, less so in the debug build. PLATFORMS & BUILDS TESTED: Bug occurs in Mozilla nightly build GTK2+XFT 2005-02-08-03 trunk Linux. Bug occurs in Linux -current debug build. Bug does not seem to occur in GTK1 builds - the onChange handler is not triggered. The type of form control is not important, I first saw it using a <select onchange>.
| Reporter | ||
Comment 1•20 years ago
|
||
| Reporter | ||
Updated•20 years ago
|
Summary: Crash if window is destroyed while executing onChange → Crash if window is destroyed while executing onChange [@ g_type_check_instance_is_a]
| Reporter | ||
Comment 2•20 years ago
|
||
| Reporter | ||
Comment 3•20 years ago
|
||
Comment 4•20 years ago
|
||
That looks like a GTK widgetry issue....
Assignee: events → blizzard
Component: DOM: Events → Widget: Gtk
Updated•15 years ago
|
QA Contact: ian → gtk
| Assignee | ||
Updated•13 years ago
|
Crash Signature: [@ g_type_check_instance_is_a]
Comment 5•6 years ago
|
||
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Reopening because crash bugs **with testcases** should not be resolved **as WONTFIX** based on queries of crash-stats. Other resolutions may be appropriate for other reasons. (Crash signatures are not the same as bug identity; they're merely a search aid to find and group similar crashes. The bug may still be present, but the signature may have changed slightly, or the bug may even still be present with the same signature but there are simply no recent reports of crashes in that function.)
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Comment 7•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:stransky, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: blizzard → nobody
Flags: needinfo?(stransky)
Updated•2 years ago
|
Status: REOPENED → RESOLVED
Closed: 6 years ago → 2 years ago
Flags: needinfo?(stransky)
Resolution: --- → FIXED
Updated•2 years ago
|
Resolution: FIXED → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•