Technical Support Forums

Technical Support Forums » Citrus Alarm Clock

Ram usage after multiple alarms (3 posts)


About this Topic

  • Started 1 year ago by Anonymous
  • Latest reply from anonymous

Tags

No tags yet.

  1. Anonymous

    Posted 1 year ago

    Hi,

    While I haven't registered this yet I've noticed an issue already. On my system it uses the FFDShow Audio codec to play the alarm which is fine. But once the alarm has finished playing it does not close the idle FFDShow Audio processes that it creates, it keeps them open consuming more and more memory per alarm played since it opens up a new one each time. Before I noticed this it was using 70mb of memory, which compared to when it's still got an alarm scheduled but hasn't played any yet(6mb) is a rather large amount. While I'd like to buy this software, I wont buy something with memory leaks.

    -Andrew

  2. Mark
    Administrator
    Posted 1 year ago

    Citrus uses the Windows Media Player API for all media playback. I haven't experienced any memory leaks under normal circumstances, but I don't use FFDShow or any non-default codec, so that could be introducing complications. I'll give it a go and see what could be causing FFDShow to linger around after the playback is all done and closed.

  3. Anonymous

    Posted 1 year ago

    Cool, look forward to hearing you've fixed it.


Reply

(required)