Can't eject in MM4 [#7868]

[ACraigL]

I have an android device and latest build of MM4 A(4.0.0.1378). Whenever I try to 'safely remove device' via the MM interface, it claims the device is in use, yet I can perform the the same task without issue using the Windows 7 tray icon.

[jiri]

Thanks, entered as http://www.ventismedia.com/mantis/view.php?id=7868 . Btw, does it happen only during the initial scan of the device (i.e. 'Scanning' text is shown)?

Jiri

[ACraigL]

Hi,

No, it happens everytime. Actually, I have the setting to unmount after sync and it alerts the device is in use then as well. Of course manually trying to unmount gives the same error. The device is definitely not being scanned or otherwise busy.

[jiri]

Interesting, we aren't able to reproduce the issue. Could you try Process Explorer (http://technet.microsoft.com/en-us/sysi ... s/bb896653 ), where after selecting MediaMonkey you can find files locked on the device. Please e-mail me this info, inclusion of a debug log might help as well.

Thanks,
Jiri

[ACraigL]

How do I determine from process explorer which files MM is using/locking?

[jiri]

It would have Type=File and start either with the device drive letter, or some identifier related to the device. If unsure, you can save the data to a .txt file and e-mail it to me (File|Save As).

Jiri

[ACraigL]

Thanks Jiri. I'm at the office right now, but I will do this when I return home this evening. Any speculation as to why it would eject from the Windows utility but not MM4?

[jiri]

No idea, providing MM4 is still running while you eject from Windows, I expect you should get the same result.

Jiri

[ACraigL]

Just downloaded the latest build and having the same experience. MM unable to eject, but no problem in Windows. According to process explorer, the device files in use is \Device\KsecDD, though this is listed 3x and became as many as 6.

When I tried to kill these handles in process explorer, it told me I needed admin rights, so I ran MM4 as admin, but got the same behavior once again.

Any suggestions?

[jiri]

Btw, what kind of device it is? And 32 or 64 bit Windows version? Does it happen even right after you connect the device? You could also e-mail me a debug log of starting MM and trying to eject the device.

Jiri

[ACraigL]

Hi,

Sorry, though I mentioned this.
Motorola Atrix on Android 2.2. Windows 7 64.

It does happen after it's connected as well... not sure if it's after a scan though. Will need to check that. I have the regular version of MM installed, so I'll need to grab debug and send you a log this evening.

[jiri]

Note that in order to check whether its related to scan, you can uncheck the option '[x] Scan as soon as the device is connected' in the main device configuration screen.

Jiri

[ACraigL]

I've captured a (huge) log file. Sorry, Jiri, I was unsure what email to use. Where should I send this?
EDIT: I just submitted it with a support ticked (was that the right thing to do?) EGX-526345

This happed prior to scan FYI -- actually when I tried to eject, a scan was initialized!?!

[jiri]

The log doesn't seem to be attached, anyway, I replied in the support ticket.

Jiri

[ACraigL]

I just emailed you the log directly Jiri. Let me know if you need anything else.