[dolphin] [Bug 505152] New: Dolphin crashed after opening a new tab

[Olaf M.]

https://bugs.kde.org/show_bug.cgi?id=505152

            Bug ID: 505152
           Summary: Dolphin crashed after opening a new tab
    Classification: Applications
           Product: dolphin
      Version First 25.04.1
       Reported In:
          Platform: KDE Linux
                OS: Linux
            Status: REPORTED
          Keywords: drkonqi
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: om at om-home.de
                CC: kfm-devel at kde.org
  Target Milestone: ---

Application: dolphin (25.04.1)

ApplicationNotResponding [ANR]: false
Qt Version: 6.9.0
Frameworks Version: 6.14.0
Operating System: Linux 6.11.0-26-generic x86_64
Windowing System: Wayland
Distribution: KDE neon 6.3
DrKonqi: 6.3.5 [CoredumpBackend]

-- Information about the crash:
Dear Dev.-team, I observed a Dolphon crah an have the follwoing add-info:
- There were severeal Dolphin windows opened, in total 7, a view with more than
one tab.
- In one window I executed a search and got the results. 
- On two of the search results (there were maybe 30 hits) I opened the
corresponding folder tabs using right mouse klick on a file.
- I retrieved data in those additional tabs and then I decided to manually open
one further tab using the button I have added to my default doplhin window
appearance.
- Immediately after I pressed the button to open this new tab then dolphin
crashed.
- I tried 3x to reproduce the case but w/o success.
- All the other remaining 6 open dolphin windows were not affected.
- I use KDE neon with KDE-Plasma-Version 6.3.5, KDE-Framworks 6.14.0,
Qt-Version 6.9.0, Kernel 6.11.0-26-generic (64bit), lenovo laptop ThinkPad X1
Yoga Gen 7, 16GB RAM, with 30% memory usage, 16 × 12th Gen Intel® Core™
i5-1240P CPU, no add GPU.
- The following apps were active at that moment: Oracle VirtualBox, Firefox,
Discover, Kate and Evolution.
Hope that helps you. Kind regards, Olaf M.

The crash does not seem to be reproducible.

-- Backtrace (Reduced):
#6  __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>)
at ./nptl/pthread_kill.c:44
#7  __pthread_kill_internal (signo=6, threadid=<optimized out>) at
./nptl/pthread_kill.c:78
#8  __GI___pthread_kill (threadid=<optimized out>, signo=signo at entry=6) at
./nptl/pthread_kill.c:89
#9  0x0000740773a4527e in __GI_raise (sig=sig at entry=6) at
../sysdeps/posix/raise.c:26
#10 0x0000740773a288ff in __GI_abort () at ./stdlib/abort.c:79


Reported using DrKonqi

-- 
You are receiving this mail because:
You are on the CC list for the bug.