Closed Bug 78422 Opened 23 years ago Closed 15 years ago

crash after viewing xul source [@ nsEventStateManager::PreHandleEvent]

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P1)

defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: mcalisk, Assigned: saari)

References

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    20001010

If I open a XUL template then right-click on the screen and choose view source, 
then close that window I get a an error and the program crashes. The error 
says "The instruction at "0X00000" referenced memory at "0X000000". The memory 
could not be read"

Reproducible: Always
Steps to Reproduce:
1.Open a XUL Template.
2.Choose view page source.
3.Close the source page.

Actual Results:  Mozilla crashes.

Expected Results:  The window should close, and I should be able to contunue 
using Mozilla.
Keywords: crash
I see this on a linux debug build from 2001-05-01

Steps to reproduce:

1) Load chrome://communicator/content/pref/pref-appearance.xul
2) right-click and select view source.
3) click in the resulting window (closing does not cause a crash for me on Linux)

#0  0x414dd138 in nsEventStateManager::PreHandleEvent (this=0x89ebf78, 
    aPresContext=0x88b8d20, aEvent=0xbfffe668, aTargetFrame=0x89eb570, 
    aStatus=0xbfffe594, aView=0x89dbb68) at nsEventStateManager.cpp:483
#1  0x41d6056f in PresShell::HandleEventInternal (this=0x89e6778,
aEvent=0xbfffe668, 
    aView=0x89dbb68, aFlags=1, aStatus=0xbfffe594) at nsPresShell.cpp:5545
#2  0x41d60178 in PresShell::HandleEvent (this=0x89e6778, aView=0x89dbb68, 
    aEvent=0xbfffe668, aEventStatus=0xbfffe594, aForceHandle=0,
aHandled=@0xbfffe538)
    at nsPresShell.cpp:5478

(gdb) frame 0
#0  0x414dd138 in nsEventStateManager::PreHandleEvent (this=0x89ebf78, 
    aPresContext=0x88b8d20, aEvent=0xbfffe668, aTargetFrame=0x89eb570, 
    aStatus=0xbfffe594, aView=0x89dbb68) at nsEventStateManager.cpp:483
483           win->GetRootFocusController(getter_AddRefs(focusController));
(gdb) p win
$1 = {mRawPtr = 0x0}
(gdb) p globalObj
$2 = {mRawPtr = 0x0}
Assignee: trudelle → joki
Status: UNCONFIRMED → NEW
Component: XP Toolkit/Widgets: XUL → Event Handling
Ever confirmed: true
OS: Windows 2000 → All
QA Contact: jrgm → gerardok
Hardware: PC → All
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.2
Priority: -- → P1
QA contact updated
QA Contact: gerardok → madhur
I'm not able to reproduce this on Win2K.  The source page comes up blank for me 
and nothing happens when I click.  I'm not sure if the blank source is another 
bug (do we treat xul source differently?) but I don't see an event problem.  Is 
this still happening on linux?
Looks like something has broken the viewing of XUL page source in general (at
least for some XUL docs).
Moving to 0.9.3.  Created new bug for not being able to view-source on xul and 
set it as dependency.
Depends on: 87918
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Missed 0.9.3.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
->0.9.5
Target Milestone: mozilla0.9.4 → mozilla0.9.5
-> 0.9.6
Target Milestone: mozilla0.9.5 → mozilla0.9.6
Looks like this won't make it in for 0.9.6.
0.9.6 has passed, moving to 0.9.7.  Load balancing 0.9.7 list shortly
Target Milestone: mozilla0.9.6 → mozilla0.9.7
Moving bugs from 0.9.7 for triaging in 0.9.8
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Target Milestone: mozilla0.9.8 → mozilla0.9.9
->moz1.1 (dumping ground) per ADT triage
Target Milestone: mozilla0.9.9 → mozilla1.1
QA Contact: madhur → rakeshmishra
BTW bug 101834 has same stack signature.
Summary: crash after viewing xul source → crash after viewing xul source [@ nsEventStateManager::PreHandleEvent]
Blocks: 101834
QA Contact: rakeshmishra → trix
Depends on: 206691
http://bugzilla.mozilla.org/show_bug.cgi?id=179125#c3

joki is no longer here
Assignee: joki → saari
Status: ASSIGNED → NEW
QA Contact: trix → ian
retargeting
Target Milestone: mozilla1.1alpha → Future
bz

attempted to find matching stacks on talkback
nsEventStateManager::PreHandleEvent doesn't fall in top 500 of talkback, so selected a 10 random crashes of 100 that don't have comments ... no crashes containing nsWidget.  (nsWidget is near top of stack trace for this bug - but of course might not be part of the process leading up to every crash)

9 crashes on crash-stats, none contain nsWidget

reporter email address is dead
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsEventStateManager::PreHandleEvent]
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: