martin189 - as I understand this, we have not been able to reproduce this internally. If we cannot reproduce it, then we cannot fix it (assuming “it” is something).
Sorry, we’d like to help you but you also have to help us to identify and isolate this. Perry asked a few questions and I don’t think you answered all of them so we might be at an impasse.
Earth to Corona Staff… Anyone there? Please answer 
Sorry about the radio silence. Your bug is on the list but isn’t being reported by anyone else so its priority is unfortunately low. I’ll see if I can find some time to look at it.
I’m seeing this error, but I can’t find where it’s listed as an official bug. Do you have a link so I can up-vote?
I tried to reproduce the problem with the code in the original post but could not see an issue after over 80 relaunches so there must be some subtlety to this that the example code doesn’t contain. Or maybe I “broke” it making the changes necessary to make it runnable. I was using build 2013.1241 on Windows 8.1
Can you report a bug to http://developer.coronalabs.com/content/bug-submission and include a complete sample app that demonstrates the problem? Please include as many details about your system as you can in case this is OS specific.
Also, does the problem occur if you just hit Ctrl+R repeatedly in the Simulator to manually relaunch the Simulator?
The issue essentially resolves itself after you close and open Corona. I had left my app running in the simulator on the desktop in the morning, and when I came back to it at night (12+ hours), I encountered this error. I closed and re-opened a new Corona session, and re-opened the same project with no changes to code. The error was gone after this.
It seems like examining my code would be useless as it doesn’t really matter the content. @Martin, are you running your code from a Dropbox/Google Drive/cloud storage service? Meaning, is your code stored in remote-synced storage medium and you run your projects from there? I think that may be where the issue arises.
Hi Just had a lok for this issue. I have noticed this a a few months but its starting to get really annoying now. What also happens is strange things start happen. Things stop working. It is connected to this audio already initialized bug as whenever things start going strange, i look on the console and see this error. I have to close simulator and start again about 30 times a day. I think it has been like tis since you added the code change=restart feature. I have just made a test by restarting (ctrl+r) 20 times and it didnt come up with the error but after, just by adding a “-” forcing it to error, it crashed and my display driver AMDkmap (or something similar named), froze my laptop and almost killed PC , I had to force close Corona. After a few tests of editing the code (just by removing some “--------------” which dont change any function, after 10 times , it did nothing,. I then edited some variable number and I noticed that it started to become unresponsive until longer and longer. After 2 code more code changes the simulator was not responding until 5 seconds. I then restart simulator, change the same bit of code and it restarts instantly. It seems there is a bottle neck of something building up on. simulator restarts. I have just done another test. I have no runtimes working and I have a alienspeeMs=200 . all i do is change this to something each time and after about 10 times, it starts to slow down on the simulator. IN fact it just killed my display driver again and almost crashed my PC. I tried this same thing. basically just redoing, undoing a minor code change and there it is the audioAlready initialized bug. Must be something to do with purging on restart
Can someone point me to the submitted bug? This needs to be bumped up. Its a messy simulator
@Panx software: No, my code is local.
@Corna Staff: It still exists in CoronaSDK-2013.1259.msi. Please fix.
Does shutting down all Corona instances and then starting once more not solve your problem? I find that normally fixes it for me, and while I do see the error every blue moon, it’s more of an annoyance than a showstopper.
Yes, it does. But I see this error every 5th or 6th time when I change any project files, not only code but also level maps or any other resource (graphics, audio). This bug makes the (very comfortable) auto reload feature useless for me.
That is a sticky wicket. I’ll report if I encounter the issue more frequently.
I’ll ask again …
Also, does the problem occur if you just hit Ctrl+R repeatedly in the Simulator to manually relaunch the Simulator?
And what version of Windows are you running?
Note that the two issues reported here are different. One is about reloading an app in the Simulator causing an audio issue, the other is about an app that, if left running for 12 or more hours, causes an audio issue. The fact that the same generic error message is printed doesn’t mean they are the same issue.
Actually there is exactly one issue here:
However after a dozens or so of reloads the following error occurs and the audio stops working (no sound at all):
We want to fix this bug but we need a reproducible case before we can do that. I have implemented the incomplete sample code in the first post and it does not trigger this behavior and the relatively few reports of the issue means that it must be something specific that is being done in certain Lua code that is triggering the issue. I have tried repeatedly to reproduce the problem using any of the sample apps that use the audio library but nothing I do triggers it. If I don’t know what causes the bug, I can’t fix it.
I hesitate to suggest the obvious, but if the automatic reload on file change feature is causing problems for you, just turn it off in the Preferences and you wont be any worse off than before the feature was added.
I have exact same issue after installing newest public release. It worked for few launches, now when it occurs (randomly) I have to restart simulator to make it work.
Thanks for your post, delwing. Unfortunately I don’t think this issue will be fixed in near future. It seems Corona has no interest in quality, but only in quantity (in the meaning of new features) 
Therefore I have decided months ago to cancel my Corona Pro membership.
martin189 - as I understand this, we have not been able to reproduce this internally. If we cannot reproduce it, then we cannot fix it (assuming “it” is something).
Sorry, we’d like to help you but you also have to help us to identify and isolate this. Perry asked a few questions and I don’t think you answered all of them so we might be at an impasse.
Hi Just had a lok for this issue. I have noticed this a a few months but its starting to get really annoying now. What also happens is strange things start happen. Things stop working. It is connected to this audio already initialized bug as whenever things start going strange, i look on the console and see this error. I have to close simulator and start again about 30 times a day. I think it has been like tis since you added the code change=restart feature. I have just made a test by restarting (ctrl+r) 20 times and it didnt come up with the error but after, just by adding a “-” forcing it to error, it crashed and my display driver AMDkmap (or something similar named), froze my laptop and almost killed PC , I had to force close Corona. After a few tests of editing the code (just by removing some “--------------” which dont change any function, after 10 times , it did nothing,. I then edited some variable number and I noticed that it started to become unresponsive until longer and longer. After 2 code more code changes the simulator was not responding until 5 seconds. I then restart simulator, change the same bit of code and it restarts instantly. It seems there is a bottle neck of something building up on. simulator restarts. I have just done another test. I have no runtimes working and I have a alienspeeMs=200 . all i do is change this to something each time and after about 10 times, it starts to slow down on the simulator. IN fact it just killed my display driver again and almost crashed my PC. I tried this same thing. basically just redoing, undoing a minor code change and there it is the audioAlready initialized bug. Must be something to do with purging on restart
Can someone point me to the submitted bug? This needs to be bumped up. Its a messy simulator