如何在Google Chrome中调试标签页崩溃 [英] How do I debug a tab crash in Google Chrome

查看:275
本文介绍了如何在Google Chrome中调试标签页崩溃的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个单页应用程序随机崩溃整个浏览器标签页。我观察到内存超过一个小时,但它不增加,一切看起来很好。



我在

中寻找一个崩溃转储

  C:\Users\cburgdorf\AppData\Local\Google\CrashReports 

但Chrome-last.dmp完全过时。是否有任何地方可以查找有关崩溃的其他信息?



我不知道我是否可以启动Chrome with windbg attach并等待(大约2小时左右) )为标签崩溃。



所有人都给出了很好的答案,并提供了有价值的建议。最后,我能够重现错误,并使用以下步骤获得明确的崩溃转储:

  1。)windbg。 exe -o chrome.exe 
2.)再生崩溃
3.).dump / ma C:\Path\To\A\CrashDump\File.dmp(正如Paul指出的)
4.)结束会话并使用windbg
加载崩溃dum 5.)使用!analyze -v提取有价值的信息


解决方案

一旦WinDbg插入,使用此命令创建一个完整的崩溃转储:

  .dump / ma C:\Path\To\A\CrashDump\File.dmp 


We have a single page application that randomly crashes the whole browser tab. I observed the memory for more than an hour but it wasn't increasing and everything looks just fine. Than out of a sudden after some more time passes, the tab crashes.

I looked for a crash dump in

C:\Users\cburgdorf\AppData\Local\Google\CrashReports

but the Chrome-last.dmp is totally outdated. Is there any place where I can look for additional information about the crash? Not to mention it's a hard to reproduce beast.

I wonder if I could start Chrome with windbg attached and wait (2 hours or so sigh) for the tab crash. Would that work?

UPDATE

All of you gave good answers and provided valueable advice for bug hunting. In the end I was able to reproduce the bug and get a clear crash dump using the following steps:

1.) windbg.exe -o chrome.exe
2.) reproduce crash
3.) .dump /ma C:\Path\To\A\CrashDump\File.dmp (as Paul pointed out)
4.) end session and load the crash dum with windbg
5.) use !analyze -v to extract valuable information

解决方案

Once WinDbg breaks in, use this command to create a full crash dump:

.dump /ma C:\Path\To\A\CrashDump\File.dmp

这篇关于如何在Google Chrome中调试标签页崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆