I've only ever seen this happen with the Linux package-manager-type process where the update might happen "underneath" the browser without its knowledge. Using their built-in upgrade system as far as I know it just happens only on browser restart... but I guess I haven't used it on Windows in a long time.