can you confirm this test build works ? https://builder.blender.org/download/patch/PR111708/
Awesome, we have the root cause now! And a Blender-side fix in sight as there is absolutely 0 valid reason for tuning the FTZ/DAZ bits from this library, I'll work on a PR to make it use a…
great finding! What is happening isn't 100% clear yet, but It could make sense if some libs check/set fp env flags or load an implementation that got compiled with unexpected flag.
Can you…
Thanks for the detailed answer.
Maybe the crash will reproduce again with a slightly less dummy lib?
I tried it and unfortunately the bugs still appear.
You mean…
it turns out that fvisibility=hidden
isn't enough to hide the STL symbols, so the test build didn't do much, but if using LD_PRELOAD aligns the bindings but doesn't fix the issue, you're right…
Sorry I've initially put a link to another build (PR110656 instead of PR111606) and edited it right after posting... not quickly enough for you apparently :) can you try with the PR111606 one ?
Thanks for the confirmation it works reliably with the dummy lib.
Can you check if this build : https://builder.blender.org/download/patch/blender-4.0.0-alpha+main-PR110656.222f3eb0bf9a-linux.x8…
Embree on Archlinux repo hasn't yet GPU support built, so that's expected that the Blender build from arch lacks the checkbox, it's not directly related.
The issue here in this thread is caused…
thanks for the additional logs. I'm not seeing any issue at a first glance. There is an interesting difference though, aren't you getting "GHOST: Wayland: unable to connect to display!" in the…
there are symbols previously coming from libOpenColorIO, now coming from libcycles_kernel_oneapi_aot, hard to say if they're conflicting yet, but it seems worth digging further into that direction…
From your previous test, there is no proof it's a symbols conflict issue, but I struggle finding another explanation at the moment. Still, HD4000 is too old to have level-zero support so blender…
I meant running Blender from a regular build yes, these commands set environment variables in the terminal you're using, you then need to launch blender from the same terminal. Can you confirm…