Avidemux v2.7.6 x64 - Problems detected:

[Liina]

Avidemux v2.7.6 x64 - Problems detected:

OS       - Windows 7 Enterprise x64
CPU      - Intel i5, 3.40 GHz
RAM      - 8 GB
Graphics - Intel HD Graphics 4600 with 2 GB graphics memory

1. Display garbage is left over the GUI. It is not a graphic card or computer's OS
   related, because it happens only with Avidemux and on any computer!
   
2. Shut-down doesn't wait for the very end of the process and the log file to be
   100% finished.

3. Log file timing starts normal (local) but then changes to UTC (or what?). Why?

[eumagga0x2a]

1. Display garbage is left over the GUI. It is not a graphic card or computer's OS
   related, because it happens only with Avidemux and on any computer!

I cannot reproduce this on Windows 10 (Intel Iris 540), on Linux (NVIDIA) or on macOS with current 2.7.7 builds (2.7.6 is already pretty outdated) with any of Qt themes (your screenshot shows the "windows" Qt theme). Is anything special needed (apart from Windows 7 with old Intel graphics) to be able to reproduce it?

2. Shut-down doesn't wait for the very end of the process and the log file to be
   100% finished.

Yes, we ask Windows from within the encoding dialog to shut down (ExitWindowsEx()) and it kicks Avidemux out of memory. The message "Requesting shutdown..." should appear in the log, however, so if it does not, we need a fflush(stdout) call with VC++ builds which don't flush the log to disk on every message. Everything thereafter is at Windows' discretion out of control of Avidemux, IMVHO.

3. Log file timing starts normal (local) but then changes to UTC (or what?). Why?

Right, the "Time: " log entry shows the local time as returned by ctime(), other messages with timestamps use gettimeofday() which returns UTC. Why not?