Rubymine and debase

Is there a path planned forward or a workaround for the debugger in Rubymine?
Seem to constantly run into an issue where a it creates a segmentation fault. This seems to be a known issue with ruby 3.4 ( older versions still work I understand ).

This is the kind of problem I keep having

22:50:52 web.1        | Don't forget to include the Crash Report log file under
22:50:52 web.1        | DiagnosticReports directory in bug reports.
22:50:52 web.1        | 
22:50:53 web.1        | [INFO] SolidQueue-1.1.5 Replaced terminated Dispatcher (3.4ms)  pid: 11541, status: "no exit status set", pid_from_status: 11541, signaled: true, stopsig: nil, termsig: 11, hostname: "Mac-Mini-M4-24GB.local", name: "dispatcher-3f300fb5b55aeb33d770"
22:50:53 web.1        | Subprocess Debugger (ruby-debug-ide 3.0.3, debase 3.0.3, file filtering is supported, block breakpoints supported, smart steps supported, obtaining return values supported, partial obtaining of instance variables supported) listens on 127.0.0.1:50723
22:50:53 web.1        | [INFO] SolidQueue-1.1.5 Replaced terminated Worker (2.8ms)  pid: 11540, status: "no exit status set", pid_from_status: 11540, signaled: true, stopsig: nil, termsig: 11, hostname: "Mac-Mini-M4-24GB.local", name: "worker-35ef4a25aa8141024aa0"
22:50:53 web.1        | Subprocess Debugger (ruby-debug-ide 3.0.3, debase 3.0.3, file filtering is supported, block breakpoints supported, smart steps supported, obtaining return values supported, partial obtaining of instance variables supported) listens on 127.0.0.1:50726
22:50:53 system       | SIGINT received, starting shutdown
22:50:53 js.1         | [webpack-cli] Gracefully shutting down. To force exit, press ^C again. Please wait...
22:50:53 system       | SIGINT received, starting shutdown
22:50:53 system       | sending SIGTERM to all processes
22:50:53 js.1         | exited with code 0
22:50:53 css.1        | exited with code 129