ZynAddSubFX crashes LMMS #1758
Labels
Comments
|
Master branch I assume? |
|
1.1.1 via KXStudio build. I should also note that this is not new as of 1.1.1, this is just the first time I've captured a stack trace. |
|
If you can reproduce with 1.1.2 built from source, then it is our bug. If you cannot, then it may be either a system configuration or packaging bug by the KXStudio team. (and then we can tag Filipe @ https://github.com/falkTX) if needed. |
|
OK... will try with 1.1.2 |
|
Not sure if this changes anything: the bug I'm seeing is that LMMS crashes, Zyn is still running |
|
Hmm... I think that was the same symptom the VST (#1736) bug per this cryptic comment:
-Tres |
|
Another recommendation I've seen historically for shared memory bugs is this:
I know Ubuntu runs this after each package installation. Not sure if Debian follows suit or not. |
|
This issue still occurs in 1.1.2: |
|
Let me know if there's anything else I can collect to help with this. I haven't been able to narrow this down to any specific action that causes the crash, just that eventually LMMS will crash if the Zyn GUI is open (whether I'm actively using either or not) |
|
Is it normal for you to compile stable-1.1 branch in a folder called "lmms-master" ? |
|
At a glance, it appears to be memory corruption in the new FxMixer. |
|
Well I don't suppose being on the wrong branch would be helping things... this build was from master, 1.1.2 tag. I'll try again with stable-1.1, 1.1.2 tag. Sorry about that... still a bit green when it comes to git. |
Yeah, the
That is partially our fault. Previously we had the current stable branch set as our default branch when cloning, but we haven't been consistent. Lately (about 6 months) it has been defaulting to master. We get a lot of valid bug reports that are really master bugs that only surface because of branch confusion. This isn't invalid though because we have to fix this stuff in master anyway, it just causes a lot of unnecessary confusion. -Tres |
|
Next attempt (git checkout stable-1.1): |
I'm not sure if it matters, but historically we've launched lmms from the build directory The reason I mention this is that IIRC it wasn't until recently (master branch) that Lukas made some changes to get the resources worked out when launched from a different directory. My best guess is that RemotePlugin cares about these resource paths to determine the location of the Zyn binary. Can you try launching it as close to our build instructions as possible? |
|
Sorry for the delay, getting over a cold. I'm trying to update my repo to the latest and try again as you requested. However, there appears to be a change in the git repo as the stable-1.1 branch no longer exists... should I be checking out a specific tag or is building the master branch now the correct approach? |
|
https://github.com/LMMS/lmms/tree/stable-1.1 Still exists for me.... |
|
@pbella can you confirm that this crash still happens on @curlymorphic's zynwin branch?
|
@curlymorphic's Zynwin branch affects master, but this bug was specific to stable-1.1. Since the OP hasn't been able to offer steps to reproduce, I'm closing out as invalid. Please feel free to reopen if we can get enough information to reproduce. In regards to the crashes we do know about, Zyn and LMMS currently have a namespace conflict (#2269) on the master branch, which will be resolved prior to the release of 1.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been noticing that Zyn periodically crashes LMMS on Linux after anywhere several minutes to an hour or so of use. The latest crash occurred after an extended period of inactivity. gdb output
The text was updated successfully, but these errors were encountered: