哪怕及时释放掉了实际的对象，但WPF的弱引用数组还是会继续持有引用，这就导致了内存泄漏。
Even when the actual objects are being released in a timely manner, WPF's arrays of weak references hang around and under stress become the memory leak.
所有关于“并行化如此容易”的理由都倾向于使用简单数组操作做例子，甚至不包含对象的分配和释放。
There's a reason all the examples of "look how easy it is to parallelize things" tend to use simple arrays and don't ever have allocations or freeing of the objects.
与数组变量不同，动态分配的数组将一直存在，直到程序显式释放它为止。
Unlike an array variable, a dynamically allocated array continues to exist until it is explicitly freed by the program.
注销那些不用的变量尤其是大数组，以便释放内存。
Unset your variables to free memory, especially large arrays.
假设分配和释放需要常量时间，这个扩容动作花费O (n)时间，这里的n是当前数组的大小。
Assuming allocates and frees run in constant time, this enlargement process takes o (n) time where nis the current size of the array.
新数组将替换数组变量中已释放的数组。
The new array replaces the released array in the array variable.
新数组将替换数组变量中已释放的数组。
The new array replaces the released array in the array variable.
应用推荐