https://bugs.kde.org/show_bug.cgi?id=375716
--- Comment #7 from Edward <look7...@gmail.com> --- Thanks for the clarification. All the best. On Jan 31, 2017 9:50 AM, "Boudewijn Rempt" <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=375716 > > Boudewijn Rempt <b...@valdyas.org> changed: > > What |Removed |Added > ------------------------------------------------------------ > ---------------- > Ever confirmed|0 |1 > Status|UNCONFIRMED |CONFIRMED > Summary|Krita Crashes when |32 bits Krita crashes if > |predifined A3 @ 600P.p.i |the initial image is too > |canvas creation. |big for the available > | |memory > > --- Comment #6 from Boudewijn Rempt <b...@valdyas.org> --- > I cannot check the code for Photoshop and Corel Painter, so whatever they > do, > isn't relevant for Krita. > > On a 32 bits Windows, you can only allocate 2GB per process. Krita by > default > allows half of the available memory for an image, that is 1GB. If the > image is > too big it tries to swap it out to disk, but that also needs memory, and I > suspect that that just isn't available. You can fiddle with the performance > settings, making Krita use 2GB of memory, for instance, instead of 3/2 = > 1.5, > reduce undo steps and so on. See https://docs.krita.org/ > Performance_Settings > > Btw, the actual PPI isn't relevant; it's only the number of pixels that is > relevant. Memory usage is width * height * number of bytes per pixel * > number > of layers + 1, roughly. > > But the bottom line is that a 7016x9920 pixel image just is too big for > your > computer. You will also have trouble actually painting on an image that > size. > There isn't much we can do at this point, I'm afraid. > > -- > You are receiving this mail because: > You reported the bug. > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
