Then you would need to talk to the makers of the roms that are doing this...
As for onCreate() you shouldn't really be doing ANYTHING except calling setContentView() and initializing a few member variables. Anything else needs to go in a separate thread (perhaps using AsyncTask) to do heavy initialization/work... On Aug 15, 2012 5:16 PM, "b0b" <[email protected]> wrote: > After more investigations, it look like each of this Wrote stack traces" > logcat line will write a /data/anr/slow??.txt : > > > shell@android:/data/anr $ ls > slow00.txt > slow01.txt > slow02.txt > slow03.txt > slow04.txt > slow05.txt > slow06.txt > slow07.txt > slow08.txt > slow09.txt > traces.txt > > > My question to thows in the know is > > - can it be disabled ? I had high hope in a property called > dalvik.vm.lockprof.threshold set to 500 but chaning it or removing it > doesn't do anything. > - who thought that this "feature" to write stack traces if the UI thread > is blocked for 500ms is a good idea ? Is it to make the device even > slower, writing stack trace that nobody will ever read ? > > This "feature" seems to be only be enabled on some ROMs but doesn't look > restricted to CyanogenMod. > > > On Wednesday, 15 August 2012 23:14:40 UTC+2, b0b wrote: >> >> I'm now convinced it is a CM9 issue as it writes stack traces for almost >> any app, at startup but also sometimes during normal execution. >> >> To prove I am not affabulating, this when starting the camera app (in >> between lines omitted): >> >> 08-15 23:08:57.078: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> 08-15 23:08:57.128: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> 08-15 23:08:57.582: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> 08-15 23:08:58.058: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> 08-15 23:08:58.558: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> 08-15 23:08:59.011: I/dalvikvm(30403): Wrote stack traces to >> '/data/anr/traces.txt' >> >> That could explained why I noticed some unexlained lags on my Samsung >> Galaxy S CM9. >> It looks like it spends its time writing stack traces... >> >> Well, that issue will have had the benefit to make me turbo optimize >> onCreate() and friends while trying to get rid of it. >> > -- > 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 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
