Windows Server 2022: performance improved a lot, but the UI process still exits by itself and 4310 becomes unreachable

[lxm98083-boop]

Hi, thank you for the recent optimization work.

I want to report both the good news and the remaining issue from my Windows environment.

Good news: performance is much better now

Previously, on my machine, the control center was almost unusable:

• Home page load was around 23 seconds
• Settings page load was around 12 seconds

After the recent updates, performance improved dramatically:

• The UI now opens very fast
• Page opening speed is now acceptable / good in normal use

So first of all: the recent performance optimization is clearly working.

Remaining problem: the UI process still exits by itself

The main remaining issue is stability.

Today, during actual use on my machine, the UI process exited by itself multiple times.

Each time this happened:

• http://127.0.0.1:4310/ stopped responding
• the browser showed connection refused
• I had to restart it manually

So this is not just a theoretical concern — it happened in real usage more than once today.

Another issue seen on first startup

On first startup, I also saw a missing file warning related to:

runtime/avatar-preferences.json

After creating that file manually, that specific warning stopped.

So this seems like a first-run initialization problem that should probably be handled automatically.

What I had to do on my side

Because the UI process could exit by itself, I ended up creating Windows scripts / scheduled tasks to:

• start it automatically at system boot
• check it periodically
• bring it back if port 4310 is no longer listening

This means the current version is already much faster, but still not stable enough for unattended use on my Windows setup.

Environment

• OS: Windows Server 2022 Standard
• OpenClaw: native Windows install
• CPU: Intel Core i9-13900K
• GPU: GIGABYTE AORUS GeForce RTX 5090 MASTER 32GB
• Motherboard: ASUS TUF GAMING Z790-PLUS WIFI
• RAM: G.SKILL Ripjaws S5 DDR5-6000 128GB (32GB x4), currently stable at 5200 MT/s
• SSD: M.2 NVMe PCIe SSD 4TB

Summary

So from my current testing result:

• Performance is much better than before
• But stability is still a real issue on Windows
• The process can still exit by itself
• When that happens, 127.0.0.1:4310 becomes unavailable

Suggestions

It would be great if future updates could improve:

1. first-run initialization for missing runtime files
2. process stability on Windows
3. built-in self-recovery / watchdog behavior if the UI process exits unexpectedly

If needed, I can continue testing on this Windows environment and provide more feedback.

Thanks again — the speed improvement is very noticeable, and I think this project is moving in a good direction.

[TianyiDataScience]

谢谢你把 Windows Server 的现象写得这么完整。

你提到的 runtime/avatar-preferences.json 首次启动 warning，我已经先修了一小块到 main：0895a0d7948b770a88213c298ee4d68fd1c84776。现在这个文件缺失会被当成正常的首次运行默认状态，不会再提示需要手动创建；如果文件存在但内容损坏，才会继续给出规范化 warning。

进程自己退出、127.0.0.1:4310 变成 connection refused 这部分我先不直接关，因为还需要崩溃时的证据。麻烦更新到最新 main 后，如果还会退出，请补充：启动命令、退出前后的终端输出、Windows 事件查看器里对应时间点的应用错误，以及大概多久会复现。这样才能区分是 Node 进程崩溃、被系统任务杀掉，还是端口/守护方式问题。