search : garbage collection

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

displaying top 100 results

Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by Rupesh K.
Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by External U.
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by External U.
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by External U.
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by Vamseekrishna N.
2596973 CF-3286878 External U. Performing a garbage collection does not help, as they are still referenced in the thread.
2597097 CF-3119991 External U. Heap does not evacuate "coldfusion.util.key" when garbage collected.
ObjectLoad() Component Never Garbage Collects / ObjectLoad() = Memory Leak
Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by External U.
3015864 CF-4198534 Jonas M. John: The high CPU might have been caused by constant full GCs due to the leaked memory. I've found that the following will allow the leaked memory to be garbage collected: Use at your own risk.
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by External U.
2614276 CF-3120864 External U. Heap does not evacuate "coldfusion.util.key" when garbage collected. Changing GC routine from UseParallelGC to alternates does not alter problem.
Objects can't be garbage collected during a request
Comment on Objects can't be garbage collected during a request by External U.
Comment on Objects can't be garbage collected during a request by External U.
collection and this process taking long enough as to exceed the server timeout setting. If this is the case, try adding the -XX:+UseConcMarkSweepGC java option" We run a somewhat similar process to personalize data for real estate agents. Our garbage collection is configured with "UseConcMarkSweepGC" (it
Comment on ObjectLoad() Component Never Garbage Collects / ObjectLoad() = Memory Leak by Dave D.
2596957 CF-3312296 External U. Please note: There may be a correlation between the CF server doing a Garbage Collection and the missing email. This is very hard to track since all the ColdFusion logs show 100% of email went through but the receiving SMTP server logs that 99% actually got
Tracker Issue JVM setting to G1GC
2673023 CF-4156095 Wishlist James Mohler JVM setting to G1GC Java is moving to use G1GC as the default garbage collection on the initial install. ColdFusion really should be moving to that too. Unless there is a documented reason why not ----------------------------- Additional Watson Details
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by External U.
Comment on Page response byte buffer cannot be Garbage Collected when storing CFC in Session by External U.
.udf = function() {} The left-hand side persists after evaluation, as it is an application-scoped variable. Whereas the right-hand side is garbage-collected after it runs.
Comment on Objects can't be garbage collected during a request by External U.
[…] The post Thread Dump Analysis using Performance Monitoring Toolset appeared first on ColdFusion. Blog,Uncategorized,garbage Collection,Heap dump,Performance enhancement,Thread dump
ColdFusion application. These scenarios covered the most common problems that developers encounter while dealing with your ColdFusion application. It covered, Issues around JVM – Gain insight on the various JVM metrics, memory management and garbage collection. Database issues – Get a good sense of how
Comment on ObjectLoad() Component Never Garbage Collects / ObjectLoad() = Memory Leak by Piyush K.
Comment on ObjectLoad() Component Never Garbage Collects / ObjectLoad() = Memory Leak by Piyush K.
's created in cf9 stay referenced under a java object and this is why they are not garbage collected. The cfc's in memory comprise of CFdummycomponent, variablescope and some other java objects. Because the references to them are kept, even though they are not referenced in coldfusion anymore, java cannot
templates, since even before script-based components were available. It's a common method of defining UDFs. A closure, when scoped should be treated as a static. The right side, is certainly not "temporal" - unless it is var-scoped for in-method usage, at which point it can be garbage collected when
Carl Meyer Hi Jose, Hard to say without enabling Java logging or management extensions (JMX), then read the log output or use Mission Control (JMC) to compare results. Performance could be effected if there are long pauses by full garbage collections. I have seen some CF11 Java 8 perform better
2611836 CF-3586424 Rupesh K. Brad, in general, the JVM does not run the GC on a fixed regular interval. It is completely up to the JVM to decide when to run the full GC. In case of RMI, since the objects are exported and used by other VM, the garbage collection is distributed and hence the name dgc
2596973 CF-3286878 Performance KlaasJan Winkel CFC Creation Memory Leak Duplicate ID: CF-3119991 Problem Description: Created cfc's within one request will NOT be garbage collected even if the coldfusion variable holding it is set to empty string or set to a new cfc/value. This is unacceptable
Page response byte buffer cannot be Garbage Collected when storing CFC in Session
!). Charlie knows way more about the inner mysteries of ColdFusion performance than I do, but I believe that if you do the manipulation inside a function, when the function exits, the references to variables created inside that function (apart from anything returned) are available for Garbage Collection, so I
.io.DeleteOnExitHook objects stay in the memory heap, eventually causing an out of memory exception. Expected Result: java.io.DeleteOnExitHook objects are correctly removed from the heap. Any Workarounds: Restart ColdFusion service whenever heap usage stays above 90% after garbage collections
make life easier when it comes to ending a user session. Especially when they are logging out and the session doesn't need to hang around for another 30 minutes (or whatever the inactivity limit is) until it expires and is garbage collected.Thanks :) Method: Result
Comment on ObjectLoad() Component Never Garbage Collects / ObjectLoad() = Memory Leak by Chris P.
5120594 CF-4203583 Aaron N. Hi all, I see one issue is that CF2018 doesn't garbage collect its superfluous S3 metadata when overwriting files, seemingly allowing some headers to grow past S3's 8KB limit for some file types. Example (just uncomment one section at a time, and start hitting F5
6502588 CF-4206045 A. B. Hi Jonathan, Yes, I agree that "a closure, when scoped should be treated as a static variable". And, yes, given the code application.myClosure = function () {} I agree with your point that application.myClosure "itself would be static and no attempt at garbage
2611836 CF-3586424 Installation/Config Bradley Wood gvInterval JVM args no longer work Problem Description: In previous version of coldfusion, the JVM args -Dsun.rmi.dgc.client.gcInterval and -Dsun.rmi.dgc.server.gcInterval could be used in jvm.config to increase the frequency of major garbage
no threads are shown as actively running, monitoring the memory usage shows that is slowly being consumed. Using FusionReactor and inspecting the PermGen memory space found that it was continuing to grow. Forced garbage collection recovers no memory even though there is no traffic on the server other than
2612313 CF-3527009 Language : CF Interfaces Jork Zijlstra Caused by: java.lang.NullPointerException On CreateObject Problem Description: We get an nullpointer exception on the createObject(). Steps to Reproduce: We are not sure, jvm has enough memory. We think: 1) concurrency problem 2) garbage
in the underlying Java classes that implement closures in CFML. I am astonished you should say that Var has nothing at all to do with this. Var scoping is relevant whenever you define a variable within a function in ColdFusion. It helps in marking objects for garbage collection, hence in reducing the risk