Description of problem: Closing the wireshark after long period it was opened, caused the error. It seems wireshark also cause the CPU usage increase even it was not used only sits idle in the taskbar.. Version-Release number of selected component: 1:wireshark-3.2.0-1.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/bin/wireshark /home/izhamsaad/Downloads/cbs_trace_ucb2_201912301100.pcap crash_function: frame_data_sequence_find executable: /usr/bin/wireshark journald_cursor: s=03dae69986bd40ec91ef3a8c3e17ff74;i=9c9344;b=56c23f63669f4a75ace6b37fbb331f38;m=1190dca2a2;t=59ae90b9a134c;x=8b23943c1a377e11 kernel: 5.4.5-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 frame_data_sequence_find at /usr/src/debug/wireshark-3.2.0-1.fc31.x86_64/epan/frame_data_sequence.c:192 #1 find_packet at /usr/src/debug/wireshark-3.2.0-1.fc31.x86_64/file.c:3677 #2 cf_find_packet_protocol_tree at /usr/src/debug/wireshark-3.2.0-1.fc31.x86_64/file.c:3028 #3 SearchFrame::on_findButton_clicked() at /usr/src/debug/wireshark-3.2.0-1.fc31.x86_64/ui/qt/search_frame.cpp:473 #4 SearchFrame::qt_metacall(QMetaObject::Call, int, void**) at /usr/src/debug/wireshark-3.2.0-1.fc31.x86_64/ui/qt/qtui_autogen/EWIEGA46WW/moc_search_frame.cpp:152 #5 QMetaObject::activate(QObject*, int, int, void**) at kernel/qobject.cpp:3825 #6 QAbstractButton::clicked(bool) at .moc/moc_qabstractbutton.cpp:313 #7 QAbstractButtonPrivate::emitClicked() at widgets/qabstractbutton.cpp:414 #8 QAbstractButtonPrivate::click() at widgets/qabstractbutton.cpp:407 #9 QAbstractButton::mouseReleaseEvent(QMouseEvent*) at widgets/qabstractbutton.cpp:1011 Potential duplicate: bug 1662281
Created attachment 1648562 [details] File: backtrace
Created attachment 1648563 [details] File: core_backtrace
Created attachment 1648564 [details] File: cpuinfo
Created attachment 1648565 [details] File: dso_list
Created attachment 1648566 [details] File: environ
Created attachment 1648567 [details] File: exploitable
Created attachment 1648568 [details] File: limits
Created attachment 1648569 [details] File: maps
Created attachment 1648570 [details] File: mountinfo
Created attachment 1648571 [details] File: open_fds
Created attachment 1648572 [details] File: proc_pid_status
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.