Chromium crashes when using certain extensions

[Peter Wang]

When using certain extensions starting with Chromium 29, Chromium crashes and gives the following error (or something similar):

44:44:1006/011329:FATAL:console.cc(62)] Check failed: false. (CONTENT_SCRIPT context for cellaaeoekimmemgdheibaibbaoeefbl) extensions::lastError:46: Uncaught TypeError: Cannot convert undefined or null to object{TypeError: Cannot convert undefined or null to object
    at Object.clear (extensions::lastError:46:24)
    at extensions::sendRequest:80:64
    at Array.forEach (native)
    at Function.target.(anonymous function) (extensions::SafeBuiltins:19:14)
    at handleResponse (extensions::sendRequest:80:12)}

I've tried using Google Chrome Dev Channel and Google Chrome Beta with the same extensions, but those are error-free.

[Saikrishna Arcot (saiarcot895)]

My guess it that it's something in 4-chromeless-window-launch-option that is causing the crash, since we're messing with extensions there.

[Chad Miller (cmiller)]

Installing a 4chan-browsing extension to test. Ick.

[Peter Wang (blinxwang)]

Now I just feel guilty.

if it's any consolation the PDF-JS extension crashed with the same error too, as well as XKit.

[Chad Miller (cmiller)]

Hah, I'm just messing with you, Peter.

A little more context:

[30549:30549:1009/155148:INFO:CONSOLE(0)] "chrome.extension is not available: 'extension' is not allowed for specified context type content script, extension page, web page, etc.).", source: http://boards.4chan.org/s/ (0)

[18:18:1009/155148:WARNING:console.cc(163)] Could not log "(CONTENT_SCRIPT context for cellaaeoekimmemgdheibaibbaoeefbl) lastError:48: Uncaught TypeError: Cannot convert undefined or null to object{TypeError: Cannot convert undefined or null to object
    at Object.clear (lastError:48:24)
    at sendRequest:80:64
    at Array.forEach (native)
    at Function.target.(anonymous function) (extensions::SafeBuiltins:19:14)
    at handleResponse (sendRequest:80:12)}": no context given

[Saikrishna Arcot (saiarcot895)]

This is going back to bug #1232575.

Also, for PDF-JS, I think it's been reported upstream as part of a slightly different error (https://code.google.com/p/chromium/issues/detail?id=270060).

[Saikrishna Arcot (saiarcot895)]

I can confirm this bug is caused by the 4-chromeless-window-launch-option patch. Now the hard part is figuring out why the bug occurs.

I'm guessing the root cause of this bug is the same as that of bug #1232575. Once I can get an example extension from there, should this be marked as a duplicate of that bug?