Does the profiler have different back references in the different scenarios.
If I could get the profiler to work I could have probably figured this out. I was at first getting
an error when trying to run the profiler. Now it just doesn't do anything.
Do you think you could help us debug our profiler problem? If we get that fixed, we could probably figure out why our modules aren't unloading. Here is my original thread about that: http://forums.adobe.com/thread/830387?tstart=0
Unfortunately, that isn't my area. I would ask on the FlashBuilder forum.
Did you verify that the preloadSWF entry in mm.cfg looks the same when it
works profiling a simple app?
Also, when you're not attempting to profile, there shouldn't be a preloadSWF
entry in there. Sometimes FB fails to remove that entry so deleting it
might help. FB will re-add the preloadSWF entry as needed.
Another thing to look into is FlashPlayer Trust files. They should be set
up automatically by FB, but occasionally an custom configuration fools the
setup. They are stored in different places based on your OS. Search the
Adobe site for details on where they go. They are typically used to get rid
of security errors when running apps from file://