搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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/