I won't be able to solve this mystery today. The regression is a Windows thing, so reproducing it locally using Mac or Linux is futile. I can't reproduce the problem on my Windows 7 VM using the Dromaeo Web harness. My XP VM isn't really suitable for running performance tests because it does its disk IO over Ethernet. I intend to continue investigation on Windows tomorrow.
I attached (https://bug591981.bugzilla.mozilla.org/attachment.cgi?id=476778) the only Gecko-side tweak that I could think of to the bug. However, that tweak didn't fix the Windows Dromaeo numbers on try. I verified on try that reverting nsScriptLoader.cpp and .h make a Dromaeo regression go away.
Should http://hg.mozilla.org/mozilla-central/rev/0ab712643a66 be backed out regressing site compat, HTML5-compliance and cross-browser compat? Or should it be left in keeping an ununderstood Dromaeo regression in the tree?
--
Henri Sivonen
hsiv...@iki.fi
http://hsivonen.iki.fi/
We'll have to figure out how to proceed from there once we know why
things regressed or otherwise have a patch that doesn't regress.
/ Jonas