The data area passed to a system call is too small

[vault-thirteen]

I am having an issue.

Every time I use this tool, it works normally for severals minutes and then comes an error after which the tool closes itrself.

The error says:

The data area passed to a system call is too small.

Here is the screenshot.

O.S. is Windows 10 22H2 (OS Build 19045.5487)

WFN was taken from the beta release:
wfn-20250103-dbe37c-x64-standalone.zip

[wokhan]

Hi, by any chance, do you use SQL server on your computer? (as there is a MS known issue when SQL server is installed on a server, the observed message shows up when launching a desktop bridge app - I doubt this is the cause as WFN doesn't use desktop bridge, but worth checking).

[vault-thirteen]

How is any SQL-based server related to the Windows' Firewall ??

[wokhan]

It's not... I'm only sharing that MS has a known issue for when SQL server is installed and you launch a desktop bridge based app (which, again, WFN is not, but better ensure it's not another edge case for this issue). I've never seen this error message and cannot reproduce, so...

[vault-thirteen]

Thank you for the information. I will try to get more details.

[vault-thirteen]

I have no SQL servers installed on the computer, so I have no idea what you are talking about.

I have made another experiment. I have started WFN and waited for some time. It showed this error again and then the application closed itself. So, the reason is this application – the WFN.

It looks like frequency of these error messages depends on the amount of network traffic. The more torrents (BitTorrent) I serve, the more frequently the error is shown.

I've never seen this error message and cannot reproduce, so...

Try WFN with many BitTorrents. WFN always crashes on my PC when I use it together with torrents.

What does this "so ..." mean ?

[wokhan]

This was my first question: "do you have SQL server installed" 😁
The last "so..." was only to emphase the fact that I cannot help, yet, as I can't reproduce.
Could you grab the log file to see if there is anything useful in there? Torrents is a good clue though, maybe some file paths are too long (we always observe "fun" things when paths are longer than 255 chars on system calls, for instance... could also be a 4096 bytes limit for some method argument).

[vault-thirteen]

Could you grab the log file to see if there is anything useful in there?

Sure. Where can I find it ?