Memory leak / log message spam with an invalid file

[fstirlitz]

With this file saved as /etc/incron.d/10-locale.nopurge:

# /etc/locale.nopurge.head IN_MODIFY /etc/locale.nopurge.sh
/etc/locale.gen IN_MODIFY /etc/locale.nopurge.sh

I get this in my logs:

mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument
mai 07 07:16:14 [REDACTED] incrond[26352]: cannot create watch for system table 10-locale.nopurge: (22) Invalid argument

and the memory usage for incrond spikes to something around 15%, which is about the same as the memory usage of Firefox (that is, about 500M).

Even disregarding the lack of support for comments (#4), this behaviour is unacceptable.

[justin8]

I'm also getting this. Was fine on 0.5.10, but 0.5.12 it is now using 11GB of ram, and it was running a find at the start that had 99% iowait for 30+ minutes as well.

7727 root 20 0 11.120g 0.011t 0.0 71.1 11:24.11 S incrond

Not sure how I feel about any program being measured in terabytes in top ;)

[robert-scheck]

I'm seeing the same here after upgrading from 0.5.10 to 0.5.12, feels like a regression.

[sdwru]

We still see a memory leak after upgrading from incron-0.5.10-8.el7.x86_64 to incron-0.5.12-11.el7.x86_64. Had to downgrade again.

[heffneil]

Did this ever get resolved? I would like to add some comments to my incrontab file so I know whats going in but I am afraid of memory issues?

[sdwru]

EPEL stable still shows v0.5.12-11 and we definitely see memory leak problems with that version. Downgrading to incron-0.5.10-8.el7.x86_64.rpm fixes it. So it appears there are still memory leak problems.

[heffneil]

So is it fair to say this product is no longer maintained?