Cumulus Support

Hi all,

Did a search and couldn't find anything on this subject, so I thought I'd post question here...
I have had Cumulus sending updates to twitter once a day for the last year or so, but now all of a sudden it crashes the program when I set it to that interval.
That is:
Interval=86400
in cumulus.ini
Even half that time crashes the program. If I set the update interval to 35000 seconds it doesn't crash. (35999 does, and that is as close as I will try and get. I don't have all day. )
But I don't want to send out an update more than once a day. Don't want to spam my Twitter followers.

This is a bit weird since I haven't updated the program and it worked just fine before. I did some changes to the text that should go on twitter (twitter.txt), and I set the interval to 2 minutes to test it. That worked fine and then when I tried to change it back to 86400 the application crashed.

Have tried to restart the machine with no better luck.

Anyone got any ideas what might be going wrong? I run the latest release: 1.9.1 on an up to date Win XP...

At what point does it crash - when you enter the value and click OK? It should produce a bugreport.txt file, if you upload that it will make it much easier for me to fix the problem.

Yes, if I enter the value in the UI it crashes when I press OK. If I change the cumulus.ini file directly it crashes during start up, just after the download / processing data pop up.
I'll attach the bugreport here.

Ah - the interval is in minutes, so a day is 1440. You're trying to set a value equivalent to 60 days.

Yes! Just shot me! I am stupid!
You are absolutely correct! That's what happens when you do too many things at the same time. Case closed. Thanks for the very quick response Steve!

But the bug is really still there. The program shouldn't crash if you are allowed to input some data in the UI.

t000ny wrote:But the bug is really still there. The program shouldn't crash if you are allowed to input some data in the UI.

Indeed; there are undoubtedly lots of bugs in Cumulus, it's not hard to make it crash if you really want to. I am one man doing this for free in his spare time, and spending nearly all of my spare time on it already. It would be very nice to have the time to make sure I have trapped every possible input error, but I don't - sorry.

Oh yes! I am very aware of that! Please don't take it the wrong way. I am _very_grateful_ for all the hard work you put in for free! And I am NOT expecting a bug free program. (Hey, not even big companies like Microsoft and Google can do that!). My last comment were meant as a kind of defence for my own stupidity. The program crashed because of me putting in garbage, and immediately I focus on saying it is something wrong with the software instead of checking my own sanity first.
My bad, no question there...

I think it is amazing how quickly things like this can get resolved in a "free" software environment. If I were to ask the same question to a commercial software vendor, the reply would take a LOT longer. If I even ever would get a reply.

Again: Thanks a lot Steve!

t000ny wrote:Oh yes! I am very aware of that! Please don't take it the wrong way.

No, I don't; you were correct, and I did see the smiley. My reply was just my way of saying that I won't be fixing that particular bug (and others like it) any time soon