How to do memory profiling for Linux DGS when running in Multiplay?

[unity_03BA514BAC145D0E9AB3]

Hi, Can we connect memory profiler for Linux DGS running in Multiplay? I have a problems with memory leaks for my server but only happen in Linux build. I see memory usage increased with or without player joined, but it’s strange because when I tested locally with Windows DGS build, there is no leaks, and profiler seems fine. I use Photon Fusion and Unity 2021.3.12f1.

[alexeyzakharov]

If you use development player, then you should be able to connect to the server by IP with the Memory Profiler.

There should be no port blocking by default on the Multiplay side.
Unity players listen on the 55000 port by default and you can also specify is in the cmdline or BootConfig parameter as player-connection-listen-address

[qumoo]

@alexeyzakharov

If you use development player, then you should be able to connect to the server by IP with the Memory Profiler.

There should be no port blocking by default on the Multiplay side.
Unity players listen on the 55000 port by default and you can also specify is in the cmdline or BootConfig parameter as player-connection-listen-address

Hi,

I’m currently working on profiling for a Linux Dedicated Game Server (DGS) running in an Agones environment.

I attempted to use the player-connection-listen-address option as a cli argument, like my_app -batchmode -nographics -player-connection-listen-address 12345 (where 12345 is the port number I intend to use), expecting this to configure the server to listen on the specified address for player connections. Unfortunately, I haven’t observed any indications that the server is actually listening on the intended port.

Could anyone advise on the correct way to specify the port with a CLI argument?

[MartinTilo]

@qumoo

expecting this to configure the server to listen on the specified address for player connections. Unfortunately, I haven’t observed any indications that the server is actually listening on the intended port.

How did you come to the conclusion that it isn’t listening for those connections?

[qumoo]

Thank you for your reply. I concluded that the server isn’t listening for those connections based on the following observations:

• I am unable to connect using the Unity Profiler.

• The specified port does not appear to be listening.

Strangely, the profiling port is opened correctly only when the player-connection-listen-address is not specified. Here is an example to illustrate:

Run application without player-connection-listen-address

nohup ./my_app -batchmode -nographics & lsof -nP -iTCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
my_app 11 root 6u IPv4 69972 0t0 TCP *:55000 (LISTEN)
my_app 11 root 27u IPv4 69356 0t0 TCP *:7080 (LISTEN)
$ kill %1

Run application with player-connection-listen-address

nohup ./my_app -batchmode -nographics -player-connection-listen-address 12345 & lsof -nP -iTCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
my_app 107 root 26u IPv4 89565 0t0 TCP *:7080 (LISTEN)

As you can see, when I don’t specify player-connection-listen-address, the application listens on the expected (default) port. However, specifying the option seems to prevent the expected port from listening.

[qumoo]

I’ve discovered the missing piece. The player-connection-listen-address option requires a value in the format address:port.
Specifying it as -player-connection-listen-address 0.0.0.0:12345 worked perfectly.

Thank you!