You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have observed occasional hangs at Publisher::WaitForConnection(), which has a potentially infinite loop. There is an alternative version of the function with takes a common::Time as a timeout argument, but it's only being used by gzlog.cc:959.
The function is called without a timeout in the following places:
Use fixed values timeouts for testing is a bit tricky since the machine performance could vary, which could end up in false positives. They could be valid when we expect a value and get a result which is clearly above or under the magnitude order we expect. To optimize the check, probably the ideal case would be to overload the Publisher::WaitForConnection() to include a callback.
If we don't set an explicit Timeout here, gtest will kill it after 240 secs right? That should cover the infinite loops and problems with the async calls.
True, gtest will kill it after 240 seconds, but gzserver and gzclient would hang if it happened. I wonder if ignition-transport will have this same problem? @caguero
Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).
I have observed occasional hangs at Publisher::WaitForConnection(), which has a potentially infinite loop. There is an alternative version of the function with takes a
common::Time
as a timeout argument, but it's only being used by gzlog.cc:959.The function is called without a timeout in the following places:
Seeing Scene.cc in this list makes me think of issue #681 (blank gzclient windows on startup).
The text was updated successfully, but these errors were encountered: