Posts Tagged ‘Flash Builder’

JRockit JVM with Flash Builder 4, Performance .ini Settings

Friday, February 7th, 2014

Flash Builder performance can be increased with the use of JRockit JVM.

Good post by Mike Cann on the process

The FlashBuilder.ini setting I am using are below (Window 7, 64 bit Flash Builder 4.7)

-vm C:/Program Files/Adobe/Adobe Flash Builder 4.7 (64 Bit)/jre/bin

Eclipse/Flash Builder 4.7 Hanging on Loading Workbench

Thursday, January 16th, 2014

Firstly, go to the .metadata folder of the workspace in question.
Open the .log file, and see if it contains the following:

!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

The recovery can sometimes fail, which will prevent Eclipse from loading, and will hang on the splash screen.

Try the following: Go to,


And delete the .snap file (make a backup first of course)

Your workspace should now open ok… hopefully.

.snap files represent the changes in workspace state of the IDE during the runtime. This is mostly for eclipse crash recovery plan. When a crash happens these files are used to recover the state fo eclipse workspace.



Flash Builder/Eclipse Breakpoint Working Sets

Wednesday, February 27th, 2013

As a way of managing (sharing, exporting, or importing) breakpoints, the Working Sets feature of Flash Builder/Eclipse can be used.

There are many occasions when I will have dozens of temporary breakpoints set while working on a particular issue/task, and at the same time I will have some permanent breakpoints that I wish to monitor regardless of the task I am working on. When the temporary task is completed, I usually just want to delete all the breakpoints in one go, but it can be tedious having to go through and deselect all of the permanent breakpoints. This is where Working Sets can come in very handy.

I have a default Working Set (WS), and any breakpoints that I create automatically get set under this WS. I also create a secondary WS, and call it Permanent, and simply move the permanent breakpoints to this WS. In the Breakpoints tab, hit the down arrow, and select Working Sets and create some new ones. Then set the default working set.

Create, then set the Default Working Set

Create, then set the Default Working Set

Group you breakpoints by Breakpoint working sets:


When Deleting breakpoints, just select the Default WS and hit the single X button. The Permanent breakpoints will be left as is. Voila!

Delete just the Default breakpoints

Delete just the Default breakpoints


Flash Builder 4.6 – Conditional Breakpoints

Wednesday, September 5th, 2012

When debugging an application, in FB 4.6 one can now set conditions on when a breakpoint is activated. This can be very handy when you want to know when a certain condition is met on a piece of logic without having to set up IF statements, traces or debug logs.

Right-click on the breakpoint in the Breakpoint window to set the BP Properties. The conditions are set as shown in the picture, and you can only reference the objects/parameters that are available at that exact breakpoint line.

Setting Conditional Breakpoints

Flex/Flash Builder – Update JRE, .ini, Increase Memory

Tuesday, May 22nd, 2012

Working with Flex Builder 3 project, and getting the odd ‘out of memory error’ on Windows 7 64bit. Can also be done for Flash Builder 4.6

The following steps helped to speed things up and alleviate the problem (so far!)

1. Check what version of the JRE FB is using Help>Product Details>Configuration (even if you have the latest, FB will probably have defaulted to JRE 1.5 which comes with the install)

Configuration Details

2. Download the latest Jre (use the 32bit version – as FB3 is 32 bit Eclipse)

JRE 6 can be downloaded here

Install, and copy the Jre Files from: C:\Program Files (x86)\Java\jre6 to C:\Program Files (x86)\Adobe\Flex Builder 3\jre (and keep backup of original of course just in case)

3. Increase the memory for FB3 – C:\Program Files (x86)\Adobe\Flex Builder 3\FlexBuilder.ini


You can only increase the memory so far, otherwise FB will fail to load (let me know what values you got away with!!)


Adding -showlocation before vmargs will display the current workspace in the title bar of FB

Adding -refresh, -clean clears the FB4 cache. Faster Garbage Collection: -XX:+UseParallelGC

Disable FB4 Validation: Window>Preferences>Validation (disable all but Class Path Dependencies)