ZynAddSubFX is crashing my PC

Having trouble with LMMS? Ask about it here.
I have been using LMMS 1.3.0 appimage on Linux Mint since a long time and I never had any problems. Recently I tried to check out ZynAddSubFX, because I never really tried it before. I can open Zyn, I can adjust some parameters there and suddenly, my entire PC resets! This is really weird! I assume it is because of the alpha, because I can't remember this kind of behaviour, when I was using LMMS 1.2.2 back in the days. I'm not sure if this issue is widespread or known among other users, so I just wanted to share it. I don't really have a clue about computers, but I dump some of my specs here. Maybe some expert here will find it useful in analyzing the issue:

System: Kernel: 5.4.0-107-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 5.2.7 wm: muffin dm: LightDM Distro: Linux Mint 20.3 Una
base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: ASUSTeK model: A88XM-A v: Rev X.0x serial: <filter>
BIOS: American Megatrends v: 0903 date: 12/06/2013
CPU: Topology: Quad Core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MCP
arch: Piledriver rev: 1 L2 cache: 2048 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31358
Speed: 1912 MHz min/max: 1900/3900 MHz Core speeds (MHz): 1: 2011 2: 2001 3: 2241
4: 2035
Graphics: Device-1: AMD Richland [Radeon HD 8570D] vendor: ASUSTeK driver: radeon v: kernel
bus ID: 00:01.0 chip ID: 1002:990e
Display: x11 server: X.Org 1.20.13 driver: ati,radeon unloaded: fbdev,modesetting,vesa
resolution: 1440x900~60Hz
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.4.0-107-generic LLVM 12.0.0)
v: 4.3 Mesa 21.2.6 compat-v: 3.1 direct render: Yes
Audio: Device-1: AMD Trinity HDMI Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:01.1 chip ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 00:14.2 chip ID: 1022:780d
Device-3: Texas Instruments PCM2902 Audio Codec type: USB
driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-1:2 chip ID: 08bb:2902
Sound Server: ALSA v: k5.4.0-107-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: e000 bus ID: 03:00.0 chip ID: 10ec:8168
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 111.79 GiB used: 13.14 GiB (11.8%)
ID-1: /dev/sda vendor: Intenso model: SSD Sata III size: 111.79 GiB speed: 6.0 Gb/s
serial: <filter>
Partition: ID-1: / size: 109.04 GiB used: 13.14 GiB (12.1%) fs: ext4 dev: /dev/sda5
Sensors: System Temperatures: cpu: 12.4 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com una main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info: Processes: 217 Uptime: 4h 02m Memory: 22.69 GiB used: 1.21 GiB (5.3%) Init: systemd
v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 client
inxi: 3.0.38
NOVAVA wrote:
Fri Apr 08, 2022 4:36 pm
my entire PC resets!
If you wasent on Mint, i would have said : virus, but not so now.
I have NO idea what is going on!
Can you reproduce or was it a 'one-off'?
If it is reproduceable it is important! Please make a bug-report:

https://github.com/LMMS/lmms/issues/new/choose
musikbear wrote:
Sat Apr 09, 2022 3:27 pm
NOVAVA wrote:
Fri Apr 08, 2022 4:36 pm
my entire PC resets!
If you wasent on Mint, i would have said : virus, but not so now.
I have NO idea what is going on!
Can you reproduce or was it a 'one-off'?
If it is reproduceable it is important! Please make a bug-report:

https://github.com/LMMS/lmms/issues/new/choose
Hey musikbear! Yes, it is actually quite easy to reproduce. Especially when you try tweaking the harmonics. I made a short video which demonstrates it: https://www.youtube.com/watch?v=1Cr-Ay4YlI4

I will soon make a github account and post it there.
I just did a test on Linux (openSUSE tumbleweed)

I downloaded the 1.3 appimage and did what you did in the youtube vid.

No problem occurred, only the shape of the wave changed (as it should be)

So now we need to try and find what is happening at your site.

I am thinking GDB, but cant recall exactly how that worked right now.
Then we might be able to make a log file and see why it goes boom.
Gps wrote:
Sun Apr 10, 2022 1:54 am
I just did a test on Linux (openSUSE tumbleweed)
Good stuff there 👍
Now we know that it is reproduceable on NOVAVA pc, but that it is not a general Linux-issue.
That is good for LMMS, not good for NOVAVA.
@NOVAVA Maybe roll-back to 1.2.2 Off, and test there?
Its annoying, but an issue like this on a local pc, is really hard to find locally (you) and impossible remote (us)
GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed.
https://www.sourceware.org/gdb/

You need to start LMMS from gdb if I recall right.
Gps wrote:
Sun Apr 10, 2022 7:03 pm
GDB, the GNU Project debugger, allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed.
https://www.sourceware.org/gdb/

You need to start LMMS from gdb if I recall right.
Thank you for looking into the issue. I really would like to try GDB, but I don't think I am competent enough to do it. All this coding and terminal typing stuff is black magic for me. 😅 I tried to look up some instructions how to do it, but this is just too complicated for me.
I know that on windows, I just need to open a powershell window in the folder, and type ./[APPNAME].exe (or ./filename.extension, whatever) and hit enter. (mind you, this does NOT debug. This simply.. something. but not debug.)
Try this: https://sourceware.org/gdb/onlinedocs/gdb/Files.html
Or https://web.eecs.umich.edu/~sugih/pointers/summary.html
Can' t recall exactly, but if I remember right you start LMMS with a special copmmand. Not the one you normally would use to just start LMMS from the cli.

Or was it that you need to start gdb first?

What it does is record what a program does while its running.

After a crash you find the log file, sand search for what went wrong.

Found something:
https://github-wiki-see.page/m/LMMS/lmm ... gging-LMMS
Debugging an AppImage

In the event a crash only occurs from a Linux AppImage:

1. Run ./lmms-x.x.x.AppImage --appimage-extract
2. Run export LD_LIBRARY_PATH="$(pwd -P)/squashfs-root/usr/lib:$LD_LIBRARY_PATH"
3. Run gdb squashfs-root/usr/bin/lmms.real (an optionally second parameter is the path to a core dump)
4. Type set sysroot ./squasfs-root and then set solib-search-path ./squashfs-root/usr/lib
5. If not working with a core dump, type run to run LMMS and reproduce a crash.
6. Type thread apply all bt full to get full backtrace of all threads.
This is for Linux though, that command will be different on Windows.