View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021289 | MMW 5 | General | public | 2024-10-22 15:18 | 2024-10-28 17:20 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1.1 | Fixed in Version | 5.1 | ||
| Summary | 0021289: Performance: MM debug takes twice as long to close as to open | ||||
| Description | MM 2024.3065 takes much longer to close (~10s on my machine) than it takes to open (~5s). Interestingly: - this is specific to the debug build - it seems to occurs more when dbugview isn't running (i.e. a debug log isn't useful for this bug) - even though the MM window has closed and appears to have terminated, 3 processes take another 5 seconds to terminate It's an annoyance for testers because it can trigger issues/errors when users attempt to run MM within 10s of closing. We've already improved the debug build's startup times, is it possible to do the same for closing times? | ||||
| Additional Information | Reported at https://www.mediamonkey.com/forum/viewtopic.php?t=106772 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3067 | ||||
|
|
Yes, I have already found before that debug builds takes long time to close when DbgView is not running.. It's very strange that if you run DbgView during closing it helps MM to close immediatelly.. So far I have no idea why.. And on the other side when DbgView is not running MM acts faster, i.e. just closing the app is faster when DbgView is running.. And when you close DbgView while MM is still running then MM can freeze.. EDIT: 5.0.4 acts the same way, the closing time is long until I run DbgView during closing and then it is closed in 200 ms: |
|
|
This is most probably unavoidable, Windows waits for debug messages to be handled and keeps sender processes in RAM, it is quickly handled in case DbgView is running, but in case nothing is catching debug messages, it lasts long, until some timeout. I think only "solution" is some wiki article, debug version should be used only for debug purposes with DbgView, otherwise users should use release version. |
|
|
I have reduced output debug messages during closing significatnly (for build 3067), but this does not seem to help much.. It's still closing for more than 5 seconds until DbgView is strtead and the first message is always [14676] MM5 [17868](B) Browser: Out of message queue. and then MM is closed immediatelly.. And the other thing is that when MediaMonkey.exe and MediaMonkeyEngine.exe are compiled without Eureka then this issue does not exist.. |
|
|
Found a workaround/fix?, added to 3067 |
|
|
3067 closes quickly without DebugView running. |
