It sounds like you're experiencing a known bug, Firefox 32.0 is supposed to fix it. I've never experienced this problem myself personally, however.