Can someone explain why once a windows app crashes, it will usually crash every time you open it until you reboot?

[notfred]

fvcking annoying :|

 

[minendo]

Originally posted by: notfred
fvcking annoying :|

I have found that another app causes this problem. I have this problem a lot with AIM and have found that if I open Outlook then terminate the process, AIM will open fine.

 

[KingNothing]

Could be the process is still hanging around too. If Electronics Workbench crashes, I have to go manually kill its process before I can restart it.

 

[Descartes]

What's the application? Is it indeed a Windows app, or is it a console app?

Do you know what DLLs it loads? Does it load COM components? Are the COM components out-of-process? Do the out-of-process COM servers exist once the "parent" process is killed? Is it a .NET app?

There are many, many reasons why this could happen, but if you can answer all of the above, I can tell you what's wrong. If it's simply a normal app then everything loaded is removed once the process is destroyed. The only way any state of disorder would be persisted is if the process serialized its memory to disk, then deserialized it once it was opened again...

 

[MeanMeosh]

manually kill the process. it'll work after that.

 

[Booster]

I think it's b/c your Windows isn't XP compliant. Am I right?

 

[Descartes]

Originally posted by: MeanMeosh
manually kill the process. it'll work after that.

He said "every time you open it" thereby implying that the process was actually dead. Whether you kill it gracefully or manually, it's still dead.

 

[EagleKeeper]

As Descartes stated:

The program has not properly cleaned up after itself and some residue is hanging around.
When the program restarts, the original left overs are causing trouble; they are not in the proper startup state.

Windows does not cleanup after an application properly if the app does not cles down properly on its own.