12-20-2010
Good evening,
Jim is right with the limitation of the virtual memory. On some 32-bits Linux system, you have up to 3Gb of VM available for the application. Assuming 8Mb stack per thread, it follows that you may have only up to 384 threads active at the same time.
Even if your threads terminate; you may still need to join them. Or as mentioned by Corona688, to detach the threads. The reason behind is explained in
this article
Cheers, Loïc
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Neo, if I have an old thread that is a few months old, and a few pages back in the forum it was posted in, is it ok to 'bump' it back to the front? or, would you rather i deleted the old thread, and just create a new one? btw the thread has no replies. (2 Replies)
Discussion started by: norsk hedensk
2 Replies
2. UNIX for Dummies Questions & Answers
i am tring to sort lots of data thats in many columns by just one column but, if I use sort +16 inputfile the column fluctuates because some of the rows have spaces etc within the text, so the end result is just a mess as it jumps around the columns depending whether it has spaces or not ....ie... (2 Replies)
Discussion started by: Gerry405
2 Replies
3. Solaris
Hi all!
1)Is there a way to write a program that will work on both solaris and intel based machines.
2)How can I achive this for a program that creates and synchronizes three threads.
Thank you.
vij. (3 Replies)
Discussion started by: vijlak
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
I have a program that has two types of threads:
1) Reader threads
2) Worker Threads
Readers: Their only job is to read files. They just read data from the files and put them into a buffer. They are obviously I/O intensive.
Workers: These are CPU intensive. They do some computation... (5 Replies)
Discussion started by: the_learner
5 Replies
5. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
6. Programming
Hello! I started studying studying about POSIX Threads a few days ago... so I am a little confused and I would appreciate some help!
I isolated this code... and I wonder if I could use threads in it!
#include <unistd.h>
#endif
#include <math.h>
//#include "main.h"
#include <sys/time.h>... (1 Reply)
Discussion started by: smurf2
1 Replies
7. Shell Programming and Scripting
Hi Unix gurus,
I am facing a threading problem in Perl.
I have a worker thread in perl in which I am calling a shell script.
The shell script echo's output to the Standard Output from time to time as it progresses.
In the worker thread, I am unable to display the echo statement of shell... (1 Reply)
Discussion started by: som.nitk
1 Replies
8. HP-UX
Hi,
I have a module by the name gateway, and it core dumps and gives a cma_dump.log file which says:
%Internal DCE Threads problem (version CMA BL10+), terminating execution.
% Reason: dispatch: no available VP (uniprocessor)
The current thread is 3 (address 0x40107c40)
DECthreads... (0 Replies)
Discussion started by: vanz
0 Replies
9. Programming
Hi guys,
I want to start studding about java threads. but the only book available on the market is "Java Threads" by O'Reilly... (0 Replies)
Discussion started by: majid.merkava
0 Replies
10. Programming
Hi Guys,
We are having one multi-threaded application.
The scenario is as follows:
--------------------------------- Client 1
|
APP Server -------------- Client 2
... (1 Reply)
Discussion started by: 14341
1 Replies
LEARN ABOUT SUSE
xlockdisplay
XInitThreads(3) XLIB FUNCTIONS XInitThreads(3)
NAME
XInitThreads, XLockDisplay, XUnlockDisplay - multi-threading support
SYNTAX
Status XInitThreads(void);
void XLockDisplay(Display *display);
void XUnlockDisplay(Display *display);
ARGUMENTS
display Specifies the connection to the X server.
DESCRIPTION
The XInitThreads function initializes Xlib support for concurrent threads. This function must be the first Xlib function a multi-threaded
program calls, and it must complete before any other Xlib call is made. This function returns a nonzero status if initialization was suc-
cessful; otherwise, it returns zero. On systems that do not support threads, this function always returns zero.
It is only necessary to call this function if multiple threads might use Xlib concurrently. If all calls to Xlib functions are protected
by some other access mechanism (for example, a mutual exclusion lock in a toolkit or through explicit client programming), Xlib thread ini-
tialization is not required. It is recommended that single-threaded programs not call this function.
The XLockDisplay function locks out all other threads from using the specified display. Other threads attempting to use the display will
block until the display is unlocked by this thread. Nested calls to XLockDisplay work correctly; the display will not actually be unlocked
until XUnlockDisplay has been called the same number of times as XLockDisplay. This function has no effect unless Xlib was successfully
initialized for threads using XInitThreads.
The XUnlockDisplay function allows other threads to use the specified display again. Any threads that have blocked on the display are
allowed to continue. Nested locking works correctly; if XLockDisplay has been called multiple times by a thread, then XUnlockDisplay must
be called an equal number of times before the display is actually unlocked. This function has no effect unless Xlib was successfully ini-
tialized for threads using XInitThreads.
SEE ALSO
Xlib - C Language X Interface
X Version 11 libX11 1.3.2 XInitThreads(3)