Bug 507327 - Dolphin leaving orphaned ripgrep searches running
Summary: Dolphin leaving orphaned ripgrep searches running
Status: REPORTED
Alias: None
Product: dolphin
Classification: Applications
Component: search (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-21 19:09 UTC by tagwerk19
Modified: 2025-08-17 07:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tagwerk19 2025-07-21 19:09:54 UTC
SUMMARY

    When Dolphin is doing simple searches and using ripgrep, it can leave leave orphaned
    searches running in the background.

    This is most obvious when searching "Everywhere" (in the new search interface), where
    the search is looking at the whole disk.

STEPS TO REPRODUCE:
    
1...
    Install ripgrep and make sure Dolphin is using it.

2...
    Run your favourite process monitor: I open a command window, run htop and make
    sure the window is wide enough to see the details of the processes.

3...
    Open Dolphin, type <ctrl>F to get the search box, make sure you are using "Simple
    Search" in Filter and "File Contents", select "Everywhere" and...

4...
    Slowly type a search expression, do this with pauses, times to think, mistpyings and
    corrections. You'll see the "Searching..." animation in the bottom right corner of
    Dolphin.

5...
    Watch htop...

OBSERVED RESULT:

    You will see more than one copy of "rg" running (you see two copies running for each
    search, that's expected), but as you pause, mistpye and correct you will see more
    copies of "rg" being started with the new search expressions. Sometimes you will see
    a running "rg" disappear and be replaced by a new copy (with the new search
    expression), however in a large number of times, the old copy will be orphaned and
    continue running.

    You can get to the state where there are more searches running than cores and
    searching take the complete CPU. Searches slow considerably...

    You can close Dolphin and the processes stay running.

EXPECTED RESULT:

    Dolphin should track which processes it is running and kill processes that it no
    longer needs.

SOFTWARE/OS VERSIONS:

    KDE Neon Unstable
    Plasma: 6.4.80
    Frameworks: 6.17.0
    Qt: 6.9.1
    Dolphin: 25.11.70

ADDITIONAL INFORMATION:

    There doesn't seem to be a problem on a system without ripgrep.

    The problem is less obvious when searching "From Here" as opposed to from
    "Everywhere", maybe because the ripgreps complete more quickly.

    You can see in htop that the "rg" processes are running with normal priority.
Comment 1 tagwerk19 2025-08-17 07:54:30 UTC
(In reply to tagwerk19 from comment #0)
> SOFTWARE/OS VERSIONS:
> 
>     KDE Neon Unstable
>     Plasma: 6.4.80
>     Frameworks: 6.17.0
>     Qt: 6.9.1
>     Dolphin: 25.11.70
Checked now that Dolphin 25.08 has reached Neon User, it's still there...
     KDE Neon User
     Plasma: 6.4.4
     Frameworks: 6.17.0
     Qt: 6.9.1
     Dolphin: 25.08