Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory leak in net i/o? #463

Closed
p5pRT opened this issue Sep 1, 1999 · 3 comments
Closed

memory leak in net i/o? #463

p5pRT opened this issue Sep 1, 1999 · 3 comments

Comments

@p5pRT
Copy link

@p5pRT p5pRT commented Sep 1, 1999

Migrated from rt.perl.org#1304 (status was 'resolved')

Searchable as RT1304$

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Sep 1, 1999

From wjspurlin@statestreet.com

perl, version 5.005_03 built for i686-linux running on a Dell PIII 500
MHz, Linux 2.2.5

The leak does not occur using the same script and modules using​:

perl, version 5.004_04 built for sun-solaris, running on a Sun Ultra 10,
Solaris 2.5.1

same modules used on both systems​:

libwww-perl-5.44
libnet-1.0606
Time-HiRes-01.20
Digest-MD5-2.09
HTML-Parser-2.22
URI-1.04
MIME-Base64-2.11
Crypt-SSLeay-0.11 (installed against openssl-0.9.4)

--
Bill Spurlin
617-985-3533

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Sep 7, 1999

From [Unknown Contact. See original ticket]

In article <37CD57DA.7CE0D60A@​statestreet.com>,
  Bill Spurlin <wjspurlin@​statestreet.com> wrote​:

A memory leak is occurring in my web-testing robots when using​:

perl, version 5.005_03 built for i686-linux running on a Dell PIII 500
MHz, Linux 2.2.5

[snip]

I experience a big leak (maybe a small one, but it gets big
since I cycle a lot) in a script which uses almost the same
modules (under linux, I didn't test it under solaris).
is there a way to track down the point where the leak occurs?
the scripts leak even to 200MBytes.

--
Bill Spurlin
617-985-3533

Thanks.

Francesco Messineo

Sent via Deja.com http​://www.deja.com/
Share what you know. Learn what you don't.

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Jul 6, 2003

@rspier - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant