GitHub/GameNetworkingSockets
1
0
Fork 0
mirror of https://github.com/ValveSoftware/GameNetworkingSockets.git synced 2026-05-29 16:20:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Tweak assert threshold.

Browse Source 
It really bothers me that this is firing.  I should get to the bottom of
it eventually.  Perhaps something is being lazily initialized the first
time a lock is actually locked re-entrantly?
This commit is contained in:
Fletcher Dunn
2020-05-12 14:41:23 -07:00
parent 96ea8abeda
commit ef27e46ab0
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/steamnetworkingsockets/clientlib/steamnetworkingsockets_lowlevel.cpp
+2 -1
View File
@@ -122,7 +122,8 @@ void SteamDatagramTransportLock::OnLocked( const char *pszTag, SteamNetworkingMi
Assert( s_threadIDLockOwner == std::this_thread::get_id() );
// Getting it again had better be nearly instantaneous!
AssertMsg1( usecTimeSpentWaitingOnLock < 100, "Waited %lldusec to take second lock on the same thread??", (long long)usecTimeSpentWaitingOnLock );
// FIXME I don't know why this is firing with a lower threshold. What is it doing?
AssertMsg1( usecTimeSpentWaitingOnLock < 2000, "Waited %lldusec to take second lock on the same thread??", (long long)usecTimeSpentWaitingOnLock );
}
AddTag( pszTag );
}