-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deallocation hangs -- regression moving from 0.9.1
to 0.10.*
#70
Comments
I created an alternative memory allocator which solves this problem and provides many more benefits, such as improved performance and memory utilization. |
Thanks for reporting this! We just published a new |
Thanks for letting me know, i'll check it out! |
Unfortunately I can confirm that the problem still occurs with I plan to dig into it within the next two weeks and will update this issue with my findings. |
Thanks for testing! Let me know if I can help with any debugging. |
We just ran into a strange issue in Theseus OS where the deallocation path hangs. I'm not yet 100% sure what the precise failure condition is, but I wanted to post this issue sooner rather than later in case anyone else has run across this.
So far it only occurs in an OS execution path that causes more heap allocations than what we normally do, so it could be related to heavy heap usage. Also not sure if it's related to the pending issue #66, which alludes to an issue with fragmentation (?).
Relevant details
Theseus uses
linked_list_allocator
as its early heap allocator. Through bisection, I've confirmed that this issue only occurred after upgrading fromlinked_list_allocator
0.9.1
to0.10.3
(theseus-os/Theseus#646), and I confirmed that the problem is present in both0.10.1
and0.10.2
as well. If it's relevant, we're usinglinked_list_allocator
as such:Using Rust nightly 1.64
Backtrace
I have a partial backtrace from GDB but it isn't complete; will work on improving it as I narrow down the exact cause.
I can also add steps to repro this behavior in Theseus but it probably wouldn't be useful until I can more specifically determine the exact failure condition.
The text was updated successfully, but these errors were encountered: