Closed Bug 82759 Opened 23 years ago Closed 23 years ago

Find in Page crashes instantly

Categories

(SeaMonkey :: UI Design, defect)

All
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: waterson, Assigned: sfraser_bugs)

Details

(Keywords: crash, regression, Whiteboard: 0.9.1)

Attachments

(2 files)

I'm crashing whenever I try to ``Find In Page''. To reproduce: 1. Open a web page (i've been opening my bug list) 2. Press Ctrl+F to bring up the ``Find'' dialog 3. Type some text and press ``Find'' Crash! The crash is in nsWebBrowserFind::FindNext(), at line 124. The problem is that docShellEnumerator.get() == 0. I'll attach the full stack trace.
Attached file stack trace at crash (deleted) —
-> smfr
Assignee: law → sfraser
Component: Browser-General → XP Apps: GUI Features
Keywords: regression
QA Contact: doronr → sairuh
Whiteboard: 0.9.1
Hrm. Who's been messing in docShell?
Status: NEW → ASSIGNED
Hardware: PC → All
seems like this works for me on win98 for todays build. searched from menu and from [ctrl]f on webpages and messages. I wonder if there is some funky search string that upsets this?
I can't repro the crash. I am able to get a JS error when trying to find in a frameset. Waterson, test URL please?
I'm not seeing a crash either in my Win32 build that's in sync with today's trunk. I just tested find on viewer demo #9 (Frames test) and it worked fine.
using the most recent opt build 2001052504 -- can't repro this one either, Chris if you can get it to crash again using the current builds, please reopen
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
wfm, linux opt trees from both 1am and 3:30pm today.
looks good to me with 052504 mozilla bits on win2K
I am not conviced that this bug is resolved. I have crashed three times with build 2001062204 on Windows 98. Each time it was right when I pressed the find button. It doesn't happen every time, but three times in five days is quite a few. Each time I submitted my browser state through talkback. Is there some way for somebody to take a look at that?
FYI, I know that find was broken for several days last week due to bug 87346. It was fixed *after* the 2001062204 build you last used, but I don't think anyone saw a crash, just errors in the console.
1010mozilla@Ostermiller.com could you please indicate the talkback incident id's?
I found what look to be incident numbers in a file called Mozilla\bin\components\Netscape\MozillaTrunk\info.db using find in page. TB32229827M Searching using the find in page feature. TB32227931W using "find on page". TB32137990G I used a hex editor to pull these from that file, so I'm not sure I got the correct numbers with the correct incidents so I will attach the db.
Attached file Talkback incident database (deleted) —
They each look the same. Incident ID 32229827 Stack Signature TXTSVC.DLL + 0x1573 (0x022e1573) 052de036 Bug ID Trigger Time 2001-06-27 04:33:53 User Comments using find in page. Build ID 2001062211 Product ID MozillaTrunk Platform ID Win32 Stack Trace TXTSVC.DLL + 0x1573 (0x022e1573) TXTSVC.DLL + 0x128d (0x022e128d) nsWebBrowserFind::SearchInFrame [d:\builds\seamonkey\mozilla\embedding\components\find\src\nsWebBrowserFind.cpp, line 401] nsWebBrowserFind::FindNext [d:\builds\seamonkey\mozilla\embedding\components\find\src\nsWebBrowserFind.cpp, line 86] XPTC_InvokeByIndex [d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp, line 139] XPCWrappedNative::CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednative.cpp, line 1883] XPC_WN_CallMethod [d:\builds\seamonkey\mozilla\js\src\xpconnect\src\xpcwrappednativejsops.cpp, line 1253] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 809] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2703] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 825] js_InternalInvoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 897] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3322] nsJSContext::CallEventHandler [d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 944] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 140] nsXBLPrototypeHandler::ExecuteHandler [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLPrototypeHandler.cpp, line 431] nsXBLWindowHandler::WalkHandlersInternal [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLWindowHandler.cpp, line 308] nsXBLWindowKeyHandler::WalkHandlers [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLWindowKeyHandler.cpp, line 132] nsXBLWindowKeyHandler::KeyPress [d:\builds\seamonkey\mozilla\content\xbl\src\nsXBLWindowKeyHandler.cpp, line 148] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\content\events\src\nsEventListenerManager.cpp, line 1598] nsXULDocument::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 2001] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3662] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsXULElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\xul\content\src\nsXULElement.cpp, line 3654] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\base\src\nsGenericElement.cpp, line 1696] nsHTMLInputElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\content\html\content\src\nsHTMLInputElement.cpp, line 1083] PresShell::HandleEventInternal [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5568] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 5495] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 377] nsViewManager::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 2051] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 68] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 724] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 741] nsWindow::DispatchKeyEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2390] nsWindow::OnChar [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2515] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3508] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 989] KERNEL32.DLL + 0x363b (0xbff7363b) KERNEL32.DLL + 0x24407 (0xbff94407) 0x00688b5e
mass verification of WorksForMe bugs: to find all bugspam pertaining to this, set your search string to "IfItWorksForSlappyTheSquirrelThenItWFM". if you think this particular bug is *still* an open issue, please make sure of the following before reopening: a. that it's still a problem with ***recent trunk builds*** on the all appropriate platform[s] b. provide clear steps to reproduce (unless a good test case is already in the bug report), making sure it pertains to the original problem (avoid morphing as much as possible :)
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
Component: XP Apps: GUI Features → UI Design
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: