On Fri, 2 Oct 2015 22:07:03 +0200
David Emanuel da Costa Santiago wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
>
> Hi Shlomi
>
> I just noticed that, if i merge yenc_encode_c_for_perl with
> _yenc_encode_c into one function then valgrind sto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Shlomi
I just noticed that, if i merge yenc_encode_c_for_perl with
_yenc_encode_c into one function then valgrind stops reporting memory
leaks.
I need to do more tests though.
Thanks and best regards,
David Santiago
On Thu, 1 Oct 2015 22
On Thu, 1 Oct 2015 19:51:12 +0200
David Emanuel da Costa Santiago wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
> Now with the code attached.
>
> Best regards,
> David Santiago
>
Hi David!
One thing that strikes me as a problem is the fact that _yenc_encode_c returns
a stri
tool a reliable tool for checking for memory leaks in
> perl and in our perl scripts?
>
> I have a perl script that's consuming all the memory available on my
> system. I rechecked the script and since i didn't found anything
> (algorithm wise) that can cause such
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
Is the valgrind tool a reliable tool for checking for memory leaks in
perl and in our perl scripts?
I have a perl script that's consuming all the memory available on my
system. I rechecked the script and since i didn't foun
d a runaway
of
>> the memory consumption.
>> After a few hundred connects and disconnects I'll get an Out of memory. :-(
>>
>> In order to test threads in perl, I wrote a new script which just spawns
and
>> terminates threads. ( Attached it below )
>>
>
Hi,
I'm still trying to get familiar with threads and sockets.
However, I got in some troubles with memory leaks, could anyone perhaps give
me a hint in which way I should write a multithreaded socket server ?
I wrote a small server, which accepts connections on a tcp socket and spawns a
I'm running some very long tests using Test::More and after ~20K
iterations I am getting ~200MB of memory usage.
It's really slowing things down.
Are there any pointers on how to track down or eliminate memory leakage?
Anything at all would probably help some.
--
To unsubscribe, e-mail: [EM
Steve Grazzini wrote:
> David <[EMAIL PROTECTED]> wrote:
>> the heap will not go away (because Perl does it's own memory
>> management) until the client exit.).
>
> Actually, the default config uses libc malloc.
you simply can't free() yourself
david
--
To unsubscribe, e-mail: [EMAIL PROTECT
David <[EMAIL PROTECTED]> wrote:
> the heap will not go away (because Perl does it's own memory
> management) until the client exit.).
Actually, the default config uses libc malloc.
(check perl -V)
--
Steve
perldoc -qa.j | perl -lpe '($_)=m("(.*)")'
--
To unsubscribe, e-mail: [EMAIL PROTEC
.--[ chad kellerman wrote (2002/09/20 at 15:32:11) ]--
|
| I tried doing the same thing but my supervisor got mad. We aren't
| allowed to use any type of system call in our scripts. If the system
| call is in a perl module it's one thing but not in our code.
|
| system or e
Frank-
I think he believes it's more of a security issue then anything
else. We only have three os's here. Solaris x86, Solaris sparc, and
linux. So I don't think it's a port issue.
--chad
On Fri, 2002-09-20 at 15:49, Frank Wiles wrote:
> .--[ chad kellerman wrote (2002/09/20 at 15
Chad Kellerman wrote:
> I tried doing the same thing but my supervisor got mad. We aren't
> allowed to use any type of system call in our scripts. If the system
> call is in a perl module it's one thing but not in our code.
>
> system or exec anything that executes from /bin/sh
>
> even thoug
I tried doing the same thing but my supervisor got mad. We aren't
allowed to use any type of system call in our scripts. If the system
call is in a perl module it's one thing but not in our code.
system or exec anything that executes from /bin/sh
even though it is so much nicer to do that, esp
Chad Kellerman wrote:
> Dave,
>
> Actually in each fork. I was tarring up information from another
> server with Net::SSH::Perl. The full tar ball was written to stdout and
> I would gzip in on the originating server. If I did not fork each tar
> the server would crash in a matter of minutes
Dave,
Actually in each fork. I was tarring up information from another
server with Net::SSH::Perl. The full tar ball was written to stdout and
I would gzip in on the originating server. If I did not fork each tar
the server would crash in a matter of minutes. But with the forks I
actually co
Chad Kellerman wrote:
>
> here's my $.02 on this subject. Correct me if I am wrong.
> Once perl uses memory it does not want to let it go back to the system.
> I believe I have read the the developers are working on this. Since you
> have your script running as a daemon. It will not release a
; -Original Message-
> From: Angerstein [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 20, 2002 12:30 AM
> To: [EMAIL PROTECTED]
> Subject: how to find memory leaks?
>
>
> Hi,
> I have a deamon like programm, which runs tasks at give timestamps.
> This is in a w
20, 2002 12:30 AM
To: [EMAIL PROTECTED]
Subject: how to find memory leaks?
Hi,
I have a deamon like programm, which runs tasks at give timestamps.
This is in a while (1) {} if startjobx == time loop.
Now i have the problem that one or more of my datastructures eats more and
more memory.
I
-Ursprüngliche Nachricht-
Von: Angerstein [mailto:[EMAIL PROTECTED]]
Gesendet am: Freitag, 20. September 2002 09:30
An: [EMAIL PROTECTED]
Betreff: how to find memory leaks?
Hi,
I have a deamon like programm, which runs tasks at give timestamps.
This is in a while (1) {} if startjobx
Hi,
I have a deamon like programm, which runs tasks at give timestamps.
This is in a while (1) {} if startjobx == time loop.
Now i have the problem that one or more of my datastructures eats more and
more memory.
I "delete" every value after using it from my hashes or array from arrays,
but it s
egrenes [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 02, 2002 6:45 AM
To: Jonathan E. Paton; [EMAIL PROTECTED]
Subject: Re: SybPerl - Memory leaks
The same thing happens when I comment out the checks.
The script uses more memory when I connect to the database:
$dbh = new Sybase::DBlib $us
ED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 12:31 PM
Subject: Re: SybPerl - Memory leaks
> > The script is not smallish, but the main loop looks like this:
> >
> > {
> > # Connecting
> > $dbh = new Sybase::DBlib $userid, $password, $host;
> The script is not smallish, but the main loop looks like this:
>
> {
> # Connecting
> $dbh = new Sybase::DBlib $userid, $password, $host;
> $dbh->dbuse($database);
>
> # Checking
> checkProsesses();
> checkSegmentStatus();
> getMonitor();
>
> # Disconnecting
>
Rune
- Original Message -
From: "Jonathan E. Paton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 12:15 PM
Subject: Re: SybPerl - Memory leaks
> > I've created a script that is checking the status of an ASE-server.
> I've created a script that is checking the status of an ASE-server.
> It's running in an infinitive loop:
>
> 1. Connect to the database
> 2. Doing some checks...
> 3. Disconnecting from the db
> 4. Sleeping for avile
> 5.
>
> I found that the perl prosess is using about 4
Hi
I've created a script that is checking the status of an ASE-server. It's running in an
infinitive loop:
1. Connect to the database
2. Doing som checks...
3. Disconnecting from the db
4. Sleeping for avile
5.
I found that the perl prosess is using about 4k more memory fo
Hi,
(excuse my poor English, I hope it will be still intelligible ;-)
I want to use Perl for some substitutions on large texts, but it seems
to me that perl does not correctly free memory after evaluating r.e.
with parentheses (see below). Problem is solved by using eval statement
around r.e. --
28 matches
Mail list logo
