為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

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

了解更多

Opening devtools make tab unresponsive

  • 1 回覆
  • 0 有這個問題
  • 3 次檢視
  • 最近回覆由 zeroknight

more options

I am developing a website (using AstroJS, but i don't think that's the problem) and since yesterday I am experiencing issues when opening devtools. Once I open devtools the whole FF tab becomes unresponsive, I cannot even refresh the page until they are done loading. I can change devtool tabs from 'inspector' to 'console' to 'network' etc but especially 'network' and 'debug' tabs are blank.

I run a 'performance' capture and got these results. In the test I have only opened the devtools and switched to the inspector tab which is unresponsive. The CPU usage is at around 90% however, I don't really know how to read the finding and understand what the problem is.

So anyone that can help me understand what is going on here?

I am developing a website (using AstroJS, but i don't think that's the problem) and since yesterday I am experiencing issues when opening devtools. Once I open devtools the whole FF tab becomes unresponsive, I cannot even refresh the page until they are done loading. I can change devtool tabs from 'inspector' to 'console' to 'network' etc but especially 'network' and 'debug' tabs are blank. I run a 'performance' capture and got [https://profiler.firefox.com/public/rsz6dx1v45m8d4yxyymd9vsx4acw0v1xq2p5g80/calltree/?globalTrackOrder=bc0wa&hiddenGlobalTracks=1w8&hiddenLocalTracksByPid=17464-0w2~15252-0~4872-0~8732-0~12200-013&implementation=js&thread=e&v=10 these] results. In the test I have only opened the devtools and switched to the inspector tab which is unresponsive. The CPU usage is at around 90% however, I don't really know how to read the finding and understand what the problem is. So anyone that can help me understand what is going on here?

由 cor-el 於 修改

所有回覆 (1)

more options

Try clearing any breakpoints or debugger statements. Click the "Deactivate breakpoints" button in the top-right corner, next to the gear icon.