Note your .capx URL is incomplete.
This is occasionally reported, but it is a bug in Windows itself. Each process can only create up to 10,000 graphics objects, which is a limitation in Windows since the 16-bit days and has never been lifted. I am amazed that anyone would actually run in to this limit; I've no idea how you could need so many frames, and anyway this seems contrary to our advice on conserving memory.
Anyway there's not much we can do about this in C2, but C3 is being architected with this limit in mind. Exporting your project is a slower way to test, but the spritesheeting on export usually brings the image count back under the limit. If another browser works then you can always test with that as well, I guess maybe Firefox have their own graphics engine that doesn't depend on the OS and can go further.