搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Javascript causes Firefox to not respond for a few minutes.

more options

I have a website form with a large amount of dynamically generated javascript that uses jQuery to handle events. When clicking on radio buttons in the form Firefox 26 will get part way through then stop responding for around two minutes while showing (Not Responding) in the title. If I go into about:config and disable javascript.options.baselinejit.content the form works fine, if I enable that option FireFox becomes unresponsive part way through the form. This started recently but I don't know exactly which version is started on, Firefox 26 definitely has the issue for me. All extensions and plugins have been disabled and "Use hardware acceleration when available" is not selected. Also the form works correctly in Chrome 31, Internet Explorer 7, 8, 9, and 10.

I have a website form with a large amount of dynamically generated javascript that uses jQuery to handle events. When clicking on radio buttons in the form Firefox 26 will get part way through then stop responding for around two minutes while showing (Not Responding) in the title. If I go into about:config and disable javascript.options.baselinejit.content the form works fine, if I enable that option FireFox becomes unresponsive part way through the form. This started recently but I don't know exactly which version is started on, Firefox 26 definitely has the issue for me. All extensions and plugins have been disabled and "Use hardware acceleration when available" is not selected. Also the form works correctly in Chrome 31, Internet Explorer 7, 8, 9, and 10.

被選擇的解決方法

Hi keviga, would you be inclined to file a new bug for this? You can reference the Baseline JavaScript compiler as the problem. I guess the tricky part is figuring out what is going on in your scripts that is triggering the issue.

You can submit bugs here: https://bugzilla.mozilla.org/

從原來的回覆中察看解決方案 👍 0

所有回覆 (1)

more options

選擇的解決方法

Hi keviga, would you be inclined to file a new bug for this? You can reference the Baseline JavaScript compiler as the problem. I guess the tricky part is figuring out what is going on in your scripts that is triggering the issue.

You can submit bugs here: https://bugzilla.mozilla.org/