For any run or just profiling? Normally the profiler swf shouldn't be in play. If a profiler session dies it can leave itself in the mm.cfg or whatever your OS equivalent is.
Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Tim Hoff Sent: Tuesday, March 17, 2009 4:58 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Security sandbox violation error after upgrade to SDK 3.2 Hi all, I just updated the Flex SDK to version 3.2, and am now getting a Security sandbox violation error everytime that I launch an AIR application from Eclipse. I was wondering if anyone else has run into this and might know of a fix. The stack trace is listed below. Thanks, -TH Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: file:///C|%2Fdev%2Fworkspace%2F.metadata%2F.plugins%2Fcom.adobe.flash.profiler%2FProfilerAgent.swf?host=localhost&port=9999<file:///\\C|%2Fdev%2Fworkspace%2F.metadata%2F.plugins%2Fcom.adobe.flash.profiler%2FProfilerAgent.swf?host=localhost&port=9999> cannot load data from localhost:9999. at ProfilerAgent()[C:\faramir\flex\sdk\modules\profiler3\as\ProfilerAgent.as:127] at runtime::ContentPlayer/loadInitialContent() at runtime::ContentPlayer/playRawContent() at runtime::ContentPlayer/playContent() at runtime::AppRunner/run() at global/runtime::ADLEntry()
