OW 5.1 Final Released

[Ken Case]

On Jan 6, 2005, at 8:39 AM, Jake Robb wrote:
> The only information I have right now that might be helpful is that 
> when you
> close OW, normally it takes a moment (possibly not a noticeable one on 
> your
> G5?), which I assume is to write the active workspace's data to the 
> file.
> If it takes this moment, you're OK.  But once in a while, OW exits very
> quickly.  On the next launch, all of the windows in that workspace 
> will be
> gone!

The next time OmniWeb quits very quickly and you suspect it lost its 
workspace, could you make a copy of it for me before you next launch 
the app?  (Then, of course, please launch to confirm that it's gone.)  
If I could see one of these emptied workspace files, that might help me 
track down the problem.  (I could see whether the file is completely 
truncated, or if it's just missing the information about the windows, 
or whatever.)

It sounds like the workspace's snapshot also disappears?

(This seems very odd, because we shouldn't be touching the existing 
workspace file until we've collected all of the new workspace's archive 
data, compressed it, and written it to a new file.  At that point we 
rename the old file, replacing it with the new file, then remove the 
old file.  So it sounds like the new file is somehow not written with 
the proper archive data, so I'm wondering what data it _does_ have in 
it.)

> Based on that, I would suggest looking for possible points of failure 
> early in the workspace file writing process triggered by a Quit.

I'll also do this.

> I will attempt to gather more information -- I hope what I have given 
> is
> useful.  If some logging and debugging code can be added, I would 
> gladly run
> that version.

Yes, it's especially useful to know that you can predict when it's 
going to happen.  I'll let you know if we create a special debugging 
build.

				Thanks!
				Ken