Issue #2975 has been updated by zrj.
mneumann wrote: > It must be related towards OpenCL. When I reinstall darktable, I can run it > with "darktable --disable-opencl" as often as I want. Do you have lang/clover installed? If so darktable is not gracefully handling opencl invocation. In current DRM driver implementation we do not support /dev/dri/renderD128+ nodes that do not require X11 authentication (mesa developers removed x-cookie verification from clover and to add it back is not so trivial). We could add /dev/dri/control and /dev/dri/render nodes into drm.ko (technically we should anyway) but that would open up a very likely security hole. Given how most of c++ programs deal with OpenCL contexts we would also need swapable drm/ttm buffer memory too and that is another story. If it is lang/beignet on i915, just don't use it. ---------------------------------------- Bug #2975: Strange corruption with graphics/darktable and OpenGL http://bugs.dragonflybsd.org/issues/2975#change-13060 * Author: mneumann * Status: New * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- The first time I run "darktable", everything is fine. When I close it, and start it again, it fails with the following error: ld-elf.so.2: assert failed: /usr/src/libexec/rtld-elf/rtld.c:3045 Signal 0 When I reinstall darktable (pkg remove darktable && pkg ins darktable), and then start it again, it works. But again, the second time, it fails with the same error. This is my configuration: DragonFly babel.localnet 4.7-DEVELOPMENT DragonFly v4.7.0.1064.g9294ae-DEVELOPMENT #14: Wed Dec 28 14:45:50 CET 2016 mneumann@babel.localnet:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64 I am using radeonkms. Is something corrupting my memory? Maybe OpenGL? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
