Purify for memory usage tracking and memory error detection.
内存使用追踪及内存错误检测。
Memory error Check for improperly seated or missing memory.
内存错误检查是因为不正确安装或者缺少内存。
Purify issues memory error reports just before the error is about to happen.
Purify议题内存错误报告仅仅是错误发生之前的报告。
Error detection example 1: Rational Purify memory error and memory leak reports.
错误检测实例1：RationalPurify内存错误和内存泄露报告。
Figure 13: EurekaJ Heap chart showing one possible scenario for Out Of Memory error.
图13：eurekaj堆图显示内存溢出错误的一种可能情形。
I've let the app running and I found it crashed after 4-5 hours with an Out of Memory Error.
我让程序运行，我发现它坠毁后4 - 5小时出现内存不足的错误。
Remember that Purify only performs memory error checking on code that you actually execute during testing.
记住Purify只执行您在测试过程中实际执行的代码中的内存错误的检验。
I cannot say whether decoding the resources would cause an out of memory error since I don't know their size.
我不能说是否解码的资源将会导致出现内存不足的错误，因为我不知道自己的尺寸。
Using them along with the debugger helps you track memory use with the program execution which manifests a memory error.
利用它们和这个调试器将帮助您跟踪带有程序执行的内存，这表明一个内存错误。
It does not seem possible for a general-purpose allocator to also serve as general-purpose memory error testing tool such as Purify.
把一个一般用途分配器也当作一般用途内存错误检测工具(像是Purify)使用看上去是不可能的。
Often, a memory error occurs only in a combination of circumstances, and sometimes you can discover memory bugs only after you deploy your program.
内存错误通常在多种情况同时存在时出现，而且您有时只能在部署程序之后才能发现内存错误。
But if a synchronous GC occurs because of the second case — an out-of-memory error — this means the GC was unable to keep up with the application allocation.
但是如果因为第二种情况发生同步gc——内存不足错误——则意味着GC不能跟上应用程序分配。
Higher temperatures generally cause more error rates, but differences in temperature at Google's data center "had a marginal impact on the incidence of memory errors."
通常我们会认为温度过高时导致内存故障率较高的主要因素之一。但据这次谷歌研究的结果表明，内存工作温度上的差异对故障率高低的影响其实很小。
The Rational PurifyPlus product has three components: Purify for memory error checking, Quantify for performance data collection, and PureCoverage for code-coverage analysis.
RationalPurifyPlus产品有三个组件：内存错误验证的Purify，性能数据采集的Quantify，以及代码覆盖分析的PureCoverage。
Even payment of the most expensive license fees among the products available in this category loses its sting when compared to the costs of having a customer be the first to identify a memory error.
与让客户首先发现内存错误的代价相比，即使对这种类别的产品支付最昂贵的许可费也失去了意义。
If you encounter an error, even simple behaviour such as printing an error message suddenly becomes problematic because you might not have the memory to perform the operation.
如果遇到错误，即便简单的行为，如打印一条错误消息，都会突然变得困难重重，因为您可能没有内存来执行这些操作。
Memory space breach — Accomplished via stack overflow, buffer overrun, or heap error, enables execution of arbitrary code supplied by the attacker with the permissions of the host process.
内存空间缺口——通过栈溢出、缓冲区溢出或堆错误来实现，以宿主进程的权限执行攻击者提供的任何代码。
It issues an error report when it detects things like using more memory than was allocated, or using memory before it was initialized or after it was freed.
当它发现事件比被分配时使用更多的内存，或者在它初始化之前或者释放之后使用内存，就会发布一个错误报告。
The error code is 12, which means no more memory.
错误代码是12，这表示无更多内存可用。
Very often, tests are less complex than the eventual production environment, so a program can contain a memory corruption error that will wreak havoc after release even though the tests all pass.
十分普遍地情况是，测试环境并没有最终的产品环境复杂，因此即使测试都通过了，程序也能够包含一个在发布版本后即将引起严重破坏的内存崩溃性的错误。
In some organizations, it is expected that developers perform memory analysis before checking in their new code, to make sure that they did not cause an unintended error.
在一些组织中，期望开发人员在检查他们的新代码前完成内存分析，以确信他们没有引入无意的错误。
Since the amount of memory in a machine is finite, if this error occurs in some kind of loop eventually the system will run out of memory.
机器中的内存数量是有限的，如果这个错误出现在某些循环中，那么系统最终会把内存耗尽。
The layout of data allocations in memory is complex and subtle to reproduce, so any symptoms might be hard to connect back to the specific error at the level of source code.
内存中数据分配的布局非常复杂并且难以再现，所以任何症状都不可能追溯到源代码级别的具体错误。
This is different from a system exception, which represents a system level error like running out of memory or running past the end of an array.
这同系统异常不同，系统异常表示系统级别的错误，如耗尽内存或者数组越界。
The operating system imposes a limit on the amount of memory that can be locked. When this limit is reached, the overlapped operations will fail with the WSAENOBUFS error.
操作系统有一个锁定最大数的限制，一旦超过这个锁定的限制，那么就会产生WSAENOBUFS错误了。
Error detection: Runtime memory corruption in user code.
错误检测：用户模式下的运行时内存崩溃。
With a preallocated Runnable object and a separate scope, you should always be in a position to report a problem without using any memory in the context the error occurred.
通过一个预先分配的Runnable对象和一个单独的作用域，在错误发生时，您就应该总是能够报告问题，而无需使用任何内存。
Any access to this memory thereafter should be an error, because the memory pointed to by namestr has been freed.
任何对这个内存的访问从此以后都将是错误，因为这个内存由namestr指向的内存已经释放。
One he highlighted was a common developer error when working with Lucene: an apparent memory leak caused by the developer failing to close an IndexReader.
他所强调的第一种应用就是用其发现普通开发者使用Lucene时的常犯错误：没有关闭IndexReader而导致的内存泄漏。
If the program reads from memory that hasn't been initialized, or reads or writes memory that has been freed or lies beyond the ends of allocated blocks, you will see a Purify error report.
如果这个程序从还没有被初始化的内存中读取，或者读取或者改写已经被释放或者仍然存在于分配区域之外的内存，您将看到一个Purify错误报告。
应用推荐