453668 - TM: Regressions with JIT enabled for Chrome

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect)

Description

[Andreas Gal :gal]

Please track regressions when JIT enabled for Chrome here. This is currently not recommended and has lower priority than polishing the JIT for content.

Comment 1

[Damon Sicore (:damons)]

Not a blocker as this is just an investigation.

Comment 2

[scratch]

I'm seeing major memory leakage when I enable JIT for chrome.  Is this known or should I file a bug on it?

Comment 3

[Bob Clary [:bc] (inactive)]

scratch, file a bug if you can not find an already filed one that matches the leaks you have found.

Comment 4

[Nochum Sossonko [:Natch]]

Will chrome jit ever be enabled for chrome by default? Post-3.5? Are there real significant perf gains? Just curious.

Comment 5

[Andreas Gal :gal]

Fennec reported visible improvements (i.e. during scrolling). Their UI is more JS-heavy than FF as far as I can tell.

Comment 6

[Brian Carpenter [:geeknik]]

To be honest, in the nightly Shiretoko builds, I can't tell a difference with jit.chrome on or off. So I just leave it on until something crashes it.

Comment 7

[Andreas Gal :gal]

I don't know much about the FF JS code base but since JS used to be pretty slow I am sure we go to great length avoiding computationally intensive code in the UI. I don't think having the JIT turned on for chrome is a huge priority, but it will definitively shift the cost around and allow to do more things in JS than before for future code.

Comment 8

[Ryan VanderMeulen [:RyanVM]]

Obsolete with the removal of tracejit.