谷歌浏览器 - 崩溃转储位置 [英] Google Chrome - Crash Dump Location

问题描述

我试图在网页应用程序中调试页面，导致Chrome崩溃（Aw，snap！错误）。我已启用/禁用自动崩溃报告，尝试使用 google-chrome --enable-logging --v = 1 （以及各种级别的详细程度）进行日志记录，我得到的只是 chrome_debug.log chrome：// crashes 显示所有的转储ID，但没有实际的转储文件

我看到涉及读取转储文件，但我找不到转储文件本身（只是ID）。

在 / tmp 和〜 /.config/google-chrome/ 什么都没有，但〜/ .config / google-chrome / chrome_debug.log 显示 发送：

   -  2015-04-06 11：10：00-- https：/ /clients2.google.com/cr/report 
正在解析clients2.google.com（clients2.google.com）... 74.125.2 28.224,74.125.228.225,74.125.228.231，... 
连接到clients2.google.com（clients2.google.com）| 74.125.228.224 |：443 ...已连接。 
发送HTTP请求，等待响应... 200 OK 
长度：未指定[text / html] 
保存到：'/ dev / fd / 3'
 
 0K 
 Crash dump id：7dac9d5d58258264 
  

有关在何处找到实际文件/数据的任何想法这是发送？ b
$ b详细信息：
Chrome版本：40.0.2214.111（官方版本）
Linux Mint 16（Petra）

编辑：一些额外的信息：

  curtis @ localhost： -  $ tail -n 5 uploads.log& amp ;&安培; echo $（pwd）
 1428584493，ddc357e4600a49e6 
 1428584497,7ac16455c152381a 
 1428589439，d00ad6f5e6426f3d 
 1428934450,66b3f722430511e8 
 1428939578,7a2efc2b681515d1 
 / home / curtis /。 config / google-chrome /崩溃报告
 
 curtis @ localhost： -  $ ll -a 
 total 12 
 drwx ------ 2 curtis curtis 4096 Apr 6 11： 32。 
 drwx ------ 9 curtis curtis 4096 Apr 13 11:43 .. 
 -rw ------- 1 curtis curtis 3291 4月13日11:39 uploads.log 
  

自动生成报告 。 ..

谢谢！

解决方案

*。dmp 文件存储在 / tmp / 中，这与自动崩溃报告复选框无关。该文件与存储在〜/ .config / google-chrome /

中的哈希无关。

code>〜/ .config / google-chrome / Crash Reports / uploads.log ：

  1429189585,5bddea9f7433e3da 
  

通过使用，此特定报告的故障转储文件为：

  chromium-renderer-minidump-2113a256de381bce.dmp 
  

解决方案：

  root @ localhost： -  $ mkdir / tmp / misc&& chmod 777 / tmp / misc 
 root @ localhost： -  $ cd / tmp 
 root @ localhost： -  $ watch -n 1'find。 -mmin -1 -exec cp {} / tmp / misc / \;'
  

然后，一个普通用户（不是root用户）：

  google-chrome --enable-logging --v = 1 
  

一旦您看到由 watch 命令创建的文件，请运行：

  root @ localhost： -  $ ls -l 
 -rw ------- 1 root root 230432 Apr 16 09:06 chromium-renderer-minidump-2113a256de381bce.dmp 
 -rw ------- 1 root root 230264 Apr 16 09:12 chromium-renderer-minidump-95889ebac3d8ac81.dmp 
 -rw ------- 1 root root 231264 Apr 16 09:13 chromium-renderer-minidump-da0752adcba4e7ca.dmp 
 -rw ------- 1 root root 236246 Apr 16 09:12 chromium-upload -56dc27ccc3570a10 
 -rw ------- 1 root root 237247 Apr 16 09:13 chromium-upload-5cebb028232dd944 
  

现在您可以使用breakpad来处理 *。dmp 文件。

I'm trying to debug a page in a web app that keeps crashing Chrome ("Aw, snap!" error). I've enabled/disabled automatic crash reporting, tried logging with google-chrome --enable-logging --v=1, (as well as various levels of verbosity), and all I get is a "crash dump ID" in the chrome_debug.log chrome://crashes Shows all of the dump IDs, but no actual dump file

I see other questions referring to reading the dump files, but I can't find the dump files themselves (just the ID).

Grepping for the crash ID in /tmp and ~/.config/google-chrome/ turns up nothing, but the ~/.config/google-chrome/chrome_debug.log shows that something was sent:

--2015-04-06 11:10:00--  https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 74.125.228.224, 74.125.228.225, 74.125.228.231, ...
Connecting to clients2.google.com (clients2.google.com)|74.125.228.224|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/3’

     0K
 Crash dump id:  7dac9d5d58258264 

Any ideas on where to find the actual file/data that's sent?

Details: Chrome version: 40.0.2214.111 (Official Build) Linux Mint 16 (Petra)

Edit: Some extra info:

curtis@localhost:-$ tail -n 5 uploads.log && echo $(pwd)
1428584493,ddc357e4600a49e6
1428584497,7ac16455c152381a
1428589439,d00ad6f5e6426f3d
1428934450,66b3f722430511e8
1428939578,7a2efc2b681515d1
/home/curtis/.config/google-chrome/Crash Reports

curtis@localhost:-$ ll -a
total 12
drwx------ 2 curtis curtis 4096 Apr  6 11:32 .
drwx------ 9 curtis curtis 4096 Apr 13 11:43 ..
-rw------- 1 curtis curtis 3291 Apr 13 11:39 uploads.log

Automatic reporting is enabled...

Thanks!

解决方案

The *.dmp files are stored in /tmp/, and this has nothing to do with the "Automatic crash reporting" checkbox. The file is also not related to the hash stored in ~/.config/google-chrome/

In ~/.config/google-chrome/Crash Reports/uploads.log:

1429189585,5bddea9f7433e3da

From using , the crash dump file for this particular report was:

chromium-renderer-minidump-2113a256de381bce.dmp

Solution:

root@localhost:-$ mkdir /tmp/misc && chmod 777 /tmp/misc
root@localhost:-$ cd /tmp
root@localhost:-$ watch -n 1 'find . -mmin -1 -exec cp {} /tmp/misc/ \;'

Then, as a regular user (not root):

google-chrome --enable-logging --v=1

Once you see files created by the watch command, run:

root@localhost:-$ ls -l
-rw-------  1 root root 230432 Apr 16 09:06 chromium-renderer-minidump-2113a256de381bce.dmp
-rw-------  1 root root 230264 Apr 16 09:12 chromium-renderer-minidump-95889ebac3d8ac81.dmp
-rw-------  1 root root 231264 Apr 16 09:13 chromium-renderer-minidump-da0752adcba4e7ca.dmp
-rw-------  1 root root 236246 Apr 16 09:12 chromium-upload-56dc27ccc3570a10
-rw-------  1 root root 237247 Apr 16 09:13 chromium-upload-5cebb028232dd944

Now you can use breakpad to work on the *.dmp files.

这篇关于谷歌浏览器 - 崩溃转储位置的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！