Manuscript (Case [Issue]22902) Iceberg (Git) - Pharo quits (no message) Windows 10 with Moose 64-bit image after Commit in Iceberg

Classic

List

Threaded

♦

♦

Locked 1 message

Pharo Issue Tracker

Reply | Threaded

Open this post in threaded view

♦

♦

|

Manuscript (Case [Issue]22902) Iceberg (Git) - Pharo quits (no message) Windows 10 with Moose 64-bit image after Commit in Iceberg

Cris Fuhrman opened Case 22902: Pharo quits (no message) Windows 10 with Moose 64-bit image after Commit in Iceberg and assigned it to Esteban Lorenzano: Bug in  Iceberg (Git): Misc  •  You are subscribed to this case Using a Dell laptop I have at home, I used Pharo Launcher to copy an image from Moose Jenkins > moose-7.0-64bit > Latest sucessful build: #10 > moose-7.0-64bit.zip I add (load) a local clone of my fuhrmanator/GitMiner project (check out the baseline-creation branch) on GitHub, make a modification to any file in my BaselineOfGitMiner package, then try to commit it. I expect the commit to complete. What I see is the progress GUI windows for Iceberg trying to commit, then the entire Pharo environment window closes with no error messages (not even a crash message). Crashes in Windows before have given me at least a dialog saying the VM crashed. But in this case, it's as if the Windows 10 process was killed. Loading up the same image, there's no trace of any changes, etc. Below is the info from System Reporter (I only checked the the Image and VM General options). If more info is needed it's easy for me to reproduce. ----- Image ----- C:\Users\Ming\Documents\Pharo\images\moose-7.0-64bit\moose-7.0-64bit.image Pharo7.0.0rc1 Build information: Pharo-7.0.0+rc1.build.51.sha.c57d949c51324aa9cc311c01708088b10e5d4cfc (64 Bit) Unnamed Virtual Machine --------------- C:\Users\Ming\Documents\Pharo\vms\70-x64\Pharo.exe CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Win32 built on Jan 5 2019 20:24:52 GMT Compiler: 4.2.1 Compatible Clang 5.0.1 (tags/RELEASE_501/final) VMMaker versionString VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 Priority: 5 – Fix If Time Status: Work Needed Assigned to: Esteban Lorenzano Milestone: Later Go to Case No longer need updates? Unsubscribe from this case. Don't want Manuscript notifications anymore? Update your preferences. A Manuscript case was opened by Cris Fuhrman. Case ID: 22902 Title: Pharo quits (no message) Windows 10 with Moose 64-bit image after Commit in Iceberg Status: Work Needed Category: Bug Project: Iceberg (Git) Area: Misc Priority: 5 - Fix If Time Milestone: Later Assigned To: Esteban Lorenzano URL: https://pharo.manuscript.com/f/cases/22902 Using a Dell laptop I have at home, I used Pharo Launcher to copy an image from Moose Jenkins > moose-7.0-64bit > Latest sucessful build: #10 > moose-7.0-64bit.zip I add (load) a local clone of my fuhrmanator/GitMiner project (check out the baseline-creation branch) on GitHub, make a modification to any file in my BaselineOfGitMiner package, then try to commit it. I expect the commit to complete. What I see is the progress GUI windows for Iceberg trying to commit, then the entire Pharo environment window closes with no error messages (not even a crash message). Crashes in Windows before have given me at least a dialog saying the VM crashed. But in this case, it's as if the Windows 10 process was killed. Loading up the same image, there's no trace of any changes, etc. Below is the info from System Reporter (I only checked the the Image and VM General options). If more info is needed it's easy for me to reproduce. ----- Image ----- C:\Users\Ming\Documents\Pharo\images\moose-7.0-64bit\moose-7.0-64bit.image Pharo7.0.0rc1 Build information: Pharo-7.0.0+rc1.build.51.sha.c57d949c51324aa9cc311c01708088b10e5d4cfc (64 Bit) Unnamed Virtual Machine --------------- C:\Users\Ming\Documents\Pharo\vms\70-x64\Pharo.exe CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Win32 built on Jan 5 2019 20:24:52 GMT Compiler: 4.2.1 Compatible Clang 5.0.1 (tags/RELEASE_501/final) VMMaker versionString VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 5 2019 You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=22902) from this case. _______________________________________________ Pharo-bugtracker mailing list [hidden email] https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker