Does it crash or just hang?
------- Comment #1 from email@example.com 2005-11-17 07:15 PST ------ Does it crash or just hang? --> no, it realy crashes. as demo you can just extend the contexmenu with another menuitem and call alert when the menuitem gets clicked.
Could you install with talkback and get a talkback ID for the crash? http://kb.mozillazine.org/Talkback
done: TB12619729H, TB12619727W, TB12619636Z this time i've used localName form am menu item.
I swear I've seen a stack like this before. Incident ID: 12619636 Stack Signature nsWeakReference::`vftable' 3b77992d Product ID Thunderbird15 Build ID 2005102519 Trigger Time 2005-12-05 05:54:11.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module xpcom_core.dll + (00042535) URL visited User Comments Since Last Crash 28216 sec Total Uptime 1185303 sec Trigger Reason Access violation Source File, Line No. N/A Stack Trace nsWeakReference::`vftable' 0x778b0c24 nsHTMLEditor::AbsolutePositionSelection [e:/builds/tinderbox/Tb-Mozilla1.8/WINNT_5.0_Depend/mozilla/editor/libeditor/html/nsHTMLAbsPosition.cpp, line 90] nsChromeTreeOwner::QueryInterface 0xf9e5e8cb
i've noticed that you have changed the severity to critical. if there is something i can do to help you, please let me know.
try crashing again w/ a different build (your stack isn't very happy), or if you're willing to use a developer's build and install windbg, let us know, and we'll make arrangements (that'd be ideal).
(In reply to comment #7) > or if you're willing to use a developer's build and install windbg, let us > know, and we'll make arrangements (that'd be ideal). of course, just tell me what to do...
hrm, sorry for the delay, this got lost in some shuffle. i'm working w/ people on getting builds available. hopefully they'll happen relatively soon.
Ok, you can use http://symbols.db48x.net/ as the symbol server. Unfortunately, I was sent the symbols for the 1.5 build as a seperate archive, so for the moment you have to use http://symbols.db48x.net/symbols_1_5/ as the url. The symbols are from builds dated 20060517.
Reporter, does the issue still occur in the latest supported 2.0.0.x / trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 188.8.131.52)
RESO INCO per lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.