Windows 7, CS5.5.2
I had this happening to me a few times times, I click the x in the top right corner to close Premiere, it asks me to save my project, I click no and the program seems to close, nothing on the taskbar left either, but it's still there in the taskmanager as a 290MB process.
I discovered this when Premiere refused to start. Now I'm forced to close the process before I can start Premiere.
What's causing this?
It seems that more people had this problem:
Some had it solved by updating the video driver, but since I already have the latest one (NVidia) I don't see how that's going to solve it. I also have the latest chipset and audio dirvers as of yesterday.
In one case I waited almost 15 min.
While I was away I have done some rigorous testing with Microsoft's driver verifier tool, the same tool they use to certify drivers. I have found two issues that I solved by removing two conflicting programs. The last diagnostics run of driver verifier was 100% successful. I also did a rigorous memory test and that didn't show any problems either. As a matter of fact I'm been amazed how stable my system is running for almost 2 years now and trust me, I stress it a lot by running applications like Photoshop, Illustrator, Cinema 4D, games and even Vmware. It's also not a system that is cluttered with all kind of junk, since I restore an image of the system partition every 3 months or so. The backup only contains the complete installation of my OS and software BEFORE use. A restore of this image before I posted my problem in this forum also didn't solve the issue
Anyway, after using driver verifier, I tried Premiere Pro again, closed it 3 times after fiddling with some videos and now after the 4th time I close the program I have the same issue as before: the program seems to close, the taskbar is empty, but again the task manager is showing the adobe premiere pro.exe process. That process is now still visible in task manager after about 10 minutes.
The only thing I could try now is cancelling all non-Microsoft processes and services and see if the problem still returns. I'm open for any other suggestions.
Mind you, I could solve this issue by writing a script that kills the process after I leave the program, but:
a - I don't know if it will do any harm (maybe the process is still saving or updating files)
b - It just camouflages the issue and I never feel good about that
EDIT: I closed all non-Windows processes (as an IT professional I know what I'm looking at), stopped all non-Windows processes and killed the adobe premiere pro.exe process that was still running, I started Premiere Pro fiddled with some videos, closed the program and again....the adobe premiere pro.exe process continues to run....for several minutes now.
To sum it up: I have the latest bios and drivers for graphics card, audio and chipset. I ran Microsoft driver verifier and managed to run a full final diagnostics without any conflicts, I ran a memory test that didn't show any error, I restored a clean backup of my system partition, I have all the latest updates for both Windows and Adobe software, I even tried running Premiere Pro without running all non- Windows processes and services and the Premiere Pro process still doesn't want to close. I don't run any brand new model video card either, I'm using a 9800GT that has very mature drivers and the card itself was bought brand new only 6 months ago and has not crashed any game so far ( the best test for any video card) or any application that makes use of GPU acceleration, like Photoshop for example, which always runs at OpenGL/normal.
Is Adobe now going to ignore me because they don't know what to do next? I have worked all night for like 5 hours to get this solved, you have no clue how many times I had to reboot to try new drivers and to run driver verifier, I expect a little more help from Adobe after all my efforts, since I've shown that I don't need to be spoon-fed when I have a technical problem (unlike most people), but are willing to do as much as possible myself to find a solution.
Oh well, I give up....just like all the others who obviously had or have the same problem that most likely will never be solved.
This is a user-to-user forum. Adobe staff (like me) help out here in our free time, when we can.
If you want a guaranteed response from Adobe personnel, then you need to contact Adobe Technical Support:
Contacting support? You're funny.... when I talked about the Microsoft driver verifier tool, their response was basically one of "Say what?!".
It's only my opinion, but if you alienate or antagonize someone with a big, white A and the moniker "Employee" under that A, your chances of getting any help at all here asymptotically approach zero.
Jeff Bellune, where you there when I contacted Adobe support? No, so stop making assumptions based on my behavior on the forum, which is partly based on my journey of over 9(!) hairpulling hours to find a solution for this irritating problem and also because of the moderator who moved my post without ever informing me, because obviously sending a tiny personal message with the text "I moved your post here <url>" which cost 15 seconds of his time was wayyyyy too much to ask.
Stuff like that doesn't sit well with me, considering that I'm running a rather large, mostly non-profit, web site for almost 9 years where I have done way more time consuming things that I never got paid for, than just sending a tiny personal message. Add to that the fact that the Adobe knowledge base is one of the worst I've ever seen (they could learn from IBM and Microsoft) and you'll understand where my current attitude comes from; pure frustration!
As for the problem at hand; it's finally solved. I've ran 20 tests with Premiere Pro and each time I closed the application, the process would still run....even after 2 or 3 min or more. I fixed what I considered the cause and not a single time did the problem return. I reversed the fix and as expected the problem returned.
Solved, 100% sure.
To anyone with the same problem (according to Google, there are many!); feel free to contact me personally and I'll erradicate this issue for you forever, because Adobe won't be of any help based on my experience on the phone and online.
To anyone with the same problem (according to Google, there are many!); feel free to contact me personally and I'll erradicate this issue for you forever, because Adobe won't be of any help based on my experience on the phone and online
You'd help a lot more people if you'd post your solution here in the forum.
based on my journey of over 9(!) hairpulling hours to find a solution for this irritating problem
which cost 15 seconds of his time was wayyyyy too much to ask
I'm running a rather large, mostly non-profit, web site for almost 9 years where I have done way more time consuming things that I never got paid for, than just sending a tiny personal message
You've already spent many hours on this -- hopefully another 15 seconds more of your unpaid time to really help future visitors out and post the solution here isn't too much to ask..
As for the moderator not sending you a PM, here are some things to think about: first, it takes more than 15 seconds. Second, if you multiply the time it does take by all the posts that have to be moved by the moderators every single day, it can add up to a lot of time. That's time that we generally don't have after sifting through the hundreds of posts that show up daily. There's an easy way for the users to find what they've posted and where it currently resides; sending a PM for every moved post or topic would be a colossal waste of our (unpaid) time. Sorry if you disagree.
Hey MDenver, i wanna take you up on your offer to help
To anyone with the same problem (according to Google, there are many!); feel free to contact me personally and I'll erradicate this issue for you forever
Can you please post the solution here, or at least tell us how to get in touch with you ?
I'm pulling my hair here too with this problem..
After clearing cache and getting rid of additional codecs (such as matrox, hali, codec pack etc) the processes for new projects in task manager do now quit, but here's the interesting thing- The old projects that used to hang , still do, so I suspect a corruption in project file /security or permisdsions may have contributed in the first place but the old projects still hang. The workaround is to create a new project and import the sequence in there. No more hanging processes in the task bar.