A lot of strange bugs.

I've been using Emscripten for a while now and have experienced a lot of strange little bugs, some I can explain and some I cannot.

1. qsort() doesn't work
2. some times in opengl models dont render the full index count leaving missing vertices (with both GLFW and SDL backends)
3. pre-enabling VBO1 for some reason; https://github.com/emscripten-core/emscripten/issues/18193
4. some times code just breaks for no apparent reason, maybe it's an internal memory leak, maybe its a compilation bug, who knows, but I know my software doesn't leak memory, one example is I have a random function outputting a range of 1-6 and that defines what 3D model is drawn to screen, but for some reason every now and then I get a ghost model that is not drawn (only with the emscripten compile) which led me to believe the random functions in emscripten was breaking but even after adding a limit check after the random number is generated in emscripten I still get this odd ghost bug.... once the number is set it's just 6 if statements checking to see which one is triggered, I get all 6 models in game + one ghost model O_o.

It's kind of a shame because it's discouraging to continue using Emscripten knowing there will be bugs that I can't really resolve lol.

Has anyone else experienced issues like this? To be fair, I have released 50+ emscripten "things" mostly using OpenGL via SDL/GLFW backends but also some 2D SDL stuff and some stuff that just computes and updates HTML DOM elements etc using no specific libraries and usually things work just fine but some projects have encountered really odd issues. The VBO 1 problem is something that effects every compile but usually people use more than one VBO so it's never really noticed but in the rare case you only want to use one VBO (0) then it breaks your shader/program to have VBO 1 enabled with nothing bound.