01-23-2013 04:45 PM
I have a problem where if i run my app on the dev alpha device and then exit the app the battery is draining after a couple of hours and the device is warm as if it is doing work but when i look at target navigator view i see that the process for my app is not there (as a running process) after I exit.
The app involves socket connections and some qt controls.
Is it possible I maybe doing something incorrect to cause the battery to drain - what should I be looking out for? I am new to native development coming from java and I obviously dont want complaints from users.
Thanks for any advice you can offer me.
01-24-2013 08:09 AM
01-24-2013 08:48 AM
I will look more into it and see if it is worth doing as you say with issue tracker.
Unfortunatley it does seem to happen only when one of my/any apps has been accessed and then closed.
01-24-2013 06:58 PM
01-24-2013 07:01 PM
Once your app quits (whether normally or abnormally), it really isn't your responsibility anymore.
You should build a very minimal test case, file it on the Developer Issue Tracker, ask them to make it public, and post the link here. That will help us in the community try to avoid the issue, perhaps help you work around it, and allow us to show RIM support for getting the core problem fixed.
01-24-2013 07:08 PM
Thanks for your reply,
I just don't think I should be seeing a sigsegv error when closing the app whilst its debugging as I don't see an error when closing another one of my apps whilst debugging. So it means it's not exiting gracefully.
It's also strange that the sigsegv occurs after all my code is executed and I can't understand why.
01-24-2013 07:12 PM
01-25-2013 08:27 AM
I have just found QBBWindow: failed to set window z-order=2, errno=22, mWindow=0x08186280 at the end of the console output (after last line of code has been executed in int main) which I haven't seen before.
What does this mean?
I am using ndk 10, QtGui and QtCore and I also mix a native screen with a QMainWindow for the purposes of the application.
Hopefully now I can see the cause of the segmentation fault.