tracker issue : CF-4198293

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

CfChart causes serious memory leak leading to crash

| View in Tracker

Status/Resolution/Reason: Closed/Withdrawn/Duplicate

Reporter/Name(from Bugbase): Nikhil Roy / Nikhil Roy ()

Created: 01/29/2017

Components: Charting/Graphing

Versions: 2016

Failure Type: Memory Leak

Found In Build/Fixed In Build: 2016.0.03.300466 /

Priority/Frequency: Normal / All users will encounter

Locale/System: English / Win 2012 Server x64

Vote Count: 1

Problem Description: We migrated our application on a new server instance with Coldfusion 2016 and within 2 days, CF crashed with no real hint of the cause. This repeated several times every 1-2 days and a couple of times we got out-of-memory errors which sent us down this track. We increased memory to extend the uptime but eventually caught up again. finally investigated the heap dump and found multiple (millions) of instances of the org.mozilla.javascript.NativeObject using about 90% of memory. 

Steps to Reproduce:Use cfchart in certain scripts and executing them causes this memory leak, unsure how many times we need to execute the tag but surely not more than a couple of hundred.

Actual Result:Out of memory over time with often no resources to include actual error in log files. We are happy to provide more log files, heapdumps, etc to assist with the bug fix.

Expected Result:Memory release as part of Garbage cleanup.

Any Workarounds: We have commented out the cfchart tags across the system and found the system stable (up for 10 days now without reboot), we will replace with native javascript graphs to get around it.


  1. January 29, 2017 00:00:00: Memory Leak Suspect 1.JPG


We have confirmed this to be source of the leak, after commenting out the cfchart tags, we have been running on a production environment with 0 performance issues and 100% uptime.
Comment by Nikhil R.
1279 | February 15, 2017 10:01:37 PM GMT
Why has this been withdrawn? It's a real bug that I've just experienced. I will open a new bug ticket.
Vote by Gary F.
1284 | April 18, 2017 12:47:00 PM GMT
This is withdrawn as a dupe of CF-4198357 which is fixed
Comment by Vamseekrishna N.
1280 | April 18, 2017 01:04:28 PM GMT
This is still a reproducible fault in CF2016 Update 3 (latest release). I'm created a new bug CF-4198534 and preparing a script to repro the bug and will email it to Adobe.
Comment by Gary F.
1281 | April 18, 2017 02:10:49 PM GMT
I am not sure why this issue is still closed, if this is a duplicate can you please direct me to the actual issue which will address the bug. If not , can you please explain why this bug is closed even though it was reproduced by your engineers.
Comment by Nikhil R.
1282 | September 05, 2017 06:25:15 AM GMT
@Nikhil This bug was marked as a duplicate of Bug# 4198357. This bug is fixed and should work fine after applying HF4.
Comment by Dattanand M.
1283 | September 05, 2017 06:51:28 AM GMT