Bug 449510

Summary:	Memory occupancy keeps going up on launching & No responded
Product:	[Applications] digikam	Reporter:	tunghaoyv
Component:	Database-Scan	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	7.5.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:	7.6.0
Sentry Crash Report:
Attachments:	the crash log I recorded follow the instruction on the help page was beyond 4000KB so I paste several lines at the beginning and end

Description tunghaoyv 2022-02-02 17:04:00 UTC

SUMMARY
The first time I launched digikam after installed, digikam shows Not Responsed in window title and the memory occupancy keeps going up.

SOFTWARE/OS VERSIONS
Windows: Windows 10 Education	19044.1503
Windows Feature Experience Pack 120.2212.4170.0

ADDITIONAL INFORMATION
The mojibake in the log should be the Chinese character as my system language is Chinese.
I recently reseted my PC and tried scoop(https://github.com/ScoopInstaller/scoop/), and  the sha-256 of the installer was checked. As digikam didnt work, I uninstalled it in the scoop and installed via installer normally, but the same crash still happened. It worked well before the reset.

Comment 1 tunghaoyv 2022-02-02 17:14:29 UTC

Created attachment 146185 [details]
the crash log I recorded follow the instruction on the help page was beyond 4000KB so I paste several lines at the beginning and end

Comment 2 caulier.gilles 2022-02-02 17:41:57 UTC

You must be found a crash report at this place :

00072610	399.20111084	[4624] digikam.general: DrMinGw crash-file will be located at:  "C:\\Users\\Randir\\AppData\\Local\\digikam_crash.log"

Comment 3 caulier.gilles 2022-02-02 17:43:16 UTC

why ffmpeg is used to parse JPEG files ???

00072324	88.10531616	[5808] digikam.database: Finishing took 4 ms	
00072325	88.13052368	[5808] digikam.metaengine: -- FFMpeg video stream metadata entries :	
00072326	88.13484192	[5808] digikam.metaengine: Loading metadata with "Exiv2" backend from "D:/Randir/Pictures/�ֻ���Ƭ/��������/202107����/IMG_20210721_181738.jpg"	
00072327	88.13768005	[5808] digikam.metaengine: QMap(("creation_time", "2018-08-03T12:28:27.000000Z")("handler_name", "VideoHandle")("language", "eng")("rotate", "90"))	
00072328	88.14143372	[5808] digikam.dimg: "D:/Randir/Pictures/�ֻ���Ƭ/��������/202107����/IMG_20210721_181738.jpg" : "JPEG" file identified	
00072329	88.14646912	[5808] digikam.metaengine: -----------------------------------------	
00072330	88.15254974	[5808] digikam.dimg.jpeg: Start of Image  ( 1 )	
00072331	88.15763092	[5808] digikam.metaengine: Exif.Image.Orientation tag set to: 6	
00072332	88.16056824	[5808] digikam.dimg.jpeg: Miscellaneous marker 0xe1, length 48357  ( 1 )	
00072333	88.16339874	[5808] digikam.metaengine: -- FFMpeg audio stream metadata entries :	
00072334	164.74880981	[7484] Error 16 (unavailable resource, function or feature) in function AudioGraphSettings::CCachedSettingsRepository::HasValue	
00072335	164.74894714	[7484] Error 16 (unavailable resource, function or feature) in function AudioGraphSettings::CCachedSettingsRepository::HasValue	
00072336	164.74897766	[7484] Error 16 (unavailable resource, function or feature) in function AudioGraphSettings::CCachedSettingsRepository::HasValue	
00072337	164.74905396	[7484] Error 10 (argument is out of bounds) in function AudioGraphSettings::CRegistrySettingsRepository::ReadSetting	
00072338	164.74908447	[7484] Error 10 (argument is out of bounds) in function AudioGraphSettings::CRegistrySettingsRepository::ReadSetting

Comment 4 Maik Qualmann 2022-02-02 17:43:46 UTC

Does digiKam close by itself? The log doesn't really show a problem. However, your collection appears to be completely rescanned, which would explain digiKam being very busy and not responding.

Maik

Comment 5 Maik Qualmann 2022-02-02 17:44:54 UTC

Yes, I've seen that with ffmpeg too, that's strange. Since there is no previous entry that a video file was found.

Maik

Comment 6 caulier.gilles 2022-02-02 17:48:36 UTC

So typically the crash appear while scanning collection, collecting metadata to record information in database.

The strange behavior is to use ffmpeg to parse JPEG. This never happen.

What do set in digiKam/Setup/Views/Mime-types dialog page ? Did you put JPEG or JPG in video section ?

Best

Gilles Caulier

Comment 7 Maik Qualmann 2022-02-02 17:54:40 UTC

I could imagine that DebugView "swallowed" debug output here. I've observed that before. A new log would be good.

Maik

Comment 8 tunghaoyv 2022-02-03 07:05:26 UTC

Briefly speaking, it worked well again but DebugView crashed this time thus I failed to save any helpful infomation. My feeling is beyond words......

I uninstalled digikam again 02:00 am and went to sleep. This morning I installed it and ran the DebugView the fifth time. It crashed at first launch. Alright, I thought, according to the comment there should be some trouble scanning media folder, so I moved the media folder out from the database, deleted the 'digikamrc' in 'APPDATA' folder and the existing 'digikam.db'. (In fact, I tried this way before and it didn't work last night.)

The second launch seemed to be perfect so I moved the media folder back and started the third launch, during which everything went perfect. So I closed the window and tried to save the new log which include the three launches, when the DebugView showed 'No Responded' ! ! ! It worked well when saving 75000+ lines and crashed saving 30000+ lines ? ? ?

Anyway, the digikam worked well at least...