This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

It still happens...

It turns out that it's not a bug, it's a desired behavior, but annoying and possibly causing some trouble.
Crontab-ui uses a database called nedb.
Apparently, it is much more "expensive" (in terms of time) to rewrite the entire database (which is a JSON) every time you do an update or a delete, than to add a line at the end of the file and then let the engine do what it has to do. The engine will compact the database when the app is restarted and that's it.
If you notice, if you reload the ui (with a F5) of crontab-ui, the database gets smaller.
But as I guess you don't get into the ui every 10 minutes, the engine has an option to auto compact the db every X milliseconds.
Just add db.persistence.setAutocompactionInterval(interval); on line 13 of crontab.js (just below var db = new Datastore({ filename: exports.crontab_db_file});) and the engine will compact the database every X milliseconds and you're done.

Likewise all this is due to an infinite loop which is as follows:

• Every time the database is modified in any way, node.js calls a method
• That method, writes some files, runs the cron and does an update to the database
• The database is modified and it starts all over again.

Interesting. Thanks for the investigation! I will fix this

I create a PR about that issue
#214

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.