Could you please open a new bug report on this over at bugbase.adobe.com? Please include sample media, code, project or app to help us reproduce the problem. Did this occur on the desktop or mobile device? Finally, once the bug has been added would you mind posting back with the URL so that others affected can add their votes and comments?
Thanks a lot.
This issue is on a desktop application. I'm not confident I can provide reproducable code, but I will try. As I mentioned in the post, when I make simple AIR applications to try to reproduce this, then I'm able to run millions of transactions very quickly without any issue. It's only when inside a larger and busier application that this issue comes up.
I had a few more ideas to try after the refreshing weekend, none of which panned out; however, during these attempts and more investigations I finally found a pattern to the issue. Even though it doesn’t happen consistently, when it does happen it is fairly consistent on where it happens. There are 1 or 2 spots during the problematic processes that try to compact the DB after doing data clearing, in order to help keep the file sizes smaller. I think the issue here is compact wasn’t worked into the async flow properly. So while we are trying to compact the db, we are also trying to start up the new transaction. So if the compact takes a bit of time every once in a while, then we get a hang up. I think the assumed behavior was for async event handling to dispatch when the transaction is finally started instead of just never happening at all, but this does make some amount of sense.
With this in mind, I might be able to write a stand alone application to replicate this behavior, if you are still interested. However, I don't feel this is really a defect for Adobe. More of improper implementation on my part.