I _think_ that this might be how to reliably reproduce the problem: # Open up BFAV # Save and quit your image with BFAV still open # Make sure that other people submit posts to BFAV # Open up your image # Load updates.
Thanks for the troubleshooting!
At this point latest.zip can't be deleted and an exception gets raised. Now if I close BFAV and save & quit the image, delete latest.zip (*) and then restart the image & re-open BFAV, the problem disappears.
(*) I'm not certain this step is necessary.
Would you try it without that step, and see if the problem still goes away? Also, what platform are you running Squeak on, primarily?
Thanks, Brent
"Brent Vukmer" 02/25/04 14:28 >>>
At this point latest.zip can't be deleted and an exception gets raised. Now if I close BFAV and save & quit the image, delete latest.zip (*) and then restart the image & re-open BFAV, the problem disappears.
(*) I'm not certain this step is necessary.
Would you try it without that step, and see if the problem still goes away? Also, what platform are you running Squeak on, primarily?
Sure, as soon as it happens again. I'm running on Win32 here at work, and FreeBSD at home. IIRC, the same sort've thing happens at home, but it's been a while now since I got the message at home so it may or may not behave the same.
frank
latest.zip can't be deleted and an exception gets raised.
I suffered this too, but I've another problem:
When reviewing things in BFAV, I use to start with an empty image and save different versions ("save as..." or "save as new version...") while I review, install and test different enhancements.
The problem is that if I "load updates" in BFAV in one image, and then try the same in another, the second image says that "there are no new posts". It seems as if the list of loaded BFAV items is maintained outside the image, and since I have different images in the same directory, the first image I updated receives the new posts, while the others think that their are OK as they are, which is of course false.
It happened to someone else? ideas?
Thanks in advance,
German Morales
Me:
At this point latest.zip can't be deleted and an exception gets raised. Now if I close BFAV and save & quit the image, delete latest.zip (*) and then restart the image & re-open BFAV, the problem disappears.
(*) I'm not certain this step is necessary.
Brent:
Would you try it without that step, and see if the problem still goes away? Also, what platform are you running Squeak on, primarily?
Without deleting latest.zip the problem disappears. I suspect Goran's suggestion of a FileStream hanging around is correct?
Does BFAV keep a FileStream open for its entire life, or just for the processes involving reading/writing? I mean, when you hit load updates, does BFAV then open a FileStream on latest.zip and then clean up that FileStream after?
frank
Typically what happens to cause this is a filestream gets left open and is awaiting execution by the registry. A garbage collect will detect the weak oop and cause the executor to run, closing the file and releasing the FILE pointer in the VM. Then you can delete the file.
Most likely the answer is a simple code change to make sure the file is closed explicitly.
tim
squeak-dev@lists.squeakfoundation.org
-
Brent Vukmer -
Frank Shearar -
German Morales -
tim Rowledge