duanyao
deepin
2017-11-12 08:18 似乎开着新立得的时候,深度系统监视器更容易崩溃,不知是不是错觉。
Reply Like 0 View the author
https://bbs.deepin.org/post/148049
我想我找到原因了:
https://github.com/manateelazycat/deepin-system-monitor/issues/11
https://bbs.deepin.org/post/148049
看着是 nethogs 这个库的问题,请给一下你的重现方式。
我看看能否在监视器的代码中进行一次保护,再传递 ...
Popular Ranking
ChangePopular Events
More
系统版本:15.5beta 64位
深度系统监视器版本:1.3.6-1
硬件:联想 V470
操作步骤:启动深度系统监视器,切换视图,搜索进程(不知道哪个有关系)。一般不会立即崩溃,放着不管几分钟一般会崩溃。
启动后不做任何操作,过一会儿也可能崩溃。
这个问题并不是升级到 15.5beta 后才出现的,以前也有,但好像没有现在频繁。
我安装了调试符号,用gdb看了一下,崩溃时的调用栈如下:
(gdb) attach 27117
Attaching to process 27117
[New LWP 27118]
[New LWP 27119]
[New LWP 27120]
[New LWP 27121]
[New LWP 27123]
[New LWP 27124]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007fa7dc0154b3 in QString::truncate(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) c
Continuing.
Thread 7 "deepin-system-m" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fa7b8d28700 (LWP 27124)]
0x00005584b5c002b8 in getcmdline[abi:cxx11](int) ()
(gdb) bt
#0 0x00005584b5c002b8 in getcmdline[abi:cxx11](int) ()
#1 0x00005584b5c004c7 in setnode(unsigned long, int) ()
#2 0x20205584b5c00831 in ()
#3 0x5b3a74656b636f73 in ()
#4 0x20205d3934363132 in ()
#5 0x2020202020202024 in ()
#6 0x20207fa7daec6ab4 in ()
#7 0x2020202020202020 in ()
#8 0x20207fa7a807f4d0 in ()
#9 0x20207fa7b8d27820 in ()
#10 0x20207fa7b8d277c0 in ()
#11 0x20207fa7b8d27740 in ()
#12 0x20205584b5c00773 in ()
#13 0x20207fa7a8071d93 in ()
#14 0x2020202020202010 in ()
#15 0x37322f636f72702f in ()
#16 0x202064662f303639 in ()
#17 0x2020202020202020 in ()
#18 0x20207fa7daec6f37 in ()
#19 0x37322f636f72702f in ()
#20 0x322f64662f303639 in ()
#21 0x20207fa7a8202020 in ()
#22 0xffffffffffffff60 in ()
#23 0x2020202020202002 in ()
#24 0x20205584b5e72835 in ()
#25 0x2020202020202024 in ()
#26 0x20207fa7a806fa70 in ()
#27 0x20207fa7b8d27870 in ()
#28 0x20207fa7b8d27860 in ()