You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Log4Perl 1.40 with Perl 5.16.2 results in the warning:
"close() on unopened filehandle FH at Log/Log4perl/Appender/File.pm line 257 during global destruction."
According to the Perl 5.16.2 documentation for perlobj:
"If your DESTROY method issues a warning during global destruction, the Perl interpreter will append the string " during global destruction" the warning."
It appears the global destruction phase in Perl automatically closes open file handles causing the DESTROY method to output the warning when it attempts to close the file handle.
The text was updated successfully, but these errors were encountered:
Can you post your code? Looks like the problem isn't that the cleanup happens in the global destruction phase (this is normal if, e.g., you're using a logger that doesn't go out of scope until the program ends by declaring it via "our"), but that it tries to close an unopened file handle, which happens, e.g. if you've already closed it manually or if it's a subprocess and the handle has already been closed in the parent process.
Using Log4Perl 1.40 with Perl 5.16.2 results in the warning:
"close() on unopened filehandle FH at Log/Log4perl/Appender/File.pm line 257 during global destruction."
According to the Perl 5.16.2 documentation for perlobj:
"If your DESTROY method issues a warning during global destruction, the Perl interpreter will append the string " during global destruction" the warning."
It appears the global destruction phase in Perl automatically closes open file handles causing the DESTROY method to output the warning when it attempts to close the file handle.
The text was updated successfully, but these errors were encountered: