Thanks for downloading 4.1.5 , sorry you are having trouble with it.
I'm on Windows 7 64 bit myself, and haven't been able to reproduce your issue.
But from your details it does sound like a memory issue. Either with SQL Dev or the machine.
Just as a bench mark My SQL Dev is running with about 500mb reserved and using between 50mb and 250mb when I check with Java VisualVM) . My Windows processes says 620mb.
First I'd check I have sufficient memory using Window Processes and make sure something else isn't eating up all the memory.
If the memory looks ok we could try lots of things to narrow down the problem , but if your like me and just want to get up and running I would try a clean install.
To do this I would
1) Export my connections. Right Click on the connections icon and choose "Export Connections", follow the wizard and save the connection details to a file.
2) Quit SQL Developer.
3) Backup your "SQL Developer" system directory so that it can't be found on restart.
I renamed C:\Users\dermot\AppData\Roaming\SQL Developer\system220.127.116.11.78 to C:\Users\dermot\AppData\Roaming\SQL Developer\system18.104.22.168.78.bak
4) Start SQL Developer and choose "No" when prompted about importing preferences from previous install.
5) Once SQL Developer has started import the connections from the saved file.
You will loose any preferences you had, but you will have a clean startup of SQL Developer which has in the past resolved some tricky issues.
Hope that helps
SQL Developer Team.
Those are pretty surprising numbers, and fortunately do not match my experience switching between 4.1.3 & 4.1.5, on my laptop. The times for doing all the tasks you mention do not vary much for me between the two versions. The only thing I tend to do is install the latest JDK and make SetJavaHome in product.conf the same for as many versions as possible (in ...\sqldeveloper\4.1.3, ...\sqldeveloper\4.1.5, and so on). Doing that will override use of the embedded JDK, and eliminate the overhead of loading / switching between multiple versions of Java. I also am using the default -Xms and -Xmx memory limit settings.
I downloaded the sqldeveloper-22.214.171.124.78-x64.zip file, and installed it as usual,
You say "installed it as usual". Does that mean both installs (as well as their user settings under ...\AppData\Roaming\...) are on the same disk (local disk)? Something must be different in your environment. You can use Help > About > Properties to see which JDK on disk is being used, and Help > About > Extensions (scroll way to the right) to see the total registration and load time for all the extensions. Maybe that will help shed some light, although the total extension time tends to make up only about 1/3 to 1/4 of the total startup time.
copying my preferences from the previous version (126.96.36.199).
I guess you mean "migrating my user settings from the previous version"?
Edit: I see Dermot also replied, which reminds me that using a 32-bit JDK will reduce the memory footprint. Good luck with working through this issue!
Thank you. That resolved my issue