Version: unspecified (using KDE 4.6.2) OS: Linux Performing instructions below, krita behaves abnormally. The second time i reproduced it, krita nearly crashed everything, thankfully i was able to issue a kill from another vt. Reproducible: Always Steps to Reproduce: open image (source, a negative scanned with xsane) $ file neg1 neg1: TIFF image data, little-endian Image Properties: W: 7596 H: 1552 R: 1200,00 ppi Model: YCbCr Depth: 8 Bits Profile: Standar YCbCr (8-Bits) *Now i select with rectange one of the photos in the negative *Edit copy, edit paste as new image, then * Filter > Colors > Color transfer... Actual Results: The first time, krita just closed. no crash, no logs, no abrt. The second time krita freeze, and then amarok had problems with keeping up with audio, then desktop became unresponsive and the hard disk started to swap like hell. I had to switch to another vt and with patience issue a manual kill of krita. (8GB RAM + 8GB SWAP) Amarok crashed when returned to kde. Expected Results: normal program behaviour, or a [error] message, if the requested operation is invalid. koffice-krita-2.3.3-4.fc15.x86_64 koffice-krita-libs-2.3.3-4.fc15.x86_64
Created attachment 59659 [details] xsession-errors contents of the .xession-erros file for the affected user (has krita crashing references so it may be usefull)
Hi Reartes, Thanks for your report. I haven't been able to reproduce yet, but I did find a new bug in paste as new image, and it's quite possible that this problem only happens on 64 bit systems. We will investigate some more.
I just triaged this bug in a 64 bit system with Krita trunk. I'm using Debian Squeeze. The images I tested ranged from 1000x1000 to 2000x2000, RGB 8 bit format. I experienced the following perfectly reproducible symptoms: --The image pasted didn't actually appear, all I got was a transparent canvas. --Upon closing Krita, it freezes and starts to slowly seep my memory, 4 MB of memory every 3-10 seconds. I think this partially confirms the bug.
Hi Reartes, I just realized I fixed this bug in commit 0a3fa8fb560dc983bf682fe1f4680747ebb45f47 -- this is available in 2.4 beta 1 and beta 2.