search

dgets / CPURecord

Just an idea that I had after a few months of noticing every time I'd turn my phone's display back on, the CPU would be pegged. I'm not sure, but I think that it might be indicative of some malware, and I want to collect some other statistics regarding what is going on when the display is inactive.
0 stars 0 forks source link

2D array of int initialization is crashing or infinite looping #2

Closed dgets closed 6 years ago

dgets commented 6 years ago

For some reason, when the line int[][] cpuStats = new int[MAX_COARS][4]; is left in CPUProbe.displayInfo(), the 'Show debug info' button stops being responsive, same as when I was having other crashes buried in the CPU* classes. Not sure why in the hell this initialization is crashing things; I've commented out every other line utilizing it (all assignments), and it does, indeed, appear to be the declaration that is hosing things. Funny, I've been doing crap like this since grade school, and I could swear that I'm following the exact template found at Programiz.com and a half a million other places.

dgets commented 6 years ago

So yeah, this was more of an infinite loop due to my stupidity.