@keropi
It's a bug. The Warp3D library init overflows the limited ramlib stack (just 2KB). It depends on the order of the library opening: If you manually open one of the sublibraries first it will hide the bug. Basically if the library init calls OpenLibrary any other diskbased libraries it will cause ramlib to recurse, eating away some of the stack area. If some of the the sublibraries are preloaded to memory the OpenLibrary will return immediately (rather than invoking ramlib again) and not cause further ramlib recursion.
Also, the crash might not happen unpatched system, or if you're just lucky and there's no critial data before the ramlib stack.
The same bug plagued multiple libraries from the same authors. The probram and the solution were brought to their attention years ago, nothing happened.
