So I had one of those awful days at work yesterday, we have all been through it at one point or another, where basically for no reason at all, everything started breaking and nothing would work. All I wanted to do was walk through my application in the debugger, and what should have been a straight shot ended up turning into hours of troubleshooting my computer. The problem was when I would try to debug my flex app, safari would crash or hang or timeout.
I had no idea what was causing flex and safari to break down like this. Started looking through the typical places, opened the flex logs, opened my mac console, then opened the system monitor but nothing showed me anything really glaring. The application monitor did tell me my syslog was running wild which really just means, something is wrong… keep looking. I restarted my syslog and kept looking, but with no luck. I did a fresh install of Eclipse from 3.2 to 3.3, reinstalled Flex plugin, reinstalled the flash debug player, I even re-checked out the project from the repository, again, all to no avail.
I then turned to my good friend google… I found a ton of articles and jira tickets dealing with this problem but none of them really fixed the issue until… drum roll please… I came across Ross Phillips’s blog. As I read through his post, he literally, word for word, had the exact same problem I had.
Basically, because I had been profiling the application two days ago, this ended up causing an issue with the debug player that resulted in the debug player crashing an hanging or not connecting at all. Ross found the solution here and while I don’t normally try to repost items like this (redundant blogging) i think this is a pretty common issue that might cause a lot of people a lot of angst and it definitely is worth a redundant post.
Ross’s solution, if your lazy and don’t want to click on the link above, is to open your mm.cfg file and remove the line in there relating to the profiler. Don’t worry, your still going to be able to profile your flex apps, this line will find its way back in here, so you’ll need to remove it again after you profile your app again but this way you can get back to debugging without interruption.
[Original Post]
http://www.fingersdancing.net/2008/06/flex-debugger-crashing-eclipse-safari.html
