It's a bug in Java 8, fixed in Java 1.8.0_202 (see also this SO answer). message is just a warning, and not the reason for Fiji hanging at startup. Windows RegCreateKeyEx(.) returned error code 5. The Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. This needs to be fixed, but it's not the reason for Fiji hanging at startup. The new launcher has a regression where the console always pops, even when not passing the -console flag. ImageJ-win64Īfter some analysis, here is what and I have concluded: The fact that no one has reported it before is a good sign, suggesting that either: A) it only affects a small fraction of win32 systems or B) there are very few people using win32 in general these I discussed with Here is how we want to proceed with the two issues discussed here. I'm guessing this has been an issue for quite some time for people who continue using 32-bit systems. But in order to do that, we'd need to publish a new version of the 32-bit launcher with a lower limit. Of course, hacking your ImageJ.cfg locally will not fix the launcher for everyone in a similar situation. Try lowering it to 1.1GB or even 1.0GB? You should be able to hack your ImageJ.cfg to change the limit. Historically, 1.2GB was pretty safe, so the launcher caps it there-but I guess it's not good enough anymore on modern systems. No one (to my knowledge) ever found a way to safely detect this upper bound on a per-system basis. You'll notice it's only 1.2GB: seemingly far less than the 2GB limit, right? But the 32-bit Windows JVM is notorious for actually allowing much less as a maximum IIRC memory is shared with Windows itself? So the cap varies depending on your system and version of Windows. That's the dreaded "trying to allocate more memory than a 32-bit JVM supports on Windows" bug. Could not reserve enough space for 1253376KB object heap
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |