程序长时间运行后，再进入卡死

11-29 11:22:52.269 18300-31340/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 660ms
11-29 11:22:52.269 18300-31080/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 676ms
11-29 11:22:52.269 18300-31356/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 659ms
11-29 11:22:52.269 18300-31289/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 659ms
11-29 11:22:52.269 18300-31331/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 658ms
11-29 11:22:52.269 18300-31200/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:52.269 18300-31194/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 658ms
11-29 11:22:52.269 18300-31214/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 658ms
11-29 11:22:52.269 18300-31087/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 659ms
11-29 11:22:52.269 18300-31328/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 659ms
11-29 11:22:52.269 18300-31359/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 659ms
11-29 11:22:52.319 18300-18319/? I/art: Background sticky concurrent mark sweep GC freed 66(6KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 13.184ms total 79.354ms
11-29 11:22:52.319 18300-18316/? I/art: WaitForGcToComplete blocked for 706.446ms for cause Alloc
11-29 11:22:52.319 18300-18300/? I/art: WaitForGcToComplete blocked for 73.519ms for cause Alloc
11-29 11:22:52.959 18300-18300/? I/art: Clamp target GC heap from 268MB to 256MB
11-29 11:22:52.959 18300-18300/? I/art: Alloc partial concurrent mark sweep GC freed 1630(89KB) AllocSpace objects, 2(2MB) LOS objects, 1% free, 252MB/256MB, paused 1.689ms total 639.742ms
11-29 11:22:52.959 18300-18319/? I/art: WaitForGcToComplete blocked for 640.126ms for cause Background
11-29 11:22:52.959 18300-31350/? I/art: WaitForGcToComplete blocked for 660.490ms for cause Alloc
11-29 11:22:52.959 18300-31077/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 668ms
11-29 11:22:52.959 18300-31285/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 668ms
11-29 11:22:52.969 18300-31176/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 668ms
11-29 11:22:52.969 18300-31007/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 669ms
11-29 11:22:52.969 18300-31060/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 670ms
11-29 11:22:52.969 18300-31186/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 670ms
11-29 11:22:52.969 18300-31267/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 670ms
11-29 11:22:52.969 18300-31203/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 670ms
11-29 11:22:52.969 18300-31263/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 670ms
11-29 11:22:52.969 18300-31080/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 672ms
11-29 11:22:52.969 18300-31044/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 673ms
11-29 11:22:52.969 18300-31189/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 673ms
11-29 11:22:52.969 18300-31054/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 674ms
11-29 11:22:52.969 18300-31340/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 674ms
11-29 11:22:52.969 18300-31071/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 674ms
11-29 11:22:52.969 18300-31356/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 675ms
11-29 11:22:52.969 18300-31308/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 675ms
11-29 11:22:52.969 18300-31087/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 674ms
11-29 11:22:52.969 18300-31311/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 675ms
11-29 11:22:52.969 18300-31353/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 675ms
11-29 11:22:52.969 18300-31289/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 675ms
11-29 11:22:52.969 18300-31362/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 676ms
11-29 11:22:52.969 18300-31214/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 676ms
11-29 11:22:52.969 18300-31295/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 676ms
11-29 11:22:52.979 18300-31371/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 677ms
11-29 11:22:52.979 18300-31200/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 677ms
11-29 11:22:52.979 18300-30410/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 677ms
11-29 11:22:52.979 18300-31197/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 677ms
11-29 11:22:52.979 18300-31094/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:52.979 18300-31219/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:52.979 18300-31322/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:52.979 18300-31068/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:52.979 18300-31040/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:52.979 18300-31194/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:52.979 18300-31074/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:52.979 18300-31182/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:52.979 18300-31273/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:52.979 18300-31029/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:52.979 18300-18658/? W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:52.979 18300-31331/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:52.979 18300-31366/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:52.979 18300-31359/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:52.979 18300-31344/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:52.979 18300-31026/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:52.979 18300-31292/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:52.979 18300-31328/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:52.979 18300-31034/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:52.979 18300-31222/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:52.979 18300-31098/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:52.979 18300-31276/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:52.979 18300-2493/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 684ms
11-29 11:22:52.979 18300-31282/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:52.989 18300-31010/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:52.989 18300-31347/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 684ms
11-29 11:22:52.989 18300-31063/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 684ms
11-29 11:22:52.989 18300-31057/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 684ms
11-29 11:22:52.989 18300-31279/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31299/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31315/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31270/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 686ms
11-29 11:22:52.989 18300-31051/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31302/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31318/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31048/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 685ms
11-29 11:22:52.989 18300-31334/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 686ms
11-29 11:22:52.989 18300-31337/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 686ms
11-29 11:22:52.989 18300-31037/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31305/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31375/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31206/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 688ms
11-29 11:22:52.989 18300-31091/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31228/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 688ms
11-29 11:22:52.989 18300-31225/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31209/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 687ms
11-29 11:22:52.989 18300-31014/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 688ms
11-29 11:22:52.989 18300-31023/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 688ms
11-29 11:22:53.019 18300-18319/com.mafintosh.nodeonandroid I/art: Background sticky concurrent mark sweep GC freed 4(400B) AllocSpace objects, 1(1200KB) LOS objects, 0% free, 254MB/256MB, paused 14.032ms total 52.655ms
11-29 11:22:53.019 18300-18300/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 51.338ms for cause Alloc
11-29 11:22:53.019 18300-31366/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 23.188ms for cause Alloc
11-29 11:22:53.659 18300-31366/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 269MB to 256MB
11-29 11:22:53.659 18300-31366/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 493(26KB) AllocSpace objects, 2(2MB) LOS objects, 1% free, 253MB/256MB, paused 1.955ms total 639.225ms
11-29 11:22:53.659 18300-31359/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 663.114ms for cause Alloc
11-29 11:22:53.659 18300-31344/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 677ms
11-29 11:22:53.659 18300-18319/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 639.658ms for cause Background
11-29 11:22:53.659 18300-18300/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 639.425ms for cause Alloc
11-29 11:22:53.659 18300-31034/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:53.659 18300-18300/com.mafintosh.nodeonandroid I/nubialog: DispatchMessage in MainLooper, delay:772ms msg:{ when=-9m3s414ms callback=com.hjq.logcat.LogcatActivity$LogRunnable target=android.view.ViewRootImpl$ViewRootHandler }
11-29 11:22:53.659 18300-31098/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:53.659 18300-31276/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 678ms
11-29 11:22:53.659 18300-31222/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:53.659 18300-31026/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 682ms
11-29 11:22:53.659 18300-2493/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 679ms
11-29 11:22:53.669 18300-31347/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 679ms
11-29 11:22:53.669 18300-31010/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 680ms
11-29 11:22:53.669 18300-31279/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 680ms
11-29 11:22:53.669 18300-31282/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31299/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 681ms
11-29 11:22:53.669 18300-31057/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 681ms
11-29 11:22:53.669 18300-31270/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 682ms
11-29 11:22:53.669 18300-31315/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 682ms
11-29 11:22:53.669 18300-31328/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:53.669 18300-31063/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31302/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:53.669 18300-31048/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31318/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:53.669 18300-31051/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:53.669 18300-31206/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 680ms
11-29 11:22:53.669 18300-31228/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:53.669 18300-31091/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 681ms
11-29 11:22:53.669 18300-31305/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31037/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31375/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31337/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:53.669 18300-31209/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 682ms
11-29 11:22:53.669 18300-31334/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 683ms
11-29 11:22:53.709 18300-18300/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 36.525ms for cause Alloc
11-29 11:22:54.349 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 270MB to 256MB
11-29 11:22:54.349 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 150(8KB) AllocSpace objects, 1(1200KB) LOS objects, 0% free, 254MB/256MB, paused 2.356ms total 641.663ms
11-29 11:22:54.349 18300-31209/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 673.507ms for cause Alloc
11-29 11:22:54.349 18300-31375/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 674.076ms for cause Alloc
11-29 11:22:54.349 18300-18318/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 530.046ms for cause HeapTrim
11-29 11:22:54.349 18300-31014/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.357s
11-29 11:22:54.349 18300-31225/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.357s
11-29 11:22:54.349 18300-31023/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.358s
11-29 11:22:54.349 18300-18300/com.mafintosh.nodeonandroid I/nubialog: DispatchMessage in MainLooper, delay:689ms msg:{ when=-9m4s740ms callback=com.hjq.logcat.LogcatActivity$LogRunnable target=android.view.ViewRootImpl$ViewRootHandler }
11-29 11:22:54.349 18300-31285/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.359s
11-29 11:22:54.349 18300-31060/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.359s
11-29 11:22:54.349 18300-31007/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.360s
11-29 11:22:54.349 18300-31176/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.361s
11-29 11:22:54.349 18300-31350/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.360s
11-29 11:22:54.349 18300-31267/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.361s
11-29 11:22:54.379 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc sticky concurrent mark sweep GC freed 25(3008B) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 2.754ms total 27.407ms
11-29 11:22:55.009 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 269MB to 256MB
11-29 11:22:55.009 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 51(3KB) AllocSpace objects, 2(2MB) LOS objects, 1% free, 253MB/256MB, paused 1.929ms total 629.873ms
11-29 11:22:55.009 18300-31350/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 657.445ms for cause Alloc
11-29 11:22:55.009 18300-18319/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 658.794ms for cause Background
11-29 11:22:55.009 18300-31014/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 657.743ms for cause Alloc
11-29 11:22:55.009 18300-31044/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.020s
11-29 11:22:55.009 18300-31080/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.022s
11-29 11:22:55.009 18300-31189/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.022s
11-29 11:22:55.019 18300-31263/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.023s
11-29 11:22:55.019 18300-31186/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.024s
11-29 11:22:55.019 18300-31340/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.024s
11-29 11:22:55.019 18300-31054/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.024s
11-29 11:22:55.059 18300-18300/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 42.565ms for cause Alloc
11-29 11:22:55.189 18300-18314/com.mafintosh.nodeonandroid I/art: Debugger is no longer active
11-29 11:22:55.699 18300-18314/com.mafintosh.nodeonandroid W/art: Suspending all threads took: 514.834ms
11-29 11:22:55.699 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 270MB to 256MB
11-29 11:22:55.699 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 33(1648B) AllocSpace objects, 0(0B) LOS objects, 0% free, 254MB/256MB, paused 1.884ms total 647.300ms
11-29 11:22:55.719 18300-18316/com.mafintosh.nodeonandroid I/art: Alloc sticky concurrent mark sweep GC freed 6(144B) AllocSpace objects, 0(0B) LOS objects, 0% free, 256MB/256MB, paused 4.087ms total 17.211ms
11-29 11:22:55.719 18300-18319/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 17.167ms for cause Background
11-29 11:22:56.379 18300-18316/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 269MB to 256MB
11-29 11:22:56.379 18300-18316/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 10(512B) AllocSpace objects, 2(2MB) LOS objects, 1% free, 253MB/256MB, paused 1.738ms total 652.845ms
11-29 11:22:56.379 18300-31014/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 1.358s for cause Alloc
11-29 11:22:56.379 18300-18300/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 669.277ms for cause Alloc
11-29 11:22:56.379 18300-18314/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 626.008ms for cause Alloc
11-29 11:22:56.379 18300-18300/com.mafintosh.nodeonandroid I/nubialog: DispatchMessage in MainLooper, delay:1357ms msg:{ when=-9m6s94ms callback=com.hjq.logcat.LogcatActivity$LogRunnable target=android.view.ViewRootImpl$ViewRootHandler }
11-29 11:22:56.379 18300-31308/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.383s
11-29 11:22:56.379 18300-31353/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.384s
11-29 11:22:56.379 18300-31311/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.384s
11-29 11:22:56.379 18300-31356/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.385s
11-29 11:22:56.379 18300-31077/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.385s
11-29 11:22:56.379 18300-31071/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.385s
11-29 11:22:56.379 18300-31087/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.386s
11-29 11:22:56.379 18300-31203/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.386s
11-29 11:22:56.379 18300-31214/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.386s
11-29 11:22:56.379 18300-31362/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.386s
11-29 11:22:56.379 18300-30410/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.387s
11-29 11:22:56.379 18300-31295/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.387s
11-29 11:22:56.379 18300-31289/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.387s
11-29 11:22:56.379 18300-31219/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.388s
11-29 11:22:56.379 18300-31094/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.389s
11-29 11:22:56.379 18300-31371/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.389s
11-29 11:22:56.379 18300-31322/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.390s
11-29 11:22:56.379 18300-31197/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.390s
11-29 11:22:56.379 18300-31040/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.389s
11-29 11:22:56.389 18300-31068/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.390s
11-29 11:22:56.389 18300-31182/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.390s
11-29 11:22:56.389 18300-31273/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.391s
11-29 11:22:56.389 18300-31194/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.392s
11-29 11:22:56.389 18300-31074/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.392s
11-29 11:22:56.389 18300-31331/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.391s
11-29 11:22:56.389 18300-31366/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.729s
11-29 11:22:56.389 18300-18658/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.393s
11-29 11:22:56.389 18300-31029/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.393s
11-29 11:22:56.389 18300-31034/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.729s
11-29 11:22:56.389 18300-31098/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.728s
11-29 11:22:56.389 18300-31292/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.394s
11-29 11:22:56.389 18300-31359/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.730s
11-29 11:22:56.389 18300-31200/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 3.395s
11-29 11:22:56.389 18300-31222/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.729s
11-29 11:22:56.389 18300-31026/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.728s
11-29 11:22:56.389 18300-2493/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.728s
11-29 11:22:56.389 18300-31347/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.728s
11-29 11:22:56.389 18300-31344/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.729s
11-29 11:22:56.389 18300-31276/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.727s
11-29 11:22:56.389 18300-31279/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=73 for 2.726s
11-29 11:22:56.389 18300-31299/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.726s
11-29 11:22:56.389 18300-31282/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=73 for 2.727s
11-29 11:22:56.399 18300-31270/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.726s
11-29 11:22:56.399 18300-31315/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.727s
11-29 11:22:56.399 18300-31010/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.727s
11-29 11:22:56.399 18300-31328/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.728s
11-29 11:22:56.399 18300-31063/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.727s
11-29 11:22:56.399 18300-31318/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.727s
11-29 11:22:56.399 18300-31302/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.727s
11-29 11:22:56.399 18300-31206/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.728s
11-29 11:22:56.399 18300-31051/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.729s
11-29 11:22:56.399 18300-31048/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.729s
11-29 11:22:56.399 18300-31037/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.728s
11-29 11:22:56.399 18300-31337/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.727s
11-29 11:22:56.399 18300-31057/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.728s
11-29 11:22:56.399 18300-31091/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.727s
11-29 11:22:56.399 18300-31305/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.729s
11-29 11:22:56.399 18300-31334/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=73 for 2.727s
11-29 11:22:56.399 18300-31228/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.730s
11-29 11:22:56.399 18300-31209/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.055s
11-29 11:22:56.419 18300-31225/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.070s
11-29 11:22:56.419 18300-31375/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 2.070s
11-29 11:22:56.419 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc sticky concurrent mark sweep GC freed 77(5KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 254MB/256MB, paused 16.347ms total 40.785ms
11-29 11:22:56.419 18300-31285/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.069s
11-29 11:22:56.419 18300-31023/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=73 for 2.066s
11-29 11:22:56.419 18300-31007/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=73 for 2.068s
11-29 11:22:56.419 18300-31060/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.071s
11-29 11:22:56.419 18300-31267/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.068s
11-29 11:22:56.419 18300-31176/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 2.069s
11-29 11:22:56.419 18300-31350/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.412s
11-29 11:22:56.419 18300-31044/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.410s
11-29 11:22:56.419 18300-31080/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.409s
11-29 11:22:56.419 18300-31186/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.406s
11-29 11:22:56.419 18300-31340/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.407s
11-29 11:22:56.419 18300-31054/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.407s
11-29 11:22:56.419 18300-31189/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.406s
11-29 11:22:56.429 18300-31263/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.407s
11-29 11:22:56.519 18300-18437/com.mafintosh.nodeonandroid D/Node.js: [2021-11-29T11:22:56.535] [INFO] default - update token
11-29 11:22:56.549 18300-18437/com.mafintosh.nodeonandroid D/Node.js: [2021-11-29T11:22:56.558] [INFO] default - update token
11-29 11:22:57.079 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:22:57.079 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 2044(205KB) AllocSpace objects, 4(80KB) LOS objects, 0% free, 255MB/256MB, paused 2.719ms total 657.544ms
11-29 11:22:57.529 18300-18437/com.mafintosh.nodeonandroid D/Node.js: [2021-11-29T11:22:57.542] [INFO] default - update token
11-29 11:22:57.709 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:22:57.709 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc concurrent mark sweep GC freed 4897(278KB) AllocSpace objects, 2(40KB) LOS objects, 0% free, 255MB/256MB, paused 1.606ms total 636.661ms
11-29 11:22:57.709 18300-18300/com.mafintosh.nodeonandroid I/art: Forcing collection of SoftReferences for 1800KB allocation
11-29 11:22:58.349 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:22:58.349 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc concurrent mark sweep GC freed 2425(132KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 1.628ms total 634.294ms
11-29 11:22:58.349 18300-18300/com.mafintosh.nodeonandroid E/art: Throwing OutOfMemoryError "Failed to allocate a 1843624 byte allocation with 754080 free bytes and 736KB until OOM"
11-29 11:22:58.349 18300-31340/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 1.764s for cause Alloc
11-29 11:22:58.349 18300-31010/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.772s
11-29 11:22:58.349 18300-31273/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.772s
11-29 11:22:58.349 18300-2493/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.774s
11-29 11:22:58.349 18300-31203/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.775s
11-29 11:22:58.349 18300-31347/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.775s
11-29 11:22:58.349 18300-31302/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.775s
11-29 11:22:58.349 18300-31299/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.776s
11-29 11:22:58.349 18300-31182/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.776s
11-29 11:22:58.349 18300-31186/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.777s
11-29 11:22:58.359 18300-31350/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.776s
11-29 11:22:58.359 18300-31263/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.777s
11-29 11:22:58.359 18300-31176/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.777s
11-29 11:22:58.359 18300-31197/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.778s
11-29 11:22:58.359 18300-31225/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.778s
11-29 11:22:58.359 18300-31063/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.779s
11-29 11:22:58.359 18300-31214/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.779s
11-29 11:22:58.359 18300-31054/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.781s
11-29 11:22:58.359 18300-31029/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.780s
11-29 11:22:58.359 18300-31023/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.780s
11-29 11:22:58.359 18300-31292/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.779s
11-29 11:22:58.359 18300-31219/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.780s
11-29 11:22:58.359 18300-31371/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.780s
11-29 11:22:58.359 18300-31311/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.780s
11-29 11:22:58.359 18300-31359/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.781s
11-29 11:22:58.359 18300-31048/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.782s
11-29 11:22:58.359 18300-31285/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.782s
11-29 11:22:58.359 18300-31194/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.782s
11-29 11:22:58.359 18300-31353/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.783s
11-29 11:22:58.359 18300-31366/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.784s
11-29 11:22:58.359 18300-31279/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.783s
11-29 11:22:58.359 18300-31200/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.784s
11-29 11:22:58.369 18300-31091/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.785s
11-29 11:22:58.369 18300-31295/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.786s
11-29 11:22:58.369 18300-31356/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.786s
11-29 11:22:58.369 18300-31060/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.786s
11-29 11:22:58.369 18300-31014/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.787s
11-29 11:22:58.369 18300-31007/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.787s
11-29 11:22:58.369 18300-31334/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.788s
11-29 11:22:58.369 18300-31344/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.787s
11-29 11:22:58.369 18300-18658/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.788s
11-29 11:22:58.369 18300-31206/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.788s
11-29 11:22:58.369 18300-31074/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.789s
11-29 11:22:58.369 18300-31267/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.788s
11-29 11:22:58.369 18300-31322/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.789s
11-29 11:22:58.369 18300-31270/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.789s
11-29 11:22:58.369 18300-31037/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.789s
11-29 11:22:58.369 18300-31318/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.790s
11-29 11:22:58.369 18300-31026/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.790s
11-29 11:22:58.369 18300-31080/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.790s
11-29 11:22:58.369 18300-31189/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.790s
11-29 11:22:58.369 18300-31362/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.791s
11-29 11:22:58.369 18300-31071/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.790s
11-29 11:22:58.369 18300-31315/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.791s
11-29 11:22:58.369 18300-31337/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.791s
11-29 11:22:58.389 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc sticky concurrent mark sweep GC freed 12(816B) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 15.647ms total 40.555ms
11-29 11:22:58.389 18300-31308/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.807s
11-29 11:22:58.389 18300-31228/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.807s
11-29 11:22:58.389 18300-31222/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.808s
11-29 11:22:58.389 18300-30410/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.808s
11-29 11:22:58.389 18300-31375/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.808s
11-29 11:22:58.389 18300-31289/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.809s
11-29 11:22:58.389 18300-31305/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.809s
11-29 11:22:58.389 18300-31328/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.810s
11-29 11:22:58.389 18300-31040/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.810s
11-29 11:22:58.389 18300-31044/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.810s
11-29 11:22:58.389 18300-31034/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.811s
11-29 11:22:58.389 18300-31087/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.811s
11-29 11:22:58.389 18300-31098/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.810s
11-29 11:22:58.389 18300-31051/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.811s
11-29 11:22:58.389 18300-31276/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.811s
11-29 11:22:58.399 18300-31282/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.811s
11-29 11:22:58.399 18300-31068/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.812s
11-29 11:22:58.399 18300-31209/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.812s
11-29 11:22:58.399 18300-31331/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.813s
11-29 11:22:58.399 18300-31094/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=75 for 1.813s
11-29 11:22:58.399 18300-31077/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 1.813s
11-29 11:22:59.029 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:22:59.029 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc partial concurrent mark sweep GC freed 266(14KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 1.939ms total 638.851ms
11-29 11:22:59.669 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:22:59.669 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc concurrent mark sweep GC freed 3486(190KB) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 1.679ms total 636.499ms
11-29 11:22:59.669 18300-18300/com.mafintosh.nodeonandroid I/art: Forcing collection of SoftReferences for 1800KB allocation
11-29 11:23:00.299 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:23:00.299 18300-18300/com.mafintosh.nodeonandroid I/art: Alloc concurrent mark sweep GC freed 11(512B) AllocSpace objects, 0(0B) LOS objects, 0% free, 255MB/256MB, paused 1.611ms total 637.153ms
11-29 11:23:01.699 18300-18300/com.mafintosh.nodeonandroid I/art: Clamp target GC heap from 271MB to 256MB
11-29 11:23:01.699 18300-18300/com.mafintosh.nodeonandroid E/art: Throwing OutOfMemoryError "Failed to allocate a 1843624 byte allocation with 210752 free bytes and 205KB until OOM"
11-29 11:23:01.699 18300-18363/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 4.825s for cause Alloc
11-29 11:23:01.699 18300-18300/com.mafintosh.nodeonandroid D/AndroidRuntime: Shutting down VM
11-29 11:23:01.699 18300-31057/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 5.116s for cause Alloc
11-29 11:23:01.699 18300-31353/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 3.230s for cause Alloc
11-29 11:23:01.699 18300-31295/com.mafintosh.nodeonandroid I/art: WaitForGcToComplete blocked for 3.230s for cause Alloc
11-29 11:23:01.699 18300-31197/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.236s
11-29 11:23:01.699 18300-31040/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.236s
11-29 11:23:01.699 18300-31054/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.236s
11-29 11:23:01.699 18300-31279/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.237s
11-29 11:23:01.709 18300-31371/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.238s
11-29 11:23:01.709 18300-31182/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.239s
11-29 11:23:01.709 18300-31176/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.240s
11-29 11:23:01.709 18300-31263/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.240s
11-29 11:23:01.709 18300-18300/com.mafintosh.nodeonandroid E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.mafintosh.nodeonandroid, PID: 18300
java.lang.OutOfMemoryError: Failed to allocate a 1843624 byte allocation with 210752 free bytes and 205KB until OOM
at java.lang.AbstractStringBuilder.enlargeBuffer(AbstractStringBuilder.java:95)
at java.lang.AbstractStringBuilder.append0(AbstractStringBuilder.java:146)
at java.lang.StringBuilder.append(StringBuilder.java:216)
at com.hjq.logcat.LogcatInfo.addLog(LogcatInfo.java:76)
at com.hjq.logcat.LogcatActivity$LogRunnable.run(LogcatActivity.java:334)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:147)
at android.app.ActivityThread.main(ActivityThread.java:5531)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:969)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:764)
11-29 11:23:01.709 18300-31060/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.244s
11-29 11:23:01.709 18300-31094/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.247s
11-29 11:23:01.709 18300-31292/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 for 3.247s
11-29 11:23:01.709 18300-31063/com.mafintosh.nodeonandroid W/art: Long monitor contention event with owner method=void com.hjq.logcat.LogcatManager$LogRunnable.run() from LogcatManager.java:89 waiters=74 fo

小伙子，你这个问题是属于 ANR 还是 OOM ？

超过三天没有响应，关闭此 issue。


Trying to enable type check features when using the typescript template

I add a declaration %type  tokens... to specify the type of those tokens. And I make some little changes to the type annotations in some sources.

Hello? Is there anything I forgot to do?


[javascript mode] Recognize regex inside template literal

Closes gh-3687

Thanks! I've pushed a slightly revised patch 764022a which doesn't assume that there is no whitespace between the { and the /.


Warn when switching to console that you are already running

RancherOS Version: (ros os version)
Custom build of v0.5.0 (os3)
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
Virtual Box
When you are already in a console, we should add a warning when you ask to switch to the same console that you are already in.

Veririfed with custom build os12.


Add Astro CLI & command astro telemetry disable

https://github.com/withastro/astro/blob/f7335c76a7f8a8251db363c7103624f286ee8d3a/packages/telemetry/README.md#L1
https://docs.astro.build/en/reference/cli-reference/#astro-telemetry

Related to https://github.com/beatcracker/toptout/issues/543


[feature]: Enhance asset_sum report to clarify conservation

Background
Strict, asset-amount conservation checks exists in the tapd VM to prevent undue inflation of asset quantities. However, there may be instances where the daemon reports asset amounts that appear to be double counted, even though they are being properly conserved.
Asset Balance Clarification
To avoid confusion, it is essential to clearly delineate between payment-channel balances and L1-only asset balances. This will ensure that users have a comprehensive understanding of their asset holdings.
Task 1: Ensure Mutual Exclusivity

[ ] Verify that the sum of L1-only asset balances and payment-channel balances are mutually exclusive, i.e., there is
no overlap or double counting between the two types of balances.

Comprehensive Asset Sum Calculations
To ensure accuracy in asset sum calculations, we need to investigate the comprehensiveness of these calculations.
Task 2: Investigate asset sum Calculation

[ ] Check if the script_key_has_script_path": true flag is being incorrectly included in the asset sum.
[ ] Verify that leased assets are not showing up in the asset sum, as they may be subject to different conservation rules.

Force Close Scenario
Background
In the scenario where two nodes have a channel
Node 1 force closes
Node 2 (the responder) -- even if it didn't have the channel's entire balance, the node insert the force close transaction, into it's own database
These inserted transaction are added to the database fields that are importing the outputs as well
While these outputs cannot be spent due to the presence of a script path.
But litd/tapd displays these as part of the node's balance today
Solution
make another delineated name space, to track the amounts in order for the wallet balance commands to by default not show these balance, by default
Considerations
These values are used during tests to assert certain outcomes have been met
add a flag to enable reporting in order for assertion tests to have the necessary data available to run tests

Further detail per debugging with @guggero: "maybe we forgot to not count "script_key_has_script_path": true in the asset sum. or maybe the leased assets still show up there."
Context: the output of tapcli assets balance includes amounts from the tapcli assets list --show_leased output that it shouldn't. Namely channel funding outputs (identified by "script_key_is_local": false, AND script_key_has_script_path": true) that have 6d7cd7ee247587eef86766140262685819deebc034ad80664fb74ec2ad6e11d7 listed as the lease_owner (representing a tapd internal lock`), meaning they've since been spent.

Updated original issue with more context

Background
In the scenario where two nodes have a channel
Node 1 force closes
Node 2 (the responder) -- even if it didn't have the channel's entire balance, the node insert the force close transaction, into it's own database
These inserted transaction are added to the database fields that are importing the outputs as well
While these outputs cannot be spent due to the presence of a script path.
But litd/tapd displays these as part of the node's balance today
Solution
make another delineated name space, to track the amounts in order for the wallet balance commands to by default not show these balance, by default
Considerations
These values are used during tests to assert certain outcomes have been met
add a flag to enable reporting in order for assertion tests to have the necessary data available to run tests

@gijswijs Will start task 2 - show balance script key path is true and considering
spend flag
is leased situation
and this is a directly spendable
have for asset list
but not asset sum
a) default values
b) RPC call sum
(asset balance)

Reopen as more remediation is needed

I confirmed in the code that we do not accidentally count non-local script keys towards the balance.
See:
https://github.com/lightninglabs/taproot-assets/blob/65539b6fd8e11657f96353a87714ed2d3e4399a6/tapfreighter/interface.go#L199-L204
And:
https://github.com/lightninglabs/taproot-assets/blob/65539b6fd8e11657f96353a87714ed2d3e4399a6/tapdb/assets_store.go#L3020-L3022
And:
https://github.com/lightninglabs/taproot-assets/blob/65539b6fd8e11657f96353a87714ed2d3e4399a6/tapdb/assets_store.go#L3039-L3042
When the asset is a tombstone, from a non-local script key, a burn, or derived by the local wallet or explicitly declared to be known the asset creation in the database is skipped and therefor those assets will not turn up in the balance queries.

Maybe it is prudent to create a test that checks whether those assets are not created in the database. But maybe that's overkill. @dstadulis ?
If the latter, then consider this issue closed, since Task 1 is more of a UX discussion that we decided should be had further down the line (cc: @Roasbeef )

Discussed with @Roasbeef
Add another assertion or two here: https://github.com/lightninglabs/lightning-terminal/blob/0-19-staging/itest/litd_custom_channels_test.go#L264

Since un completed items is UX clarification, will deprio a bit to focus on adding testing https://github.com/lightninglabs/lightning-terminal/issues/867

It is now confirmed that L1-balances and custom channel balances are not reported mutually exclusive.
The listBalances endpoints use a database query to sum the total value of the assets. Non-local assets should not turn up in those queries. To check whether an asset is local we ask LND. Sadly, there is currently no way to do that in the database. I see two solutions:
A) iterate through all assets returned by ListAssets and use that to calculate the balances. ListAssets already hits LND for each asset, so we know for each asset whether it's local or not.
B) Update the database to include a field indicating whether an asset is local or not. During upsert hit LND once to determine whether the asset is local.
Option A will probably be slow(ish) with large numbers of assets.
Option B requires a go-based db migration, which are :-1:
This litd PR depends on this issue being resolved: https://github.com/lightninglabs/lightning-terminal/pull/871

I thought about this quite a bit and have come up with the following plan:

I don't think we always want to exclude script keys that are not local. For example, you could have a MuSig2 combined internal key, or a NUMS internal key with some tapscript leaves on top. So always filtering by script_key_is_local will probably be too restrictive.
Filtering by keys that have a script path (script_key_has_script_path) also doesn't fully solve the issue, since that should probably be a flag as well (for example --include_script_paths or something like that).

So what I think we want is to just always exclude any script keys that are the exact key of 0350aaeb166f4234650d84a2d8a130987aeaf6950206e0905401ee74ff3f8d18e6, which is equivalent to tapchannel.NewFundingScriptTree().TaprootKey.SerializeCompressed().
We of course wouldn't hard code that in the SQL query but pass it in as an excludeKey from the Go code.
And yes, I know this feels hacky, but IMO it's the only key we'll ever not want to show up. Any other potentially non-local/combined/NUMS key could be important to an app that's using the RPC.


CMake presets are not working properly

On my platform whether I specify windows-x86-release or windows-x64-release preset with CMake I get the same type of build. And it depends not on the preset, but which VS environment I am in.
If I set up 32bit environment and then configure 64bit build:
prompt> "c:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvars32.bat"
prompt> cmake --preset windows-x64-release
prompt> cmake --build out\build\windows-x64-release -j8

I still end up with 32bit binaries:
prompt> dumpbin /headers out\build\windows-x64-release\Orbiter_ng.exe
...
FILE HEADER VALUES
             14C machine (x86)
...

Likewise, if I set up 64bit environment and try to build 32bit build:
prompt> "c:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
prompt> cmake --preset windows-x86-release
prompt> cmake --build out\build\windows-x86-release -j8

I end up with 64bit binaries:
prompt> dumpbin /headers out\build\windows-x86-release\Orbiter_ng.exe
...
FILE HEADER VALUES
            8664 machine (x64)
...

Not sure if Visual Studio automatically selects the right environment based on the "architecture.value" parameter in the preset, but it doesn't seem to work when building from the command line.

Closing as this could just be specific to my setup (running msvc under wine).


support Role.inlinePolicies

Adds support for inline policies for Role resources.
The new Role.Spec.inlinePolicies field is a map[string]*string, keyed by the inline policy name and valued with the inline policy document (serialized JSON string).
Inline policies are actually added and removed from a Role using different IAM API calls than their managed policy counterparts. Whereas managed policies (contained in the Role.Spec.Policies field) are attached and detached from the Role using the AttachPolicyRole and DetachRolePolicy API calls, the inline policies are attached and detached from the Role using the AddRolePolicy and DeleteRolePolicy API calls. Yes, this is confusing and why I hadn't actually included inline policies from the very beginning (I did not realize these were separate things and separate API calls).
Similar to managed policies, all inline policies are removed from the Role prior to role deletion.
Issue aws-controllers-k8s/community#1644
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test

/lgtm


extend the activity generator extension to allow the autogeneration o…

…f user code
With the current approach the extensions are only allow the create code on the src-gen folder, code that if modified is not protected. For some Mixed Ports cases this is not enough, please check https://github.com/seronet-project/SeRoNet-Tooling-ROS-Mixed-Port/pull/30 for further details.
These modifications only add new optional methods, can't break for other non-ROS mixed port cases

Thanks for your contribution. I will address it at the next possible opportunity.

@alex-lotz will this be merged soon?
I am finishing the documentation and this PR simplify considerably the code that the user has to modify manually (and consequently the documentation).
This makes also the code at components level for the ROS mixed ports completely consistent with the Smartsoft ones.

Thanks for merging this. :+1:
can you please ping me when the release is ready(i.e. updated the latest version of the update site)? . So I can continue with the release of the rest of the plugins.


Visualization not working

Hello,
I tried installing the visualizer both manual and automatic. The song name info works for spotify but I can't select an audio device. All the devices are there but nothing happens when I select one. I've also tried stable and beta versions of rain meter and running as admin and it's still not working. Any ideas? I have also noticed the sliders for the settings being very laggy and sometimes rain meter completely freezes.

So from what I've found it's a RealTek driver issue so maybe it will be fixed in the future? I'd leave this issue open for further updates.


Change the newsletter events heading.

Coverage remained the same at 65.131% when pulling 423d03e6b50431bc4d33fa19d881e3b9feb3e6cc on OCW-67 into a2e8eebc127f76433252fb45e67ad6b830e18454 on master.


feature/TK-456

Frontend Select Component to add personal user event

We're waiting for PR #332 related to TK-452 before we can merge this PR


1.Upgraded the version of torch, torchvision, h5py and onnxruntime

2.Fixed the problem that test_adaptative.py fails under python3.9
3.Upgraded the python compatibility to python3.9

Checklist
GitHub

[ ] I've given this PR a concise, self-descriptive, and meaningful title
[ ] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[ ] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

Resolves #770

Pull Request Test Coverage Report for Build 912244960

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.936%

Totals

Change from base Build 900933177:
0.0%

Covered Lines:
4043

Relevant Lines:
5781

💛  - Coveralls

After testing on Ubuntu 20 and Windows 10, I can confirm that there are at least three unit tests failing consistently when tested with GPU. I TENTATIVELY believe across the OS these are the similar if not the same three unit tests that are failing:
2021-09-28T203314EST_WinGPUTrainingLog.txt
I believe these are mostly related GPU IDs and a system exit error which should have fairly minor effect on the actual library performance and are more related to how the tests are setup/asserted.

So GPU ID was a relative easy fix. Somehow the GPU ID in the data_functional_testing was defaulting to 7, which is VERY atypical (unless somehow you have 8 GPUs). Switching it back to default [0] should address most of the issues.


[Fix #7212] Fix a false positive for Layout/EmptyLinesAroundAccessModifier

Fixes #7212.
Fixes #7246.
This PR fixes a false positive for Layout/EmptyLinesAroundAccessModifier and UselessAccessModifier when using method with the same name as access modifier around a method definition.
The main changes are as follows.

Added test for where #7194 change did not find a regression.
The implementation needed to resolve #7186 will be moved to Style/MixinUsage cop. This solves false positives that occurred in other cops.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Seems the build got stuck.

Thanks!


Bug in calling unexisting function

https://github.com/jarektkaczyk/eloquence-base/blob/master/src/Relations/Joiner.php#L197
This function getQualifiedForeignKey doesnt exist anymore on BelongsTo, see:
https://github.com/laravel/framework/blob/5.8/src/Illuminate/Database/Eloquent/Relations/BelongsTo.php
It is now named getQualifiedForeignKeyName. I tried to trace down the date+version at which it was changed, but for some reason I am unable to find it in the commits. If anyone want to take a look that would be appreciated:
https://github.com/laravel/framework/commits/5.8/src/Illuminate/Database/Eloquent/Relations/BelongsTo.php
As for a quickfix: anyone know how to easily override this class function so that I can make it work on Laravel 5.7/5.8?

Just change the getQualifiedForeignKey to getQualifiedForeignKeyName and upload via FTP.

obviously thats not gonna do much if you update composer...
I now simply copied the file and changed the line, and added it to composer.json like so:
"files": [
            "app/FixJoiner.php"
        ]

Composer update will not affect any files unless the package has a newer version.
In case it does update, that bug would be fixed anyway, so you're all good. ;)

This also breaks compatibility with laravel 5.6, maybe bump the Illuminate/Database version restriction in composer.json?

This also breaks the compatibility with Laravel 5.7, the getQualifiedForeignKeyName was introduced in Laravel 5.8.

I'm having the same issue with Laravel 5.5


Bump ephemeral couchdb to v2.3

Bump the ephemeral CouchDB version to 2.3.  Version 2.1 apache image (in current use) fails when mounting external data storage file systems set up with different uids than the docker daemon.

Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[X] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[X] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[X] I signed an Apache CLA.
[X] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@jonpspri not sure if #4250 is related - do you mind taking a look?

Codecov Report

Merging #4202 into master will decrease coverage by 7.92%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4202      +/-   ##
==========================================
- Coverage   86.21%   78.28%   -7.93%
==========================================
  Files         152      156       +4
  Lines        7275     8314    +1039
  Branches      477      561      +84
==========================================
+ Hits         6272     6509     +237
- Misses       1003     1805     +802

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...n/scala/org/apache/openwhisk/common/CausedBy.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.54%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-83.34%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
0% <0%> (-62.5%)
:arrow_down:

...penwhisk/core/database/cosmosdb/CosmosDBUtil.scala
57.5% <0%> (-38.5%)
:arrow_down:

...apache/openwhisk/core/database/LimitsCommand.scala
63.82% <0%> (-34.54%)
:arrow_down:

...containerpool/kubernetes/KubernetesContainer.scala
64.28% <0%> (-30.46%)
:arrow_down:

.../containerpool/ApacheBlockingContainerClient.scala
48.14% <0%> (-22.77%)
:arrow_down:

... and 29 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb02bdb...d7de2f0. Read the comment docs.


Memory dom fixes

Upgraded substance-bundler using latest rollup
Fixed two issues in MemoryDOMElement

Codecov Report

Merging #1133 into develop will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           develop   #1133      +/-   ##
==========================================
+ Coverage    59.99%     60%   +0.01%
==========================================
  Files          377     377
  Lines        13962   13963       +1
==========================================
+ Hits          8376    8379       +3
+ Misses        5586    5584       -2

Impacted Files
Coverage Δ

dom/MemoryDOMElement.js
89.2% <100%> (+0.02%)
:arrow_up:

dom/BrowserDOMElement.js
85.79% <0%> (+0.54%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 208135e...45c459c. Read the comment docs.


stdenv/custom: avoid aliases

Avoid hostPlatform and targetPlatform aliases, so that the following is possible:
nixpkgs.config = {
  allowAliases = false;
  replaceStdenv = { pkgs }: pkgs.zigStdenv;
};

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

github ci eval worked


set get accessors in tool scripts don't work for arrays, unless defined in separate functions

Godot version
Godot 4 alpha
System information
Windows 10
Issue description
In this tool script, the array's elements are not stored when saving and closing the scene. It works if the set, get are defined in separate functions.

Steps to reproduce
Open the example scene.
Enter some data in the empty array: array_set_get_does_not_work.
Save the scene.
Close, and re-open the scene.
The array is now empty.
Minimal reproduction project
https://github.com/oOjor-elOo/godot_set_get

Duplicate of https://github.com/godotengine/godot/issues/58285.


Print out exceptions occuring in WASM code.

Print out exceptions occuring in WASM code.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

unrelated files reverted.


[NFC] Split Workspace.swift into smaller files

Motivation:
Workspace.swift has grown to an unmanageable size: ~4k lines, close to 4200 before #7000 was merged. The Workspace type is the main API for SourceKit-LSP interactions with SwiftPM. As we'd like to add more cross-compilation functionality here (e.g. allowing SourceKit-LSP to select a different Swift SDK), this API should be more navigable and easier to work with. Since the amount of public functions on Workspace is limited, we should keep them grouped in the main Workspace.swift file, but the actual implementations can be moved to separate files for easier subsequent refactoring and further changes.
Modifications:
Split Workspace.swift into more files, with each file corresponding to an implementation aspect of the Workspace API.
Also applied our formatting rules to the new files.
Result:
Workspace.swift is now only 1384 lines long. When looking for a specific Workspace functionality implementation, you can look it up in separate files that correspond to a larger area grouping that functionality.

@swift-ci test

@swift-ci test

@swift-ci test windows

@swift-ci test

@swift-ci test windows

@swift-ci test windows


How do I send an ESP networked device like ESP8266 or ESP32 via ESPNOW protocol from my mobile device? (AEGHB-28)

I want to be able to use my cell phone to achieve this kind of light and fast connection to control the device quickly in some places where the network is not good, if I can't use this kind of protocol, is there a protocol that can be paired-free and fast connection can be achieved.

For your situation, I recommend that you use BLE for communication. For examples, see: https://github.com/espressif/esp-idf/tree/master/examples/bluetooth/nimble

ESP-NOW can coexist with regular Wi-Fi either AP or STA as soon as you use same channel for both protocols.

@xiaodeme-aha Closing this issue since there has been no update on this. Please feel free to reopen if required.