Window Maker now crashes right after launching. This PR addresses some of the most immediate causes:
Writing our own wmalloc/wfree/wrealloc that actually do something different from the system malloc/free/realloc means that this codebase can no longer do things like pass pointers from wmalloc to free.
Our hashtable rewrite was pulled in from a stale branch without adequate integration testing. It turns out that the WUtils hashtable should not take ownership of keys and values. We can't be rid of WMHashTable fast enough, but correcting this ownership story should suffice for now.
Window Maker now crashes right after launching. This PR addresses some of the most immediate causes:
* Writing our own `wmalloc`/`wfree`/`wrealloc` that actually do something different from the system `malloc`/`free`/`realloc` means that this codebase can no longer do things like pass pointers from `wmalloc` to `free`.
* Our hashtable rewrite was pulled in from a stale branch without adequate integration testing. It turns out that the WUtils hashtable should not take ownership of keys and values. We can't be rid of `WMHashTable` fast enough, but correcting this ownership story should suffice for now.
This fixes a lot of memory bugs which arose as a result of doing something
different from the system malloc/free when allocators were rewritten in Rust.
These changes originate from a different approach to writing the allocator in
Rust:
https://git.sdf.org/vitrine/wmaker/pulls/1/files#diff-04a0fd2319b9969373b75377716e45c836d22869
There are other function calls (to XFree) that need to be fixed, but that can be
done in another commit. This one is already getting large.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Window Maker now crashes right after launching. This PR addresses some of the most immediate causes:
wmalloc/wfree/wreallocthat actually do something different from the systemmalloc/free/reallocmeans that this codebase can no longer do things like pass pointers fromwmalloctofree.WMHashTablefast enough, but correcting this ownership story should suffice for now.