Console Stops Working

[KAZ Vorpal]

I'm developing a Chrome extension, and have run into a strange problem when trying to debug:

When I go to my extension in the settings and click Background Page to open the console for it, that console opens and functions correctly for a short time. 

But then the actual console part, where console.log output goes, stops working at all. If I try to type into the command line part of the console, it does not do completion suggestion, and when I hit enter the command goes away, but does not appear to be parsed or used in any way. It remains like this until I close the console and reopen it.

I can force this error any time I want, by hitting Reload (Ctrl+R) while the background console is already open. If I do this, the error occurs and persists until I close and reopen the console again.

I have a 300 line background.js file, not enormous and with little unconventional in it. I am working on this for a corporate client, so I can't really post code unobscured, so first I'm simply asking if this sounds like any known bug. I couldn't find anything on the 'net that sounds like it, but the obvious search strings (chrome console stops working|background extension console stops working) brings up a lot of completely different kinds of discussions that may be obscuring the results I need.

If it helps, the permissions for this extension are:

"permissions": [

"tabs",

"activeTab",

"<all_urls>", 

"cookies", 

"debugger", 

"webRequestBlocking", 

"webRequest"

]

[PhistucK]

I am not familiar with such an issue, but have you searched crbug.com for a similar issue (perhaps select "All issues" instead of only "Open issues", because it might have been fixed recently and might not show up as an open issue)?

If you cannot find one, you can file a new one. Unless you can reproduce this with a minimal test case (the minimal amount of code that is needed to reproduce this), you will need to provide your code (you can always change the words in the code in order to remove corporate references).

In order to debug this on your own, you can undock the Developer Tools feature and press Control + Shift + J, which opens a second Developer Tools instance that inspects the first Developer Tools instance ("devtools on devtools" :)). You can see whether there is an exception of some sort and perhaps it will be meaningful.

☆PhistucK

--
You received this message because you are subscribed to the Google Groups "Google Chrome Developer Tools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-chrome-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-chrome-developer-tools/6fb52bac-47fc-4375-ad76-0e5abebe3bae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.