Again the issue manifests itself only with Firefox 52.9.0 32-bit. This will cause the problematic code to be launched repeatedly by the benchmark framwork. The attached file contains a simple page with which I am able to systematically reproduce the issue whenever I click the 'Benchmark' button. The issue is better described as a javascript bug, which causes in the current case an endless loop. The people there assume a problem with build or similar and the issue located in vacuum, but best: look at the discussion there. after some tries, it came clear, that uBlock-origin triggers the problem.īut further analysis shows, that uBlock is not the real cause, but just triggers the bug in firefox and only in 32bit, not 64bit. History: after firefox-update the user-interaction of firefox is ugly. With 52.9.0: timeout after small-size/regex-based test, a bit later OutOfMem on js-console (even with multiple GB RAM free!)īoth should do the tests without problem. With 52.8.0: no problem (takes a moment) and will do 3x3 tests for small/medium/large-size set/regex/ties-based dictionary Load in each of it and click there 'creation'

Firefox setup 52.9 0esr 32 bit download