Steamworks.NET icon indicating copy to clipboard operation
Steamworks.NET copied to clipboard

Editor hangs every few seconds after initializing Steamworks.NET

Open sebastianfreitag opened this issue 6 years ago • 2 comments

When entering Play Mode in the Unity Editor, and initializing Steamworks there, and ending the game, the Unity Editor starts hanging every few seconds. So, every few seconds, the GUI does not react at all for ~2 seconds. It does not happen in Play Mode (only in the Editor), and only happens after Steamworks is first initialized (in Play Mode). Restarting Unity fixes the issue until Steamworks is initialized again. Note that it also doesn't happen if Steam is not started and therefore Steamworks is never correctly initialized.

This makes it almost impossible to work with Unity.

For me, the bug has only existed for a week or so (maybe May 6th?), and might have appeared together with a Steam update, but I'm not sure.

I can reproduce the bug every time without fail, so it's very deterministic.

Unity Version is 2017.3.0 Steamworks SDK 1.42 latest master branch of Steamworks.NET (also happens on the last Release version)

sebastianfreitag avatar May 10 '18 15:05 sebastianfreitag

Did you ever figure out what was causing this?

rlabrecque avatar Nov 26 '18 06:11 rlabrecque

It sounds like it could be a network issue, for example a dead DNS server in network settings, which hangs every time a host is looked up, until it times out and moves to the next DNS server. Just guessing. Should be easy to reproduce by adding a non working IP address to the top of DNS list, and seeing if it causes the hang.

spajus avatar Nov 27 '18 05:11 spajus