Errors from AppTestLite

Hi Steve

It may be that there are no errors. N90 is based on S60 v3, and as you will
see from www.symbiansigned.com, there is no version of apptestlite (yet) for
S60 v3. If you are using the one for UIQ3, this might explain your errors.

Regards
Hamish

"Steve" <[email protected]> wrote in message
news:[email protected]...
> I've tried running AppTestLite on my game on an N90 and it comes back
> with 4 errors that I can't see as errors in my game.
>
> 1: FAILED PKG-04 Uninstall provides complete removal of all files
> and the installed data.
>
> The only errors I can see in the log are:
>
> <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> C:\Private\101F7989\</log>
> <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> C:\Private\101F7989\sms\</log>
> <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> C:\Private\101F7989\sms\smsreast.dat</log>
> <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> C:\Private\101F7989\sms\smssegst.dat</log>
> <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> C:\Private\101F7989\sms\wapreast.dat</log>
>
> Which indicates the only problem is the test suite itself creating new
> files.
>
> 2: FAILED PKG-07 UID and version for platform compatibility is
> appropriate for the target device.
>
> Not sure what's up here, the relevant parts from my .pkg file are:
>
> #{"Oval Racer"},(0x10003FF4),0,54,0
> ; Supports Nokia Series60 Platform 2.0 Specific features
> (0x10200BAB),0,0,0,{"Series60ProductID"}
>
> Any idea what the problem is?
>
> 3: FAILED PHN-01 Service Interruption. (call, SMS, MMS, alarm,
> charger)
>
> The relevant part from the log I can see is:
> <log time="144.234375" type="dll" name="AppScreenMonitor">Searching
> for image 'C:\system\apps\apptestlite\tests\alarm.png'.</log>
> <log time="159.375000" type="dll" name="AppScreenMonitor">Timeout
> expired. Execution terminated.</log>
>
> I'm guessing it might be to do with the app running in v8.0
> compatibilty mode, or that it uses OpenGL ES direct screen access
> which might affect the ability of the test suite to read back from the
> screen. But it certainly looks fine when I test this manually.
>
> 4: FAILED MEM-01 Low Memory Startup.
> I've run my own extensive low mem tests which showed up nothing wrong
> under WINS. So test it on real hardware I hacked some code into my
> start up to alloc then free a huge amount of memory which I could then
> move around the startup code to try and narrow down where the error
> occured.
>
> It seemed that putting this right at the start still hit the errors
> indicating that they are most likely in the system code not mine.
>
> These errors seem to occur before the code even hits my appui
> constructl
> <log time="3.062500" type="dll" name="AtStartupTester">[heap 24576
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.125000" type="dll" name="AtStartupTester">[heap 25600
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.171875" type="dll" name="AtStartupTester">[heap 26624
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.218750" type="dll" name="AtStartupTester">[heap 27648
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.265625" type="dll" name="AtStartupTester">[heap 28672
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.359375" type="dll" name="AtStartupTester">[heap 29696
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.406250" type="dll" name="AtStartupTester">[heap 30720
> bytes] Panic: Font Utilities 0 in phase Construction</log>
> <log time="3.468750" type="dll" name="AtStartupTester">[heap 31744
> bytes] Panic: Font Utilities 0 in phase Construction</log>
>
> After those when it gets to my massive alloc I then get a ton of the
> following errors:
>
> <log time="3.656250" type="dll" name="AtStartupTester">[heap 32768
> bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> <log time="3.828125" type="dll" name="AtStartupTester">[heap 33792
> bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> <log time="4.015625" type="dll" name="AtStartupTester">[heap 34816
> bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> <log time="4.203125" type="dll" name="AtStartupTester">[heap 35840
> bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
>
> with finally later on as the heap gets bigger finally getting a load
> of these errors:
>
> <log time="88.515625" type="dll" name="AtStartupTester">[heap 152576
> bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> <log time="89.656250" type="dll" name="AtStartupTester">[heap 153600
> bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
>
> All these seem to be happening as a result of hitting my instant leave
> where I allocate 200K right at the start of my appui ConstructL so I
> can't see they're anything I'm doing wrong.
>
> Does seem a bit much that the we're expected to pass symbian signed
> tests haven't even been run on the builit in app startup code.
> http://www.GreatApe.com
> http://www.Oval-Racer.com

Correction. N90 is based on v8.1.

"Hamish Willee" <[email protected]> wrote in message
news:[email protected]...
> Hi Steve
>
> It may be that there are no errors. N90 is based on S60 v3, and as you
will
> see from www.symbiansigned.com, there is no version of apptestlite (yet)
for
> S60 v3. If you are using the one for UIQ3, this might explain your errors.
>
> Regards
> Hamish
>
> "Steve" <[email protected]> wrote in message
> news:[email protected]...[color=green]
> > I've tried running AppTestLite on my game on an N90 and it comes back
> > with 4 errors that I can't see as errors in my game.
> >
> > 1: FAILED PKG-04 Uninstall provides complete removal of all files
> > and the installed data.
> >
> > The only errors I can see in the log are:
> >
> > <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> > C:\Private\101F7989\</log>
> > <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> > C:\Private\101F7989\sms\</log>
> > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > C:\Private\101F7989\sms\smsreast.dat</log>
> > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > C:\Private\101F7989\sms\smssegst.dat</log>
> > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > C:\Private\101F7989\sms\wapreast.dat</log>
> >
> > Which indicates the only problem is the test suite itself creating new
> > files.
> >
> > 2: FAILED PKG-07 UID and version for platform compatibility is
> > appropriate for the target device.
> >
> > Not sure what's up here, the relevant parts from my .pkg file are:
> >
> > #{"Oval Racer"},(0x10003FF4),0,54,0
> > ; Supports Nokia Series60 Platform 2.0 Specific features
> > (0x10200BAB),0,0,0,{"Series60ProductID"}
> >
> > Any idea what the problem is?
> >
> > 3: FAILED PHN-01 Service Interruption. (call, SMS, MMS, alarm,
> > charger)
> >
> > The relevant part from the log I can see is:
> > <log time="144.234375" type="dll" name="AppScreenMonitor">Searching
> > for image 'C:\system\apps\apptestlite\tests\alarm.png'.</log>
> > <log time="159.375000" type="dll" name="AppScreenMonitor">Timeout
> > expired. Execution terminated.</log>
> >
> > I'm guessing it might be to do with the app running in v8.0
> > compatibilty mode, or that it uses OpenGL ES direct screen access
> > which might affect the ability of the test suite to read back from the
> > screen. But it certainly looks fine when I test this manually.
> >
> > 4: FAILED MEM-01 Low Memory Startup.
> > I've run my own extensive low mem tests which showed up nothing wrong
> > under WINS. So test it on real hardware I hacked some code into my
> > start up to alloc then free a huge amount of memory which I could then
> > move around the startup code to try and narrow down where the error
> > occured.
> >
> > It seemed that putting this right at the start still hit the errors
> > indicating that they are most likely in the system code not mine.
> >
> > These errors seem to occur before the code even hits my appui
> > constructl
> > <log time="3.062500" type="dll" name="AtStartupTester">[heap 24576
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.125000" type="dll" name="AtStartupTester">[heap 25600
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.171875" type="dll" name="AtStartupTester">[heap 26624
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.218750" type="dll" name="AtStartupTester">[heap 27648
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.265625" type="dll" name="AtStartupTester">[heap 28672
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.359375" type="dll" name="AtStartupTester">[heap 29696
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.406250" type="dll" name="AtStartupTester">[heap 30720
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > <log time="3.468750" type="dll" name="AtStartupTester">[heap 31744
> > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >
> > After those when it gets to my massive alloc I then get a ton of the
> > following errors:
> >
> > <log time="3.656250" type="dll" name="AtStartupTester">[heap 32768
> > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > <log time="3.828125" type="dll" name="AtStartupTester">[heap 33792
> > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > <log time="4.015625" type="dll" name="AtStartupTester">[heap 34816
> > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > <log time="4.203125" type="dll" name="AtStartupTester">[heap 35840
> > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> >
> > with finally later on as the heap gets bigger finally getting a load
> > of these errors:
> >
> > <log time="88.515625" type="dll" name="AtStartupTester">[heap 152576
> > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> > <log time="89.656250" type="dll" name="AtStartupTester">[heap 153600
> > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> >
> > All these seem to be happening as a result of hitting my instant leave
> > where I allocate 200K right at the start of my appui ConstructL so I
> > can't see they're anything I'm doing wrong.
> >
> > Does seem a bit much that the we're expected to pass symbian signed
> > tests haven't even been run on the builit in app startup code.
> > http://www.GreatApe.com
> > http://www.Oval-Racer.com
>
>[/color]

OK, so spent a little more time on this. See comments below preceeded by ##

"Hamish Willee" <[email protected]> wrote in message
news:[email protected]...
> Correction. N90 is based on v8.1.
>
> "Hamish Willee" <[email protected]> wrote in message
> news:[email protected]...[color=green]
> > Hi Steve
> >
> > It may be that there are no errors. N90 is based on S60 v3, and as you
> will
> > see from www.symbiansigned.com, there is no version of apptestlite (yet)
> for
> > S60 v3. If you are using the one for UIQ3, this might explain your[/color]
errors.[color=green]
> >
> > Regards
> > Hamish
> >
> > "Steve" <[email protected]> wrote in message
> > news:[email protected]...[color=darkred]
> > > I've tried running AppTestLite on my game on an N90 and it comes back
> > > with 4 errors that I can't see as errors in my game.
> > >
> > > 1: FAILED PKG-04 Uninstall provides complete removal of all files
> > > and the installed data.
> > >
> > > The only errors I can see in the log are:
> > >
> > > <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> > > C:\Private\101F7989\</log>
> > > <log time="21.812500" type="dll" name="AtFileSnapshot">NEW
> > > C:\Private\101F7989\sms\</log>
> > > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > > C:\Private\101F7989\sms\smsreast.dat</log>
> > > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > > C:\Private\101F7989\sms\smssegst.dat</log>
> > > <log time="21.828125" type="dll" name="AtFileSnapshot">NEW
> > > C:\Private\101F7989\sms\wapreast.dat</log>
> > >
> > > Which indicates the only problem is the test suite itself creating new
> > > files.
> > >
> > > 2: FAILED PKG-07 UID and version for platform compatibility is
> > > appropriate for the target device.
> > >
> > > Not sure what's up here, the relevant parts from my .pkg file are:
> > >
> > > #{"Oval Racer"},(0x10003FF4),0,54,0
> > > ; Supports Nokia Series60 Platform 2.0 Specific features
> > > (0x10200BAB),0,0,0,{"Series60ProductID"}
> > >
> > > Any idea what the problem is?[/color][/color]

## Try UID 0x102032BD, the value for S60 v2 FP3. I'm guessing that it simply
checks against product ID for this device and pops up the warning (which
would be a bug)
[color=green][color=darkred]
> > >
> > > 3: FAILED PHN-01 Service Interruption. (call, SMS, MMS, alarm,
> > > charger)
> > >
> > > The relevant part from the log I can see is:
> > > <log time="144.234375" type="dll" name="AppScreenMonitor">Searching
> > > for image 'C:\system\apps\apptestlite\tests\alarm.png'.</log>
> > > <log time="159.375000" type="dll" name="AppScreenMonitor">Timeout
> > > expired. Execution terminated.</log>
> > >
> > > I'm guessing it might be to do with the app running in v8.0
> > > compatibilty mode, or that it uses OpenGL ES direct screen access
> > > which might affect the ability of the test suite to read back from the
> > > screen. But it certainly looks fine when I test this manually.[/color][/color]

## Could be as you've said. Certainly SymbianSigned test house will run the
test manually.
[color=green][color=darkred]
> > >
> > > 4: FAILED MEM-01 Low Memory Startup.
> > > I've run my own extensive low mem tests which showed up nothing wrong
> > > under WINS. So test it on real hardware I hacked some code into my
> > > start up to alloc then free a huge amount of memory which I could then
> > > move around the startup code to try and narrow down where the error
> > > occured.
> > >
> > > It seemed that putting this right at the start still hit the errors
> > > indicating that they are most likely in the system code not mine.
> > >
> > > These errors seem to occur before the code even hits my appui
> > > constructl
> > > <log time="3.062500" type="dll" name="AtStartupTester">[heap 24576
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.125000" type="dll" name="AtStartupTester">[heap 25600
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.171875" type="dll" name="AtStartupTester">[heap 26624
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.218750" type="dll" name="AtStartupTester">[heap 27648
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.265625" type="dll" name="AtStartupTester">[heap 28672
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.359375" type="dll" name="AtStartupTester">[heap 29696
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.406250" type="dll" name="AtStartupTester">[heap 30720
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > > <log time="3.468750" type="dll" name="AtStartupTester">[heap 31744
> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> > >
> > > After those when it gets to my massive alloc I then get a ton of the
> > > following errors:
> > >
> > > <log time="3.656250" type="dll" name="AtStartupTester">[heap 32768
> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > > <log time="3.828125" type="dll" name="AtStartupTester">[heap 33792
> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > > <log time="4.015625" type="dll" name="AtStartupTester">[heap 34816
> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > > <log time="4.203125" type="dll" name="AtStartupTester">[heap 35840
> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> > >
> > > with finally later on as the heap gets bigger finally getting a load
> > > of these errors:
> > >
> > > <log time="88.515625" type="dll" name="AtStartupTester">[heap 152576
> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> > > <log time="89.656250" type="dll" name="AtStartupTester">[heap 153600
> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> > >
> > > All these seem to be happening as a result of hitting my instant leave
> > > where I allocate 200K right at the start of my appui ConstructL so I
> > > can't see they're anything I'm doing wrong.
> > >
> > > Does seem a bit much that the we're expected to pass symbian signed
> > > tests haven't even been run on the builit in app startup code.
> > > http://www.GreatApe.com
> > > http://www.Oval-Racer.com
> >[/color][/color]

## What happens on low mem if you run using TOOL2? This tool starts testing
above the area where there are known low memory issues with S60 application
framework.
[color=green]
> >
>
>[/color]

On Fri, 22 Sep 2006 05:38:12 -0000, "Hamish Willee"
<[email protected]> wrote:

>OK, so spent a little more time on this. See comments below preceeded by ##
>
>
>## Try UID 0x102032BD, the value for S60 v2 FP3. I'm guessing that it simply
>checks against product ID for this device and pops up the warning (which
>would be a bug)

I've tried doing that on the N90, and also running with the original
on a 6680 and both are failing, so guess that's not the issue.

Unfortunately there's no extra log created for this test so hard to
get any idea what's wrong.
[color=green][color=darkred]
>> > >
>> > > 3: FAILED PHN-01 Service Interruption. (call, SMS, MMS, alarm,
>> > > charger)
>> > >
>> > > The relevant part from the log I can see is:
>> > > <log time="144.234375" type="dll" name="AppScreenMonitor">Searching
>> > > for image 'C:\system\apps\apptestlite\tests\alarm.png'.</log>
>> > > <log time="159.375000" type="dll" name="AppScreenMonitor">Timeout
>> > > expired. Execution terminated.</log>
>> > >
>> > > I'm guessing it might be to do with the app running in v8.0
>> > > compatibilty mode, or that it uses OpenGL ES direct screen access
>> > > which might affect the ability of the test suite to read back from the
>> > > screen. But it certainly looks fine when I test this manually.[/color]
>
>## Could be as you've said. Certainly SymbianSigned test house will run the
>test manually.[/color]

Think I'll just assume this one is done to something in the test
suite, quite complicated to handle automating this sort of test and
easy for it to get it wrong somehow.
[color=green][color=darkred]
>> > >
>> > > 4: FAILED MEM-01 Low Memory Startup.
>> > > I've run my own extensive low mem tests which showed up nothing wrong
>> > > under WINS. So test it on real hardware I hacked some code into my
>> > > start up to alloc then free a huge amount of memory which I could then
>> > > move around the startup code to try and narrow down where the error
>> > > occured.
>> > >
>> > > It seemed that putting this right at the start still hit the errors
>> > > indicating that they are most likely in the system code not mine.
>> > >
>> > > These errors seem to occur before the code even hits my appui
>> > > constructl
>> > > <log time="3.062500" type="dll" name="AtStartupTester">[heap 24576
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.125000" type="dll" name="AtStartupTester">[heap 25600
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.171875" type="dll" name="AtStartupTester">[heap 26624
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.218750" type="dll" name="AtStartupTester">[heap 27648
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.265625" type="dll" name="AtStartupTester">[heap 28672
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.359375" type="dll" name="AtStartupTester">[heap 29696
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.406250" type="dll" name="AtStartupTester">[heap 30720
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > > <log time="3.468750" type="dll" name="AtStartupTester">[heap 31744
>> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
>> > >
>> > > After those when it gets to my massive alloc I then get a ton of the
>> > > following errors:
>> > >
>> > > <log time="3.656250" type="dll" name="AtStartupTester">[heap 32768
>> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
>> > > <log time="3.828125" type="dll" name="AtStartupTester">[heap 33792
>> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
>> > > <log time="4.015625" type="dll" name="AtStartupTester">[heap 34816
>> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
>> > > <log time="4.203125" type="dll" name="AtStartupTester">[heap 35840
>> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
>> > >
>> > > with finally later on as the heap gets bigger finally getting a load
>> > > of these errors:
>> > >
>> > > <log time="88.515625" type="dll" name="AtStartupTester">[heap 152576
>> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
>> > > <log time="89.656250" type="dll" name="AtStartupTester">[heap 153600
>> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
>> > >
>> > > All these seem to be happening as a result of hitting my instant leave
>> > > where I allocate 200K right at the start of my appui ConstructL so I
>> > > can't see they're anything I'm doing wrong.
>> > >
>> > > Does seem a bit much that the we're expected to pass symbian signed
>> > > tests haven't even been run on the builit in app startup code.
>> > > http://www.GreatApe.com
>> > > http://www.Oval-Racer.com
>> >[/color]
>
>## What happens on low mem if you run using TOOL2? This tool starts testing
>above the area where there are known low memory issues with S60 application
>framework.[/color]

Is TOOL2 another program I can download from Symbian Signed? Stuck for
access to that at the moment (see forgotten password thread 😊)

I've tried the normal low mem tool and with the massive alloc cheat at
the start it reports no failures, but 21 mem leaks.

The same code on my 6680 passed the lowmem test, so could be v8.1
changes causing more problems in the rom code resulting in the
failure.
http://www.GreatApe.com
http://www.Oval-Racer.com

Lowmem = TOOL2.
This tool comes with a calibration app you can use to find the minimum OK
setting for a particular phone - so find the minimum calibration first, then
if you have any errors over and above that setting, they are almost
certainly in your application.

Regards
H

"Steve" <[email protected]> wrote in message
news😛[email protected]...
> On Fri, 22 Sep 2006 05:38:12 -0000, "Hamish Willee"
> <[email protected]> wrote:
>[color=green]
> >OK, so spent a little more time on this. See comments below preceeded by[/color]
##[color=green]
> >
> >
> >## Try UID 0x102032BD, the value for S60 v2 FP3. I'm guessing that it[/color]
simply[color=green]
> >checks against product ID for this device and pops up the warning (which
> >would be a bug)
>
> I've tried doing that on the N90, and also running with the original
> on a 6680 and both are failing, so guess that's not the issue.
>
> Unfortunately there's no extra log created for this test so hard to
> get any idea what's wrong.
>[color=darkred]
> >> > >
> >> > > 3: FAILED PHN-01 Service Interruption. (call, SMS, MMS, alarm,
> >> > > charger)
> >> > >
> >> > > The relevant part from the log I can see is:
> >> > > <log time="144.234375" type="dll"[/color][/color]
name="AppScreenMonitor">Searching[color=green][color=darkred]
> >> > > for image 'C:\system\apps\apptestlite\tests\alarm.png'.</log>
> >> > > <log time="159.375000" type="dll" name="AppScreenMonitor">Timeout
> >> > > expired. Execution terminated.</log>
> >> > >
> >> > > I'm guessing it might be to do with the app running in v8.0
> >> > > compatibilty mode, or that it uses OpenGL ES direct screen access
> >> > > which might affect the ability of the test suite to read back from[/color][/color]
the[color=green][color=darkred]
> >> > > screen. But it certainly looks fine when I test this manually.
> >
> >## Could be as you've said. Certainly SymbianSigned test house will run[/color][/color]
the[color=green]
> >test manually.
>
> Think I'll just assume this one is done to something in the test
> suite, quite complicated to handle automating this sort of test and
> easy for it to get it wrong somehow.
>[color=darkred]
> >> > >
> >> > > 4: FAILED MEM-01 Low Memory Startup.
> >> > > I've run my own extensive low mem tests which showed up nothing[/color][/color]
wrong[color=green][color=darkred]
> >> > > under WINS. So test it on real hardware I hacked some code into my
> >> > > start up to alloc then free a huge amount of memory which I could[/color][/color]
then[color=green][color=darkred]
> >> > > move around the startup code to try and narrow down where the error
> >> > > occured.
> >> > >
> >> > > It seemed that putting this right at the start still hit the errors
> >> > > indicating that they are most likely in the system code not mine.
> >> > >
> >> > > These errors seem to occur before the code even hits my appui
> >> > > constructl
> >> > > <log time="3.062500" type="dll" name="AtStartupTester">[heap[/color][/color]
24576[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.125000" type="dll" name="AtStartupTester">[heap[/color][/color]
25600[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.171875" type="dll" name="AtStartupTester">[heap[/color][/color]
26624[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.218750" type="dll" name="AtStartupTester">[heap[/color][/color]
27648[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.265625" type="dll" name="AtStartupTester">[heap[/color][/color]
28672[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.359375" type="dll" name="AtStartupTester">[heap[/color][/color]
29696[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.406250" type="dll" name="AtStartupTester">[heap[/color][/color]
30720[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > > <log time="3.468750" type="dll" name="AtStartupTester">[heap[/color][/color]
31744[color=green][color=darkred]
> >> > > bytes] Panic: Font Utilities 0 in phase Construction</log>
> >> > >
> >> > > After those when it gets to my massive alloc I then get a ton of[/color][/color]
the[color=green][color=darkred]
> >> > > following errors:
> >> > >
> >> > > <log time="3.656250" type="dll" name="AtStartupTester">[heap 32768
> >> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> >> > > <log time="3.828125" type="dll" name="AtStartupTester">[heap[/color][/color]
33792[color=green][color=darkred]
> >> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> >> > > <log time="4.015625" type="dll" name="AtStartupTester">[heap[/color][/color]
34816[color=green][color=darkred]
> >> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> >> > > <log time="4.203125" type="dll" name="AtStartupTester">[heap[/color][/color]
35840[color=green][color=darkred]
> >> > > bytes] leaked 20 heap cell(s), 3 handle(s) and 0 request(s)</log>
> >> > >
> >> > > with finally later on as the heap gets bigger finally getting a[/color][/color]
load[color=green][color=darkred]
> >> > > of these errors:
> >> > >
> >> > > <log time="88.515625" type="dll" name="AtStartupTester">[heap[/color][/color]
152576[color=green][color=darkred]
> >> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> >> > > <log time="89.656250" type="dll" name="AtStartupTester">[heap[/color][/color]
153600[color=green][color=darkred]
> >> > > bytes] Panic: KERN-EXEC 3 in phase DestroyEnvironment</log>
> >> > >
> >> > > All these seem to be happening as a result of hitting my instant[/color][/color]
leave[color=green][color=darkred]
> >> > > where I allocate 200K right at the start of my appui ConstructL so[/color][/color]
I[color=green][color=darkred]
> >> > > can't see they're anything I'm doing wrong.
> >> > >
> >> > > Does seem a bit much that the we're expected to pass symbian signed
> >> > > tests haven't even been run on the builit in app startup code.
> >> > > http://www.GreatApe.com
> >> > > http://www.Oval-Racer.com
> >> >
> >
> >## What happens on low mem if you run using TOOL2? This tool starts[/color][/color]
testing[color=green]
> >above the area where there are known low memory issues with S60[/color]
application[color=green]
> >framework.
>
> Is TOOL2 another program I can download from Symbian Signed? Stuck for
> access to that at the moment (see forgotten password thread 😊)
>
> I've tried the normal low mem tool and with the massive alloc cheat at
> the start it reports no failures, but 21 mem leaks.
>
> The same code on my 6680 passed the lowmem test, so could be v8.1
> changes causing more problems in the rom code resulting in the
> failure.
> http://www.GreatApe.com
> http://www.Oval-Racer.com[/color]