Bug 452145 - Changing the Colour Model often causes a crash
Summary: Changing the Colour Model often causes a crash
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Color models (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: Dmitry Kazakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-01 10:14 UTC by Ahab Greybeard
Modified: 2022-04-19 05:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ahab Greybeard 2022-04-01 10:14:28 UTC
SUMMARY
This bug is not present in the Mar 29 5.1.0-prealpha and previous versions.
It was introduced in the Mar 30 5.1.0-prealpha (git b1e8749c17) and is reported for the Mar 31 5.1.0-prealpha (git 625152f808) appimage on Debian 10.

Commit f5d73bbf0c5cac5c3746abdaab1242815d2ab719 seems to be related.

STEPS TO REPRODUCE
1. With a fresh session, create a new RGB/A image.
2. Create a new Grayscale/Alpha image
3. If no crash, create a new RGB/A image
4. If no crash, convert the RGB/A image to Greyscale/Alpha
5. If no crash, Close each image in turn.

OBSERVED RESULT
2. With a fresh session, a crash often happens
3. A crash sometimes happens
4. A crash sometimes happens
5. A crash sometimes happens

This has also been seen with other colour model changes.
It does not seem to be related to bit depth changes.
It doesn't happen every time so it's difficult to do detailed structured tests.

The terminal says "Segmentation fault".

EXPECTED RESULT
Not crash.

SOFTWARE/OS VERSIONS
Krita

 Version: 5.1.0-prealpha (git 625152f)
 Languages: en_GB, en, en, en_GB, en
 Hidpi: false

Qt

  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 4.19.0-20-amd64
  Pretty Productname: Debian GNU/Linux 10 (buster)
  Product Type: debian
  Product Version: 10
  Desktop: MATE

OpenGL Info
 
  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 750 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 460.73.01" 
  Shading language:  "4.60 NVIDIA" 
  Requested format:  QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
  Current format:  QSurfaceFormat(version 4.6, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 0, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
     Version: 4.6
     Supports deprecated functions true 
     is OpenGL ES: false
Comment 1 Dmitry Kazakov 2022-04-18 11:56:54 UTC
Hi, Ahab!

I tried to reproduce the issue with the full ASAN build, but it seems to work fine here :( Could you do the following test for me?

1) Download the ASAN-enabled package from this post:
    https://krita-artists.org/t/krita-5-0-is-extremely-unstable-constant-crashes/39225/34?u=dkazakov
2) Try to reproduce the issue
3) If you manage to reproduce the crash, send me the log from ASAN **and** the list/screenshot of the dockers you had open while you were testing the bug.
Comment 2 Ahab Greybeard 2022-04-18 13:46:41 UTC
Hi Dimitry :)

Thank you for reminding me about this.
I tried the ASAN build but had difficulty getting it to run. 

However, after many runs of 5.0.5, the Apr 03 5.1.0-prealpha and the Apr 17 5.1.0-prealpha, I can't get it to crash with a variety of colour model changes and conversions.
(I no longer have the March 29 and March 31 builds.)

Please set this to Resolved Fixed if you feel this is the best thing to do.
Comment 3 Bug Janitor Service 2022-04-19 04:35:13 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.