Bug 393800

Summary:	Krita 4 autosave and save are not running on separate thread.
Product:	[Applications] krita	Reporter:	SirPigeonz <GBirdboy>
Component:	General	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	halla
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.0.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description SirPigeonz 2018-05-03 11:39:11 UTC

Hello,

I've noticed that autosave and save are not running in separate thread on my machine. It results in freeze every autosave or ctrl+S.
My girlfriend has exact same hardware with Ubuntu but on her machine Krita saves 2GiB file with no lag.

Ubuntu 17.10
RAM 15,6 GiB
Intel® Core™ i7-7700 CPU @ 3.60GHz × 8
GeForce GTX 1070/PCIe/SSE2
AppImage Krita version.

Can I provide more info on the matter somehow?

Thx in advance.

Comment 1 Halla Rempt 2018-05-03 11:45:41 UTC

If on two instances of the same hardware, the same os and the same version of Krita, Krita behaves differently, then there must be a difference between the two systems after all. Until we know what that difference is, we cannot investigate this report.

Comment 2 SirPigeonz 2018-05-03 14:19:32 UTC

It might be my Krita settings?
Some pointers what to check?

Comment 3 Halla Rempt 2018-05-03 15:48:52 UTC

I doubt that... You could try to backup your .config/kritarc and try with a fresh config, but there's nothing in the config that influences this. H**k... looking at the code there's no way saving can happen in the gui thread anymore! This is very mysterious.

Comment 4 Andrew Crouthamel 2018-09-28 03:36:19 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 set the bug status 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 5 Andrew Crouthamel 2018-10-29 02:00:31 UTC

Dear Bug Submitter,

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!