JIT Check failed on MacOS
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 283
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 135
Description
**Describe the bug**
The JIT dies when I'm running a test. I can reproduce it with a second, different test (in an entirely different DSLX file). It happens on MacOS but not when I run these same tests on Linux. I know that MacOS isn't supported, but am letting you know anyway. I can't share the files that stimulate the failure (unless you can give me a DSLX minimizer?).
I can share the two stack traces
```F0618 19:09:17.327625 5771671 jit_callbacks.cc:106] Check failed: res != nullptr Null alloc with 1024 (adjusted to: 1024) aligned at: 1
*** Check failure stack trace: ***
@ 0x1038d268c absl::lts_20250127::log_internal::LogMessage::SendToLog()
@ 0x1038d2354 absl::lts_20250127::log_internal::LogMessage::Flush()
@ 0x1038d2a1c absl::lts_20250127::log_internal::LogMessageFatal::~LogMessageFatal()
@ 0x1038d2a34 absl::lts_20250127::log_internal::LogMessageFatal::~LogMessageFatal()
@ 0x101e13318 xls::(anonymous namespace)::AllocateBuffer()
@ 0x105af8f98 0x0
@ 0x105af8e78 0x0
@ 0x100a17e08 xls::dslx::RunComparator::RunComparison()
@ 0x100a2795c std::__1::__function::__func<>::operator()()
@ 0x100ba017c xls::dslx::BytecodeInterpreter::Run()
@ 0x100b9f450 xls::dslx::BytecodeInterpreter::Interpret()
@ 0x100a1a474 xls::dslx::DslxInterpreterParsedTestRunner::RunTestFunction()
@ 0x100a1d228 xls::dslx::AbstractTestRunner::ParseAndTest()
@ 0x1009f64d4 main
@ 0x19fa62b98 start
```
```
F0618 19:09:28.411358 5774269 jit_callbacks.cc:106] Check failed: res != nullptr Null alloc with 8192 (adjusted to: 8192) aligned at: 4
*** Check failure stack trace: ***
@ 0x10581268c absl::lts_20250127::log_internal::LogMessage::SendToLog()
@ 0x105812354 absl::lts_20250127::log_internal::LogMessage::Flush()
@ 0x105812a1c absl::lts_20250127::log_internal::LogMessageFatal::~LogMessageFatal()
@ 0x105812a34 absl::lts_20250127::log_internal::LogMessageFatal::~LogMessageFatal()
@ 0x103d53318 xls::(anonymous namespace)::AllocateBuffer()
@ 0x107a22bc8 0x0
@ 0x102957e08 xls::dslx::RunComparator::RunComparison()
@ 0x10296795c std::__1::__function::__func<>::operator()()
@ 0x102ae017c xls::dslx::BytecodeInterpreter::Run()
@ 0x102adf450 xls::dslx::BytecodeInterpreter::Interpret()
@ 0x10295a474 xls::dslx::DslxInterpreterParsedTestRunner::RunTestFunction()
@ 0x10295d228 xls::dslx::AbstractTestRunner::ParseAndTest()
@ 0x1029364d4 main
@ 0x19fa62b98 start
```
**To Reproduce**
Steps to reproduce the behavior:
1. Run either of my two bazel tests on MacOS. Unfortunately I can't share the test sources with you.
**Expected behavior**
The JIT should not crash. The tests should pass (they do on Linux).
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Environment (this can be helpful for troubleshooting):**
- OS: MacOS
- Versions: The latest XLS from June 17 or 18, 2025.
Contributor guide
Assessment
This issue has not been assessed yet.