- Joined
- Mar 17, 2007
- Messages
- 9,304
It would be interesting to hear how someone else's experience goes with it, and that way if there is an issue I can optimize that area before you're ready to do it for real. I have imported large maps, but I have generally had plenty of memory.
The PC is old and slow. Systemsteuerung (sorry, no idea how it is labeled in the english version of Windows) says that it has 2,0 GB of RAM.
The Editor allways runs out of memory, when I swapped the unit/building list from old (fixed) to new (swing) listing. After restarting the editor, it runs without memory warnings (except that I do not check the logfile each time).
This is what your editor says with my huge BIQ-file open:
PS: I have added in the mean time two new units (one air, one land) with the new version: Both are lacking the "Go to City X" button in game (as the Porsche Tiger pictured on the previous page of this thread).
I will have to think about the always-running-out-of-memory thing. The dialog does indicate it should be able to use up to 250 MB or so - and that Java already has permission for that - and as long as you don't zoom out, it looks like you are probably okay - at the least, you are well below the limit at the time of that screenshot. I'd been afraid perhaps it only had 64 MB or so, but while 250 MB is quite a bit lower than the limit on newer systems, it isn't super-low.
But that does let me know what to test it with - I can set up my system to simulate only having 250 MB available.
I'm also somewhat familiar with old systems - the laptop I typically use is from 2007, although it does have 3.5 GB of memory. It's amazing how much I can still do on a system from 2007 with an operating system from 2001, though, even considering a couple hardware upgrades over the years. But that being my laptop, as well as being on XP as a main OS until last year, is why I'd like to keep things working on older systems.
---------------
As for the crash, I have verified that something in the switch from Java 1.8.0_131 to 1.8.0_151 caused the issue, testing back and forth with both. Still investigating what I can do from a code standpoint to work around it - but in the meantime, I found a somewhat clunky workaround. When I copied the glass.dll file, which the Java crash indicated was where the issue occurred, from my _131 install into my _151 install folder, it fixed the problem.
To work around the issue locally, go to C:\Programme\Java\jre1.8.0_151\bin\, and rename glass.dll to something like glass_backup.dll. Then download the update 131 version I uploaded here (on my e-mail's file storage system), and save it as glass.dll in the same folder. The new lists should now work properly - at least, it did when I followed the process locally. If it works worse than before, there's still the backup.
I'm investigating the interim Java updates to see where exactly it broke, and may file a bug report or think of a way to work around it from an editor standpoint, as opposed to overwriting a DLL file (which may have to be repeated when Java updates itself). But that should get it working for now.
I'll take another look at the go-to-city issue and see if I can reproduce that.
------------
Update: Investigated the crash more, it was update 151 that introduced the issue. I was also able to reproduce it with almost the simplest possible JavaFX code, so I'm now confident that it is a bug in Java and not in the editor's use of Java. There is an update 152, but it doesn't solve the issue.
The downside is that as almost the simplest possible JavaFX code triggers this issue, it is very unlikely that I could work around it. However, the copy-pasting of the older glass.dll does seem to work. The upside is that as this can be reproduced using very simple code, there is a chance that it might be fixed in a future Java update.
Whether it will be fixed after I submit a bug report, I don't know. XP isn't officially supported, but Java 8 has run on it for years and I know they've fixed some XP-specific issues in the past. It also seems to be a fairly noticeable bug.
I'm currently trying to install Windows Vista on my laptop so I can see if the issue occurs there (it does not occur on 8.1, with the same update of Java). Vista is officially supported for Windows 8, so if it happens there it's more likely that it will be fixed. I don't have Windows 7 to test with, but if it happens there the chances of it being fixed would be much higher. If anyone has 7, testing the new "Add"/"Rename" buttons for units would be appreciated!
Last edited:
). 
