You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the karma test runner, the blake2f() function hangs in Firefox. The tests for F() below it work fine.
It is not immediately obvious to me what could be going wrong, especially because the precompile doesn't seem to rely on any special external crypto module or anything other than BN.
The text was updated successfully, but these errors were encountered:
There are some pretty heavy Blake2f tests on our suite. I would first check if the same tests take long in Chrome, so we might want to adjust timeouts. It's not uncommon to see SpiderMonkey and Webkit performing differently under the same workload.
The other hypothesis, is that whenever a script takes too much resources from FF, the browser prompts the user if they want to stop or continue. I suspect the script execution is halted when the prompt appears. So we should either:
Find ways to "smoothen out" the way for FF to consume the script
Have a way to click on Continue in that prompt
Remove such tests from FF test suite (that would be unfortunate)
In the karma test runner, the
blake2f()
function hangs in Firefox. The tests forF()
below it work fine.It is not immediately obvious to me what could be going wrong, especially because the precompile doesn't seem to rely on any special external crypto module or anything other than
BN
.The text was updated successfully, but these errors were encountered: