C#•16mo ago

FileSystemWatcher causes user limit exceptions on Kubuntu Linux

Using the following code results in the exception

The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

public static void Init(string ProjectPath, List <ProjectFile> ProjectFileList, List <ProjectDirectory> ProjectDirList, List <Icon> IconList)
{
    ProjectFiles = ProjectFileList;
    ProjectDirs = ProjectDirList;
    Icons = IconList;

    FSWatcher.BeginInit();
    FindItemsInProjectDirectory(null, null);

    FSWatcher.IncludeSubdirectories = true;
    FSWatcher.EnableRaisingEvents = true;
    FSWatcher.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.FileName | NotifyFilters.DirectoryName;
    FSWatcher.Changed += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Created += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Deleted += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Renamed += new RenamedEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Path = ProjectPath;
    FSWatcher.EndInit();
}

public static void Init(string ProjectPath, List <ProjectFile> ProjectFileList, List <ProjectDirectory> ProjectDirList, List <Icon> IconList)
{
    ProjectFiles = ProjectFileList;
    ProjectDirs = ProjectDirList;
    Icons = IconList;

    FSWatcher.BeginInit();
    FindItemsInProjectDirectory(null, null);

    FSWatcher.IncludeSubdirectories = true;
    FSWatcher.EnableRaisingEvents = true;
    FSWatcher.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.FileName | NotifyFilters.DirectoryName;
    FSWatcher.Changed += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Created += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Deleted += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Renamed += new RenamedEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Path = ProjectPath;
    FSWatcher.EndInit();
}

public static void Init(string ProjectPath, List <ProjectFile> ProjectFileList, List <ProjectDirectory> ProjectDirList, List <Icon> IconList)
{
    ProjectFiles = ProjectFileList;
    ProjectDirs = ProjectDirList;
    Icons = IconList;

    FSWatcher.BeginInit();
    FindItemsInProjectDirectory(null, null);

    FSWatcher.IncludeSubdirectories = true;
    FSWatcher.EnableRaisingEvents = true;
    FSWatcher.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.FileName | NotifyFilters.DirectoryName;
    FSWatcher.Changed += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Created += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Deleted += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Renamed += new RenamedEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Path = ProjectPath;
    FSWatcher.EndInit();
}

public static void Init(string ProjectPath, List <ProjectFile> ProjectFileList, List <ProjectDirectory> ProjectDirList, List <Icon> IconList)
{
    ProjectFiles = ProjectFileList;
    ProjectDirs = ProjectDirList;
    Icons = IconList;

    FSWatcher.BeginInit();
    FindItemsInProjectDirectory(null, null);

    FSWatcher.IncludeSubdirectories = true;
    FSWatcher.EnableRaisingEvents = true;
    FSWatcher.NotifyFilter = NotifyFilters.LastWrite | NotifyFilters.FileName | NotifyFilters.DirectoryName;
    FSWatcher.Changed += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Created += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Deleted += new FileSystemEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Renamed += new RenamedEventHandler(FindItemsInProjectDirectory);
    FSWatcher.Path = ProjectPath;
    FSWatcher.EndInit();
}

FindItemsInProjectDirectory

FindItemsInProjectDirectory

FindItemsInProjectDirectory

FindItemsInProjectDirectory does not do anything with the fs watcher object.

MSCPOP•9/12/24, 10:10 PM

I read that I could modify this limit, but that's just a workaround instead of a real solution. It also doesn't work well for portable applications.

Petris•9/13/24, 12:27 AM

it's either that or having a background thread that call Directory.EnumerateFiles in a loop

MSCPOP•9/13/24, 2:23 AM

But doesn't it already run on a separate thread?

deprecatio•9/13/24, 5:52 AM

what gave you this impression?

MSCPOP•9/13/24, 7:10 AM

The application runs without any delays or freezing, even with a large amount of files. That's flawed though now that I think about it

wasabi•9/13/24, 2:04 PM

The issue is INcludeSubdiretories, probably.

wasabi•9/13/24, 2:05 PM

It's been awhile since I looked, but from what I remember it opens a new inotify channel for each watched directory.

wasabi•9/13/24, 2:05 PM

And Linux limits those.

MSCPOP•9/13/24, 7:35 PM

Ah. There really aren't thatany subdirectories though, is there a way to work around this?

wasabi•9/14/24, 1:46 PM

Nope. Gotta increase the per-user limit.

wasabi•9/14/24, 1:50 PM

Actually, looking at your error, it's not erroring because of max watches, but because of max instances. Might be the case you're creating too many FSWs

MSCPOP•9/14/24, 5:39 PM

I should only be creating one, I'll add a console.writeline in the fs watcher init function

MSCPOP•9/14/24, 9:39 PM

Yeah it's only creating one instance as far as I'm aware

Petris•9/14/24, 9:49 PM

for context, the limit that's hit is usually the global one

Petris•9/14/24, 9:49 PM

not the per app one

Petris•9/14/24, 9:50 PM

also why do you have it at 128

Petris•9/14/24, 9:50 PM

the default seems to be 8192

wasabi•9/14/24, 10:06 PM

watch != instance

PPetris also why do you have it at 128

MSCPOP•9/14/24, 11:52 PM

That seems to be Kubuntu's default

MSCPOP•9/14/24, 11:52 PM

Nvm, just read the above comment

PPetris for context, the limit that's hit is usually the global one

MSCPOP•9/14/24, 11:53 PM

Ah. I'm not sure what else could be causing the limit to be hit though, as there are only about 3 applications running at a time

wasabi•9/15/24, 12:13 AM

You can probably check something in procfs to see how many are used

MSCPOP•9/15/24, 2:14 AM

I could add a check before the few gets set up

wasabi•9/15/24, 5:33 AM

or you could just go look. with your eyes

MSCPOP•9/15/24, 5:33 AM

I meant as a warning for users.

MSCPOP•9/15/24, 5:34 AM

Y'know, so they don't just have to deal with some random error that might look like gibberish to them

MSCPOP•9/15/24, 5:34 AM

We don't want Microsoft error messages

FileSystemWatcher causes user limit exceptions on Kubuntu Linux

Similar Threads

Similar Threads

Similar Threads