cLive ;-) has asked for the wisdom of the Perl Monks concerning the following question:

Hi all, I'm getting this a lot at the moment in my Apache error error log:
Attempt to free unreferenced scalar
It only appears when warnings are on. I didn't notice it immediately - like all lazy coders, I only parse the error_log when I'm getting a 500 error :)

It started appearing about two hours ago, and I can't think what I could have done to trigger it?!?

When I looked up the error in the camel, it says that the error is " likely a problem with the C extension module you're developing".

But all I'm doing is playing with CGI under mod_perl. So now I'm totally confused.

Has anyone got any suggestions on a quick way to try and pinpoint where this is coming from?

cLive ;-)

--

Replies are listed 'Best First'.
Re: Attempt to free unreferences scalar
by Coruscate (Sexton) on Feb 04, 2003 at 03:20 UTC

    Our own merlyn has apparently come across this problem as well, as I discovered while reading an old archived message. It seems that the problem stems from a bug in earlier versions of mod_perl. Particularly, I read on this page that the problem was supposidly fixed in version 1.1.6 (not 1.1.6_01-dev, you still get those errors with this version). But then again, a yahoo groups message has a guy with a problem with mod_perl 1.24, but his case is quite different. Of course, you did not tell us what version of apache, perl, mod_perl you are running, so I can't know for sure that this is the problem. Try posting some of the versions and specifications if you want more direct help...


          C:\>shutdown -s
          >> Could not shut down computer:
          >> Microsoft is logged in remotely.
        

      Here's the beef:
      Apache 1.3.27 PHP 4.3.0 mod_perl 1.27 mod_ssl 2.8.12 OpenSSL 0.9.6g
      The irritating thing is that I only get the error (I think) when the child process exits, so even when I'm tailing my error log, they don't turn up when I do a reload, they appear quite a few seconds later. So I can't just sit there trimming my code until the problem goes - well I can, but only at a speed that makes me want to head-butt my desk...