https://bugs.kde.org/show_bug.cgi?id=474132
Albert Astals Cid changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/
https://bugs.kde.org/show_bug.cgi?id=474132
Albert Astals Cid changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=474132
Bug Janitor Service changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=474132
--- Comment #3 from Vit Pelcak ---
Created attachment 161410
--> https://bugs.kde.org/attachment.cgi?id=161410=edit
valgrind log
I tried to run valgrind --error-limit=no --log-file="lokalize.log" lokalize
but ended up with computer frozen. I let it
https://bugs.kde.org/show_bug.cgi?id=474132
--- Comment #2 from Vit Pelcak ---
==12805== Memcheck, a memory error detector
==12805== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==12805== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==12805== Command:
https://bugs.kde.org/show_bug.cgi?id=474132
--- Comment #1 from Albert Astals Cid ---
Can you run
valgrind lokalize
and attach the valgrind trace when doing the thing that makes it crash?
--
You are receiving this mail because:
You are watching all bug changes.