Windows VM crashes on GitHub Actions running on `windows-2022`/`windows-latest`

[j4yk]

Hi,

Seems like the Windows VMs are crashing during a Smalltalk CI run recently:

• https://github.com/hpi-swa/Squot/runs/5522586506?check_suite_focus=true
• https://github.com/hpi-swa/Squot/runs/5526922611?check_suite_focus=true

Extracting virtual machine...
Archive:  /c/Users/runneradmin/.smalltalkCI/_cache/squeak.cog.spur_win64x64_202101260417.zip
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/B3DAcceleratorPlugin.dll  
 extracting: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/CameraPlugin.ignore  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/DESPlugin.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/FileAttributesPlugin.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/MD5Plugin.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SHA2Plugin.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/Squeak.exe  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/Squeak.exe.manifest  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/Squeak3D.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SqueakConsole.exe  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SqueakConsole.exe.manifest  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SqueakFFIPrims.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SqueakSSL.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/UUIDPlugin.dll  
  inflating: /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/Win32OSProcessPlugin.dll  
Cog VM Information
Win32 built on Jan 26 2021 04:41:38 Compiler: 4.2.1 Compatible Clang 8.0.1 (tags/RELEASE_801/final) [Production Spur 64-bit VM]
CoInterpreter VMMaker.oscog-eem.2940 uuid: 29171f50-756f-4560-8488-ced65f2d4841 Jan 26 2021
StackToRegisterMappingCogit VMMaker.oscog-eem.2940 uuid: 29171f50-756f-4560-8488-ced65f2d4841 Jan 26 2021
VM: 202101260417 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Date: Mon Jan 25 20:17:24 2021 CommitHash: 010c20e
Plugins: 202101260417 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
 > Time to run: 0.331s
Preparing Squeak64-trunk image for CI...
................................................................................................................... > Time to run: 574.578s
/c/Users/runneradmin/.smalltalkCI/_builds/vm: line 1:   787 Segmentation fault      /c/Users/runneradmin/.smalltalkCI/_cache/vms/Squeak64-trunk/SqueakConsole.exe "$@"

Error with status code 139:
653 travis_wait /c/Users/runneradmin/.smalltalkCI/helpers.sh
Error: Process completed with exit code 1.

A build from 4 days ago went fine, but from the next one, at this time 18 hours ago, all the Windows builds got the segmentation fault.

GitHub Actions switched to Windows 2022 but I do not know whether that is related or not.

Maybe a newer version of the VM must be used by Smalltalk CI? If that does not help, I guess an issue in https://github.com/OpenSmalltalk/opensmalltalk-vm/ would be in order. Since this is a Squeak-trunk build, a recent change in the Squeak trunk might also be the trigger for the crash.

Kind regards, Jakob

[fniephaus]

Not sure what's going on here. We can certainly update the VMs if we are certain that this fixes things. Maybe @marceltaeumel or @LinqLover know more about this?

[LinqLover]

This could be related to my observation that it is not possible to snapshot & reopen some images for a few days: https://lists.squeakfoundation.org/pipermail/squeak-dev/2022-March/219479.html

[marceltaeumel]

GitHub Actions switched to Windows 2022 but I do not know whether that is related or not.

Please pin to windows-2019 instead of windows-latest. We did this for OSVM as well. I cannot yet report on what changed in the new build environment.

This could be related to my observation that it is not possible to snapshot & reopen some images for a few days

Very unlikely since all other platforms seem to work fine. :-)

[j4yk]

I failed to follow-up on the windows-2019 suggestion in the Squot repository, but lately the windows-latest builds are not crashing anymore.