Bug 406555 - Frequent and unexpected unresponsiveness.
Summary: Frequent and unexpected unresponsiveness.
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Brush engines (show other bugs)
Version: 4.1.7
Platform: unspecified Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-15 07:51 UTC by 3flow
Modified: 2019-05-15 04:33 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 3flow 2019-04-15 07:51:49 UTC
SUMMARY
Essentially a frequent but random problem where brush or any other action suddenly stops working and a dialog pops up stating - 'Waiting for image operation to complete...'. 

Saving is impossible.

The only way to get out of it is to kill Krita in the Task manager, losing the work done.

This is happening constantly but unexpectedly. It's happened at least 6 times today and I've lost a lot of work consequently. 

Essentially it's unusable at the moment. Windows update occurred yesterday and maybe connected.

STEPS TO REPRODUCE
1. Use the program until it ceases to respond. There doesn't appear to be any specific action that triggers this 
2. 
3. 

OBSERVED RESULT

Unresponsiveness and a dialog that won't close as mentioned above if you attempt to save the work. 

EXPECTED RESULT


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

ADDITIONAL INFORMATION

Krita
  Version: 4.1.7

Qt
  Version (compiled): 5.9.3
  Version (loaded): 5.9.3

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

OpenGL Info
  **OpenGL not initialized**

Intel(r) Core i7-7500U @ 2.70GHz 2.90GHz
32GB
NVidia GTX 950M
Comment 1 Halla Rempt 2019-04-15 07:55:09 UTC
Yes, it sounds like it may be connected to your windows update or system state, because, of course, this isn't normal. That also means there really isn't something we can do to investigate because we don't have access to your system.

* what color model, channel depth and size are your images?
* can you make a crash log (see https://docs.krita.org/en/reference_manual/dr_minw_debugger.html#dr-minw)
* does this happen if you run Krita as administrator?
* can you check whether this helps if you use the latest nightly build (download the zip file and copy the folder to your desktop): https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/
Comment 2 Bug Janitor Service 2019-04-30 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 3 Bug Janitor Service 2019-05-15 04:33:13 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!