Each new memory allocation requires updates to the memory Pointers, and as this happens more and more, it creates more and more resource consumption.
每个新内存分配都需要到内存指针的更新，而随着这一动作发生得越来越多，会带来越来越多的资源消耗。
There might be leaks, dangling Pointers, or incorrect memory usage.
可能是泄漏、空指针或者错误的内存使用。
The arrows in this diagram represent Pointers to the location of the next node in memory.
图中的箭头表示指向内存中下一个节点位置的指针。
It frees every memory block you created earlier and invalidates all the Pointers returned from the allocator routines.
该方法释放您先前创建的内存块，并使得从分配程序例程返回的所有指针失效。
The more data, the more mapping information and Pointers required for memory translation and the maintenance of them.
数据越多，内存转换和数据维护所需的映射信息和指针也越多。
And say you get through the steps described above, you still have to deal with Pointers and worry about memory leaks!
就算您竭尽全力完成了上面的步骤，还必须处理指针，并且担心内存泄露！
Dangling Pointers are likely to arise in code, which USES memory in subtle ways.
悬空指针可能发生在以微妙方式使用内存的代码中。
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.
库可以解决多种不同的内存问题，以致于直接对它们进行比较是非常困难的；这方面的常见主题包括垃圾收集、智能指针和智能容器。
Ask anybody working with C what bothers them the most about C, and many of them will probably answer Pointers and memory leaks.
对于任何使用c语言的人，如果问他们c语言的最大烦恼是什么，其中许多人可能会回答说是指针和内存泄漏。
Before assigning the Pointers, make sure memory locations are not becoming orphaned.
在对指针赋值前，请确保内存位置不会变为孤立的。
The linked list hash table contains information about the shared memory logging token pointers.
这个链表散列表包含有关共享内存日志标记指针的信息。
Before assigning the Pointers, make sure no memory locations will become orphaned.
在对指针赋值前，要确保没有内存位置会变为孤立的。
For example, there are no addressing exceptions since all Pointers get aligned and truncated to the local store size when attempting a memory access.
例如，根本就不存在寻址异常，因为所有的指针都是对齐的，并且在视图访问某处内存时都根据本地存储的大小进行了截断。
The garbage collector may incorrectly reclaim some storage that, when referenced, appears to contain pointers to uninitialized memory.
垃圾收集器可能错误地收回某些存储，当引用这些存储时，似乎包含到尚未初始化内存的指针。
If you are aware of what can go wrong beforehand, then you can take care to avoid the pitfalls and get rid of most of the Pointers and memory-related problems.
如果您预先知道什么地方可能出错，那么您就能够小心避免陷阱，并消除大多数与指针和内存相关的问题。
This is especially true for many .NET developers whom have never had to worry about memory management, pointers, and other C language responsibilities that they are unfamiliar with.
特别对于哪些从来不用担心内存管理、指 针和C语言要负责处理的东西的开发人员来说，更是如此。
You can still have memory leaks if you forget to set unused Pointers to null.
如果您忘记将不再使用的指针设置为null，那么仍然会有内存泄漏。
The display changes when you swap memory pages so you need not copy an Image object from program memory to video memory; you merely change video Pointers and the display changes.
当交换内存页时显示就发生更改，所以您不需要将Image对象从程序内存复制到显示内存；您只要更改视频指针，显示就会发生更改。
To avoid dangling Pointers (the dangerous situation where a block of memory is freed but a pointer still references it), you must delete the object only after the last reference is released.
为了避免悬空指针(一种危险的情况，即一块内存已经被释放了，而一个指针还在引用它)，必须在最后的引用释放之后才删除对象。
The overhead averages about (m + b) bytes (ignoring the Pointers at the beginning of each memory block).
内存开销大约为(M +B)个字节(每个内存块开头的指针忽略不计)。
You might forget to keep track of all the pointers (pointing to these memory locations), and some of the memory segments are not freed and stay allocated to the program.
您可能会忘了跟踪所有指针（指向这些内存位置），并且某些内存段没有释放，还保持分配给该程序。
There are two major memory-management hazards to avoid in non-garbage-collected languages: memory leaks and dangling Pointers.
在非垃圾收集语言中需要避免两个主要的内存管理危险：内存泄漏和悬空指针。
It's hard to get worked up about still dealing with low-level, per-byte-precise entities like pointers and C structs when your application is constantly receiving low-memory warnings from the OS.
当你的程序持续不断的收到系统发送的低内存警告；当你不得不与低级语言、字节级精度的指针与C结构打交道的时候，你怎么嗨的起来？
Iterating an Intrusive container needs less memory accesses than the semantically equivalent container of Pointers: iteration is faster.
介入式容器的迭代比相同语义的指针容器需要更少的内存访问：迭代可以更快。
If several read or write operations have occurred through bad Pointers, memory may be corrupted.
如果多次读或写操作时都遇到无效指针，则内存可能已损坏。
The problems, such as fragments and Pointers, existing in this kind of memory management method, are presented.
文章指出了这种内存管理机制存在的问题，阐述了内存碎片问题和指针问题。
Since it knows how frequently each variable is used and which variables are dependent, it can optimize pointers and position objects in the most efficient memory spaces.
因为它了解每个变量的使用频率以及其所依靠的变量是哪个，所以它能够优化指针，并将对象安置在最为有效的存储空间内。
Since it knows how frequently each variable is used and which variables are dependent, it can optimize pointers and position objects in the most efficient memory spaces.
因为它了解每个变量的使用频率以及其所依靠的变量是哪个，所以它能够优化指针，并将对象安置在最为有效的存储空间内。
应用推荐