Aptech Systems, Inc. Worldwide Headquarters
Aptech Systems, Inc.
2350 East Germann Road, Suite #21
Chandler, AZ 85286
Ready to Get Started?
Request Quote & Product Information
Training & Events
Step-by-step, informative lessons for those who want to dive into GAUSS and achieve their goals, fast.
Have a Specific Question?
Q&A: Register and Login
Premier Support and Platinum Premier Support are annually renewable membership programs that provide you with important benefits including technical support, product maintenance, and substantial cost-saving features for your GAUSS System or the GAUSS Engine.
Join our community to see why our users are considered some of the most active and helpful in the industry!
Where to Buy
Recent Tagsapplications character vectors CML CMLMT Constrained Optimization datasets dates dlibrary dllcall error error handling errors Excel file i/o floating network GAUSS Engine graphics GUI hotkeys installation Java API license licensing linux loading data loops matrices matrix matrix manipulation Maxlik MaxLikMT Memory optimization Optmum output PQG graphics procs RAM random numbers string functions strings structures threading Time Series writing data
Time Series 2.0 MT
Find out more now
Time Series MT 2.1
Find out more now
Solving Threading Error 'Resource Temporarily Unavailable'
I am running a 50000 round loop using two threads. The procedure called by each thread also includes a 2000 round bootstrap procedure that is divided into two threads within the top procedure.
I have run the code on a two-core-CPU desktop using GAUSS 13 without any problem. However, when I run the code on a four-core-CPU laptop using GAUSS 12, after about several thousand rounds of the main loop, there will be an error message appearing: error G0576 : 'Resource Temporarily Unavailable' : Threading error.
I don't know why this error would appear only on the laptop after thousands of loops have been run without the problem. Can anyone help.
The error G0576: 'Resource Temporarily Unavailable': Threading error is almost certainly coming from the creation of a new thread. GAUSS uses the pthreads library for threadStat, threadBegin, etc.
There are many possible factors. If one of the laptops is using and older operating system (i.e. Windows XP or Red Hat Linux 4), and your program logic is set up to spin a very large number of threads, it may simply be an OS thread limit.
GAUSS 13 for Windows uses a newer version of the pthreads for Windows library, which is significantly improved vs. the version used in GAUSS 12. GAUSS 13 and 14 are also more memory efficient in certain thread contexts than GAUSS 11 or 12. I would recommend installing GAUSS 13 or 14 on this machine to see if it solves the problem.