0005753: initial SUMo (Pro) scan action after auto-update crashes with error popup

ID	Project	Category	View Status	Date Submitted	Last Update

0005753	SUMo	Bug	public	2019-11-12 11:18	2019-11-28 21:04

Reporter	wolf	Assigned To	Kyle_Katarn
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	feedback	Resolution	open
Platform	Notebook	OS	Windows 10 64-bit	OS Version	1903
Product Version	5.10.2

Summary	0005753: initial SUMo (Pro) scan action after auto-update crashes with error popup
Description	SUMo Pro offered my auto-update of version 5.10.1 to 5.10.2. So I did. Then it proposed a scan action as not having run it with the new version. So I did. That scan action didn't finish. It aborted with an error popup message. That message wasn't localized although the rest of the GUI is. Claiming something about an index out of range. See attached screenshots.
Additional Information	Obviously, the scan steps did not yet start consolidation as seen by the count of the 2nd screenshot. When I did the last scan action with the previous version of SUMo, that unconsolidated count was much higher, just below 27500. Consolidated they turn down to something between 8020 and 8150. Just to provide some context which index might get out of range. Obviously, 32k wasn't reached. It's no server. It's a workstation configuration on a notebook.
Tags	No tags attached.

wolf 2019-11-12 11:18 reporter	sumo.scan.20191112.png (17,663 bytes) sumo.scan.20191112.png (17,663 bytes) sumo.scan.a.20191112.png (158,490 bytes) sumo.scan.a.20191112.png (158,490 bytes)

Kyle_Katarn 2019-11-12 21:55 administrator ~0003763	Please attach log at the time of the crash

wolf 2019-11-28 16:14 reporter	sumo.scan.20191114.png (330,704 bytes)

wolf 2019-11-28 16:14 reporter ~0003786	This behaviour isn't limited to scan action after auto-update. It also happens sometimes on scan action. It doesn't require an auto-update of SUMo itself. I couldn't make that issue deterministic. Don't know the circumstances. Sometimes it happens. Sometimes scan action works as expected without issues. On your request I was looking for a log file when such an issue happens. But I can't provide you such a log file! The log file was a day old when such a symptom happens, so nothing getting logged. And as you know, I cannot turn on debugging for SUMo with my SUMo configuration as this will lead to a different crash already reported also without a current log file. But that behaviour was deterministic while the currently reported one is not yet deterministic.

Kyle_Katarn 2019-11-28 21:04 administrator ~0003790	OK

Date Modified	Username	Field	Change
2019-11-12 11:18	wolf	New Issue
2019-11-12 11:18	wolf	File Added: sumo.scan.20191112.png
2019-11-12 11:18	wolf	File Added: sumo.scan.a.20191112.png
2019-11-12 21:55	Kyle_Katarn	Assigned To	=> Kyle_Katarn
2019-11-12 21:55	Kyle_Katarn	Status	new => feedback
2019-11-12 21:55	Kyle_Katarn	Note Added: 0003763
2019-11-28 16:14	wolf	File Added: sumo.scan.20191114.png
2019-11-28 16:14	wolf	Note Added: 0003786
2019-11-28 21:04	Kyle_Katarn	Note Added: 0003790