[Bug]: Extreme performance issues upon file change with File Explorer

[Sutaai]

🐛 Describe the bug

This extension will, upon modification in the File Explorer (Mostly, deleting, creating, renaming), make Visual Studio Code experience a huge lag, and will be unresponsive to open other files.

👣 Steps to reproduce

1. Install and use the icon pack
2. Open a repository with a lot of files in one folder, 10 should be just enough.
3. Rename a file or create a new file

✨ Expected behavior

As quick as usual

📎 Files & Screenshots

No response

📦 Extension version

4.0.2

💻 VS Code version

1.99.3

🖥️ Operating System

Windows

ℹ️ Additional context

• Confirmed caused by extension, extension bisect used. No A/B testing report availably as VSC didn't wish I could open it.

[SuperAnt220]

🤔 Hmm can't reproduce. I am on windows, VS code version 1.94.2, opened a folder with 1.21.4 vanilla dp and rp, which contains 16k files, and I can create and modify files with no lag.

Our dynamic icons system updates every time the user modifies something in the file explorer. Can you try disabling all the dynamic icons features in the extension settings and see if it removes the lag? open command pallete → Datapack Icons: Open Extension Settings → untick Namespace Icons, Subfolder Icons, Load Tick Auto Change, pack mcmeta check, and disable Christmas Icons.

Also try to reinstall the extension.

[Sutaai]

Here is something interesting;

And I promise this is not a potato PC.

I had an absolute difficult time to even save the settings because VSC wasn't able to save settings.json.
Which doesn't happen when this extension is uninstalled.

This is still happening despite the following settings:

{
  "mc-dp-icons.enableNamespaceIcons": false,
  "mc-dp-icons.enableChristmasIcons": "Disable",
  "mc-dp-icons.enableLoadTickAutoChange": false
}

Additionally, I had slow down in the editor too; but I had auto save enabled personally, yet, this is still likely because of the extension.

[SuperAnt220]

Unfortunately I can't think of a way of fixing this at the moment, I just can't reproduce this. Maybe I can make a no-code version of the extension for you to at least make the main part of the extension usable?

[Sutaai]

Sure, I'd honestly absolutely prefer over the code version. But that's your call if you want to maintain yet another package.