After a reflash without restoring from backup, I have a problem with python. Many times (i 've notice that it usually happens when i open apps, like tear) python processes begin to get created eating 7-8 MB each, and if i don 't kill them soon (with load-applet) the memory will be filled and the system may hang and reboot.
I didn't find anything and i 'm afraid i m the only one with this problem . Can anyone help me please? I 'm not going to reflash again, and it 's boring killing processes

do you happen to use mcalendar?

Oh, yes, i forgot to mention that. Why that? Does the developer know that? I didn't find anywhere about that

heh, its a combo of mcalendar and python-launcher, where the end result is multiple processes trying to sync with gcal over and over from what i can tell...

only real option is to uninstall python-launcher and manually clean out the alarmd xml file using alarmtool (its a commandline tool) of all the scheduled sync events (if i knew enough grep regular expressions, i could maybe build a script to do it).

i think i informed the mcalender dev of the issue at one point, but lately there seems to be little activity at his end...

i don't have python-launcher installed. And where is the alarmd xml file? I set the auto sync time on mcalendar on 0 mins, and I 'll see if that stops the problem, but i 'm probably going to remove this ram-eating app...

/var/lib/alarmd/ should hold the file in question...

did you have python-launcher installed before the reflash?

i deleted the mcalendar entries. Now i ll not need again to do this?
I ve never installed python-launcher

ok, then i am not fully sure, as i have only seen it happen with a combo of mcalendar and python-launcher...

still, it could be that mcalendar was the sole culprit all along, and that i just happened to trigger the issue on my own device when having python-launcher installed.