Closed Bug 601561 Opened 15 years ago Closed 15 years ago

Crash as soon as you try to surf to any website or Minefield starts up already going to website

Categories

(Firefox :: General, defect)

x86_64
Windows 7
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 601355

People

(Reporter: abresh2, Unassigned)

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b7pre) Gecko/20101003 Firefox/4.0b7pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b7pre) Gecko/20101003 Firefox/4.0b7pre I am having a problem where Minefield X64 crashes as soon as you try to go to any website. Before the latest update on October 3rd, I did not have this issue. The issue is NOT present in Safe Mode, but even when I use all the Safe Mode settings to set things back to a 'fresh' install of Minefield, the issue is still present. Reproducible: Always Steps to Reproduce: 1.Open Minefield 2.Surf to any website 3.Watch as Minefield X64 crashes out with no crash reporter dialog. Actual Results: Minefield crashes out and does not bring up the Crash Reporter dialog. Expected Results: Gone to the website in question.
Version: unspecified → Trunk
Exactly the same problem here. Build identifier: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:2.0b7ore) Gecko/20101004 Firefox/4.0b7pre The only websites I can open are about:blank and about:home Can't even open about:addons without crashing. No problems at all using safe-mode. Issue present with all addons disabled, even with a clean install.
This is all I could get with VS 2010: Problem signature: Problem Event Name: APPCRASH Application Name: firefox.exe Application Version: 2.0.0.3929 Application Timestamp: 4ca9b3b7 Fault Module Name: mozjs.dll Fault Module Version: 0.0.0.0 Fault Module Timestamp: 4ca9a85f Exception Code: c0000005 Exception Offset: 00000000001ab60e OS Version: 6.1.7600.2.0.0.256.48 Locale ID: 1033 Additional Information 1: ae61 Additional Information 2: ae61702521dd6121f7be0fc073032d6c Additional Information 3: 3aa5 Additional Information 4: 3aa529f651f839c91e1402897a62c672 > mozjs.dll!000007feead5b60e() [Frames below may be incorrect and/or missing, no symbols loaded for mozjs.dll] 0000000004ef0000()
-safe-mode works, so the problem might not be with addons or plugins (tested with all of them disabled)
the problem has been reported on 4.10, but first faulty build appears to be 02.10. exactly as christopherkidwell1@comcast.net said. can be useful to review the changes made then. If not everyone has this issue, then it is driver related. graphics card: geforce gt 330m
I haven't tested 02.10, but 03.10 was also broken here. Graphics card: ATI HD3200 (mobile graphics) Software information: Driver Packaging Version 8.762-100803a-103697C-ATI Catalyst™ Version 10.8 Provider ATI Technologies Inc. 2D Driver Version 8.01.01.1059 2D Driver File Path /REGISTRY/MACHINE/SYSTEM/ControlSet001/Control/CLASS/{4D36E968-E325-11CE-BFC1-08002BE10318}/0000 Direct3D Version 8.14.10.0775 OpenGL Version 6.14.10.10151 Catalyst™ Control Center Version 2010.0803.2125.36577 Hardware information: Primary Adapter Graphics Card Manufacturer Powered by ATI Graphics Chipset ATI Radeon HD 3200 Graphics Device ID 9612 Vendor 1002 Subsystem ID 3045 Subsystem Vendor ID 103C Graphics Bus Capability PCI Maximum Bus Setting PCI BIOS Version 010.094.001.030 BIOS Part Number BK-ATI VER010.094.001.030.035140 BIOS Date 2009/11/03 Memory Size 320 MB Memory Type HyperMemory Core Clock in MHz 500 MHz Memory Clock in MHz 400 MHz My OS info: OS Name Microsoft Windows 7 Professional Version 6.1.7600 Build 7600 System Manufacturer Hewlett-Packard System Model HP TouchSmart tx2 Notebook PC System Type x64-based PC Processor AMD Turion(tm) X2 Ultra Dual-Core Mobile ZM-82, 2200 Mhz, 2 Core(s), 2 Logical Processor(s) BIOS Version/Date Hewlett-Packard F.25, 11/6/2009 SMBIOS Version 2.4
Please provide Stacktraces: https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg (Probably you have to use the 64-Bit Version of WinDBG). mozjs.dll points to a Crash in the JS Module.
Keywords: crash, stackwanted
This is probably what you need. I had to build it myself with debugging flags, so I don't know if I did it correctly. I've had problems using WinDBG, but here's what I got with VS 2010. mozjs.dll!InjectJaegerReturn() + 0x1a bytes Asm 000000000028c840() 0000000004e3a448() 0000000004d90000() 000000000028cc60() 000491d4bf80809b() 0000000004d90688() 0000000015f80e8b() 0000000004d90620() 0000000010962d40() 0000000004e3a448() 0000000004d90530() 0000000004d90470() 000000000028cb00() 000000000028ca70() fffa80000fe3b540() 00007fffffffffff() ffff800000000000() 0000000004d90510() 000000000028ccf0() > mozjs.dll!EnterMethodJIT(JSContext * cx=0x0000000010962d40, JSStackFrame * fp=0x0000000004d90530, void * code=0x0000000009440000) Line 752 + 0x22 bytes C++ mozjs.dll!js::mjit::JaegerShot(JSContext * cx=0x0000000010962d40) Line 781 C++ mozjs.dll!js::RunScript(JSContext * cx=0x0000000010962d40, JSScript * script=0x00000000122c4850, JSFunction * fun=0x000000000dabbed8, JSObject & scopeChain={...}) Line 635 + 0xa bytes C++ mozjs.dll!js::Invoke(JSContext * cx=0x0000000010962d40, const js::CallArgs & argsRef={...}, unsigned long flags=0) Line 746 + 0x27 bytes C++ mozjs.dll!js_fun_call(JSContext * cx=0x0000000010962d40, unsigned int argc=2, js::Value * vp=0x0000000004d904e8) Line 2288 + 0x15 bytes C++ 000000000780274c() 0000000010962d40() 0000000000000002() 0000000004d904e8() 0000000006df17ed() 000000000028cc60() 0000000004e3a290() 0000000004d90000() 000000000028d8c0() 000491d4bf8066ea() 0000000004d90510() 0000000012295216() 0000000004d90470() 0000000010962d40() 0000000004e3a290() 0000000004d90378() 0000000004d902c8() 000000000028cf20() 000000000028ce90() fff8800000000001() 00007fffffffffff() ffff800000000000() 000000000da0f4c0() 000000000028d950() mozjs.dll!EnterMethodJIT(JSContext * cx=0x0000000010962d40, JSStackFrame * fp=0x0000000004d90378, void * code=0x0000000009282ee0) Line 752 + 0x22 bytes C++ mozjs.dll!js::mjit::JaegerShot(JSContext * cx=0x0000000010962d40) Line 781 C++ mozjs.dll!js::RunScript(JSContext * cx=0x0000000010962d40, JSScript * script=0x0000000015e93e30, JSFunction * fun=0x000000000dabf688, JSObject & scopeChain={...}) Line 635 + 0xa bytes C++ mozjs.dll!js::Invoke(JSContext * cx=0x0000000010962d40, const js::CallArgs & argsRef={...}, unsigned long flags=0) Line 746 + 0x27 bytes C++ mozjs.dll!js_fun_apply(JSContext * cx=0x0000000010962d40, unsigned int argc=2, js::Value * vp=0x0000000004d90340) Line 2415 + 0x15 bytes C++ mozjs.dll!CallCompiler::generateNativeStub() Line 450 + 0x2b bytes C++ mozjs.dll!js::mjit::ic::NativeCall(js::VMFrame & f={...}, unsigned long index=1) Line 680 + 0xa bytes C++ 0000000006df2ae8() 000000000028d8c0() 0000000000000001() 0000000004d90528() 0000000006df17ed() 000000000028d8c0() 0000000004e39f60() 0000000004d90000()
Looks like a duplicate of bug 601355, so I'm marking it as such. Please reopen if you disagree.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.