ardour:memoryleak
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ardour:memoryleak [2008/11/12 22:21] – deva | ardour:memoryleak [2008/11/24 19:24] (current) – deva | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| =====The Ardour memory leak===== | =====The Ardour memory leak===== | ||
| + | ^ **UPDATE:** As of svn revision r4240 (Ardour v2.7.1), the problem seems fixed. ^ | ||
| + | |||
| + | \\ | ||
| Ardour has for a very long time been having a pretty nasty memory leak, somehow connected to its undo history list.\\ | Ardour has for a very long time been having a pretty nasty memory leak, somehow connected to its undo history list.\\ | ||
| - | The author implemented a way to no store more than a given number of elements in the list, but this did not seem to fix the issue.\\ | + | The author implemented a way not to store more than a given number of elements in the list, but this did not seem to fix the issue.\\ |
| The problem manifests itself whenever an action is performed, by allocating an amount of memory, growing with number of actions taken to reach the current point in the project. In other words, the longer you work, the more memory one action will take up.\\ | The problem manifests itself whenever an action is performed, by allocating an amount of memory, growing with number of actions taken to reach the current point in the project. In other words, the longer you work, the more memory one action will take up.\\ | ||
| The leak is particularly nasty when working on big projects with 16 or more tracks, in which high end computers with as much as 4GB of memory will quickly be sent to its knees.\\ | The leak is particularly nasty when working on big projects with 16 or more tracks, in which high end computers with as much as 4GB of memory will quickly be sent to its knees.\\ | ||
ardour/memoryleak.1226524901.txt.gz · Last modified: 2008/11/12 22:21 by deva