I thought I was on to something. . . A colleague had a static textview and a static object that references a LoaderManager in another activity. No good reason, it wasn't proper communication between fragments, and the compiler probably prompted him to make them static in a Quick Fix. While it shouldn't affect the Activity I've been monitoring, It's not.
However, now adb is broken all of a sudden. After two weeks of doing heap dumps, it suddenly can;t even debug. Happening with emulators too. Resetting adb, restarting eclipse, and restarting the macbook haven't helped. I may need to move to another topic to solve that. I see that there is possibly an update to ADT. And I know ADT updates always go smoothly and help - not. "Cannot complete the install because of a conflicting dependency." I see rebuilding my development environment for the gazillionth time in my near future. Nathan -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
