Page 1 of 2
Close program, gets into zombie state
Posted: Fri Jan 18, 2013 11:03 pm
by mcow
Part of the continuing train of stability issues: I've several times encountered this with build 1619 (Win7/64). I'm playing music for a while, browsing or testing MMA sync or whatever. Program starts acting iffy, so I go to restart: File | Exit. Window closes; icons persist in taskbar and tray. Click icon, window reopens, but is unresponsive to anything.
Re: Close program, gets into zombie state
Posted: Fri Jan 18, 2013 11:12 pm
by Lowlander
Any portable devices or Addons installed (common cause)? You can always capture it in a debug log (step 4b) and send it to support:
http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341
Re: Close program, gets into zombie state
Posted: Sat Jan 19, 2013 12:29 am
by mcow
I can't always capture it because it's not reproducible on demand. Once it's happened, I can take a log while trying to close the zombie window, and there is a message that shows up when I click the Close widget or Exit from the menu -- something like, "We were requested to shut down". But no other messages, beyond the "updating drive letter" thread progress.
I have no add-ons that run all the time, just a couple of on-demand scripts. But I am playing music, with AutoDJ (selecting from a randomized playlist), and using the Vitreous skin. There were no drives plugged in when I saw this earlier this evening.
Re: Close program, gets into zombie state
Posted: Tue Jan 22, 2013 7:45 am
by Ludek
Please try to reproduce using build 1622:
http://www.mediamonkey.com/forum/viewto ... 50#p358279
If this occurs again than send debug log (
http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341), we should see the last line in the log then to guess where the problem could be, but I guess that it was most probably fixed in recent builds.
Re: Close program, gets into zombie state
Posted: Wed Jan 23, 2013 12:18 am
by mcow
This problem did not happen with my first run of build 1622. In fact, it seemed noticeably stabler than previous builds after a typical session of a couple hours' music playing accompanied by library browsing, MMA syncing, and serving UPnP to MMA. No weird window behaviors seen.
I did not connect the iPod this session.
Re: Close program, gets into zombie state
Posted: Wed Jan 23, 2013 11:40 pm
by mcow
OK, I have seen the refusal-to-restore-window symptom with 1622, but I was able to exit the program without difficulty.
Re: Close program, gets into zombie state
Posted: Tue Jan 29, 2013 10:52 pm
by mcow
With 1622, I saw a couple of instances where the window completely closed, but it turned out the program was still running. I'll keep an eye out for this with the new build.
Re: Close program, gets into zombie state
Posted: Wed Jan 30, 2013 8:45 am
by Ludek
I have also reproduced something similar, I think it might be related to UPnP/DLNA closing. Added more debug messages to build 1624 so that I could see more then.
In my case the closing has taken long (half of minute?), not forewer.
Re: Close program, gets into zombie state
Posted: Wed Jan 30, 2013 8:57 am
by Ludek
I found a problem in code that is most probably reason of this issue, will be fixed in 1624:
http://www.ventismedia.com/mantis/view.php?id=10464
Re: Close program, gets into zombie state
Posted: Fri Feb 01, 2013 12:17 am
by mcow
Ludek wrote:I have also reproduced something similar, I think it might be related to UPnP/DLNA closing.
I saw the symptom of window closing but program not exiting again. This time, I had not served UPnP from MMW. I had sync'd to MMA once, and then just played music, using ScrobblerDJ to keep the tunes going.
I did also have my monitoring plugin running: It's a Python script that subscribes to events from the automation object, which is responsible for
another issue. I need to debug this when I get some time. Altho the script indicated that it detected MM shutting down, Python did not terminate (which it should, and did with 4.07); neither did MM. Even after killing Python, MM continued for minutes before I killed it.
Re: Close program, gets into zombie state
Posted: Wed Feb 20, 2013 10:14 pm
by mcow
I think MMW has been more stable with this fix -- I'm running 1624.
I reported a crash
here that I thought might have been related to the automation-object issue I'm having. Yesterday I saw what seemed to be that same crash again, but without having run my script, nor having played or browsed from UPnP. The symptom is, I close the program, and get two "MediaMonkey has closed" errors from Windows. I have a crash log from the first time I saw this (when my script was running).
Today I saw the following:
Started MMW, sync'd plays from MMA, played some local tracks on MMA, played some on MMA from UPnP; then switched to MMW. While playing, sync'd MMA again. Later I noticed that, starting around this sync, scrobbling stopped. I exited MMW; then restarted the program; then opened the last.fm log. Got a crash at this point, and discovered that the first run of MMW had not exited entirely, which led to the crash when I tried to open the log. Did not get a log file for this.
I did not run my script yesterday or today. Both days I was running scrobbler and the ScrobblerDJ. I'm turning off ScrobblerDJ for the time being.
So, there are still some stability problems at shutdown.
Re: Close program, gets into zombie state
Posted: Thu Feb 21, 2013 12:00 am
by Peke
Reopen, If you can replicate constantly can you please add more details and make things easier to find.
Re: Close program, gets into zombie state
Posted: Thu Feb 21, 2013 9:38 pm
by mcow
Peke wrote:Reopen, If you can replicate constantly can you please add more details and make things easier to find.
Where to put the crash log?
Re: Close program, gets into zombie state
Posted: Fri Feb 22, 2013 10:25 am
by Lowlander
Re: Close program, gets into zombie state
Posted: Mon Feb 25, 2013 2:14 am
by mcow
I had another instance of the double-crash at shutdown. No crash log generated, these are hard Windows errors; I did not have dbgview running at the time. But I did look at the "details" part of the Windows error box, and they contained the following.
First error:
Code: Select all
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6f85
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: fa66
Additional Information 2: fa6696398de2b9f98383d7a3bf5c3ea1
Additional Information 3: fa66
Additional Information 4: fa6696398de2b9f98383d7a3bf5c3ea1
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6db9
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: f3f6
Additional Information 2: f3f6a1403802118ada460cd45530935b
Additional Information 3: 72eb
Additional Information 4: 72ebf455a7c50c258dc65105bbeeaddd
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Second, almost identical except for the "additional information" lines:
Code: Select all
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6f85
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: fa66
Additional Information 2: fa6696398de2b9f98383d7a3bf5c3ea1
Additional Information 3: fa66
Additional Information 4: fa6696398de2b9f98383d7a3bf5c3ea1
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
Problem signature:
Problem Event Name: BEX
Application Name: MediaMonkey.exe
Application Version: 4.1.0.1625
Application Timestamp: 5127cb2e
Fault Module Name: gen_LastFMScrobbler.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4dffc8b2
Exception Offset: 088a6db9
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: f3f6
Additional Information 2: f3f6a1403802118ada460cd45530935b
Additional Information 3: 72eb
Additional Information 4: 72ebf455a7c50c258dc65105bbeeaddd
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
The only ongoing features I had running were scrobbling and AutoDJ; no other plugins. I had played tracks from MMW, then later some tracks from MMA via UPnP, then sync'd, then closed the program.