[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

Tracking an "Out of Memory!" error



I've got an application that uses a local library, a couple of CPAN
libs and a couple of core libs. None of the libraries are unique to
this application, and the combination in this specific application
isn't unique, either. However, this application crashes with the panic
message, "Out of Memory!", whereas none of the other applications in
this system do. I've stepped through the debugger, and the point at
which it appears to be occuring is inside of the CPAN library
Text::Template, at a point where it eval's a chunk of code from within
the template being filled out. When these evals run (it dies on the
third or fourth), it appears to be evaluating the whole script itself,
as well as the chunk in question. However, this could be a side effect
of running under the debugger.

At this stage, I'm dead in the water. I cannot determine what is
causing the memory error, and I cannot work around the need for
Text::Template in the application. Any ideas are greatly welcomed.

Randy
--
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Randy J. Ray            | "NSA doesn't need a key to compromise security in
rjray@redhat.com        | Windows. Programs like Back Orifice can do it without
415-777-9810 x246       | any keys." --Bruce Schneier on the MS/NSA controversy


Follow-Ups from:
Ilya Zakharevich <ilya@math.ohio-state.edu>

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]