search

pharo-project / pharo

Pharo is a dynamic reflective pure object-oriented language supporting live programming inspired by Smalltalk.
http://pharo.org
Other
1.22k stars 358 forks source link

Pharo 8 (stable) opens unresponsive image #5575

Closed LizaChambi closed 3 years ago

LizaChambi commented 4 years ago

Hello, I have an issue with a Pharo 8 (stable) image this morning. I saved&quit that image yesterday, I didn't change the image name. Now it opens blank (no background nor menues) and it accepts no imput from mouse or keyboard. I started with PharoLauncher. Image: Pharo8.0.0 [Build information: Pharo-8.0.0+build.1122.sha.bbcdf9770748d12e2c1b84f168f0232e4f918d20 (64 Bit)] . I also tried running the image from the terminal (linux) and It reports no errors or warnings. The windows was unresponsive and the only way to close it was by means of "kill -9..." .

Screenshot from 2020-01-24 09-59-52

welcome[bot] commented 4 years ago

Thanks for opening your first issue! Please check the CONTRIBUTING documents for some tips about which information should be provided. You can find information of how to do a Pull Request here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo

GitHub
pharo-project/pharo
Pharo is a dynamic reflective pure object-oriented language supporting live programming inspired by Smalltalk. - pharo-project/pharo
astares commented 4 years ago

Can you please retry by download a fresh Pharo 8 image using Launcher and tell us if it works or if you have a reproducible case? Thanks!

Ducasse commented 4 years ago

+1 I imagine that liza is following our lecture (so we will see if we get an answer before next friday).

LizaChambi commented 4 years ago

I downloaded a new image of Pharo 8 (stable) with Launcher that same day and it worked fine, then I installed PetitParser2 and GToolkit with Metacello to work with them, but soon after, as I was writing, the image suddenly closed. Now when I try to open the image with Launcher, it closes immediately and with the terminal it only says 'Aborted (core dumped)' I have generated a crash.dmp file, I attach them as .txt. crash.txt .

Ducasse commented 4 years ago

Can you tell us exactly how you installed PetitParser2 ?

Ducasse commented 4 years ago

Because it should not be loaded via monticello.

LizaChambi commented 4 years ago

I downloaded PetitParser2 with a guide from https://github.com/kursjan/petitparser2.

Metacello new baseline: 'PetitParser2'; repository: 'github://kursjan/petitparser2'; load.

Metacello new baseline: 'PetitParser2Gui'; repository: 'github://kursjan/petitparser2'; load.

GitHub
kursjan/petitparser2
A high-performance top-down parser. Contribute to kursjan/petitparser2 development by creating an account on GitHub.
Ducasse commented 4 years ago

Thanks! We saw that some other people have the same problem and we cannot reproduce it. I tried with Pharo 80, 70 and it worked. :(

Ducasse commented 4 years ago

Pablo I tried to reproduce it because serge reported this problem with kendrick and I could not. Now I will retry with the latest stable VM.

Alisu commented 4 years ago

You gave the metacello scripts for PetitParser2 but can you also give the one you used for GToolkit please ? Oh and also the version of your OS ?

It seems this happens during the GC and may be a vm problem. You should try the new VM.

LizaChambi commented 4 years ago

I use Ubuntu 19.10, and downloaded GToolkit from https://github.com/feenkcom/gtoolkit:

EpMonitor current disable. [ Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load ] ensure: [ EpMonitor current enable ].

GtWorld asClass open.

This week I used the Image: Pharo8.0.0 [Build information: Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 Bit)] with PetitParser2, and Its working fine. I recently installed GToolkit, if I have any problem I will inform them.

GitHub
feenkcom/gtoolkit
Glamorous Toolkit is the moldable development environment. - feenkcom/gtoolkit
akgrant43 commented 4 years ago

I downloaded a new image of Pharo 8 (stable) with Launcher that same day and it worked fine, then I installed PetitParser2 and GToolkit with Metacello to work with them, but soon after, as I was writing, the image suddenly closed. Now when I try to open the image with Launcher, it closes immediately and with the terminal it only says 'Aborted (core dumped)' I have generated a crash.dmp file, I attach them as .txt. crash.txt .

This looks more like a known GC issue in the VM than a PP2 or Gtoolkit issue.

There's a new VM available, see http://forum.world.st/New-Latest-VM-Please-Test-td5110167.html (it has issues with earlier versions of Ubuntu, but if you're on 19.04 you should be OK)

Pharo Smalltalk Developers - New Latest VM - Please Test
New Latest VM - Please Test. Hello, I have just uploaded a new version of the VM as the latest. This version is the one to be intended for Pharo 8 release. Please feel free to test...
LizaChambi commented 4 years ago

Today the Image: Pharo8.0.0 [Build information: Pharo-8.0.0+build.1124.sha.0932da82f08175e906b0e2a8052120c823374e9f (64 Bit)] suddenly closed while working. When I try to open the image with Launcher, it closes immediately, and from terminal report an Error: 'Segmentation fault'. I didn't use the new VM, but I will use it now.

MarcusDenker commented 3 years ago

Can we close this issue?

LizaChambi commented 3 years ago

Yes, they can close it.

El vie, 23 de jul. de 2021 a la(s) 09:36, Marcus Denker ( @.***) escribió:

Can we close this issue?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pharo-project/pharo/issues/5575#issuecomment-885607779, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCBMPDVJBXL57RDSPHAWYTTZFO4VANCNFSM4KLJYVSQ .