v13.0.40 Beta Available -- This one's going to blow your minds!

[FigBug]

Hi - I'm getting regular freezes (i.e. every 5-10 minutes) in WF 13.0.40. No obvious trigger - has happened even when I was away from the computer. I'm running on Ubuntu 24.04, Pipewire, Wayland. I've switched sandboxing on and off, and switched from OpenGL and software rendering, but the problem persists. I end up killing Waveform from the Task Manager so I'm not sure it is generating a crash log. Happy to try to diagnose this but not sure what the next steps are to do so.

I have run Waveform from the terminal and captured some of the output there plus associated logs below in case this is useful.

An exit message of "double free or corruption (out)" is quite common.

Code: Select all

Lock-up:
malloc(): unsorted double linked list corrupted

Crash:
23 Apr 2024 9:25:07  Crash Location: UnknownLocation
23 Apr 2024 9:25:07  Maintenance took: 3 ms
23 Apr 2024 9:25:07  Crashed

Crash:
23 Apr 2024 9:27:48  Crash Location: UnknownLocation
23 Apr 2024 9:27:48  Crash Location: UnknownLocation
23 Apr 2024 9:27:48  Maintenance took: 4 ms
23 Apr 2024 9:27:48  Crashed
23 Apr 2024 9:27:48  Crashed

double free or corruption (out)

Crash:
23 Apr 2024 11:30:51  Crash Location: UnknownLocation
23 Apr 2024 11:30:51  Maintenance took: 2 ms
23 Apr 2024 11:30:51  Crashed
23 Apr 2024 11:30:51  

double free or corruption (out)

I'm suspecting this is due to a corrupt project. I have created a brand new project and edit from scratch and copied the tracks from the faulty project into it. So far it seems stable. Could just be down to this project being based on an old template which has been moved between a few installations of Waveform (and between Windows and Ubuntu). If the problem returns I'll post back. Meanwhile I'll re-build the template in the same way.

Could you zip up the entire project folder and send it to me? roland@tracktion.com, you might need to use Dropbox / WeTransfer if it's large.

[unholyeyebrows]

Could you zip up the entire project folder and send it to me? roland@tracktion.com, you might need to use Dropbox / WeTransfer if it's large.

Will do my best. Sods law has kicked in here - after re-building my template I deleted the old one (via Waveform, so permanently), but have now restored it from a backup a couple of days old. So far I cannot re-create the problem. If I can I'll send the template.

[Watchful]

Not to jinx myself, but I've been using .40 for a few days and it's been rock solid.

[unholyeyebrows]

I'm suspicious more of my system than Waveform at this point. W13 in general has been running very smoothly for me too.

[dysjoint]

I'm suspicious more of my system than Waveform at this point. W13 in general has been running very smoothly for me too.

I get these freezes too periodically and I'm also suspicious of my system. Perhaps graphics or which hard drive the project is on? but I've never narrowed it down. Its struck again on point 40. It's a temporary (up to 30 seconds or so) whole system freeze, including mouse, or Waveform goes unresponsive. It's a home built PC so could be my ignorance of some settings also.

[unholyeyebrows]

I get these freezes too periodically and I'm also suspicious of my system. Perhaps graphics or which hard drive the project is on? but I've never narrowed it down. Its struck again on point 40. It's a temporary (up to 30 seconds or so) whole system freeze, including mouse, or Waveform goes unresponsive. It's a home built PC so could be my ignorance of some settings also.

So I have been having pretty much the same experience today just as you describe - 30 - 60 seconds when WF would just freeze, and then unfreeze. The audio would keep playing, but the whole UI would be stuck. However when it was really bad the whole system would permanently freeze (i.e. the entire desktop) which to me suggests something else other than the DAW. I am running the brand new Ubuntu 24.04, plus pipewire-jack at 96khz / 2048 sample size, with some realtime tweaks (i.e. adding my user to the pipewire group). All of the above might be contributing to the issues. Hardware-wise all pretty modern - Ryzen 5 8600G, 32GB DDR5, on a Gigabyte B650i AX motherboard. I've ben running Ubuntu 24.04 since the beta was released with no real issues. One change I did make about a week ago was to update my motherboard BIOS to a version which unlocked the AMD STAPM which I believe increases performance of my 8600G. Whether that is a factor, who knows?

Anyway, I suspect I'm deviating well off topic here. Having used WF 11, 12, and now 13, 13 certainly has been the best performer and I suspect my issues over the last couple of days are related to the not-quite-finished OS I'm running!

[unholyeyebrows]

I just noticed this thread elsewhere in the forum. Possibly similar symptoms for the lock-up issue:

viewtopic.php?t=586505

[FigBug]

Are the people who are having lockups Windows users? Any chance you have high refresh rate monitors?

[unholyeyebrows]

Are the people who are having lockups Windows users? Any change you have high refresh rate monitors?

I'm on Ubuntu, but running dual monitors each set at 120Hz. I'll test at 60hz and report back. Having thought I'd made my problem go away it has returned again so may be able to get a good / bad comparison.

[unholyeyebrows]

Another thought, might the lock-ups be realtime related? I have some realtime config in my Pipewire / Jack set-up, and have noticed some instances of "sched: RT throttling activated" in my /var/log/kern.log around the time Waveform crashed. Here are some examples in case this is any use:

Code: Select all

2024-04-22T17:23:21.483514+01:00 ubuntu-pc kernel: Waveform13[209385]: segfault at 1c ip 00005daa48e92445 sp 00007ffc3ad494c0 error 4 in Waveform13[5daa476a3000+241b000] likely on CPU 9 (core 3, socket 0)
2024-04-22T17:23:21.483519+01:00 ubuntu-pc kernel: Code: 83 ec 08 e8 ad 1e ff ff 48 8b 4d 40 48 89 ee 31 ff 4c 8b a0 c8 00 00 00 31 d2 e8 f6 ca 0d 00 48 89 c6 4c 89 e7 e8 cb 4c fa ff <48> 8b 50 1c 48 8b 40 14 48 83 c4 08 5d 41 5c c3 90 66 2e 0f 1f 84


2024-04-23T08:49:04.526027+01:00 ubuntu-pc kernel: process '/usr/bin/Waveform13' started with executable stack
2024-04-23T08:49:10.222019+01:00 ubuntu-pc kernel: warning: `AppRun' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
2024-04-23T08:49:29.465136+01:00 ubuntu-pc kernel: sched: RT throttling activated


2024-04-23T10:09:03.446054+01:00 ubuntu-pc kernel: process '/usr/bin/Waveform13' started with executable stack
2024-04-23T10:09:22.836034+01:00 ubuntu-pc kernel: audit: type=1400 audit(1713863362.834:184): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4140 comm="snap-confine" capability=12  capname="net_admin"
2024-04-23T10:09:22.836038+01:00 ubuntu-pc kernel: audit: type=1400 audit(1713863362.834:185): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4140 comm="snap-confine" capability=38  capname="perfmon"
2024-04-23T10:09:23.027039+01:00 ubuntu-pc kernel: audit: type=1400 audit(1713863363.025:186): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4196 comm="snap-confine" capability=12  capname="net_admin"
2024-04-23T10:09:23.027047+01:00 ubuntu-pc kernel: audit: type=1400 audit(1713863363.025:187): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4196 comm="snap-confine" capability=38  capname="perfmon"
2024-04-23T10:09:30.774039+01:00 ubuntu-pc kernel: Waveform13[4000]: segfault at 357 ip 00007ccdb8b6c76e sp 00007fff2a0a5f20 error 4 in ld-linux-x86-64.so.2[7ccdb8b6b000+2b000] likely on CPU 1 (core 1, socket 0)
2024-04-23T10:09:30.774052+01:00 ubuntu-pc kernel: Code: cf 02 00 e9 b4 c3 00 00 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 41 54 4c 8d 25 a7 62 03 00 53 48 89 fb 4c 89 e7 ff 15 c2 52 03 00 <80> bb 57 03 00 00 00 75 47 8b 93 50 03 00 00 85 d2 74 7f 48 b8 ff
2024-04-23T10:10:03.542576+01:00 ubuntu-pc kernel: sched: RT throttling activated
2024-04-23T10:11:24.071045+01:00 ubuntu-pc kernel: Waveform13[4621]: segfault at 357 ip 0000796e2d94776e sp 00007ffd8a51f560 error 4 in ld-linux-x86-64.so.2[796e2d946000+2b000] likely on CPU 2 (core 2, socket 0)
2024-04-23T10:11:24.071059+01:00 ubuntu-pc kernel: Code: cf 02 00 e9 b4 c3 00 00 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 41 54 4c 8d 25 a7 62 03 00 53 48 89 fb 4c 89 e7 ff 15 c2 52 03 00 <80> bb 57 03 00 00 00 75 47 8b 93 50 03 00 00 85 d2 74 7f 48 b8 ff

[JamminFool]

there is still a problem with saving presets in the samplers. In the Multi-Sampler, for example, if you save a preset "foo" and disable "save audio preview", then the preset is saved, but the Preset Name field is not filled in with the new name. (Note that I actually dismissed the Save Audio Preview window rather than select "discard" or "use as preview", in case that is necessary to reproduce).

if you leave "save audio preview" enabled , then (again) the preset is saved but the drop-down preset menu begins to behave erratically after that, sometimes crashing, if it displays at all.

the other 3 samplers need to be checked for all combinations of the above also (i can't remember all the various oddities, some scenarios worked correctly, some did not...)

[FigBug]

I'm not exactly sure what "sched: RT throttling activated" means, but some googling suggests it has to do with abusing real time threads. The only real time threads we use are in plugin bridge. Can you disable if you are using it?

[unholyeyebrows]

I'm not exactly sure what "sched: RT throttling activated" means, but some googling suggests it has to do with abusing real time threads. The only real time threads we use are in plugin bridge. Can you disable if you are using it?

Do I assume you want me to disable my realtime config? If so yes I can do that. I'm just trying to work out a way to reliably duplicate the problem to try to give you some decent data to work off. Will report back once I get anything,

[dysjoint]

Windows user, 3 monitors at 60hz. Definitely had trouble moving mixer/clip launcher to a second screen, but haven't spent enough time with this version yet to give any real useful info. Needle in a haystack, and problem is only intermittent. I couldn't definitively claim it as a bug yet on my end.

[dajonaga]

FWIW the only time I experienced slowness, GUI stutter or the likes was when using OpenGL renderer... so I only use software renderer