search

EpicGamesExt / PixelStreamingInfrastructure

The official Pixel Streaming servers and frontend.
MIT License
137 stars 47 forks source link

RenderOffscreen on Linux issue #145

Open PotatoMilks opened 3 weeks ago

PotatoMilks commented 3 weeks ago

Component your question relates to

Background

We develop on Windows11 and provide pixel streaming services on Linux servers. Development environment: Windows 11, UE Engine 5.0.3 & UE Engine 5.4.1 Cross-compilation: v20_clang-13.0.1-centos7 (for UE 5.0.3) & v22_clang-16.0.6-centos7 (for UE 5.4.1) Linux server: Centos 8, i9-12900KF, RTX3080, memory 128GB

Question

  1. When starting with -RenderOffscreen command，Server memory will increase significantly over time until the memory is full. In Linux system, through the command: ./Fuzzy.sh -PixelStreamingURL="ws://127.0.0.1:13250" -PixelStreamingHideCursor -RenderOffScreen -ForceRes -ResX=1896 -ResY=800 When running, the system's memory usage will continue to grow in a short period of time. When the server is connected to the screen, run it through the command: ./Fuzzy.sh -PixelStreamingURL="ws://127.0.0.1:13250" -PixelStreamingHideCursor -ForceRes -ResX=1896 -ResY=800 The memory will not change significantly.（ I connect the server to a monitor and start it through the graphical interface, without using -RenderOffscreen command, the memory is normal.）

  2. Note: In the production deployment environment, the project is generally started through SSH, and the server will not be equipped with a display. And through SSH, if the -RenderOffScreen command is not used, a display window will pop up on the client.

Additional context

Operating system 系统版本 Graphics card and driver version 驱动版本 启动命令 启动命令 Memory problem Satrt:

Start

Run for half an hour:

End
lukehb commented 1 week ago

Hi,

As you are using 5.0.3 there have been a number of bug fixes around memory leaks since that version.

  1. Would you be able to try a newer version of UE (such as 5.4.2) to confirm if the issue still exists in your setup?

  2. Additionally, could you make a fresh third person project with Pixel Streaming enabled and check if you can reproduce the issue?

Regards, Luke.