Jump to content
  • Who's Online   0 Members, 0 Anonymous, 2 Guests (See full list)

    • There are no registered users currently online
  • 0

ISO! YOU SAID SO


KAZ

Question

16 answers to this question

Recommended Posts

Hi there i am in task manager what am i looking for ?? i cant see

 

Processes tab, then go to View->Choose columns menu option. Select checkbox for Number of threads option (or similar name, I am not on English Windows). Click OK. Now you should see a new column with numbers in Processes tab.

 

X.

Link to comment
Share on other sites

Hi did a google search and got this info but still do not know what i have to do?? Please help.

 

PRB: Error on Win32s: R6016 - not enough space for thread data

View products that this article applies to.

Article ID : 126709

Last Review : October 30, 2003

Revision : 3.0

This article was previously published under Q126709

SYMPTOMS

Spawning and closing an application repeatedly succeeds around 60 times, then the spawn fails with this error:

R6016 - not enough space for thread data

Back to the top

 

CAUSE

The thread local storage (TLS) is not freed by the system.

 

The failure occurs only if there is another Win32-based application active while you are doing the spawns. The message itself is not generated by Win32s. It is generated by the Microsoft C Run-time (CRT) libraries LIBC.LIB and LIBCMT.LIB.

Back to the top

 

RESOLUTION

In Win32s version 1.25, TLS indices are freed during module cleanup. The TLS index is owned by the application's main module, so that it is freed when the application terminates. This solves the problem for LIBC and LIBCMT.

 

There is a similar problem with MSVCRT20.DLL. This DLL version of the CRT allocates a new TLS index each time a process attaches to it. MSVCRT20 doesn't free the TLS indices when unloading. The system should free them. If only one application uses MSVCRT20 at a time, then the application can be spawned successfully up to about 60 times on Win32s version 1.20. On Win32s version 1.25, there is no limitation.

 

If there is already an active application that uses MSVCRT20, it is not possible to spawn and close a second application that uses MSVCRT20 more than about 60 times under Win32s version 1.25. This is because MSVCRT20 allocates a TLS index each time a process attaches to it. Win32s will free all of the TLS indices only when MSVCRT20 is unloaded

Link to comment
Share on other sites

To me that sounds like another application is taking control of MSVCRT20.DLL and not releasing it. Check for running apps to see if you can shut it down (in task manager, processes) before starting up EMC

 

Thankyou for the information, i origanally had 700mb in there but took out 512mb, i and i am left with 252mb, i am waiting for a 1gb ram, do you think this could be affecting the way it works??

Link to comment
Share on other sites

To me that sounds like another application is taking control of MSVCRT20.DLL and not releasing it. Check for running apps to see if you can shut it down (in task manager, processes) before starting up EMC

 

"Win32s is an extension for the Windows 3.1 and Windows 3.11 operating systems, which allows them to run some 32-bit applications". Are we talking Windows 3 here?

 

Kaz, try to increase swap file, but I am afraid that thread stack memory may not be swappable. So another solution might be stopping any non-necessary software you run.

 

Also look at Task Manager at thread numbers for Roxio's and other processes (add appropriate column with View menu). Do they grow rapidly before the error?

 

X.

Link to comment
Share on other sites

X - it's more here than Win32S

 

There is a similar problem with MSVCRT20.DLL. This DLL version of the CRT allocates a new TLS index each time a process attaches to it. MSVCRT20 doesn't free the TLS indices when unloading. The system should free them.

Link to comment
Share on other sites

If you keep being helpful X, I'm going to have to treat you to a cyber beer - this one suit you? :)

 

Oh, well, thanks... :D

 

Żywiec is one of the best Polish beers, it has won many international awards.

If you need info on Polish alcoholic beverages, don't hesitate to ask. :huh:

 

X.

Link to comment
Share on other sites

Hello tried again and got this error

runtime error

 

R6016 not enough space for thread date

Do a disk cleanup (defrag is also suggested). How much space do you have on your hard drive?

I'm not even sure what the error message means. :)

Link to comment
Share on other sites

X - it's more here than Win32S

 

There is a similar problem with MSVCRT20.DLL. This DLL version of the CRT allocates a new TLS index each time a process attaches to it. MSVCRT20 doesn't free the TLS indices when unloading. The system should free them.

 

 

Hi there i am in task manager what am i looking for ?? i cant see

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...