Web and WebWorks Development

[Saeger]

If you need beta testers, i could be !!
I really need this fix! Thanks!

[oyvindsh]

Any update on this matter?

[tneil]

v2.1.1 should be out in the next couple days

[Saeger]

Nice!!
But, what about the SDK 2.1.* version ?
I mean... i read somewhere else around here saying that 2.1 doesn't work for webworks anymore.. ?

[tneil]

Hi Saeger,

I'm not sure I understand your question... If you are referring to the WebWorks plug-ins for Visual Studio and Eclipse... they only can support up to v2.0 of the WebWorks SDK. Those plug-ins have been End of Lifed and will not be recieving any more updates.

[Saeger]

So, for the emulator of the plugin, it will compile on sdk 2.0.0
I'll have to compile with 2.1.1 and put into the device manually to test the app?

[tneil]

Yes, with 2.1.1 you will need to build with the command lind and then drag/drop the cod file onto the runnig emulator

[Saeger]

Hello guys,

I updated my SDK to the v.2.1.1 and used it to compile my application again.

Result: Same memory leak problem... I'm still stuck at this point...

I just move the device for a few seconds and i got this problem.

I don't know what to do anymore. The problem only occour in the BlackBerry OS 6. In the OS5, it's not getting the memory leak.

I'll do this: I uploaded my application to my private server. You can download the zip (contains the standarInstall and the fonts of my application)

Link: http://download.marciosaeger.com.br/MemoryLeakApp.zip

To reproduce the memory leak, just follow the menu: "Cadastro de CLiente" then a little freeze will occour (creating default data). Then some registry will appear in the grid (with photo and so on..) Click on the registry "Marcio".

Then, with the registry opened, click in the button "Editar" (in the top).

Then take some pictures for example, try to save the registry or something. Memory leak will occour. See the image below:

[Saeger]

PS: the message in the phone is "There's a few memory available in the device. Close some itens below.", but in portuguese...

[tneil]

We are still tracking down other sources of memory leaks.. the JavaScript extension leaks have been cleaned-up.  We are trying to get to the bottom of images being used in the DOM not freeing themselves between page transistions.  This could be in the Java Browser Field API we use which is part of the OS, or it could be in the WebWorks template code.

We still need to get to the root of the issue... it is a top priority for the team... memory leaks are plain hard to track down.