[mnemonik]

> It might be just me, but it's very common when I use the JavaScript debugger in Firefox that it either freezes the site, the debugger, or Firefox itself.

If you have a test case and steps to reproduce, please file a bug! We can't usually fix the bugs we don't know about.

[ahmelsayed]

It's just very inconsistent. It just happens sometimes and I either restart firefox or close and open the tab and it goes away. I can try to take a memory dump when that happens. I don't know how useful that might be for you. If I ever get something consistent I will make sure to file a bug.

Thanks for all the amazing work though! nothing beats the visual tools and network traces in Firefox.

[chrisan]

Have you tried a fresh install of FF? New profile with no addons and slowly (1 by 1) add your customizations back?

[acdha]

I think you may have fixed it since I haven't had a problem in awhile but I sporadically had problems where the debugger didn't trigger on a break-point after awhile in a long debugging session. Is there a way to report heisenbugs like that which isn't going to waste your time?

[mnemonik]

This is a great question, thanks for asking.

For crashes, definitely submitting the crash report found in about:crashes helps a ton.

Checking the browser console for an error message + stack and pasting that in a bug + description of bad behavior can be useful.

Finally, in extreme cases you can enable all the devtools logging[0] and then run firefox while piping stdout into a log file. This is a firehose of information, but it should hopefully point to the part of the code base that is misbehaving.

[0] https://wiki.mozilla.org/DevTools/Hacking#Enabling_DevTools_...

[fixedd]

Mozilla: we care about the problems you're facing, unless you're one of the 80+% of people who hate Australis... then fuck you.