Closed Bug 18792 Opened 25 years ago Closed 25 years ago

[CRASH]selecting edit menu while page is loading causes crash

Categories

(SeaMonkey :: UI Design, defect, P3)

x86
Windows 98
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: rcrespo, Assigned: trudelle)

Details

i tried to paste a url into the location bar and it didnt work (shift+insert) then i tried the usual way by hitting the "Edit" menu and it crashed.. the following message then came up MOZILLA caused an invalid page fault in module GKHTML.DLL at 015f:60217247. Registers: EAX=0063f794 CS=015f EIP=60217247 EFLGS=00010206 EBX=6026ce50 SS=0167 ESP=0063f768 EBP=0063f79c ECX=0063f78c DS=0167 ESI=00000000 FS=511f EDX=0063f768 ES=0167 EDI=00000000 GS=0000 Bytes at CS:EIP: 8b 1e 89 45 f0 e8 29 29 fd ff 50 56 ff 53 30 8b Stack dump: 01567540 6026ce50 00000000 60259628 00b7910c 00000000 60259628 00b7910c 00000000 0002d7e2 01567540 00000000 00b79114 0063f888 60217d65 00b7910c if you need more info or need me to give a more detail email me
Severity: normal → critical
Assignee: leger → beppe
Component: Browser-General → Editor
QA Contact: leger → beppe
Assigning to beppe who may have an idea.
Assignee: beppe → sfraser
QA Contact: beppe → sujay
Summary: selection in edit menu causes crash in today's nightly (11/13) → [CRASH]selecting edit menu while page is loading causes crash
I was able to reproduce the crash using build 1999111808. 1. launchhed seamonkey 2. selected http://mozilla.org 3. selected a link via right-mouse button and selected Edit Page 4. selected the Edit menu as the page was loading RESULT: app crashed. see talkback incident 1039918: Call Stack: (Signature = nsFileSpecHelpers::Canonify 46cf84c9) nsFileSpecHelpers::Canonify [d:\builds\seamonkey\mozilla\xpcom\io\nsFileSpecWin.cpp, line 77] nsFilePath::nsFilePath [d:\builds\seamonkey\mozilla\xpcom\io\nsFileSpec.cpp, line 661] nsFileURL::nsFileURL [d:\builds\seamonkey\mozilla\xpcom\io\nsFileSpec.cpp, line 488] nsEditorShell::PrepareDocumentForEditing [d:\builds\seamonkey\mozilla\editor\base\nsEditorShell.cpp, line 402] nsEditorShell::OnEndDocumentLoad [d:\builds\seamonkey\mozilla\editor\base\nsEditorShell.cpp, line 3727] nsWebShell::OnEndDocumentLoad [d:\builds\seamonkey\mozilla\webshell\src\nsWebShell.cpp, line 3586] nsDocLoaderImpl::FireOnEndDocumentLoad [d:\builds\seamonkey\mozilla\webshell\src\nsDocLoader.cpp, line 970] nsDocLoaderImpl::OnStopRequest [d:\builds\seamonkey\mozilla\webshell\src\nsDocLoader.cpp, line 847] nsLoadGroup::RemoveChannel [d:\builds\seamonkey\mozilla\netwerk\base\src\nsLoadGroup.cpp, line 606] nsHTTPChannel::ResponseCompleted [d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPChannel.cpp, line 820] nsHTTPResponseListener::OnStopRequest [d:\builds\seamonkey\mozilla\netwerk\protocol\http\src\nsHTTPResponseListener.cp p, line 243] nsOnStopRequestEvent::HandleEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsAsyncStreamListener.cpp, line 326] nsStreamListenerEvent::HandlePLEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsAsyncStreamListener.cpp, line 174] PL_HandleEvent [plevent.c, line 538] PL_ProcessPendingEvents [plevent.c, line 499] _md_EventReceiverProc [plevent.c, line 976] KERNEL32.DLL + 0x3663 (0xbff73663)
Target Milestone: M12
Status: NEW → ASSIGNED
This bug confuses me. In the original report, there is no mention of editor. Oh well, I'll take a look.
Assignee: sfraser → trudelle
Status: ASSIGNED → NEW
I am not able to reproduce on Mac. Reassigning to the toolkit team, since this is almost certainly a toolkit issue. It needs a Windows owner.
Component: Editor → XPApps
it sounds like the editor's involvement is irrelevant. the original report talks about clicking on the "edit" menu while a page is loading. sounds like it doesn't matter if the app loading the page is the browser or the editor. Changing component to XPApps. Maybe it's really XP Toolkit?
Mass-moving non-PDT+ bugs to M13
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Can't reproduce crash using any of these scenarios, using today's opt comm bits on Win98. Resolving as wfm. If anyone can come up with one, don't add it to this report, open a new one.
Status: RESOLVED → VERIFIED
QA Contact: sujay → claudius
verified in 12/7 build. how did I get assigned as the qa_contact for this bug??
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.