AutoNotification RAM usage for updating notification explodes

Hey,
I've been using AutoNotification for some time now to display my current profile as a notification (WiFi, Work, Home, ...). The notification gets initialized once and gets updated when a profile chance occurs. Everything works perfectly but after approx. a day AutoNotification consumes all my RAM and I have to kill it manually to release the RAM. Most of the cases it starts with a notification update error even tho the notification is still there. How do I provide you with a log or s.th. to find the bug?

Philipp

 

I am having the same problem (I posted a RAM screenshot on the G+ forum a while back, before I worked out what triggers the problem).

In my case, rather than displaying a notification, I am intercepting notifications from common media playing apps in order to set variables, so that the last-used app can be re-started later in time. In particular, the notifications created by Podcast Addict trigger the problem particularly badly, as it seems the notifications are updated many times during an episode playback, rather just on episode changes. My task description:


Profile: Set PA Info (22)
Notification: no
Event: AutoNotification Intercept [ Configuration:Event Behaviour: true
Notification Type: Only Created Notifications
Persistency Type: Persistent Only
Has Reply Action: false
Notification Apps: Podcast Addict
Get All Fields : true
Text Names : firsttext,nop,secondtext
Big Text Names : firsttext,secondtext
Get Internal Actions: false
Get Internal Actions Big: false ]
Enter: Set PA Vars (18)
A1: Variable Set [ Name:%AMAPP To:%anapp Do Maths:Off Append:Off ]
A2: Variable Clear [ Name:%AMARTIST Pattern Matching:Off ]
A3: Variable Clear [ Name:%AMTRACK Pattern Matching:Off ]
A4: [X] Flash [ Text:Got music app: %AMAPP Long:Off ]


(I have separate profiles for other media apps)

 

Hi Joao,

Sorry for the slow response on this, I forgot about it for a while since I wasn't listening to podcasts. I tried out your suggestion and it seems to do the trick! So far I haven't seen the memory use go above about 15mb in the couple of weeks since I changed it. So happy to have a workaround and I guess that gives you a good hint of where to look for a leak?

Cheers,
Len.