debug.log file is being created in a few Windows folders (possibly from Chrome). How can I troubleshoot and...
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.
google-chrome logging
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
|
show 1 more comment
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.
google-chrome logging
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
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
Aug 15 '17 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
Aug 15 '17 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
Aug 16 '17 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
Aug 16 '17 at 10:45
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36
|
show 1 more comment
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.
google-chrome logging
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
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.
google-chrome logging
google-chrome logging
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
asked Aug 15 '17 at 17:31
cag8fcag8f
1197
1197
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
Aug 15 '17 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
Aug 15 '17 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
Aug 16 '17 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
Aug 16 '17 at 10:45
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36
|
show 1 more comment
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
Aug 15 '17 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
Aug 15 '17 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
Aug 16 '17 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
Aug 16 '17 at 10:45
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36
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
Aug 15 '17 at 17:38
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
Aug 15 '17 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
Aug 15 '17 at 18:15
We went through a bout of this in our organization. It was Chrome. Subsequent updates to Chrome eventually solved the issue.
– Appleoddity
Aug 15 '17 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
Aug 16 '17 at 10:45
@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
Aug 16 '17 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
Aug 16 '17 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
Aug 16 '17 at 10:45
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36
|
show 1 more comment
2 Answers
2
active
oldest
votes
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.
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
add a comment |
I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:
- Stop Chrome
- Delete the directory %AppData%LocalGoogleChromeUser DataCrashpad and all its contents
- 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.
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1241154%2fdebug-log-file-is-being-created-in-a-few-windows-folders-possibly-from-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
add a comment |
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.
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
add a comment |
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.
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
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.
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
answered Sep 15 '17 at 12:48
cag8fcag8f
1197
1197
add a comment |
add a comment |
I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:
- Stop Chrome
- Delete the directory %AppData%LocalGoogleChromeUser DataCrashpad and all its contents
- 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.
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
add a comment |
I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:
- Stop Chrome
- Delete the directory %AppData%LocalGoogleChromeUser DataCrashpad and all its contents
- 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.
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
add a comment |
I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:
- Stop Chrome
- Delete the directory %AppData%LocalGoogleChromeUser DataCrashpad and all its contents
- 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.
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
I just experienced this for a few days and it drove me mad... so what fixed it for me was the following:
- Stop Chrome
- Delete the directory %AppData%LocalGoogleChromeUser DataCrashpad and all its contents
- 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.
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
answered Jan 25 at 22:24
Gerhard PoulGerhard Poul
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1241154%2fdebug-log-file-is-being-created-in-a-few-windows-folders-possibly-from-chrome%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
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
Aug 15 '17 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
Aug 15 '17 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
Aug 16 '17 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
Aug 16 '17 at 10:45
Have you tried deleting your user profile so chrome behaves like it's suppose to?
– Ramhound
Aug 16 '17 at 11:36