Pharo or Squeak ? In squeak, this stackframe / large stackframe bug was introduced some months ago by a change for the compiler but it is already fixed. In pharo, we have a simliar bug (in pharos compiler (opal), not related to the change on the squeak compiler). This is a bug that is known but not yet fixed 13854 <https://pharo.fogbugz.com/default.asp?13854> frameSize calculated wrongly for #lineSegmentsDo: ! 2015-08-09 18:39 GMT+02:00 tim Rowledge <tim@rowledge.org>:

Sabine, As a general rule of thumb, if a method is too long to see at a glance - in practice this means too long to fit on your screen - then it almost certainly needs splitting up. I have been forcibly reminded of this a lot recently due to having to decode insanely long Python routines; seriously - 1100 lines for a single function?

tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: FSRA: Forms Skip and Run-Away