Bug Clicking on MP3 when WMP Has Not Been Initialized

[therube]

Bug Clicking on MP3 when WMP Has Not Been Initialized


I threw together a hodge podge of a system.

(Hodge podge.
Installed XP on one computer. Messed around for a bit. Pulled HD. Installed it into a different computer, different architecture. Appears to be running Ok.)

I threw SS on it.

I clicked on MP3.

Up to that point, I had not played any media files. Windows Media Player (v9) had not been run. WMP's first "run" is an "initialization" (setup) routine. I don't typically use WMP, so I don't typically run it or initialize it.

The WMP setup dialog comes up. And you can cancel out of it - which I did.

At that point, SS became quirky.

Mouse can no be used to position the cursor. Though it can be used to change the sort column. If you try to click another file in the panel, the icon changes. You cannot close SS, the X button simply dings.

You can tab key over to the other panel. After tabbing back, the cursor keys are operable, but the mouse still is not.

If you then click on a file (with the Enter key), SS generate the following dialog.

I've sent the Abort via email.

(And I'm assuming that this is not simply some quirk with my hodge podge of a system .)

[Jan Rysavy]

There is a (reproducible) bug in Windows Media Player that causes described problem. You can try to start WMP and walk through initial windows, so they will not open next time. Sometimes even this doesn't help.

The problem: when you open file associated with WMP (for example .MP3 or .WMA) WMP shell extension (wmpshell.dll) is loaded into our process. When you close the WMP windows, the wmpshell.dll doesn't exit.

Try to reproduce described problem. Then start second instance of Salamander and using menu Help > Task List break the first instance. Look at generated Bug Report to the "Stack Back Trace" section

Code: Select all

Stack Back Trace:
  Thread ID: 0xB90
  EIP = 0x7C90EB94 ntdll.dll
  0x7C802451 kernel32.dll
  0x0048EE94 SALAMAND.exe
  0x004FE539 SALAMAND.exe
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  0x77D4B4C0 USER32.dll
  0x77D4B50C USER32.dll
  0x7C90EAE3 ntdll.dll
  0x77D4D598 USER32.dll
  0x77D4D545 USER32.dll
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  0x77D4C63F USER32.dll
  0x77D4E905 USER32.dll
  0x004FE49C SALAMAND.exe
  0x0048A070 SALAMAND.exe
  0x004FE539 SALAMAND.exe
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  0x77D4B4C0 USER32.dll
  0x77D4B50C USER32.dll
  0x7C90EAE3 ntdll.dll
  0x77D4D598 USER32.dll
  0x77D4D545 USER32.dll
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  0x77D4C63F USER32.dll
  0x77D4E905 USER32.dll
  0x004FE49C SALAMAND.exe
  0x0048A070 SALAMAND.exe
  0x004FE539 SALAMAND.exe
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  0x77D489CD USER32.dll
  0x77D48A10 USER32.dll
  0x085CA1FC wmpshell.dll
  0x085C5615 wmpshell.dll
  0x085C6B87 wmpshell.dll
  0x085C6C7B wmpshell.dll
  0x7CA0E283 SHELL32.dll
  0x7CA0E1D5 SHELL32.dll
  0x004D4970 SALAMAND.exe
  0x004D4C75 SALAMAND.exe
  0x00441183 SALAMAND.exe
  0x00439080 SALAMAND.exe
  0x0043A716 SALAMAND.exe
  0x00434E9C SALAMAND.exe
  0x004FE539 SALAMAND.exe
  0x77D48734 USER32.dll
  0x77D48816 USER32.dll
  ----

You can see the wmpshell.dll injected into Salamander. Unfortunately only Microsoft can fix this problem, but they didn't reflect on us.