搜索 | 用户支持

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

详细了解

Debugger statement stops firefox to a crawl after reloading webapp

  • 1 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 Svetlana

more options

I'm testing several webapps on Firefox 58 and the problem is that when I insert the debugger statement on my javascript code(react 16+) and the app hot reloads itself, the first time the debugger tab of the developer tools shows all the info I need and the current state of my app.

But, If I modify something else and reload my app or just refresh the current page, with the debugger statement still on the code, the browser slows down until the UI of the entire browser is unresponsive to my mouse clicks and the debugger tab shows nothing at all.

The only way to be able to exit this state is to close the developer tools, where the browser exits its frozen status and all the tabs and the UI start to function again.

This was happening in firefox 57, also I've tested the same code on Chrome and none of the freezing occurs.

I'm testing several webapps on Firefox 58 and the problem is that when I insert the debugger statement on my javascript code(react 16+) and the app hot reloads itself, the first time the debugger tab of the developer tools shows all the info I need and the current state of my app. But, If I modify something else and reload my app or just refresh the current page, with the debugger statement still on the code, the browser slows down until the UI of the entire browser is unresponsive to my mouse clicks and the debugger tab shows nothing at all. The only way to be able to exit this state is to close the developer tools, where the browser exits its frozen status and all the tabs and the UI start to function again. This was happening in firefox 57, also I've tested the same code on Chrome and none of the freezing occurs.

由erzei于修改

所有回复 (1)

more options

1. Do you have a small hello world app that reproduces this problem? Please provide a copy. This may help me reproduce the issue.

2. Please test for this issue in Firefox's Safe Mode. It opens a Firefox session without your customization temporarily, which may help to identify the problem.