You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can take a look at it tomorrow. However, I think it might be best to just drop that allocator in favor of malloc for now until there is a general purpose allocator in base.
Context
I am calling this code from a threadpool with a size of 10, rapidly:
and sometimes i get an error!
I'm trying to pipe the result of a command I'm calling back to my application and continue processing that...
the full proc looks like this:
Edit: to add a bit more context: I have a Tracking_Allocator setup and the thread pool is setup this way:
and the connection pool this way:
note: they all share the same context thus the same allocator.
perhaps this is relevant for tracking down the issue!
odin report
output:Odin: dev-2025-01-nightly
OS: Fedora Linux 41 (Forty One), Linux 6.12.6-200.fc41.x86_64
CPU: 12th Gen Intel(R) Core(TM) i5-12400
RAM: 31821 MiB
Backend: LLVM 18.1.6
Expected Behavior
No assertion failure
Current Behavior
Assertion failure
Failure Information (for bugs)
/opt/odin/core/os/os2/heap_linux.odin(316:2) runtime assertion: alloc.free_idx == NOT_FREE
71888 Illegal instruction
Steps to Reproduce
Failure Logs
See screenshot for stacktrace~:
The text was updated successfully, but these errors were encountered: