WebGl loading process throws exceptions (just plain numbers)

Our webgl loader page has a custom error handler defined where we send the incoming error to our internal communication channels. Once in a while those channels get flooded with a weird exception which is just a number. The exception occurs in Chrome, as well as Firefox as well as Edge. The number ALWAYS starts with a 1 and ALWAYS has eight digits. If we take these numbers, put them in order and count the deltas it ALWAYS is 16 (or 4104).

By the way, FF reports the exception as 'uncaught exception: x', Chrome as 'Uncaught x' and Edge just reports the exception without any words in front.

We have a slight clue that the error occurs during the (down)loading of the content but cannot reproduce internally. Questions to the community:

1. Has anyone encountered such behavior before?
2. What could possibly be the cause?
3. What area could I inspect further?

Any help greatly appreciated.

BTW: using 5.4.2f2...

 

Anyone?

 

I capture errors from my webgl pages as well and have never seen this. I recommend you try and capture the console log as well and put that in your report, so you can at least know at what point during the startup process the error is happening.

Then you can add additional logging around that area to narrow down where the error is coming from, and hopefully figure out why it's happening to make a repro.

 

Thanks. I now log everything via window.onerror but the source, line ,col and error parameters give nothing extra. Next step would then be to refactor the unityloader script... Don't think I want to tangle with that one...