The log ends when the JVM runs out of memory.

当JVM内存不足时，日志结束。

As you can imagine, running out of memory is a bad thing.

正如您可以想象的，内存耗尽是一件很糟糕的事情。

For this reason, pages can be moved out of memory and onto the disk.

由于这个原因，页面可以移出内存并放入磁盘中。

For example, your program runs out of memory or encounters divide-by-zero.

例如，你的程序运行耗尽内存，或者遇到被零除。

All programs inevitably generate errors — files not found, running out of memory, etc.

所有程序都不可避免地会生成错误——找不到文件、内存不足等等。

Hope fades into the world of night through shadows falling out of memory and time.

希望已隐没在夜晚，将摆脱黑暗，穿越记忆和时间。

Figure 13: EurekaJ Heap chart showing one possible scenario for Out Of Memory error.

图13：eurekaj堆图显示内存溢出错误的一种可能情形。

This heap dump can be generated automatically when the JVM runs out of memory or crashes.

此堆转储可在JVM用尽内存或崩溃时自动生成。

For a more indepth discussion on why you get Out of Memory exceptions see my earlier post.

关于为什么会发生内存溢出异常的更多深入的讨论，可以参看我先前的帖子。

These memory Settings have a direct impact on what the JVM does when it runs out of memory.

这些内存设置对JVM在用尽内存时所执行的操作有直接影响。

If you do not set this, Memcache will keep everything in cache until it runs out of memory.

如果不进行设置，Memcache将把所有内容都保存在缓存中，直至用光内存。

If the user typed in a really long word, we're out of memory, something else went wrong, could be.

可能是，如果用户输入了一个很长的单词，内存不足了，程序出错了，就有可能。

One of the perhaps easiest ones to put your finger on is what if the computer is out of memory?

一个可能的情况是，计算机的内存不足？

It's also pretty simple to see the effect running out of memory has on your system: everything stops.

要了解内存耗尽对您的系统所产生的影响，也是非常简单的：所有的工作都将停止。

Monitoring memory allocations to uncover leaks and other potential paths leading to running out of memory.

监测内存的分配，从而找出漏洞以及导致耗尽内存的其它潜在路径。

Even before truly running out of memory, you can cause the computer to get so busy that it becomes useless.

甚至在内存真正用完之前，也可能导致计算机变得太忙而不可用。

Split up batch update calls to keep the generated XML small enough to not run into out of memory exceptions.

分割批量更新调用，以保持生成的XML足够小，不会出现内存溢出异常。

Even when it didn't actually run out of memory, the GC overhead was just too high when memory consumption was high.

就算没有内存溢出，当内存消耗很高时GC的开销也会很大。

Each extra session requires extra memory for its backups on every node in the cluster, so you quickly run out of memory.

每个额外节点都需要额外的内存来保存集群中每个节点的备份，所以很快就会用光内存。

This type of memory leak will cause your programs to be bloated, get slower over time, and eventually run out of memory.

这种类型的内存泄漏将会导致您的程序越来越大，运行越来越慢，最终耗尽内存。

The operating system handles important details like paging different parts of the file into and out of memory as needed.

操作系统会处理一些重要的细节问题，如把文件的不同部分分页到内存上，并在需要的时候从内存里提取出来。

If a row is larger than a page (that is larger than 2 KB), then the page containing that row might be kicked out of memory.

如果某个行的大小大于页大小(即大于2 KB)，那么包含该行的页面可能被置换出内存。

In this example the applications memory usage increased rapidly, to a point where the application simply ran out of memory.

这个例子中，程序内存占用快速上升，直到产生程序内存溢出。

Running out of memory can be a problem when using very large documents (generally in the 5 + MB range) with document models.

当利用文档模型使用非常大的文档(通常有5 + MB大小)时，运行时内存的不足会成为一个问题。

If there are many idle agents and all of them retain their private memory, it is possible that the system runs out of memory.

如果有很多的闲置代理，并且所有这些闲置代理都保留了它们的私有内存，那么就可能导致系统耗尽内存。

You've also seen how you can permanently add swap to your configuration and how to add swap in an emergency when you run out of memory.

您还看到了如何向您的配置永久地添加交换空间，以及如何在内存不足时紧急添加交换空间。

Batch processing usually doesn't need data caching, otherwise you may run out of memory and dramatically increase your GC overhead.

批处理通常不需要数据缓存，否则你会将内存耗尽并大量增加GC开销。

Assume you have an application that, over time, runs out of memory for no apparent reason (you can probably think of at least one).

假设您有一个应用，随着时间的推移，没有明显原因(您可能会想到至少一个原因)就逐渐耗尽了内存。

With these tools, you'll be able to analyse problems such as out of memory errors, or simply browse through the available artifacts.

借助这些工具，您将能够分析各种问题，比如内存不足错误，或者只是浏览可用的工件。

If your JVM is swapped out of memory, GAE must spend additional time to start your entire application the next time a request comes in.

如果您的JVM被换出内存，那么在下一次请求到来时，GAE必须花费更多的时间来启动整个应用程序。