由模糊测试导致的许多故障都是内存分配错误及缓冲器溢出的直接结果。
Many of the crashes resulting from fuzz testing are direct results of memory allocation mistakes and buffer overflows.
这对于安装在笔记本电脑或者内存不多于4GB的低规格系统中的测试或开发环境很有用。
This is useful on test or development environments that are installed on laptops or low-spec systems with 4 GB or less of RAM.
为了更加清楚起见，解决内存泄漏的最佳方法是在测试时检测并解决它们。
To be clear, the best approach for solving memory leaks is to detect and resolve them in test.
这个特殊的功能在程序中可以产生正确的答案，您的测试可以通过，但是仍然可能存在内存错误。
The individual functions in the program can produce the right answers and your tests can pass, but there can still be memory errors.
性能是一个常量，但是总的来说，是我们所执行的所有测试中最慢的，并且消耗最多的本地内存。
Performance was fairly constant but was, overall, the slowest of all tests that we performed and consumed the most local memory.
这两个测试都是采用了冷启动，内存缓冲器中没有数据。
Both of these tests were from a cold start with no data in the memory buffers.
这一测试、收集、分析和修改系统的过程同样恰当地适用于性能的所有方面，包括内存利用。
This process of testing, gathering, analyzing, and modifying a system applies equally well to all aspects of performance, including memory utilization.
同样，测试完成的详情包括每次运行后的内存泄漏分析的结果。
Also, the test completion details included the results of memory leak analysis following each run.
在测试自动化中增加内存分析工具将会增加组织的总体效率。
Augmenting test automation with a memory analysis tool increases the overall efficiency in an organization.
另一个可选的方式是为测试使用内存数据库。
One alternative is to use an in-memory database for your tests.
由于在这些测试环境中重现问题的难度很大，所以相关内存泄漏的成本增加了。
The cost of associated memory leaks is magnified by the difficulty of reproduction in these test environments.
这种错误可能不会导致您的程序崩溃或者您的测试失败，但是仍然存在内存崩溃的危险。
That kind of off-by-one error might not cause your program to crash or your test to fail, but there is still memory corruption going on.
应认真测试每个应用程序，以确保它不存在内存泄漏问题。
Each application should be carefully tested to ensure that it does not suffer from memory leaks.
运行与测试无关的其他应用程序将引入针对本地CPU、内存和磁盘资源的竞争。
Having other applications also running that are unrelated to the testing introduces competition for local CPU, memory and disk resources.
在每个测试之前，系统测试人员配置许多产品参数来允许在测试过程中收集内存泄漏分析信息。
Prior to each test, the system testers configured several product parameters to allow the memory leak analysis information to be collected during testing.
将测试环境仅仅看作是属性的一套属性：可利用内存，操作系统版本，或者特定的安装软件。
Think of a test environment as simply a set of attributes: available memory, operating system version, or specific installed software.
这个应用程序组合了来自LTP的测试套件不同方面的多个测试以及内存和网络传输负载生成器。
This application combines multiple tests from different areas of LTP's test suite, along with memory and network traffic load generators.
某些类型的测试有糟糕的内存问题，这些问题只在某几次运行期间出现。
Some categories of tests have bad memory problems that surface only during certain runs.
代码是使用称为HSQLDB的内存数据库测试的，这种产品包含一个简单的GUI工具。
The code was tested using an in-memory database called HSQLDB, and this product includes a simple GUI tool.
例如，如果创建一个用于测试的模式，您可能需要确保所有测试部署使用了相同数量的虚拟内存。
For example, if you are creating a pattern to be used in testing, you might want to make sure that all test deployments use the same amount of virtual memory.
BIOS需要执行很多工作，例如对基本组件(例如系统内存)进行初始测试，确定如何引导操作系统。
The BIOS has many jobs, such as initial testing of basic components (such as the system's memory) and determining how to boot the operating system.
不过到目前为止，BIOS阶段最耗时的过程就是内存测试。
But by far, the most time-consuming aspect of the BIOS stage is in memory test.
运行测试需要多少虚拟内存？
性能测试LPAR配置了12GB的中心存储内存。
The performance test LPAR was configured with 12 GB of central storage memory.
我们面对的问题是：基准测试中是否需要将内存维护或者垃圾回收的时间包括进来？
The question is: should a benchmark measurements include the time needed for maintenance or garbage collection?
性能测试LPAR配置了12GB内存。
性能测试LPAR配置了12GB的内存。
The performance test LPAR was configured with 12 GB of memory.
这是因为每个测试都预先分配了共享内存。
This is due to the pre-allocation of Shared memory that was done for each of the tests and explained previously.
这是因为每个测试都预先分配了共享内存。
This is due to the pre-allocation of Shared memory that was done for each of the tests and explained previously.
应用推荐