Chrome Canary 35 freeze when Web Worker is closed with active IndexedDB transaction

[Deni Spasovski]

I've noticed this bug today, that Chrome freezes if you terminate web worker in which it has open transaction.
In my scenario I don't care about the transaction since it's read only and I close the worker before it's finished, however I currently disabled this feature since it was crashing Chrome.
Anyone with similar experience ? Do you use web workers in Chrome for IndexedDB ?

[Taylor Buley]

Can you set us up with a page where we can see this happen? I'm very curious 

--
You received this message because you are subscribed to the Google Groups "IndexedDB Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to indexeddb-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kyaw]

It will be great, you could setup a simple test case.

[Deni Spasovski]

I wasn't able to reproduce the issue, however the Chrome team released a patch that fixes it.
The problem was when IDB transaction was running in a worker which is terminated and when transaction completed the execution context was no longer available.

Here are details for the fix:
https://codereview.chromium.org/213073004