Status: Accepted Owner: ---- Labels: Type-Bug Priority-Medium New issue 273 by christian.plesner.hansen: Unit tests leak memory http://code.google.com/p/v8/issues/detail?id=273
Some of our unit tests leak memory. This is not a serious problem in itself but it pollutes the valgrind output and precludes running automated leak detection over all our tests. Here are the leaks, distilled from the valgrind output: cctest/test-utils/SNPrintF TestSNPrintF() v8/test/cctest/test-utils.cc:165 cctest/test-strings/Traverse cctest/test-strings/Slice InitializeBuildingBlocks(v8::internal::Handle<v8::internal::String>*) v8/test/cctest/test-strings.cc:110 cctest/test-strings/DeepAscii TestDeepAscii() v8/test/cctest/test-strings.cc:345 cctest/test-ast/List TestList() v8/test/cctest/test-ast.cc:38 cctest/test-api/Threading2 LocalContext::LocalContext(v8::ExtensionConfiguration*, v8::Handle<v8::ObjectTemplate>, v8::Handle<v8::Value>) v8/test/cctest/test-api.cc:83 cctest/test-api/PreCompile TestPreCompile() v8/test/cctest/test-api.cc:5632 In addition there is a "Conditional jump or move depends on uninitialised value(s)" in cctest/test-api/AccessChecksReenabledCorrectly v8_str(char const*) v8/test/cctest/test-api.cc:67 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
