This has been a problem for a long time and there have been a bunch of threads about it, with no definitive answers for how to fix it.
Here are a few previous examples that describe the problem nicely:
sqldeveloper64W.exe has stopped working
SQL Developer 4.1.2 (64 Bit) Crashes on MS Windows 7 When Double Clicking SQL Script File to Open
So has anybody actually figured out a real fix for this? Lots of threads mention things like changing your shell association to sqldeveloper64W.exe instead of sqldeveloper.exe. This does not solve the problem. Also lots of talk about cleaning up the file associations in your registry, this also does NOT appear to solve the problem permanently. And using 32 bit SQL Developer isn't an option for me because I often have to do large exports that cause it to run out of memory and grind to a complete halt.
In general, the problem seems to typically go away for a while if you reboot so lots of the "solutions" that have been posted for this don't actually solve it, but they trick people into thinking it's solved because they involve a reboot. If you comb through all the threads made over the years about this problem there's lots of instances of someone thinking their problem was solved only to come back a few days later a say that it started happening again.
It's been years now dealing with this, eagerly downloading each new version hoping it's finally fixed and nothing. It's really, really frustrating.