Reporting one-off issues with CFBuilder

Would like to put a note here to all our beta users and request you to report to us any instability issues that you might hit upon while using CFBuilder. For example, such issues could be something like editor becoming unusable, IDE freezing up, editing becoming unusually slow, system slowing down due to use of CFBuilder, certain file/operation causing editor to behave abnormally etc. Since such cases or any other similar ones are either not very consistently reproducible, or they do not have any straightforward reproducible pattern, in order to report them to us you need to launch CFBuilder from console, take a thread dump, attach and upload it in forums or mail it to
Here is how you can do it:
On Windows – Start CFBuilder from console as CFBuilder.exe -consolelog -debug and keep using it. Once you hit upon the issue, take the thread dump using Ctrl+Break.
On Mac – Start CFB from Mac console. Go to /Applications/Adobe ColdFusion Builder/ Then run ./CFBuilder -debug -consolelog. Use the “ps” command to find out the process id (pid) of the Java VM. Invoke “kill -3 ” where is the process id of the Java VM.
A thread dump will be printed on the console where you started Eclipse. Since it may be long, in order to Copy & Paste it, it might be necessary to scroll and/or reduce the font size (xterm: right-click > font size > unreadable).
Alternatively, you can use the handy stacktrace tool at
All you need to do is to select the CFBuilder process id from the current list of processes and get the thread dump. The tool is free if you use Java Web Start to download it. And works on MAC, Linux & Windows.
Follow the link and select button “Launch” (press “OK” to “Run as a Java WebStart Application”)
Select menu Process > Select
In the combo box “Process ID” press the “…” button, select application and click OK
Pick menu Process > Thread Dump
File > Save As (enter some name e.g. C:\myThreadDump.txt)

Comments are closed.