Using build 2001051404 on W2KSP1, I get a stack overflow exception in GKCONTENT.DLL when trying to go to URL (www.kde.org) This has started relatively recently and is happening with 100% reproducibility. Talkbacks: TB30453211H and TB30453226E

from talkback: gkcontent.dll + 0xb6ad3 (0x020f6ad3) jsdom.dll + 0x107b8 (0x605507b8) jsdom.dll + 0x492a (0x6054492a) gkcontent.dll + 0x83e38 (0x020c3e38) gkcontent.dll + 0xe0052 (0x02120052) gkcontent.dll + 0xe0034 (0x02120034) gkcontent.dll + 0xe0034 (0x02120034) gkcontent.dll + 0xe0034 (0x02120034) gkcontent.dll + 0xe0034 (0x02120034) gkcontent.dll + 0xe1b23 (0x02121b23) jsdom.dll + 0x492a (0x6054492a) gkcontent.dll + 0x10203 (0x02050203) gkcontent.dll + 0x2887e (0x0206887e) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0xd20ee (0x021120ee) gkcontent.dll + 0x28860 (0x02068860) gkcontent.dll + 0xcadd4 (0x0210add4) gklayout.dll + 0x1fd50 (0x6032fd50) gklayout.dll + 0x1fc5a (0x6032fc5a) gklayout.dll + 0xa1da1 (0x603b1da1) gklayout.dll + 0xa1cde (0x603b1cde) gklayout.dll + 0xa54b1 (0x603b54b1) gklayout.dll + 0xa1ed3 (0x603b1ed3) gklayout.dll + 0xa4169 (0x603b4169) gklayout.dll + 0xa1232 (0x603b1232) gklayout.dll + 0xa4271 (0x603b4271) gklayout.dll + 0xa9a0d (0x603b9a0d) gkcontent.dll + 0xd1fe7 (0x02111fe7) xpcom.dll + 0x2c5c1 (0x60e7c5c1) xpc3250.dll + 0xfd7a (0x60b7fd7a) xpc3250.dll + 0x12e28 (0x60b82e28) js3250.dll + 0x181f0 (0x60c881f0) js3250.dll + 0x1cf68 (0x60c8cf68) js3250.dll + 0x1822e (0x60c8822e) js3250.dll + 0x184b5 (0x60c884b5) js3250.dll + 0x475a (0x60c7475a) jsdom.dll + 0x3184 (0x60543184) jsdom.dll + 0x15b14 (0x60555b14) gkcontent.dll + 0xb6aaa (0x020f6aaa) gkcontent.dll + 0xb7675 (0x020f7675) gkcontent.dll + 0x28926 (0x02068926) gkcontent.dll + 0xcadd4 (0x0210add4) gklayout.dll + 0x1fd50 (0x6032fd50) gklayout.dll + 0x1fc5a (0x6032fc5a) gklayout.dll + 0xa1da1 (0x603b1da1) gklayout.dll + 0xa1cde (0x603b1cde) gklayout.dll + 0xa54b1 (0x603b54b1)

Works fine. BID: 2001050515 (0.9) on W98.

I am still seeing this crash on build 2001051604. Talkback: TB30547230E

from latest talkback: ntdll.dll + 0x14399 (0x77f94399) ntdll.dll + 0x49816 (0x77fc9816) MSVCRT.DLL + 0x1089 (0x78001089) MSVCRT.DLL + 0x1026 (0x78001026) xpcom.dll + 0x7042 (0x60e67042) xpc3250.dll + 0x1021a (0x60b9021a) xpc3250.dll + 0xfedb (0x60b8fedb) xpc3250.dll + 0x12f3b (0x60b92f3b) js3250.dll + 0x18290 (0x60c98290) js3250.dll + 0x18555 (0x60c98555) js3250.dll + 0x243c6 (0x60ca43c6) js3250.dll + 0x1c435 (0x60c9c435) js3250.dll + 0x182ce (0x60c982ce) js3250.dll + 0x18555 (0x60c98555) js3250.dll + 0x243c6 (0x60ca43c6) js3250.dll + 0x1c435 (0x60c9c435) js3250.dll + 0x182ce (0x60c982ce) xpc3250.dll + 0xdb6e (0x60b8db6e) xpc3250.dll + 0xcb99 (0x60b8cb99) xpcom.dll + 0x2becc (0x60e8becc) urildr.dll + 0x5533 (0x60af5533) urildr.dll + 0x5610 (0x60af5610) urildr.dll + 0x4afd (0x60af4afd) urildr.dll + 0x4940 (0x60af4940) necko.dll + 0x1c67a (0x6078c67a) necko.dll + 0x1c3e7 (0x6078c3e7) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402)

This may be network related. I've watched it crash about 6 times now and i've noticed the status bur never changes from "resolving host www.kde.org" It takes about 45 seconds tring to resolve and then I get my stack overflow error message.

I had almost the exact same kind of stack overflow crash trying to log in to http://mail.excite.com with any username and password. Could this be related to bug 81341 ? Talkback of excite crash: TB30552165E

Just had another stack overlfow, this time trying to go to bugzilla. TB30570363Z

Crashes on Top100 site. http://www.greatsports.com Talkback: TB30580387W

from talkback: Call Stack: (Signature = jsdom.dll + 0x1f76 (0x60541f76) 03864181) jsdom.dll + 0x1f76 (0x60541f76) js3250.dll + 0x18b1b (0x60c98b1b) js3250.dll + 0x182c1 (0x60c982c1) xpc3250.dll + 0xdb6e (0x60b8db6e) xpc3250.dll + 0xcb99 (0x60b8cb99) xpcom.dll + 0x2beaf (0x60e8beaf) urildr.dll + 0x5527 (0x60af5527) urildr.dll + 0x5610 (0x60af5610) urildr.dll + 0x4afd (0x60af4afd) urildr.dll + 0x4940 (0x60af4940) necko.dll + 0x1c67a (0x6078c67a) necko.dll + 0x1c3e7 (0x6078c3e7) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402) urildr.dll + 0x49e3 (0x60af49e3) necko.dll + 0x1c402 (0x6078c402)

maybe bug 81273?

Same crash happens on Win2K SP1 with http://homebrew.universal.net.au/~thekon/metaverse/ after going to: http://homebrew.universal.net.au/~thekon/bugzilla/ (or any other site on the same server). This is with Mozilla Build ID: 2001051704. with a similar stack trace as your 2001-05-16 19:45 comment: NTDLL! 77f8234e() NTDLL! 77fca100() MSVCRT! 78001089() MSVCRT! 78001026() XPCOM! 60e7710b() XPC3250! 60ba01e8() XPC3250! 60b9fea9() XPC3250! 60ba2f09() JS3250! 60ca81e7() JS3250! 60ca84ac() JS3250! 60cb4581() ...

I think Asa is correct. This was probably a dup of bug 81273. On build 2001051804 all the crash pages no longer crash. I'm sure that's because the fix on 81273 has been checked in. *** This bug has been marked as a duplicate of 81273 ***

VERIFIED: thanks for the update, Stephen.

really verifying