Tested this issue using #59.0.3071.115 on Win 10. and did not obsevre any errors in the Collect Errors page as per the steps mentioned in Comment #0.

@behindthemath: Could you please find the attched screen cast and let us know if we missed any steps from our end. If possible please add a expected screen cast for further triaging of the issue.

Thanks!!

Deleted: Jul 9 2017 11-15 PM.webm 2.8 MB

	Jul 9 2017 11-15 PM.webm 2.8 MB View Download

The "errors" dialog was always doing it. Sometimes it's useful, so a practical solution is to rename the label to "errors and messages".

@sandeepkumars, it appears from that screen cast that you're using Chrome Stable. This issue only occurs on dev builds (I was using Canary). This is because the issue is not with the standard console on the background page, but rather with the Collect Errors dialog that is launched by clicking the Errors link on the Extension page. This feature is only available in dev builds.

@woxxom, that's a good suggestion. I didn't realize this might have been by design. If yes, there should be some documentation about it. I was actually unable to find any documentation about this at all.

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Somehow, didn't observe the Collect Errors for the above extension attached on the chrome version: 61.0.3152.0.

Deleted: 740404.png 130 KB

	740404.png 130 KB View Download

@a... It looks from your screenshot that you're using Chromium Stable. As I mentioned in #4, I believe that the Collect Errors feature is only available in dev builds.

Able to reproduce this issue(as in attached screen shot) on Win-10 using chromium reported version #61.0.3152.0 and latest chromium version #61.0.3161.0.

This is a non-regression issue as it is observed from M58 old builds. 
Note: The extension doesn't get installed in builds older than M58.

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!

Deleted: console_error.JPG 145 KB

	console_error.JPG 145 KB View Download

@krajshree The reason it doesn't install in builds earlier than v58 is because I mistakenly put in the "minimum_chrome_version": "58" option in the manifest.
Here's a sample without it, that should work on all versions.

Deleted: Chrome bug test.zip 517 bytes

Chrome bug test.zip 517 bytes Download

@woxxom's https://bugs.chromium.org/p/chromium/issues/detail?id=740404#c2 is the correct explanation.

I'm going to rename this bug to consider renaming the dialog and checkbox label to point out that this refers to messages/logs and errors.

@behindthemath, your suggestion about documentation sounds good, where do you think in https://developer.chrome.com/extensions would be a good place to put this?

Two issues to summarize:
1. "Errors" dialog label is a bit misleading, it shows logs (console.log) beside any errors. Perhaps rename them to reflect that?: e.g. "Logs and errors". Similarly "Collect errors" checkbox label can be renamed.
2. We should document this somewhere in https://developer.chrome.com/extensions

Though I can guess it will be low priority to fix...

@lazyboy Thank you for the clarification.

How about putting a note on the Debugging Tutorial page (https://developer.chrome.com/extensions/tut_debugging) about this feature?
Something along the lines of, "To aid in debugging, you can use a dev build of Chrome, which has a Logs and Errors feature", with some more detail about how it works.

Should probably be fixed now. Refer  issue 837401 .