This project has moved and is read-only. For the latest updates, please go here.
1
Vote

Thread spam

description

I'm several having issues with both the old and new versions.

How I run WFN: Disable both incoming and outgoing, then notify for both.
Windows 7, SP1
Tested with versions 1.7.0 and 2.0 Alpha 11

issue 1: When I try to create a new rule (allow outbound), about 30 threads spin up. In the new version, they also create WerFaults for each one, ending in "The corresponding rule has not been created"

The logfile says:
2017/02/19 13:09:31 - SYSTEM [False] - [WARNING] Unable to retrieve the target process SessionID. Process may have already exited.

This could be something to do with Notifier.exe running as "below average" priviledges by default (something I noticed, but I don't know why)

issue 2: I'm getting duplicate rules for Discord (chat app), and League of Legends in particular. These programs operate on a "new version, new folder, every 2 sort of weeks" system. I'm not getting duplicates in the sense that I have to allow each version (that's acceptable, but would actually be nice to add functionality where I didn't have to do this). I'm getting duplicates in the sense that: for each version, I'm getting multiple TCP and UDP rules (ignoring ports, and the rest of it).

It was mostly fine until recently, and I was on 1.7, so I'm thinking maybe something in Windows changed?

If this is a bad ticket, please get me to change it.

I figure 1 part might be able to inform the other for now

comments

DanielPharos wrote Feb 19 at 4:13 PM

Issue 2: I'll look into it, but it might be related to known issues that will be fixed in a future version, so let's focus on issue 1 for now.

It's probably spinning up so many threads because WerFault tries to connect to the outside world. So the underlying problem is the crash that happens when you try to create a rule. Is there any more info in the Windows Event Viewer about this crash? And what version of the .NET framework do you have installed? (WFN needs .NET 4.5.2 or higher.)

Bigfootmech wrote Feb 21 at 10:54 PM

I have .NET 4.6.1 installed
"tries to connect to the outside world"
Would it get stopped by the firewall autoblocking connections until I make a rule?

Also, if I wanted to debug this, is it as simple as getting visual studio with the source code, building/running with that (don't know how I'd link up my existing exe), and setting breakpoints?

DanielPharos wrote Feb 22 at 6:55 AM

Would it get stopped by the firewall autoblocking connections until I make a rule?
Yes, WerFault's connections are getting blocked because there's no rule allowing them. If you allow it through, my guess would be that you'll see only one instead of many.
Also, if I wanted to debug this, is it as simple as getting visual studio with the source code, building/running with that (don't know how I'd link up my existing exe), and setting breakpoints?
Not for a full 100%, because the firewall will still call Notifier.exe, so you'll only be able to follow the code from after those Notifier.exe's send their information to the Visual Studio one. And there's a large chance the problem in happening in that code. I guess you could try attaching the Visual Studio debugger when Notifier.exe crashes, or use "poor man's debugging": add logging to the code, and afterwards read the log to see what happened.

DanielPharos wrote May 20 at 10:05 AM

I've just released a new version which contains fixes that may help out here too: https://wfn.codeplex.com/releases/view/631360

Can you please test that version?