I tried running 4.0 EA3 on my Windows 7 64-bit PC with the 64-bit JDK. I then immediately got a warning about my roaming profile exceeding the maximum space allocated. We have 60 MB allocated and I was using 30 MB or less prior to running EA3.
It appears the culprits are the files in %APPDATA%\SQL Developer\system22.214.171.124.30\system_cache\var\cache, specifically the all-resources.dat file which was just over 30 MB in size. I can delete this file, but it of course is re-created when SQL Developer is run again. Since these are cache files, should they perhaps be stored somewhere in %LOCALAPPDATA% instead?
I had not tried the previous EA releases, so I do not know if this is specific to EA3 or not. I have not had this problem with releases prior to 4.0, though. Our developers will not be able to use 4.0 in our environment if it blows their roaming profile space allocation.
SQL Developer 4.0 inherited the system_cache requirement from the latest JDeveloper IDE framework on which it is based. To avoid the maximum space limitation your admins have placed on the roaming profile, try adding a line to your sqldeveloper.conf file:
where <path> begins with something other than %APPDATA%
Hope this helps,
SQL Developer Team
Try running sqldev with the option -J-Dorg.netbeans.core.update.all.resources=never or by setting
in your sqldeveloper.conf file. For all possible values of this property--never, missing & always) see the bug we used to track this: