Version-Release number of selected component: heaptrack-1.2.0-10.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-gnome-jetbrains\x2dclion-8672.scope cmdline: /usr/lib64/heaptrack/libexec/heaptrack_interpret crash_function: (anonymous namespace)::demangle executable: /usr/lib64/heaptrack/libexec/heaptrack_interpret journald_cursor: s=197bfe23d0854382adeeffe1c8dfff1b;i=8f94e9;b=f8c50fd0c182413fb795ad215c964583;m=17bad8f3d5;t=5efe0c652c904;x=a56535a7cebd264b kernel: 6.1.0-0.rc8.20221209git0d1409e4ff08.62.vanilla.1.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 (anonymous namespace)::demangle at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:57 #1 operator() at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:162 #2 _FUN at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:164 #3 backtrace_syminfo at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/3rdparty/libbacktrace/fileline.c:189 #5 (anonymous namespace)::Module::resolveAddress at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:158 #6 (anonymous namespace)::AccumulatedTraceData::resolve at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:253 #7 (anonymous namespace)::AccumulatedTraceData::addIp at /usr/src/debug/heaptrack-1.2.0-10.fc37.x86_64/src/interpret/heaptrack_interpret.cpp:312
Created attachment 1933446 [details] File: backtrace
Created attachment 1933447 [details] File: core_backtrace
Created attachment 1933448 [details] File: cpuinfo
Created attachment 1933449 [details] File: dso_list
Created attachment 1933450 [details] File: environ
Created attachment 1933451 [details] File: exploitable
Created attachment 1933452 [details] File: limits
Created attachment 1933453 [details] File: maps
Created attachment 1933454 [details] File: mountinfo
Created attachment 1933455 [details] File: open_fds
Created attachment 1933456 [details] File: proc_pid_status
FEDORA-2023-3d2dbd4a42 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3d2dbd4a42
FEDORA-2023-c3d1890550 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c3d1890550
FEDORA-2023-d60ffe2322 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d60ffe2322
FEDORA-2023-d60ffe2322 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-d60ffe2322` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-d60ffe2322 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-c3d1890550 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c3d1890550 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3d2dbd4a42 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-3d2dbd4a42` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3d2dbd4a42 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-3d2dbd4a42 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-d60ffe2322 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-c3d1890550 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.