https://bugs.kde.org/show_bug.cgi?id=406531
Boudewijn Rempt changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=406531
--- Comment #8 from Dmitry Kazakov ---
I cannot reproduce the problem either :(
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406531
Boudewijn Rempt changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=406531
--- Comment #6 from Boudewijn Rempt ---
I tested on a 32gb system.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406531
tus...@vista.aero changed:
What|Removed |Added
CC||tus...@vista.aero
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=406531
--- Comment #4 from Scott Petrovic ---
this computer has 8GB of RAM too. Not sure how much that might play into it if
it is starting to use swap space
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406531
--- Comment #3 from Boudewijn Rempt ---
merge down starts a different and longer calculation though. I couldn't
reproduce the hang locally, but, like I said, this needs investigation :-)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=406531
--- Comment #2 from Scott Petrovic ---
I am believing more it is specific to how merge down works. Simply deleting
the layer and hitting save has no issues.
It is large. This is for a banner graphic that I have at the conventions. I am
just trying to
https://bugs.kde.org/show_bug.cgi?id=406531
Boudewijn Rempt changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
