View Single Post
Old May 1st, 2013, 11:07 PM   #176 (permalink)
The PearlyMon
EarlyMon's Avatar
Join Date: Jun 2010
Location: New Mexico, USA
Posts: 46,377
Device(s): M8, LTEvo, 3vo, and Shift - Evo retired
Carrier: Sprint

Thanks: 42,731
Thanked 57,187 Times in 22,979 Posts

Probably a runaway app, most likely what we call a race condition. Apps naturally parallelize using constructs that we call threads. Think of it this way - for listening to music, the app may have a thread for the display updates, a thread to sense inputs and one for actually playing music. (That's an insanely simplified fictional example, but good enough for the idea - threads can run in parallel.)

And quite often, threads will rendezvous with one another for control purposes.

Every so often, you get a bug where they won't, they just hang waiting for each other.

Or, you can get the condition where they spin out of control missing the rendezvous at top speed - and Android will automagically distribute threads across CPU cores. And spinning threads racing each other can and will do that across multiple cores at top speed. Drawing max power and dissipating it as heat.

If it comes back, you have a flakey app somewhere.

If it doesn't, you could have just had a single bit in ram stuck for a while, and coincidentally at the point that would induce the race condition.

Minutus cantorum, minutus balorum, minutus carborata descendum pantorum.

Links: Site Rules / Guidelines -and- Zero Tolerance Policy (All Members Read)

For right-on help, the Thanks button is on the right of the post.
For anything out in left field, the /!\ report button is to the left.

Remember, it's our forums and we're all in this together - so let's keep it cool!

Shoot the breeze at the best new gun forum!
EarlyMon is offline  
Reply With Quote
The Following 2 Users Say Thank You to EarlyMon For This Useful Post:
Abird! (May 1st, 2013), sikclown (May 2nd, 2013)