When I started my game on HTML5 it is crashing in the very beginning, right after Defold loading bar is full and game should be started.
In Console I see:
exception thrown: RuntimeError: function signature mismatch,RuntimeError: function signature mismatch
at <anonymous>:wasm-function[429]:0x99e2
at <anonymous>:wasm-function[1265]:0x5533d
at <anonymous>:wasm-function[3240]:0x110fb8
at <anonymous>:wasm-function[1263]:0x551f0
at <anonymous>:wasm-function[3223]:0x10febd
at <anonymous>:wasm-function[3256]:0x1123b5
at <anonymous>:wasm-function[1963]:0xab6cf
at <anonymous>:wasm-function[4442]:0x171b73
at <anonymous>:wasm-function[4445]:0x17272f
at <anonymous>:wasm-function[2946]:0xfe553
And also:
INFO:CRASH: Successfully wrote Crashdump to file: /data/.Defold/_crash
But I don’t know where that location could be.
Could you please help me in debugging this? I don’t know where to start. It is happening everytime.
It is happening with project uploaded on itch. I will try to upload empty project today, but I guess it’s something with my project
Was checking on Opera, will check on Chrome
Monarch, Log, Err, Defsave, DefOS, Defold-Input, Playfab, Ludobits, Defold-Metrics, Gooey (customized), Orthographic (customised) and Editor scripts by Jerakin
This (in Debug mode) has given me more console logs and now there’s something to debug!
You can check out on your own here: https://paweljarosz.itch.io/defold-test
I will try to fix those warnings, but those are only warnings, right? Or do you see already what could cause the error to load a go+sprite collection bootstrap?
Ok, removed the fragment from quad_postprocess.fp and looks like it’s solving the case for simple bootstrap! I will get back to the original collection bootstrap (with that correction) and see if it is working.
EDIT: And it is starting now so it was only because of that part of the code in fragment program, thank you @Pkeod and @britzl for your suggestions and helping me debug it
I am sad, those logs weren’t visible in the Debug Mode but with original collection - I will double check it.
I’m afraid I have no real idea why the shader error output didn’t work in one case but not in the special collection. Could it be that the game was still using Release mode? e.g. because of caching of the web page?