#16903 closed bug (invalid)
digiKam & showPhoto Crash (Beta 2)
| Reported by: | ArDrakho | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | - General | Version: | R1/beta2 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Every attempt to start up digiKam or showPhoto either freezes up the system (forcing a reboot) or aborts with an error windows (see attached PNG file).
I saved two 'Save report' files--see attached files.
Attachments (4)
Change History (18)
by , 4 years ago
| Attachment: | digiKam-error-2021-04-09_21-53.png added |
|---|
by , 4 years ago
| Attachment: | digiKam-2336-debug-10-04-2021-02-58-43.report added |
|---|
digiKam debug file
by , 4 years ago
| Attachment: | showFoto-2365-debug-10-04-2021-02-59-39.report added |
|---|
showPhoto debug file
comment:1 by , 4 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Bugs in ports from haikuports should be reported at their issue tracker. The attached reports are missing any useful information. Maybe you need to wait longer for the writing of the debug reports to be finished?
comment:2 by , 4 years ago
Bugs in ports from haikuports should be reported at their issue tracker.
No. 3-rd party software should be not able to freeze system.
comment:3 by , 4 years ago
Just installed digikam-7.2.0-1-x86_64.hpkg. Both apps work for me on 64bit hrev55029. No freeze, no crash.
I don't think this ticket provides any info to help track ArDrakho's issue. Feel free to re-open, if you think otherwise, or more informtion is provided
comment:4 by , 4 years ago
I recreated the 'Save report's for each and it recreated the reports as previously submitted. The report generation was not interrupted by me. So I do not have a clue how to make them with more details. Should I select 'Write core file' option instead?
I doubled checked my version for digiKam, which is also 7.2.0-1--so I cannot attest if it ever worked before me installing last week and failed from the get go.
Thanks about letting know. I will create a bug report at the other site.
comment:5 by , 4 years ago
What kind of freeze is happening? Does cursor move? Is it possible to move windows?
comment:6 by , 4 years ago
At this time it has not caused the system freezing scenario--which is good thing at this time.
The last three times it presented the error window as cited in the PNG file, where I select the 'save report' option and exits cleanly.
However previously starting digiKam, it would cause the system freezes, where the CPU #1 or #2 pegs max and the error window is not presented. The mouse moves for short time and then nothing...the screen freezes. Forcing me to reboot. But luckily, I have not had to do this the last three times when I initiated digiKam or showPhoto.
So at this time--it is a crap-shoot it causes a system freeze or I get the error window.
comment:7 by , 4 years ago
Also, to note--my Otter-Browser has started to do the same thing at the same time when I installed digiKam. I know Otter-Browser worked before since it was my primary means to browse where Web+ was my backup to browse the Internet. It may or may not be related to the install of digiKam. And it may coincidental. I will attached its 'save report' for you to glean.
by , 4 years ago
| Attachment: | Otter-Browser-4967-debug-11-04-2021-06-07-50.report added |
|---|
comment:8 by , 4 years ago
Otter crashed in adblock filter. It could be that your Otter profile (or BFS) is corrupted. digiKam requires quite a lot of memory to start. Haiku tends to freeze in out of memory situations.
comment:9 by , 4 years ago
Haiku tends to freeze in out of memory situations.
That makes sense. "low resource manager" kernel thread will take 100% CPU and freeze system in low memory conditions. I can't find existing ticket about that, similar behavior is observed here.
comment:10 by , 4 years ago
Hmm...that would explain the spike of one of CPUs spiking to MAX (100%).
With 4Gb of RAM, the memory never went RED or maxed out that I could tell.
That may explain why the debug text files does not get completely written because the CPU freezes the system before it can dump the rest of the data to text.
But this past week, it has frozen my system again forcing me to perform a "hard" reboot.
How can I load the previous version of digiKam since the current version is causing me headaches. The package manager does not have a rollback feature or options to load previous versions at this time. (I imagine that is in the works soon.)
I would like to see if the older version of digiKam will cause the same issue.
comment:12 by , 4 years ago
Diver stated: "Otter crashed in adblock filter. It could be that your Otter profile (or BFS) is corrupted. digiKam requires quite a lot of memory to start. Haiku tends to freeze in out of memory situations."
So I cleaned out the settings for Otter and amended the 'otter.conf' by removing all entries as follows:
[ContentBlocking] Profiles=
Now Otter is back!! Good call Diver.
digiKam still causing crashes...
comment:13 by , 4 years ago
With 4Gb of RAM, the memory never went RED or maxed out that I could tell.
Used memory calculation may be wrong (https://discuss.haiku-os.org/t/app-server-font-cache-is-causing-high-cpu-load-in-low-resource-manager-thread-and-cause-mysterious-resource-exhaustment/10147/6).
comment:14 by , 4 years ago
I will wipe this system and start with a clean install and see if it duplicates. Just sucks that I have reload everything and set up the menus and databases again.
Thanks for the information.
digiKam screenshot