Post by Stefan on Sept 17, 2021 8:44:26 GMT -5
Observed using version 2.5.21247
Please note: I do not have a reliable diagnosis, let alone a repeatable set of events.
Most of the time, (PA1) works as it should, but occasionally I've also experienced:
(1) A redisplay of the current screen (same line number range) but with all lines blank/empty
(2) A Loop detection, leading to ...Crashsave versions of open tabs
(3) An immediate closure of SPFLITE
It is intermittent, but I think(!?!)...
the issue may arise when editing a large file (say 40000 lines/4Mb on disc), possibly only with other tabs also open.
the user interacts with SPFLITE, WHILST(!) (PA1) is trying to replace the screen with it's previous image
e.g.:
I might be overtyping a line on the displayed range of 00001 to 00045 and then changing my mind and invoking (PA1) by pressing the <PAUSE> key.
Suddenly lines 1 to 45 are completely blank as in (1).
Sometimes they remain so, regardless of how long I wait, and even if I press (PA1) again. At other times they turn back to original data.... eventually.
Note that while (PA1) is busy doing it's thing, there's no outward indication of the looping nature of its efforts.
While (PA1) is still processing, the keyboard is, in 3270 parlance, unlocked, so the user can move the cursor, type commands, etc.
Windows may also update the title bar to show "(Not Responding)".
I assume that occurs if the user causes another 'attention' event (e.g. press <ENTER>) before (PA1) has finished processing.
It might be nothing serious, but the fact that SPFLITE might suddenly close or become unstable is probably worthy of some investigation.
