Web and WebWorks Development

[khafra]

My app is fairly simple:

• jquery (1.3.2) ajax request to JSON web service for a list of items
• loop through results to produce list (approx 20-30 items in the list)
• user clicks on item which initiates another ajax call for the item's details
• to exit i call system.exit() using the apis
• the app uses no custom extensions
• in the app i also use the messages and calender apis (for sending and adding reminders)

After a few sessions of using the app, i get the "Previous instance still active (report to http://go/memoryleaks)" error. I know the GC is being called as i see the spinning clock on exit.

in the application manager on OS7 i can see that the app exceeds 2MB of memory at times.

Can anyone suggest what aspects of my implementation is causing memory to leak still?

Thanks

Khafra

[khafra · Accepted solution]

I've isolated the offending script

I was using the API to handle the back key functionality (which worked as intended), somehow even on WW 2.3 SDK it still isnt releasing the back key listener. my code to handle the back key:

function trapForBackKey() {
     blackberry.system.event.onHardwareKey(blackberry.system.event.KEY_BACK, handleBack);
}

function handleBack() {

    if ($("#panel1").css("display")=="none")
   {
      showPanel(document.getElementById('tab1'), 'panel1');
   }
   else
   {
      blackberry.app.exit();
   }

}

Of course i would prefer to be able to control the back key without getting the error, but for now i'm leaving it out.

Any ideas on how to control the back key and ensure that the listener on the JAVA side gets released?

Khafra