The 4.0 releases control the JVM's -Xmx memory limit via C:\Users\<your_userid>\AppData\Roaming\sqldeveloper\220.127.116.11.0
in product.conf. This is in fact a minor naming pattern bug on Windows since it should be ...\sqldeveloper\4.<x>.<y> instead.
I recommend upgrading to the latest 4.1.5 production release unless you are accessing an old version of the Oracle database that the latest JDBC driver shipped with 4.1.5 no longer fully supports, but even then you should be using the 4.0.3 release. Note that the 4.1.x releases require Java 8, if you do decide to upgrade.
Just as an experiment, I tried 18.104.22.168 with an -Xmx setting of 5 GB (Add64VMOption -Xmx5120m) and was able display about 113,000 lines of ALL_OBJECTS (several of them, actually, via SELECT ... UNION ALL ...) with Task Manager reporting a working set size of 1,873 MB on an 8 GB machine. So I cannot recommend this brute force approach, but if you have the RAM and a 64-bit OS, it should work fine.