Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reach 1.6.4 Crashes Reaper on exit #24

Open
maxxatgit opened this issue Jun 7, 2024 · 7 comments
Open

Reach 1.6.4 Crashes Reaper on exit #24

maxxatgit opened this issue Jun 7, 2024 · 7 comments

Comments

@maxxatgit
Copy link

maxxatgit commented Jun 7, 2024

I'm on Ubuntu 22.4, Reaper 7.14.

I have been using Reach 1.3 for quite a while with no issues. I upgraded to 1.6.4 and after adding the plugin, when I attempt to remove the plugin, or when I try to close the project (leaving Reaper open), Reaper crashes.

I have some info about the crash, when I run Reaper from the terminal, it sometimes leaves interesting info in the terminal window. I copied the terminal window info to a .txt file. I have attached that file.

Crash Report!.txt

I know it starts out with "Bliss 2> Crash detected:" but this does not happen with Reach v 1.3. There are a lot of plugins in this project, and the only change is the updated Reach.

I am using a purchased, registered copy of Reach.
I have reverted back to 1.3 for now. It still works great! However, I am looking forward to experimenting with the new features in 1.6.3.
Thanks for supporting Linux!

@maxxatgit
Copy link
Author

I just did a quick test.
I created a test project that only contained two tracks, one with Bliss2 and one with Reach.

There were no crashes.

The project that crashes has ~50 tracks, one track has 11 plugins in it.
I'll try to find the track(s) that make it crash...

@maxxatgit
Copy link
Author

Following up...
I deleted the track in Reaper that had Bliss2 in it, and the project would not load, Reaper would simply crash. I reverted back to Reach 1.3, and the project loaded fine.

@oskarsh
Copy link
Member

oskarsh commented Jun 12, 2024

Hey you can try wiping the old REACH settings before installing the new version this might fix the issue.

You can find it in ~/.config/Sinuslabs/Reach

Inside is a User Presets folder, please back it up before proceeding to avoid any Preset loss. You can then install the new REACH version and open it up in Reaper which will recreate the User Presets folder with all the new Presets.

Please let me know if that fixes the issue for you.

@maxxatgit
Copy link
Author

I renamed the existing directory, and tried v1.6.4. Unfortunately, that didn't solve the problem. I also added the package xsettingsd.

Adding xsettingsd did make a difference. Before (as in my 3rd post above), Reaper would crash if I tried to open the offending project. After adding xsettingsd, I could open the project, but attempting to close the project, or removing Reach from the project, caused Reaper to crash. So the crash is happening when Reach tries to exit.

If there is anything else I can do to help find the origin of this, I am happy to do it.

Thanks again for supporting Linux!

@oskarsh
Copy link
Member

oskarsh commented Jun 18, 2024

Hey I will need to look into this in more detail on my own. These crashes needs to be debugged on a deeper level. I will make sure to use REAPER for this as well.

@maxxatgit
Copy link
Author

maxxatgit commented Jul 21, 2024

Just a quick FYI...
Just for the heck of it, I tried Reach 1.6.1-Beta. It works fine, no crashes. 1.6.3 crashes.
Thanks

@maxxatgit
Copy link
Author

Just curious... Did some Rust based code get introduced after 1.6.1 beta? There is a bug: RustAudio/baseview#142 that I have encountered in a Rust based plugin..
Just FYI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants