内存管理问题。
要正确使用列表和DataObjectPtrs，现在必须在SDO 中处理内存管理问题。
To use both lists and DataObjectPtrs correctly, you must now address memory management in SDO.
此时，标准库负责处理所有的内存管理问题，我们不必再担心每一次修改字符串时涉及到的大小问题。
Now the library handles all memory management, and we need no longer worry if the size of either string changes.
然而，这种自由可能会导致严重的内存管理问题，而这些问题可能导致程序崩溃或随时间的推移导致性能降级。
This freedom, however, can lead to significant memory management problems, and these problems can cause programs to crash or degrade over time.
能显示内存泄漏、溢出等等的位置的工具可以解决内存管理问题，我发现MEMWATCH和YAMD很有帮助。
Tools that show the location of memory leaks, overruns, and the like can solve memory management problems, and I find MEMWATCH and YAMD helpful.
为了理解这些新增功能的含义，我们需要深入研究内存管理中的艺术，并考虑为什么分配开销和运行速度是大问题。
To understand the implications of these new features, we need to delve into the fine art of memory management a bit and consider why allocation overhead and speed are a big deal.
从这个类的名称中，你或许能够获得JVM如何实现硬实时线程的一些线索；讨论内存管理的时候，我们还会再详细地讨论这个问题。
The name of the class used for hard real-time threads probably gives you a clue about how it is implemented by the JVM; we'll discuss this more when we get to memory management.
举例来说，如果是一家游戏主机开发公司而他们主要使用C语言，那你就要准备回答链表，内存管理之类底层的问题。
For example, if it's a console company and they mainly use c, be ready to answer questions on linked lists, memory usage, and other low level questions.
由于没有哪一方需要管理内存，确定缓冲区的大小就变得不必要了(因而也不可能存在前面指出的多次执行问题)。
Because no party needs to manage memory, buffer-size identification becomes unnecessary (hence there's no possibility of the multi-execution problem identified earlier).
尽管这个命令提供一些有价值的信息，但是除非有可信的管理员已经诊断出系统中存在某种内存问题，否则我们通常不会首先使用这个命令。
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.
事务管理和内存管理比起来没有多大的不同，而且我们看到由于生命周期问题，语言的总体趋势是不再让开发人员负责内存管理。
Transactions are not much different than memory and we see the general trend in languages to removing the responsibility of memory management from developers due to life cycle issues.
当 2.4内核发布时，用户几乎马上就开始遇到内存管理相关的稳定性问题。
When the 2.4 kernel was released, users started having memory management-related stability problems almost immediately.
RTSJ 处理了几个有问题的地方，包括调度、内存管理、线程、同步、计时、时钟和异步事件处理。
The RTSJ addresses several problematic areas, including scheduling, memory management, threading, synchronization, time, clocks, and asynchronous event handling.
有大量导致内存泄漏的问题，它们对于系统管理员特别棘手。
There are a number of problems that cause memory leaks to be particularly troublesome for System administrators.
例如，在本文编写之际，WebSphereApplicationServer有47个不同的组件领域，例如管理控制台、崩溃、ejb容器、内存不足问题等等。
For example, as of this writing there are 47 different component areas for WebSphere Application Server, such as administrative console, crash, EJB container, out-of-memory issues, and so on.
事实上，许多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.
这就释放了WebSphere 程序-变更管理员服务器中使用的大量本地内存，而这正是CM 服务器 7.1.0.0 以及7.1.0.1 版本中经常观察到的问题。
This solved the excessive native memory use in the WebSphere Application-Change Manager Server, which was a problem observed with CM Server 7.1.0.0 and 7.1.0.1 releases.
服务器内存不足服务器上内存不足，无法运行您的程序。请与管理员联系，以解决此问题。
Server Out Of Memoryis no memory on the server to run your program. Please contact your administrator with this problem.
服务器内存不足服务器上内存不足，无法运行您的程序。请与管理员联系，以解决此问题。
Server Out Of MemoryThere is no memory on the server to run your program. Please contact your administrator with this problem.
文章指出了这种内存管理机制存在的问题，阐述了内存碎片问题和指针问题。
The problems, such as fragments and Pointers, existing in this kind of memory management method, are presented.
操作系统内存管理的主要问题是存储空间的分配和回收。
The main problems in the memory management of operating system are the distribution and recovery of the storage space.
如果我们直接创建个对象实例，内存管理没有问题。
If we create object instances indirectly, memory management is not a problem.
分析开发过程中常遇的内存泄露和内存越界等问题，提出一种有效的内存管理方案。
The paper analyses memory leakage and out of range problems in software development, and provides a new scheme to effectively manage memory.
与原始环境不同，你不需要为内存泄漏、不定的指针、未初始化的指针或者其它内存管理陷阱问题负责。
Unlike native environments, you are not responsible for memory leaks, dangling Pointers, uninitialized Pointers, or a host of other memory-management issues.
自动内存管理可解决常见问题，例如，忘记释放对象并导致内存泄漏，或尝试访问已释放对象的内存。
Automatic memory management can eliminate common problems, such as forgetting to free an object and causing a memory leak, or attempting to access memory for an object that has already been freed.
可以检测内存泄漏、内存写溢出、释放野指针和内存管理函数的不匹配等问题。
The module can detect memory leak, write overflow, free wild pointer and mismatch using of memory functions of the executable files.
为了解决这一问题，本文设计了高效内存管理器(HPMM)来负责内存单元的申请与释放。
In order to solve this problem we designed the High Performance memory Manager (HPMM) that is responsible for the allocation and deallocation of the memory in F-Miner algorithm.
为了解决这一问题，本文设计了高效内存管理器(HPMM)来负责内存单元的申请与释放。
In order to solve this problem we designed the High Performance memory Manager (HPMM) that is responsible for the allocation and deallocation of the memory in F-Miner algorithm.
应用推荐