[BUG] EXO (All models) hang on WARMING UP, then 0% RAM usage on Python 3.13 systems

[Stratamesh]

Describe the bug

On any model, and any # of nodes, EXO will active its "LOADING" step, then switch to "WARMING UP"... On Ubuntu 25, which natively ships with and runs Python 3.13, Python process during the "WARMING UP" stage will break and lose all RAM assigned to it. The Python task will then become zombie.

To Reproduce

Steps to reproduce the behavior:

1. Launch EXO, load model on Ubuntu 25 (Python 3.13)
2. Wait for WARMING UP stage
3. You should get a FAILED message after the Python task has failed and possibly a "Python 3.13 has quit unexpectedly" pop-up.

Expected behavior

EXO should correctly load the model as it does with Python 3.11 on all connected nodes.

Actual behavior

EXO starts, begins to load model (ex. Llama3.1:8B) 1 or 2+ nodes. EXO successfully loads model into RAM on both/one node(s). 5s after, python task held by EXO quits due to incompatible memory manager causing a crash at the C-extension level.

Environment

• macOS Version: N/A
• EXO Version: Latest (Official)
• Hardware:
  • Device 1: Dell PowerEdge (64GB) x2 Intel Xeon
  • Device 2: Dell PowerEdge (128GB) x2 AMD
  • Additional devices:
• Interconnection:
  • 1GbE Ethernet between all devices.

Additional context

ALL packages up to date, many models attempted, Python reinstalled. I understand this is likely an already known issue, but would like to express my concerns/experience to better improve the software.

Add any other context about the problem here.

[Evanev7]

Exo does not support python 3.11 and never has. Are you running the old exo?

[Stratamesh]

I am using the most recent version of Exo. As newer systems and users are transitioning to newer OS versions and Python versions (3.13), I think that it should explicitly state in the documentation what version of Python you need. (or maybe I just didn't see it.) I'm sorry, when I mentioned Python 3.11 I meant 3.12, or the version it functions best on. I feel that they should add support for newer Python systems, that's all. Also, I do believe it to have some relation with 3.13, as in code tab, python-version shows 3.13.

[Evanev7]

Ah yeah, we've always been on 3.13. What you may be running into is the mlx[cpu] g++12 dependency - this is an upstream issue with mlx - some kind of error message would be useful to diagnose further.

[Stratamesh]

Okay thanks I'll see If i can get anything. Does Exo have a debug or verbose mode?

[Evanev7]

It does, though I don't think it will help much in your situation (uv run exo -v). You can also check the log file at .cache/exo.log or .exo/exo.log

[Nkr1shna]

It does, though I don't think it will help much in your situation (uv run exo -v). You can also check the log file at .cache/exo.log or .exo/exo.log

Here is the log file.

exo.log