| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020906 | MMW 5 | Other | public | 2024-05-04 16:37 | 2024-10-15 15:29 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | feedback | Resolution | open | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1.1 | ||||
| Summary | 0020906: AV EFBE0000 (out of memory) / navigating menus increases memory utilization | ||||
| Description | Found MediaMonkey in the morning with this AV. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
It was "out of memory" error :-/ Analyzing the debug log and between lines 00361777 51325.65625000 [18856] 51247 MM5 [13868](R) MemRAM: 962.5 MB, MemPrivate: 926.3 MB, MemVirtual: 1.5 GB ... 00362639 53973.66796875 [18856] 53895 MM5 [19184](R) MemRAM: 3.1 GB, MemPrivate: 3.1 GB, MemVirtual: 3.9 GB the memory utilization has grown +2 GB!! without any activity seen in the debug log.. @Petr, any idea? Are there any debug lines in Chromium that could be enabled to see what is causing this huge mem utilization? |
|
|
Same thing happened to me when I left MM running overnight (log was submitted). |
|
|
And it happened again after next night |
|
|
Could you please start MediaMonke.exe via command line with /CEFDEBUG parameter and re-generate new DbgView log? MediaMonkey.exe /CEFDEBUG |
|
|
New log in same spot. |
|
|
The log with /CEFDEBUG parameter still does not show anything useful, assigned to Petr to get even more debug messaging from Chromium (related to used memory) in order to catch what could be the culprit... |
|
|
image-2.png (16,937 bytes) |
|
|
Another AV on return in the morning (3026). image-3.png (13,722 bytes) |
|
|
More logs added from 3027 |
|
|
When I run MM 2024.3028 memory utilization is around 350MB. After using it for an hour it'll go up to about 600MB, and after leaving it playing overnight, it increases to about 1.5GB. Interestingly, switching skins caused memory utilization to go from 1.5GB to 500MB! |
|
|
Rusty, do you have pop-up playback notifications enabled? According to my tests, these could be guilty of some memory leaks. |
|
|
Yes, playback Pop-up notifications are enabled. |
|
|
Note that the Rusty's issue is most likely only another instance of https://www.ventismedia.com/mantis/view.php?id=20906, the original Martin's might be something different. |
|
|
83180000 Seen on 3030, after leaving MediaMonkey paused overnight. New full log added. image-4.png (12,429 bytes) |
|
|
We've changed chromium memory management in 3031 so please retest. |
|
|
Haven't seen the error in few days on 3031 (with petr libcef.dll)/3032. However high memory usage has seen ~1400MB and constant CPU usage of 5-6% while MM is idle. This particular instance was after a large (>8000 files) wifi Sync (after failed USB Sync). |
|
|
I reported at 0021030:0076089 , but apparently it's part of this issue: "Tested 3032, and it appears that this (memory utilization increasing as a result of menu navigation) isn't fully fixed. Navigating the Send to folder hierarchy (i.e. moving the cursor up and down between Folder (move)/Folder (copy)/Folder (Rip/convert) for a minute, memory utilization grows by 100MB! " |
|
|
@lowlander: I would need to see debug log of the sync process.. @Rusty, I can confirm that navigating menus is still leaking memory, AFAIK this is because each menu is shown as separated window and the window is not fully cleaned up, Petr is solving it.. |
|
|
Retested 3061 and navigating the Send to / FMFS menus still increases memory utilization significantly (by about 45MB after navigating through the menus for one Artist). More importantly the memory doesn't free up after waiting 15m. Note: 0021234 is being used to track memory issues related to Node/View switching (to test the above, navigate the menus without actually clicking them). Please triage. |
