New
#130
Hey Mike. I wasn't being sarcastic:). I genuinely don't know anything at all about YaegerMonkey code or the significance of the true or false commands.
Hey Mike. I wasn't being sarcastic:). I genuinely don't know anything at all about YaegerMonkey code or the significance of the true or false commands.
Blongs fix worked and Minefield has been stable. There was another update and it's still mostly fine.
I just noticed a reluctance to close or minimize and had to close from the task bar. Oh dear......
That's OK. I decided to go with the new builds and set both mothodjit (YaegerMonkey) entries to "false" per Blongs' recommendation.
At least it keeps TraceMomkey code set to "true."
I just couldn't handle not being updated regardless of the settings. :)
I'm keeping an eye on the bug though:
https://bugzilla.mozilla.org/show_bug.cgi?id=601355
Any sign that ANY of the MineField releases since 10/1/10 do not need BLongs' "config" settings put to "false" to avoid crashing?
Regards,
- - Phil
Can someone explain to me what is the perceived danger in leaving the config settings set as false permanently?
There is no "danger" but once JaegerMonkey is implemented bug-free, performance enhancements will finally be realized even more for the Javascript engine.
The "false" setting disables JaegerMonkey.
The TraceMonkey build works with JaegerMonkey enabled. Just don't update through the program - go to the TraceMonkey build link I referenced to check for the latest version.
Additionally, a poster on the Mozillazine site has compiled a new x64 installer with the fix for the JIT bug incorporated. It is a newer build than the JS Preview build as it incorporates the new spinning progress wheel on the tab.
Last edited by mikedl; 13 Oct 2010 at 21:00.
Thanks Mike. That's a lot clearer to me now. Presumably a build is coming that will not have this problem. J:)