Does not fail on Fedora.

With Debian 9.1 32-bit, the freeze happens on the first move.  With the "volatile" patch in, it works.  I had an old AMD Slackware O/S and wanted to try it there also, but it had an error on the build so decided not to pursue it there.

  Never heard of the "volatile" keyword C++ before but when I looked it up, I found this and am still laughing:

In other words, I would explain this as follows:

volatile tells the compiler that,

"Hey compiler, I'm volatile and, you know, I can be changed by some XYZ that you're not even aware of. That XYZ could be anything. Maybe some alien outside this planet called program. Maybe some lightning, some form of interrupt, volcanoes, etc can mutate me. Maybe. You never know who is going to change me! So O you ignorant, stop playing an all-knowing god, and don't dare touch the code where I'm present. Okay?"

I will check in the patch soon.  The "volatile" may be a good fix for BT #632 also.

On Wed, Sep 20, 2023 at 2:06 PM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:

вс, 17 сент. 2023 г., 10:44 Andrew Randrianasulu <randrianasulu@gmail.com>:

вс, 17 сент. 2023 г., 10:38 Andrea paz <gamberucci.andrea@gmail.com>:

I try to compile with the only patch 0004-Fix-for-group-move-hang-v2.patch.
Build OK; no error messages on terminal.

I started the appimage while compiling CinGG, but had no LV2 errors.
(I have a CPU with many threads and have lots of Ram).
No freeze with (build) or without (appimage) patch...

Thanks for testing .... I'll try few more times on my end (may be after reboot).

Reboot happened, my laptop exhibits same symptom (hang), so I guess this is more software than hardware thing.

Phyllis, can you try v2 patch on Fedora and also 32-bit debian and see how it behaves there?