Project

General

Profile

Actions
Copy link

Optimization #975

closed

DrMemory leak check

Added by Victor Julien over 10 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Effort:
Difficulty:
Label:

Description

We need a build that runs DrMemory's leak check on pcaps with rules. Preferably more than one.

This build should fail on any leaked memory detected, which means we first have to fix a bunch of them as we are not clearing all one-time allocations.

Leaks that can't be fixed or are in support libraries should be suppressed.

DrMemory is 32bit only: http://drmemory.org/

Actions
Copy link
 #1

Updated by Andreas Herz about 8 years ago

  • Tracker changed from Bug to Optimization
  • Assignee set to OISF Dev
Actions
Copy link
 #2

Updated by Victor Julien almost 5 years ago

  • Status changed from New to Closed
  • Assignee deleted (OISF Dev)
  • Target version deleted (BuildBot)

DrMemory is no longer only 32-bit, however in my private QA it has had lots of stability issues. So I prefer valgrind even if that is a bit more resource hungry.

Actions
Copy link

Also available in: Atom PDF