Carsten Haitzler (The Rasterman) <ras...@rasterman.com> writes: > so as a result, evas is following a much stricter clean "init and shtudown > when > u are done" model which at least allows you to write an app, use evas, then > stop using it and for the next 10 weeks run it without ever using evas again > and > have stuff freed/shut down and out of memory (hopefully). if we don't init and > shutdown .. then you keep resources around - in practice, not a problem, but > in > theory, can be. > > one big nasty though... fc maintains fc cache files. in ~/.fontconfig.... > files > survive a process exit. if any of these files were intended to be cleaned up > on > shutdown (normally are not - but let's assume fc's internals change to need to > do this) we may see apps leaking junk/files/garbage in ~/.fontconfig if we are > not letting fc know that t we are done and want to delete such out-of-process > resources on a "clean" shutdown (yes a segv and so on will leave junk... thats > life)
I understand your points. And judging from what you wrote, not calling FcFini() is a no-go for evas, right? In this case, can you think of another solution for the problem that doesn't involve changing WebKit and/or fontconfig? ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_jan _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
