Topic: MC is slow to close (Read 6191 times)

jleerigby · « **on:** January 13, 2004, 02:39:35 am »

MC 10 seems to be very slow to close down in the background. If you close it down you have to leave it several seconds before you can fire it up again. Often when I use my remote to send an mjextman.exe /power command to close MC whilst files are playing (especially if in full screen) I get a media core error once MC has closed.

I tried completely uninstalling and reinstalling MC to troubleshoot this but the problem is still there.

TimB · « **Reply #1 on:** January 13, 2004, 05:32:04 am »

Quote from: JLee on January 13, 2004, 02:39:35 am

MC 10 seems to be very slow to close down in the background. If you close it down you have to leave it several seconds before you can fire it up again.

I've had this forever as just accepted it as the cost of doing business.

It would be great if it was resolvable!

-=Tim=-

JimH · « **Reply #2 on:** January 13, 2004, 06:44:47 am »

Can you try to see if you have any third party plug-ins in common?

Or anything else unusual?

jleerigby · « **Reply #3 on:** January 13, 2004, 06:56:23 am »

I thought plug ins too so that was the first thing I got rid of. I also made sure I retested it after the reinstall before loading any plug ins. As far as other things in common:

23K Audio only library
42" Plasma monitor
ATI Radeon 9600 pro
Powerstrip.
Girder.

Can't post system info right now as I'm not at PC but it's an Athlon XP 2700+ with 1GB of DDR333 RAM.

JimH · « **Reply #4 on:** January 13, 2004, 07:03:11 am »

23K, meaning 23,000 files?

What type of files? APE? MP3?

What about lyrics, cover art, etc. in the files?

Has Girder always been installed?

jleerigby · « **Reply #5 on:** January 13, 2004, 07:17:52 am »

Sorry Jim -

Yes 23000 all MP3 CBR

About 70 % lyrics and the same for cover (art inside files). Very little BIOS info.

Girder has been installed for some time now and has previously worked fine.

I can't replicate the problem on my other PC which uses the same library, though not concurrent usage. I've ruled out the fact that it's a network issue (reading library and files across network) by copying the library and a few files to the local HDD. The differences on my other PC are:
- No Girder
- No Irman
- No powerstrip
- No Plasma
- ATI Radeon 7500

I guess I just talked myself into some more troubleshooting!

JimH · « **Reply #6 on:** January 13, 2004, 08:07:10 am »

Try checking the physical size of the database files (jmd files).

PhatPhreddy · « **Reply #7 on:** January 13, 2004, 08:25:00 am »

I also have this... Plus the MC icon in the system tray hangs around for ages (after a crash also)..

nila · « **Reply #8 on:** January 13, 2004, 08:38:00 am »

Quote

I also have this... Plus the MC icon in the system tray hangs around for ages (after a crash also)..

And me.

Edited:

JimH · « **Reply #9 on:** January 13, 2004, 08:40:38 am »

Nila,
Playing Now plug-in?

Skin related?

"And me" doesn't help at all.

Matt · « **Reply #10 on:** January 13, 2004, 08:41:44 am »

On close, the database is saved. It can take a few seconds. Especially if you have lyrics, bios, etc.

JimH · « **Reply #11 on:** January 13, 2004, 08:50:43 am »

Please post details. Example:

Files: 23,000
Database size*: 12MB
Time to close: 4 seconds

* Total size of the jmd files in the [program directory]/data.

nila · « **Reply #12 on:** January 13, 2004, 08:55:52 am »

Files: 22,167 (close!! - nearly 23,000)
Db size: 57Mb
First test close - 12 seconds then media core crash.
Second/third times - 4 seconds

KingSparta · « **Reply #13 on:** January 13, 2004, 11:46:11 am »

All this is going to depend on the DB, it takes sometime even after you close MC for it to really close because of the saving of the db been dealing with this for years.

if i close MC i can not use the compiler to compile a OCX untill maybe 15 seconds so i normaly take a drink of coffee and look at the TV for a second or two before I build a new OCX with changes.

It also depends on the speed of the computer and if you happen to be using the dives for something else, like copying files etc...

I don't see this as a problem.

jleerigby · « **Reply #14 on:** January 13, 2004, 12:02:22 pm »

I don't have MC Icon shown in the system tray and I can only replicate the problem when I send the mjextman.exe /power command via Irman to Girder provided I've been in full screen mode and started playing files (even if I stop playback well before closing it still happens). I think it's something to do with Irman as I can even invoke the close from within Girder (Commands>Test Command) i.e. without pressing the remote, and it does not cause a media core error. I can also close MC by sending mjextman.exe /Power from one of my internet keyboard hot keys and I don't get the crash. Regardless of which method I use MC is still slow to close.

Something strange that I've noticed through repeating this test lots of times with Task Manager opened at the processes tab is that sometimes I get 2 instances of Media Jukebox shown and 2 or more mjextman.exe. One of the media jukebox entries sometimes hangs around after MC has closed. I haven't been able to pin point the various different behaviours to the different methods of closing though (Irman, Keyboard etc). It just seems to vary.

Files: 23120 MP3 using 108.5 GB
Database size: 32.6 MB
Time to close: 18 secs followed (sometimes) by Media Core error

nila · « **Reply #15 on:** January 13, 2004, 12:20:21 pm »

King - the 4 seconds I quoted was just from starting it up and closing instantly with NO changes made to the db or any files.

With changes it's longer.

RhinoBanga · « **Reply #16 on:** January 13, 2004, 12:31:19 pm »

Quote from: JimH on January 13, 2004, 08:40:38 am

Nila,
Playing Now plug-in?

Nila,

Jim is suggesting that PlayingNow may be the problem ... is this the case?

nila · « **Reply #17 on:** January 13, 2004, 12:54:30 pm »

Uninstalled Playing Now and it's not changing the speed at all.

TimB · « **Reply #18 on:** January 13, 2004, 01:10:19 pm »

Files: 17.000
Database size*: 11MB
Time to close: I'd guess, as I don't know until I try to reopen MC, about 20-30 seconds.

-=Tim=-

JimH · « **Reply #19 on:** January 13, 2004, 01:49:23 pm »

It looks like the problem is related to the size of the database.

The storage of lyrics and other metadata inside the database can really affect the size (in MB).

To prove this, try creating a smaller database with no lyrics, etc. Just to test.

RhinoBanga · « **Reply #20 on:** January 13, 2004, 01:51:52 pm »

Is MC saving the database on close even if nothing has changed?

jleerigby · « **Reply #21 on:** January 13, 2004, 04:30:59 pm »

RhinoBanga- The database includes the curent playing now list. Also, if you play any tracks this updates the Last Played and Number of Plays data for that track. That's why I only get the problem if I've played any tracks.

Jim - I already tried that yesterday and still got the error. The database had just one file imported into it. When I played that file with full screen Vis and tried to shutdown MC using my Irman I got the media Core error.

I've run benchmarks to stress my system in case there's some other issue but it stands up really well. I can't understand it.

Could someone set Task Manager to 'Always on top', play some files and then close MC with remote (mjextman.exe /power) just to see what goes on. Like why does Media Jukebox.exe list itself twice and why does one entry hang around after MC has been closed? Mjextman.exe is also listed several times even though I only press one button on the remote and it's not a girder multigroup. Can anyone replicate this or is it just normal behaviour.

The thing about MC still showing in task manager afterwards is what worries me. Although it looks like it's closed down (vanished from taskbar) it clearly hasn't closed and that's why I get no response from the shortcut when I try and restart it.

TimB · « **Reply #22 on:** January 13, 2004, 04:59:29 pm »

Wish I could contribute more but I'm heading out for a few days away from my desktop machine. If I get a chance tonight before I leave I'll post the message I get, but its not MC Core crash.

-=Tim=-

skeeterfood · « **Reply #23 on:** January 13, 2004, 07:26:58 pm »

Quote from: JLee on January 13, 2004, 04:30:59 pm

Could someone set Task Manager to 'Always on top', play some files and then close MC with remote (mjextman.exe /power) just to see what goes on. Like why does Media Jukebox.exe list itself twice and why does one entry hang around after MC has been closed? Mjextman.exe is also listed several times even though I only press one button on the remote and it's not a girder multigroup. Can anyone replicate this or is it just normal behaviour.

The thing about MC still showing in task manager afterwards is what worries me. Although it looks like it's closed down (vanished from taskbar) it clearly hasn't closed and that's why I get no response from the shortcut when I try and restart it.

I tried the following:
1) Start MC 10.0.32
2) Play a couple of files
3) Start->Run mjextman /Power

I only ever have 1 MediaJukebox.exe and 1 mjextman.exe running and everything closes just fine with nothing hanging around.

-John

RhinoBanga · « **Reply #24 on:** January 14, 2004, 12:58:46 am »

Quote from: JLee on January 13, 2004, 04:30:59 pm

RhinoBanga- The database includes the curent playing now list. Also, if you play any tracks this updates the Last Played and Number of Plays data for that track. That's why I only get the problem if I've played any tracks.

If MC is like any other normal database system then an update should not cause the slowdowns as the space has already been allocated, so it's just a matter of seeking to the right location and writing the bytes. Maybe this is not the case though, only Matt can answer that.

As far as playing now is concerned it's actually written out to "curplaylist.jmd".

PhatPhreddy · « **Reply #25 on:** January 14, 2004, 02:00:33 am »

Quote

I don't have MC Icon shown in the system tray and I can only replicate the problem when I send the mjextman.exe /power command via Irman to Girder provided I've been in full screen mode and started playing files (even if I stop playback well before closing it still happens). I think it's something to do with Irman as I can even invoke the close from within Girder (Commands>Test Command) i.e. without pressing the remote, and it does not cause a media core error. I can also close MC by sending mjextman.exe /Power from one of my internet keyboard hot keys and I don't get the crash. Regardless of which method I use MC is still slow to close.

I have had very similar errors (not with MC) that I determined were due to Girder recieving multiple IR codes from the remote and sending multiple commands very quickly... If you have a pronto examine the recorded IR code and see if it is a loop or double code learnt and also increase the delay that Girder will send the command via mjextman.

TimB · « **Reply #26 on:** January 14, 2004, 02:06:45 am »

Didn't sleep as well as I hoped, here are my error messages.

"Could not create WebRemote Listener"

then

"Failed to start remote server"

If I wait long enough after quitting MC to restart I won't get these. Not sure if these are connected to this actual thread but they are minorly annoying.

Media Center Registered 10.0.32 -- C:\Program Files\J River\Media Center\

Microsoft Windows XP Workstation 5.1 Service Pack 1 (Build 2600)
Intel Pentium 4 2398 MHz MMX / Memory: Total - 1048 MB, Free - 534 MB

Internet Explorer: 6.0.2800.1106 / ComCtl32.dll: 5.82 (xpsp1.020828-1920) / Shlwapi.dll: 6.00.2800.1276 / Shell32.dll: 6.00.2800.1233 (xpsp2.030604-1804) / wnaspi32.dll: N/A
Ripping / Drive E: Copy mode:Normal CD Type:Auto Read speed:Max
Drive F: Copy mode:ModeSecure CD Type:Auto Read speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: No / Play sound after ripping: No

Burning / Drive F: LITE-ON LTR-52327S Addr: 1:1:0 Speed:52 MaxSpeed:52 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: Yes
Use playback settings: Yes / Normalization: None

-=Tim=-

jleerigby · « **Reply #27 on:** January 14, 2004, 06:59:30 am »

Quote from: PhatPhreddy on January 14, 2004, 02:00:33 am

Quote
I don't have MC Icon shown in the system tray and I can only replicate the problem when I send the mjextman.exe /power command via Irman to Girder provided I've been in full screen mode and started playing files (even if I stop playback well before closing it still happens). I think it's something to do with Irman as I can even invoke the close from within Girder (Commands>Test Command) i.e. without pressing the remote, and it does not cause a media core error. I can also close MC by sending mjextman.exe /Power from one of my internet keyboard hot keys and I don't get the crash. Regardless of which method I use MC is still slow to close.

I have had very similar errors (not with MC) that I determined were due to Girder recieving multiple IR codes from the remote and sending multiple commands very quickly... If you have a pronto examine the recorded IR code and see if it is a loop or double code learnt and also increase the delay that Girder will send the command via mjextman.

I just use the remote from my DVD player via IRMAN. What do you mean by 'see if it's a loop or double code learnt' ? There's only 1 event associated with the command. Is that what you mean?

JimH · « **Reply #28 on:** January 14, 2004, 07:28:35 am »

JLee,
If you're using IRMAN, why not just use MC's remote plug-in. You don't need Girder to do that.

Jim

jleerigby · « **Reply #29 on:** January 14, 2004, 11:26:16 am »

Quote from: JimH on January 14, 2004, 07:28:35 am

JLee,
If you're using IRMAN, why not just use MC's remote plug-in. You don't need Girder to do that.

Jim

I used to use this but soon reaslised that it's way to limiting. MC's remote plug in does not support all of the mjextman commands I need, and I don't use that many - honest!

I never understood why MC developed a load of really useful command line parameters and did not enable the functions (applying ratings for example) to be used with it's own remote plug in. I spent hours on this forum trying to encourage newbies to try the built in plug in rather than start on the steep learning curve needed to use Girder. Now I've seen the power of Girder and realised that it's really not that difficult when you get going I always recommend Girder over MC's plug in.

Following PhatPhreddy's comment I think I'll try assigning a different button on my remote. I want to get to the bottom of this business where media jukebox.exe remains in the processors list on task manager after closure and where I see several instances of mjextman.exe. I'm sure that's a clue to the problem I'm having and I've a feeling PhatPhreddy might be on to something.

jleerigby · « **Reply #30 on:** January 14, 2004, 12:30:28 pm »

Yep. That's it. I've assigned it to a new button and I no longer get the media core crash. Thanks PhatPhreddy

Robert Taylor · « **Reply #31 on:** January 14, 2004, 10:23:37 pm »

If you're trying to track problems like this down, sometime the crappy little task manager in WinXP just isn't up to it (I think).

Try this tool, Process Explorer http://www.sysinternals.com/ntw2k/freeware/procexp.shtml. It's much more comprehensive, and can show things like what DLLs a given process is accessing etc.

And best of all, it's free!!

TimB · « **Reply #32 on:** January 15, 2004, 06:16:42 am »

Great to see JLee's problem is solved!

Any ideas on my problem (listed above?)

-=Tim=-

JimH · « **Reply #33 on:** January 15, 2004, 07:32:34 am »

Tim,
Like JLee's problem, it's likely to be connected to use of another piece of software. Plug-in, 3rd party plug-in, background task, etc.

How do you start MC?

Try describing your system really well. Start by posting your system info.

Jim

JaWe · « **Reply #34 on:** January 15, 2004, 09:20:58 am »

Quote from: Matt on January 13, 2004, 08:41:44 am

On close, the database is saved. It can take a few seconds. Especially if you have lyrics, bios, etc.

Why can't database be updated and saved when you change it? It is very annoying when sometimes I have been working with tags for couple of hours and then MC crashes. I have to all again. Do I have to close and restart MC every half an hour to save changes?

RhinoBanga · « **Reply #35 on:** January 15, 2004, 09:46:11 am »

Matt,

Why can't CTRL+S be implemented to save?

Matt · « **Reply #36 on:** January 15, 2004, 10:20:10 am »

Quote

Why can't database be updated and saved when you change it? It is very annoying when sometimes I have been working with tags for couple of hours and then MC crashes. I have to all again. Do I have to close and restart MC every half an hour to save changes?

It is saved periodically. How often depends on the size of your database.

Quote

Matt,

Why can't CTRL+S be implemented to save?

The improved database engine we're working on will eliminate the need for this. It's too soon to say when it'll be ready for release.

PhatPhreddy · « **Reply #37 on:** January 15, 2004, 07:20:34 pm »

Quote

Like JLee's problem, it's likely to be connected to use of another piece of software. Plug-in, 3rd party plug-in, background task, etc.

Partially true... It is correct the error is manifested by Girder sending multiple shutdown commands in quick sequence via MJextman...

Its also true that MJextman and MC should be robust enough to refuse the repeated commands without crashing.

jleerigby · « **Reply #38 on:** January 16, 2004, 07:13:24 am »

Quote from: PhatPhreddy on January 15, 2004, 07:20:34 pm

Quote
Like JLee's problem, it's likely to be connected to use of another piece of software. Plug-in, 3rd party plug-in, background task, etc.
Partially true... It is correct the error is manifested by Girder sending multiple shutdown commands in quick sequence via MJextman...

Its also true that MJextman and MC should be robust enough to refuse the repeated commands without crashing.

See what you mean but that might be a little harsh on MC in this case. If I send multiple Close commands to MC while it's open it doesn't crash, nor does it crash if I send multiple Open commands while it's not open. What girder was doing was sending multiple /Power commands. This is supposed to open MC if it's not running or close MC if it is running. I can see how sending multiple /Power commands in quick succession would therefore be a little more troublesome.

Couch · « **Reply #39 on:** January 29, 2004, 12:21:49 am »

Quote

"Could not create WebRemote Listener"

then

"Failed to start remote server"

Tim:
I've Noticed I only get this error when I have Media Server start up with Windows.

^ Thus 'Media Server' is already running when I start Media Center.

INTERACT FORUM

Author Topic: MC is slow to close (Read 6191 times)

jleerigby

jleerigby

jleerigby

nila

nila

jleerigby

nila

nila

jleerigby

jleerigby

jleerigby

jleerigby

jleerigby