state of unstable

[Steven Parkes]

We're still not out of the woods with the unstable branch. While it
passes the johnson tests, it core dumps elsewhere.

My test right now is one of the specs in capybara -envjs:

smparkes@smp ~/capybara-envjs i386$ spec spec/driver/
envjs_driver_spec.rb
.... WARNIING: [Thu Aug 19 2010 09:31:18 GMT-0700 (PST)] {ENVJS}
Exception while processing XHR: redirected more than 5 times, check
for infinite redirects.
WARNIING: [Thu Aug 19 2010 09:31:18 GMT-0700 (PST)] {ENVJS} Exception
while loading window: redirected more than 5 times, check for infinite
redirects.
................

Finished in 2.289428 seconds

20 examples, 0 failures
/Users/smparkes/i386/rvm/ruby-1.8.7-p249/gems/rspec-1.3.0/bin/spec:5:
[BUG] Segmentation fault
ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10.4.0]

Dies in the final GC:

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000a8004b
0x000000010235a131 in gc_root_traversal ()
(gdb) bt
#0 0x000000010235a131 in gc_root_traversal ()
#1 0x000000010233571d in JS_DHashTableEnumerate ()
#2 0x0000000102358a34 in js_TraceRuntime ()
#3 0x0000000102358cad in js_GC ()
#4 0x000000010232a4c1 in js_DestroyContext ()
#5 0x0000000102313454 in deallocate (runtime=0x1004cdfc0)
at ../../../../ext/tracemonkey/runtime.cc:481
#6 0x000000010003b04b in rb_gc_call_finalizer_at_exit () at gc.c:2026
#7 0x000000010001f910 in ruby_finalize_1 () at eval.c:1573
#8 0x000000010002ee32 in ruby_cleanup (ex=0) at eval.c:1610
#9 0x000000010002ef59 in ruby_stop (ex=<value temporarily
unavailable, due to optimizations>) at eval.c:1665
#10 0x0000000100035124 in ruby_run () at eval.c:1686
#11 0x0000000100000ee4 in main (argc=<value temporarily unavailable,
due to optimizations>, argv=<value temporarily unavailable, due to
optimizations>, envp=<value temporarily unavailable, due to
optimizations>) at main.c:48
(gdb)

This happens on p249, p299, and p302.

It's okay under c228c6263df35047fa323bbe4240f81b507a9fda.