Thought I was on VM-dev but obviously I'm not :-)
-------- Weitergeleitete Nachricht -------- Betreff: Squeak 5.0 All in one crashed on my Pi after running 3 weeks at 40% CPU Datum: Fri, 18 Sep 2015 18:04:23 +0200 Von: Herbert König herbertkoenig@gmx.net An: vm-dev@lists.squeakfoundation.org
Hi,
since the 5.0 all in one I use it 24/7 on my Pi without any problems. The recent uninterrupted run was about three weeks (there had been a two week run before) and a few minutes ago it crashed with no apparent reason.
As the stack dump suggests I use BitBlt a lot, Squeak averages on 40% CPU, over all the Pi averages at 60% CPU.
I have no idea what happened and there was no apparent reason. for the crash. There is no squeakDebug.log and I found nothing in /var/log.
I restarted Squeak and it works nicely.
Cheers,
Herbert
On 18-09-2015, at 9:06 AM, Herbert König herbertkoenig@gmx.net wrote:
since the 5.0 all in one I use it 24/7 on my Pi without any problems. The recent uninterrupted run was about three weeks (there had been a two week run before) and a few minutes ago it crashed with no apparent reason.
I don’t think I’ve ever run anything for that long continuously. That long implies it isn’t any simple run-out-of-memory problem, or code-generation. The best I can think of right now is that the *data* you had got in this case was a bit ugly and upset the bitblt prim. The only real way to find anything out here would be to run a debug vm under gdb and see what can be found when it crashes. Which with a three-week use case is going to be such fun…
Which reminds me, I have no idea if we provide debug build VMs for people to grab? Anyone?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: BNE: Buy Non-IBM Equipment
And I'm always amazed how stable Squeak runs. If there's such a debug VM I'll try to run it.
Now lets talk about ugly bits that upset the blt :-) It was the 360somethingthousandth bmp from the same old garden being watched for pooing cats. No evil deeds the last week.
Vigilance!
Herbert
Am 18.09.2015 um 19:38 schrieb tim Rowledge:
On 18-09-2015, at 9:06 AM, Herbert König herbertkoenig@gmx.net wrote:
since the 5.0 all in one I use it 24/7 on my Pi without any problems. The recent uninterrupted run was about three weeks (there had been a two week run before) and a few minutes ago it crashed with no apparent reason.
I don’t think I’ve ever run anything for that long continuously. That long implies it isn’t any simple run-out-of-memory problem, or code-generation. The best I can think of right now is that the *data* you had got in this case was a bit ugly and upset the bitblt prim. The only real way to find anything out here would be to run a debug vm under gdb and see what can be found when it crashes. Which with a three-week use case is going to be such fun…
Which reminds me, I have no idea if we provide debug build VMs for people to grab? Anyone?
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: BNE: Buy Non-IBM Equipment
squeak-dev@lists.squeakfoundation.org
-
Herbert König -
tim Rowledge