Ok, I’m actually jumping over a more intricate bug description in this post just because I find this one too much fun to pass up.

I discovered a bug in SpikeMark that would spew out erroneous log message, but only after the computer running SpikeMark had been running for 25 days or more without a reboot. Read the rest of this entry »

If you’ve been paying attention to the updates on our site, you may have noticed a flurry of activity recently. We added some new features to SpikeMark which I’ll discuss in another post, but we also have been tracking down some nasty little bugs. The latest rash of bug squashing has been centered around a theme, because multiple performances in various venues have been experiencing similar problems involving tight sequences of linked cues. Read the rest of this entry »