https://bugs.kde.org/show_bug.cgi?id=269667
--- Comment #8 from <benson bear gmail com> 2012-01-05 05:05:51 --- I can't really test it any more because I have moved to a 64 bit kernel from a 32 bit PAE kernel. The latter, as I understand it, allows only a 3G virtual user process size out of the possible 4G address space. It was when X reached the 3G limit that the problem arose. So now, my X is usually about 4G virtual size and I have no problems (in one of the above messages I erroneously suggested I might have to get a new video card -- but I saw shortly afterwards that could make no difference). People running the PAE kernels might still be concerned with this problem. Does the newer okular do anything about it? It is not clear what it could do, it would be tricky, I guess. It would have to know to what degree it was responsible for the size of the X process and then call back some of its pixmap caches when X was reaching the limit, if it was responsible. This is something that I guess would really have to be more global, with X calling back its pixmaps from apps when it got overextended, and that would require altering all the potentially problematic apps with code that handled such eventualities. I guess it will remain the task of the user for quite a while to monitor this stuff... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Okular-devel mailing list Okular-devel@kde.org https://mail.kde.org/mailman/listinfo/okular-devel
