Macrium Support Forum

Ctrl key redraws scheduled task history

By JK - 22 January 2022 5:42 AM

In v8.0.6161, if one clicks on one of the listed backup definitions or the corresponding schedules in the Scheduled Backups view, the scheduled task history is drawn in the History tab.  If one subsequently taps the Ctrl key, the history list is redrawn.  Holding down the Ctrl key apparently causes the Reflect to attempt to repeatedly redraw the history list at a frequency that is too high to allow the list to be displayed, resulting in a blank list (with flickering artefacts along the GUI borders).

As I was testing this behavior by repeatedly tapping/pressing the Ctrl key, I also caused Reflect to crash with Event ID 1000, as reported by the Windows Event Viewer: [Edited to Add: Per the discussion in follow-up posts below, this crash appears to be unrelated to the Ctrl key issue described above, but is most likely a symptom of general instabilities in v8.0.6161 that have been fixed in v8.0.6392)]
Faulting application name: reflectbin.exe, version: 8.0.6161.0, time stamp: 0x613732fe
Faulting module name: reflectbin.exe, version: 8.0.6161.0, time stamp: 0x613732fe
Exception code: 0xc000041d
Fault offset: 0x0000000000573d4f
Faulting process id: 0x2d68
Faulting application start time: 0x01d80f49eed5e0f5
Faulting application path: C:\program files\macrium\reflect\reflectbin.exe
Faulting module path: C:\program files\macrium\reflect\reflectbin.exe
Report Id: adb10e4d-fca3-443f-a6cd-b67a0f2ab125
Faulting package full name:
Faulting package-relative application ID:

Does v8.0.6392 still have the history redraw behavior triggered by the Ctrl key as described above?  I've been holding out on updating until the next patch (I think there's one coming soon?), but if this is confirmed fixed in v8.0.6392, then perhaps I'll go ahead and grab that one.
By capair45 - 22 January 2022 2:08 PM

I was able to reproduce that behavior with .6392 however, Reflect did not crash with continued pressing of the Ctrl key.  It attempted to redraw the list and the screen flickered as you describe but after about 20 seconds, I released the Ctrl key and the list was visible.
By JK - 22 January 2022 2:51 PM

Thanks for confirming, Cap.  The crash may have been related to a similar instability issue I recently encountered (with the same exception code -- 0xc000041d), which tech support says is supposed to have been fixed in v8.0.6392.  Thus, the crash described above is probably not directly related to the Ctrl key issue; I will edit my OP accordingly.

This leaves still leaves us with a confirmed observation of unexpected Ctrl key behavior when viewing the History page.  Not a huge deal, as far as bugs go, but it does make it difficult to take screen shots of the History page using PrintScreen (which is how I discovered this issue).  Hopefully I am correct about the crash being unrelated.
By capair45 - 22 January 2022 2:55 PM

I've found the snipping tool much easier to use for screen shots.  Smile
By JK - 22 January 2022 2:58 PM

Well, you know the one about old dogs and new tricks...   Smile
By capair45 - 22 January 2022 3:00 PM

JK - 22 January 2022 2:58 PM
Well, you know the one about old dogs and new tricks...   Smile

All too well....
By dbminter - 22 January 2022 3:12 PM

As another data point, I can also reproduce the redrawing with the CTRL key on 6392.  Never got a crash, either, though.
By JK - 22 January 2022 11:13 PM


After some further testing, I discovered that the redraw behavior occurs for almost every key on the keyboard, not just Ctrl.  The main exceptions I found were the Alt key (which changes the focus to the navigation menu at the top of the GUI), and the PrintScreen key.
By dbminter - 22 January 2022 11:23 PM

Ditto.  I also discovered it occurs if you click on an entry in Scheduled Backups with the mouse and click on it again.  But, that may actually be intentional since the software doesn't really have a frame of reference to know the user has selected a different entry, so it has to redraw with every mouse selection.