> It's exceedingly unlikely that swapping the slice allocator with the system one will cause a
> crash in correct code; it's much more likely that the slice allocator was masking an incorrect
> deallocation or an invalid write. Valgrind would also have caught it, since we automatically
> disabled the slice allocator when using it.
which means it's probably an issue to fix in the openbox codebase
Upstream glib reply
> It's exceedingly unlikely that swapping the slice allocator with the system one will cause a
> crash in correct code; it's much more likely that the slice allocator was masking an incorrect
> deallocation or an invalid write. Valgrind would also have caught it, since we automatically
> disabled the slice allocator when using it.
which means it's probably an issue to fix in the openbox codebase