Closed Bug 720433 Opened 12 years ago Closed 12 years ago

Crash in avmplus::Toplevel::lookupInternedObject when running debug builds

Categories

(Tamarin Graveyard :: Virtual Machine, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: brbaker, Unassigned)

References

Details

Running a debug build (32bit or 64bit) produces a crash in lookupInternedObject():

#0  0x0000000100141da7 in avmplus::Toplevel::lookupInternedObject (this=0x1010b30e0, id=2, toAddIfMissing={t = 0x0}) at ../core/Toplevel.cpp:1704
#1  0x0000000100054947 in avmplus::WorkerObjectBase<avmshell::ShellWorkerObject>::setDescriptors (this=0x10120a5a0, desc=2, parentDesc=1) at Isolate-inlines.h:115
#2  0x00000001000553f1 in avmplus::WorkerObjectBase<avmshell::ShellWorkerObject>::initialize (this=0x10120a5a0) at Isolate-inlines.h:100
#3  0x0000000100054f5a in avmshell::ShellWorkerDomainObject::createWorkerFromByteArrayInternal (this=0x1010fd1d0, byteArray=0x0) at ../shell/ShellWorkerDomainGlue.cpp:51
#4  0x0000000100049f66 in avmplus::NativeID::flash_system_WorkerDomain_private_createWorkerFromByteArrayInternal_thunk (env=0x101273930, argc=1, argv=0x7fff5fbfe268) at shell_toplevel.cpp:563
#5  0x00000001000f159b in avmplus::BaseExecMgr::debugEnterExitWrapper32 (env=0x101273930, argc=1, argv=0x7fff5fbfe268) at ../core/exec.cpp:427
#6  0x00000001000f1d61 in avmplus::BaseExecMgr::verifyEnterGPR (env=0x101273930, argc=1, ap=0x7fff5fbfe268) at ../core/exec.cpp:277

This was reproduced running worker testcase as3/Workers/PromiseWhen.abc, but I believe any worker testcase will produce the crash.
hg bisect points to:

Changeset 7505:424104856c99: good
The first bad revision is:
changeset:   7506:a6f8dd8fb00a
branch:      integration
user:        kpalacz@adobe.com
date:        Fri Jan 20 09:22:49 2012 -0800
summary:     merge
Forgot to regenerate tracers, should be fixed as of 7516:ae862c1c8f20
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Verified in 7517:515b4806f3f1
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.