summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/vnc/806656
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-07-03 07:27:52 +0000
commitd0c85e36e4de67af628d54e9ab577cc3fad7796a (patch)
treef8f784b0f04343b90516a338d6df81df3a85dfa2 /results/classifier/gemma3:12b/vnc/806656
parent7f4364274750eb8cb39a3e7493132fca1c01232e (diff)
downloadqemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.tar.gz
qemu-analysis-d0c85e36e4de67af628d54e9ab577cc3fad7796a.zip
add deepseek and gemma results
Diffstat (limited to 'results/classifier/gemma3:12b/vnc/806656')
-rw-r--r--results/classifier/gemma3:12b/vnc/8066568
1 files changed, 8 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/vnc/806656 b/results/classifier/gemma3:12b/vnc/806656
new file mode 100644
index 000000000..d69e144c3
--- /dev/null
+++ b/results/classifier/gemma3:12b/vnc/806656
@@ -0,0 +1,8 @@
+
+Tight PNG VNC encoding is sent even when --disable-vnc-png is set
+
+This bug exists in 0.14.1 and also in 9312805d33e8b (Jun 17, 2011) in the master git repo.
+
+The "Tight PNG" encoding is a derivative of the "Tight" encoding that replaces zlib encoded rects with PNG encoded data instead. However, when the "Tight PNG" encoding is disabled (--disable-vnc-png), the server will send frame buffer updates that are marked as "Tight PNG" but in fact contain zlib encoded regions (i.e. it's really "tight" protocol).
+
+The "Tight PNG" encoding should only be used when --enable-vnc-png is set.
\ No newline at end of file