BlackBerry downloading a file - file

Question

I have a blackberry application that is downloading a file from online. Sometimes the download succeeds and other times it fails somewhere in the middle. It only seems to be a problem on the Curve 9360 device. When it fails, on the device it closes my app and shows a pop-up that says
"Uncaught exeption Application [MyApp] is not responding; process
terminated"
this is the while loop that it is in when it fails:
byte data[] = new byte[1024];
try {
while ((count = is.read(data)) != -1) {
total += count;
progress = (int)(total*100/lengthOfWebFile);
if(model.getValue() < progress){
UiApplication.getUiApplication().invokeLater(new Runnable()
{
public void run()
{
EmbeddedMediaScreen.this.model.setValue(progress);
}
});
}
//write this chunk
os.write(data, 0, count);
}
} catch (Exception e) {
e.printStackTrace();
}
I don't get any kind of stack trace in the console when this happens. I get the following:
[710.328] Application BBCurve9360DemoLoop(314) is not responding; process terminated
[710.328]
[710.429] [0 0]
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
.[lots more "0 2"s]
.
.
.
[710.429] 2 203
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
[710.429] 0 2
.[lots more "0 2"s
.
.
Has anyone run across anything like this while pro grammatically downloading a file on a blackberry device?
Can anyone see anything in my IO loop that would cause this type of crash?
And lastly does anyone know if there is someway that I can get an actual stack trace of whatever exception is being thrown?

Answer 1

To print stack trace, you have to catch throwable instead of exception. My conclusion is based on the RIM note given below
RIM Implementation Note
Only uncaught exceptions have stack traces. The VM checks the current catch stack and if it finds anything that will catch the exception, it eliminates the stack trace to save time and memory. Any code in the current stack such as catch (Exception e) eliminates the stack trace.
If the exception is never caught, then the stack trace is generated.The stack trace is also generated if there is code such as catch (Throwable t).
Also
You get a "process terminated" message if the while loop doesnt end and the loop is continually putting in runnable objects in the event thread. Try to get rid of the invokeLater() and see if your process still gets terminated.

Answer 2

Try adding Thread.yield() after os.write(). This will give other threads the opportunity to run, and should stop your app from being killed by the JVM.