-
-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pharo images can crash after sleep of OSX #2422
Comments
I've attached the crash.dmp file in case that helps (had to add .log suffix to upload it) |
I just got another crash exactly the same 5 hours later on the same image (unsaved from before - and download on Friday 8/feb - 64bit osx using zero conf). I had started the image for a few hours and was looking at some code - i did get a walkback from another bug (saving a method and using the autocorrect of a class name gives an error). I then closed my laptop for lunch. An hour later it was being used but I was in mail when Pharo crashed in the background. 2 other Pharo images (earlier versions) were running fine and havne't crashed even though they've been running for days. The console output is similar but shows 2 "cant allocate region securely" msgs (the last 2 times there were just 1). Tim [ :each | self visitNode: each ] in OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitMessageNode: in Block: [ :each | self visitNode: each ] Segmentation fault Tue Feb 12 17:31:59 2019 VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git C stack backtrace & registers: Smalltalk stack dump: Most recent primitives
<
primSignal:atUTCMicroseconds:
< stack page bytes 4096 available headroom 2788 minimum unused headroom 2328
./pharo-ui: line 11: 67603 Abort trap: 6 "$DIR"/"pharo-vm/Pharo.app/Contents/MacOS/Pharo" "$@" |
Interestingly - that same image that was crashing, when saved to pharo.1.image doesn't seem to crash everyday like before? This echo's a problem I had with corrupted fonts in a fresh image - saving the image seemed to fix it - so maybe the build process is doing something weird? |
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. It will be closed in 1 month if no further activity occurs. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
|
I haven’t noticed this recently - using later vm’s to when this was reported, however I have got in the habit of saving my image as per above , so it really needs testing again in a fresh 8 image, left unsaved for 24 hours. I’ll do that |
It still happens to me. |
I haven't noticed it in a P8 launched from pharo launcher this morning - however i notice in my original report it was zero conf images loaded from the terminal - wonder if that makes the difference? |
I got crashes from time to time and I use the launcher. |
Just so we leave a clear message thread - are these crashes when you were doing something or just when the image was sitting ie unused? (In my reported cases with seg traces - the image was not being used, but not sure if that’s relevant). As mentioned, when I started saving images it seemed to help (not sure if save caused some cleanup like with corrupted fonts) |
It happen as I explained in my first message. |
So it sounds similar to what I’ve seen before too. But I’m getting it less now, but sounds like it’s still a bug, but without an obvious repro case |
I've moved the issue to pharo-project/pharo-vm#72 |
It happens to me a lot when I launch my computer that was in sleep mode that a Pharo image crashes on OSX.
This is really annoying because I lose some code and on top of that I don't know which image it was.
The text was updated successfully, but these errors were encountered: