Remove and reinstall, it's an isolated issue as you mentioned. I have almost the same number of Lions running around with CS5.5 with no issues. Reinstalling takes less time than diagnosing.
CS6? TONS of issues. CS5.5? No issues.
You should know from iOS programming EXC_BAD_ACCESS is accessing an object that doesn't exist. The worst, most useless error to diagnose. Not worth the time.
Very interesting. I am having the same issue. I start up Flash, got to "Loading Accelerators" and then the spinning ball. "Force quit" indicates "not responding". This last time during my attempt to start the app up again I started looking for info online and found your posting. So as I am reading your post and logging in to reply to you Flash actually starts. I can even open my files. I checked the crash log - yes, I had the same error message as you did.
Crashed Thread: 15 Java: VM Thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010
But it's working now. I've even quit and started it again. Yes, it took just as long - probably 5 minutes or so - to start up. Its a long time to wait, and it shouldn't be happening, but all I really want is to be able to finish my project.
@ lmagellan Thanks very much for your response Linda, I gave your approach a shot, and it appears to work.
7 of 25 installations were affected on my end.
Two approaches appear to have resolved the problem: One, was your approach, which resolved the issue on 5 of the 7 affected machines.
The other, that resolved the issue on the other 2 machines, was to clear the Java caches ("Delete Files..." button in "Network" pane of "Java Preferences")
Very weird, but hey, I'll take it. Beats remove and reinstall by a longshot. Hopefully the installs will continue to perform as expected. If not, I'll post back to this thread.
@ sinious Thanks for your response. I agree that's one of the most useless, and frustrating errors ever. I was about to do a remove/reinstall on one of the affected machines when I received lmagellan's reply. Her solution worked, so no need to remove/reinstall. Thank you anyway, though!
@ lmagellan; I noticed that after letting the app launch "in it's own time", then quitting and relaunching, the relaunch went much faster - dare I say in it's "normal/usual" amount of time. If yours is still taking 5 min or so to relaunch, you might try clearing your Java caches. Thanks again for your response!
Thanks Don. Clearing the Java cache made it launch much faster.