https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #18 from Christoph Feck ---
There is no need to add more backtraces. If your investigation resulted in a
possible patch, please add it to
https://phabricator.kde.org/differential/diff/create/
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #17 from Matt Fagnani ---
Created attachment 117348
--> https://bugs.kde.org/attachment.cgi?id=117348&action=edit
New crash information added by DrKonqi
ksysguard (5.14.4) using Qt 5.11.3
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #16 from Matt Fagnani ---
Created attachment 116888
--> https://bugs.kde.org/attachment.cgi?id=116888&action=edit
New crash information added by DrKonqi
ksysguard (5.14.4) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #15 from Matt Fagnani ---
AddressSanitizer caught a use-after-free error in TopLevel::answerReceived at
ksysguard.cpp:450 while ksysguard was closing on the 24th time I ran it. The
second function from the top was KSGRD::SensorAgent::process
https://bugs.kde.org/show_bug.cgi?id=400499
Matt Fagnani changed:
What|Removed |Added
Version|5.13.5 |5.14.3
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #14 from Matt Fagnani ---
Created attachment 116434
--> https://bugs.kde.org/attachment.cgi?id=116434&action=edit
AddressSanitizer output from running and closing ksysguard
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #13 from Matt Fagnani ---
Created attachment 116433
--> https://bugs.kde.org/attachment.cgi?id=116433&action=edit
valgrind --leak-check=yes --show-leak-kinds=definite
--log-file=valgrind-ksysguard-5.txt ksysguard output
--
You are receiv
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #12 from Matt Fagnani ---
All of the valgrind runs' first invalid reads were in
KSGRD::SensorAgent::processAnswer at SensorAgent.cpp:186 as in the following.
All of the other invalid reads or writes have
KSGRD::SensorAgent::processAnswer(cha
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #11 from Matt Fagnani ---
Memory leaks were detected with 8-9 definitely lost blocks, 48 indirectly lost
blocks, and 19 possibly lost blocks per run. I'm unsure if the segmentation
faults are related to those memory leaks. One line I wrote s
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #10 from Matt Fagnani ---
Created attachment 116396
--> https://bugs.kde.org/attachment.cgi?id=116396&action=edit
valgrind --read-var-info=yes --log-file=valgrind-ksysguard-3.txt ksysguard
output
--
You are receiving this mail because:
Y
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #9 from Matt Fagnani ---
Created attachment 116395
--> https://bugs.kde.org/attachment.cgi?id=116395&action=edit
valgrind --log-file=valgrind-ksysguard-2.txt ksysguard output
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #8 from Matt Fagnani ---
Created attachment 116394
--> https://bugs.kde.org/attachment.cgi?id=116394&action=edit
valgrind --log-file=valgrind-ksysguard-1.txt ksysguard output
--
You are receiving this mail because:
You are watching all b
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #7 from Matt Fagnani ---
I ran valgrind on ksysguard three times. valgrind showed invalid reads and
writes each time after I closed ksysguard. 97 invalid reads and 23 invalid
writes were listed on both of the first and third runs. 89 invali
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #6 from Matt Fagnani ---
Crashes involving segmentation faults in operator== (s1=..., s2=...) at
tools/qstring.cpp:3153 were reported for:
kpat at https://bugs.kde.org/show_bug.cgi?id=363726#c5
kdeconnectd at https://bugs.kde.org/show_bug.c
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #5 from Matt Fagnani ---
Those ksysguard crashes with segmentation faults at operator==(QString const&,
QString const&) (s1=..., s2=...) at tools/qstring.cpp:3153 seem to involve the
line if (s1.d->size != s2.d->size) in the function
/*!
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #4 from Matt Fagnani ---
Created attachment 116390
--> https://bugs.kde.org/attachment.cgi?id=116390&action=edit
New crash information added by DrKonqi
ksysguard (5.14.3) using Qt 5.11.1
- What I was doing when the application crashed:
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #3 from Matt Fagnani ---
Created attachment 116263
--> https://bugs.kde.org/attachment.cgi?id=116263&action=edit
New crash information added by DrKonqi
ksysguard (5.14.3) using Qt 5.11.1
- What I was doing when the application crashed:
I
https://bugs.kde.org/show_bug.cgi?id=400499
Christoph Feck changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=400499
--- Comment #1 from Matt Fagnani ---
Created attachment 116189
--> https://bugs.kde.org/attachment.cgi?id=116189&action=edit
New crash information added by DrKonqi
ksysguard (5.13.5) using Qt 5.11.1
- What I was doing when the application crashed:
I
https://bugs.kde.org/show_bug.cgi?id=400499
Matt Fagnani changed:
What|Removed |Added
CC||matthew.fagn...@utoronto.ca
--
You are receivin
20 matches
Mail list logo
