I agree with @Daniel it sounds like a memory or resource exhaustion issue. It is happening after a few hours which is typical of a slow memory leak. And what you are seeing, or not seeing, corresponds to it being unable to create any more objects due to memory/resource exhaustion.
Memory seems much more likely with Filters as they do use a lot of in particular GPU memory. You might not see any errors as Flash normally tries very hard to keep on running after errors. Normally an error causes the current event handler to halt, but it starts up again with the next ENTER_FRAME/MOUSE_DOWN/... You only see the error if you are running in a debug environment, which would be the first thing to try as once it stops drawing filters it should hopefully be generating lots of errors.
You can try enabling Starling's enableErrorChecking
for a further source of errors. And run it in Scout to see if you can spot any memory/resource issue earlier.