Recently I've been having a completely bizarre issue with Flash Pro CS5 which is bothering me to no end.
Whenever I hit Ctrl + Plus (the keyboard shortcut to zoom). Flash will completely disappear from my taskbar, as if it is crashed. However, looking at the task manager, although nothing can be seen in 'Applications', under 'Processes Flash is still visible.
To restart Flash, I have to manually kill this process then reopen it.
This does not happen when you use the manual zoom controls in the toolbar, nor does it happen when I zoom out via the shortcut (Ctrl + Minus)
Even if I reassign the zoom function to another button combo, (like Ctrl + ] ) It will still crash on me, making me think it's not a conflict with another program. I have temporarily just completely disabled the zoom shortcut altogether.
Anyone else experienced this error and have any clue what I can do? It's driving me batty, because zooming is a pretty constant part of my workflow.
I am running Windows 7 Enterprise.
Running Win7 Pro 64 SP1 and I just loaded up old CS5 and all I can say is it works as intended. Do any other Adobe apps have similar behavior like Photoshop with the same key combo? Have you tried wiping out preferences for CS5 (not ideal, but better than reinstalling), or have you tried reinstalling?
We tried to repro this issue at out end but wasn't able to . Can you try after clearing the Flash CS5 preferences and restarting Flash again ?
Further , in case you get any crash dump or logs generated , you can send that to us for better investigation.
Let me know if this solves the problem for you.
Thanks and regards,
Adobe Flash Professional Team.
Thanks Sinious and Sudeshna. Your help is very much appreciated. It is a very strange issue, and something i've never come across in my many years of using Flash.
I removed the preferences files, but unfortunately it didn't fix the issue. The problem appears to be unique to Flash, I use a number of Adobe products and I haven't been able to reproduce it in any others.
I couldn't find anything in the AMT3.log that stuck out, but here it is:
I am going to liase with our IT Department to reinstall the program, as unfortunately I do not have access to do so myself. Hopefully that will help the issue!