Discussion:
[krita] [Bug 391850] New: Autosave lag is back
(too old to reply)
Storm Engineer
2018-03-14 11:32:28 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

Bug ID: 391850
Summary: Autosave lag is back
Product: krita
Version: git master
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: General
Assignee: krita-bugs-***@kde.org
Reporter: ***@gmail.com
Target Milestone: ---

When Krita auto-saves the whole program freezes entirely for 4-6 seconds.

If you can't reproduce, try with a large file.


I can't regression test right now, but I believe my last master build without
this issue was about one to one and a half weeks ago.
--
You are receiving this mail because:
You are watching all bug changes.
Boudewijn Rempt
2018-03-14 11:45:17 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

Boudewijn Rempt <***@valdyas.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDSINFO
CC| |***@valdyas.org
Resolution|--- |WAITINGFORINFO

--- Comment #1 from Boudewijn Rempt <***@valdyas.org> ---
Sorry, Storm, as a bug report this is completely useless. You need at least to
specify _how_ big that image of yours is; if you don't have time to test with
older appimages, you should wait with the report until you have had time. You
probably should also make a video of this that includes the entire Krita window
including all decorations.

Right now, we have nothing to go on. Please come back later with the required
information.
--
You are receiving this mail because:
You are watching all bug changes.
Storm Engineer
2018-03-15 23:01:14 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #2 from Storm Engineer <***@gmail.com> ---
Sorry, I have my limits too. I said I don't have time because building git
commits is the only method I was aware of, and that takes me 40 minutes each
time (for clean build).

I didn't know appimages of git master exist, you should have just said so.

With krita-4.0.0-beta1-b322ae6-x86_64 the issue is not present.

Freeze is proportional to the size of document. With 3000 x 3000 8bit sRGB
single layer it's 2 seconds, with 5000 x 5000 nit's 3-4. With my work file
about 4000 x 7000 16 bit and several layers it's in a range of 5-8 sec.
--
You are receiving this mail because:
You are watching all bug changes.
Storm Engineer
2018-03-15 23:06:51 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #3 from Storm Engineer <***@gmail.com> ---
Created attachment 111424
--> https://bugs.kde.org/attachment.cgi?id=111424&action=edit
video of issue
--
You are receiving this mail because:
You are watching all bug changes.
Dmitry Kazakov
2018-03-17 15:47:45 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

Dmitry Kazakov <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #4 from Dmitry Kazakov <***@gmail.com> ---
Hi, Storm!

Could you send me a screenshot of your memory configuration on the Performance
tab in the settings?

And could you make a screenshot of the About->Krita window to let me know sha1
of the commit you have?

The point is, I've just tried to reproduce the problem on my local build and I
cannot do that :(

I have the following ideas what can be the problem with your build:

1) If you build Krita yourself, you might have some very old plugins installed
(e.g. histogram had this problem is some point of time). Please try the latest
nightly build to eliminate this possibility:

https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/

2) There might also be a problem that Krita does extensive swapping while you
paint. That is why I ask about the memory settings dialog.

3) Please also tell me if you have Instant Preview enabled or not :)
--
You are receiving this mail because:
You are watching all bug changes.
Storm Engineer
2018-03-19 11:07:49 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #5 from Storm Engineer <***@gmail.com> ---
Hi Dmitry! Thanks for looking into this!

Last commit from git log is 8e738a0e0a8302322a647d42076200bed924f283 -
interestingly About Krita only says "3.3.3"

1) I build myself, and with krita-4.1.0-pre-alpha-dbd65ef-x86_64.appimage the
issue is _not_ present. So how do I fix this? I thought erasing my install dir
and then clean building does the trick.

2) Attaching screenshot, just in case.

3) Instant Preview is off.
--
You are receiving this mail because:
You are watching all bug changes.
Storm Engineer
2018-03-19 11:08:41 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #6 from Storm Engineer <***@gmail.com> ---
Created attachment 111494
--> https://bugs.kde.org/attachment.cgi?id=111494&action=edit
Performance settings screenshot
--
You are receiving this mail because:
You are watching all bug changes.
Boudewijn Rempt
2018-03-19 12:13:32 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

Boudewijn Rempt <***@valdyas.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |INVALID
Status|NEEDSINFO |RESOLVED

--- Comment #7 from Boudewijn Rempt <***@valdyas.org> ---
If you build yourself, make sure the build type is Release, RelWithDebInfo or
KritaDevs. Make sure you have all deps, especially Vc. Removing the install dir
should be enough to make sure you don't have any old plugins about. Beyond
that, there isn't much we can do now.
--
You are receiving this mail because:
You are watching all bug changes.
Storm Engineer
2018-03-20 12:29:13 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #8 from Storm Engineer <***@gmail.com> ---
I did everything you said and the issue is still there.

- type is RelWithDebInfo
- wiped my build dir and install dir
- all deps installed, including Vc and all optional
- pulled master fresh
--
You are receiving this mail because:
You are watching all bug changes.
Dmitry Kazakov
2018-04-05 07:10:43 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391850

--- Comment #9 from Dmitry Kazakov <***@gmail.com> ---
Hi, Storm!

Did you try resetting your settings directory? That looks extremely weird that
you don't have the issue with the appimage and have it with a manually built
build. I have the following guesses:

1) Recommended value for "Internal Pool" now is "0%", please set it to null.
2) If it doesn't help, try resetting all configuration directories [0]
3) If it doesn't help either, it means you have some weird problems with your
local build... Try using AppImage instead :)


[0] - https://docs.krita.org/KritaFAQ#Resetting_Krita_configuration
--
You are receiving this mail because:
You are watching all bug changes.
Loading...