Audacity Forum

No, sorry, it's not different with today's version, really stupid. This is how it looks:

Thanks for trying it out, george13.

This time I was able to replicate the bug on my intel mac. I was testing in debug build before, and the version you (and the rest of the world) will use is release. A classic mistake that should be done at least once a year. I fixed it on my intel mac and checked the fix in. However, I am not positive and would like verification, as the bug was caused as a race condition. Can you please check it on tomorrow's build?

Hi,

This is good news that you also get the bug now . I will try tomorrow, thanks for your efforts.

Hmm, I tried the newest version today (http://www.audacity.homerow.net/index.p ... 6-03.15%2F) with some files and it's still the same.

I tried it out on intel and g4 and it worked using that link. I have no idea what is causing on your machine, so now I'm going to have to get into paranoid remote debugging mode. If you've been using firefox, can you try quitting it when you run Audacity? Can you also verify that the build date is current?

I'll try to think of a way to replicate the bug, because without that, I can't really do anything. If you think of something in the meantime, let me know. Thanks for looking at it.

Hi,
I tested this version with my fresh installation of OS X, no other programs running, and it's still the same: Maybe you can see where this happens in the source?

<<<I'll try to think of a way to replicate the bug, because without that, I can't really do anything. >>>

Without that, it's not a bug.

A bug is an unintentional, usually evil, performance of a program reproducible at will by many different people. Miss any of those conditions and it's just a machine being wacky.

Koz

kozikowski wrote:Without that, it's not a bug.

A bug is an unintentional, usually evil, performance of a program reproducible at will by many different people. Miss any of those conditions and it's just a machine being wacky.

No, it's still a bug, just one that I couldn't produce on two of my machines. This is a bug caused by race conditions in asynchronous behavior, which means that it is a bug that will affect a certain class of computers that run with a certain speed/have a certain amount of disk usage/etc.

I was able to reproduce it on my third machine, and I fixed it. Please george13, bear with me just a little more and try it again with tonight's build. It will drive me crazy till I know I've fixed it.

Hi mchinen,

Now it is working for me! Thank you very much! (must have been a reelly nasty bug).

hey mchinen, well done - a gold star for persistence and tenacity.

WC