View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004465 | MMW v4 | Conversion/Leveling | public | 2008-03-13 16:32 | 2008-03-21 15:50 |
Reporter | Ludek | Assigned To | |||
Priority | immediate | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 3.0 | ||||
Summary | 0004465: f_aac_codec: Huge memory leak when converting m4a -> mp3 | ||||
Description | As reported here: http://www.mediamonkey.com/forum/viewtopic.php?t=27206 | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Note that this mem leak was present also in case of decoding FLAC and AAC, not only M4A, M4B and MP4. Fixed. |
|
Tested build 1144 with 1.0.1 of the aac plugin and the bug still seems to occur. I was able to reproduce the problem twice with 'You can't hurry love.m4a' (no drm): once during auto-conversion and once during conversion. In both cases, conversion gets 'stuck' partway through, with 1 CPU at 100% and memory at 150-250MB (alternating). I'm not sure if it's the same problem, though, since although the track plays normally, the cpu/memory problem seems to also occur at the conclusion of the track. Note: The track plays correctly on both iTunes, Quicktime, and Winamp. |
|
Yes, I see, it is another problem specific to this track and occurs on the conclusion of this track, and in addition this bug occurs only with release version of the plugin. I am looking into it. |
|
Yes, the decoding never ends for some tracks and only in the release version of the AAC plugin. This was a really strange one, I fixed it, but I haven't found why this occured only in release version and only by using some tracks. Fixed packages of MediaMonkey_AAC_Plug-in_1_0_1_Trial.exe and MediaMonkey_AAC_Plug-in_1_0_1.exe are uploaded. |
|
Verified. |