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

v2ray-core v5.14.1 bug #2953

Closed
donghj2000 opened this issue Mar 31, 2024 · 6 comments
Closed

v2ray-core v5.14.1 bug #2953

donghj2000 opened this issue Mar 31, 2024 · 6 comments
Labels
documentation Documentation needs improvement Stale

Comments

@donghj2000
Copy link

你正在使用哪个版本的 V2Ray?

客户端 v2rayN 6.18, v2ray-core 5.14.1

你的使用场景是什么?

chrome看网页。

你看到的异常现象是什么?

升级到v2ray-core 5.14.1后就不能上网了。

你期待看到的正常表现是怎样的?

能正常上网。

请附上你的配置

服务端配置:

// 在这里附上服务器端配置文件

客户端配置:

// 在这里附上客户端配置
无。

请附上出错时软件输出的错误日志

服务器端错误日志:

// 在这里附上服务器端日志

客户端错误日志:

下载Core成功
正在解压......
https://github.com/v2fly/v2ray-core/releases/download/v5.14.1/v2ray-windows-64.zip
2024/3/31 星期日 下午 3:16:57 系统代理设置改变
更新Core成功!正在重启服务...
更新Core成功
配置成功

[VLESS] xxxxx(xxxxxxx:443)
启动服务(2024/3/31 星期日 下午 3:16:58)...
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime.asmstdcall(0x22fcf8)
	runtime/sys_windows_amd64.s:75 +0x7a fp=0x22fc80 sp=0x22fc60 pc=0x47a4da
rax     0x0
rbx     0x22a6638
rcx     0x285b528
rdx     0x20
rdi     0x7fffffde000
rsi     0x22fe78
rbp     0x22fdc0
rsp     0x22fc58
r8      0x0
r9      0x22fee8
r10     0x2bfa2e8
r11     0xc000004000
r12     0x22fec8
r13     0x0
r14     0x22a5120
r15     0x3
rip     0x0
rflags  0x10293
cs      0x33
fs      0x53
gs      0x2b

请附上访问日志

// 在这里附上服务器端日志

其它相关的配置文件(如 Nginx)和相关日志

如果 V2Ray 无法启动,请附上 --test 命令的输出

如果 V2Ray 服务运行异常,请附上 journal 日志

@donghj2000
Copy link
Author

donghj2000 commented Mar 31, 2024

v5.13.0 x64 exe和v5.12.1 x64 exe及以前的版本是好的。v5.14.0 x64 exe出异常。
但是v5.13.0 和v5.14.0 的源码只相差一行,编译出来的exe都能正常运行。
image

@donghj2000
Copy link
Author

找到原因了,v5.15.0 使用了go 1.21版本来编译,该版本需要windows 10, 有些API在windows 7下没有。所以使用windows 7 会异常 。
golang/go#64622

@AkinoKaede AkinoKaede added the documentation Documentation needs improvement label Apr 5, 2024
@AkinoKaede
Copy link
Contributor

Thank you for your feedback, it helps other users.

@i486
Copy link

i486 commented May 5, 2024

I'm not a developer, but from what I can gather from this discussion, it seems like there's only one API change that broke Go on Windows 7. After reading the entire conversation, it looks like many of the main Go developers are open to make Go compatible with Windows 7 again. They're just waiting for a volunteer to handle it through proper channels. Anyone?

@AkinoKaede
Copy link
Contributor

I'm not a developer, but from what I can gather from this discussion, it seems like there's only one API change that broke Go on Windows 7. After reading the entire conversation, it looks like many of the main Go developers are open to make Go compatible with Windows 7 again. They're just waiting for a volunteer to handle it through proper channels. Anyone?

V2Ray will continue to be built using the latest mainline version of Go, and continued support for Windows 7 will depend on Go.

Copy link
Contributor

This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 5 days

@github-actions github-actions bot added the Stale label Sep 20, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation needs improvement Stale
Projects
None yet
Development

No branches or pull requests

3 participants