-
Notifications
You must be signed in to change notification settings - Fork 404
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
Logic crashed validation (multiple startup deal improperly with locked db) #4822
Comments
Oh wow yeah that’s my fault. The validation will start multiple surges and I don’t deal with that case properly. Thanks for the excellent bug report as a quick workaround start the xt standalone and let it run for a minute before trying in logic |
Fix here is theee things (note to self)
I’ll close this when I merge 1 and 2; and add 3 to the patch browser book of work issue |
1. Opened the standalone Surge XT.
2. Let it run for a while.
3. Closed the app.
4. Opened Logic
5. Rescanned in plugin manager.
6. Validation still failed.
|
Same error? |
Yes I got the same error.
However, I restarted, rescanned, and it passed!!!
|
Yeah it’s a timing tbing if the db is built which is why running headless for a bit plus a restart masked it. I will def get a fix in though. Thanks for the great report! |
OK super easy to repro. Just build latest XT at head |
OK I have a fix for the validation crash. Still get a huge mess of errors though if you end up starting two patch browsers at once against a fresh db. I'll add that over in #2359 though along with the status indicator. |
1. Don't initialize the DB on startup; rather init it when you first open the patch browser 2. End my 'throw in destructor' bad habit since that worked horribly. Catch everything properly etc... This closes surge-synthesizer#4822 but there's still lots to do in surge-synthesizer#2359 including a nasty locked handler fail when you start two surges against a fresh db
1. Don't initialize the DB on startup; rather init it when you first open the patch browser 2. End my 'throw in destructor' bad habit since that worked horribly. Catch everything properly etc... This closes #4822 but there's still lots to do in #2359 including a nasty locked handler fail when you start two surges against a fresh db
OK great this problem on crash-at-validation is now fixed. Thanks for the excellent report. |
(new nightly will have fix in ~1hour) |
Bug Description:
I installed the Surge Nightly_XT, and Logic validation fails.
Surge Version
Reproduction Steps:
Expected Behavior:
Validation passes.
Computer Information (please complete the following information):
Additional Information:
The text was updated successfully, but these errors were encountered: