OS X 10.4.11 crash

[Leland]

I tried running it from the desktop because I've seen some applications have problems if they're too deep in the directory tree - but it seemed to make no difference. Like just now I tried with all the plugins installed, and got the same symptoms. I rebooted the Mac, ran that latest build of Audacity 1.3.10 before I launched any other apps... hang. I did not get a trace in the console logs the last 3-4 times I launched Audacity, either. It shows "not responding" in the Activity Monitor.

Sorry... there must be something I'm not doing. I installed 1.2.4 again, and it runs fine. Checking to see if maybe something wasn't getting created by 1.3.x when it ran, I switched to 1.3.10 again, and it still hangs. I'll keep trying to work out a set of conditions that allows it to run and let you know if I get something to work...

Can you tell us what plugins you have in /Library/Audio/Plug-Ins/VST and ~/Library/Audio/Plug-Ins/VST? I'll see if I can reproduce the issue here on my studly G5 dualie.

Also, if you're willing, I've uploaded a Debug build of the .app to http://www.homerow.net/audacity/Audacity-Debug.zip. If you can reproduce the crash with it, then the console log will be much more helpful.

Thanks,

Leland

[BobDobbs]

That's funny - the official name of my machine is "My studly DP G5".

I'll post my list of plugins when I get home, but honestly it hung even with no plugs installed. I'll dl the debug version and see what I can come up with.

Oh, and I can't get the 1.3.7 download to complete; maybe I was using a bad URL? I just edited the 1.3.9 URL from the official links page to "1.3.7" but it aborted part way through and seems not to work now.

[Leland]

That's funny - the official name of my machine is "My studly DP G5".

That's where I got it from. On the devel list, we thought it was about the best hostname we've seen.

Leland

[BobDobbs]

Heh. Of course, it was in my log. I like to tweak the handful of my friends with Windows boxes.

That debug version must be for Intel? It won't launch on my machine.

I have found that 1.3.5 launches and runs fine - with the plugins installed. Replacing the application or the whole folder with 1.3.7 or above (can't find a copy of 1.3.6) causes the hang. And I'm not getting anything in Audacity.crash.log or crashreporter.log now. I've been removing preferences and plugin.cfg files after every successful launch, to avoid confusing the next test.

Should I try 1.3.7 with all the plugins removed, or try another path?

[Leland]

That debug version must be for Intel? It won't launch on my machine.

DOH!!! Sorry about that. I forgot the debug configurations on build one platform. I can rebuild it when I get home.

Should I try 1.3.7 with all the plugins removed, or try another path?

If you could, that would be great. That will prove that we're dealing with something entirely different. What sort of audio devices do you have attached? Anything like Jack or Soundflower or any system-wide audio processing applications?

I know you've probably been doing this already, but can you be certain that the following get deleted before trying?

"~/Library/Preferences/audacity Preferences"
"~/Library/Application Support/audacity" <--- The entire folder

Thanks,

Leland

[kozikowski]

That's very interesting. 1.3.7 did not do all the crazy plug-in management, so it's clearly something else.

Are you doing all this on one (1) machine? Did you buy and put the memory sticks in this machine? Have you run a memory checker?

http://www.memtestosx.org/joomla/index.php

As I recall when I last did this, you log in in single user mode and run it as a text application. It catches something like 95% of the memory when you do that. Run it multiple times.

Koz

[BobDobbs]

Should I try 1.3.7 with all the plugins removed, or try another path?

If you could, that would be great. That will prove that we're dealing with something entirely different. What sort of audio devices do you have attached? Anything like Jack or Soundflower or any system-wide audio processing applications?

No, the only things that I think might have some interference are Magic Menu and Little Snitch. I've already tried disabling Default Folder X with no differences.

Running through them again without any plugins, in any of the searchable directories, gives the same result: anything newer than 1.3.5 hangs.

I know you've probably been doing this already, but can you be certain that the following get deleted before trying?

"~/Library/Preferences/audacity Preferences"
"~/Library/Application Support/audacity" <--- The entire folder

Thanks,

Leland

Yes, confirmed.

[BobDobbs]

That's very interesting. 1.3.7 did not do all the crazy plug-in management, so it's clearly something else.

Are you doing all this on one (1) machine? Did you buy and put the memory sticks in this machine? Have you run a memory checker?

Yes, yes, and not lately. I'll do that while I'm away tomorrow - won't be using the machine all day anyway.

[Leland]

That debug version must be for Intel? It won't launch on my machine.

Universal debug version uploaded now:

http://homerow.net/audacity/Audacity-Debug.zip

It may not tell us anything since you're not crashing, but with a debug build, several assertions are active that may help us out. Also, when you hang and "Force Quit", does it not still pop up a dialog asking if you wish to report the issue?

Leland

[BobDobbs]

Not much difference; it did pass through the sections where it discerned the capture and playback rates, but that's all I saw in any of the logs. Here's the last of the trace:

Code: Select all

[Debug] 21:01:48: Getting supported capture rates for device 0
[Debug] 21:01:48: Rate 8000 Hz is supported
[Debug] 21:01:48: Rate 9600 Hz is supported
[Debug] 21:01:48: Rate 11025 Hz is supported
[Debug] 21:01:48: Rate 12000 Hz is supported
[Debug] 21:01:48: Rate 15000 Hz is supported
[Debug] 21:01:48: Rate 16000 Hz is supported
[Debug] 21:01:48: Rate 22050 Hz is supported
[Debug] 21:01:48: Rate 24000 Hz is supported
[Debug] 21:01:48: Rate 32000 Hz is supported
[Debug] 21:01:48: Rate 44100 Hz is supported
[Debug] 21:01:48: Rate 48000 Hz is supported
[Debug] 21:01:48: Rate 88200 Hz is supported
[Debug] 21:01:48: Rate 96000 Hz is supported
[Debug] 21:01:48: Rate 192000 Hz is supported
[Debug] 21:01:51: DirManager: Created new instance

This is still with no plugins in any of the library paths.

And no, I didn't get any dialog about reporting the crash...