Yesterday, I downloaded the nightly build and I noticed that it crashes when I open two documents at the same time. This is also the case for today’s nightly. I found this strange, so I downloaded the nightly from November 2, which this does not occur.
Also in nightly, from November 2nd to today’s, there is a strange banding visible on the canvas that is caused when I am using the crop tool and removing parts of the image.
For the 5.2.0-prealpha appimage running on Debian 10, The Nov 07 and Nov 06 builds are unchanged from the Nov 05 build.
I have the Nov 05 build crash when running normally and opening a simple .kra file.
If I run it from the terminal, it doesn’t crash with that simple .kra file.
If I run it normally and open a ‘complex’ .kra file, it crashes immediately.
Running from the terminal has a complex file crash final terminal output of:
“ForegroundNormal” - conversion from “0” to QColor failed
“ForegroundNormal” - conversion from “0” to QColor failed
“ForegroundNormal” - conversion from “0” to QColor failed
“ForegroundNormal” - conversion from “0” to QColor failed
Segmentation fault
The Nov 03 build can open both the simple .kra file and then the complex .kra file with no problems.
Please make a bug report and post a link to it here.
That Crop tool banding is ghosting of the crop tool rectangle outline when its size/position is changed.
It’s not there when Canvas Graphics Acceleration is off so I think it’s just cosmetic but it’s not a good look.
Please make a separate bug report for that and post a link to it here.
Do the files that trigger the crash contain Reference Images, Vector Layers, Selection Masks, or something similar? The Nov. 5 build (git 4225dada) contains a crash when importing Reference Images. That’s the most likely set of changes made since the Nov. 3 (c64143d8) build.
If you can provide a crash log, that could help to confirm the cause.
As for the "ForegroundNormal" - conversion from "0" to QColor failed message, I have no idea where it’s coming from or whether it’s relevant.
Ah… The ‘simple’ file has vector layers and a clone layer with a filter mask on it (but it is actually quite simple).
The ‘complex’ file has vector layers and vector text (and animation) but no Reference Images or Selection Masks.
Using two other .kra files that have none of the features you mentioned, I can open them both at the same time with no crashing, even though one of them has an animated transform mask.
I can try to get a crash log from a Windows 10 system tomorrow.
Yes, if you could please.
It looks like problems were introduced after the Nov 03 build, which seems ok so far.
Forrmal bug reporting takes a little bit of getting used to but it’s not all that difficult after you’ve had some experience with it
For the team to start working on 461595 – Crashes When Two or More Documents are Opened, they need two documents where the crash occurs when they are opened together. I have attempted to attach my files; however, they are both too large to be attached. Does someone have this same crash and can attach two documents?