Closed
Bug 322023
Opened 19 years ago
Closed 18 years ago
crash [@ nsMenuFrame::Notify ed8d5e50] access violation (nsMenuFrame.cpp line 1031) clicking on a link
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 241733
People
(Reporter: tonymec, Assigned: vlad)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
9.05 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051230 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051230 Firefox/1.5 see talkback event TB13448127M Reproducible: Didn't try Steps to Reproduce: Actual Results: crash Expected Results: no crash Here are the details of the Talkback report: Stack Signature nsMenuFrame::Notify ed8d5e50 Product ID Firefox15 Build ID 2005123003 Trigger Time 2005-12-31 13:54:18.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module firefox.exe + (0026c769) URL visited User Comments Since Last Crash 97064 sec Total Uptime 97064 sec Trigger Reason Access violation Source File, Line No. c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsMenuFrame.cpp, line 1301 Stack Trace nsMenuFrame::Notify [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/layout/xul/base/src/nsMenuFrame.cpp, line 1301] nsTimerImpl::Fire [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/threads/nsTimerImpl.cpp, line 407] PL_HandleEvent [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/threads/plevent.c, line 689] 0x778b0c24 0x00200064 0xc68b0090
Reporter | ||
Updated•19 years ago
|
Summary: crash [@ nsMenuFrame::Notify ed8d5e50] clicking on a link (nsMenuFrame.cpp line 1031) → crash [@ nsMenuFrame::Notify ed8d5e50] access violation (nsMenuFrame.cpp line 1031) clicking on a link
Comment 1•19 years ago
|
||
Some idea of what you were doing would help; it's impossible to fix a bug the developers can't reproduce. Also, please list any extensions you had installed.
Reporter | ||
Comment 2•19 years ago
|
||
Reporter | ||
Comment 3•19 years ago
|
||
(In reply to comment #1) > Some idea of what you were doing would help; it's impossible to fix a bug the > developers can't reproduce. Also, please list any extensions you had > installed. > I had just clicked right on an image link, "Open in New Tab". I have now created an attachment with the list of my extensions. If I can't reliably reproduce a crash _myself_, does it mean I may not report it?
Reporter | ||
Updated•19 years ago
|
Attachment #207297 -
Attachment mime type: text/plain → text/html
Comment 4•19 years ago
|
||
It's fine that you reported it; I'm not suprised you can't reproduce something on a short timer and probably depends on exactly how you moved the mouse. What I can figure out without reproducing this: http://lxr.mozilla.org/seamonkey/source/layout/xul/base/src/nsMenuFrame.cpp#509 is where the timer gets kicked off. If somehow a menu item were selected and the menu disappeared without generating an NS_MOUSE_EXIT_SYNTH event (not quite sure how this would happen), and the content got destroyed before the frame was properly destroyed, the timer could be set off on a frame with an invalid content pointer. It would be extremely hard to reproduce because it would depend on the timer executing at exactly the right moment to interrupt event processing, making this extremely infrequent. Some extension that put a submenu on the context menu would be necessary because there are no submenus by default on links. Cursory search shows as possibly related: Bug 301537, Bug 297570, Bug 273981 (traces not really the same, but something similar seems to be happening). Moving to a more appropriate component.
Component: General → XP Toolkit/Widgets: Menus
Product: Firefox → Core
Version: 1.5 Branch → 1.8 Branch
Updated•19 years ago
|
QA Contact: general → xptoolkit.menus
Reporter | ||
Comment 5•19 years ago
|
||
Eli, the way you describe it, it sounds like it could be a side-effect of Firefox gobbling lots of memory and thus causing Windows to start seesawing on its disk swap file, which in turn slows all running programs (and especially Firefox) to an asthmatic snail's crawl. If the timer you mention measures wall clock time and not application CPU time, it could time out before the application got enough memory cycles to properly set up the related object (in this case, the context right-click menu on a link which is also an image, I suppose). I was hunting for "Open Link in New Tab" but the mouse could quite possibly have passed over other link-related or image-related menu items with submenus. On a link similar to the one I clicked at the time of failure, I notice (among many menu items which aren't submenus) the following submenus: - deviantLINK to <deviantname> -> - Open Link Host -> - View Image in... -> - Zoom image -> - Character encoding -> - View source with... -> Note: Firefox's memory use usually climbs (slowly) without limit until I restart it. AT the moment Firefox uses 203 MB swap according to Windows Task Manager, with the next biggest program (Windows Explorer) at 36.5 MB; but Firefox often (more than once per 24h) climbs to 400 MB or so, at which point everything slows down until I close down Firefox and reopen it -- even with all the same pages in the same tabs, just restarting Fx can usually bring its memory use from above 400 MB to below 100 MB.
Dupe of bug 241733?
Comment 8•18 years ago
|
||
marking as dupe. reporter: feel free to undupe if you disagree :) *** This bug has been marked as a duplicate of 241733 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 9•18 years ago
|
||
(In reply to comment #8) > marking as dupe. reporter: feel free to undupe if you disagree :) > > *** This bug has been marked as a duplicate of 241733 *** > I lack proper expertise; but this one happened to me in Firefox, and that one is described as a mailer bug. Well, let's hope you know what you're doing. Also, I'm using mostly Linux these days.
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: xptoolkit.menus → xptoolkit.widgets
Updated•13 years ago
|
Crash Signature: [@ nsMenuFrame::Notify ed8d5e50]
You need to log in
before you can comment on or make changes to this bug.
Description
•