Guest Fenley Crunchwhistle Posted June 20, 2008 Posted June 20, 2008 Many applications when closed normally still appear in Task Manager. Some exhibit this behavior all the time, some only sometimes. For example, SysInternals Process Explorer and Vegas Pro 8 seem to never close properly and show an additional process in Process Explorer with every launch/exit. This is not application-specific behavior. I have XP 2002 SP3. Norton 360 with latest signatures finds no viruses or spyware. Windows Update finds no updates for my computer. Thanks
Guest Bob I Posted June 20, 2008 Posted June 20, 2008 Re: Processes won't close If you ignore this immediate check and observe later, have they gone away? Fenley Crunchwhistle wrote: > Many applications when closed normally still appear in Task Manager. > Some exhibit this behavior all the time, some only sometimes. > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never > close properly and show an additional process in Process Explorer with every > launch/exit. > This is not application-specific behavior. > I have XP 2002 SP3. > Norton 360 with latest signatures finds no viruses or spyware. > Windows Update finds no updates for my computer. > Thanks >
Guest db.·.. > Posted June 20, 2008 Posted June 20, 2008 Re: Processes won't close sometimes if the cpu is overwhelmingly busy, it cannot execute commands, which is "not" a good thing. however, you can control how busy your computer should be. my suggestion is to begin with what should be loaded when windows initializes, then be sure you conduct routine system maintenances like with: http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm -- db·´¯`·...¸><)))º> "Fenley Crunchwhistle" <Fenley Crunchwhistle@discussions.microsoft.com> wrote in message news:0DFD0264-E1A7-4D7D-AFC0-0FDD1A8C4241@microsoft.com... > Many applications when closed normally still appear in Task Manager. > Some exhibit this behavior all the time, some only sometimes. > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never > close properly and show an additional process in Process Explorer with every > launch/exit. > This is not application-specific behavior. > I have XP 2002 SP3. > Norton 360 with latest signatures finds no viruses or spyware. > Windows Update finds no updates for my computer. > Thanks >
Guest Fenley Crunchwhistle Posted June 21, 2008 Posted June 21, 2008 Re: Processes won't close No. They stick around indefinitely. With some applications, trying to load them a second time just does nothing. The application doesn't become visible and a second instance doesn't appear in Task Manager or Process Explorer. With other applications the instances shown in Task Manager or Process Explorer just pile up as you load and then "close" them... "Bob I" wrote: > If you ignore this immediate check and observe later, have they gone away? > > Fenley Crunchwhistle wrote: > > Many applications when closed normally still appear in Task Manager. > > Some exhibit this behavior all the time, some only sometimes. > > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never > > close properly and show an additional process in Process Explorer with every > > launch/exit. > > This is not application-specific behavior. > > I have XP 2002 SP3. > > Norton 360 with latest signatures finds no viruses or spyware. > > Windows Update finds no updates for my computer. > > Thanks > > > >
Guest Fenley Crunchwhistle Posted June 21, 2008 Posted June 21, 2008 Re: Processes won't close When this anamoly occurs the CPU is typically at 10-12% (Sytem Idle process: 90-92%). "db.·.. ><))) ·>` .. ." wrote: > sometimes if the cpu > is overwhelmingly > busy, it cannot execute > commands, which is > "not" a good thing. > > however, you can > control how busy > your computer should > be. > > my suggestion is to > begin with what should > be loaded when windows > initializes, then be sure > you conduct routine > system maintenances > like with: > > http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm > > -- > > db·´¯`·...¸><)))º> > > > "Fenley Crunchwhistle" <Fenley Crunchwhistle@discussions.microsoft.com> wrote in > message news:0DFD0264-E1A7-4D7D-AFC0-0FDD1A8C4241@microsoft.com... > > Many applications when closed normally still appear in Task Manager. > > Some exhibit this behavior all the time, some only sometimes. > > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never > > close properly and show an additional process in Process Explorer with every > > launch/exit. > > This is not application-specific behavior. > > I have XP 2002 SP3. > > Norton 360 with latest signatures finds no viruses or spyware. > > Windows Update finds no updates for my computer. > > Thanks > > > >
Guest db.·.. > Posted June 21, 2008 Posted June 21, 2008 Re: Processes won't close well, even if the cpu show that small amount, the dialog you are using to view that data is also a process and may not likely be reporting the correct amount, until the cpu is free'd up. also, sometimes if virtual memory is set to auto and it is trying to increase the size due to more memory requirement then that process can stall the system. my suggestion is to set the virtual mem to a custom size of initial=2 and max=?. the recommended max amount is provided by windows on the lower part of the v.m. dialog window. next you may also want to download and install this: http://www.amsn.ro/ it will clear out the memory of any processes that are orphaned in the memory and stalling. -- db·´¯`·...¸><)))º> "Fenley Crunchwhistle" <FenleyCrunchwhistle@discussions.microsoft.com> wrote in message news:6C3F0292-172E-4528-B398-21574FF7C1CB@microsoft.com... > When this anamoly occurs the CPU is typically at 10-12% (Sytem Idle process: > 90-92%). > > "db.·.. ><))) ·>` .. ." wrote: > >> sometimes if the cpu >> is overwhelmingly >> busy, it cannot execute >> commands, which is >> "not" a good thing. >> >> however, you can >> control how busy >> your computer should >> be. >> >> my suggestion is to >> begin with what should >> be loaded when windows >> initializes, then be sure >> you conduct routine >> system maintenances >> like with: >> >> http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm >> >> -- >> >> db·´¯`·...¸><)))º> >> >> >> "Fenley Crunchwhistle" <Fenley Crunchwhistle@discussions.microsoft.com> wrote >> in >> message news:0DFD0264-E1A7-4D7D-AFC0-0FDD1A8C4241@microsoft.com... >> > Many applications when closed normally still appear in Task Manager. >> > Some exhibit this behavior all the time, some only sometimes. >> > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never >> > close properly and show an additional process in Process Explorer with >> > every >> > launch/exit. >> > This is not application-specific behavior. >> > I have XP 2002 SP3. >> > Norton 360 with latest signatures finds no viruses or spyware. >> > Windows Update finds no updates for my computer. >> > Thanks >> > >> >>
Guest Fenley Crunchwhistle Posted June 22, 2008 Posted June 22, 2008 Re: Processes won't close Virtual memory was already set close to your recommendation. I have 1G of physical memory , the initial page file size is set to 1534M, the maximum size is set to 1534M. "db.·.. ><))) ·>` .. ." wrote: > well, even if the cpu > show that small amount, > the dialog you are using > to view that data is also > a process and may not > likely be reporting the > correct amount, until > the cpu is free'd up. > > also, sometimes if virtual > memory is set to auto > and it is trying to > increase the size due > to more memory > requirement then that > process can stall the > system. > > my suggestion is to > set the virtual mem > to a custom size of > initial=2 and max=?. > > the recommended > max amount is provided > by windows on the > lower part of the > v.m. dialog window. > > next you may also > want to download > and install this: > > http://www.amsn.ro/ > > it will clear out the > memory of any processes > that are orphaned in the > memory and stalling. > > -- > > db·´¯`·...¸><)))º> > > > > "Fenley Crunchwhistle" <FenleyCrunchwhistle@discussions.microsoft.com> wrote in > message news:6C3F0292-172E-4528-B398-21574FF7C1CB@microsoft.com... > > When this anamoly occurs the CPU is typically at 10-12% (Sytem Idle process: > > 90-92%). > > > > "db.·.. ><))) ·>` .. ." wrote: > > > >> sometimes if the cpu > >> is overwhelmingly > >> busy, it cannot execute > >> commands, which is > >> "not" a good thing. > >> > >> however, you can > >> control how busy > >> your computer should > >> be. > >> > >> my suggestion is to > >> begin with what should > >> be loaded when windows > >> initializes, then be sure > >> you conduct routine > >> system maintenances > >> like with: > >> > >> http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm > >> > >> -- > >> > >> db·´¯`·...¸><)))º> > >> > >> > >> "Fenley Crunchwhistle" <Fenley Crunchwhistle@discussions.microsoft.com> wrote > >> in > >> message news:0DFD0264-E1A7-4D7D-AFC0-0FDD1A8C4241@microsoft.com... > >> > Many applications when closed normally still appear in Task Manager. > >> > Some exhibit this behavior all the time, some only sometimes. > >> > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never > >> > close properly and show an additional process in Process Explorer with > >> > every > >> > launch/exit. > >> > This is not application-specific behavior. > >> > I have XP 2002 SP3. > >> > Norton 360 with latest signatures finds no viruses or spyware. > >> > Windows Update finds no updates for my computer. > >> > Thanks > >> > > >> > >> > >
Guest db.·.. > Posted June 22, 2008 Posted June 22, 2008 Re: Processes won't close set initial=2 -- db·´¯`·...¸><)))º> "Fenley Crunchwhistle" <FenleyCrunchwhistle@discussions.microsoft.com> wrote in message news:4840AAF1-EFFF-4060-8D70-279FA15DA796@microsoft.com... > Virtual memory was already set close to your recommendation. I have 1G of > physical memory , the initial page file size is set to 1534M, the maximum > size is set to 1534M. > > "db.·.. ><))) ·>` .. ." wrote: > >> well, even if the cpu >> show that small amount, >> the dialog you are using >> to view that data is also >> a process and may not >> likely be reporting the >> correct amount, until >> the cpu is free'd up. >> >> also, sometimes if virtual >> memory is set to auto >> and it is trying to >> increase the size due >> to more memory >> requirement then that >> process can stall the >> system. >> >> my suggestion is to >> set the virtual mem >> to a custom size of >> initial=2 and max=?. >> >> the recommended >> max amount is provided >> by windows on the >> lower part of the >> v.m. dialog window. >> >> next you may also >> want to download >> and install this: >> >> http://www.amsn.ro/ >> >> it will clear out the >> memory of any processes >> that are orphaned in the >> memory and stalling. >> >> -- >> >> db·´¯`·...¸><)))º> >> >> >> >> "Fenley Crunchwhistle" <FenleyCrunchwhistle@discussions.microsoft.com> wrote >> in >> message news:6C3F0292-172E-4528-B398-21574FF7C1CB@microsoft.com... >> > When this anamoly occurs the CPU is typically at 10-12% (Sytem Idle >> > process: >> > 90-92%). >> > >> > "db.·.. ><))) ·>` .. ." wrote: >> > >> >> sometimes if the cpu >> >> is overwhelmingly >> >> busy, it cannot execute >> >> commands, which is >> >> "not" a good thing. >> >> >> >> however, you can >> >> control how busy >> >> your computer should >> >> be. >> >> >> >> my suggestion is to >> >> begin with what should >> >> be loaded when windows >> >> initializes, then be sure >> >> you conduct routine >> >> system maintenances >> >> like with: >> >> >> >> http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm >> >> >> >> -- >> >> >> >> db·´¯`·...¸><)))º> >> >> >> >> >> >> "Fenley Crunchwhistle" <Fenley Crunchwhistle@discussions.microsoft.com> >> >> wrote >> >> in >> >> message news:0DFD0264-E1A7-4D7D-AFC0-0FDD1A8C4241@microsoft.com... >> >> > Many applications when closed normally still appear in Task Manager. >> >> > Some exhibit this behavior all the time, some only sometimes. >> >> > For example, SysInternals Process Explorer and Vegas Pro 8 seem to never >> >> > close properly and show an additional process in Process Explorer with >> >> > every >> >> > launch/exit. >> >> > This is not application-specific behavior. >> >> > I have XP 2002 SP3. >> >> > Norton 360 with latest signatures finds no viruses or spyware. >> >> > Windows Update finds no updates for my computer. >> >> > Thanks >> >> > >> >> >> >> >> >>
Guest Bob I Posted June 23, 2008 Posted June 23, 2008 Re: Processes won't close It would seem that something is preventing them from closing normally. Have you checked for malware, keyloggers and the like? I presume you have not installed some "reg cleaner" or "memory manager" which is causing this issue, if so, remove them. Fenley Crunchwhistle wrote: > No. They stick around indefinitely. With some applications, trying to load > them a second time just does nothing. The application doesn't become visible > and a second instance doesn't appear in Task Manager or Process Explorer. > With other applications the instances shown in Task Manager or Process > Explorer just pile up as you load and then "close" them... > > "Bob I" wrote: > > >>If you ignore this immediate check and observe later, have they gone away? >> >>Fenley Crunchwhistle wrote: >> >>>Many applications when closed normally still appear in Task Manager. >>>Some exhibit this behavior all the time, some only sometimes. >>>For example, SysInternals Process Explorer and Vegas Pro 8 seem to never >>>close properly and show an additional process in Process Explorer with every >>>launch/exit. >>>This is not application-specific behavior. >>>I have XP 2002 SP3. >>>Norton 360 with latest signatures finds no viruses or spyware. >>>Windows Update finds no updates for my computer. >>>Thanks >>> >> >>
Recommended Posts