| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0020906 | MMW 5 | Other | public | 2024-05-04 16:37 | 2024-05-15 15:38 |
| Reporter | lowlander | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | sometimes |
| Status | assigned | Resolution | open | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | ||||
| Summary | 0020906: AV EFBE0000 (out of memory) | ||||
| 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) |
