Project

General

Profile

Bug #716

Memory leak in g_rms when using the -prev flag

Added by Daniel Larsson almost 8 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Low
Category:
-
Target version:
Affected version - extra info:
4.5.3 and earlier
Affected version:
Difficulty:
uncategorized
Close

Description

g_rms eats up all system memory and crashes when analyzing long and large trajectories using the -prev flag.

Associated revisions

Revision d40ce2b8 (diff)
Added by Rossen Apostolov over 4 years ago

Issue a warning for using gmx_rms -prev with large trajectories.

Refs #716.

Change-Id: I607d6a63259e0dd9de7c8c99e4917bbe9f37ff8e

History

#1 Updated by Rossen Apostolov over 6 years ago

  • Assignee set to David van der Spoel
  • Priority changed from Normal to High
  • Target version set to 4.5.6

#2 Updated by David van der Spoel over 6 years ago

  • Priority changed from High to Low
  • Target version changed from 4.5.6 to 5.0

To fix this would require a large amount of work. This can be postponed to a later release when we do more modularization.

#3 Updated by Erik Lindahl over 4 years ago

  • Affected version set to 5.0

Rossen: I would consider removing the -prev feature for now.

#4 Updated by Gerrit Code Review Bot over 4 years ago

Gerrit received a related patchset '1' for Issue #716.
Uploader: Rossen Apostolov ()
Change-Id: I607d6a63259e0dd9de7c8c99e4917bbe9f37ff8e
Gerrit URL: https://gerrit.gromacs.org/3491

#5 Updated by Rossen Apostolov over 4 years ago

I added only a warning because in most cases it will work fine despite the memory requirements.

#6 Updated by Erik Lindahl over 4 years ago

  • Target version changed from 5.0 to future

#7 Updated by Erik Lindahl 12 months ago

  • Status changed from New to Closed

No point in keeping this open. As the C++ underpinnings are maturing it's time to reimplement many of these tools, and then we should be strict about not allowing any memory leaks. However, we won't touch the old tools.

Also available in: Atom PDF