Worker does not work so well

Question

Hi everyone,
     I am trying to decrypt an encrypted video in my opne-source project SparrowPlayer(https://github.com/yatsen-yang/SparrowPlayer),and I found that decrypting the video may block the main thread for several seconds.It resulted in stopping renderring UI assets on the stage, which is unacceptable.So I think 'Worker' may do some help. I followed the example code of the online API about Worker(http://help.adobe.com/zh_CN/FlashPlatform/reference/actionscript/3/flash/system/Worker.htm l). I tested and it worked well.
     But I found that if I embed the BGWorker.swf in other class like com.xx.Test instead of in the document class, 'Worker' did not work so well.Sometimes main worker could not communicate with bgworker even that the state of bgworker is running.
The example code followed:
    private function handleBGWorkerStateChange(event:Event):void
          if (bgWorker.state == WorkerState.RUNNING)
                  _statusText.text = "Background worker started";
                 bgWorkerCommandChannel.send(["startCount", 100000000]);
    It happened sometime, not everytime. If main worker send a message after 1 second when listerning that the state of bgworker is running, the code works well
    So it confused me. Logically, if the state of bgworker is running, it should mean that main worker can communicate with bgworker, and it works well if you embed the bgworker swf in the document class.But if you embed the bgworker swf in other class, you will have problem sometime.
    Finally, I found a solution.I embed the bgworker swf in other class instead of in the document class, and when bgworker initializes succesfully, it send a message to main worker.Main worker communicates withe bgworker immediately if it  receives the message coming from bgworker.Now the problem is solved.
    I want to know why the state of Worker not reliable when I embed the bgworker swf in other class.Is it a bug of Worker?   
    thanks

Answer 1

We would need to debug it to definitively understand the problem.  I would recommend filing a bug with a simplified example that demonstrates the problem.  If you post the bug number here, I'll escalate it to the engineering team.
Also, have you tried multiple browsers?  We can always do that triage here, but it would be an interesting data point.