OwO-Network/DeepLX

Win10一打开就闪退, 把能关的都关了也无法解决问题, 用ProcessMonitor记录了下崩溃过程

Closed this issue · 22 comments

Logfile.CSV

内容有点多, 保存成CSV文件了

It should not be double-clicked to open. You must first open Terminal and execute the following command in the directory where the binary file is located.

.\deeplx_windows_amd64.exe

It should not be double-clicked to open. You must first open Terminal and execute the following command in the directory where the binary file is located.

.\deeplx_windows_amd64.exe

It doesn't work
QQ截图20240325052900

Since there is no error, it seems that your port is occupied, so the process is killed.

Since there is no error, it seems that your port is occupied, so the process is killed.

I have also checked the port, and there is no case of port 1188 being occupied.

QQ截图20240325053649

I'm sorry I don't have a Windows device to test on.

我的也是这个问题,闪退,你的解决了吗

我的也是这个问题,闪退,你的解决了吗

Can you test the last version?

image

I commissioned a friend to test this and was unable to reproduce the problem.

我的也是这个问题,闪退,你的解决了吗

没解决, 我的主力机是win10的, 还有一台win11的电脑里DeepLX可以正常启动, 只能用局域网转发到那台电脑上来使用DeepLX

我是win11的一直可以运行,但从3月24号就突然打开就闪退。我也弄了两天都不行

我的也是这个问题,闪退,你的解决了吗

Can you test the last version?

I'm using version 0.9.1, but it still doesn't work. It crashes

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

The 0.9.0 version also crashes.

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

The 0.9.0 version also crashes.

What about earlier versions? Is it convenient to test it?

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

The 0.9.0 version also crashes.

What about earlier versions? Is it convenient to test it?

Sure. Convenient. But I've tried many versions already. Still crashing!

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

The 0.9.0 version also crashes.

What about earlier versions? Is it convenient to test it?

Sure. Convenient. But I've tried many versions already. Still crashing!

Is it an issue with the .NET installation?

At present, I have not found out the specific reason, but the code of the latest version v0.9.1 has indeed undergone major changes. It is recommended that you use v0.9.0 for the time being. Basically, the experience is the same.

The 0.9.0 version also crashes.

What about earlier versions? Is it convenient to test it?

Test if it can run normally in Windows Sandbox.

image

I commissioned a friend to test this and was unable to reproduce the problem.

i have same problem, v0.9.1
image
without any error message then exit.
my windows version is
image
I hope the author can fix this bug as early as possible, Thanks!

image
I commissioned a friend to test this and was unable to reproduce the problem.

i have same problem, v0.9.1
image
without any error message then exit.
my windows version is
image
I hope the author can fix this bug as early as possible, Thanks!

看不到你的图片。

image
I commissioned a friend to test this and was unable to reproduce the problem.

i have same problem, v0.9.1
image
without any error message then exit.
my windows version is
image
I hope the author can fix this bug as early as possible, Thanks!

看不到你的图片。



这是双击打开录下的gif

换了一台AMD笔记本就行了,系统版本是一样的

的确可能是端口占用的问题,我尝试添加参数-p 手动指定端口,测试成功了。默认1188的端口可能存在冲突或其他未知的问题。感谢作者这么优秀的作品,希望后续能持续更新维护。