Objects in Memory
References, garbage collection, and what == really compares.
0 of 22 answered
Start here
Copying an object with a list inside
Foundation
- Not triedCopying an object with a list insideFoundation
- Not triedPassing an object and changing it anywayFoundation
- Not triedReturning null or an empty listFoundation
- Not triedThe variable and the objectFoundation
- Not triedWhat == comparesFoundation
- Not triedWhen an object can be collectedFoundation
- Not triedWhere things liveFoundation
- Not triedWhy strings are immutableFoundation
- Not triedA list passed into a constructorCore
- Not triedClosing what the collector will notCore
- Not triedHow long a static field livesCore
- Not triedThe cost of many small objectsCore
- Not triedThe file handles the collector did not closeCore
- Not triedTwo objects that share one listCore
- Not triedA leak with a garbage collectorChallenge
- Not triedA pause with no code runningChallenge
- Not triedA reference that does not keep an object aliveChallenge
- Not triedThe fix, and the one that only looks like a fixpart of Memory that is reachable and uselessChallenge
- Not triedThe hidden referencepart of Memory that is reachable and uselessChallenge
- Not triedThe object that vanishes from the setChallenge
- Not triedWhat is passed to a methodChallenge
- Not triedWhy the collector keeps thempart of Memory that is reachable and uselessChallenge