Martijn Jacobs wrote:
Hello Leo!
Tell us if your segfaults go away and whether Zope performance is
impacted by it.
The segfault is AWAY! I have an uptime of 2 hours now, it has never been
so long since it's in use! I don't notice any performance differences,
but I also have to say that I
Hello segfaulters and others interested in Zope instability issues!
Hello again :)
Our demi-god Matt Kromer from ZopeCorp has come up with a possible way
to corner the instability issue AND give you a stable, cycle-garbage
collecting Zope.
We probably should build a statue for this guy
On Tue, 2002-03-26 at 07:31, Martijn Jacobs wrote:
Just to make sure : I put gc.disable() in Z2.py and apply this
ZServerPublisher.py patch? Or do I have to add some more code to let the
garbage collector collect more often or less or...
No, you don't need to explicitly call gc.disable()
Hello segfaulters and others interested in Zope instability issues!
Our demi-god Matt Kromer from ZopeCorp has come up with a possible way
to corner the instability issue AND give you a stable, cycle-garbage
collecting Zope.
Since the problem seems, so far, to be caused by the Python
Ok, got some data on using this patches.
First of all, for those following, these patches don't seem to work well
if starting Zope as root, cause gdb will be started as the user Zope
turns to, and this gdb won't be able to attach to a root started
process, even if it's dropped it's privileges.
Leonardo Rochael Almeida wrote:
The official unofficial Zope place on irc is #zope at
irc.openprojects.net. Lots of cool and very knowledgeable people hang
out there.
OK, I put up a set of patches and a rather frazzled looking README for a
profiler patch to Python at
Hi Martijn,
We're basically just trying to construct traps to try to identify a
smoking gun. The upside is, if it works, we'll be able to fix the bug
very quickly. However, its based on assumptions about the exact nature
of the bug -- so each trap I write essentially is making a hypothesis
On Fri, 2002-03-15 at 08:19, Martijn Jacobs wrote:
Hello Leo, Matt, Brian,
I'm on it. Will send results when they're available. If anyone wants
to talk to me during the period, I'll be on IRC.
If you need any assistance for anything, I'm at your service
Which channel/server are
Sorry, the correct URL is http://www.coherence.nl/crash.txt
(without the dot)
martijn.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
Hello,
We also have the problem with zope crashing with segfault 11.
I've read al earlier posts on this subject, but couldn't notice anything
that could arrange a direct solution, or I should have missed something?
The only thing I can try is to describe our situation :
- We have a
The
On Wed, 2002-03-13 at 10:05, Martijn Jacobs wrote:
[...]
I don't know where to start, because attaching GDB doesn't make any
sense, since you have to start zope single threaded (according to Matts
Stability Howto) and then no crashes occur.
Actually, at least in Linux, with a recent
Actually, at least in Linux, with a recent gdb, you can attach gdb to
zope in multithread mode. Just take the -t 1 from the command line
sugested by the StabilityHOWTO and you're set. Best results are achieved
by compiling everything from source (python even, use the
12 matches
Mail list logo
