Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Toby Dickenson
On Tue, 12 Mar 2002 18:38:16 +0100, Oliver Bleutgen <[EMAIL PROTECTED]> wrote: >Acquisition.ImplicitAcquirerWrapper: 42442 That class is used to glue together acquisition content chains. Being top of the list indicates that you have been leaking an acquisition context chain. That doesnt mean t

Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Oliver Bleutgen
Toby Dickenson wrote: > On Tue, 12 Mar 2002 18:38:16 +0100, Oliver Bleutgen <[EMAIL PROTECTED]> > wrote: > > >>Acquisition.ImplicitAcquirerWrapper: 42442 >> > > That class is used to glue together acquisition content chains. Being > top of the list indicates that you have been leaking an acquis

Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Toby Dickenson
On Wed, 13 Mar 2002 11:37:00 +0100, Oliver Bleutgen <[EMAIL PROTECTED]> wrote: >- I did paste only the objects which have such a high count (next one >was approx 200). Hmm. Ill have to ponder what that means. >- This server (2.3.3) has no special products on it, just 2 Folderish >ZClasses, wh

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Matthew T. Kromer
On Tuesday, March 12, 2002, at 05:08 PM, Leonardo Rochael Almeida wrote: > > > Matthew, thanks for taking the time to gdb the beast with me. Did you > come up with any instrumentation I should add to Python or Zope to get > what it is that Python is trying to resease twice? If you want, I can > a

Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Andre Schubert
Andre Schubert schrieb: > > Andy McKay schrieb: > > > > Didnt Shane do a leak finder product that can help debug this? > > http://www.zope.org/Members/hathawsh > > I will install the LeakFinder product on the server and look what > happens If have installed LeakFinder this morning and resta

[Zope-dev] Re: more on the segfault saga

2002-03-13 Thread Martijn Jacobs
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 produc

Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Oliver Bleutgen
One more question then I'll shut up ;-). Toby Dickenson wrote: >>Is there a description somewhere what the basic causes of such leakages >>are? I.e. only bugs in python c-code/zope c-code? >> > > No, its possible for a bug in through-the-web edited dtml to cause > this. Waah, this is the fir

Re: [Zope-dev] Memory Leak Problem

2002-03-13 Thread Toby Dickenson
On Wed, 13 Mar 2002 13:46:27 +0100, Oliver Bleutgen <[EMAIL PROTECTED]> wrote: >Waah, this is the first time I hear that. That means that even if >zope/python would be bug-free, it's possible to write dtml that causes a >leak? >Is there a (non-esoteric) example for that? (untested, but the pri

Re: [Zope-dev] Re: more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
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 rec

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 09:09, Matthew T. Kromer wrote: > > On Tuesday, March 12, 2002, at 05:08 PM, Leonardo Rochael Almeida wrote: > > > > > > Matthew, thanks for taking the time to gdb the beast with me. Did you > > come up with any instrumentation I should add to Python or Zope to get > > what

[Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Andrew Sydelko
I'm curious as to what is holding up Zope 2.5.1? 2.5.1b1 has been out for quite a while now (in Zope time). --andy. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (R

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Brian Lloyd
We are trying to get to the bottom of a few straggling instability reports, so we're planning to go ahead with a b2 as soon as we've either a) figured out and fixed them b) figured them out and found it wasn't a Zope core problem or c) decide that we can't make enough progress in a reasonable time

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Shane Hathaway
Leonardo Rochael Almeida wrote: > Well, I have the energy, I just don't know where to start. But it's > beginning to look like I'll just have to roll up my sleeves and dive in > C code to hunt this beast down. And to think that I'd chosen Python as > my official programming language to avoid just

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 13:04, Shane Hathaway wrote: > I just found out about something that might help. If you compiled > against the GNU C library, you can set the environment variable > MALLOC_CHECK_ to 1 to get malloc usage warnings printed to stderr, or > set it to 2 to cause an abort() as

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 13:03, Brian Lloyd wrote: > We are trying to get to the bottom of a few straggling > instability reports, so we're planning to go ahead with > a b2 as soon as we've either a) figured out and fixed them > b) figured them out and found it wasn't a Zope core problem > or c) deci

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 12:40, Leonardo Rochael Almeida wrote: > Also, how about turning on some flags in > gc.seg_debug()? Do you think we might be able to glance something by > seeing what objects where logged as freed or by storing them in > gc.garbage? Forgot to mention, gc module documentation

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Shane Hathaway
Leonardo Rochael Almeida wrote: > On Wed, 2002-03-13 at 13:04, Shane Hathaway wrote: > >>I just found out about something that might help. If you compiled >>against the GNU C library, you can set the environment variable >>MALLOC_CHECK_ to 1 to get malloc usage warnings printed to stderr, or

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Brian Lloyd
> > We are trying to get to the bottom of a few straggling > > instability reports, so we're planning to go ahead with > > a b2 as soon as we've either a) figured out and fixed them > > b) figured them out and found it wasn't a Zope core problem > > or c) decide that we can't make enough progress

Re: [Zope-dev] Re: more on the segfault saga

2002-03-13 Thread Martijn Jacobs
> 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 > --prefix=/path/to

[Zope-dev] Help with DTML-IN statement

2002-03-13 Thread Gary Yee
Hello,   I am very new to Zope/DTML and I am a little confused with the operation of the DTML-IN statement. Here is the snippet of code       This code displays the contents 4 cells in a table and the output is12(4,5,6)(7,8,9)I am a litte confused because I though

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 14:04, Brian Lloyd wrote: > > The best way to help is to help get this (these) down to > a minimal, reproducable test case. The problem is, as far as I could check, the crashes all happen inside the gc, which runs orthogonal to the requests, so getting a reproduceable test

Re: [Zope-dev] Help with DTML-IN statement

2002-03-13 Thread Leonardo Rochael Almeida
Hi Gary, This question is more suited to [EMAIL PROTECTED] instead of [EMAIL PROTECTED], and you should not send html e-mail to any of these two lists, but since we are here... On Wed, 2002-03-13 at 16:13, Gary Yee wrote: > Hello, > > I am very new to Zope/DTML and I am a little confused with

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
I set MALLOC_CHECK_ to 1 and it said it was using the malloc debug hooks, but didn't report anything else before the crashes, so no point in setting it to 2... On Wed, 2002-03-13 at 13:49, Shane Hathaway wrote: > Leonardo Rochael Almeida wrote: > > On Wed, 2002-03-13 at 13:04, Shane Hathaway wrot

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Andy Dustman
On Wed, 2002-03-13 at 12:04, Brian Lloyd wrote: > - Absolutely eliminate SQL db access as a cause (it sounds > like we have proof of this now) This sounds like it is not specific to any DA. Is that the case? -- Andy Dustman PGP: 0x930B8AB6 @ .net http://dustman.net

RE: [Zope-dev] where is Zope 2.5.1?

2002-03-13 Thread Brian Lloyd
> > - Absolutely eliminate SQL db access as a cause (it sounds > > like we have proof of this now) > > This sounds like it is not specific to any DA. Is that the case? The only one I know of is the MySQL DA, but what I was getting at here was that eliminating ANY sql db access lets us d

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Matthew T. Kromer
On Wednesday, March 13, 2002, at 10:40 AM, Leonardo Rochael Almeida wrote: > > What about patching Python to report the freed objects like you > mentioned on IRC? Also, how about turning on some flags in > gc.seg_debug()? Do you think we might be able to glance something by > seeing what objects

Re: [Zope-dev] more on the segfault saga

2002-03-13 Thread Leonardo Rochael Almeida
On Wed, 2002-03-13 at 21:30, Matthew T. Kromer wrote: > > On Wednesday, March 13, 2002, at 10:40 AM, Leonardo Rochael Almeida > wrote: > > > > What about patching Python to report the freed objects like you > > mentioned on IRC? Also, how about turning on some flags in > > gc.seg_debug()? Do you