Worker makes Chrome crash when creating/deleting many editors

[dgaviola]

We have a single page application and we have to show several snippets of Javascript code in different editors. We create them when a popup is opened and we destroyed them when the popup is closed.

This works great when we don't use workers. When we enabled them, after opening and closing the popup a few times, Chrome crashes.

I created a snippet of code that demonstrate the issue:

http://embed.plnkr.co/BdAo3m0b5yfI2LvT5uX6/

If you click in the 'Recreate' button several times (around 15 times), Chrome will crash (I tested in different computers under Linux).

Obviously you need to run that example somewhere where you can run the worker as it doesn't work on Plunker due to the cross origin issue.

Maybe this is related to #331 but not sure.

[nightwing]

Destroying editor doesn't destroy the session, and chrome crashes after ~70 workers are created.
As a workaround you can call editor.session.$stopWorker() before editor destroy,
And i'll add session.destroy in the next version. It can cause problems if one destroys the editor before setting session to another editor, but current version causes more problems.
Also in long run we need to use one worker shared by all editors instead of one per session.

[nightwing]

Btw your example works fine in chromium nightly! Huray for getting rid of stupid cross origin restrictions!

[dgaviola]

Thanks nightwing! I will use that workaround.

[carlos-aguayo]

This would be great to have fixed.