Update the vnc_server's sequential frame number on frame updates
The vnc_server asks for frames newer than the last frame it got. The
last frame's sequential number was not being updated properly, which
caused the vnc_server to always ask for a frame newer than 0 causing
the call to return immediately and jpeg-encode and send to the client
the same frame repeatedly, hence overusing the CPU.
Bug: 132206213
Test: run locally, verified CPU usage is lower
Change-Id: I46380ba5934c3432d55cce6f4f767ee35891a947
diff --git a/host/frontend/vnc_server/screen_connector.cpp b/host/frontend/vnc_server/screen_connector.cpp
index ea82f7e..1b9b900 100644
--- a/host/frontend/vnc_server/screen_connector.cpp
+++ b/host/frontend/vnc_server/screen_connector.cpp
@@ -61,6 +61,7 @@
while (seq_num_ == *seq_num) {
new_frame_cond_var_.wait(lock);
}
+ *seq_num = seq_num_;
return newest_buffer_;
}