[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #15 from Boudewijn Rempt  ---
Okay, thanks for all the testing :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #14 from til.schmit...@gmx.de ---
i used onedrive for transfer btw

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #13 from til.schmit...@gmx.de ---
forget this thread. it had sth to do with the file. i transferred it over from
my desktop btw. i think i mentioned that somewhere.
i created a file full of gradients and kept filling layers up to 424M which is
bigger than my previouzs file. i was still able to do everything i wanted
though.
(send me an email if you wanna have a look at the problem file)

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #12 from til.schmit...@gmx.de ---
actually, i decreased the undo stack size and now i've encountered the same
problem with over 200 mb of ram unused while i was able to work on other files
with even less ram left. vram should do the trick, so shouldn't it just get
slower if the ram is used up?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #11 from til.schmit...@gmx.de ---
thanks, that sounds plausible. however, with a lower memory limit, i can't even
open the file i wanted to edit. i guess i have to protect myself from doing
that then by decreasing the memory limit, haha. 

i checked occupied ram and stuff and krita was using 600mb as well as reserving
a similar amount that isn't actually in use when the file is open with as
little as 100 mb remaining unused. does that confirm your suspicions?

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[Boudewijn Rempt]

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

--- Comment #10 from Boudewijn Rempt  ---
Yes... It's clear Krita is running out of memory. With only 1gb available
that's not so strange: just things like brushes and stuff take ~150mb. The
backtrace seems to suggest that there isn't even memory to create the temporary
data for a stroke. You might try to decrease the Memory Limit in
Krigta/Settings/performance: that memory limit is only for image data, and
krita needs lots of other data as well. If you decrease that, out of the
available memory, more will be available for krita.

And you probably shouldn't run applications like firefox together with krita on
that system: all of that takes memory.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #9 from til.schmit...@gmx.de ---
would performance logging help? it is a problem that seems to be connected to
file size after all

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #8 from til.schmit...@gmx.de ---
here's an external report i just got, maybe you can tell something more than me
from it(deleted some passages that weren't displaing anything comprehensible):

sorry in advance, idk how to add an attachment to comments on here

Hang report for C:\Program Files\Krita (x86)\bin\krita.exe
Generated by using WhatIsHang on 21.05.2018 17:56:12
Web site: http://www.nirsoft.net


Remarks:
* The program hangs in a single system call. You can look in the call stack and
 stack data to find out which API function cause this hang.
* This program hangs because it waits to another system object. The type of the
system object is Event and its handle is 0x318


Strings found in the stack:
fill:#cacaca;fill-opacity:1;stroke:none
g{h@Zx%òd*l
PMIGV|4j
! 

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[Boudewijn Rempt]

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

--- Comment #7 from Boudewijn Rempt  ---
I see... I'm not sure whether there's anything more we can actually try then
:-(

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #6 from til.schmit...@gmx.de ---
ok, so i've been trying without results for some time now and neither are there
 crash logs from the previous times, so it seems to be that krita locked up...

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #5 from til.schmit...@gmx.de ---
thanks for the quick response, i'll try to get a crashlog...

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[Boudewijn Rempt]

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

Boudewijn Rempt  changed:

   What|Removed |Added

 CC||b...@valdyas.org

--- Comment #4 from Boudewijn Rempt  ---
Hi Til,

A 32 bits Windows system cannot use more than 2gb of memory per process. By
default, Krita uses 50% of available memory, so only 1gb of memory is
available. Krita does swap out image data, but some things needs to go into
memory. One layer of your image should only take 192mb. Fourteen layers will
take 2880 mb, just for the image data, though. And there's also the projection,
the display textures, the resources like brush presets and so on.

If we've got a backtrace (https://docs.krita.org/Dr._Mingw_debugger) we might
be able to figure out a way to let you load the image on your laptop, but it
will never run fast enough to do anything useful. Krita just isn't made for
devices like this, I'm afraid.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #3 from til.schmit...@gmx.de ---
this also happened when i created a 3500 x 2400 canvas (was able to paint) and
then wanted to open the problem file. it seems to be to big for my hardware to
handle, however, at no point does krita use all my resources.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #2 from til.schmit...@gmx.de ---
actually, the problem image is 3500 x 2400 and has been created on my desktop
pc, also with krita

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 394460] modifying larger canvas crashes krita on low end system

[bugzilla_noreply]

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

--- Comment #1 from til.schmit...@gmx.de ---
i am able to paint from scratch on smaller images (example: 491 x 695 2 layers)

-- 
You are receiving this mail because:
You are watching all bug changes.