-
Notifications
You must be signed in to change notification settings - Fork 420
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
[BUG] 日志爆了 #637
Comments
你是不是开了 trace level 忘记关了?正常使用建议开启 info 以上的等级
发自我的iPhone
…------------------ 原始邮件 ------------------
From: Ns2Kracy ***@***.***>
发送时间: 03/19/2024, 17:34
To: LibNyanpasu/clash-nyanpasu ***@***.***>
抄送: Subscribed ***@***.***>
Subject: Re: [LibNyanpasu/clash-nyanpasu] [BUG] 日志爆了 (Issue #637)
复现步骤 / Step to reproduce
不清楚复现的过程。在日常使用中突然出现。
预期行为 / Expected behaviour
应该是很小的日志文件
实际行为 / Actual Behaviour
出现了一个单log 269GB,将c盘空间完全占用
应用日志 / App logs
No response
备注 / Addition details
a392c220fea074b6856a3072158e929e_720.jpg (view on web)
c4e550db71a82db963e400a00b8e3593.png (view on web)
5f84d7f4dabd78d4f255ac7b1ba01c1f_720.jpg (view on web)
Clash Nyapasu 版本号 / Clash Nyapasu
1.5.0
Clash 核心及其版本号 / Clash core and version
v1.18.1 Meta
是否为 Pre-release / Is pre-release version
否
操作系统及版本 / OS version
Windows 11
自查步骤 / Verify steps
如果您有足够的时间和能力,并愿意为此提交 PR ,请勾上此复选框 / Pull request is welcome. Check this if you want to start a pull request
您已知悉如果没有提供正确的系统信息,以及日记,您的 Issue 会直接被关闭 / You have known that if you don't provide correct system information and logs, your issue will be closed directly
您已仔细查看并知情 Q&A 和 FAQ 中的内容 / You have read and understood the contents of Q&A and FAQ.
您已搜索过 Issue Tracker,没有找到类似内容 / I have searched on Issue Tracker, No duplicate or related open issue has been found
您确保这个 Issue 只提及一个问题。如果您有多个问题报告,烦请发起多个 Issue / Ensure there is only one bug report in this issue. Please make mutiply issue for mutiply bugs
您确保已使用最新 Pre-release 版本测试,并且该问题在最新 Pre-release 版本中并未解决 / This bug have not solved in latest Pre-release version
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
杂项设置里有个 App Level
发自我的iPhone
…------------------ 原始邮件 ------------------
From: Ns2Kracy ***@***.***>
发送时间: 03/19/2024, 17:47
To: LibNyanpasu/clash-nyanpasu ***@***.***>
抄送: Jonson Petard ***@***.***>, Comment ***@***.***>
Subject: Re: [LibNyanpasu/clash-nyanpasu] [BUG] 日志爆了 (Issue #637)
并不是。之前的log都是正常的大概几十kb。日志等级也是info
image.png (view on web)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
所以说不知道形成这个日志炸弹的原因,也不知道该如何复现。 |
把超大的日记打开来看一下,如果打不开的话能否压缩一下,提交上来 |
这个文件将c盘所有空间都占了,1字节都没留,所以只能删除了,不然啥都干不了。 下午做的事大概就是开着代理开着腾讯会议看视频,期间有几次开启/关闭系统代理。 |
我前段时间也遇上了,生成了一个 400 多G的日志,当时软件非常卡。 |
硬盘爆了,但时间刚好卡在晚上 12 点,30 号的文件太大打不开,1 号的小一点,勉强打开看了一部分,最多的是: {"timestamp":"2024-05-01T01:10:13.550601Z","level":"ERROR","fields":{"message":"Incoming connection failed: 管道正在被关闭。 (os error 232)","log.target":"tauri_plugin_deep_link::platform_impl","log.module_path":"tauri_plugin_deep_link::platform_impl","log.file":"tauri-plugin-deep-link\\src\\windows.rs","log.line":62},"target":"tauri_plugin_deep_link::platform_impl","filename":"tauri-plugin-deep-link\\src\\windows.rs","line_number":62} |
@LJason77 能看下这种错误的时间戳是紧挨着的,类似于爆炸式出现的么?还是隔一会出现一次? |
@4o3F 时间戳连续的,爆炸式出现的,文件太大已经删除了。 |
请问下你的杀软是哪个?pipeline被强制关闭这个一般来说是权限更高的程序才能做到 |
没有使用任何杀软,只有微软自带的,并且开发需要把所有盘都设置为排除扫描了。 |
看了记录,第一次遇上好像是在看剧(?),时间太久记不清了。 |
复现步骤 / Step to reproduce
不清楚复现的过程。在日常使用中突然出现。
预期行为 / Expected behaviour
应该是很小的日志文件
实际行为 / Actual Behaviour
出现了一个单log 269GB,将c盘空间完全占用
应用日志 / App logs
No response
备注 / Addition details
Clash Nyapasu 版本号 / Clash Nyapasu
1.5.0
Clash 核心及其版本号 / Clash core and version
v1.18.1 Meta
是否为 Pre-release / Is pre-release version
否
操作系统及版本 / OS version
Windows 11
自查步骤 / Verify steps
The text was updated successfully, but these errors were encountered: