AutoNotification Possible runaway CPU usage problem with AutoNotify, Tasker, Android 6 / 7, and Google Maps navidatio

Please see https://groups.google.com/d/topic/tasker/okqBs0jDBbs/discussion for details/logs.

This might be the same problem as I originally reported in https://groups.google.com/d/topic/tasker/EuOjwD7ILPg/discussion
but a lot worse since upgrading my Nexus 6 to Android 7. This is stock (but rooted).

My suspicion is it has something to do with the Autonotification plugin intercepting the status bar updates from Google maps because I only see these problems when I navigate (earlier in the day it was so bad it actually caused tasker to crash and restart itself several times until the phone eventually rebooted itself). The run log doesn't show anything interesting (e.g. high volume) but the debug log shows 8600 instances of autonotification in just 30 seconds!

 

Yes - tasker's debug log

 

Is that still available almost 2 weeks after this happened? I didn't explicitly turn on any autonotification logging at the time because I didn't think I needed to.

If I need to go through specific steps to collect logs for you, please provide details.

 

There seems to be 2 different ways of turning on logs - the system logs checkbox and the circle-slash icon in the log listing - which do I need?
After the problem occurs
- Where are the log files stored so I can copy/post them?
- How long before they wrap or get purged?

 

I just uploaded the latest autonotification log and crash log along with the latest tasker logs to https://groups.google.com/d/topic/tasker/okqBs0jDBbs/discussion
(the zip file was too big to upload here).

You can see events in tasker's run log where at 8:45am I initiated a phone call via Bluetooth from my car's speed dial but the phone didn't actually open the dialer to start dialing that number until 9am.