|
A memory leak caused server memory to grow steadily without limit and performance eventually degraded significantly. This leak has been eliminated.
Note that this memory leak motivated users to periodically shut down and re-start the server for the purpose of reclaiming the memory. Elimination of this leak has helped the situation and periodic restart may no longer be necessary, or at least, it will not be necessary to re-start as often. Which is the case is yet to be determined conclusively.
In circumstances that were rare, but which did occur, it was possible to cause the creation of invalid index records. Because NewViews continually performs a series of checks on all records this bug would occasionlly surface as a error message that reported a bug and which would shut NewViews down. Invalid records introduced by this bug were detected by the nvcheck diagnostic tool, and could be fixed by the nvreorganize tool.
The bug occurred under relatively rare circumstances that required several database conditions to coincide. These circumstances involved the number of objects loaded and the order in which they had been loaded, so the bug depended on the dynamics of database usage. It also required that a transaction's header fields such as it's account, reference, or date, were changed either more than once before committing, or else changed several times and then the changes were aborted using the Edit>Quit command. It also occurred only on transactions with a number of transaction line items. Although the set of circumstances was rare, it was less rare in a multi-user environment where the object loading conditions were more likely to occur.
The point is that because this set of circumstances was so rare, and subtle, no user or Q.W.Page staff member was able to reproduce the bug, despite repeated efforts. That made the source of the bug very difficult to track down. However, information gathered over time allowed Q.W.Page staff to finally home-in on the bug, and once found, to reproduce it at will, and therefore eliminate it.
This release should not introduce additional invalid index records. However, the bug could still be reported due to invalid records already created by previous versions. In that case, run nvreorganize to eliminate the pre-existing invalid records
This release includes all corrections from Service Pack 1 , Service Pack 2 , Service Pack 3 , Service Pack 4 , Service Pack 5 , Service Pack 6 , Service Pack 7 , Service Pack 8 , Service Pack 9, and Service Pack 10. New features and corrections issued in the initial 2.08 release can be found here.