Hi,
>> Some of the Flash content on the web is not really ... well ...
>
> No thats not how the rules are. Bad content may not crash
> applications, especially if you can't trust the guy how created the
> content. If a flash file is broken it may not be loaded, not crash
> the browser.
What I meant is that some Flash content may happily (try to) consume
100MBs of RAM. I guess Flash and Opera deal with running out of memory
OK, but Gtk (with which the application UIs are done with) most
definately does not. For Gtk, the Glib allocations abort the process
if Glib allocation fails[1] (and even if Glib alloc functions would be
changed to return NULL when alloc fails instead of aborting, Gtk widgets
don't have additional code to handle this gracefully[2]).
[1] Mentioned e.g. in my ancient Gtk study:
http://www.movial.fi/client-data/file/movial_gtk1.pdf
[2] By e.g. showing only "half" of the UI? :-)
- Eero
_______________________________________________
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
