Frontier JIT problem

[hexaae]

JIT problems with Frontier WHDLoad using these settings: https://drive.google.com/open?id=1Yi...j9voflK4wjlH0M
and with Beast: https://drive.google.com/open?id=1Tc...NdUvLWou-2OVqV

Frontier makes WinUAE freeze with black screen.
Beast crashes JIT with "Serious JIT error: Could not allocate block pool!" report.

[Toni Wilen]

But does it happen only in 3.6 betas? Required information missing.

[DamienD]

Maybe it's just me, but why do you need JIT anyway?

...I never use it.

[hexaae]

Originally Posted by Toni Wilen

But does it happen only in 3.6 betas? Required information missing.

Yes, with my old 2.5.2 or 2.6.0 didn't happen.
Attached my cfg in my msg above.

[hexaae]

Originally Posted by DamienD

Maybe it's just me, but why do you need JIT anyway?

...I never use it.

If you limit your Amiga activity to a retro-game emulator front-end maybe... but if you want to run a "real" Workench env, it's very useful (and faster then real Amiga HW)
E.g.: [ Show youtube player ]

[Toni Wilen]

I said in previous version. 2.6.0 surely isn't previous. Usual rule: this is wrong thread if it also happens in previous official version.

(This is also not topic arguing when to use some feature or not. Unless it makes no sense at all to use some feature. Frontier surely is much smoother with JIT due to being correctly programmed and display timing is not hardwired to game logic)

[hexaae]

Originally Posted by Toni Wilen

I said in previous version. 2.6.0 surely isn't previous. Usual rule: this is wrong thread if it also happens in previous official version.

Ok I see... just tested 3.6.0b1 and was able to reproduce the issues with Beast and Frontier. I'll open a new thread to discuss this JIT emu issue, because I've been able to reproduce it even on 3.5.0... Have to find when it started.

EDIT: ok, it started with WinUAE 3.3.0 public release.

[Toni Wilen]

Does it still happen if you start the game without JIT and then enable it manually after title screen?

EDIT: I can't duplicate it with Frontier whdload, it seems to work fine (and smoothly) in JIT mode.

Include also your whdload.prefs

[hexaae]

ConfigDelay=60                  ;wait to select options in splash window (1/50 seconds)
;ButtonWait                      ;wait for button pressed (slave must support this)
;ChipNoCache                     ;disable cachebility of Chip-Memory
CoreDumpPath=T:                  ;path for coredump files
DebugKey=$5b                     ;rawkey code to quit with coredump (debug)
ExecuteStartup=""
ExecutePostDisk=S:WHDLoad_start  ;command to execute on WHDLoad startup
ExecuteCleanup=S:WHDLoad_cleanup ;command to execute on WHDLoad exit
;Expert                          ;selects expert mode
;FreezeKey=$5a                   ;rawkey code to enter HrtMon/TK
;MMU                             ;use MMU (for 68030)
;NoAutoVec                       ;ignore unwanted autovector interrupts
;NoFilter                        ;disable audio filter
;QuitKey=$59                     ;rawkey code to quit
;ReadDelay=50                    ;wait after reading from disk (1/50 seconds)
SplashDelay=100                  ;time to display splash window (1/50 seconds)
;WriteDelay=150                  ;wait after saving something to disk (1/50 seconds)
NoFlushMem

In the .info I've set:
Name: Ram:Frontier/Frontier
Type: NewIcon
SS: 20000
IT: Project
BP: 1,0
SZ: x= 3, y= 4, w= 8, h= 8
DT: (YES) whdload
TT: (YES, NEWICON)
slave=fr.slave
preload
quitkey=$46
ExecuteStartup=C:uae-configuration cachesize 0 immediate_blits false cpu_speed max
Cache
PreloadSize=801134
Config=C1:B:Trainer

...to disable JIT only, basically...

[Toni Wilen]

Now I am confused. How is this JIT problem if you disable it in whdload.prefs?

[hexaae]

Sorry Tony, I forgot I already disabled JIT using uae-configuration WB command in the icon, I think it's not JIT the issue with Frontier indeed, but it is for sure with Beast.
Can you reproduce WinUAE crash with the Beast WHDLoad above?

[Toni Wilen]

Originally Posted by hexaae

Can you reproduce WinUAE crash with the Beast WHDLoad above?

No crash, but there is lots of flickering (which is normal)

[hexaae]

No crash launching it from that icon with "UAE-configuration cachesize 8 ..."? Mmmh
I've been able to reproduce it also on WB3.9 standard installation, so it's not my WB... Attached my prefs and bootlogs and crash dump.

[Toni Wilen]

It looks like JIT runs out of memory but it can't be right.. If you open windows task manager details page and select working set and private working set columns, do they jump to very large values when you start the game?

Does 64-bit winuae.exe have same problem?

[hexaae]

The problem seems with "UAE-configuration cachesize 8...". When I change the value to 0 (JIT disabled) or 512 runs well...

Yes, crashes also with 64bit