Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news


  

Author Topic: wincab Version 3.1.4 Unstable?  (Read 16472 times)

0 Members and 1 Guest are viewing this topic.

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
wincab Version 3.1.4 Unstable?
« on: November 06, 2007, 09:59:57 pm »
Wincab repeatedly shuts down and goes to a windows error. It is random either when a song is playing or when someone is changes the pages. I have the error log set to the highest level and still donít show any error. I am running XP Home SP2.

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #1 on: November 06, 2007, 10:03:43 pm »
Wincab repeatedly shuts down and goes to a windows error. It is random either when a song is playing or when someone is changes the pages. I have the error log set to the highest level and still donít show any error. I am running XP Home SP2.
It may not show an error but it will show the last thing WinCab was trying to do when it crashed.  What are the last 5 or 6 lines at the end of the log after a crash?

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #2 on: November 06, 2007, 10:06:37 pm »
0:04:18.38-LVL5-ARTCACHE: Found cached pointer #23
0:04:18.38-LVL5-ARTCACHE: Found cached pointer #24
0:04:18.39-LVL5-ARTCACHE: Found cached pointer #25
0:04:18.39-LVL5-ARTCACHE: Found cached pointer #26
0:04:18.39-LVL3-MQ_PROCESS: Processing message: MSG_INTERSONG
0:04:20.38-LVL3-MQ_PROCESS: Processing message: -MSG_INTERSONG
0:04:20.38-LVL2-SONG_LOAD: Trying to load C:\Documents and Settings\Laptop\Desktop\Music\Allan Jackson\Greatest Hits 2\It's Five O' Clock Somewhere.mp3...
0:04:20.38-LVL5-SONGBUF_LOAD: Allocating 9422640 bytes...
0:04:20.38-LVL5-SONGBUF_LOAD: Song buffer relocated from 1ab0020 to c0f0020
0:04:20.69-LVL2-SONGBUF_LOAD: Loaded 9357104 bytes for file C:\Documents and Settings\Laptop\Desktop\Music\Allan Jackson\Greatest Hits 2\It's Five O' Clock Somewhere.mp3
0:04:20.69-LVL3-MQ_PROCESS: Processing message: MSG_PRESONG
0:04:20.69-LVL3-MQ_PROCESS: Processing message: -MSG_PRESONG
0:04:20.71-LVL1-SONG_START: Starting song It's Five O' Clock Somewhere, type 1
0:04:20.83-LVL3-SONG_START: Song It's Five O' Clock Somewhere started
0:04:20.84-LVL5-ARTCACHE: Found cached pointer #23
0:04:20.85-LVL5-ARTCACHE: Found cached pointer #24
0:04:20.86-LVL5-ARTCACHE: Found cached pointer #25
0:04:20.86-LVL5-ARTCACHE: Found cached pointer #26
0:04:20.86-LVL3-MQ_PROCESS: Processing message: MSG_SONGSTART
0:08:14.16-LVL3-MQ_PROCESS: Processing message: -MSG_SONGSTART
0:08:14.16-LVL3-MQ_PROCESS: Processing message: MSG_POSTSONG

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #3 on: November 06, 2007, 10:10:47 pm »
Did this one crash at the beginning of a song or on a page change?
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #4 on: November 06, 2007, 10:12:52 pm »
Page change

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #5 on: November 06, 2007, 10:20:17 pm »
Somewhere early in the debug log, there's a section that looks like this:

0:00:00.00-LVL2-ARTCACHE_INIT: ****** Initializing cover art cache ******
0:00:00.00-LVL2-ARTCACHE_INIT: Cover art size after scaling: 217x217
0:00:00.00-LVL2-ARTCACHE_INIT: Color depth: 16 bits/pixel, 2 bytes/pixel
0:00:00.00-LVL2-ARTCACHE_INIT: Bytes per cache entry: 95110 (932 for BITMAP structure and row pointers)
0:00:00.00-LVL2-ARTCACHE_INIT: Requested cache size: 4 MB
0:00:00.00-LVL2-ARTCACHE_INIT: Cache entries: 44
0:00:00.00-LVL2-ARTCACHE_INIT: Actual cache size: 3.99 MB
0:00:00.00-LVL2-ARTCACHE_INIT: ****** Cover art cache initialization complete ******

What does yours say?

--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #6 on: November 06, 2007, 10:26:31 pm »
0:00:00.00-LVL2-ARTCACHE_INIT: ****** Initializing cover art cache ******
0:00:00.00-LVL2-ARTCACHE_INIT: Cover art size after scaling: 267x267
0:00:00.00-LVL2-ARTCACHE_INIT: Color depth: 16 bits/pixel, 2 bytes/pixel
0:00:00.00-LVL2-ARTCACHE_INIT: Bytes per cache entry: 143710 (1132 for BITMAP structure and row pointers)
0:00:00.00-LVL2-ARTCACHE_INIT: Requested cache size: 4 MB
0:00:00.00-LVL2-ARTCACHE_INIT: Cache entries: 29
0:00:00.00-LVL2-ARTCACHE_INIT: Actual cache size: 3.97 MB
0:00:00.00-LVL2-ARTCACHE_INIT: ****** Cover art cache initialization complete ******

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #7 on: November 06, 2007, 10:34:39 pm »
The very next page would fill the last of the image cache buffers and need to clear at least one existing buffer.  Hmm.

I wonder if you crash it again if it's always on the last page of buffers?

Try running WinCab again but page backward instead of forward until it crashes and send me the last dozen lines again.

Thanks!

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #8 on: November 06, 2007, 10:46:15 pm »
:02:05.21-LVL5-ARTCACHE: Replacing cache entry #23
0:02:05.29-LVL5-ARTCACHE: Replacing cache entry #24
0:02:05.39-LVL5-ARTCACHE: Replacing cache entry #25
0:02:05.47-LVL5-ARTCACHE: Replacing cache entry #26
0:02:05.53-LVL3-MQ_PROCESS: Processing message: BTN_PREVPG
0:02:05.54-LVL3-MQ_PROCESS: Processing message: -BTN_PREVPG
0:02:05.58-LVL5-ARTCACHE: Found cached pointer #23
0:02:05.58-LVL5-ARTCACHE: Found cached pointer #24
0:02:05.58-LVL5-ARTCACHE: Found cached pointer #25
0:02:05.58-LVL5-ARTCACHE: Found cached pointer #26
0:02:05.58-LVL3-MQ_PROCESS: Re-processing message: BTN_PREVPG (delayed due to page turn animation)
0:02:05.58-LVL5-ARTCACHE: Replacing cache entry #27
0:02:05.61-LVL5-ARTCACHE: Replacing cache entry #28
0:02:05.63-LVL5-ARTCACHE: Replacing cache entry #0
0:02:05.65-LVL5-ARTCACHE: Replacing cache entry #1

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #9 on: November 06, 2007, 10:50:37 pm »
Hmm... ok, the image cache probably isn't the problem; it loks like you were able to get through a full cycle through the cache.

Just to be complete, though, can you change the ArtCacheMB setting in jukebox.ini to a different number, preferably an odd number like 7 amd try the test again?

Thanks!

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #10 on: November 06, 2007, 11:00:03 pm »
Same Thing again here is the results

0:00:31.09-LVL3-MQ_PROCESS: Re-processing message: BTN_PREVPG (delayed due to page turn animation)
0:00:31.10-LVL5-ARTCACHE: Replacing cache entry #38
0:00:31.12-LVL5-ARTCACHE: Replacing cache entry #39
0:00:31.14-LVL5-ARTCACHE: Replacing cache entry #40
0:00:31.16-LVL5-ARTCACHE: Replacing cache entry #41
0:00:31.20-LVL3-MQ_PROCESS: Processing message: BTN_PREVPG
0:00:31.21-LVL3-MQ_PROCESS: Processing message: -BTN_PREVPG
0:00:31.25-LVL5-ARTCACHE: Found cached pointer #38
0:00:31.26-LVL5-ARTCACHE: Found cached pointer #39
0:00:31.26-LVL5-ARTCACHE: Found cached pointer #40
0:00:31.26-LVL5-ARTCACHE: Found cached pointer #41
0:00:31.26-LVL3-MQ_PROCESS: Re-processing message: BTN_PREVPG (delayed due to page turn animation)
0:00:31.27-LVL5-ARTCACHE: Replacing cache entry #42
0:00:31.29-LVL5-ARTCACHE: Replacing cache entry #43
0:00:31.32-LVL5-ARTCACHE: Replacing cache entry #44

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #11 on: November 06, 2007, 11:24:26 pm »
Can you post the cache initialization info for that run?
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

konafan

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 8
Re: wincab Version 3.1.4 Unstable?
« Reply #12 on: November 06, 2007, 11:48:48 pm »
0:00:00.00-LVL2-ARTCACHE_INIT: ****** Initializing cover art cache ******
0:00:00.00-LVL2-ARTCACHE_INIT: Cover art size after scaling: 267x267
0:00:00.00-LVL2-ARTCACHE_INIT: Color depth: 16 bits/pixel, 2 bytes/pixel
0:00:00.00-LVL2-ARTCACHE_INIT: Bytes per cache entry: 143710 (1132 for BITMAP structure and row pointers)
0:00:00.00-LVL2-ARTCACHE_INIT: Requested cache size: 7 MB
0:00:00.00-LVL2-ARTCACHE_INIT: Cache entries: 51
0:00:00.00-LVL2-ARTCACHE_INIT: Actual cache size: 6.99 MB
0:00:00.00-LVL2-ARTCACHE_INIT: ****** Cover art cache initialization complete ******

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #13 on: February 06, 2008, 11:01:06 pm »
I'm digging up this old thread because the symptoms described look similar to what I was experiencing with old versions and still appear to manifest themselves with the new version (3.1.5).

The outline of the problem is that I start wincab, choose R for radio play and then proceed to rapidly flip through the pages until eventually wincab aborts. (Note that I tend not to do this myself but my son regularly uses the joystick to rapidly change pages, most often by going up/down one letter to get to a particular artist, whereas other people just do it to amuse themselves and be beyotches!)

Anyhoo, we're talking a song database of around 5,000 tracks at the moment split across a host of artists (it's what I consider the best songs of every artist in my collection)

My suspects for this error are to do with the cover art caching (I'm using the 6-CD album skin - cd6-1-ws) or some form of stack overflow as the message queue tries to handle an inordinate number of button/joystick presses. With Wincab 3.1.5 having a "Auto" default for ArtCacheMB (which equates to 32MB for Windows) I was wanting to see if the problem "disappeared"/was masked (since each individual cover art itself is usually only around 20kb). Hence I set DEBUG to 5, got a song playing and madly held the left mouse button depressed over the "next page" button until it fell over.

Here's some relevant extracts from the log.

Cache Initialisation:

Code: [Select]
0:00:00.29-LVL2-ARTCACHE_INIT: ****** Initializing cover art cache ******
0:00:00.29-LVL2-ARTCACHE_INIT: Cover art size after scaling: 300x300
0:00:00.29-LVL2-ARTCACHE_INIT: Color depth: 16 bits/pixel, 2 bytes/pixel
0:00:00.29-LVL2-ARTCACHE_INIT: Bytes per cache entry: 181264 (1264 for BITMAP structure and row pointers)
0:00:00.29-LVL2-ARTCACHE_INIT: Requested cache size: 32 MB
0:00:00.29-LVL2-ARTCACHE_INIT: Cache entries: 185
0:00:00.29-LVL2-ARTCACHE_INIT: Actual cache size: 31.98 MB
0:00:00.29-LVL2-ARTCACHE_INIT: ****** Cover art cache initialization complete ******

Bottom 10 lines of 42,988 lines of log:

Code: [Select]
0:01:06.19-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.19-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.19-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.20-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.20-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.20-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:06.20-LVL3-MQ_PROCESS: Processing message: BTN_NEXTPG
0:01:06.22-LVL4-ARTCACHE: Replacing cache entry #101
0:01:06.24-LVL4-ARTCACHE: Replacing cache entry #102
0:01:06.26-LVL4-ARTCACHE: Replacing cache entry #103

You'll see the last logged entry is a 'replacing cache entry'

I went nuts and set ArtCacheMB to its maximum of 1024 and tried again. Sure enough it got further this time.

Cache Initialisation:

Code: [Select]
0:00:00.27-LVL2-ARTCACHE_INIT: ****** Initializing cover art cache ******
0:00:00.27-LVL2-ARTCACHE_INIT: Cover art size after scaling: 300x300
0:00:00.27-LVL2-ARTCACHE_INIT: Color depth: 16 bits/pixel, 2 bytes/pixel
0:00:00.27-LVL2-ARTCACHE_INIT: Bytes per cache entry: 181264 (1264 for BITMAP structure and row pointers)
0:00:00.27-LVL2-ARTCACHE_INIT: Requested cache size: 1024 MB
0:00:00.27-LVL2-ARTCACHE_INIT: Cache entries: 5923
0:00:00.27-LVL2-ARTCACHE_INIT: Actual cache size: 1023.89 MB
0:00:00.27-LVL2-ARTCACHE_INIT: ****** Cover art cache initialization complete ******

Bottom 10 lines of 61,629 lines of log:

Code: [Select]
0:01:24.39-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.39-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.39-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.40-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.40-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.40-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.40-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:24.40-LVL3-MQ_PROCESS: Processing message: BTN_NEXTPG
0:01:24.42-LVL4-ARTCACHE: Creating cache entry #1402
0:01:24.45-LVL4-ARTCACHE: Creating cache entry #1403

Notice that this time there are no references to replacing cover art entries. This makes me wonder if it's not cache replacement at fault but rather an inability to keep up with button presses. On the other hand I went madly pressing... it's seems as if my son only needs to look askew at the joystick and flick it a couple of times to get it to fall over (and when he does it I usually have DEBUG disabled)

Any thoughts / extra information I can supply?
« Last Edit: February 07, 2008, 12:51:27 am by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #14 on: February 06, 2008, 11:10:06 pm »
I'll have to add a debig for the message queue filling up... I never considered it a possibility for it to overflow so I don't trap for it.  There is a failsafe that's supposed to drop messages on the floor rather than overflow but the failsafe could be buggy.
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #15 on: February 06, 2008, 11:17:23 pm »
Wow! That was a quick reply... I'd only just hit post! I'll monitor for a debug version to download and retry when ready.

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #16 on: February 06, 2008, 11:25:14 pm »
I just had a "DOH!" moment.

There are actually three message queues: the standard queue, a "timed" queue, and a retry queue.  When a key is pressed, it's message is put onto the standard queue and its release message is put onto the timed queue set for a tenth of a second later.  When its timer expires it moves its message to the main queue.

However, the key repeat rate can be set to 30 times per second... at maximum repeat speed, messages are being sent faster than the releases.  The default repeat rate is only 5 times per second.  Are you using the default rate or the maximum rate?

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #17 on: February 06, 2008, 11:56:16 pm »
Checkity-checkity-check (don't remember looking at or altering that value)... so that means:-

KeyRepeatRate = 5

If it's factored into the equation, this is running on a 3.2GhZ Dual Core processor (I went nuts cause I wanted Jukebox/Mame/Pinball/Videos/PC Games, the works...)
« Last Edit: February 06, 2008, 11:58:57 pm by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #18 on: February 07, 2008, 12:04:22 am »
Well, then it's not over-repeating.  And looking at the code the fail-safes are pretty fail-safe as far as preventing overflows.  Still, I added code that clears any existing releases before adding a new release so even if a key is pressed thirty times in a second it will only ever have one release pending.  I've also added messages to show when the delay queue fills up (there was already one on the main queue); both of these are Level 0 messages so they will show up in jbdebug.log even if the debug log is disabled.

I have not been able to reproduce the problem, but for some reason on this machine page turn animations are insanely slow which may have something to do with it.

--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #19 on: February 07, 2008, 12:10:08 am »
Hmmm... I just did a count of particular strings in the 2nd of my two logs.

The number of occurrences of the string

LVL1-DO_INPUT: Mouse button pressed, b = 1

is a staggering 26,931. (they appear to be in blocks of 5)

The number of occurrences of the string

LVL3-MQ_PROCESS: Processing message: -BTN_NEXTPG

is a comparatively tiny 239. Is one what I'm asking it to do versus what it has actually done?

No LVL0 messages appear at all.
« Last Edit: February 07, 2008, 12:15:21 am by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #20 on: February 07, 2008, 12:14:28 am »
"Mouse button pressed" isn't supposed to be there... it's a temporary messageg I forgot to remove.

Toward the end of your log, about 5 or 6 lines from the end, is an idle loop average.  What does yours read?


Thanks!

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #21 on: February 07, 2008, 12:22:49 am »
Did a search for AVERAGE. No hits.

Did a search for IDLE.

Top part shows:-

0:00:00.27-LVL5-GUI_OBJ_DUMP: 116 - x=0 y=0 w=0 h=0 d1=0 d2=0 type=Idler

Then there's some crap about Bette MIDLEr (yep, the jukebox is geared for chick music as well  :P  )

And then two messages separated further down

0:00:07.34-LVL3-MQ_PROCESS: Processing message: MSG_IDLE

and

0:00:09.49-LVL3-MQ_PROCESS: Processing message: -MSG_IDLE


No statistics found.

Visually scrolling through many pages at the end of the log only shows various combinations of lines of one of the following three flavours:-

0:01:22.60-LVL1-DO_INPUT: Mouse button pressed, b = 1
0:01:22.60-LVL3-MQ_PROCESS: Processing message: BTN_NEXTPG
0:01:22.62-LVL4-ARTCACHE: Creating cache entry #1348

Presumably I need to fire it up and not touch anything for a while to give it a chance to write one? If so I'll need to do that from home after volleyball tonight.
« Last Edit: February 07, 2008, 12:26:42 am by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #22 on: February 07, 2008, 12:31:09 am »
If the only log you have hand is one where the jukebox crashed you won't have it.  The idle counter stat is only written if it exits cleanly.

I still haven't found the problem, but there's clearly something wrong with the relationship between the turn animation and the two queues.  If you set the animation speed to 0, does it not crash?  Or perhaps does it crash faster?

Unfortunately, I need to get up early for work, so I'm going to wrap up for the night.
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #23 on: February 07, 2008, 05:30:26 pm »
Not sure how helpful this is going to be but I set

AnimationSpeed = 0

(which is disabled... was 30) as suggested. With this in place I was able to get through a whole cycle (A-Z) of the artists in my 5,000 song collection but, being a stubborn bugger, I continued holding down the mouse button to turn pages and it eventually fell over I guess somewhere around the C section on the second pass through (it was replacing artwork (cover) entries again).... this was with the ArtCacheMB = Auto (which is 32MB))

Abandoning that test for a moment I tried a few successful executions of Wincab doing various actions but keeping my page turning down to something more reasonable. Results vary for the Idle Loop Average but most times it was over 500. Off the top of my head the range was something like 426 - 528 loops per second (? not sure if that terminology is correct... going off memory this time)
« Last Edit: February 07, 2008, 05:41:32 pm by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #24 on: February 07, 2008, 10:37:49 pm »
I wonder if this is something specific to the mouse?  I haven't been able to duplicate it, but I'm holding down the PgDown key to flip, not using the mouse.... hmm...
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #25 on: February 08, 2008, 01:18:25 am »
No, not specific to the mouse. Joystick would have to be a suspect as well.... it was originally falling over when navigating using the joysticks (Ultimarc 360s connected via USB and not emulating keypresses - left/right for prev/next page, up/down for prev/next alpha) or trackball/mouse button combination.)

It's just that at the moment the (test) control panel is disconnected since I'm about to apply artwork to the true replacement metal panel before wiring it all up again.  I still have the PC setup though with a keyboard/mouse for testing purposes and continuing front-end development under Mamewah.

I can try this weekend (work's almost finished for the day) and remap nextpage to a keypress and see if I can get it to fall over.

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #26 on: February 08, 2008, 09:49:48 am »
Decided to try something different when I got home.

Set the values for FirstAutoFlipTimer and AutoFlipTimer to Disabled (used to be 60 and 30 respectively). Then I hit R for Radio and didn't touch a damn thing for well over two hours whilst I did other things and badly singing karaoke to the tunes. Worked like a charm.

I then stopped it and set the two of them to 10 and 5 respectively (which should still be way slower than me madly pressing on the mouse button). Sure enough, after 51 long minutes and 23 seconds, with it only playing a few songs via the PlayStimulator (and one wasn't playing at the time) it fell over.

I repeated this test a few times and invariably it fell over but never at the same place or at the same time ... all subsequent times were quicker (i.e. a couple of times it fell over before the first PlayStimulator kicked in)...

Don't get me wrong... the last log entry posted in jbdebug.log was ALWAYS a Replacing Cache Entry but it usually wasn't the same number to the right. One time the pages went through at least one complete cycle, possibly two (it was getting boring watching it waiting for it to fall over).

So, the only thing kicking the page turns was the automated one (CMD_NEXTPG) and it ALWAYS fell over at the same offset according to the Windows dialog box... not sure if you can track this back to the source code in question Chris but the offset was 6f502.

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #27 on: February 08, 2008, 10:21:56 am »
As an aside, there doesn't seem to be a way to turn off the caching (my theory being I have a fast machine so who needs the caching if it's causing me problems.)

I tried using 0 and Disabled (which it didn't whinge about so I guess it regards it as zero) and reviewing the log after it falls over shows it is still replacing cached entries (albeit the highest cache number was probably only 4 or 5 with disabled (I think it was 0 when I had a value of 0 set))

For the sake of completeness I also tried multiple button presses on some other skins (I'm using the 6 CD one because I have a 1920x1200 widescreen monitor). Seems like none of the strip ones fall over (at least they didn't before I got bored) which is presumably because they have no art to cache.

Some of the other CD cover art ones I tried didn't fall over but then again I didn't try them long since the Animation of the page turning slowed everything down and stuttered the song badly (remember this is running on a 3.2GHZ Duo Core as well!) and it just became annoying given it's 2 in the morning and I should be asleep.

I turned the animation off inside the skins and eventually they fell over at the same offset as well.

G'night!
« Last Edit: February 08, 2008, 10:24:07 am by wwwombat »

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #28 on: February 19, 2008, 12:40:32 am »
Any thoughts yet Chris (does the abend offset any clues)?

Alternatively, would you contemplate providing an option to turn off the caching logic (or let me know how if it can already be done) if that's a suspect?

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #29 on: February 19, 2008, 12:56:27 am »
I've played with a number of possibilities but nothing solid yet.

I have to be able to cache at least enough album covers to fit on one screen worth of the skin, because I need to scale and rotate them as needed before display.
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #30 on: March 04, 2008, 09:07:57 pm »
Assuming nothing's come to light yet can I request a possible option for the next release?

Alternatively, would you contemplate providing an option to turn off the caching logic (or let me know how if it can already be done) if that's a suspect?

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #31 on: March 05, 2008, 10:37:24 am »
Assuming nothing's come to light yet can I request a possible option for the next release?

Alternatively, would you contemplate providing an option to turn off the caching logic (or let me know how if it can already be done) if that's a suspect?
No, that's not really possible.

Each image needs to be loaded, decoded from its native format, scaled/stretched/antialiased, and rotated before it's ready for the screen.  The cache is a set of bitmap objects ready to receive the results of this loading.  For a particular skin, all cover art images are the same size; I take advantage of this by pre-allocating a number of bitmap objects equal to the cache size, along with a set of paths corresponding with them.  This way I am not continually creating and destroying bitmaps, which would lead to memory fragmentation over a period of time.

When a page is loaded, the four images are each loaded, scaled, etc. before the page change animation starts.  On an image load request, the set of path pointers is checked; if it is an image that has previously loaded, the request returns the existing image object; otherwise, it is loaded into a temporary bitmap and written into the least recently used bitmap or the next completely unused bitmap.

Without storing the post-processed images somewhere, I would have to repeat the scale/rotation/antialias every time I need to update the screen, which would get ugly during the page change.

I think the "Replacing Cache Entry" at the end of the log is a red herring: the error is not in the replacement per se, it is somewhere between there and the next entry which never makes it to the log.  I suspect my problem is in the jpg decode itself, and that whatever jpg is causing the problem is overrunning a buffer and destabilizing the system, causing it to crash sometime later.  But it's easy for me to say that because I can just say "Well, you must have a bad jpg somewhere" and fob off responsibility for it.  It would explain why no one else has reported it and I can't duplicate it, though.

How many albums are we talking about?  Would it be completely unreasonable to do a search for *.jpg on your music subfolders (with hidden and system files displayed), ZIP them all up and E-mail them to celamantia@gmail.com?  At least then I could replicate your conditions properly.

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #32 on: March 08, 2008, 01:47:16 am »
Thanks for the detailed explanation. It's very informative to know about the process behind the program.

Okay... keep in mind that I'm using the 6-CD cover skin on a 1920x1200 screen so there's a bit more loading/caching/scaling etc. going on. Some artists also exist with more than 14 'Greatest Hits' tracks (Beatles is the worst... they might get 3 or 4 "slots"). There's quite a lot of 1 or 2-hit wonders.

Also keep in mind that, due to my past problems with CD cover jpgs (as expanded upon in another post) I now save them all with particular options although I do keep some of them at a better size/resolution if I'm able to. I have managed to step through an entire cycle #-Z of all of my covers under wincab without problem (although if I do it again I can randomly fall over.. rarely in the same place). Thus I don't think any one particular cover is corrupt (but I'm willing to be told otherwise!)

The zipped up covers themselves are probably too big to email via your client (it covers 1,761 artists and runs at about 27MB by itself). Hence I've loaded it up to a mate's website and will send you the url via email separately. Won't you need a correctly tagged MP3 in each folder to trigger the display though or do you have other plans afoot (or could I provide my wincab db files and you fudge them in without wincab doing a DB update? Let me know)
« Last Edit: March 08, 2008, 01:49:28 am by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #33 on: March 09, 2008, 02:30:22 pm »
The tagging is irrelevant.  It simply uses the first image in the song's folder that matches the file mask.

As far as a corrupt JPG goes, an error could destabilize the system without crashing it completely, causing an unrelated event later to push it over the edge.
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #34 on: March 11, 2008, 04:16:17 pm »
Well I still haven't solved this.  I was going to fudge it with an auto-restart after a crash but it won't work in this case because it's dying in a way I can't intercept.  *sigh*

One thing I've noticed is that my new video card, an nVidia 8500GT, is behaving differently from the Radeon 9600Pro I was using (the animation is a LOT slower on the nVidia which is a more powerful card), so perhaps the video driver plays into this.

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #35 on: March 11, 2008, 10:30:09 pm »
Okay.... but in strange way I'm glad you're now seeing the error as well.

As an aside (or perhaps a correlation) I too am running an nVidia card on the arcade machine. It's an 8600GT and before anyone asks, its drivers are up-to-date (although that said, the OpenGL driver (nvoglnt.dll) has caused me some problems on just a couple of reasonably old PC games.

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #36 on: April 14, 2008, 07:03:59 pm »
As far as a corrupt JPG goes, an error could destabilize the system without crashing it completely, causing an unrelated event later to push it over the edge.

In an attempt to resolve this problem, and using Chris' possisble suspicion above, I took every bit of album art that I previously passed onto Chris and reprocessed them under ThumbsPlus (effectively saving them over the top of themselves as a jpg ensuring that the correct options were used) and loaded this back over the existing ones.

Initially things were looking good as I was able to scroll forwards and backwards through the list utilising both page flips and alpha page flips for quite a few "laps".

I then turned on the Auto-Flip (initial delay 180 seconds, page flip every 30 seconds thereafter) and put it on Radio Play. After 4 hours it was still going strong but sadly, oh-so-sadly, it eventually fell over at the same offset as described in the previous messages.

I'm not sure where to go from here...
« Last Edit: April 15, 2008, 06:51:56 pm by wwwombat »

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #37 on: April 23, 2008, 01:29:16 pm »
That blows a lot of theories out of the water.

I'm just going to have to learn how JPG's work and take apart my JPG library, or look for another one.

If you are willing to try another huge project, I wonder what would happen if you reprocessed that same art as BMP or PCX files?

Unfortunately, I am having additional isses with things falling over in a different way that seem to be specific to my video card and are making it harder to find what is truly the problem.
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

Chris

  • Moderator
  • Trade Count: (+2)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 4572
    • Chris's MAME Cabinet
Re: wincab Version 3.1.4 Unstable?
« Reply #38 on: May 27, 2008, 01:44:50 am »
Update on this issue:

I'm trying to add the long-planned feature of being able to switch skins on the fly.  The feature works for a few switches then crashes.  It crashes faster if one of those skins is an album skin.  To me, this implies that it's not a JPG processing problem after all, it's a memory corruption error of some sort; either a memory leak, a memory overrun, or an improper/premature memory release.  I'm picking through the code with a fine toothed comb, adding a lot of logging and sanity checks.  I believe if I find and fix the problem that is keeping skin switching from working properly, it will also fix the problem of the jukebox falling over after a number of page turns.

--Chris
--Chris
DOSCab/WinCab Jukebox: http://www.dwjukebox.com

wwwombat

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 64
Re: wincab Version 3.1.4 Unstable?
« Reply #39 on: May 29, 2008, 11:49:31 pm »
That's somewhat encouraging news Chris... I haven't had time to try the BMP reprocessing you wanted to see tested (cab has been "finished" and now available for family/friends playing and critiquing  :cheers: ), and I'm hopeful I won't have to if you eventually sniff out the supposed memory leak problem.

I'll continue to monitor this thread with interest  :notworthy:

  
 

Sitemap 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31