No doubt about that. But, there is a really simple fix for this issue. Simply restart AlexaCookie.js once a day. It doesn't even have to be reconfigured.
This fix was discovered by @dan.t who reported it here. @gabriele, who wrote AlexaCookie.js, independently discovered the same thing as indicated two messages after @dan.t's in the same thread.
I've been doing this using a nightly cron job for the last month - works flawlessly.
