8.3.0 pre-release running slow

Gilles Caulier caulier.gilles at gmail.com
Sat Dec 23 04:36:03 GMT 2023


Le ven. 22 déc. 2023 à 22:53, Nadine Helkenn <cnhelkenn at comcast.net> a écrit :
>
> I decided to reboot the system & run debug again.
>
> Google Drive is on my system for another purpose. DigiKam also tried to access drive A:(floppy), drive Z:(cloud storage), drive I: (Google drive); none of which are included in my DigiKam collections.

I think A: and Z: are visible in your traces because it's the whole
Windows kernel messages visible from users area; DebugView catches all
statements, not only from digiKam.

But google drive introduces time latency, i'm sure. I see the same
network behavior in my office with the local network mounts. Network
mount is a black hole under Windows. Only mount this drive on demand.

>
> Missing plug-ins,

Which ones ? A missing plugins will not introduce time latency at run
time, expected at startup, but nothing special.

>no language dictionaries,

The language dictionaries are handled by the KDE framework (Sonnet),
which is used to check string forms (for ex comments). I see the same
behavior under Linux, it's not Windows specific. I dont include a
dictionary (open-source) in the Windows bundle to prevent a heavy
size. This does not introduce a time latency, but bloat the debug
traces for sure...

>smoke test failed.

Ah, This is certainly an English form that a French guy like me
doesn't match (:-)))....

>Why is it trying to access the Google Drive?

See my comment before. DebugView messages come from all Windows, not
only digiKam...

>
> What tempest have I created here?

Nothing i think.

The difference between digiKam 8.1 and the later ones are huge for
Windows target. We use the Microsoft compiler under Windows 10 instead
Linux and the GCC cross compiler (yes the whole previous digiKam
version was not compiled under Windows but under Linux).

This opens the pandora box, with plenty of missing features from
Microsoft and typically a better compatibility, but of course it
introduces side effects.

Another difference is the switch from Qt5 to Qt6, a huge open source
framework used to build all digiKam; Here I also use a Qt6 version
under Linux without problems, but of course Windows is not Linux and
specific platform problems can appear. This is why we have a large
list of bug reports coming from Windows users for one month.

Voilà for the explanations under the Christmas tree...

Gilles Caulier


More information about the Digikam-users mailing list