public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Jason Jones <jasonaptech@gmail.com>
To: pthreads-win32@sourceware.org
Subject: Possible memory leak in Pthreads-Win32
Date: Fri, 02 Dec 2011 02:11:00 -0000	[thread overview]
Message-ID: <CABYyr4FaAKXN5ADJ6rP-QEb3-ygL=F8_O54B8Us+FBxLojy45g@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

Hello!

I am having memory leaks when using Pthreads-Win32. I have attached a
very simple example program that illustrates the problem. It is very
simple:

1) Inside a for loop, I create two threads with pthread_create.
2) Each of these threads executes a function that just returns 0;
3) I print out the return from the pthread_create calls.
4) Then use pthread_join on the two threads and the execute the next
iteration of the loop.

As I run this program, I can watch the memory constantly growing (
through task manager ). If I let it run long enough, I have seen it
use 600 megabytes of memory. If I run the same program on Linux with
native pthreads, I do not see any memory growth no matter how long I
let it run. On Windows I see the memory leak with Visual Studio 2008
and also with the latest version of the Intel compiler.

Is this a memory leak? Or am I doing something stupid?

Thanks,

Jason

[-- Attachment #2: pthread_leak.c --]
[-- Type: text/x-csrc, Size: 946 bytes --]

#include <stdio.h>
#include <stdlib.h>
#include <pthread.h>
/********* COMPILE/LINK LINE **********************/
/*** cl -I./pthreads.2 pthread_leak.c pthreads.2/pthreadVC2.lib ******/ 
/*** icl pthread_leak.c -I./pthreads.2 pthread_grandchild.c pthreads.2/pthreadVC2.lib ******/ 

int *call_print(void *ptr);
 
int main()
{
  pthread_t thread1, thread2;
  char *message1 = "1";
  char *message2 = "2";
  int  iret1, iret2, i;
 
 /* Create independent threads each of which will execute function */

   for(i=0;i<4000000;i++)
   { 
     iret1 = pthread_create( &thread1, NULL, call_print, (void*) message1);
     iret2 = pthread_create( &thread2, NULL, call_print, (void*) message2);

     printf("Thread 1 returns: %d iteration: %d\n",(int)iret1,(int)i);
     printf("Thread 2 returns: %d\n",(int)iret2);

     pthread_join( thread1, NULL);
     pthread_join( thread2, NULL);

   }
   return 0;
}

int *call_print(void *ptr)
{
    return 0;
}
 

             reply	other threads:[~2011-12-02  2:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  2:11 Jason Jones [this message]
2011-12-02 14:10 ` Ross Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABYyr4FaAKXN5ADJ6rP-QEb3-ygL=F8_O54B8Us+FBxLojy45g@mail.gmail.com' \
    --to=jasonaptech@gmail.com \
    --cc=pthreads-win32@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).