Xuggle 5.4 is available

[legend80]

The builds from this forum.

Which Java version should I be using for best results in jpsp? The latest?

[serio]

java 1.6. don't use 1.7 until it goes out of beta and the emulator's adjusted to it.

[legend80]

Ok, I updated to java6u31. No change.

But then I tried the 32bit JPCSP and bam, complete stability. So it's an issue with the 64bit version or libs causing the instability.

Hopefully you can sort this out and find a good solution!

[Vegerunks]

Maybe its a RAM issue? because judging from your Sig you only have 4 gigs of RAM and I have no problems with the recent Revisions

[hyakki]

I've also have had no issues with using 64bit or 32bit and the new xuggle , is this only on a specific game ?
I went through every game I have in the umd browser and no crashes at all.

First make sure all your visual c++ runtimes, directx and drivers are all uptodate, since the xuggle dll is crashing is probably related to something like that and not jpcsp, check in your event log for more error information (Control Panel -> Administrative Tools -> Event Viewer).

Post any logs from jpcsp also (Debug -> Tools -> Logger -> Show Logger -> Select INFO. Load Game and run ) as well as any java console errors that appear (dont use javaw since it doesn't show the console.)

[legend80]

Maybe its a RAM issue? because judging from your Sig you only have 4 gigs of RAM and I have no problems with the recent Revisions

Only? That's plenty for pretty much everything. And why would it be a ram issue if it only happens on the x64 bit version and after the new lib integration?

I've also have had no issues with using 64bit or 32bit and the new xuggle , is this only on a specific game ?
I went through every game I have in the umd browser and no crashes at all.

First make sure all your visual c++ runtimes, directx and drivers are all uptodate, since the xuggle dll is crashing is probably related to something like that and not jpcsp, check in your event log for more error information (Control Panel -> Administrative Tools -> Event Viewer).

Post any logs from jpcsp also (Debug -> Tools -> Logger -> Show Logger -> Select INFO. Load Game and run ) as well as any java console errors that appear (dont use javaw since it doesn't show the console.)

It's only with Mega Man X (that I can see) in gameplay but both it and 3rd Birthday crash frequently when their tile is selected in the browser.

The jpcsp logs show nothing as noted before. Attached system crash info log from event viewer if it helps.

All my visual c++ runtimes, directx and drivers are uptodate.I even tried a build from emucr with the same results. I HATE it when no one else is seeing a bug that I am!!!

[legend80]

Not sure what more I can do here. Seems like a valid lib bug. Anything we can do to the x64 builds to alleviate this? Anything else you want me to try?

[gid15]

In your log file, javaw was reported. Could you try with java.exe as suggested by Hyakki to see if something is displayed on the console. Any hs_err_pid file created?

Also, post the log file when you can start the game and the crash happens during game play.

[legend80]

In your log file, javaw was reported. Could you try with java.exe as suggested by Hyakki to see if something is displayed on the console. Any hs_err_pid file created?

Also, post the log file when you can start the game and the crash happens during game play.

No difference in jave.exe. Not sure how to change that in the jpcsp launcher so I used the bat file.

New log of the crash (main menu) with logger set to ALL. It crashes at a different spot every time and shows nothing in any log. It just suddenly stops because of that one lib.

I can get it to crash 100% of the time in the umd browser by simply going back and forth between Mega Man and 3rd Birthday. Does NOT happen with my other three games: LBP, SFA3, Worms OW2.

I also did a clean install - created a new folder, extracted the latest build, changed the game dir, open umd launcher and bam, crash as soon as I clicked on MegaManX. I also removed all my tens of c++ redists and installed the latest of from ms (2005-2010, x64/86, sp1 and all).

[serio]

And why would it be a ram issue if it only happens on the x64 bit version and after the new lib integration?

as far as i know 32 bit system doesn't let you assign more than 2 gb of ram to any application and struggles with accessing 4 gb globally (usually gets less than that, mine only shows 3.5 gb total even though i also have 4). 64 bit removes that limit, so it can access all of it.

maybe that's related to the problem.