2.1.1 Hangs and/or Crashes on Sound Activated Recording

Audacity Help Forum macOS
1

Tried for the first time this evening to use Sound Activated Recording on 2.1.1. Upon opening the recording track window by clicking on the red record button the window opens and seems ok for a few seconds then most of the time Audacity locks up and CPU is over 50% until I force kill it. Some times it will come with an error window saying it had created a debug file, but nothing is showing in the window for files collected and there is no debug file where it says it should be. It also just plain crashed a couple of times. I do have 3 different dumps - spin, hand and resource if you would like to see them.

I’ve tried on Yosemite and El Capitan with identical results. 2.1.0 works just fine with the same config file etc. and on both OS versions. Guess I’m back to using 2.1.0 though 2.1.1 seems to work fine for everything else.

Found the following messages in the Console at the time of or just a little later than one of the hangs/crashes. Some of the messages seem important, though maybe not directly related to this issue.

----------------------------------
8/30/15 9:38:04.943 PM Audacity[2770]: 21:38:04.942 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.

8/30/15 9:38:21.211 PM WindowServer[217]: disable_update_timeout: UI updates were forcibly disabled by application "Audacity" for over 1.00 seconds. Server has re-enabled them.

8/30/15 9:38:32.580 PM spindump[405]: Saved spin report for Audacity version 2.1.1.0 (2.1.1.0) to /Library/Logs/DiagnosticReports/Audacity_2015-08-30-213832_Cliffs-MacBook-Pro.spin

8/30/15 9:38:35.211 PM WindowServer[217]: disable_update_likely_unbalanced: UI updates still disabled by application "Audacity" after 15.00 seconds (server forcibly re-enabled them after 1.00 seconds). Likely an unbalanced disableUpdate call.

8/30/15 9:41:03.000 PM kernel[0]: process Audacity[2770] thread 78862 caught burning CPU! It used more than 50% CPU (Actual recent usage: 50%) over 180 seconds. thread lifetime cpu usage 90.007307 seconds, (7.910670 user, 82.096637 system) ledger info: balance: 90004257756 credit: 90004257756 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 178289583166 

8/30/15 10:09:16.697 PM Audacity[419]: objc[419]: Class TSSandboxPrefs is implemented in both /Library/Frameworks/TSLicense.framework/Versions/A/TSLicense and /Library/QuickTime/Flip4Mac WMV Import.component/Contents/MacOS/Flip4Mac WMV Import. One of the two will be used. Which one is undefined
-----------------------------

Let me know if you need more info.

Cliff

2

Thanks, Cliff. 2.1.2-alpha had a crash as you describe on Linux, though I could never reproduce that on Mac (or in 2.1.1).

What device are you recording from in Device Toolbar? Does it make any difference if you record from the built-in mic or your external devices?

If you don’t mind, it would be most useful if you could test Sound Activated Recording in 2.1.2-alpha (30Aug2015) where we think we have fixed the crash: http://www.audacity.homerow.net/index.php?dir=wx3%2Faudacity-nightly-2015.08.30-15.09-ce07211%2F. Try at different Sound Activation Levels including a low level like -60 dB.

I don’t get any crashes on Yosemite or Mavericks in latest 2.1.2-alpha using Sound Activated Recording with line-in or Soundflower recording.


Gale

3

I don’t see those messages in 2.1.2-alpha 30Aug15 (I do not have Flip4Mac so I would not see the message relating to that).

Please try running that 2.1.2-alpha version and looking at the console messages for that version.


Gale

4

What device are you recording from in Device Toolbar? Does it make any difference if you record from the built-in mic or your external devices?

Makes no difference which input is used.

I’ll give 2.1.2 Alpha a try and get back to you.

Cliff

5

Downloaded the 2.1.2 Alpha Zip file and it will not run. Tried on both Yosemite and El Capitan. It says an image is missing. I’ve attached the report.

Cliff
Aud212A.txt (2.08 KB)

6

Might you have got a bad download? Clear your download cache and try again, or try the DMG.

I build my own, but that download runs for me on Yosemite.


Gale

7

Bad download isn’t likely since the Zip opened without problems. How did you install it? I just had Finder unzip it and then dropped the Audacity folder on to Applications. I downloaded the Zip to save bandwidth since my Internet has a cap, but I suppose I could download the .dmg. I’ve used the Zip of other versions of Audacity without problems.

It starts up with the usual warning about being from an unknown developer then the error pops up.

Cliff

8

After extracting the ZIP into the Downloads folder I just double-clicked Audacity.app from the extracted folder.


Gale

9

Hi Gale,

Here’s ,more info.

Dyld Error Message:
Library not loaded: /usr/local/lib/libwx_osx_cocoau_release_adv-3.0.dylib
Referenced from: /Applications/Audacity 2.1.2 Alpha/Audacity.app/Contents/MacOS/Audacity
Reason: image not found

The above message was in the error report. Checking that location on my system I find no file by that name. I’m assuming that your system has that file in that location for some reason, but it isn’t there in either of my installations. El Capitan has no .dylib files in that directory where as Yosemite has some, but no libwx… files in that directory. Is the file included in the .dmg and not in the ZIP version? I noticed that the 2.1.2 Alpha had another directory named Frameworks that isn’t in the older versions that had a bunch of .dylib files in it, but not the one in question. Searching both OSs shows that that file does not exist on either of my systems.

I haven’t downloaded the .dmg yet as I wanted to verify exactly what the problem was. Now I suspect the .dmg wouldn’t work on my system as well do to the missing file.

Cliff

10

Yes I saw that error, but those libwx* files are I assume installed when wxWidgets is built and installed, which is prerequisite for building Audacity itself. You would not have those files as someone who does not build Audacity.

I get the same error as you if I trash that libwx_osx_cocoau_release_adv-3.0.dylib file then try to run my 2.1.2-alpha build. So perhaps something is not being built into Audacity that should be. On Windows the required wxWidgets DLL’s are included with Audacity.

I don’t know what is supposed to happen on Mac, so I asked Leland to look into it.

Thanks, Cliff.


Gale

11

Glad we tracked down the problem.

As an interim solution could you put that file somewhere I could get it so I can put it into that directory and hopefully 2.1.2A would run?

Cliff

12

Probably no point until Leland works out exactly what is missing. I might give you one file then another would be reported missing.

I’ll post when there is a fix.


Gale

13

Hi Cliff

Can you please try this one: http://www.audacity.homerow.net/index.php?dir=wx3%2Faudacity-nightly-2015.09.06-01.49-c86c262%2F ?


Gale

14

Gale,

The new version of 2.1.2A started just fine. Tried different levels of Sound Activated Recording without issues. From what I see all is ok. Is there anything else I could test for you?

BTW, I went to Add/Remove Plugins and disabled all because I had multiple ones and I wanted to get rid of the duplicates since I have 2.1.0, 2.1.1 and now 2.1.2 all available. At that point it locked up and I couldn’t do anything in Audacity. Almost all menu items were grayed out including Add/Remove Plugins. I had to Force Quit the program. Went to 2.1.1 and re-enabled the plugins I wanted and then 2.1.2A was ok. This happens everytime I try it. If I open 2.1.2A with no Effects enabled then the Add/Remove Plugins menu item is available and I can re-enable the plugins, however 2.1.2A still locks up after I click Enable and Ok and the Effects Menu shows no Effects. Force Quitting then restarting 2.1.2A then shows the Effects and all is ok. Seems like a problem somewhere. I tried disabling all then enabling one and it still hung though it showed all the effects grayed out in the Effects menu so maybe it has to have some certain ones enabled to run.

Another observation related to Audacity in general, not just 2.1.2A. The Tool Tips are nice, but could the display position of the text be moved to above the tip of the cursor? Where it is now the text is underneath the cursor and some of the text can not be read. I’ve got a fairly large cursor and it blocks out quit a bit of the text on the shorter ones. Putting it anywhere not under the cursor would be helpful.

Hope all this helps.

Cliff

15

Thanks very much for testing.

In 2.1.2-alpha on Yosemite, are you still getting prominent flashing of toolbars when you import files by any method, or when you save or export? Do you avoid crashes working with files? I understand the flickering may not occur on El Capitan in any case.

If you were to relax some of the precautions I think you take against crashes when you want to record, does 2.1.2-alpha crash? I know you would not want to risk important recordings but you could perhaps test by turning AppNap on again, leaving Audacity idle between recordings, letting the display sleep, or changing to another desktop while Audacity is running, then plug in your second monitor.

Note that we have not done anything to specifically address crashes or flickering. We have updated to wxWidgets 3.0.2 which we think could make Audacity more stable with the latest versions of OS X.

Thanks again. Quitting Audacity, deleting ~/Library/Application Support/audacity/pluginregistry.cfg then restarting Audacity is usually the most convenient way to remove duplicate plugins and start over again with the default shipped and enabled effects. But it seems even after deleting pluginregistry.cfg, I can’t add or remove any effects in that session without having to force quit.

So we’ll try to fix that.

Thanks. We know about that one: http://bugzilla.audacityteam.org/show_bug.cgi?id=171.


Gale

16

Thanks very much for testing.

You’re welcome. Trouble shooting is something I really enjoy whether it’s software or mechanical/electrical things.

In 2.1.2-alpha on Yosemite, are you still getting prominent flashing of toolbars when you import files by any method, or when you save or export? Do you avoid crashes working with files? I understand the flickering may not occur on El Capitan in any case.

If you were to relax some of the precautions I think you take against crashes when you want to record, does 2.1.2-alpha crash? I know you would not want to risk important recordings but you could perhaps test by turning AppNap on again, leaving Audacity idle between recordings, letting the display sleep, or changing to another desktop while Audacity is running, then plug in your second monitor.

Note that we have not done anything to specifically address crashes or flickering. We have updated to wxWidgets 3.0.2 which we think could make Audacity more stable with the latest versions of OS X.

Haven’t tried the new 2.1.2 on Yosemite yet. Will do.

Flickering indeed is non-existant on El Capitan. Will check on Yosemite.

I’ve relaxed all the precautions on recording on El Capitan running 2.1.1 without problems. Even moving the Record Buffer back to 100ms from 15ms. I’ll see what happens on Yosemite.

Thanks again. Quitting Audacity, deleting ~/Library/Application Support/audacity/pluginregistry.cfg then restarting Audacity is usually the most convenient way to remove duplicate plugins and start over again with the default shipped and enabled effects. But it seems even after deleting pluginregistry.cfg, I can’t add or remove any effects in that session without having to force quit.

So we’ll try to fix that.

Glad you were able to duplicate it. It seems as so often issues I see in software others have a hard time duplicating so they’re hard to fix.

Glad also that you know about the Tool Tips. Not a major issue, but would just make it nicer.

I’m curious, what the thinking is for the change in font size on the track window and the Project Rate and Snap To lists. Will those be user adjustable? For me personally I prefer the way they are in 2.1.1. 2.1.2 Track Window time line seems gaudy being so big and the Project Rate and Snap To lists are now micro size, at least on my 15" MBP.

Cliff

17

I’m pretty sure it’s unintentional and due to the move to wxWidgets 3.

So I’ll be raising the text size disparities as an accessibility issue.

Gale

18

So I’ll be raising the text size disparities as an accessibility issue.

Sounds good.

Just and update on 2.1.2 testing.

  • Just verified that the Add/remove plugins locks up regardless of how many plugins are already enabled. I did as you suggested and removed the plugins.cfg and it generated a new list, but some were not enabled so enabled some of them and exited the dialog and it locks up. Restarted and finished the enabling of the rest of the plugins and again it locks up.

  • So far no crashes or hic-ups on Yosemite. Letting it sit so far does not cause a crash or sitting then plugging in my second monitor is ok so far also.

  • So far no flashing on saving a project. I haven’t had a need to do any importing yet so haven’t tried that. But so far it looks like the new wxWidgets seems to have solved some issues on Yosemite. It would be interesting to know what changed in El Capitan that the issues seemed to go away even with using the older wxWidgets.

BTW, App Nap is allowed and putting the display to sleep with App Nap allowed doesn’t seem to mess up the recording and it did with 2.1.0 on Yosemite.

I still need to do more testing, but wanted to give an update anyway.

Cliff

19

I think Leland fixed the plugins problem - Leland does not have a build up but try mine:
http://gaclrecords.org.uk/test-builds/audacity-macosx-r5f985a2-2.1.2-alpha.zip.

If you don’t mind, try opening other dialogues too and see if the project window is still usable after you close the dialogue.

The plugins.cfg file is for older versions of Audacity - I guess you deleted pluginregistry.cfg though if it had the intended effect.

Thanks, Cliff. Doing a recording, opening a new window, doing a new recording in that new window then saving or exporting would be a good test. Some users have a lot of crashes with that or variations thereon.


Gale

20

Opps, yes I deleted the plugingregistry.cfg. Did it again with your build and it comes up just fine and I can work with the dialog and make changes as normal. I’m not sure what you were referring to opening other dialog windows as a test. I don’t see any other ones other than the plugin dialog that can be opened from several menu items. That all works fine. That was a quick fix. :slight_smile:

In the process of editing a recording last night I noticed another issue.

You can reproduce it by having a recording displayed in the track display. Then click somewhere on the recording with the cursor and notice that you can move the cursor with the arrow keys. Then either zoom in or out using the zoom tools from the tool bar. Now try to move the cursor with the arrow keys. You’ll find the cursor will not move anymore. Click somewhere else and now the arrow keys work. Do another zoom and you’ll find the arrow keys unresponsive again. This is on both 2.1.2A versions.


A question regarding Tool Tips. I notice that all, but the recording and playback tool tips don’t work on 2.1.2 Alpha. Is this planned? Also when hovering over the recording/playback slider when the Tool Tip comes up the focus in Audacity changes so the color goes away in the drop down buttons for things like “Input Source” and the like and the yellow box around the selected track display goes away. You may not have any control over that, but it seems like a whole lot more processing going on that would be necessary just to put up the Tool Tip.

Would you rather use another means to report suspected bugs than this forum thread? I was just thinking the topic is kind of changing.

Cliff