Lee JeongHo

Is there any chance to merge the patch about setTimeout on above or the other plan for this issue?

In this case, the screenshot is useless. there are no exception or error throws for this. following is the information about reproduced environment. UA: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0;...

seems like worker is forked with empty script.   

> Can you console log https://github.com/webpack-contrib/worker-loader/blob/master/src/runtime/inline.js#L23 `content` and `blob` and show me it here? Are you sure L23 is the place what you want to put logpoint? (Blob is supported...

It's not. BlobBuilder won't used. https://github.com/webpack-contrib/worker-loader/blob/master/src/runtime/inline.js#L14-L25 is never reached because globalScope.Blob is available.  and Blob data is not broken either as you can see. 

I've already attached. see the last line of logs.  - blob generation is broken: No. It's working If I commented out revokeObjectURL or give some delay using setTimeout. -...

https://github.com/webpack-contrib/worker-loader/blob/master/src/runtime/inline.js#L35 ~~Replacing that line with `globalScope.setImmediate(URL.revokeObjectURL, objectURL);` works.~~ ~~oops, no. Above approach throws an error on safari. I'll try another way.~~ It works now. ```ts if (globalScope.setImmediate) { globalScope.setImmediate(URL.revokeObjectURL, objectURL);...

Okay. I accepted CLA.

Good. Thanks for your efforts.

I've found a minor glitch for this approach. https://github.com/webpack-contrib/worker-loader/issues/292#issuecomment-839061164