You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Jamulus 3.7 hangs -eventually- on Mac Big Sur #1791
Jamulus hangs -- pretty much every time -- after a while -- can be 5 minutes, can be an hour, on my Macbook Pro (2020, 2 GHz Intel quad-core I5) running Big Sur 11.2.3. Not a problem with same Jamulus version on an older Mac running an older OS.
To Reproduce
Join a Jamulus session, then don't touch anything. Eventually I will get a spinning ball and can't activate any Jamulus controls. Sometimes Jamulus continues to function; at other times, the connection drops. (does not happen with current Jamulus on an old Mac running High Sierra.)
Expected behavior
Expected behavior is a normal Jamulus session.
Screenshots
Operating system
MacOS 11.2.3
Version of Jamulus
Jamulus on this same machine seems to have buffer underruns/overflows -- sound gets glitchy: I can temporarily cure it by re-setting the buffer delay. It seems to be when I don't do reset the buffer delay that the hang occurs.
Hi!
Thanks for the report. This sounds very similar to #1643, but I'd like to keep it open for now as the other issue mainly targeted a regression introduced in 3.8.0 (despite the initial report).
We suspect a general problem in the Qt event handling on Mac with recent Qt versions and yet have to find a way to work around it.
It would help if you could try the following:
3.8.0rc2 (regular Mac build) - It woud be best if this version did not show any issues for you as it is planned to become the 3.8.0 final release. I suspect that you will encounter the issue with this version as well, but this information would help a lot.
Also @RonCohen1 could you say which skin you are using? Normal, Compact or Fancy? And could you try using a different one to see if it makes any difference?
Hi,
I hadn't found issue #1643 on a search before posting my report; it does seem like the same issue. I am trying to figure out how I can usefully contribute to this discussion -- my rehearsals with large numbers of participants are becoming less frequent as pandemic restrictions are lessening. But maybe the following is of use:
Last night I had Jamulus running simultaneously on two Mac computers -- one I was using to provide a one-way audio bridge to Zoom using Blackhole as output device on Jamulus and input device on Zoom. That was running on my 2020 MBP running Big Sur, and that's the one that got the spinning beachball, twice -- once when I was first setting up, before the connection to Zoom (but with 4 clients connected to Jamulus), and once after an hour with 20 clients connected. The second Jamulus was running on my 2009 Macbook Pro (running High Sierra), that I was using for my active participation in the rehearsal. On that one, Jamulus ran flawlessly for close to two hours. Same version of Jamulus (3.7.0) on both.
The reason for running two instances of Jamulus on two machines: Jamulus on the 2020 MBP has been consistently problemmatic. Particularly with large numbers of clients, I get a build-up of glitchy crackles and pops in the audio that I can temporarily stop by re-clicking on the buffer delay button. I do not have this problem at all on the older Mac. But the older mac is sufficiently under-powered that I can't count on running both Jamulus and Zoom. Hence the two-Mac solution.
I note that if I run a Jamulus session on the newer Mac and do the temporary fix of the glitches I mentioned above every few minutes, I can stay in a rehearsal for two hours with no problem -- so the suggestions made in the #1643 discussion about memory leaks and swapping seem to be right on target.
I think I did not have the spinning ball problem on 3.6.2.
But I can't help but think that the fact that I had had the problem a bunch of times on the newer mac and never on the older one implies a connection between the beachball problem and the glitchy audio problem; I've wondered about that being related to a memory leak. Is that plausible?
I think one of the other replies asked about skin, etc: when I'm participating in big groups, I almost always have the compact skin activated. Chat window may be open or closed. Settings window is always open, but may not be in the foreground.
As to testing with different versions: this is probably only practical if I can reproduce the problem with only two clients connected, as I'm not having frequent-enough large-group rehearsals to gather sufficient data in a timely way.
Ron
https://bugreports.qt.io/browse/QTBUG-88248 sounds related (event-related leaks), but seems to only occur with Qt 5.14 or newer while our previous builds were based on 5.9, IIRC.
There is a small chance that moving our builds to Qt6 might help with this issue.
If someone wants to try, feel free to download the completely untested Qt6 Mac build from PR #2300. Expect breakage though.
Please post in this issue, if you can still observe the described bug with this build or if things get better or worse.
Please post to #2300 if you find any other issues with this build.
This seems to be (1) not specific to a MacOS version (has been reported on Mojave, Big Sur, and maybe others) and (2) requires that no Jamulus windows have focus for some time (amount of time varies). I haven't seen any reports for a M1 Mac (all seem to be Intel), but I have an M1 so will see if I can replicate.
Another thing to try: Could someone try running export QT_MAC_WANTS_LAYER=1 and starting Jamulus via command line (from the same Terminal)?
(The linked bug report does not match exactly what's reported here. Still, it's also about UI-related hangs starting with Big Sur, so there's at least some chance... And btw, Qt 5.12.3 5.15.3, which was just released, claims to have a fix for exactly the linked issue).
I tried it today in an online session. The bug is still there, but it is much better now. memory usage does only increase slowly. Here you can find a few videos showing the activity window of MacOS 11.6.4. when Jamulus is in front or not and when quitting Jamulus.
Hi, under Jamulus 3.9 beta 2 and MacOS 11.6.8 this bug is no longer exiting. I had a session today with Jamulus running in the background a lot and it remained responsive and there was no hang at all :-)
As there is at least one positive report that this issue should be fixed as of 3.9.0, I'm closing this for now. If someone has different experiences, please comment or open a new issue. Thanks.
Activity
hoffie commentedon May 31, 2021
Hi!
Thanks for the report. This sounds very similar to #1643, but I'd like to keep it open for now as the other issue mainly targeted a regression introduced in 3.8.0 (despite the initial report).
We suspect a general problem in the Qt event handling on Mac with recent Qt versions and yet have to find a way to work around it.
It would help if you could try the following:
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
Mac autobuild: Update to Xcode 12
hoffie commentedon May 31, 2021
Linked another build to try based on #1794 in the comment above now.
softins commentedon May 31, 2021
Also @RonCohen1 could you say which skin you are using? Normal, Compact or Fancy? And could you try using a different one to see if it makes any difference?
RonCohen1 commentedon May 31, 2021
hoffie commentedon May 31, 2021
@RonCohen1 Thanks for the feedback!
Just a short brain dump of things to play around with, although all of it seems QML-related so might have no effect for us:
https://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html
QSG_RENDER_LOOP=threadedvsQSG_RENDER_LOOP=basic.https://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph-renderer.html#performance
https://bugreports.qt.io/browse/QTBUG-88248 sounds related (event-related leaks), but seems to only occur with Qt 5.14 or newer while our previous builds were based on 5.9, IIRC.
Mac autobuild: Update to Xcode 12
21 remaining items
hoffie commentedon Jan 27, 2022
There is a small chance that moving our builds to Qt6 might help with this issue.
If someone wants to try, feel free to download the completely untested Qt6 Mac build from PR #2300. Expect breakage though.
Please post in this issue, if you can still observe the described bug with this build or if things get better or worse.
Please post to #2300 if you find any other issues with this build.
MattMerz-Violin commentedon Feb 4, 2022
Tried it today with latest MacOS 11 version. Still the same issue unfortunately :-(
chrisrimple commentedon Feb 4, 2022
This seems to be (1) not specific to a MacOS version (has been reported on Mojave, Big Sur, and maybe others) and (2) requires that no Jamulus windows have focus for some time (amount of time varies). I haven't seen any reports for a M1 Mac (all seem to be Intel), but I have an M1 so will see if I can replicate.
hoffie commentedon Mar 4, 2022
Here's another build to try: https://github.com/jamulussoftware/jamulus/suites/5504510055/artifacts/176206626
It's from #2449 which uses a newer Xcode/macOS SDK. Again, there's only a rather small chance that it helps, but it would be helpful to know.
Feedback appreciated!
hoffie commentedon Mar 7, 2022
Another thing to try: Could someone try running
export QT_MAC_WANTS_LAYER=1and starting Jamulus via command line (from the same Terminal)?(The linked bug report does not match exactly what's reported here. Still, it's also about UI-related hangs starting with Big Sur, so there's at least some chance... And btw, Qt
5.12.35.15.3, which was just released, claims to have a fix for exactly the linked issue).MattMerz-Violin commentedon Mar 10, 2022
I tried it today in an online session. The bug is still there, but it is much better now. memory usage does only increase slowly. Here you can find a few videos showing the activity window of MacOS 11.6.4. when Jamulus is in front or not and when quitting Jamulus.
http://www.vaskez.de/jamulus_bug/Jamulus_in_front.mov
http://www.vaskez.de/jamulus_bug/Jamulus_not_in_front.mov
http://www.vaskez.de/jamulus_bug/Quit_Jamulus.mov
So it looks like the switch to QT6 at least brings some changes. I hope this is helpful.
MattMerz-Violin commentedon Jul 21, 2022
Hi, under Jamulus 3.9 beta 2 and MacOS 11.6.8 this bug is no longer exiting. I had a session today with Jamulus running in the background a lot and it remained responsive and there was no hang at all :-)
Great improvement!
pljones commentedon Jul 22, 2022
Can you confirm which MacOS build you used?

Thanks!
MattMerz-Violin commentedon Jul 22, 2022
Hi, I used the jamulus_3.9.0beta_mac.dmg build.
Best regards, Matt
pljones commentedon Jul 22, 2022
@MattMerz-Violin
Cheers
@RonCohen1 @Rob-NY @chrisrimple,
Can you comment at all on the 3.9.0beta2 release?
Thanks
hoffie commentedon Aug 16, 2022
As there is at least one positive report that this issue should be fixed as of 3.9.0, I'm closing this for now. If someone has different experiences, please comment or open a new issue. Thanks.