12-07-2011 05:21 AM - edited 12-07-2011 05:48 AM
We've just finished developing a large, complex WebWorks application and before release our customer has been doing some testing. Unfortunately they are completely unable to run the application on a specific BOLD 9780. When they launch the app, the loading screen appears momentarily and then the app crashes with no memory warning, it just closes/disappears.
The interesting thing is the application runs fine on our own BOLD 9780 and on other devices it is just this specific BOLD 9780 that is causing the problem.
Having done thorough testing and debugging I have been able to prove that this crash has nothing to do with our application code. If I create the simplest WebWorks application possible with a single BUT LARGE htm page and a config.xml (as below) exactly the same behaviour is exhibited.
<head><title>Simple Large HTML Page</title></head>
... this same line repeated 5000 times to deliberately increase the file size of the page
<?xml version="1.0" encoding="utf-8"?>
<widget xmlns="http://www.w3.org/ns/widgets" xmlns:rim="http://www.blackberry.com/ns/widgets" version="1.0" rim:header="RIM-Widget:rim/widget">
<content src="index.htm" />
Occasionally the application will launch but if I refresh the page (using one of the many links) it will normally crash immediately. Is WebWorks not handling the memory correctly? Is there anything I can do on the device to cure this fatal issue? (Note we have already tried a factory reset)
This application is due for release last week but with such a severe and critical problem it just isn't feasible to proceed. I would really appreciate some feedback urgently, preferably from someone at BlackBerry.
I would to point our that our company has plans to develop numerous other WebWorks application for a number of other customers however unfortunately if problems like these continue to materialise the platform just is not a feasible option for development. what a shame.
Really hoping someone can help,
The problem BOLD 9780 in question has been factory reset and is running v6.0.0294, (Bundle 905, Platform 220.127.116.11)
I am building with the 18.104.22.168 version of the WebWorks Windows SDK with no template or ext modifications.
I have also checked out the "Next" branch of the SDK source code, compiled myself a copy of the most recent SDK code and built with this and the simple application still crashes in exactly the same way.
12-12-2011 11:31 AM - edited 12-12-2011 12:31 PM
OK, so we've found a Torch 9800 device with exactly the same problem and fortunately this has enabled us to do a more thorough investigation of version numbers and the like. Note we have another Torch 9800 that works perfectly. My findings are shown in the image below. Basically the two problem devices are running v22.214.171.124?? of the BlackBerry OS where as all our other devices which work fine are on v126.96.36.199?? and above.
12-12-2011 12:33 PM
I have just upgraded the Torch 9800 to 188.8.131.527 and its still having problems. Off to try the another version. Hopefully at some point it will start working and I'll have some idea at what point the BB OS was fixed.
12-13-2011 05:14 AM
Have now installed version 184.108.40.2068 on the Torch 9800 and all WebWorks application seem to run correctly now. Hurray!
There was obviously a BB OS fix for memory/garbage collection at some point between 220.127.116.117 and 18.104.22.1688. I guess we will just have to advise customers that they must upgrade to 22.214.171.1248 or higher in order to use the application, not ideal but at least its not our code or WebWorks that's the culprit.
12-13-2011 10:20 AM
I was able to easily reproduce the issue you've described. While I am in contact with the browser team, it seems like its just an out of memory error.
There is a hard limit of memory set aside for all browserfield instances (including webworks apps) and this amount appears to change between different versions of the OS.
Unfortunately I don't know of any workarounds at the moment, but I will continue investigating.
12-13-2011 10:55 AM - edited 12-13-2011 10:56 AM
Thanks for your reply jeffheifetz, nice to know someone from BlackBerry is actually reading and acknowledging. If there is any workaround possible then I would extrememly interested in knowing.
For the time being we have introduced a new light-weight "VersionCheck" page into our app that checks the device version using blackberry.system.softwareVersion. If the device is lower than v126.96.36.1998 an appropriate warning message is displayed telling the user to upgrade their OS. If the OS version is good we immediately redirect to an actual application start page (which is much larger and will cause a crash on lower OS devices).
Not ideal but at least the user doesn't just have a home screen icon for an app that always crashes!
01-20-2012 02:44 PM
Thank you for creating and contributing to this thread. I am experiencing this same issue (application crashes right after launch and sometimes opens but crashes soon after) on a Blackberry 9780 v188.8.131.525 with a Webworks application we are working on.
Can someone from RIM please confirm what OS version is the minimum version to run a Webworks application on or please direct me to where I can find this information?