Does anybody has any suggestions/ideas regarding this?
Long shot but...
When I had an issue with Flash Builder 4.6 PC mobile in regards to the java heap problem I discovered myself that my project had content which apparently blew out the FB threshold. In particular my mp3 files (3 units) were of too much high quality (360 kbps), I had to scale down the files to 128 kbps. This is an extreme shame.
I am currently running these threshold tests to see if my mp3s can be of better kbps. I did hack my CONFIG scripts in the sdk folders in the installation location but that did not solve my issue. LESSON LEARNED: FB apparently employs the web logic where reduced files equal better performance.
Yeah, thanks for your long shot reply. Anything could potentially help, but i think what youre talking about is a problem with RAM during complie-time. So it seams youre running out of java heap memory for the compiler/flash-builder, when compiling/builduing your application. The problem i have is that the flash-player is going out of RAM while running the application.
I found a PATCH some developer made which 'edits' the Flash Builder executable file and embeds the usage of more memory...it solved my problem where editing the CONFIG files did not. It's a shame that Adobe puts out these tools with so many limitations and now they have the nerve to remove design mode from version 4.7...I guess they don't want to make any money...I don't care who anyone is in the developing world, we can always use design mode...afterall...Eclipse has it still so what is Adobe trying to do? LOL