[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-06 Thread Sergey Zh
$ cat ~/.config/user-dirs.dirs # This file is written by xdg-user-dirs-update # If you want to change or add directories, just edit the line you're # interested in. All local changes will be retained on the next run # Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped # homedir-relati

[Bug 2092535] [NEW] ding.js takes 100% CPU time!

2024-12-26 Thread Sergey Zh
Public bug reported: The process gjs /usr/share/gnome-shell/extensions/d...@rastersoft.com/app/ding.js -E -P /usr/share/gnome-shell/extensions/d...@rastersoft.com/app takes 100% of CPU time after fresh Ubuntu 24.04.1 installation! CPU is heated and cooler makes noise just because of this one a

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-08 Thread Sergey Zh
update: on the next day the bug re-appeared again. I ran: $ gnome-extensions disable d...@rastersoft.com (process stopped) $ gnome-extensions enable d...@rastersoft.com and it still uses 100% cpu. May be I could attach debug messages here ? There are console.log() strings in application, where are

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-14 Thread Sergey Zh
It's a pity, that current patch mixes up 2 different issues, number of files and bug with number of opened directories. It's would be simple to create 2 variables for 2 different logically unconnected limits, like this: this._maxNumberOfOpenedDirs = 100; this._maxNumberOfTemplat

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-02 Thread Sergey Zh
I also have this bug and reported it here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons-ng/+bug/2092535 I have approximately 100% CPU usage by the ding.js process. I removed all files from my ~/Desktop folder and still had this bug. -- You received this bug not

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-10 Thread Sergey Zh
It was not a soft link, but this time I created soft link for testing )) A cycling soft link does NOT create a bug, as it stopped following symlink to directory at about depth=80 (with 40 symblinks), with the longest path looked like this ~/Templates/a/l/a/l/a/l/a/l/a/l/a/l/a/l/a/l/a/l/a/l/a/l/a/

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-10 Thread Sergey Zh
As for your patch, the first check on the number of calls to _processDirectory() fixes the issue, but the second check (after fileList.push) is NOT needed. As the files are not opened during directory scan, there is no need to limit its number, only the number of scanned (opened) directories. To

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-10 Thread Sergey Zh
The issue here is that while scanning directories the app keeps open directory handles. When this number is going close to 1024 kernel limit on open files/dirs, the app gets the error below and restarts. Then again scans, gets error, restarts. Thus taking 100% CPU forever. (in a few minutes after

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-07 Thread Sergey Zh
I just identified the package where the ding.js belong to, and removed it with $ apt remove gnome-shell-extension-desktop-icons-ng that solved the problem for me. I decided to check with your "disable", and installed the package again. Then I logout/logged back to activate it. Now ding.js does NO

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-09 Thread Sergey Zh
After more investigation with added console.log() I found, that in the file d...@rastersoft.com/app/templatesScriptsManager.js the function _processDirectory() is called 300 times a second. This function can call itself, so it is an infinite loop taking all of CPU. More details (TSM=TemplatesScr

[Bug 2081198] Re: ding.js is consuming too much CPU

2025-01-09 Thread Sergey Zh
$ journalctl -f /usr/bin/gnome-shell $ gnome-extensions enable d...@rastersoft.com got this: Launching DING process DING: Detected async api for thumbnails DING: (gjs:75251): Gjs-WARNING **: 14:43:11.722: GLib.unix_signal_add has been moved to a separate platform-specific library. Please upda