Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 OS-Mac Area-BrowserBackend Size-Medium Valgrind

New issue 20581 by [email protected]: Memory leak in btreeCreateTable() in  
history::URLDatabase::CreateURLTable()
http://code.google.com/p/chromium/issues/detail?id=20581

Probably happens in 1 of 4 runs.  Seen in

http://build.chromium.org/buildbot/waterfall.fyi/builders/Mac%20UI%202%20of%203%20(valgrind)/builds/932/steps/valgrind%20test:%20ui/logs/stdio

and

http://build.chromium.org/buildbot/waterfall.fyi/builders/Mac%20UI%202%20of%203%20(valgrind)/builds/938/steps/valgrind%20test:%20ui/logs/stdio

Valgrind complains:

4,104 bytes in 1 blocks are definitely lost in loss record 7,715 of 7,752
   malloc (vg_replace_malloc.c:195)
   sqlite3MemMalloc (third_party/sqlite/src/mem1.c:43)
   mallocWithAlarm (third_party/sqlite/src/malloc.c:228)
   sqlite3PageMalloc (third_party/sqlite/src/malloc.c:414)
   pagerAllocatePage (third_party/sqlite/src/pager.c:3682)
   sqlite3PagerAcquire2 (third_party/sqlite/src/pager.c:3831)
   pagerAcquire (third_party/sqlite/src/pager.c:3780)
   sqlite3PagerAcquire (third_party/sqlite/src/pager.c:3918)
   sqlite3BtreeGetPage (third_party/sqlite/src/btree.c:1082)
   allocateBtreePage (third_party/sqlite/src/btree.c:4248)
   btreeCreateTable (third_party/sqlite/src/btree.c:6145)
   sqlite3BtreeCreateTable (third_party/sqlite/src/btree.c:6159)
   sqlite3VdbeExec (third_party/sqlite/src/vdbe.c:4101)
   sqlite3Step (third_party/sqlite/src/vdbeapi.c:476)
   sqlite3_step (third_party/sqlite/src/vdbeapi.c:540)
   sqlite3_exec (third_party/sqlite/src/legacy.c:73)
   history::URLDatabase::CreateURLTable(bool) (url_database.cc:466)


--
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

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to