[JSanders]

Originally Posted by JasonSamfield

My guess on why each of those would be running is below:

You guess? It's been discussed here many times as to why those apps are running in the background and cannot be closed.

Getting off OS .75 would be your best bet.

[JasonSamfield]

Originally Posted by JSanders

You guess? It's been discussed here many times as to why those apps are running in the background and cannot be closed.

It's anyone's guess unless they work at RIM and would like to elaborate on the reasoning of why they are persistently running. What's with the hostility?

[JSanders]

You just don't have to guess at it.

What's your empirical data say?

[JasonSamfield]

Originally Posted by JSanders

You just don't have to guess at it.

What's your empirical data say?

not everyone is omniscient like you...sorry...i guess you are a better reverse engineer than me

i don't have empirical data because i cannot isolate the applications...the system lacks that control

anyway...

for those who are actually paying attention to the decent information being provided and to stop detouring the thread

net_rim_bb_messaging_app() is the BB name of the message app, not the BlackBerry messenger app...

hopefully that tagline-string-character sequence can help future google searches and forum searches for information pertaining to why the message app can crash...maybe low memory or leaking memory because of the OS...who knows at this point..maybe jsanders knows..he seems pretty knowledgeable about this stuff...what do you think?

[JSanders]

Two things:

1) Have you examined your event log?

2) I mentioned a day or so ago that for what you want you should hire a developer to build your desired app. How's the progress there?

[JasonSamfield]

I'm going to develop the apps (task manager and start-up configuration manager) myself. I've just got to learn some more about the secret internals and get a better handle on the API.

The event log hasn't shown me much yet as to what the problems are exactly. I'm still working on getting any information from them that coincides with my apparent problems. By turning on debug level logging, it takes more memory usage and in effect triggers more problems, so it's almost a catch 22 situation.