Bugzilla

I can easily lock up Firefox by debugging the scripts at https://ageor.dipot.com/2020/03/Covid-19-in-Greece.html . For instance, this is what I *wanted* to do, to investigate why the page throws a SecurityError on a stock nightly build, but not on a local (non-debug) artifact build:
1) visit the site on a stock nightly build and open the debugger
2) full-text search for "dataStudioOfflineCache"
3) open the result
4) pretty print (optional)
5) put a breakpoint on `this.H=(this.D=d.indexedDB)&&`
6) reload the page
7) wait for the first breakpoint to trip
8) see what the value of `d` is (it is probably a restricted window)
9) repeat the same steps on the other build 

However, the moment I start trying to set the breakpoint, Firefox starts freezing. Sometimes it recovers after 10 seconds (on my 2018 macbook), but before I can read the value of `d` it has almost certainly locked up completely, my CPU fans spin up, and I have to crash the app. I managed to get the nightly build, but an artifact build consistently locks up by the time I'm waiting for it to show me the scope variables.

I wonder if it would be feasible for it to not lock the process up entirely while it's doing whatever it's doing, or at least provide some sort of progress feedback so I can judge whether it has locked up entirely? By contrast the Chrome and Safari devtools manage to get me to the results with only a few seconds of delay here and there.

I can easily lock up Firefox by debugging the scripts at https://ageor.dipot.com/2020/03/Covid-19-in-Greece.html . For instance, this is what I *wanted* to do, to investigate why the page throws a SecurityError on a stock nightly build, but not on a local (non-debug) artifact build:
1) visit the site on a stock nightly build and open the debugger
2) full-text search for "dataStudioOfflineCache"
3) open the result
4) pretty print (optional)
5) put a breakpoint on `this.H=(this.D=d.indexedDB)&&`
6) reload the page
7) wait for the first breakpoint to trip
8) see what the value of `d` is (it is probably a restricted window)
9) repeat the same steps on the other build 

However, the moment I start trying to set the breakpoint, Firefox starts freezing. Sometimes it recovers after 10 seconds (on my 2018 macbook), but before I can read the value of `d` it has almost certainly locked up completely, my CPU fans spin up, and I have to crash the app. I managed to get the nightly build, but an artifact build consistently locks up by the time I'm waiting for it to show me the scope variables.

I wonder if it would be feasible for it to not lock the process up entirely while it's doing whatever it's doing, or at least provide some sort of progress feedback so I can judge whether it has locked up entirely? By contrast the Chrome and Safari devtools manage to get me to the results with only a few seconds of delay here and there.

Update: after about 5 minutes the artifact build managed to get the scopes listed