But they have problems of their own. When arbitrarily sized data is accepted, you may run out of memory — and that may not happen just during input.
但它们也具有自身的问题：在接受任意大小的数据时，可能会遇到内存不足的情况——而这在输入时也许不会发生。
However, such an implementation is hardly ever acceptable: it will cause a program to run out of memory quickly since it never reclaims unused space.
尽管如此，这样的实现是无法接受的：因为它从来不回收不使用的空间，它导致程序很快会用光内存。
For a more indepth discussion on why you get Out of Memory exceptions see my earlier post.
关于为什么会发生内存溢出异常的更多深入的讨论，可以参看我先前的帖子。
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.
所有程序都不可避免地会生成错误——找不到文件、内存不足等等。
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.
机器中的内存数量是有限的，如果这个错误出现在某些循环中，那么系统最终会把内存耗尽。
This type of memory leak will cause your programs to be bloated, get slower over time, and eventually run out of memory.
这种类型的内存泄漏将会导致您的程序越来越大，运行越来越慢，最终耗尽内存。
Split up batch update calls to keep the generated XML small enough to not run into out of memory exceptions.
分割批量更新调用，以保持生成的XML足够小，不会出现内存溢出异常。
These memory Settings have a direct impact on what the JVM does when it runs out of memory.
这些内存设置对JVM在用尽内存时所执行的操作有直接影响。
The operating system handles important details like paging different parts of the file into and out of memory as needed.
操作系统会处理一些重要的细节问题，如把文件的不同部分分页到内存上，并在需要的时候从内存里提取出来。
Running out of memory can be a problem when using very large documents (generally in the 5 + MB range) with document models.
当利用文档模型使用非常大的文档(通常有5 +MB大小)时，运行时内存的不足会成为一个问题。
The fixed heap must be at least as big as the maximum memory usage of the application to avoid out-of-memory errors.
固定大小的堆不得小于应用程序的最大内存使用量，以避免出现内存不足的错误。
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.
这同系统异常不同，系统异常表示系统级别的错误，如耗尽内存或者数组越界。
In this example the applications memory usage increased rapidly, to a point where the application simply ran out of memory.
这个例子中，程序内存占用快速上升，直到产生程序内存溢出。
Even when it didn't actually run out of memory, the GC overhead was just too high when memory consumption was high.
就算没有内存溢出，当内存消耗很高时GC的开销也会很大。
The log ends when the JVM runs out of memory.
当JVM内存不足时，日志结束。
One of the perhaps easiest ones to put your finger on is what if the computer is out of memory?
一个可能的情况是，计算机的内存不足？
Each extra session requires extra memory for its backups on every node in the cluster, so you quickly run out of memory.
每个额外节点都需要额外的内存来保存集群中每个节点的备份，所以很快就会用光内存。
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必须花费更多的时间来启动整个应用程序。
Server administrators then have to deal with the fallout in the form of "out of memory" errors, server affinity in clustered environments, and serialization exceptions on server restarts.
然后，服务器管理员则必须处理由此导致的 “内存溢出”错误，集群环境中的服务器相似性，以及服务器重启时的串行化异常。
It's also pretty simple to see the effect running out of memory has on your system: everything stops.
要了解内存耗尽对您的系统所产生的影响，也是非常简单的：所有的工作都将停止。
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.
如果某个行的大小大于页大小(即大于2KB)，那么包含该行的页面可能被置换出内存。
If the user typed in a really long word, we're out of memory, something else went wrong, could be.
可能是，如果用户输入了一个很长的单词，内存不足了，程序出错了，就有可能。
With these tools, you'll be able to analyse problems such as out of memory errors, or simply browse through the available artifacts.
借助这些工具，您将能够分析各种问题，比如内存不足错误，或者只是浏览可用的工件。
If the garbage collector does not have enough space for its collections you will get a fatal out of memory exception and the process will die.
若没有留给垃圾回收器足够的空间用于垃圾整理，就会产生一个致命的内存异常，进程也将终结。
If there are many idle agents and all of them retain their private memory, it is possible that the system runs out of memory.
如果有很多的闲置代理，并且所有这些闲置代理都保留了它们的私有内存，那么就可能导致系统耗尽内存。
Otherwise, you may encounter out-of-memory errors, especially when dealing with firmware images.
否则，您可能会遇到内存不足问题，特别是在处理固件镜像时。
These UTE error messages are common symptoms of a native out-of-memory condition because the trace engine is enabled and active by default.
这些UTE错误消息是本机内存不足的一般症状，因为跟踪引擎在默认情况是启动且活动的。
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.
您还看到了如何向您的配置永久地添加交换空间，以及如何在内存不足时紧急添加交换空间。
It is used to perform in-depth analysis when out-of-memory conditions are observed.
它用于在出现内存不足的情况下执行深入分析。
应用推荐