Bug 428490

Summary: I don't know if it correlates, but ever since the 4.4.1 update when I use the brush engine and then go to the canvas after a few minutes Krita crashes losing all my brush tweaks.
Product: [Applications] krita Reporter: SyrenityBloom <syrenitybloom>
Component: Brush enginesAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: halla
Priority: NOR    
Version First Reported In: 4.4.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: My usage log which states there has been already 6 crashes.
Krita crash log.
attachment-18638-0.html
attachment-19977-0.html
attachment-20596-0.html

Description SyrenityBloom 2020-10-31 02:09:45 UTC
Created attachment 132899 [details]
My usage log which states there has been already 6 crashes.

SUMMARY
I don't know if it correlates, but ever since the 4.4.1 update when I use the brush engine and then go to the canvas after a few minutes Krita crashes losing all my brush tweaks. 

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT
Krita completely closes out.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

I also attached my usage log which states there has been already 6 crashes.

Krita

 Version: 4.4.1
 Languages: en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.9
  Version (loaded): 5.12.9

OS Information

  Build ABI: i386-little_endian-ilp32
  Build CPU: i386
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.19041
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10

OpenGL Info
 
  Vendor:  "Google Inc." 
  Renderer:  "ANGLE (Intel(R) Iris(R) Graphics 550 Direct3D11 vs_5_0 ps_5_0)" 
  Version:  "OpenGL ES 3.0 (ANGLE 2.1.0.57ea533f79a7)" 
  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0.57ea533f79a7)" 
  Requested format:  QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
  Current format:    QSurfaceFormat(version 3.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile) 
     Version: 3.0
     Supports deprecated functions false 
     is OpenGL ES: true 

QPA OpenGL Detection Info 
  supportsDesktopGL: true 
  supportsAngleD3D11: true 
  isQtPreferAngle: true 

Hardware Information

  GPU Acceleration: angle
  Memory: 2000 Mb
  Number of Cores: 4
  Swap Location: C:/Users/htehi/AppData/Local/Temp

Current Settings

  Current Swap Location: C:/Users/htehi/AppData/Local/Temp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 1000
  Use OpenGL: true
  Use OpenGL Texture Buffer: false
  Use AMD Vectorization Workaround: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 900
  Use Backup Files: false
  Number of Backups Kept: 1
  Backup File Suffix: ~
  Backup Location: Same Folder as the File
  Backup Location writable: false
  Use Win8 Pointer Input: false
  Use RightMiddleTabletButton Workaround: true
  Levels of Detail Enabled: false
  Use Zip64: false


Display Information
Number of screens: 1
	Screen: 0
		Name: \\.\DISPLAY1
		Depth: 32
		Scale: 2
		Resolution in pixels: 1280x720
		Manufacturer: 
		Model: 
		Refresh Rate: 59
Comment 1 Halla Rempt 2020-10-31 06:06:35 UTC
Could you please also check whether there's a kritacrash.log file the same place as the usage log?
Comment 2 SyrenityBloom 2020-10-31 16:37:37 UTC
I added the krita crash log to the attachments.
Comment 3 SyrenityBloom 2020-10-31 16:38:33 UTC
Created attachment 132921 [details]
Krita crash log.
Comment 4 SyrenityBloom 2020-10-31 22:32:14 UTC
Now its crashing every time I open a krita project.
Comment 5 Bug Janitor Service 2020-11-01 04:33:29 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.
Comment 6 SyrenityBloom 2020-11-01 04:57:00 UTC
Ok thanks.
Comment 7 SyrenityBloom 2020-11-01 04:57:30 UTC
Will I know when the issue is fixed?
Comment 8 Halla Rempt 2020-11-11 08:46:59 UTC
The crash log doesn't show just one crash, but quite a few different ones. Usually, when Krita halts on startup, there's a broken icc profile in Windows' color management folder, but that's not the case here. The latest crash happens deep inside QML, which suggests a problem with the display driver.

I'm not sure what's going on, though, and I'd first try to reset Krita's configuration and see whether that helps: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration .
Comment 9 SyrenityBloom 2020-11-11 11:26:52 UTC
Created attachment 133223 [details]
attachment-18638-0.html

Would you know why the display driver is having problems?
On Nov 11, 2020 3:47 AM, "Boudewijn Rempt" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=428490
>
> --- Comment #8 from Boudewijn Rempt <boud@valdyas.org> ---
> The crash log doesn't show just one crash, but quite a few different ones.
> Usually, when Krita halts on startup, there's a broken icc profile in
> Windows'
> color management folder, but that's not the case here. The latest crash
> happens
> deep inside QML, which suggests a problem with the display driver.
>
> I'm not sure what's going on, though, and I'd first try to reset Krita's
> configuration and see whether that helps:
> https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration .
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 10 Halla Rempt 2020-11-11 11:55:16 UTC
I can't be sure; you might want to try to switch between Angle and OpenGL in Krita's settings to see whether that helps, but please first try with clean settings.
Comment 11 SyrenityBloom 2020-11-11 12:01:37 UTC
Created attachment 133225 [details]
attachment-19977-0.html

Oh ok! Also I think the microsoft update was the problem since it was 32bit
instead of 64bit windows. I was the was one having the startup crashes. :)
On Nov 11, 2020 6:55 AM, "Boudewijn Rempt" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=428490
>
> --- Comment #10 from Boudewijn Rempt <boud@valdyas.org> ---
> I can't be sure; you might want to try to switch between Angle and OpenGL
> in
> Krita's settings to see whether that helps, but please first try with clean
> settings.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 12 Halla Rempt 2020-11-11 12:09:56 UTC
Ah, right... I thought the crash log looked familiar. In that case, I'll close this report, too, because it's the same thing.
Comment 13 SyrenityBloom 2020-11-11 12:13:47 UTC
Created attachment 133226 [details]
attachment-20596-0.html

Sounds good! Thank you so much for your time with other bug! I know it was
a simple error but you really tried to figure it out so I appreciate that!
:) Have a wonderful rest of your day! :)
On Nov 11, 2020 7:09 AM, "Boudewijn Rempt" <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=428490
>
> Boudewijn Rempt <boud@valdyas.org> changed:
>
>            What    |Removed                     |Added
> ------------------------------------------------------------
> ----------------
>              Status|REPORTED                    |RESOLVED
>          Resolution|---                         |FIXED
>
> --- Comment #12 from Boudewijn Rempt <boud@valdyas.org> ---
> Ah, right... I thought the crash log looked familiar. In that case, I'll
> close
> this report, too, because it's the same thing.
>
> --
> You are receiving this mail because:
> You reported the bug.