On 22 Jan 2005 at 21:31, [EMAIL PROTECTED] wrote:
My theory is that at this point, there is a problem with the way Finale has been programmed. . . .
I think *that's* indisputable!
. . . A problem, which results in the Overwrite Bug, that when there is more memory in a machine, doesn't occur. But when there isn't enough memory and the system gets to the point of thrashing, then the mistakes made in the way that Finale was written result in this problem.
I don't know that anyone has identified low memory as a requirement to produce the bug.
That is true...no one has identified that for sure. But given the way the machines act about the time the bug bites, and Christopher at least has said that it has never happened to him on a newly booted machine, to me, it seems possible that there may be a correlation between memory and this bug...but I'm also just speculating :-)
Can you think of anything in the way a program is coded that would fit into this scenario and possibly cause the overwrite bug? Problems with the way the program uses threads? I/O issues? Caching? etc....?
I can't think of a reason why low memory could suddenly cause corruption of such a minor type. When a program can't handle low memory conditions, usually the results are fairly catastrophic.
Well, for those that are losing the work, it can be catastrophic!! :-) And I think that Christopher mentioned that after the bug hit on his machine, Finale crashed shortly after that.
I just looked back at a couple of posts one from Chuck and one from Mark. Chuck mentioned that his system seemed to start to slow down after a long Finale session and that is when the icon for the selected tool in the tool palette turns into the Finale icon. (I've had this happen to me too.) Mark had a similar thing happening with icons appearing incorrectly....with the wrong graphic and then a garbled graphic. His system was also in the state where it seemed that memory was "tight" as he put it.
Of course, it depends on the type of low memory condition.
Can you elaborate here?
I still don't think the memory issue really has anything to do with it. When the OS is thrashing, Finale should just slow down to a crawl, and, perhaps, stop.
Well, your input is much appreciated David. Many thanks to you.
-K
-- _______________________________________________ Finale mailing list [email protected] http://lists.shsu.edu/mailman/listinfo/finale
