tracker issue : CFB-4029822

select a category, or use search below
(searches all categories and all time range)
Title:

Builder hangs with 100%

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Bradley Wood / Bradley (Bradley Wood)

Created: 08/01/2015

Components: Performance

Versions: 3.0

Failure Type: Performance Issue

Found In Build/Fixed In Build: 3.0 Final /

Priority/Frequency: Major / Not Reproducible

Locale/System: English / Windows 7 SP1 64-bit

Vote Count: 0

Problem Description:
While editing a script CFC, Builder will occasionally hang and consume 100% of my CPU.  I have to kill the process and restart the editor.

I am attaching a series of stack traces that I pulled from the CFBuilder.exe process via jstack while it was unresponsive and consuming 100% of the CPU that show what the JVM was doing.  Perhaps the running thread will provide some helpful information.

Steps to Reproduce:
Seems random, but it happened 3 times today in the same file.

Actual Result:
Program hangs, consuming entire CPU.
 
Expected Result:
Program shouldn't hang.

Any Workarounds:
None

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4029822

External Customer Info:
External Company:  
External Customer Name: Bradley
External Customer Email:  
External Test Config: My Hardware and Environment details:

Attachments:

Comments:

Hi Bradley , We are unable reproduce the issue while editing the script CFC file . Can you please provide script CFC file on which builder will get hang and consume 100 % of CPU.
Comment by Mukesh K.
26700 | August 18, 2015 11:37:15 PM GMT
Did you look at the stack trace I attached? I do not know how to reproduce it on demand, but I did capture all the threads running in CF Builder's JVM at the time.
Comment by External U.
26701 | August 19, 2015 12:04:04 AM GMT
reproducible, but this is more or so related to builder bad memory management like cpu usage and crash on intensive usage(not scalable) this will be taken later with rest of the memory issues. and this is reproducible in 3.0 too.
Comment by Milan C.
26702 | February 02, 2016 04:37:04 AM GMT
Issue is fixed, and this will be available via update 2. (Comment added from ex-user id:prk)
Comment by Adobe D.
26703 | May 04, 2016 04:35:38 AM GMT