3.6.1 crashes while recording vinyl & can't send error report

I’m running Windows 11 Home on a Razer Blade 16 (i9-13950HX w/32GB RAM). Several times, while recording vinyl, Audacity 3.6.0 and 3.6.1 crashes. [Well, it actually disappears.] An error window comes up, but the ‘send’ request fails.

I can’t send it all because of the forum post size limits, but here is the beginnings of the contents of the error dialog box:

Operating system: Windows NT
10.0.22631 3958
CPU: amd64
family 6 model 183 stepping 1
32 CPUs

GPU: UNKNOWN

Crash reason: EXCEPTION_ACCESS_VIOLATION_READ
Crash address: 0xffffffffffffffff
Process uptime: 533 seconds

Thread 0 (crashed)
0 lib-wave-track-paint.dll + 0xc5d0
rax = 0x0000000000000010 rdx = 0x0000000000000010
rcx = 0x0000000000000004 rbx = 0x0c0001981ce8e580
rsi = 0x0000000000e80000 rdi = 0x00000018d1bdda60
rbp = 0x0000000000000080 rsp = 0x00000018d1bdd960
r8 = 0x0000000000000010 r9 = 0x00000018d1bdda60
r10 = 0xfffffffffffc0000 r11 = 0x0000000000001000
r12 = 0x0000000000000081 r13 = 0x0000000000000600
r14 = 0x0000000000080000 r15 = 0x0000019815deb888
rip = 0x00007ffd2cc8c5d0
Found by: given as instruction pointer in context

Stack contents:
 00000018d1bdd960 00 b8 de 15 98 01 00 00 88 b8 de 15 98 01 00 00  .¸Þ......¸Þ.....
 00000018d1bdd970 88 b8 de 15 98 01 00 00 01 00 00 00 00 00 00 00  .¸Þ.............
 00000018d1bdd980 00 00 00 00 00 00 e0 43 00 00 00 00 00 00 00 00  ......àC........
 00000018d1bdd990 00 00 00 00 00 00 b0 40 00 00 00 00 00 00 00 00  ......°@........
 00000018d1bdd9a0 80 15 e9 1c 98 01 00 00 95 d7 c8 2c fd 7f 00 00  ..é.....•×È,ý...
Possible instruction pointers:

1 lib-wave-track-paint.dll + 0xd795
rsp = 0x00000018d1bdd9b0 rip = 0x00007ffd2cc8d795
Found by: stack scanning

Stack contents:
 00000018d1bdd9b0 60 da bd d1 18 00 00 00 0d 00 00 00 fd 7f 00 00  `Ú½Ñ........ý...
 00000018d1bdd9c0 52 f3 3a a5 a5 ef 00 00 00 00 00 00 00 00 00 00  Ró:¥¥ï..........
 00000018d1bdd9d0 00 10 00 00 00 00 00 00 e4 db c8 2c fd 7f 00 00  ........äÛÈ,ý...
Possible instruction pointers:

2 lib-wave-track-paint.dll + 0xdbe4
rsp = 0x00000018d1bdd9e0 rip = 0x00007ffd2cc8dbe4
Found by: stack scanning

Stack contents:
 00000018d1bdd9e0 00 00 00 00 00 00 00 00 80 00 00 00 00 00 00 00  ................
 00000018d1bdd9f0 00 00 e8 00 00 00 00 00 00 10 00 00 00 00 00 00  ..è.............
 00000018d1bdda00 40 da bd d1 18 00 00 00 d0 c3 63 14 98 01 00 00  @Ú½Ñ....ÐÃc.....
 00000018d1bdda10 00 00 e8 00 00 00 00 00 00 00 10 00 00 00 00 00  ..è.............
 00000018d1bdda20 00 f0 79 be 00 1c 92 3e 01 00 00 00 00 00 00 00  .ðy¾..’>........
 00000018d1bdda30 02 00 00 00 98 01 00 00 d8 75 ee 73 b7 06 00 00  ........Øuîs·...
 00000018d1bdda40 00 00 00 00 00 00 00 00 00 00 80 7f 00 00 80 ff  ...............ÿ
 00000018d1bdda50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 00000018d1bdda60 00 10 00 00 00 00 00 00 00 00 80 7f 00 00 80 ff  ...............ÿ
 00000018d1bdda70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 00000018d1bdda80 00 00 80 bf 00 00 00 00 00 00 00 00 00 00 00 00  ...¿............
 00000018d1bdda90 00 00 00 00 80 88 25 40 00 00 00 00 00 00 00 00  ......%@........
 00000018d1bddaa0 00 00 00 00 00 00 b0 40 00 00 00 00 00 00 00 00  ......°@........
 00000018d1bddab0 00 00 00 00 80 88 e5 40 00 00 00 00 00 00 00 00  ......å@........
 00000018d1bddac0 ff ff ff ff ff ff ff ff 90 dc bd d1 18 00 00 00  ÿÿÿÿÿÿÿÿ.ܽÑ....
 00000018d1bddad0 00 00 00 00 00 00 00 00 00 df bd d1 18 00 00 00  .........᫥....
 00000018d1bddae0 10 1c 0d 1f 98 01 00 00 a0 05 ce 1e 98 01 00 00  ........ .Î.....
 00000018d1bddaf0 00 b7 de 15 98 01 00 00 71 de bd d1 18 00 00 00  .·Þ.....qÞ½Ñ....
 00000018d1bddb00 e8 28 de 1c 98 01 00 00 f2 42 c8 2c fd 7f 00 00  è(Þ.....òBÈ,ý...
Possible instruction pointers:

3 lib-wave-track-paint.dll + 0x42f2
rsp = 0x00000018d1bddb10 rip = 0x00007ffd2cc842f2
Found by: stack scanning

Stack contents:
 00000018d1bddb10 00 b7 de 15 98 01 00 00 01 00 00 00 00 00 00 00  .·Þ.............
 00000018d1bddb20 a0 05 ce 1e 98 01 00 00 01 00 00 00 00 00 00 00   .Î.............
 00000018d1bddb30 00 00 00 00 80 88 25 40 00 00 e0 00 00 00 00 00  ......%@..à.....
 00000018d1bddb40 e0 04 e3 15 98 01 00 00 09 88 38 b0 fc 7f 00 00  à.ã.....	.8°ü...
Possible instruction pointers:

4 wxbase313u_vc_x64_custom.dll + 0x38809
rsp = 0x00000018d1bddb50 rip = 0x00007ffcb0388809
Found by: stack scanning

Stack contents:
 00000018d1bddb50 98 dc bd d1 18 00 00 00 2f f1 fe 49 fd 7f 00 00  .ܽÑ..../ñþIý...
Possible instruction pointers:

5 ucrtbase.dll + 0x2f12f
rsp = 0x00000018d1bddb60 rip = 0x00007ffd49fef12f
Found by: stack scanning

Stack contents:
 00000018d1bddb60 80 c3 63 14 98 01 00 00 90 25 5f 14 98 01 00 00  .Ãc......%_.....
 00000018d1bddb70 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 00000018d1bddb80 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
 00000018d1bddb90 00 00 00 00 80 88 e5 40 00 00 00 00 00 00 00 00  ......å@........
 00000018d1bddba0 f0 5d c1 15 98 01 00 00 00 00 00 00 00 00 00 00  ð]Á.............
 00000018d1bddbb0 10 1c 0d 1f 98 01 00 00 40 dd c3 15 98 01 00 00  ........@ÝÃ.....
 00000018d1bddbc0 80 dd bd d1 18 00 00 00 0d 97 c8 2c fd 7f 00 00  .ݽÑ.....—È,ý...
Possible instruction pointers:

6 lib-wave-track-paint.dll + 0x970d
rsp = 0x00000018d1bddbd0 rip = 0x00007ffd2cc8970d
Found by: stack scanning

Stack contents:
 00000018d1bddbd0 e8 28 de 1c 98 01 00 00 00 b7 de 15 98 01 00 00  è(Þ......·Þ.....
 00000018d1bddbe0 71 de bd d1 18 00 00 00 e0 04 e3 15 98 01 00 00  qÞ½Ñ....à.ã.....
 00000018d1bddbf0 60 dc bd d1 18 00 00 00 00 00 00 00 00 00 00 00  `ܽÑ............
 00000018d1bddc00 00 01 63 14 98 01 00 00 5d f7 3c b0 fc 7f 00 00  ..c.....]÷<°ü...
Possible instruction pointers:

Happened again. Almost through the end of one side of a vinyl record, running 3.6.1 Audacity on Windows 11. Audacity window disappears and I get the error window which cannot send the crash logs for some reason.

Audacity Crash 2024-08-03.txt (285.5 KB)

I think since Audacity 3.6.0, the logging system has long ago overloaded. 3.6.0 changed everything and everybody who touched 3.6.0 after using the older system generated errors. My personal experience was sweeping the broken Audiobook Mastering tools off the floor.

I wonder if your C:\ drive has enough room for a one-pass capture. And don’t point to your "D:\ " or higher cloud-linked or external drives. Audacity hates those. The show has to fit on C:\ or it doesn’t get done.

If you’re calculating file sizes in your head right now, know that Audacity uses super high-quality file format to avoid damage during editing, so it’s a lot worse than you think. If you got through a partial vinyl capture, I would use that as the rule and use two passes rather than one.

At the end of the first pass, Export the music as WAV (Microsoft) rather than trying to use Audacity Projects. Then move the work off the machine and out of the way. Do Not Make Audacity Directly Export to an External Drive!

See how that goes.

Koz

So, to emphasize, there are two problems here.

  1. If an error occurs, users cannot send error reports. That would make it difficult for the Audacity devs to see which errors are important and require attention.
  2. Midway through capturing a side of a vinyl record, the Audacity window just disappears. It’s not a storage problem. I have ~350GB of storage left on C:. It’s not a RAM problem. My laptop has 32GB running 64-bit Windows 11. And the error log is less than 300KB. The aup3 files I’ve been generating with 3.6.1 have been in the range of 750MB to 1GB.

I think you’re confusing this with normal software and a normal development cycle. 3.6 introduced massive changes and modifications and I’m betting didn’t massively increase the developer staff.

We can wait for one of the other helper elves to post.

Koz

I used to have a joke when someone would post about why the developers didn’t do this or that.

This is the Audacity Land’s End World Headquarters.


Koz

1 Like

I too have problems during recording of vinyl: 1) same crashes, 2) Audacity disappears, 3) same error report 4) no way to send crash report, 5) have >500GB spare drive (SSD), 6) went back to 3.5.1 w/no issues. 6) I am running Windows 10 Pro on an old Intel(R) Core™ i7-7820HQ CPU @ 2.90GHz 2.90 GHz, 32.0 GB (31.9 GB usable), 64 BIT that has been a powerhouse.

1 Like

This happens leaving it to record Heritage Chart when away to not move the mouse as well.

I would think that the smaller the dev team, the more important it would be to know which errors are causing the most problems so that fixing those could be prioritized over less-frequent errors that impact fewer users. Personally, if I was one of the Audacity devs, I’d work to fix the sending of errors before anything else, so that I wasn’t “flying blind” when I am deciding which errors are important and which ones are not.

But somebody has to read them. I think you underestimate the popularity of Audacity and the billions of complaints that would be generated during a stiff software update. In the old Audacity service, we would invite you to come help out. There is no “they.”
`

There is a new trick to fix inexplicable failures and crashes. Do Not Upgrade. Audacity updates keep your settings, preferences, adjustments, yadda, yadda, around from the old install so you don’t have to Fresh/New start over each time. Apparently, that can get you into trouble.

Use System Cleaning Software (or do it yourself if you know how) and burn off the existing Audacity install. All of it. Then install fresh from the accepted repository.

Koz

Newer Audacity versions can open older aup & _data projects and the newer aup3 projects.

Project Rules apply. An AUP and the _DATA folder of the same name have to be in the same location or folder for a show to open.

Newer Audacity versions will only make aup3 projects.

Koz

There is a section of the manual having to do with cleaning out the old Audacity.

https://manual.audacityteam.org/man/faq_installation_and_plug_ins.html#How_do_I_install_and_update_Audacity.3F

It’s part of the install segment.

Koz

At the moment I’m having to open Magix Audio Cleaning Lab as a backup because recording crashing on the black screen into flicky screen to turn it back on screensavers is so bad.

It is the highest priority for recording to be 100% foolproof on 8GB 3.60MHZ Dual Core i7 of power it shouldn’t have any problems on that power it’s only a few years out from the power of PC’s now.

Trying the portable Windows version of 3.6.1 now. Will report if it also has problems.

I ripped about 7 records using the portable version of Audacity since the last post, only to fail on an 8th record. Ran that record a 2nd and 3rd time and it worked. ?!?!? %@$#&!!!

Failures are intermittent. The Audacity app disappears and a Problem Report dialog box asks whether to send or not. Failures happen about 1 time out of 4 recordings.

Attaching the crash report and the dialog box that fails to send the crash report.
Crash reason - EXCEPTION_ACCESS_VIOLATION_READ - 2024-08-20.txt (289.3 KB)

Haven’t had any failures since 3.6.2… Recently upgraded to 3.6.3 and still no failures. Yay!