Messages in this thread | | | Date | Wed, 22 Jan 2014 23:19:28 +0400 | From | Cyrill Gorcunov <> | Subject | Re: [Bug 67651] Bisected: Lots of fragmented mmaps cause gimp to fail in 3.12 after exceeding vm_max_map_count |
| |
On Wed, Jan 22, 2014 at 07:08:16PM +0000, Mel Gorman wrote: > Cyrill, > > Gimp is broken due to a kernel bug included in 3.12. It cannot open > large files without failing memory allocations due to exceeding > vm.max_map_count. The relevant bugzilla entries are > > https://bugzilla.kernel.org/show_bug.cgi?id=67651 > https://bugzilla.gnome.org/show_bug.cgi?id=719619#c0 > > They include details on how to reproduce the issue. In my case, a > failure shows messages like this > > (gimp:11768): GLib-ERROR **: gmem.c:110: failed to allocate 4096 bytes > > (file-tiff-load:12038): LibGimpBase-WARNING **: file-tiff-load: gimp_wire_read(): error > xinit: connection to X server lost > > waiting for X server to shut down > /usr/lib64/gimp/2.0/plug-ins/file-tiff-load terminated: Hangup > /usr/lib64/gimp/2.0/plug-ins/script-fu terminated: Hangup > /usr/lib64/gimp/2.0/plug-ins/script-fu terminated: Hangup > > X-related junk is there was because I was using a headless server and > xinit directly to launch gimp to reproduce the bug. > > Automated bisection using mmtests (https://github.com/gormanm/mmtests) > and the configuration file configs/config-global-dhp__gimp-simple (needs > local web server with a copy of the image file) identified the following > commit. Test case was simple -- try and open the large file described in > the bug. I did not investigate the patch itself as I'm just reporting > the results of the bisection. If I had to guess, I'd say that VMA > merging has been affected.
Thanks a lot for report, Mel! I'm investigating...
| |