One small bug fix in this release:
I think it should be noted here that Cronicle has some limits, which this bug exercised quite nicely. The main schedule, for example, is only designed to handle a few hundred items, possibly a thousand at the extreme maximum. The author of issue #112 was trying to push this far beyond that soft limit, and thus it inevitably caused memory issues. The Cronicle schedule is stored in memory at all times, and synced to all clients, so it needs to be small and compact.
The schedule is really intended as a replacement for a Crontab. That is, with a relatively small amount of repeating events, possibly hourly, daily, or weekly. It isn't meant to hold a large number of arbitrary events.
Perhaps I will look into redesigning this in v2.0.