Hi Tim --

> The problem here is image file bloating

I know. Is this a problem? I assume that the user can spare those extra megs on disk while working. Yet, it is annoying to get a stuttering system after snapshotting, which might even encourage people to not save that often.

>  It should start ok but might be a problem for server cases where startup time is important?

Which server images save on a regular basis? :-D You can always call "Form shutdown: true" and "TTCFont shutdown: true" in your server scripts directly before snapshotting ... I assume that servers have such scripts anyway and those two extra lines wouldn't hurt...

Best,
Marcel
Am 14.02.2022 18:29:21 schrieb tim Rowledge <tim at rowledge.org>:


> On 2022-02-14, at 8:43 AM, Marcel Taeumel wrote:
>
> Hi all --
>
> Please report whether I am overlooking something here... It was kind of annoying that my entire TrueType cache was gone after just saving the image and keep on working.

The problem here is image file bloating; the hibernation is intended to save (quite a bit of) space in the image file. If we only hibernate when save&quitting then we will see patterns in the snapshot file size like

100mb
112mb
121mb
(quit) 101mb

.. which maybe wouldn't bother anyone, maybe would annoy some?

Also, a few save-no-quits followed by a damn-I-broke-it-quit-no-save would lave the large file as the one you have to start up. It should start ok but might be a problem for server cases where startup time is important?

High-tech-insane solution - use DTL's spawn-an-image and have that image do the hibernate & save! Couldn't possibly go wrong...


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: CM: Circulate Memory



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220216/b4a43fd9/attachment.html>