Loading Stalls

[HercMighty]

Hardy,

Trying to diagnose why the Aerowinx loading screen will come up and will stall at 79% (A few times at 63%). I always start the simulator before starting any addon and I have been able to force quit java.exe in Windows Task Manager and restart the application and it will most often then go.

But something will stall it on load and no amount of waiting sees the application actually start (Only seen as a Java process running, isn't shown as an application running on the application page).

Any ideas, or a log I can look at to see where it might be getting stuck? Once it's up there is no issues with the sim...

Thanks

running on Windows 7 Java 1.8.0_25b18 64Bit.

[Balt]

Same here on OSX, it stalls about 1 out of 10 times on the MacMinis. It's only happened once or twice on the Macbook Pro (which is a lot beefier).

When it stalls, it does so always at 79%.

Cheers

- Balt

[Hardy Heinlin]

I've never got such a problem on my OSX. How much RAM is free when you start it? Are any other programs running?

Are you sure you always use AerowinxStart.jar and not Aerowinx.jar?


Regards,

|-|ardy

[Balt]

The MacMini's have 4GB of RAM, after loading 2 (two) instances of PSX, 3.6GB are in use. There's noticeable load on them, i.e. the GUI slows down a bit when moving Finder windows etc, but it's far from being deadlocked.

I have a link on the desktop to the AerowinxNetStart.jar, so definitely this is not a case of running the wrong jar. I just tried running that from the terminal, but that yields zero output, and after the two instances are started, returns to the command line without having written anything. I suppose your forking two new JVMs there?

Cheers

- Balt

[Hardy Heinlin]

To start Aerowinx.jar directly (without AerowinxStart.jar) from the terminal, you need to enter:

java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar

This is actually what AerowinxStart.jar does; it tries to reserve 500 MB of RAM for the JVM before the Aerowinx.jar loads. If you then get around 300 to 400 MB -- that's normal (see "About" page). The "Interfaces" path is required for the 3rd-party USB and sound libraries.


Cheers,

|-|ardy

[HercMighty]

Hardy,

I will double check some things tonight, but I know my PC has 8G RAM and I am using the proper start file.

Like any Windows PC there will be some misc background files running but nothing that I thought should interfere with PSX loading. Why I was hoping of being able to see some type of log that might give a clue. But the fact that it will start without any changes is interesting...

thanks

[Hardy Heinlin]

When did this problem start?

[Will]

Loading stalls: I expected to find a discussion of aerodynamic stall characteristics at 45 degrees of bank... :-)

[HercMighty]

When did this problem start?

Seen it off and on in recent memory...but I believe it started with 10.0.1, but don't fully hold me to that...

It is more of an annoyance, but yesterday it was being a real pain...tried re-booting the PC and even that didn't help, but after the reboot, quitting Java.exe, it finally booted and was fine...

It's really odd and am not sure if it is something with the loading or my PC configuration...could be a combination of both, but be nice if it didn't happen...

[Hardy Heinlin]

It's really odd and am not sure if it is something with the loading or my PC configuration...

At this stage during the loading there are no system critical commands in my code. I'm 100% sure that my code is clean there. This part of the code has been executed a million times in the past years without problems. If you're saying restarting Java solved the problem, then I guess this is a bug in the Java version you're currently using. Which one is it, SDK or normal kit? And which OS?

What happens at this stage is the initialization of the Instructor frame. That contains many Java GUI commands. They are all standard actually. If there is a problem there, it must be a Java problem or a memory or graphic buffer problem, something like that, outside the PSX scope.


Regards,

|-|ardy

[Balt]

Wouldn't you know it... it just happened 3 times in a row today on the MacMini, always on the same one.

They have Java 1.8 rel 25 JRE installed.

It's stuck on the splash screen, 79%, no other GUI elements are showing.

Cheers

- Balt

[HercMighty]

unsure but I believe normal kit, 1.8.0 Update 25 64 Bit on Windows 7.

I hear where your coming from Hardy, just trying to figure out exactly what it might be so a final determination can be made if there is anything anyone can do...

Not saying it's PSX per se but it is the only Java application I have this issue with...

Though loaded today with no issue....

[Hardy Heinlin]

Balt and HercMighty, please try the developer kit version of your Java 1.8. I heard it has less bugs.


Regards,

|-|ardy

[HercMighty]

argh....now always stops at 79% and won't go no further....

Downloaded the Windows64 from here:

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html

[Hardy Heinlin]

Can you start PSX from the terminal and enter this? (Copy and paste.)

java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar

Are there any error messages?

[HercMighty]

Ok, got it started through the normal way...but ran it from the console and got this output when it started:

C:\\Simulator\\Aerowinx>java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx.jar

Jan 22, 2015 10:33:06 PM net.java.games.input.ControllerEnvironment log
INFO: Failed to initialize device  CP 1500C because of: java.io.IOException: Failed to acquire device (8007001e)

RudRatios not found

hope this helps....

[HercMighty]

Ok, this is what I get when it hangs:


C:\\Simulator\\Aerowinx>java -Xmx500m -Djava.library.path=Interfaces -jar Aerowinx
.jar
Jan 22, 2015 10:36:13 PM net.java.games.input.ControllerEnvironment log
INFO: Failed to initialize device  CP 1500C because of: java.io.IOException: Failed to acquire device (8007001e)

Exception in thread "main"
Exception: java.lang.AbstractMethodError thrown from the UncaughtExceptionHandler in thread "main"

[Hardy Heinlin]

Thanks.

got it started through the normal way

What do you mean by "normal way"?

OK, message analysis:

"net.java.games.input" -- This is 3rd party code that I can't control. It is used for PSX's USB interface. Are you having any problems with USB inputs? This message is just for "info", it seems.


"RudRatios not found" --- That's a normal message. This appears when an older situ is loaded which doesn't contain the RudRatios variable. The RudRatios variable has been introduced in PSX 10.0.1. If the situ doesn't have it, it's added automatically in the current scenario.


Exception: java.lang.AbstractMethodError thrown from the UncaughtExceptionHandler in thread "main"

That's interesting. Unfortunately it doesn't help because it's too vague, and it doesn't look like a PSX error, rather like a Java internal error. Was that the complete message?


|-|

[HercMighty]

Thanks.

got it started through the normal way

What do you mean by "normal way"?

OK, message analysis:

"net.java.games.input" -- This is 3rd party code that I can't control. It is used for PSX's USB interface. Are you having any problems with USB inputs? This message is just for "info", it seems.


"RudRatios not found" --- That's a normal message. This appears when an older situ is loaded which doesn't contain the RudRatios variable. The RudRatios variable has been introduced in PSX 10.0.1. If the situ doesn't have it, it's added automatically in the current scenario.


Exception: java.lang.AbstractMethodError thrown from the UncaughtExceptionHandler in thread "main"

That's interesting. Unfortunately it doesn't help because it's too vague, and it doesn't look like a PSX error, rather like a Java internal error. Was that the complete message?


|-|

Normal way was using my shortcut pointing to AerowinxStart.jar.

No problems with my USB joystick.

That was the full message.

[Balt]

I've now changed the way PSX is started on all three macminis, so when it happens again I should be seeing the terminal output. Can you confirm that when all goes well, there is no output at all being written?

Interestingly, the machines it was happening on three times in a row don't have any USB game controllers attached at all. The touchscreens are the only USB devices there.

Cheers

- Balt