Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nonpaged Pool Memory Leak in netio.sys When Using Mirrored Network Mode #12006

Closed
1 of 2 tasks
wuxie0ne opened this issue Sep 8, 2024 · 6 comments
Closed
1 of 2 tasks

Comments

@wuxie0ne
Copy link

wuxie0ne commented Sep 8, 2024

Windows Version

Microsoft Windows [Version 10.0.22631.4112]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Arch rolling

Other Software

No response

Repro Steps

.wslconfig

[experimental]
networkingMode=mirrored

Expected Behavior

Nonpaged Pool Memory should be a stable and low value, usually within 1G.

Actual Behavior

Nonpaged Pool Memory will grow by 1~2 Mib per second until all memory is occupied.

61322c64113de6b74f63f7e36da3a96
f0fd8799c05f31016ca75bbb2bd480f

This problem does not occur when I set networkingMode=NAT, but only occurs when I change it to mirrored.

Diagnostic Logs

WslNetworkingLogs-2024-09-08_22-15-38.zip

Copy link

github-actions bot commented Sep 8, 2024

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@wuxie0ne
Copy link
Author

wuxie0ne commented Sep 8, 2024

Logs are required for review from WSL team

WSL 团队需要审核日志
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.如果这是一个功能请求,请回复“/feature”。如果这是一个问题,请用“/question”回复。 Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.否则,请按照以下说明附加日志​​,除非添加日志,否则您的问题将不会被审核。这些日志将帮助我们了解您的机器中发生的情况。

How to collect WSL logs
如何收集WSL日志
Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:下载并在管理 powershell 提示符下执行collect-wsl-logs.ps1

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.完成后,脚本将输出日志文件的路径。

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here如果这是网络问题,请使用collect-networking-logs.ps1 ,按照此处的说明进行操作

Once completed please upload the output files to this Github issue.完成后,请将输出文件上传到此 Github 问题。

Click here for more info on logging单击此处了解有关日志记录的更多信息 If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.如果您选择通过电子邮件发送这些日志而不是附加到错误中,请将它们发送至[email protected] ,并在主题中注明 github 问题的编号,并在消息中提供指向您在 github 中的评论的链接使用“/emailed-logs”发出和回复。

View similar issues 查看类似问题

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!请查看下面的问题,看看它们是否能解决您的问题,如果该问题描述了您的问题,请考虑关闭此问题并点赞另一个问题,以帮助我们优先处理它!

Open similar issues: 打开类似问题:

Closed similar issues: 已关闭类似问题:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.注意:您可以通过赞成或反对此评论来向我提供反馈。

WslNetworkingLogs-2024-09-08_22-15-38.zip

Copy link

github-actions bot commented Sep 8, 2024

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information
appxpackage.txt not found
optional-components.txt not found
No logs.etl found in archive.
Error while parsing the logs. See action page for details

Copy link

github-actions bot commented Sep 8, 2024

No logs.etl found in the archive. Make sure that you ran collect-wsl-logs.ps1 as administrator and that the logs.etl file is in the archive.

Diagnostic information
Issue was edited and new log file was found: https://github.com/user-attachments/files/16922571/WslNetworkingLogs-2024-09-08_22-15-38.zip
appxpackage.txt not found
optional-components.txt not found
No logs.etl found in archive.
Error while parsing the logs. See action page for details

@shdancer
Copy link

same problem

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants