View Issue Details [ Jump to Notes ]

[ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000911

VTK

(No Category)

public

2004-06-04 13:05

2007-08-28 13:56

Reporter

Ivan

Assigned To

Priority

high

Severity

minor

Reproducibility

always

Status

closed

Resolution

duplicate

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0000911: Memory leak in vtkTimerLog / vtkOpenGLPolyDataMapper

Description

1. Code in vtkTimerLog::CleanupLog() has a bug:
instead of

  if (!vtkTimerLog::TimerLog )
    {
    return;
    }
it has
if (vtkTimerLog::TimerLog)
As a result memory for the log is never freed.

2. In vtkOpenGLPolyDataMapper TimerLog is allocated by default in calls to vtkTimerLog::MarkStartEvent, but clean up is never called. Destructor of vtkOpenGLPolyDataMapper should call vtkTimerLog::CleanupLog().

This memory leak was reported earlier in mailing list: http://vtk.org/pipermail/vtkusers/2002-September/013067.html, [^] but looks like was never tracked down.

Tags

No tags attached.

Project

Type

Attached Files

Relationships

Notes
(0001177) Mathieu Malaterre (developer) 2004-06-04 13:16	Fixed in CVS: http://www.vtk.org/cgi-bin/cvsweb.cgi/VTK/Common/vtkTimerLog.cxx.diff?r1=1.38;r2=1.38.4.1;f=u [^] The problem is that TimerLog has static members and thus this is really tricky to solve. BTW this is already enter in the database: bug 0000138

Issue History
Date Modified	Username	Field	Change
2007-08-28 13:55	Zack Galbreath	Note Deleted: 0008280
2007-08-28 13:56	Zack Galbreath	Assigned To	Utkarsh Ayachit =>
2007-08-28 13:56	Zack Galbreath	Status	tabled => closed
2007-08-28 13:56	Zack Galbreath	Summary	Goodsite => Memory leak in vtkTimerLog / vtkOpenGLPolyDataMapper
2007-08-28 13:56	Zack Galbreath	Project	@5@ => VTK
2011-06-16 13:11	Zack Galbreath	Category	=> (No Category)