Yeah, that has been my experience. However, Jeff (AM List maintainer) has pawned this off as likely being a firefox bug since he is having no signs of this, as is the norm with most bugs I and others seem to report, although the bug completely disappears after changing an option in ad muncher or exiting it completely. This seems to be the norm from my experience.
I just fail to see how the bug could be firefox's fault when ad muncher's options (or exiting) fixes the issue. Can anyone explain this to me?
Mouser or any developer for that matter, from your experience, does this explanation make sense? In my limited development experience (limited to programs suiting my own particular needs) this doesnt make sense. If my program, when terminated, resolves an issue, or enabling an option in my developed program fixes a problem in another, how can this bug not be my programs fault?