Bug 53060 - crash in JSC::Heap::markRoots
Summary: crash in JSC::Heap::markRoots
Status: RESOLVED DUPLICATE of bug 53177
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac (Intel) OS X 10.6
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-24 21:26 PST by John Moe
Modified: 2011-01-27 10:40 PST (History)
1 user (show)

See Also:

Attachments
Crash Log (48.40 KB, application/octet-stream)
2011-01-24 21:26 PST, John Moe 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Moe 2011-01-24 21:26:47 PST 
Created attachment 80013 [details]
Crash Log

r76498 nightly


Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000000011cebfec4


JSC::Heap::markRoots() + 465
JSC::Heap::allocate(unsigned long) + 77
JSC::BytecodeGenerator::emitLoad(JSC::RegisterID*, JSC::Identifier const&) + 1023
JSC::AssignResolveNode::emitBytecode(JSC::BytecodeGenerator&, JSC::RegisterID*) + 576
JSC::CommaNode::emitBytecode(JSC::BytecodeGenerator&, JSC::RegisterID*) + 97
JSC::BytecodeGenerator::emitNode(JSC::RegisterID*, JSC::Node*) + 206
JSC::BytecodeGenerator::emitNode(JSC::RegisterID*, JSC::Node*) + 206
JSC::BlockNode::emitBytecode(JSC::BytecodeGenerator&, JSC::RegisterID*) + 67
JSC::TryNode::emitBytecode(JSC::BytecodeGenerator&, JSC::RegisterID*) + 428
JSC::BytecodeGenerator::emitNode(JSC::RegisterID*, JSC::Node*) + 206
JSC::ProgramNode::emitBytecode(JSC::BytecodeGenerator&, JSC::RegisterID*) + 131
JSC::BytecodeGenerator::generate() + 62
JSC::ProgramExecutable::compileInternal(JSC::ExecState*, JSC::ScopeChainNode*) + 1002
JSC::evaluate(JSC::ExecState*, JSC::ScopeChain&, JSC::SourceCode const&, JSC::JSValue) + 427
Comment 1 John Moe 2011-01-24 21:28:42 PST 
And I can't reproduce this.  I was just opening gmail, I think.
Comment 2 Alexey Proskuryakov 2011-01-27 10:40:41 PST 

*** This bug has been marked as a duplicate of bug 53177 ***