Grinder problem | developer.brewmp.com Grinder problem | developer.brewmp.com

Developer

Grinder problem

Forums:

I'm having trouble with the Grinder. I've done a number of grinds, both on the emulator and on the LGE VX4400. I've hit a consistent problem, where the emulator dies in the same place every time, whether I'm grinding the phone or the emulator (the phone does not die, but keeps on playing, however.)

I'm using the attached custom events file. It always dies on event 48. I've tried the 1.1, 2.0 and 2.1 emulators, all same behavior, which I guess is not surprising since its the same Grinder.

If I take all the number keys out of the events file, it does not die.

If I slow it down to one event per second, it still dies.

If I change my app to handle only EVT_APP_START, it still dies.

If I grind "Lord of the Rings" on the phone rather than my app, it still dies.

Sure looks like something about the Grinder. Here is the log:

====================================================================================
Date (MM/DD/YY), Time (HH:MM:SS.Milliseconds), Event Number, Character/KeyCode
====================================================================================
Brew(TM) Version 1.1.0.18

The Grinder(TM) Version 2.1.1.4

12/04/03,14:28:39.838,1,0
12/04/03,14:28:40.128,2,3
12/04/03,14:28:40.419,3,RIGHT
12/04/03,14:28:40.709,4,9
12/04/03,14:28:40.999,5,6
12/04/03,14:28:41.420,6,p
12/04/03,14:28:41.640,7,LEFT
12/04/03,14:28:42.652,8,v
12/04/03,14:28:42.882,9,SELECT
12/04/03,14:28:43.914,10,y
12/04/03,14:28:44.184,11,SELECT
12/04/03,14:28:44.935,12,K
12/04/03,14:28:45.346,13,DOWN
12/04/03,14:28:46.227,14,e
12/04/03,14:28:46.517,15,9
12/04/03,14:28:47.399,16,n
12/04/03,14:28:47.699,17,5
12/04/03,14:28:48.190,18,p
12/04/03,14:28:48.490,19,0
12/04/03,14:28:49.792,20,v
12/04/03,14:28:50.213,21,1
12/04/03,14:28:51.725,22,y
12/04/03,14:28:52.025,23,6
12/04/03,14:28:52.937,24,K
12/04/03,14:28:53.267,25,2
12/04/03,14:28:54.128,26,e
12/04/03,14:28:54.369,27,3
12/04/03,14:28:55.160,28,n
12/04/03,14:28:55.420,29,SELECT
12/04/03,14:28:55.881,30,p
12/04/03,14:28:56.151,31,8
12/04/03,14:28:57.323,32,v
12/04/03,14:28:57.563,33,2
12/04/03,14:28:58.735,34,y
12/04/03,14:28:58.965,35,0
12/04/03,14:28:59.816,36,K
12/04/03,14:29:00.057,37,0
12/04/03,14:29:00.948,38,e
12/04/03,14:29:01.198,39,7
12/04/03,14:29:02.010,40,n
12/04/03,14:29:02.250,41,SELECT
12/04/03,14:29:02.691,42,p
12/04/03,14:29:02.951,43,UP
12/04/03,14:29:04.093,44,v
12/04/03,14:29:04.343,45,8
12/04/03,14:29:05.485,46,y
12/04/03,14:29:05.735,47,6
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 01576858 01:00005858 J:\Program Files\BREW v11\bin\Grinder.dll

Any suggestions?

Kelton

Hi Kelton,
We'll be testing our game on the grinder in the next few days. I'll try this sequence and let you know what happens.

Hi Kelton,
We'll be testing our game on the grinder in the next few days. I'll try this sequence and let you know what happens.

Hey Ed :)
I'm suspecting the problem is related to the use of the custom events file. Something bad about the file.
Tracked down a race condition, and just did a 50 minute grind on the VX4400. I think we're close.
Kelton

Hey Ed :)
I'm suspecting the problem is related to the use of the custom events file. Something bad about the file.
Tracked down a race condition, and just did a 50 minute grind on the VX4400. I think we're close.
Kelton

I tested this on several emulators with our game and it crashed in the same way. Considering we can run the grinder normally all day without a problem, I agree this seems like a problem with the custom events file.
The only other possibility seems to be that this sequence of events triggers some bug common between both our apps, and is not be replicated even with long runs of the grinder.
How did you come by this particular event sequence?

I tested this on several emulators with our game and it crashed in the same way. Considering we can run the grinder normally all day without a problem, I agree this seems like a problem with the custom events file.
The only other possibility seems to be that this sequence of events triggers some bug common between both our apps, and is not be replicated even with long runs of the grinder.
How did you come by this particular event sequence?

Ed,
I had a crash due to the afore-mentioned race condition, and I made up the events file from the sequence of keys that caused the crash. Probably an incorrect use of the file, though it made sense.
Kelton

Ed,
I had a crash due to the afore-mentioned race condition, and I made up the events file from the sequence of keys that caused the crash. Probably an incorrect use of the file, though it made sense.
Kelton