MD keeps crashing all the time (Solved)

solquest

Member
Hey there.

I'm having MD crashing very often lately.
It has just happened now (18:41/42) and in MD logs there's nothing.
In phone logs (attached) I see:

09-25 18:41:58.428 1807 1896 I InputDispatcher: Application is not responding: Window{441bf6e u0 com.arlosoft.macrodroid/com.arlosoft.macrodroid.logging.systemlog.SystemLogActivity}. It has been 5014.3ms since event, 5005.9ms since wait started. Reason: Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 36. Wait queue head age: 5507.2ms.
...
09-25 18:42:13.735 1807 1830 E ActivityManager: 100% 2787/com.arlosoft.macrodroid: 99% user + 0.4% kernel / faults: 2170 minor

Any idea on what's the problem or on what I can do?
Thanks.
Luigi.

MD 5.18
Android 9
Xiaomi redmi 4x
rooted with custom rom
 

Attachments

  • Log_2021-9-25_18-42-35.txt
    277 KB · Views: 2

solquest

Member
I couldn't say properly cause I don't spend a lot of time with phone in my hands (so I don't notice if it crashes or if macros fire properly), but trying now seems that everytime I try to open MD, I get the popup saying it's not responding...
 

Pseudocyclic

Well-known member
Try disabling some macros - maybe a category at a time first - and see if you can narrow it down to one in particular.
 

solquest

Member
Great idea.
I've found out that the problem was a macro test I had for trying the new trigger Logcat message.
Deleting it seems I'm not having the issue.
Thanks!
 

Pseudocyclic

Well-known member
Maybe you could create the simplest possible macro that consistently causes the problem and then generate a bug report for it.
 

solquest

Member
True, but that was an unconsistent macro, a test I created for testing that new trigger, so I'd say it's more my fault then a bug,,,
Let's see if I need to use that trigger for a proper macro
 
Top