[Zope-dev] Re: Zope 2.4 crashes -- possible fix identified, other solutions also suggested

[Joseph Wayne Norton]

Matt et al -

We are using python 2.1.1 with pymalloc disabled and gc enabled with
zope 2.4.3 on the solaris platform.  We are currently seeing only 1 or
2 restarts a day for the zope/zeo clients.  Fortunately, we have not
experienced any trouble with the zeo server.

We have applied the a) extensionclass bugfix and I'm also planning to
apply the b) frame setup bugfix later this week.  We feel that patch
a) has reduced the number of restarts ... but the site activity has
descreased as well so it is difficult to really confirm.

1) I would like to know if any patches are available yet for the c)
compiler stack size bug.  When and if this patch is available, would
it require a new python installation, a new zope installation, or
both?

2) Are there any other related patches/comments with respect to python
2.1.1 and zope 2.4.3 and this issue?

thanks,

- joe n.


At Tue, 18 Dec 2001 10:44:33 -0500,
Matthew T. Kromer wrote:
> 
> Well, one suspicion I have is that (aside from memory corruption caused 
> by the compiler sack size bugs and the frame setup bug in 2.1 when 
> handling exceptions) ExtensionClasses are providing bogus data to 
> modules which aren't checking the flags to see if the GC fields are 
> populated.
> 
> Some of the people who have tried the modified extensionclass.h which 
> pads out the type object to align it with the 2.1 type object THINK they 
> have seen a reduction in crashes, but these same folks also have not 
> applied fixes for the two known bugs.
> 
> Soo... if shutting off GC extends time between crashes for some folks 
> from every 15 minutes to 3 times a day, my advise is to shut off GC.
>