When running Visualization tests locally or on the CI with xvfb, memory leaks are reported by asan.
Same with wayland.
2 Callstacks are reported:
- 1 when creating the bgfx renderer. Callstack is detailed enough so it's easy to add it to suppress list
- 1 without module infos. I got no luck trying to extract infos (using gdb) and I could not add it to suppress list. Maybe it's possible but I didn't find a way.
Until it's possible to discard xvfb leaks I've commented the corresponding steps in the CI pipelines.
When running Visualization tests locally or on the CI with xvfb, memory leaks are reported by asan.
Same with wayland.
2 Callstacks are reported:
Until it's possible to discard xvfb leaks I've commented the corresponding steps in the CI pipelines.