Closed thheller closed 9 months ago
We got a recent report of this from inside Google with the same stack trace. It should be fixed with https://github.com/google/closure-compiler/commit/23e25dae584075decfd7c7e3ecc876cd8f55d42d (and npm nightly builds should restart soon - https://github.com/google/closure-compiler-npm)
We run into an INTERNAL COMPILER ERROR, When trying to process the bwip-js npm code with the Closure Compiler.
It reproduces with the current
google-closure-compiler
npm release (20230802.0.0), but the full trace when running viashadow-cljs
is a bit more informative due to running with-XX:-OmitStackTraceInFastThrow
. That stacktrace is down below.The steps to reproduce with just
google-closure-compiler
are:It seems to fail in two locations "randomly", which I guess is due to different hash ordering. One is
but on a different run you might get
The NPE they run into is the same from
com.google.javascript.rhino.HamtPMap.equivalent (HamtPMap.java:412)
though.