- Pharo-dev - lists.pharo.org

Re: Pharo 8 Image blows up after restart

by Sabine Manaa

Hi Eliot, hi Guille, you saved my day! starting from command line and killing with SIGUSR1 showed the stack below. Starting the image without mongoservice running avoids the blowup. Then, saving the image, starting mongoservice again and then I can proceed using the image. I don't know yet why I get the MongoWireProtocolError(MongoNativeError)>messageText but I have a point where I can start seaching. Thanks a lot Sabine SIGUSR1 Wed Dec 9 09:51:45 2020 VM: 202002121007 https://github.com/pharo-project/opensmalltalk-vm.git Date: Wed Feb 12 11:07:12 2020 CommitHash: 2bd9e39 Plugins: 202002121007 https://github.com/pharo-project/opensmalltalk-vm.git C stack backtrace & registers: rax 0x00000001107d28f0 rbx 0x0000000000000003 rcx 0x0000000000000000 rdx 0x0000000000000008 rdi 0x00000003351a4690 rsi 0x00000003351a4690 rbp 0x00007ffeea61f050 rsp 0x00007ffeea61f020 r8 0x00ffffffffffffff r9 0x0000000000000001 r10 0x00000003351a4698 r11 0x000000022b0c8fc8 r12 0x00000003351a45d8 r13 0x0000000000000001 r14 0x0000000000000000 r15 0x0000000000000006 rip 0x00000001055f9862 0 Pharo 0x00000001055f9862 scavengeReferentsOf + 277 1 Pharo 0x00000001056392da reportStackState + 952 2 Pharo 0x00000001056394f8 sigusr1 + 182 3 libsystem_platform.dylib 0x00007fff725995fd _sigtramp + 29 4 ??? 0x00000000c0000000 0x0 + 3221225472 5 Pharo 0x00000001055d5eea doScavenge + 542 6 Pharo 0x00000001055de05e scavengingGCTenuringIf + 333 7 Pharo 0x00000001055c163a checkForEventsMayContextSwitch + 111 8 Pharo 0x00000001055c5815 ceStackOverflow + 110 9 ??? 0x0000000109cca53b 0x0 + 4459373883 10 Pharo 0x00000001055adb0a interpret + 632 11 Pharo 0x000000010563aa62 -[sqSqueakMainApplication runSqueak] + 393 12 Foundation 0x00007fff3aac429b __NSFirePerformWithOrder + 360 13 CoreFoundation 0x00007fff38330335 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 14 CoreFoundation 0x00007fff38330267 __CFRunLoopDoObservers + 457 15 CoreFoundation 0x00007fff3832f805 __CFRunLoopRun + 874 16 CoreFoundation 0x00007fff3832ee3e CFRunLoopRunSpecific + 462 17 HIToolbox 0x00007fff36f5babd RunCurrentEventLoopInMode + 292 18 HIToolbox 0x00007fff36f5b6f4 ReceiveNextEventCommon + 359 19 HIToolbox 0x00007fff36f5b579 _BlockUntilNextEventMatchingListInModeWithFilter + 64 20 AppKit 0x00007fff355a1039 _DPSNextEvent + 883 21 AppKit 0x00007fff3559f880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352 22 AppKit 0x00007fff3559158e -[NSApplication run] + 658 23 AppKit 0x00007fff35563396 NSApplicationMain + 777 24 libdyld.dylib 0x00007fff723a0cc9 start + 1 25 ??? 0x0000000000000002 0x0 + 2 All Smalltalk process stacks (active first): Process 0x120172de8 priority 20 0x7ffeea630130 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63d980 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63d9b0 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63d9e0 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63da10 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63da40 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63da70 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63daa0 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dad0 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63db00 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63db30 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63db60 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63db90 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dbc0 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dbf0 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dc20 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dc50 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dc80 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dcb0 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dce0 M MongoWireProtocolError>errorMessage 0x120173f58: a(n) MongoWireProtocolError 0x7ffeea63dd10 M MongoWireProtocolError(MongoNativeError)>messageText 0x120173f58: a(n) MongoWireProtocolError (repeat 100.000 times).... 0x1196a9fa8 s MongoWireProtocolError(MongoNativeError)>messageText 0x1196aa060 s MongoWireProtocolError>errorMessage 0x1196aa118 s MongoWireProtocolError(MongoNativeError)>messageText 0x1196aa1d0 s MongoWireProtocolError>errorMessage 0x1196aa288 s MongoWireProtocolError(MongoNativeError)>messageText 0x1196aa340 s [] in MongoWireProtocolError(Exception)>description 0x1196aa3f8 s String class(SequenceableCollection class)>new:streamContents: 0x1196aa4b0 s String class(SequenceableCollection class)>streamContents: 0x1196aa568 s MongoWireProtocolError(Exception)>description 0x1196aa620 s MongoWireProtocolError(Exception)>debug 0x1196aa6d8 s MorphicUIManager>unhandledErrorDefaultAction: 0x1196aa790 s UnhandledError>defaultAction 0x1196aa848 s UndefinedObject>handleSignal: 0x1196aa900 s Context>handleSignal: 0x1196aa9b8 s UnhandledError(Exception)>signal 0x1196aaa70 s UnhandledError class>signalForException: 0x1196aab28 s MongoWireProtocolError(Error)>defaultAction 0x1196aabe0 s UndefinedObject>handleSignal: 0x1196aac98 s Context>handleSignal: 0x119b91af8 s MongoWireProtocolError(Exception)>signal 0x119b91d20 s MongoWireProtocolError(Exception)>signal: 0x119b91f48 s MongoWireProtocolError class(Exception class)>signal: 0x119b91988 s MongoCursor>execute 0x119b91c68 s Mongo>queryOne: 0x119b91e90 s Mongo>command:database:flags: 0x119b920b8 s Mongo>command:database: 0x119b92228 s [] in SCRAMSHA1AuthMechanism>authenticateUsername:password:forcedDatabase: 0x119b91a40 s BlockClosure>on:do: 0x120221980 s SCRAMSHA1AuthMechanism>authenticateUsername:password:forcedDatabase: 0x120221c48 s SCRAMSHA1AuthMechanism(MongoAuthMechanism)>authenticateUsername:password:database: 0x120222010 s Mongo>authenticateUsername:password:database: 0x120222300 s RKARepositoryManager class>authenticateAdminRepository 0x120223688 s RKARepositoryManager class>databaseNames 0x120223988 s RKARepositoryManager class>customerDatabaseNames 0x120223be8 s RKAMailSender class>sendReminderMails 0x120223d88 s [] in RKAScheduler class>newReminderMailsScheduler 0x12043fac0 s [] in ScheduledTask>run 0x120442d98 s BlockClosure>ensure: 0x120445d90 s [] in ScheduledTask>run 0x120448eb0 s [] in BlockClosure>newProcess processes at priority 10 Process 0x1191f2220 priority 10 0x1201735e8 s ProcessorScheduler class>idleProcess 0x1201879e8 s [] in ProcessorScheduler class>startUp 0x1191f7d80 s [] in BlockClosure>newProcess Process 0x119f75ed0 priority 10 0x12eaa4228 s [] in BlockClosure>newProcess Process 0x181024e98 priority 10 0x1810253c8 s [] in BlockClosure>newProcess Process 0x1d5a8e568 priority 10 0x1d5a8f020 s [] in BlockClosure>newProcess Process 0x17eaa3c78 priority 10 0x1f23c8698 s [] in BlockClosure>newProcess Process 0x2111a5f20 priority 10 0x2111a6320 s [] in BlockClosure>newProcess Process 0x2590f8cd8 priority 10 0x2590faa98 s [] in BlockClosure>newProcess Process 0x279aadfa0 priority 10 0x27ac91450 s [] in BlockClosure>newProcess Process 0x2b6261ee0 priority 10 0x2b62624f0 s [] in BlockClosure>newProcess Process 0x2de054360 priority 10 0x2de0549b0 s [] in BlockClosure>newProcess Process 0x29eb28580 priority 10 0x2fcdffb28 s [] in BlockClosure>newProcess Process 0x31b7dfa68 priority 10 0x31b7e05d0 s [] in BlockClosure>newProcess suspended processes Process 0x1191f2cb0 priority 50 0x1191f8af0 s WeakArray class>finalizationProcess 0x120173ea0 s [] in WeakArray class>restartFinalizationProcess 0x119ed8b78 s [] in BlockClosure>newProcess Process 0x10cd52ed0 priority 80 0x109f28000 s DelayMicrosecondTicker>waitForUserSignalled:orExpired: 0x10da04408 s [] in DelaySemaphoreScheduler(DelayBasicScheduler)>runBackendLoopAtTimingPriority 0x10da04620 s BlockClosure>ensure: 0x10ce7e868 s DelaySemaphoreScheduler(DelayBasicScheduler)>runBackendLoopAtTimingPriority 0x10da04350 s [] in DelaySemaphoreScheduler(DelayBasicScheduler)>startTimerEventLoopPriority: 0x10ce7e940 s [] in BlockClosure>newProcess Process 0x1121775c0 priority 31 0x118db5a88 s AtomicSharedQueue>waitForNewItems 0x118e51048 s AtomicSharedQueue>next 0x119196820 s [] in ClyDataSourceUpdateScheduler>processQueue 0x112187878 s BlockClosure>repeat 0x11217e940 s ClyDataSourceUpdateScheduler>processQueue 0x1121877c0 s [] in ClyDataSourceUpdateScheduler>ensureRunning 0x11217ea18 s [] in BlockClosure>newProcess Process 0x1191f21d0 priority 60 0x1191f7cc8 s SmalltalkImage>lowSpaceWatcher 0x120173d30 s [] in SmalltalkImage>installLowSpaceWatcher 0x119ed8100 s [] in BlockClosure>newProcess Process 0x1191f2998 priority 40 0x326d25100 s [] in DelayWaitTimeout>wait 0x327434bf0 s BlockClosure>ensure: 0x326d258b8 s DelayWaitTimeout>wait 0x327435268 s Semaphore>waitTimeoutMSecs: 0x3274355e0 s [] in UnixOSProcessAccessor>grimReaperProcess 0x120204400 s BlockClosure>repeat 0x119ed8cb0 s [] in UnixOSProcessAccessor>grimReaperProcess 0x119ed8d98 s [] in BlockClosure>newProcess Process 0x1191f3120 priority 60 0x1408b30d0 s InputEventFetcher>waitForInput 0x120174528 s InputEventFetcher>eventLoop 0x12018b9e8 s [] in InputEventFetcher>installEventLoop 0x119ed8a50 s [] in BlockClosure>newProcess Process 0x1191f3030 priority 70 0x1191f9070 s [] in DelayWaitTimeout>wait 0x120173998 s BlockClosure>ensure: 0x119e57648 s DelayWaitTimeout>wait 0x120173a50 s Semaphore>waitTimeoutMSecs: 0x12018adb0 s Socket>waitForConnectionFor:ifTimedOut: 0x119ed84b8 s Socket>waitForAcceptFor:ifTimedOut: 0x119ed8590 s Socket>waitForAcceptFor: 0x120173b08 s ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>serveConnectionsOn: 0x12018ae68 s [] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>listenLoop 0x12019a808 s BlockClosure>repeat 0x119ed8668 s [] in ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>listenLoop 0x120173bc0 s BlockClosure>ifCurtailed: 0x119ed8760 s ZnManagingMultiThreadedServer(ZnMultiThreadedServer)>listenLoop 0x120173c78 s [] in ZnManagingMultiThreadedServer(ZnSingleThreadedServer)>start 0x12018af20 s BlockClosure>repeat 0x119ed8838 s [] in ZnManagingMultiThreadedServer(ZnSingleThreadedServer)>start 0x119ed8910 s [] in BlockClosure>newProcess Process 0x1191f27c8 priority 70 0x109f280b8 s [] in Delay>wait 0x109f2cbc8 s BlockClosure>ifCurtailed: 0x109f2cf40 s Delay>wait 0x109f2d260 s [] in OSSVMProcess>initializeChildWatcher 0x12021cd08 s BlockClosure>repeat 0x119ed82b8 s [] in OSSVMProcess>initializeChildWatcher 0x119ed8398 s [] in BlockClosure>newProcess Most recent primitives **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** **StackOverflow** stack page bytes 4096 available headroom 1480 minimum unused headroom 848 (SIGUSR1) bash: line 1: 29529 Terminated: 15 "/Users/sabine/Documents/Pharo/vms/80-x64/Pharo.app/Contents/MacOS/Pharo" "/Users/sabine/Documents/Pharo/images/Pharo 8.0 - 64bit (15)/Pharo 8.0 - 64bit (15).image" Sabines-MBP:~ sabine$ . -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 9, 2020

Re: Pharo 8 Image blows up after restart

by Guillermo Polito

Another idea is that as soon as you detect the problem, you send the SIGUSR1 signal to the VM from another terminal. $ kill -SIGUSR1 thePID When the Pharo process receives the SIGUSR1 signal it will output a dump with - the C execution stack - the Pharo execution stacks Maybe for debugging this case you donât want to use the launcher, and you want to manually launch the VM from a terminal, so youâll have more control and see the output (maybe youâre already doing it, but just in case). G. > El 9 dic 2020, a las 6:35, Eliot Miranda <eliot.miranda(a)gmail.com> escribiÃ³: > > Hi Sabine, > >> On Dec 8, 2020, at 10:49 AM, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: >> >> ï»¿Hi, >> >> I have the following problem: >> >> sometimes, after restarting my Pharo 8 image on mac, it is not responsive >> and it blows up the memory. >> >> I tried with commandline handler >> eval "self halt" >> and with >> Smalltalk addToStartUpList: >> >> but both is too late - the Image starts and blows up and is not responsive. >> >> I can not interrupt it and it grows to several GB memory (eg after 20 >> seconds 10 GigaByte! ) and I have to kill it. >> >> Anyone having an idea what I can do to find the reason for this? > > Run the system under a low level debugger (lldb, gdb). > Put a break point on the function sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto, which is called when the heap must grow to allocate new objects. > When the system hits the breakpoint for the second or third time call the function > printCallStack() > and be patient; it will print a lot of stack. > > There is also a command line argument to limit the maximum size of the heap. So an alternative might be to restrict the heap to a few megabytes above the image size and see if you get a crash.dmp file when the vm exits when the system runs out of memory. > > HTH > >> >> Sabine >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html <http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html>

Dec. 9, 2020

Re: Pharo 8 Image blows up after restart

by Eliot Miranda

Hi Sabine, > On Dec 8, 2020, at 10:49 AM, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > ï»¿Hi, > > I have the following problem: > > sometimes, after restarting my Pharo 8 image on mac, it is not responsive > and it blows up the memory. > > I tried with commandline handler > eval "self halt" > and with > Smalltalk addToStartUpList: > > but both is too late - the Image starts and blows up and is not responsive. > > I can not interrupt it and it grows to several GB memory (eg after 20 > seconds 10 GigaByte! ) and I have to kill it. > > Anyone having an idea what I can do to find the reason for this? Run the system under a low level debugger (lldb, gdb). Put a break point on the function sqAllocateMemorySegmentOfSizeAboveAllocatedSizeInto, which is called when the heap must grow to allocate new objects. When the system hits the breakpoint for the second or third time call the function printCallStack() and be patient; it will print a lot of stack. There is also a command line argument to limit the maximum size of the heap. So an alternative might be to restrict the heap to a few megabytes above the image size and see if you get a crash.dmp file when the vm exits when the system runs out of memory. HTH > > Sabine > > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 9, 2020

Re: Progress Report -> Refactoring Project - (November 30 - December 4)

by Sean P. DeNigris

Sounds great! Thanks for the update :) Keep us posted... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 9, 2020

Pharo 8 Image blows up after restart

by Sabine Manaa

Hi, I have the following problem: sometimes, after restarting my Pharo 8 image on mac, it is not responsive and it blows up the memory. I tried with commandline handler eval "self halt" and with Smalltalk addToStartUpList: but both is too late - the Image starts and blows up and is not responsive. I can not interrupt it and it grows to several GB memory (eg after 20 seconds 10 GigaByte! ) and I have to kill it. Anyone having an idea what I can do to find the reason for this? Sabine -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 8, 2020

New version of FFICHeaderExtractor v1.0.2 and OSubprocess v1.3.0

by StÃ©phane Ducasse

Hi Some news since StandardFileStream got deprecated in Pharo 80, we removed it form Pharo 90. We updated - FFICHeaderExtractor now version v1.0.2 got migrated to Tonel and pharo-contributions + github actions https://github.com/pharo-contributions/OSSubprocess - OSSubprocess version v1.3.0 is out https://github.com/pharo-contributions/OSSubprocess Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Esteban Lorenzano

On Dec 7 2020, at 5:22 pm, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > > El 7 dic 2020, a las 17:02, Sean P. DeNigris <sean(a)clipperadams.com> escribiÃ³: > > > > Wow! Impressive list :) > > > > > > Marcus Denker-4 wrote > >> - Activation in single click (which triggers column expansion) is now > >> default for inspections (it was double click, but it felt weird). > > > > -1 on this. The problem with single click is that it adds a column even when > > you don't want it to. This was very annoying. IMO after using the > > double-click for a few months (it took that long to get used to it), the > > extra click is significantly less disruptive than the unnecessary column > > adding. > > > +1 on this. > That is why I made double click by default when I first implemented it. > Every time you click on glamour everything shifts, rotates, moves, it is super disrupting when you **just want to click**. > > The single click should not shuffle the UI, or the UI should provide a way to âclickâ on something without moving everything around. that's why it was double click first and is a setting now. I preferred the other way too, but people complained so I added a setting. we are still trying so we can revert the default. but there is a bug around I want to fix: default activation event is double click or enter, and that's not how it works now (easy to fix, though). Esteban

Dec. 7, 2020

Progress Report -> Refactoring Project - (November 30 - December 4)

by EVELYN CUSI LOPEZ

Hi everyone, Last week I did these tasks: - Review refactoring metamodel - Check if all tests passed and if these have sense - Refactor some tests - Add tests (https://github.com/pharo-project/pharo/pull/7965) - Do report if refactorings has or not UI command, if work or not work, if need add more tests. You can see this report in: https://github.com/Lin777/PharoRefactorings Tasks for this week: - Review commander2: http://books.pharo.org/booklet-Commander/pdf/2020-11-30-booklet-Commander20… - Review refactoring2, and compare with refactoring. Show pros and cons - Fix issues of Extract method: - https://github.com/pharo-project/pharo/issues/4429 - https://github.com/pharo-project/pharo/issues/5269 - https://github.com/pharo-project/pharo/issues/4973 - Fix issues Undo refactoring: - https://github.com/pharo-project/pharo/issues/5010 Cheers, Evelyn

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Guillermo Polito

> El 7 dic 2020, a las 17:02, Sean P. DeNigris <sean(a)clipperadams.com> escribiÃ³: > > Wow! Impressive list :) > > > Marcus Denker-4 wrote >> - Activation in single click (which triggers column expansion) is now >> default for inspections (it was double click, but it felt weird). > > -1 on this. The problem with single click is that it adds a column even when > you don't want it to. This was very annoying. IMO after using the > double-click for a few months (it took that long to get used to it), the > extra click is significantly less disruptive than the unnecessary column > adding. +1 on this. That is why I made double click by default when I first implemented it. Every time you click on glamour everything shifts, rotates, moves, it is super disrupting when you **just want to click**. The single click should not shuffle the UI, or the UI should provide a way to âclickâ on something without moving everything around. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2020

Re: This week (49/2020) on the Issue Tracker

by Sean P. DeNigris

Wow! Impressive list :) Marcus Denker-4 wrote > - Activation in single click (which triggers column expansion) is now > default for inspections (it was double click, but it felt weird). -1 on this. The problem with single click is that it adds a column even when you don't want it to. This was very annoying. IMO after using the double-click for a few months (it took that long to get used to it), the extra click is significantly less disruptive than the unnecessary column adding. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Dec. 7, 2020