Nope. Just stderr. It is continuing to happy at random times so it is obviously 
connected to page requests. I have some logging in. Place so I have increased 
that to try and help get to the point where it happens.

David

> On 16 Apr 2021, at 15:45, Davide Varvello via Pharo-users 
> <pharo-users@lists.pharo.org> wrote:
> 
> Hi David,
> Usually when the image crashes you'll find a crash.dmp file.
> It's weird there isn't anything
> Davide
> 
> 
> Long Haired David wrote
>> Sorry to but in here but I have just moved my Pharo/Seaside server
>> software from my MacBookAir, where it has run without issue for the last
>> couple of weeks, onto firstly a Lenovo desktop running Windows 2012 server
>> and then, in frustration , onto a Dell laptop but it hasn’t managed to run
>> for 24 hours without crashing (by crashing, I mean Pharo just
>> disappears!). I don’t us any OsProcess, just ordinary Seaside and
>> Smalltalk code. It has happened three days in a row at different times
>> with different pages being accessed.
>> 
>> Both Windows machines have ample disk space (SSD) and 16GB memory.
>> 
>> How do I get a dump as I can’t see any files that would be regarded as so?
>> 
>> David
>> 
>>> On 15 Apr 2021, at 14:55, Guillermo Polito &lt;
> 
>> guillermopolito@
> 
>> &gt; wrote:
>>> 
>>> Hi Davide,
>>> 
>>> Taking a look at the dump, I’d say it looks like a memory corruption.
>>> It crashes when running the GC, but very probably because the heap was
>>> already corrupt.
>>> 
>>> 
>>> 5   Pharo                               0x000000010582ea3b mapStackPages
>>> + 345
>>> 6   Pharo                               0x000000010582e0ff
>>> mapInterpreterOops + 16
>>> 7   Pharo                               0x000000010580af54 doScavenge +
>>> 648
>>> 8   Pharo                               0x000000010581305e
>>> scavengingGCTenuringIf + 333
>>> 9   Pharo                               0x00000001057f663a
>>> checkForEventsMayContextSwitch + 111
>>> 10  Pharo                               0x00000001057fa815
>>> ceStackOverflow + 110
>>> 11  ???                                 0x000000010b25c62b 0x0 +
>>> 4481992235
>>> 12  Pharo                               0x00000001057e2b0a interpret +
>>> 632
>>> 
>>> Does this happen often in your setup?
>>> 
>>> G
>>> 
>>> 
>>>> El 14 abr 2021, a las 10:21, Davide Varvello via Pharo-users &lt;
> 
>> pharo-users@.pharo
> 
>> &lt;mailto:
> 
>> pharo-users@.pharo
> 
>> &gt;> escribió:
>>>> 
>>>> Hi Sven,
>>>> It has not happened today. I also use a lot of OsProcess, but I don't
>>>> know
>>>> if it is related to it.
>>>> Cheers
>>>> Davide
>>>> 
>>>> 
>>>> 
>>>> Sven Van Caekenberghe-2 wrote
>>>>> I can't see anything networking, HTTP or Zinc related in the dump.
>>>>> It looks like something went wrong during garbage collection.
>>>>> I suppose this is not a repeatable case, is it ?
>>>>> 
>>>>>> On 14 Apr 2021, at 09:22, Davide Varvello via Pharo-users &lt;
>>>> 
>>>>> pharo-users@.pharo
>>>> 
>>>>> &gt; wrote:
>>>>>> 
>>>>>> Hi guys,
>>>>>> I'm working on Pharo 8 on BigSur 
>>>>>> (Pharo 8.0.0 Build information:
>>>>>> Pharo-8.0.0+build.1128.sha.9f6475d88dda7d83acdeeda794df35d304cf620d
>>>>>> (64
>>>>>> Bit))
>>>>>> 
>>>>>> Yesterday after an http call to my zinc server the image crashed.
>>>>>> Can you please take a look to the dump file and tell me what happened?
>>>>>> 
>>>>>> It would be worth so much to me, thank you
>>>>>> 
>>>>>> The file is here: https://pastebin.com/SrE6gcCv
>>>>>> &lt;https://pastebin.com/SrE6gcCv&gt;
>>>>>> 
>>>>>> 
>>>>>> Davide
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>>>>> &lt;http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html&gt;
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>>>> &lt;http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html&gt;
> 
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Reply via email to