Fix Version/s: None
0.4.11-RC-23-gb5fef42 gcc dbg
Revo Uninstaller 1.95 from rapps
I noticed similar stuff in earlier release tests already, but was never able to give exact repro-steps for heap-assertion and exception. Now I can.
-Install and run the application
-select "Hunter mode" ("Jagdmodus" in german)
-click or drag the appearing Cross on the screen, side-note: Notice that the balloon-tips are not overpainted correctly when they vanish
-reopen the GUI of RevoUninstaller via Systray-icon
-click a different entry in menubar (in my video I clicked "Tools")
click "Hunter mode" a second time
Reproducibly and exactly when we click "Hunter Mode" the second time, we will get a heap assertion. It is reproducibly impossible to type 'b' then with the aim to break into debugger (to collect a stacktrace). Execution will immediately continue whatever I press here. Immediately afterwards we see an unhandled exception.
At this point it is very wise to ACPI-soft-power-off ros, because after this point it is possible to have horrible follow-up issues in WIN32SS (even in the lucky case that we still manage to close the Revo-process via taskmgr).
DefinitionOfDone is to prevent the heap-assertion / exception.
I double-checked: In Windows XP SP3 the described sequence causes absolutely no problems.