Ticket #204 (assigned defect)
Scalars leaked: 1
| Reported by: | szabgab | Owned by: | tsee |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | editor | Version: | trunk |
| Keywords: | bounty | Cc: |
Description
After closing padre I get the above warning on the command line.
It does not seem to be too serious an issue but better documented. (r2412)
Change History
comment:2 Changed 2 years ago by waxhead
- Owner set to tsee
- Status changed from new to assigned
Looks like tsee gets the beers!
This maybe fixed with the work done in the branch and waiting for merge after the 0.56 release.
I'm assigning this one to tsee so it gets closed if it turns out we owe him beers and cheers for solving the Leaking Scalar warning! :)
comment:4 Changed 4 months ago by gyles19
This issue is still present in 0.90 and can be reproduced with a simple "padre foo" thusly:
+ ulimit -c unlimited
+ LIBC_FATAL_STDERR_=1
+ PERLDB_OPTS='NonStop?=1 AutoTrace?=1 frame=2 LineInfo?=/dev/null noTTY'
+ /usr/bin/perl -d /usr/local/bin/padre foo
Scalars leaked: 1

For the record: This warning is issued when extra threads are joined. It's a combination of threads and Wx. Tough issue. I'll pay a couple of beers to whoever fixes it.