Strange and hard to reproduce crash

Fernando Perez at
Mon Oct 23 17:44:24 CDT 2006

On 10/23/06, Travis Oliphant <oliphant.travis at> wrote:
> Fernando Perez wrote:
> > Hi all,
> >
> > two colleagues have been seeing occasional crashes from very
> > long-running code which uses numpy.  We've now gotten a backtrace from
> > one such crash, unfortunately it uses a build from a few days ago:
> >
> This looks like a reference-count problem on the data-type objects
> (probably one of the builtin ones is trying to be released).  The
> reference count problem is probably hard to track down.
> A quick fix is to not allow the built-ins to be "freed" (the attempt
> should never be made, but if it is, then we should just incref the
> reference count and continue rather than die).
> Ideally, the reference count problem should be found, but other-wise
> I'll just insert some print statements if the attempt is made, but not
> actually do it as a safety measure.

If you point me to the right place in the sources, I'll be happy to
add something to my local copy, rebuild numpy and rerun with these
print statements in place.

I realize this is probably a very difficult problem to track down, but
it really sucks to run a code for 4 days only to have it explode at
the end.  Right now this is starting to be a serious problem for us as
we move our codes into large production runs, so I'm willing to put in
the necessary effort to track it down, though I'll need some guidance
from our gurus.



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo

More information about the Numpy-discussion mailing list