search

Hassan1Hr / dashclock

Automatically exported from code.google.com/p/dashclock
0 stars 0 forks source link

Inactive widgets still make DashClock … go crazy? Don't mind if I do! #436

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install Battery Widget Reborn 
(https://play.google.com/store/apps/details?id=net.hubalek.android.reborn.beta&h
l=en)
2. Observe logcat

What is the expected output? What do you see instead?
BWR wakes up every time the battery level changes, does some work, and then 
pokes DashClock, which does even more work, to the point that a GC nearly 
always occurs.

Key: PID 25138 = BWR, PID 23361 = DC.

05-07 10:23:42.794: W/System.err(25138): LOG: Warning Unknown dock level 
ignored.
05-07 10:23:42.894: D/dalvikvm(23361): GC_FOR_ALLOC freed 3186K, 26% free 
11021K/14804K, paused 38ms, total 40ms
05-07 10:23:42.944: D/dalvikvm(23361): GC_FOR_ALLOC freed 18K, 26% free 
11057K/14804K, paused 38ms, total 38ms
05-07 10:23:42.944: I/dalvikvm-heap(23361): Grow heap (frag case) to 11.819MB 
for 1048592-byte allocation
05-07 10:23:42.964: D/dalvikvm(23361): GC_FOR_ALLOC freed <1K, 19% free 
12080K/14804K, paused 15ms, total 15ms
05-07 10:23:43.044: D/dalvikvm(23361): GC_FOR_ALLOC freed 242K, 14% free 
12872K/14804K, paused 14ms, total 14ms
05-07 10:23:52.875: W/System.err(25138): LOG: Warning Unknown dock level 
ignored.
05-07 10:23:52.895: D/dalvikvm(23361): GC_FOR_ALLOC freed 3186K, 26% free 
11020K/14804K, paused 13ms, total 13ms
05-07 10:23:52.915: D/dalvikvm(23361): GC_FOR_ALLOC freed 18K, 26% free 
11057K/14804K, paused 12ms, total 12ms
05-07 10:23:52.915: I/dalvikvm-heap(23361): Grow heap (frag case) to 11.819MB 
for 1048592-byte allocation
05-07 10:23:52.945: D/dalvikvm(23361): GC_FOR_ALLOC freed 0K, 19% free 
12081K/14804K, paused 34ms, total 34ms
05-07 10:23:52.985: D/dalvikvm(23361): GC_FOR_ALLOC freed 242K, 14% free 
12872K/14804K, paused 13ms, total 13ms

What version of the product are you using?
DC 1.5 BETA
BWR 1.7.1/BETA

Which device and Android version are you experiencing this issue on?
Nexus 4, Android 4.X

Are you using a custom launcher or ROM? If so, which one? Note that custom
launchers and ROMs are not supported.
#gotroot

Original issue reported on code.google.com by dsand...@google.com on 7 May 2013 at 2:26

GoogleCodeExporter commented 8 years ago 
In case this wasn't clear: this occurs without actually adding the BWR widget 
to DashClock. (I may have done at one point in the past but it certainly isn't 
added now.)

Original comment by dsand...@google.com on 7 May 2013 at 2:27

GoogleCodeExporter commented 8 years ago 
I'll need to troubleshoot this after I/O :-)

Original comment by roman.nurik on 7 May 2013 at 2:28

GoogleCodeExporter commented 8 years ago 
WHAT COULD POSSIBLY BE MORE IMPORTANT THAN THIS BUG

Original comment by dsand...@google.com on 7 May 2013 at 2:33

GoogleCodeExporter commented 8 years ago 
:)

Original comment by roman.nurik on 7 May 2013 at 2:34

GoogleCodeExporter commented 8 years ago 
Just started looking into this... I installed BWR and added it to DC (v1.5 Beta 
2). Pressing the "refresh" button in the BWR expanded notification certainly 
triggers a bunch of GC_FOR_ALLOC. I'm looking into that now. However, after 
removing BWR and pressing "refresh" I don't see any GC's occurring. Which other 
extensions were added at the time? Also was this a Daydream, Lock screen or 
home screen?

Original comment by roman.nurik on 11 Jun 2013 at 4:04

GoogleCodeExporter commented 8 years ago 
Bumping, I have dashclock and BWR. 

Looking over my logs and searching led me here. Please oh code monkeys, fix it.

Original comment by stev...@gmail.com on 19 Aug 2013 at 7:10