7

A few weeks ago I noticed a file named debug.log begin to appear in a few Windows folders (Win 10, x64). Does anyone know if it is due to Google Chrome, and/or how to resolve? The only reason I ask is because of this previous post in the Chrome Help Forum.

The contents of the file are log entries of this form:

[0810/181603.876:ERROR:crash_report_database_win.cc(427)] unexpected header
[0810/182501.651:ERROR:crash_report_database_win.cc(427)] unexpected header
[0810/192930.630:ERROR:crash_report_database_win.cc(427)] unexpected header

Right now I cannot seem to reproduce the issue, so troubleshooting is a bit difficult. One such log file is in my folder D:\temp, and a few new entries get logged to that file every day. If I delete it, the file returns within a day.

I posted to the Chrome Help Forum, but didn't receive many replies. Someone began walking me through how to check if my Chrome had debugging enabled, but that person stopped replying.

WordPress saves its PHP log to a file named 'debug.log,' and I am a WordPress developer. But I don't develop locally, so this file shouldn't really appear locally. Plus the contents of this log file aren't even close to the typical contents/form of the WordPress log.

Thanks.

Improve this question
8
  • Which folders specifically? Chrome only has the ability to write to the user profile directory and it's installation directory. Any file outside of those two folders wouldn't have been created by Chrome since it doesn't have the ability to do so.
    – Ramhound
    Commented Aug 15, 2017 at 17:38
  • We went through a bout of this in our organization. It was Chrome. Subsequent updates to Chrome eventually solved the issue.
    – Appleoddity
    Commented Aug 15, 2017 at 18:15
  • @Ramhound, one of the folders is D:\temp. That is not a default user profile directory. BUT a couple months ago I did re-assign it is one--it is my default 'Pictures' directory.
    – cag8f
    Commented Aug 16, 2017 at 10:45
  • @Appleoddity I was hoping Chrome updates would do the trick as well. On 31 July, I updated Chrome from v.59.0 to v.60.0. But the log files kept appearing.
    – cag8f
    Commented Aug 16, 2017 at 10:45
  • Have you tried deleting your user profile so chrome behaves like it's suppose to?
    – Ramhound
    Commented Aug 16, 2017 at 11:36

4 Answers 4

Reset to default
5

I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:

  1. Stop Chrome
  2. Delete the directory %AppData%\Local\Google\Chrome\User Data\Crashpad and all its contents
  3. Restart chrome

Due to the fact that this happened to me when opening PDF files in Chrome I thought the error was related to a header in the PDF, but my current theory is that this is actually the crash report database that might have become corrupt; I have already deleted mine, but there seems to be a utility for the crashpad database. Maybe next time.

Improve this answer
1

I have an update, with the eventual workaround I implemented.

I tried to uninstall Chrome, then re-install. But doing so via Control Panel resulted in an error--it could not locate the installer file (sorry, no screenshots). I then followed the instructions in this Google Product Forum post, and was able to re-install Chrome. Initial tests indicate that the issue is gone. At least, I can no longer re-create the issue as I before.

Improve this answer
1

I have faced a similar problem and found what is created it but not sure why.

I have set the latest Microsoft Edge web browser as my default PDF viewer. When I'm opening PDF files, the Edge browser (randomly) creates a debug.log file in the same folder as the PDF file. The contents of this file is often as following:

[1011/085129.427:ERROR:settings.cc(430)] Settings version is not 5

Not sure why these files are being created.

Improve this answer
0

I recently had the same problem, and found a simple way to fix this:

I uninstalled Chrome (making sure I had an installer on standby). When you uninstall Chrome, you get the option to remove your history as well. You should check this option.

After uninstalling Chrome, I reinstalled it and the debug.log file didn't show up again.

Remember that doing so will be the same as installing Chrome for the first time, so you need to restore your bookmarks and log in to your favorite websites again.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .