Crash on loading MultiFile folder

Support
1

Hi,

I’m unable to load a MultiFile folder.

In AbleSet 3.04, I first got this error several times when trying to open it:

“Uncaught Exception: Error: EBADF: bad file descriptor, lstat ‘/dev/fd/12’”

I then updated to 3.07. Now AbleSet just crashes or becomes unresponsive when I try to open the MultiFile folder.

I already cleaned all cache folders.

When I remove ableset.json from the folder, AbleSet no longer crashes, but it also does not load the folder. I’ve attached the file. Removing canvases or setlists does not help.

When I remove the entire AbleSet folder from the MultiFile folder, it loads fine. I can then manually add back canvases, setlists, and the project script, and everything seems to work. However, as soon as I disable the MultiFile project and try to enable it again, the issue returns.

Could you please help me figure out what is causing this? It worked just fine few hours ago…

System details:

  • AbleSet 3.07

  • macOS Tahoe 26.1

  • Ableton Live Suite 12.3.6

ableset.json (31.0 KB)

Edit: other multifile folders works fine. Just not the one I need for show :smiley:

2

Hey @Jan_Slawinski,

Thank you for reporting this!

To understand what’s going on, could you please create a Log Package?
You can create a log package by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.
Please make sure to include your project files as well (just the.als files, no audio needed)
To send the files, you can upload them to AbleSet’s support inbox.

I’m looking forward to your reply!

3

Files uploaded, thank you!

1 Like
4

The problem does not appear on my colleagues computer (M2 Air, Tahoe 26.1) running version 3b18. The folder is identical, iCloud synced, owned by the primary (my) machine.

5

Hi,

I’ve reviewed the crash report (with help from ChatGPT, based on my non-expert interpretation), and it seems this is not a typical file-loading error but a hard crash inside the Electron/Node runtime.

The crash is EXC_BAD_ACCESS (SIGSEGV) with a possible pointer authentication failure, occurring on the main browser thread (CrBrowserMain). The stack trace repeatedly references:

  • v8::api_internal::DisposeGlobal

  • node::AsyncWrap::~AsyncWrap()

  • node::sqlite::UserDefinedFunction::xDestroy(void*)

This suggests the crash happens during object cleanup / memory deallocation in the V8/Node layer, rather than during normal project parsing.

Previously, version 3.0.4 produced:

EBADF: bad file descriptor, lstat ‘/dev/fd/12’

After updating to 3.0.7, the behavior changed to a full crash when opening the same MultiFile folder. This makes me suspect both issues are related, with the newer version failing earlier or more aggressively.

Key observations:

  • Removing ableset.json prevents the crash but the folder does not load.

  • Removing the entire AbleSet project folder allows the MultiFile folder to load normally.

  • The issue appears tied to specific project data rather than system configuration.

Additionally, although removing the AbleSet folder works as a workaround for loading, the system was unstable during today’s show:

  • Canvases were randomly crashing on multiple devices

  • Scores were not loading reliably

  • AbleSet reported disconnections from Ableton, even though there were no actual network issues

This suggests there may be a broader issue with project state handling or data integrity, not just a one-time loading problem.

Also worth noting: when reverting back to beta 21, the same project loads reliably (although some newer features are missing). This further points to a regression introduced in newer versions.

Based on this, it looks like a bug triggered by specific content in the AbleSet project folder (e.g. ableset.json, canvases, or setlists), leading to a failure in internal handling and possibly affecting runtime stability as well.

Thanks!