The difference on AWFY between OS X and Windows is huge for octane-RayTrace (31k vs 60k). This should not be the case. It looks like they were on par up until February, but the Windows builds didn't benefit from later changes. Possibly relevant bugs (improvements on OS X that don't show on Windows): Bug 994054 Bug 1005030 At least one of these (changelog: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=b2f9a0080f9c&tochange=0a0ef0583c2a): Bug 989035 Bug 988326 Bug 988053

shu asked me yesterday to CC jandem on this bug. I didn't do it yet, because terrence jumped in and asked me for the bug number. Still no reply from either of them, so CCed all three.

Okay, I think terrence wanted to try "bug 994054" for windows. But I don't think it will fix the issue. The difference is not the platform. The difference is the shell VS browser. Local numbers for shell give me 64000, while the browser only gives 23000 on windows 7. Since bug 994054 also improved the shell, I suspect this is not a fix for the discrepancy between shell/browser on windows 7.

Seems like bug 1031068 has nullified the difference between the official nightly builds and custom builds. Official Nightly/Aurora/Beta has extra debugging code (--enable-js-diagnostics). Those can now get disabled using the environment flag JSGC_DISABLE_POISONING=1.