Sam Deane
I've been tracing through a similar crash recently, and I think I've satisfied myself that there is a bug in Mocha around this. When setting up the arguments for a...
Interesting. So in the example, I was incorrectly using the MOPointer object? My reading of it was that it was supposed to be able to allocate its own storage for...
I did wonder about that after I made the issue - hadn't actually checked to code to see how much of the debug output happened outside the context of a...
I'd be interested in that rev, just in case it suggests anything. One of my theories is that it's a problem relating to MOBox, which Mocha uses to associate a...
With my hacked together Mocha 2.0 based version, I've managed to get this monster script to crash: for (var n = 0; n < 10000; n++) { var test =...
Whereas this doesn't, even with 10 x the iterations: for (var n = 0; n < 100000; n++) { var test = [NSString stringWithString:@"1"]; print(n + ": " + test);...
My suspicion is that it's some sort of memory overwrite coming from Mocha, in which case the WebKit revision might be a coincidence. If the memory access pattern changes slightly,...
It's a nice pragmatic workaround...
It looks like we might have an alternative fix here: https://github.com/logancollins/Mocha/pull/23. The Mocha code in the main branch of Cocoascript is a copied-in version of Mocha 1.0 (with a few...
Yay for address sanitizer - seems like just what we need here.