使用 winDBG 获取 sharepoint w3wp.exe 进程内存转储
我尝试使用 winDBG (adplus) 转储 w3wp 进程。
当我运行此命令 adplus.vbs -hang -quiet -p **** 时，我发现它创建了一个包含大文件的文件夹，并且大小正在增长。然后突然，大文件消失了，该过程再次重新开始。有人知道吗？
此致，
I try to use the winDBG (adplus) to dump the w3wp process.
When I run this command adplus.vbs -hang -quiet -p ****, I found it create a folder with a big size file, and the size was growing. Then suddenly, the big size file disappeared and the process re-start again. Does anyone know about it?
Best Regards,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
永伟，
科林是对的；实际上，您正在与 IIS 竞争，因为它正在回收应用程序池。当您拍摄进程快照时，您要么达到了回收的内存阈值，要么运行状况检查发现进程被挂起并开始回收（可能是由于 ADPlus 锁定了进程）
以下是我将如何修改您的在尝试下一次捕获之前，应用程序池特征。您只需要在捕获转储时执行这些更改：
有效：您需要关闭所有尝试以保持应用程序池正常运行的功能。捕获内存快照需要时间（如您所知）。
我还建议查看 ProcDump (http://technet.microsoft.com/ en-us/sysinternals/dd996900.aspx）来自 SysInternals 人员。它上个月刚刚发布，它使进程内存捕获变得更加容易。有关使用它捕获 W3WP 的文章位于：http://blogs.msdn.com/webtopics/archive/2009/08/08/using-procdump-exe-to-monitor-w3wp-exe- for-cpu-spikes.aspx
我希望这有帮助！
Yongwei,
Colin is right; in effect, you're racing against IIS as it is recylcing the application pool. As you're snapping your process snapshot, you're either hitting a memory-threshold for recycling, or health checks are perceiving the process to be hung and instituting a recycle (possibly due to ADPlus locking the process)
Here's how I would modify your application pool characteristics prior to attempting your next capture. You only need these changes in effect for as long as it takes to capture your dump:
In effect: you need to turn off all of the features that try to keep your app pools running well. Capturing a memory snapshot takes time (as you know).
I would also recommend checking out ProcDump (http://technet.microsoft.com/en-us/sysinternals/dd996900.aspx) from the SysInternals guys. It was just released last month, and it makes process memory captures a bit easier. An article on using it to capture the W3WP is here: http://blogs.msdn.com/webtopics/archive/2009/08/08/using-procdump-exe-to-monitor-w3wp-exe-for-cpu-spikes.aspx
I hope this helps!
我只能想象 w3wp 进程的内存使用量太多，从而触发了应用程序池回收，这意味着重新启动 w3wp。
I can only imagine the memory usage of the w3wp process got to much which triggered an app pool recycle, which means restarting w3wp.