Skip to main content

Java: Strong References, Soft References and Weak References

There are many use-cases where we want to control, when our objects are collected by GC(Garbage Collector). Package "java.lang.ref" provides reference-object classes, which support a limited degree of interaction with the garbage collector. And GC reclaim the object memory based on it's reachability.

Strong Reference

Newly created objects are strongly reachable by the thread that created it. So object will be remain in heap till thread is running or some variable hold this object reference.

//leaking array
private static List<String> leakingArrayWithStrongRef = 
                                new LinkedList<String>();

    public void StrongReferenceTest(){
        try {
            for (int i = 0; i < 500000; i++) {
                String data = LEAKING_DATA + i;
                // Add data to our leaking array...
                leakingArrayWithStrongRef.add(data);
            }
        } catch (OutOfMemoryError ofm) {
            System.out.println("OutOfMemoryError");
        } catch (Throwable e) {
            System.out.println("UnexpectedError");
        }        
    }



imageHeap Memory trend chart when unwanted objects added in Array

In this example array hold the strong reference of string. As we start adding string object in array then heap memory increase to it's max limit and throws "OutOfMemoryEerror" exception.



Soft Reference

Soft Reference are the softly reachable object. These kind of object will remain in the heap memory till GC clean them out in need of memory.


//leaking array
private static List<SoftReference<String>> leakingArrayWithSoftRef = 
                                new LinkedList<SoftReference<String>>();

    public void SoftReferenceTest(){
        try {
            for (int i = 0; i < 500000; i++) {
                SoftReference<String> data = new SoftReference<String>(LEAKING_DATA + i);
                // Add data to our leaking array...
                leakingArrayWithSoftRef.add(data);
            }
        } catch (OutOfMemoryError ofm) {
            System.out.println("OutOfMemoryError");
        } catch (Throwable e) {
            System.out.println("UnexpectedError");
        }     
    }



imageHeap Memory trend chart when unwanted objects added in Array

In this example array hold the soft reference of string object. As we start adding string object in array then heap memory increase to it's max limit and GC reclaim the soft reference object from heap. And in this code you will not get "OutOfMemoryEerror".



Weak Reference

Weak Reference are weakly reachable objects. And these kind of object will reclaim by the GC at any point of time.


//leaking array
private static List<WeakReference<String>> leakingArrayWithWeakRef = 
                                new LinkedList<WeakReference<String>>();

    public void WeakReferenceTest(){
        try {
            for (int i = 0; i < 500000; i++) {
                WeakReference<String> data = new WeakReference<String>(LEAKING_DATA + i);
                // Add data to our leaking array...
                leakingArrayWithWeakRef.add(data);
            }
        } catch (OutOfMemoryError ofm) {
            System.out.println("OutOfMemoryError");
        } catch (Throwable e) {
            System.out.println("UnexpectedError");
        }       
    }



image Heap Memory trend chart when unwanted objects added in Array



In this example array hold the weak reference of string object. As we start adding string object in array then heap memory start increasing slightly and decrease after few seconds. It's happen because GC clean these object from the array more frequently. And in this code you will not get "OutOfMemoryEerror".



PS: I have used "jconsole.exe" to generate above graphs, which comes as a part of "JDK" toolkit.

Comments

Popular posts from this blog

ERROR: Ignored call to 'alert()'. The document is sandboxed, and the 'allow-modals' keyword is not set.

Recently I found this issue while writing code snippet in "JSFiddle". And after searching, found this was happening because of new feature added in "Chrome 46+". But at the same time Chrome doesn't have support for "allow-modals" property in "sandbox" attribute. Chromium issue for above behavior: https://codereview.chromium.org/1126253007 To make it work you have to add "allow-scripts allow-modals" in "sandbox" attribute, and use "window.alert" instead of "alert". <!-- Sandbox frame will execute javascript and show modal dialogs --> <iframe sandbox="allow-scripts allow-modals" src="iframe.html"> </iframe> Feature added: Block modal dialog inside a sandboxed iframe. Link: https://www.chromestatus.com/feature/4747009953103872 Feature working Demo page: https://googlechrome.github.io/samples/block-modal-dialogs-sandboxed-iframe/index.html

Application Design Notes

Don’t be afraid to write your own code, but be absolutely sure you need to Don't reinvent the wheel Learn more about your libraries and take full advantage  Date time calculation is hard ( leap second ,  leap year ), use trusted library  js-joda ,  momentJs ,  joda (java) Simple is better than perfect (nearly) every time If you can deliver a sub-optimal solution (that solves the problem but has known limitation) in a week instead of a full featured one in a month DO, IT Simple system are Easy to reason about  Easy to debug Easy to refactor Easy to learn Simple doesn't mean you skip good engineering, but you can use duct tape. Build things the right way from the start, refactoring is hard and expensive Security Manage and store passwords securely Telemetry Common retrofitting "grunt work" Internationalization + localization Web Content Accessibility Factoring and styling HTML UI Adding unit test to an existing codebase LOG LOG LOG Log, but do it right We spend lot of t

How to store user password at server!!!

Trick is, you should never store user password… never ever. Now the real question is, then how to authenticate and authorize the user with password. And answer is when user enter the password, we should encrypt the password and store the hints. So next time when user enter the password we follow the same process and compare hints, if both hints are same then password is matched, else it is wrong password. Next question will be, what kind of hints, and how to generate these hints. In simple term hints are the obfuscated and fragmented form of user password. And very important part is hints generation process, which have to be collision resistant , means there will be very less possibility to find the data which generate same hints (like Cryptographic hashing functions ). Below is the simple checklist of password hashing and storing, which you should always keep in mind. PS You're Probably Storing Passwords Incorrectly Storing Passwords - done rig