View Issue Details

IDProjectCategoryView StatusLast Update
0010987MMW v4Otherpublic2014-05-13 02:27
Reporterlowlander Assigned To 
PriorityimmediateSeverityblockReproducibilitysometimes
Status closedResolutionfixed 
Product Version4.1 
Summary0010987: MediaMonkey fails to start
DescriptionThis is the second time this has happened and it seems related to device connection. This time I had an iPod Nano connected, synced it with MM, closed MM, disconnected device, synced it with iTunes, disconnected device, start MM and it fails with list index out of bounds (all in a log).
Steps To ReproduceDebug on FTP
TagsNo tags attached.
Attached Files
MediaMonkey.elf (230,869 bytes)
Fixed in build

Relationships

has duplicate 0010953 closedLudek Large node and/or Column Browser cause startup failure 

Activities

lowlander

2013-06-13 04:40

developer   ~0036469

Even PC restart fails to fix this. Currently can't run MM.

lowlander

2013-06-13 04:52

developer   ~0036470

Added DB to FTP as it seems the cause of the hang. My presumption is that it is trying to load a node that isn't available. Any solutions to get MM started again?

lowlander

2013-06-13 04:56

developer   ~0036472

Finally managed to get MM started by starting in non-skinned, then back to normal.

Ludek

2013-06-13 13:02

developer   ~0036480

Last edited: 2013-06-13 13:27

I attached the ELF. From the ELF it looks that it is not related to any MM settings/data, it fails when creating main form in Forms.TScreen.GetMonitor
Looks very strange and actually I don't have no idea why it crash there, it looks like if Win API's function for getting monitor or monitors count failed, studing further...

Do you use multiple monitors? Does MM 4.0.7 start? Have you changed/upgraded GDI drivers recently?

lowlander

2013-06-13 15:50

developer   ~0036481

No, single monitor, no other updates than Windows Updates (skipped an update for the NVidia card). The 2 times I've seen this has been with portable devices being connected or after being disconnected. The first time a Sandisck and Apple device (not sure if it was a Nano or Touch) were connected and MM failed in the same way (AV's were send in) disconnecting the devices resolved it. This time it happened after the Nano was disconnected and MM was restarted (after using iTunes). Running unskinned resolved the problem this time. Note that MM did start without the DB (tested with both removing custom DB link in ini and renaming ini). My hunch would be that it's trying to load the node for the device or something similar.

(Note first time I was testing problems with starting MM large node and Column Browser enabled. I just happened to also have the 2 devices connected).

Ludek

2013-06-13 18:10

developer   ~0036489

Last edited: 2013-06-13 18:11

The issue with "MM large node and Column Browser" that you experienced had the exactly same ELF and from the ELF it doesn't look as related to MM data nor attached devices. It fails when creating the main form and getting proper monitor. I am confused by the logs and unfortunatelly so far I am not able to get enough info from the logs. I also have not been able to replicate it using your uploaded DB.

lowlander

2013-06-13 19:24

developer   ~0036492

I regularly restart MediaMonkey (especially as Now Playing isn't saved on change) and never see this. On the current install of Windows I haven't used nor use more than 1 monitor. The only constant in the 2 cases is that portable devices were used. I don't know if the first incident involved the iPod Nano (second one did) and the second incident for which a log was attached shows MM use with the Nano, then close and restart of MM resulting in failure. Maybe the first part of the log including the close shows why this is an issue. Also in both cases starting MM without the DB worked, while with the DB it failed. I suspect the monitor error may be a symptom of another problem (DB, startup node or portable device). However I can't explain why the unskinned version would resolve this.

lowlander

2013-06-13 19:33

developer   ~0036493

Note that I'm unable to reproduce trying several iPod Nano connect/disconnect scenarios. I'll keep updating if it happens again.

Ludek

2013-06-14 09:21

developer   ~0036499

Last edited: 2013-06-17 14:04

The logs really don't indicate any failure related to a portable device or DB. I think it was just your speculation, because you couldn't constantly reproduce the issue. I've added some output debug strings to 1643, If it appears again in 1643, send ELF, and mainly save standard debug log (using DbgView) and assign to me.

BTW: do you use an application for desktop management?

peke

2013-09-21 04:31

developer   ~0037629

Unable to reproduce in 1659 and touch 4G

rusty

2014-01-21 21:31

administrator   ~0039320

LL, please re-open if you can replicate.

lowlander

2014-05-13 02:27

developer   ~0040204

Haven't seen this in recent builds.