[Okular-devel] [okular] [Bug 320753] Okular crashed when searching large document

[Fabio D'Urso]

https://bugs.kde.org/show_bug.cgi?id=320753

--- Comment #16 from Fabio D'Urso <fabiodurso at hotmail.it> ---
(In reply to comment #15)
> However, the reason for the crash this time seems to be
> that valgrind ran out of memory. I have 16 GB RAM, but run 32-bit Kubuntu
> with PAE. I don't see any "Painter not active" messages this time.
Makes sense, the algorithm that decides when to stop allocating only looks at
the amount of physical memory, and it ignores the fact that you can't allocate
more than 3GB under 32-bit linux.

@Albert: In the light of this, the "QPainter::begin: Paint device returned
engine == 0, type: 3" might be a result of a failed allocation too, what do you
think? A failed new is supposed to throw an exception instead of returning
NULL, but it's possible that Qt is using plain malloc or nothrow new somewhere.

-- 
You are receiving this mail because:
You are the assignee for the bug.