第2部分将讨论一些跟踪内存问题的方法。
Part 2 discusses some approaches to tracking down memory problems.
寻找内存问题不需要一定有系统崩溃的情况发生。
Finding memory problems does not need to be restricted to the cases where a crash occurs.
在用户使用时程序死机或者突然崩溃：内存问题。
Program dies or crashes abruptly when customer USES it: memory.
最有可能的类型是内存问题，如内存泄漏、堆碎片、或者大对象分配。
The most likely type is a memory problem, such as memory leak, heap fragmentation, or large object allocation.
更多的程序员在他们应用程序的调试版本中使用多种寻找内存问题的方法。
Most programmers do incorporate memory problem finding tactics in debug versions of their applications.
这一部分将讨论几个调试工具，它们极大地简化了检测和找出内存问题的过程。
This section looks at a few debugging tools that greatly simplify detecting and isolating memory problems.
如果重叠，将会有数据完整性和内存问题，新informix实例可能会失败。
If they are overlapped, then there would be data integrity and memory problems and new Informix instance may fail.
事实上，许多UNIX管理员甚至不知道可以使用ps帮助确定内存问题的原因。
In fact, I would add that many UNIX administrators don't even know that you can use ps to help you determine the cause of a memory problem.
由于这些内存问题，在本文的其余小节中，我将假定该程序使用了一种垃圾收集器。
Because of these memory issues, I'll assume in the remainder of the article that there is a garbage collector with the programs.
为了能做到这点，视频必须直接传输到文件存储中，以此避免内存问题。
To do this the video is streamed directly to the file storage to avoid memory issues.
并且，对于大型附件，这有可能会中断应用程序并因为内存问题而使服务器停止运行。
And, in case of large attachment this kills the application and brings down the server with memory problems.
识别内存问题，包括较低的缓冲池命中率、较低的目录缓存命中率和较低的包缓存命中率。
Identify problems with memory, including low buffer pool hit ratios, catalog cache hit ratios, and package cache hit ratios.
在本文中，您将了解EVTK的功能并查看EVTK可以帮助您诊断内存问题的示例场景。
In this article, you'll learn about the GC and memory Visualizer's capabilities and see some example scenarios where the GC and memory Visualizer can help you diagnose memory problems.
我已经在这里讨论了一系列的问题—从类型的大小调整到可以帮助您发现代码中内存问题的工具。
I've covered a range of issues here, from the sizing of types to tools that can help you discover memory issues in your code.
虽然这样会变得稍微慢一点，但是这将保证当出现内存问题时，你的消息生产者能够及时得到通知。
While this is going to be slower, it will ensure that your message producer is informed immediately of memory issues.
的热修复补丁版本0.16 (0.16 .H2)现在生活在一个小解决内存问题在最新的构建。
A hotfix for version 0.16 (0.16. H2) is now live with a small fix for a memory issue in the latest build.
通过使用“依附进程”特性，以及导入内存dump文件的功能，极大地简化了对产品代码中的内存问题的概要。
Profiling memory problems in production code is greatly simplified by using the "attach to process" feature, along with the ability to import memory dump files.
RationalApplication Developer还提供了概括应用程序从而确定性能和内存问题的功能。
Rational application Developer also provides the capability to profile applications to identify performance and memory problems.
记录GC使用情况并不具有干扰性，因此如果需要分析内存问题或者调优垃圾收集器，在生产环境中默认启用gc日志是值得的。
Logging GC usage is not intrusive, and so it is reasonable to enable GC logging in production by default in the event you ever need to analyze memory problems or tune the garbage collector.
但是，迁移到 64位并不是适用于所有本机内存问题的通用解决方案；您仍然需要足够的物理内存来保存所有数据。
Moving to 64-bit is not a universal solution to all native-memory woes, however; you still need sufficient physical memory to hold all of your data.
库可以解决多种不同的内存问题，以致于直接对它们进行比较是非常困难的；这方面的常见主题包括垃圾收集、智能指针和智能容器。
Libraries address so many different memory issues that it's difficult to compare them directly; common rubrics in the domain include garbage collection, smart Pointers, and smart containers.
尽管这个命令提供一些有价值的信息，但是除非有可信的管理员已经诊断出系统中存在某种内存问题，否则我们通常不会首先使用这个命令。
While this command provides useful information, we don't usually start with this unless a trusted administrator has already diagnosed that there is a memory issue of some kind on the system.
至此，您应该已经了解了verbose GC以及如何使用此工具来分析和解决WebSpherePortal服务器内存问题。
You should now understand how to read verbose garbage collection and how to use this tool to analyze and address WebSphere Portal server memory concerns.
在分析native_stderr . log时，我们发现垃圾收集周期没有问题，并且不存在内存问题，如内存泄漏、堆碎片和大对象分配。
When analyzing native_stderr.log, we found that the GC cycles were fine, and there were no memory issues, such as memory leak, heap fragmentation, and large object allocation.
WebSphereApplicationServer中的轻量级内存泄漏检测是为了在测试和生产环境中提供内存问题的早期检测而设计的。
Lightweight memory leak detection in WebSphere Application Server is designed to provide early detection of memory problems in test and production environments.
我重复一下我写的关于风格的内容：尽管大量发布的内存问题描述都强调工具和语言，对于我来说，最大的收获来自“软的”以开发人员为中心的流程变更。
I repeat what I wrote about style: While most published descriptions of memory problems emphasize tools and languages, for me, the greatest gains come from "soft," developer-centered process changes.
应用程序有内存泄漏问题。
为了方便调试，还添加了一些新的特性，以帮助您修复各种内存分配问题。
Some new features were also added to the debugging facility, to help in your ability to repair memory allocation problems.
除了这些可伸缩性和内存使用问题，现有应用程序的兼容性也需要处理。
Apart from these scalability and memory usage issues, the existing application's compatibility also needs to be handled.
若要识别代码中最常导致内存分配问题的部分，请参阅工具。
To identify the parts of your code that contribute most to memory allocation issues, see Tools.
应用推荐