https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
Latest Commit|https://commits.kde.org/kri |https://commits.kde.org/kri
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #11 from Boudewijn Rempt ---
I am not sure I follow that logic... Shouldn't that assert for everyone then?
Plus, savingImage() returns the actual image, the pointer should be valid.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #10 from Dmitry Kazakov ---
Heh... I just checked... the crash Boud and Bruno has happens most probably
dues to the "clone-image-on-saved-disabled" patch. KraExport::convert()
accesses KisDocument::savingImage() and checks it with Q_CHECK_PT
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #9 from Bruno P. Kinoshita ---
FWIW, when I reduced the memory settings to 1 GB, it would still work, but then
I noticed the virtual memory in htop, and after reducing the virtual memory the
issue happened.
Maybe she has 16 gb but her virtu
https://bugs.kde.org/show_bug.cgi?id=376382
Dmitry Kazakov changed:
What|Removed |Added
CC||dimul...@gmail.com
--- Comment #8 from Dmitry
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #7 from Bruno P. Kinoshita ---
Not a problem Boudewijn. Sounds interesting. Will keep an eye for the commit
diff to learn how to fix this kind of problems. Guess I'm not able to produce a
patch for it at the moment, but hopefully with some p
https://bugs.kde.org/show_bug.cgi?id=376382
Boudewijn Rempt changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #5 from Bruno P. Kinoshita ---
I think you are right Boudewijn.
Here's how I (think I) reproduced it.
1. Play a while reproducing the issue, looking at top or htop to look at the
memory and virtual memory numbers.
2. Guess the amount of vi
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #4 from Boudewijn Rempt ---
I suspect Kate's computer may be running out of memory. I've just tried to
reproduce, and didn't get a crash, though I did see
Error std::bad_alloc sending event 63 to object
In the output. I still need a crash
https://bugs.kde.org/show_bug.cgi?id=376382
Bruno P. Kinoshita changed:
What|Removed |Added
CC||brunodepau...@yahoo.com.br
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=376382
Boudewijn Rempt changed:
What|Removed |Added
CC||b...@valdyas.org
--- Comment #2 from Boudewij
https://bugs.kde.org/show_bug.cgi?id=376382
--- Comment #1 from katearche...@yandex.ru ---
oh, the specs: win7sp3, gtx965m, i7, 16gb
--
You are receiving this mail because:
You are watching all bug changes.
19 matches
Mail list logo