1 files changed, 71 insertions, 0 deletions
diff --git a/results/classifier/118/none/1802915 b/results/classifier/118/none/1802915
new file mode 100644
index 00000000..12d98ef4
--- /dev/null
+++ b/results/classifier/118/none/1802915
@@ -0,0 +1,71 @@
+performance: 0.422
+graphic: 0.362
+semantic: 0.333
+mistranslation: 0.303
+device: 0.275
+user-level: 0.203
+socket: 0.201
+PID: 0.191
+register: 0.190
+debug: 0.184
+vnc: 0.172
+risc-v: 0.161
+architecture: 0.142
+ppc: 0.136
+files: 0.135
+permissions: 0.131
+boot: 0.120
+network: 0.115
+arm: 0.109
+virtual: 0.100
+hypervisor: 0.090
+peripherals: 0.090
+VMM: 0.085
+TCG: 0.081
+x86: 0.079
+assembly: 0.070
+kernel: 0.070
+i386: 0.063
+KVM: 0.062
+
+GTK display refresh rate is throttled
+
+Guest OS running with GL enabled GTK display shows a reduced refresh rate, e.g. moving cursor around with iGVT-g DMA Buf.
+
+It seems that a default refresh interval GUI_REFRESH_INTERVAL_DEFAULT (30ms) is defined in include/ui/console.h, throttling the display refresh rate at 33Hz.
+
+To correct this throttle issue, a shorter interval should be applied to display change listener or the default value should be used.
+
+
+
+Slow motion clips for host/guest were uploaded as attachments.
+
+Instead of changing the value, I think there should be a function that determines the ideal "GUI_REFRESH_INTERVAL_DEFAULT" value, with the option to override it. That way, monitor greater than 60 Hz can also benefit.
+
+The QEMU project is currently considering to move its bug tracking to
+another system. For this we need to know which bugs are still valid
+and which could be closed already. Thus we are setting older bugs to
+"Incomplete" now.
+
+If you still think this bug report here is valid, then please switch
+the state back to "New" within the next 60 days, otherwise this report
+will be marked as "Expired". Or please mark it as "Fix Released" if
+the problem has been solved with a newer version of QEMU already.
+
+Thank you and sorry for the inconvenience.
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
+The bug is still here.
+
+People are simply modifying the code and recompiling.. It only needs to change the code cap from 30ms (10 years old cap) to 16ms, and we got a smooth gui capable of gaming.
+
+Please, don't ignore us. Recompiling qemu only for one number is very annoying.
+
+The ticket has been re-opened here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/700
+
+... so let's keep this one here closed, please.
+