https://bugs.kde.org/show_bug.cgi?id=518169
--- Comment #6 from Noel Santos <[email protected]> --- (In reply to Dmitry Kazakov from comment #5) > Hi, Noel! > > Do you have a lot of custom fonts in your system? Could you, perhaps, send > me your resourcecache.sqlite file privately, so I could look into that? I probably have 10 or fewer custom fonts installed. I generally only use Noto for writing things, and I think Noto comes installed by default. If it doesn't, then I guess I do have "a lot" of the same font since Noto comes with dozens of different variations of the same font. But I don't think that's the problem. I have already attached to the bug report the resourcecache.sqlite file that was created after 15 minutes of "Loading Resources" when I created this bug report. I could send to you the resourcescache.sqlite after successfully loading, but I don't think it would make much difference. I don't see any font names in the resources table of the sqlite I attached, so it's taking an extremely long to load things that aren't even fonts. It occurs to me that I never tried re-running Krita after it successfully loaded. So I'm adding this to the report: it loads quickly the second time. So it's really creating the database or the first-time set up that is taking forever. After the first time it loads quickly. Maybe it's just the "foreign_keys" constraint being enabled that is making it slow? The database does seem to have indexes for all foreign keys, so I'm not sure how could that be it, but I thought it was weird that Krita logged that message for 5.3.0 even though it doesn't happen for 5.2.9. Everyone is downloading the same .appimage as me, right? So everyone is running it with the foreign keys constraint enabled? I wonder if it's really just me having this issue? -- You are receiving this mail because: You are watching all bug changes.
