The problem appears to be caused by another Add-on; FEBE. This is the message I get when FEBE is enabled. A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: XStringBundle:20
While it appears FEBE causes the hang and script error, LastPass is still unusable even with FEBE disabled.
Gary, you don't need to ask -- the method JIT is new and bugs will be fixed. Any failure to follow JS standards (de-facto or de-jure) that the engine follows w/o the method JIT are bugs. Chrome being bit first does not mean these bugs won't bite content. So in general, they're serious bugs and they'll get fixed, without add-on authors having to change their code to work around. Of course real software ships with bugs unfixed, whether discovered and diagnosed or not, so they may be some bugs to work around, but that would be something to avoid, and release-noted if known when shipped, else determined after the fact by add-on devs. So while bugs happen in shipped products, this bug and others are all in beta software that we're trying to get ship-shape. The trick here, as in the D-Link router HTML/JS bug, is to help get reliable STR, and then reduced testcases. That is a good way to ensure a fix soon, before Firefox 4 is close to shipping. /be
Gary, can you try again now? I just installed LastPass and FEBE, and LastPass seems to work fine. This was in a Tracemonkey nightly from Friday or so.
(In reply to comment #7) > Working Ok. Thanks!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.