Loading ...

Blob

Smart Reasoning:

C&E

See more*

Qaagi - Book of Why

Causes

Effects

# We also needto setgarbage collection mechanizm

Because...http://www.google.com/patents/US6349312?utm_source=gb-gplus-sharePatent US6349312 - Method and apparatus for performing pre - allocation of memory to avoidtriggeringgarbage collection operationsAdvanced

the need for the stat commandwas causinggarbage collection issues

the garbage collector ... we needto manually triggergarbage collection

gb ssd ... You do not needto setup garbage collection

And you even do n't needto triggerthe garbage collection

circular referencepreventsgarbage collection

a held referencepreventinggarbage collection

the given function ... functionsmay triggergarbage collection

A live referencewill preventgarbage collection

reference to srHolderto preventgarbage collection

some reference cycleis preventinggarbage collection

The exported referencecan preventgarbage collection

a reference to m_valueFactorymight preventgarbage collection

a reference to ' thispreventsgarbage collection

a reference to the bufferto preventgarbage collection

cyclic referencepreventfrom garbage collection

a reference should be maintainedto preventgarbage collection

the exact referencesare preventinggarbage collection

Storing referencespreventsgarbage collection

Strong referencespreventinggarbage collection

stray referencespreventgarbage collection

valid referencespreventgarbage collection

The remaining referencespreventinggarbage collection

MonoTouch object referencepreventinggarbage collection

the printout ... not not which functionmight have causedthe garbage collection

the pointer ... any functionmight causea garbage collection

the weak reference ... strong enoughto preventgarbage collection

to keep a reference to that other object in scopeto preventgarbage collection

circular references in memorypreventsgarbage collection

An allocation in a timemay causegarbage collection

creating a reference type instancecan causegarbage collection

The second object allocationmight causea garbage collection

any memory allocation in the processcan ... triggera garbage collection

# Hold references to objectsto preventgarbage collection

cyclic references between objectscould ... causegarbage collection issues

The finalizer references the finalized objectpreventinggarbage collection

the allocation inside the callbackwill triggerthe garbage collection

the large allocationis triggeringa garbage collection

The next allocationcan triggera garbage collection

all the performance issues(passive) caused byall the performance issues

application pauses(passive) caused byapplication pauses

the total pause time(passive) caused bythe total pause time

Java performance problemsis creatingJava performance problems

noticeable pauses in the applicationcan causenoticeable pauses in the application

long pauses in the computationcan causelong pauses in the computation

long pause time(passive) caused bylong pause time

problems for your applicationcould be causingproblems for your application

performance problems , and point out memory leaksis causingperformance problems , and point out memory leaks

system pauses(passive) caused bysystem pauses

the unavoidable pauses(passive) caused bythe unavoidable pauses

dramatic pausescould causedramatic pauses

longer pauses(passive) caused bylonger pauses

not all pauses in Firefox(passive) are caused bynot all pauses in Firefox

garbage collection Performance problems(passive) caused bygarbage collection Performance problems

pauses in the execution of the applicationmight causepauses in the execution of the application

annoying pauses during gameplaycan causeannoying pauses during gameplay

several potential bugs that occur in manually managed memory , such as dangling pointers , double free errors , and several types of memory leakspreventsseveral potential bugs that occur in manually managed memory , such as dangling pointers , double free errors , and several types of memory leaks

problems with performancecan causeproblems with performance

a memory leakpreventsa memory leak

long pauses in your app(passive) are ... caused bylong pauses in your app

problems in our gameis causingproblems in our game

memory problems(passive) to be prevented bymemory problems

semantic problemscausessemantic problems

pauses in the execution of the programcausespauses in the execution of the program

the system - wide pauses(passive) caused bythe system - wide pauses

non - deterministic pausescausesnon - deterministic pauses

the unpredictable pause times(passive) caused bythe unpredictable pause times

some serious performance problems , especially in multithreaded applicationscreatessome serious performance problems , especially in multithreaded applications

the long pause times(passive) caused bythe long pause times

the pause time or memory consumption(passive) caused bythe pause time or memory consumption

dropped frames as it pauses to clean up memorymay causedropped frames as it pauses to clean up memory

performance problems and suggests more appropriate command line optionsis causingperformance problems and suggests more appropriate command line options

latency spikes(passive) caused bylatency spikes

long pauses while the JVM reorganizes memorycan causelong pauses while the JVM reorganizes memory

annoying delays in playcausingannoying delays in play

occasional extra delaysmay causeoccasional extra delays

delays in running programscan causedelays in running programs

critical delays in your software(passive) caused bycritical delays in your software

prolonged user - interface pausescan causeprolonged user - interface pauses

Blob

Smart Reasoning:

C&E

See more*