opensmalltalk-vm icon indicating copy to clipboard operation
opensmalltalk-vm copied to clipboard
verified publisher icon OpenSmalltalk

Crash in 202312181441 when resizing Squeak window

Open bpieber opened this issue 5 months ago • 5 comments

I am on macOS Monterey Version 12.7.6 (21H1320) on an Intel Mac mini. The stable Squeak VM (https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/download/202312181441/squeak.cog.spur_macos64x64.dmg) just crashed when I resized the Squeak window to make it smaller.

I have a large external display: DELL U3224KBA 31,5-Zoll (6720 × 3780)

Here is the crash.dmp: crash.dmp

Cheers, Bernhard

bpieber avatar Jun 21 '25 16:06 bpieber

Does this happen with the latest VM build too?

https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/latest-build

codefrau avatar Jun 21 '25 16:06 codefrau

I am afraid I was not able to reproduce it yet. It only happened once so far.

Sorry, I wrote stable. I was using the release tagged latest from December 2023. Your link is to a version from July 2021. Did you mean this?

I forgot to mention it happened in an old image:

Image: /Users/bernhard/Entwicklung/Squeak/bp-squeak/bp-squeak.image Squeak6.0alpha latest update: #21313 Current Change Set: Mona Image format 68021 (64 bit) Preferred bytecode set: SistaV1

Is my assumption correct, that the latest VM should be able to run such an old image?

Interestingly, a new trunk image has a different image format: Image format 68533 (64 bit)

This should not be the reason, right?

bpieber avatar Jun 22 '25 09:06 bpieber

Your link is to a version from July 2021. Did you mean this?

squeak.cog.spur_macos64x64.dmg in the folder I linked to was built yesterday

codefrau avatar Jun 22 '25 10:06 codefrau

Ah, now I get it. I got confused because on https://squeak.org/downloads/ the link OpenSmalltalk VMs (stable) links to a release labelled Latest and OpenSmalltalk VMs (stable) links to a release which says "github-actions released this Jul 30, 2021" on top.

So I was using the stable VM and not the latest. I will use the the latest VM going forward and see if this happens again.

Should I even have reported the crash given it happened in the stable VM and not in the latest?

Thanks for your support, Vanessa!

bpieber avatar Jun 22 '25 10:06 bpieber

I fixed the (or a?) regression. But we still need an extra check for low-dpi images to avoid flickering in some situations.

See ab70a416c52b041299c62f41dad271c871feb6b5

marceltaeumel avatar Nov 01 '25 15:11 marceltaeumel