Bug 1087 - Simulation progress bar doesn't complete as expected
Summary: Simulation progress bar doesn't complete as expected
Status: RESOLVED FIXED
Alias: None
Product: DIRSIG4
Classification: Unclassified
Component: User Interface (show other bugs)
Version: 4.5.3-release
Hardware: Intel x86-64 Windows 64-bit
: P5 normal
Assignee: Scott D. Brown
URL:
Depends on:
Blocks:
 
Reported: 2014-02-04 14:28 EST by Scott D. Brown
Modified: 2015-07-13 12:30 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Scott D. Brown 2014-02-04 14:28:30 EST
This was observed on Windows 7 machines at the January training session on single frame simulations.
Comment 1 Scott D. Brown 2014-02-06 12:19:56 EST
On a single capture simulation, the progress bar stopped at 83% even though all 6 of 6 scheduled events were performed.  We think this is because of the order that the progress bar current and maximum values were updated.

A fix has been added and will be tested on the training laptops.
Comment 2 Scott D. Brown 2015-07-13 12:26:25 EDT
We noticed that this issue has persisted and the proposed fix from a year and a half ago didn't work.
Comment 3 Scott D. Brown 2015-07-13 12:30:43 EDT
The bug seemed to be isolate to Windows laptops, but we believe that it has been observed on Linux and Mac as well (just far less rarely).

After some thorough testing and debugging on Windows, it was discovered that if the routine that scans the output of the dirsig sub-process was long and contained more than one event update message, that the progress bar update logic would not work correctly.  Perhaps the reason the problem occurred so regularly on Windows was because the process output was processed less frequently, which resulted in larger output text chunks and an increased liklihood of multiple event messages.

Improved logic was introduced for the 4.6.3 release.