Hi Arcana, Depending on how long you expect your app to run without restart, you may also want to avoid Flash because in a application setting with constant Flash there appears to be really dramatic memory leaks (will crash a 512MB Linux in about 24 hours).
The leakage behavior is reproduceable in Firefox too, linking from HTML screen to screen using html timeouts every few seconds where each screen contains a Flash movie produces huge leaks, on both Windows and Linux. However, this is obviously not a normal browsing situation for hours on end so I don't think it's a priority right now for mainstream browser development, and of course it could be an Adobe problem too. Depending on how you are embedding, intercepting and validating content before rendering doesn't necessarily work either, because not all the call backs work yet as published, and some attempts to hook events result in crashes on some configurations. The only way we found to really get control of the browser reliably on all platforms was to point it to a local server, intercept everything from the browser, and then use the local server to control what the browser did and did not get, but I'm not sure whether that approach would work with Flash (we weren't looking for Flash events). (Seems embedding is still the poor cousin but not complaining because maybe that's the way it has to be for us to gain from all the mainstream development.) Regards, J _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
