New issue
Advanced search Search tips

Issue 709207 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Log-Analyzer Results

Reported by nhix...@fortsmithschools.org, Apr 6 2017

Issue description

Chrome Version       : 
--------------------------------------------------------------------------
Google Chrome:	56.0.2924.110 (Official Build) (64-bit)
Revision:	0
Platform:	9000.91.0 (Official Build) stable-channel candy
JavaScript:	V8 5.6.326.55
Flash:	        24.0.0.221
                /opt/google/chrome/pepper/libpepflashplayer.so
User Agent:	Mozilla/5.0 (X11; CrOS x86_64 9000.91.0) 
                AppleWebKit/537.36 (KHTML, like Gecko) 
                Chrome/56.0.2924.110 
                Safari/537.36
--------------------------------------------------------------------------
URLs (if applicable):  N/A
--------------------------------------------------------------------------
Other browsers tested: N/A
  Add OK or FAIL, along with the version, after other browsers where you
  have tested this issue:
     Safari:  N/A
    Firefox:  N/A
         IE:  N/A
--------------------------------------------------------------------------
What steps will reproduce the problem?
(1) Randomly occurs  

What is the expected result?

These problems seem to happen in the background.  I don't really notice them.  I'm reporting because once I ran Google's Log Analyzer, it told me to report the issue

What happens instead?


Please provide any additional information below. Attach a screenshot if
possible.

Just out of curiosity I typed in chrome://net-internals and ran the Chrome OS debugger to gather logs to analyze.  Once I ran the analyzer I noticed a message stating "This always constitutes a coding error. Please report a bug!" for the following observation:  NOTREACHED() ui.20170406-184627(1).  It also displays:  Hardware Write Protection may be off debug_vboot_noisy.log(1) bios_info.txt(2) "contact support to know what to do"

 
debug-logs_20170406-151325.tgz
112 KB Download
Labels: Needs-Milestone OS-Chrome
As per the original comment confirming this is chrome OS issue, adding appropriate label for further triage.

Thanks!
Components: Internals>Logging
Project Member

Comment 3 by sheriffbot@chromium.org, Nov 5

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment