Bug 509411 - Filelight gets stuck at 100% single core CPU usage with corrupted files
Summary: Filelight gets stuck at 100% single core CPU usage with corrupted files
Status: REPORTED
Alias: None
Product: filelight
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-12 09:32 UTC by ungive
Modified: 2025-09-15 14:15 UTC (History)
2 users (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 ungive 2025-09-12 09:32:13 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY


STEPS TO REPRODUCE
1. Open FileLight
2. Select C:\Users\USER\AppData\Local\Temp
3. If you have this directory it might get stuck: C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\
3. Observe it may get stuck and using one CPU core at 100%

OBSERVED RESULT
It gets stuck. You can still open e.g. the help menu but clicking stop hangs the app and you have to force close it.

EXPECTED RESULT
It doesn't get stuck. The directory seems to be corrupt and that makes it get stuck. It would make sense for the app to skip corrupted directories on Windows.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
PS C:\Users\USER> cd C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services
PS C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services> Get-Item -Path .\Microsoft.VisualStudio.Setup.Service\ | Format-List *


PSPath            : Microsoft.PowerShell.Core\FileSystem::C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\
                    ServiceHub\Services\Microsoft.VisualStudio.Setup.Service\
PSParentPath      : Microsoft.PowerShell.Core\FileSystem::C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\
                    ServiceHub\Services
PSChildName       : Microsoft.VisualStudio.Setup.Service
PSDrive           : C
PSProvider        : Microsoft.PowerShell.Core\FileSystem
PSIsContainer     : True
Mode              : d-----
BaseName          : Microsoft.VisualStudio.Setup.Service
Target            : {C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services\Microsoft.VisualS
                    tudio.Setup.Service}
LinkType          :
Name              : Microsoft.VisualStudio.Setup.Service
FullName          : C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services\Microsoft.VisualSt
                    udio.Setup.Service\
Parent            : Services
Exists            : True
Root              : C:\
Extension         :
CreationTime      : 03.06.2025 23:17:09
CreationTimeUtc   : 03.06.2025 21:17:09
LastAccessTime    : 12.09.2025 11:25:17
LastAccessTimeUtc : 12.09.2025 09:25:17
LastWriteTime     : 11.06.2025 00:39:25
LastWriteTimeUtc  : 10.06.2025 22:39:25
Attributes        : Directory



PS C:\Users\USER\AppData\Local\Temp\uisir431.qvf\resources\app\ServiceHub\Services> dir .\Microsoft.VisualStudio.Setup.Service
dir : Die Datei oder das Verzeichnis ist beschädigt und nicht lesbar.
In Zeile:1 Zeichen:1
+ dir .\Microsoft.VisualStudio.Setup.Service
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ReadError: (C:\Users\USER\...o.Setup.Service:String) [Get-ChildItem], IOException
    + FullyQualifiedErrorId : DirIOError,Microsoft.PowerShell.Commands.GetChildItemCommand
Comment 1 Harald Sitter 2025-09-15 14:15:49 UTC
I don't suppose you could debug this with visual studio and get me a stacktrace?

Getting stuck isn't exactly ideal, but TBH the options are somewhat limited when the filesystem itself is broken.