I have my app, running one on XP & one on Vista OS.
But there is a difference in thread count.
XP - 18 , Vista -14 threads.
Few threads are not started in my application which is running in Vista OS. So my application in Vista is not fully functioning. Any setting to be done?.
I have switched off the UAC in Vista.
Sounds crazy but true..
Unless you are observing other symptoms of failure, your application is probably working normally. When used by an application, various Windows subsystems will start threads of their own within the application's process. COM, for example, starts and stops its RPC worker threads at will. No guarantee is made that the number of such threads will remain constant within a single application instance, let alone from one version of Windows to the next.
Related
I'm a hobbyist programmer and have written a small application using Python3 and Gtk3.
It has two threads in it. One is a simple clock showing current time and updating the GUI every minute. The other is a countdown timer which can be started and stopped (the thread is killed with a flag on pause, and a new thread created on start). Both threads are daemons and neither interacts with the other.
It is working perfectly in linux.
In Windows it freezes / locks up, even when I haven't started the timer (i.e. only the clock thread is active). Windoze complains: "Python.exe is not responding".
My initial question is just whether it is safe to use threads in Windows. Or perhaps it is not a good idea to use GTK3?
Has anyone else experienced something like this?
I have a problem with server process in Windows XP (C:\Windows\system32\svchost.exe -k netsvcs). When I reboot system this process is in running stage and it end after 10 minutes:( It is very strange, because after this event windows works perfect.
No problem in windows log.
I thought it is a Virus but I checked system and do COMBOFIX. No change.
Any idea?
Regards
Svchost is a process that hosts services. It is essential for many windows programs to function, and simply killing it will not help and may stop something important from functioning. If you get sysinternals process explorer you can see what processes are linked to the particular svchost you are having trouble with so you can then uninstall or stop it.
I just moved from WinXP to Win7.
My software needs to have real time response to I/O so it makes a busy-wait in one thread (which has affinity to run on one CPU).
The result is 100% CPU on one of the cores and 0% CPU for others, on Winows XP it worked just fine.
In Windows 7 the system freezes. (The software is a console application, for Windows application it behaves a bit different. only if the main thread make busy-wait without peeking messages it freezes)
Any ideas ?
So you're using a non real-time OS for realtime I/O. Simply put the code isn't working correctly and should do a non busy-wait (change to a sleep-wait) loop and change the thread timer settings to something that is realtime enough.
See this question to setup windows for millisecond precision on a timer callback.
How to trigger a C# function at a certain time with millisecond precision?
all dos base application experts here is one thread i am creating.
i would like your opinion for this issues
i found one problem in windows xp or any windows system higher to windows 98
i have a dos base application which runs perfect on windows 98 but when i am running it on windows xp or other system it is showing me following error message
16 bit Ms-Dos Subsystem
An application has attemped to directly access the hard disk, which cannot
be supported. This may cause the application to function incorrectly.
Choose close to terminate the application
as i can run it by pressing ignore but want to remove this error message
second thing i found is dos base printing
printing is not working properly
as it prints some part then it pause for some time and then resume printing
so how to solve these problems.
An application has attemped to directly access the hard disk, which cannot be supported.
This error means exactly what it says. Older versions of Windows including 95/98/Me gave DOS programs full control over the system, meaning they could access hardware as they wished -- while this maintained compatibility with older programs, it could also cause the entire OS to crash if this one program did something wrong.
The Windows NT family (including XP and all newer versions) runs DOS programs in an NTVDM (NT virtual DOS machine) which does not have direct access to hardware, and any attempt by programs to access such things will cause the program to be terminated. Of course, you can ignore the error, but your program will likely not work correctly.
We are observing 4-6 threads on Windows 7 x64 in the application which have 3 threads and behaves normally on any Windows (either 32 or 64 bit) prior Windows 7.
Process Explorer shows the following "unknown" thread:
ntdll.dll!EtwDeliverDataBlock+offset
after random interval the following threads appear:
ntdll.dll!TpCallbackIndependent+offset
ntdll.dll!TpCallbackIndependent+offset
after that application can't create thread (error code 8, hot enough space ...).
It seems to me that some system DLL creates ETW threads or something. Does anyone know what these threads for and how to manage them?
The TP threads are a part of the Windows threadpool API and are created because your application (or a DLL used by your application) has used the Windows threadpool API. It also appears that your application (or one of the DLLs used by your application) is using the ETW APIs which also use a couple of threads. You really don't have the ability to manage these threads.
I seriously doubt that those threads are what is causing the out of memory error. It is more likely that the problem is that there isn't enough contiguous memory available in your process to reserve the room for the new thread's stack.