Open azrogers opened 2 months ago
There's a few issues with this test as it stands... the test can only actually run for three hours total... I can't think of a better dataset than P3DT to run this test with, so do we fix this bug instead?
Hitting the token refresh interval doesn't sound like an issue with this PR. If the soak test does fail because of token issues, sounds like it's doing the job perfectly (finding any issue when running a long time).
(deleted this comment because I added it to the wrong issue)
To test out CesiumGS/cesium-native#876, I've created a long-running soak test to evaluate the memory usage of cesium-native over a long period. The test consists of loading the Google P3DT and flying to random locations around the globe over and over again for twelve straight hours. There's a few issues with this test as it stands: