The js primitive caml_wrap_exception (from stdlib.js) has special branches to turn a JS stack overflow exception into the OCaml counterpart. The OCaml exception is created with:
return [0,caml_global_data[9]];
I did not try to produce a failing example, but this seems to be incompatible with the new representation of constant exceptions, which are represented directly as their exception constructor slot and not wrapped in an extra block.