Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Z10


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
Highlighted
Trusted Contributor
Posts: 210
Registered: ‎03-17-2013
My Device: Z-10
My Carrier: T-Mobile

Reboot/Restarts / Memory Leaks

I believe I have identified how they happen.

 

It appears that if there is a connectivity problem the memory buffers allocated by the process involved are not released even when the process is closed (the "X" is used.)  

 

This would point to some sort of problem in the cleanup for the working set of a process that gets abandoned.  It appears to be worse if the process is running in the Android sandbox, but as near as I can determine with my testing it is not limited to Android apps -- native ones also leak memory under these conditions.

 

When the system gets short enough on memory and cannot manage its way out of the box it also appears there's a watchdog somewhere in the code that forces a restart.  This is arguably good rather than bad, as memory exhaustion that arises from this sort of problem can otherwise (and in fact almost-certainly would!) lead to a deadlock, which is really bad.

 

Blackberry needs to get on this; I'd love to look at more-detailed information on the memory allocation pattern and what has RAM out under synthetic conditions to try to reproduce this, but I cannot get a shell into the phone's OS or otherwise see enough data in real-time to know exactly where it's leaking -- but all signs point toward the network stack.

Market Information? Come read The Market Ticker!