View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006216 | MMW v4 | Main Panel/Toolbars/Menus | public | 2009-12-10 22:50 | 2011-09-12 19:53 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | crash | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0006216: Automatically accessing network nodes at startup can trigger freeze | ||||
| Description | Petr send me the Eureka Log and from the log I see that MM freezes when expanding Network Node and thus accessing network resources. User probably navigated to a network node and then closed MediaMonkey. After that he opened MediaMonkey, but MediaMonkey tries to capture the last used node after restart and therefore it freezes. MediaMonkey maybe shouldn't access nodes like UPnP and Network nodes automatically after start up in order to prevent from such a situations. Workaround from such a freeze is to edit MediaMonkey.ini file and delete the [LastTreePathPartsList] section. MM will not access the network node after start up. | ||||
| Additional Information | http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=7261 | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Fixed in build | 1420 | ||||
|
|
Fixed in build 1301. |
|
|
Merged to build 1295. |
|
|
Verified 1295 |
|
|
Re-opened as this no longer works (regression was introduced by 0006505 ) Note that same logic should be applied for 'Media Servers' subnodes, they needs to be initialized and their browsing can be slow. So we don't access them automatically after start up. |
|
|
Fixed in build 1420. |
|
|
Verified in 1430 that network node doesn't open on restart. Tab Title issue does occur and is reported here: http://www.ventismedia.com/mantis/view.php?id=8248#c27617 |
