Closed Bug 320157 Opened 19 years ago Closed 19 years ago

With google toolbar when you use the spell checker and apply the spelling change it crashes

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 319293

People

(Reporter: dmcdave, Unassigned)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051207 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20051207 Firefox/1.6a1

I have the very latest update of Deer Park Alpha 2 (Updated 13/12/05)
I have Google Toolbar 1.0.20051122

I went to spell check some infomation that I had in a form and it picked up the mistakes. When trying to apply one of the corrections it came with the following...

Application Error, the instruction at 0x005436f0 refrenced 0x00000000 could not be read.

And the application fails.

Reproducible: Always

Steps to Reproduce:
1.Type in a form area and get the google toolbar to correct a spelling.
2.Then correct the mistake and the error is returned and Firefox (Deer Park) Crashes

Actual Results:  
Firefox (Deer Park) Crashes

Expected Results:  
Google Toolbar should have replased the word with the correct spelling.

I have changed the app.extensions.version to 1.5 so that the google toolbar installs.
Confirmed with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051213 Firefox/1.6a1 ID:2005121305

Don't know if its Firefox's fault or Google Toolbar's but I get a crash when I click "ABC Check". 

TB12924253K  TB12924296H

1.9a1_2005120214 = no crash, 1.9a1_2005120300 = crash.

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=PhoenixTinderbox&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-12-02+13%3A00%3A00&maxdate=2005-12-03+00%3A00%3A00&cvsroot=%2Fcvsroot

Severity: major → critical
Incident ID: 12924253 
Stack Signature ClassifyWrapper 10a698b0 
Product ID FirefoxTrunk 
Build ID 2005121305 
Trigger Time 2005-12-13 14:09:43.0 
Platform Win32 
Operating System Windows NT 5.1 build 2600 
Module firefox.exe + (001433c4) 
URL visited  
User Comments  
Since Last Crash 258 sec 
Total Uptime 258 sec 
Trigger Reason Access violation 
Source File, Line No. c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsDOMClassInfo.cpp, line 5093 
Stack Trace  

ClassifyWrapper  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsDOMClassInfo.cpp, line 5093]
nsDOMClassInfo::BeginGCMark  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsDOMClassInfo.cpp, line 5136]
nsDOMClassInfo::MarkReachablePreservedWrappers  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsDOMClassInfo.cpp, line 5029]
nsEventReceiverSH::Mark  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/dom/src/base/nsDOMClassInfo.cpp, line 6687]
XPC_WN_Helper_Mark  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp, line 1030]
js_Mark  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsobj.c, line 4229]
MarkGCThing  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1146]
js_MarkGCThing  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1446]
js_GC  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1702]
js_ForceGC  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/js/src/jsgc.c, line 1510]
nsAppStartup::Run  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/toolkit/components/startup/src/nsAppStartup.cpp, line 162]
main  [c:/builds/tinderbox/Fx-Trunk/WINNT_5.2_Depend/mozilla/browser/app/nsBrowserApp.cpp, line 61]
kernel32.dll + 0x16d4f (0x7c816d4f)
Keywords: crash
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 319293 ***

*** This bug has been marked as a duplicate of 319293 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.