SQL Developer Memory Leak

I have been using SQL Developer in lieu of DbVisualizer and Toad for the past year for no other reason that it is free. It is pretty handy and does the work quite well if you’re working with an Oracle database, but it’s been giving me a lot of hassle lately.

After some time, it takes quite an awful lot of memory… Making its use impossible, but also making the whole machine an absolute nightmare to work with. Here is a snapshot I’ve taken yesterday:

As you can see, SQL Developer takes more than 600k of RAM, and takes CPU resources for quite some time, whilst Eclipse is living happily with 300k.

The only solution is then to kill the process and restart it… To me, that sounds like a memory leak, and should be addressed quite quickly because it makes the application totally unusable.



  1. This happens all too often :(

    I would love to use SQL Developer over TOAD but this makes the decision hard.

    élza · 2009-05-28 21:00 · #

  2. Tell me about it, brother. Painful.

    Brett · 2011-03-15 13:13 · #

  3. I totally aggre, I’m facing the same problem with my SQL developer, The problem I have is that I need to handle several connections to different databases at the same time. and this big has become a pain for me. I hope someone here can give us a good workaroud

    Kevin · 2011-06-17 22:50 · #

  4. I also use the same sql developer.
    After quite some time, it is indeed eating up memory, you just need to clean up the temp files, and all history.

    I just did that, and it works quite well now. Scratch that, it works well. :D

    All those unnecessary files are kept here:
    C:\Documents and Settings\<your_user_id>\Application Data\SQL Developer.

    1) Just empty the SqlHistory.xml (not quite sure, what will happen if you delete this file, better just empty it)

    2) all files in tmp folder

    3) search for all files with size > 1MB, you may find files without extension, with weird file name, like “1306994194387”, in folder C:\Documents and Settings\<your_user_id>\Application Data\SQL Developer\systemXX.XX\.history\. Just delete those files

    That’s it.

    Roswara · 2011-12-22 03:21 · #