Open-ps2-loader: GUI freeze while creating VMC in 720p (HIRES)

[zappepappe]

Issue checklist

Note: these are not necessarily requirements

• [x] I have checked existing OPL issues for duplicates and found none @ http://psx-scene.com/forums/official-open-ps2-loader-forum/ & https://github.com/ifcaro/Open-PS2-Loader/issues

Open PS2 loader version

Since r1190 9df6607

Open PS2 loader mode (USB, SMB, HDD)

USB, SMB

Open PS2 type (Normal, Childproof, VMC, GSM, PS2RD)

Default

Issue description - Describe the problem you are having

While creating VMCs when in 720p (HIRES), and only in 720p, the OPL GUI will freeze at random. Leaving the only option to force shutdown the system. If waiting sufficient amount of time before shutting down, the VMC will be created correctly and working after reboot.

How to reproduce the issue

Set the GUI to 1280x720p (HIRES) and create a new VMC, preferably larger than 8 Mb as it doesn't take long enough to reliably trigger the freeze. Since it takes about 1 sec to make a new card with HDD, I haven't been able to reproduce it there.

[J013k]

It's been a while, but does this problem still exist in your setup?

I've tried new test build from here:
https://www.psx-place.com/threads/open-ps2-loader-v0-9-3.13415/page-41#post-202680.

It seems that everything seems to be fine through SMB.
I mean, I can without a problem create 16\32\64 VMC
while I've set V-mode:

• HDTV 1280x720p @ 60Hz 16bit (HIRES).

Haven't tried USB device so far.

[Tupakaveli]

I can't replicate this via USB either.

Testing with r1368 I am able to create 64Mb VMC in 720p Vmode without issue. Tested multiple times.

I did find a separate issue that seems to be GUI related though.

Once you create a VMC and go back into the Configure VMC screen you are unable to move the cursor to modify / delete it.

[Jay-Jay-OPL]

@Tupakaveli about the 2nd issue -- make sure "_Enable Write Operations_" is set to ON under OPL Settings. That is the way to be able to modify or delete a VMC you just created. NOTE: That setting doesn't need to be enabled in creating a VMC, but for other more advanced options, you need to enable it.

[Tupakaveli]

Yeah I didn't realise I had it off.

Anyway this issue should be closed since it can't be reproduced.

[zappepappe]

I will try to test it in the coming days. My PS2 is currently stored away, that's why I haven't tested it earlier.
If I'm unable to reproduce it on newer versions I will close the issue.

[J013k]

Any progress?
Does this issue can be closed or it can be reproduced in some way?

[zappepappe]

Sorry, had a fuller week than I thought I would and got a bad cold at the weekend.
Will get to it ASAP.

[zappepappe]

So I did a bunch of testing with this.

With SMB creating a 64Mb VMC and 720p I wasn't able to get it to freeze with official r1386 PADEMU.
However r1386 without PADEMU or if I build it myself, with PADEMU or not, it still freezes for me.

[J013k]

I can confirm that there must be some problem.
For now I've only made quick test through SMB with OPL 1386 without PADEMU.

I'm getting random freeze while creating new VMC at 720p:

Sometimes I'm getting stuck at 11%, sometimes at 29%...

[Jay-Jay-OPL]

Make sure to check your HDDs for fragmentation. In the past, that's usually the case and the fix. If not, then it must be a new bug. Weird, that it would be related to the HIRES modes. What happens when creating a VMC with a different video mode?

[zappepappe]

This has nothing to do with fragmentation. For USB I'm using an almost empty USB flash drive and fragmentation on the NAS wouldn't really affect SMB.

As I said in my original post, it has been like this ever since HIRES was added to OPL, over a year ago. So not new.

Haven't tried on newer builds, but in my original testing all resolutions except 720p worked fine.

[TnA-Plastic]

Fragmentation on USB only causes issues in-game or when starting a game, not In-GUI (at least I see no reason for it)!

[J013k]

The weird thing as you mention is that it only happens on "clean" build,
without PADEMU.

With PADEMU even creating 64 MiB MC is not causing any problems.

[zappepappe]

Not only on "clean" builds. If I compile it myself it freezes with PADEMU as well.
Which makes it even weirder.

Anyone know how the official binaries are built?

EDIT: Seems to be built with Ubuntu 14.04 and GCC 4.4. Could try and see if that makes a difference.

[J013k]

What about other things?
PS2SDK, ps2toolchain, ps2-packer, gsKit...

[zappepappe]

We both seem to be using the latest of all of it.

[zappepappe]

Only tested with USB, but since I can't reproduce this on newer revs I'll close this PR.

[J013k]

Out of curiosity, what version you have recently been testing?

EDIT: With or without PADEMU?
Because I remember that this issue was in version without PADEMU.

[zappepappe]

r1510, r1534, r1535 (couldn't create VMCs) and r1537. All with PADEMU and some without.
Started trying after the new newlib was introduced but due to issues with the clock function it was generally unstable. After the PS2SDK clock function fix all but r1535 have worked.

[J013k]

After adding fix for clock() function, all rev (r1510, r1534, r1537) started to work except 1535?

[zappepappe]

Not exactly.
After the newlib update I decided to see if anything had changed. Due to the clock bug things were generally unstable so I waited for it to be fixed. Since then all revisions I have tried work except r1535, but that is unrelated to this bug.
Also, I forgot that while bisecting the bug in r1535 I also quickly tested a handful of revisions between r1510 and r1535.