I wrote this patch because I'm not 100% sure that we have a WorkerGlobalScope at any time we are playing with a WorkerDebuggerGlobalScope. If this is, we don't need all these security checks and we can use directory WorkerPrivate::GlobalScope().

Comment on attachment 8731626 [details] [diff] [review] console0.patch GetOrCreateGlobalScope gets the worker's global scope, or creates it if it doesn't yet exist (this can happen, because the worker is registered before it starts running, so the debugger can initialise before the worker itself). In other words, GetOrCreateGlobalScope can never return nullptr, so this patch is unnecessary.

Good. It means that we can use WorkerPrivate::GlobalScope() directly. New patch coming.

Hold on, GetOrCreateGlobalScope() can fail. This patch covers this scenario.

Huh. You're right! I don't know if this was originally not the case, or that we just forgot to check for it properly. In any case, we need to check against it, which is what your patch. Good catch!