Robert Small, The blog thereof.

I believe the following two URL’s are exactly the same bug as I’ve experienced.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/121413
https://lists.ubuntu.com/archives/ubuntu-mozillateam-bugs/2007-June/016597.html

Symptoms: Eclipse completely dies on you when you open a web browser or one is opened for you. It also happens if you go to the web browser settings page.

Failed possible solutions: Recompiling everything. It looked like a weird linking problem to me so I went for the traditional response, recompile. This wasted a lot of CPU time but gained me nothing.

Solution: Surprisingly I’ve yet to see this anywhere else on the Internet. The problem seems to be somewhere within the ~/.mozilla/eclipse/ directory, if you remove it completely then it’s replaced and everything starts working fine again. I haven’t gone deeper into it to find out what’s actually causing this or if there’s a better solution. However, I don’t think I missed anything in that directory and Eclipse is working perfectly again.

Conclusion

I know this set me back a few hours in work figuring it out, I know that there are a lot of Eclipse developers out there who may benefit from this as well.

This must be quite a complex bug as nobody on IRC seemed to know what to do. Hopefully this guide will help other people with problems.

Comments welcome.

Kind regards, Robert.

It would logically follow that if I’ve had this problem others must also have had it or be having it on a regular basis now. Unfortunately I don’t know how to trigger the problem and so I’m unable to provide you with a picture.

Versions: Caught in 1.3.4 and 1.3.5, haven’t tested anything else.

Symptoms: CPU usage climbs to 100% and when you click ‘export’ or ’save as’ you get a standard export/save dialog box but without a path or any files/directories shown. It refuses to let you search or manually input a path.

Possible related problem: I had this problem last immediately after the same project had got stuck while loading the audio into the memory. The issues might be related but I can’t see any reason to suspect that myself.

Solution: It’s not that hard but it took me a little while to work it out. Make a small edit and save, this seems to work every time. If it doesn’t then save and restart Audacity.

What doesn’t work: I tried all the normal tricks.

• # killall audacity
• # killall -9 audacity
• Moving the files around
• Renaming them
• Manually comparing the .aup with other .aup’s and trying to fix.

Diagnosis: Bug, probably a stomach one. I honestly can’t see where the problem is, I’ve tried looking for it but don’t have the time to do full strace’s and all the rest of that fun stuff. Let’s hope the audacity team manage to find it and fix it. After all, Audacity is a brilliant tool even if it does lack a few things.

Kind regards, Robert.