Bug 423384

Summary: freezes/crashes on redo of rectangle
Product: [Applications] krita Reporter: chipet92s
Component: ToolsAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: ahab.greybeard, halla
Priority: NOR    
Version First Reported In: 4.3.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: attachment-16848-0.html

Description chipet92s 2020-06-23 06:36:22 UTC
SUMMARY 

Sometimes the program freezes when trying to redo. I think it happened only with rectangles (Drawing them with the rectangle tool), this happened to me at least 3 times.
When it happens, if I try to close the document it keeps waiting to some process to finish ("creating" something. sorry, I don't remember exactly), gives me 3 options and none of them work (wait and then save the document, close without saving, and another one). Then I wait and the program crashes.

STEPS TO REPRODUCE

Undo and redo a rectangle.

OBSERVED RESULT

I tried to reproduce it but, instead of freezing, the only time I managed to do it, Krita just closed automatically without any type warning.

EXPECTED RESULT


SOFTWARE/OS VERSIONS

Krita

 Version: 4.3.0
 Languages: es_ES, es, en_US, en
 Hidpi: true

Qt

  Version (compiled): 5.12.8
  Version (loaded): 5.12.8

OS Information

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

OpenGL Info
 
  Vendor:  "NVIDIA Corporation" 
  Renderer:  "GeForce GTX 980 Ti/PCIe/SSE2" 
  Version:  "4.6.0 NVIDIA 446.14" 
  Shading language:  "4.60 NVIDIA" 
  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 4.6, options QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::sRGBColorSpace, profile  QSurfaceFormat::CompatibilityProfile) 
     Version: 4.6
     Supports deprecated functions true 
     is OpenGL ES: false 

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

Hardware Information

  GPU Acceleration: auto
  Memory: 16333 Mb
  Number of Cores: 8
  Swap Location: C:/Users/MIP/AppData/Local/Temp

Current Settings

  Current Swap Location: C:/Users/MIP/AppData/Local/Temp
  Current Swap Location writable: true
  Undo Enabled: true
  Undo Stack Limit: 30
  Use OpenGL: true
  Use OpenGL Texture Buffer: true
  Use AMD Vectorization Workaround: false
  Canvas State: OPENGL_SUCCESS
  Autosave Interval: 900
  Use Backup Files: true
  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: false
  Levels of Detail Enabled: false
  Use Zip64: false
Comment 1 Halla Rempt 2020-06-23 09:19:48 UTC
* Does this happen with rectangles on a paint layer or on a vector layer?
* Could you please check whether there's kritacrash.log file in .appdata/local? 
* Could you also attach the output of help->Show Krita log for bug reports?
Comment 2 Ahab Greybeard 2020-06-26 15:38:23 UTC
It may not be the same situation as the OP but I can induce such a crash with the 4.2.9 and 4.3.0 appimages.

The latest 4.3.1 alpha and 5.0.0 prealpha appimages do not show the crash.

STEPS TO REPRODUCE:
1. Create a vector layer and draw a shape.
2. Do Edit -> Undo Create Shape
3 In the Layers docker, select a paint layer
NOTE that the Edit menu offers Undo Add Layer and Redo Create Shape
4. Do Edit -> Redo Create Shape

OBSERVED RESULT
A 'Create shape' progress bar, always at 50% progress, appears on the status bar  and it just stays there with 0% CPU usage.
At this stage you can create a new image and work on it normally.
If you go back to the original tab then the stuck progress bar comes back along with a window that says the same thing and can not be closed for long. Total freeze up which needs a Kill.
The log says KRITA DID NOT CLOSE CORRECTLY.
The terminal has no information related to this.
Comment 3 chipet92s 2020-07-05 21:41:25 UTC
Created attachment 129926 [details]
attachment-16848-0.html

 Sorry for the delay.
Yes, that's exactly the problem I was having. Thanks.

El vie., 26 de jun. de 2020 a la(s) 12:38, Ahab Greybeard (
bugzilla_noreply@kde.org) escribió:

> https://bugs.kde.org/show_bug.cgi?id=423384
>
> Ahab Greybeard <ahab.greybeard@hotmail.co.uk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|
> |ahab.greybeard@hotmail.co.u
>                    |                            |k
>
> --- Comment #2 from Ahab Greybeard <ahab.greybeard@hotmail.co.uk> ---
> It may not be the same situation as the OP but I can induce such a crash
> with
> the 4.2.9 and 4.3.0 appimages.
>
> The latest 4.3.1 alpha and 5.0.0 prealpha appimages do not show the crash.
>
> STEPS TO REPRODUCE:
> 1. Create a vector layer and draw a shape.
> 2. Do Edit -> Undo Create Shape
> 3 In the Layers docker, select a paint layer
> NOTE that the Edit menu offers Undo Add Layer and Redo Create Shape
> 4. Do Edit -> Redo Create Shape
>
> OBSERVED RESULT
> A 'Create shape' progress bar, always at 50% progress, appears on the
> status
> bar  and it just stays there with 0% CPU usage.
> At this stage you can create a new image and work on it normally.
> If you go back to the original tab then the stuck progress bar comes back
> along
> with a window that says the same thing and can not be closed for long.
> Total
> freeze up which needs a Kill.
> The log says KRITA DID NOT CLOSE CORRECTLY.
> The terminal has no information related to this.
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 4 Bug Janitor Service 2020-07-06 04:33:09 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 5 Ahab Greybeard 2020-07-06 05:31:23 UTC
The Stable/Plus Linux appimage does not have the bug so it seems to have been fixed.

Please download and use the Stable/Plus Windows package from here:
https://binary-factory.kde.org/job/Krita_Stable_Windows_Build/
Either the -setup.exe or the portable -.zip package as you prefer.

If it works for you, please set this bug report to Resolved Fixed.
Comment 6 Bug Janitor Service 2020-07-21 04:33:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2020-08-05 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!