FF Type-0 ARM-JIT Issue

[Kenny4343]

Hello

So there seems to be another bug on the arm-jit, when in game, on the world map, if I try to move onto a different zone I'll be moved to a far away random spot of the map, and sometimes even places that are unreachable normally or places where you can't move or go back at all.
Disabling the JIT allows you to bypass this, which is what made me assume there's a bug in it, also, I tried reproducing this issue in windows with no chance, it only seems to happen on Android (or on mine, until someone else can confirm).

Tested on a Samsung Galaxy S4 using the build v0.9.8-1263-gd8c392e.
If I can provide any more information please let me know, thanks in advance.

[unknownbrackets]

Do you have a compiler? If you do, you can follow these steps to find it:
#2278 (comment)

Otherwise, do you know if it's possible to reproduce this problem in either demo?

-[Unknown]

[Kenny4343]

Sorry I do not own any compilers... I don't really understand much of builing or coding aplications (tried once and ended up downloading a lot of compilers and couldn't get any to work despite all the different guides I tried to read), and I don't think you can reproduce it on the demo as it takes you directly into misions if my memory doesn't fail.

[xsacha]

Can you give me a screenshot of whereabouts this bug appears? The screen just before.

[Kenny4343]

Sure thing, here are some:

This is where I first found it, moving onto the togoreth region (you get there right after thebcity called corsi).
https://www.dropbox.com/s/jr0z3o3dq0h7x4e/Screenshot_2014-06-18-05-33-03.png
So upon transition, you should appear here, just a bit more forward:
https://www.dropbox.com/s/r0ovmgh1x0k4sqb/Screenshot_2014-06-18-05-33-44.png

But if I don't turn off the jit, I appear here instead:
https://www.dropbox.com/s/5g22r3e4pi17eyl/Screenshot_2014-06-18-05-34-26.png
Edit:
Here, I thought I'd also upload my savegame right before heading to the worldmap just in case:
https://www.dropbox.com/sh/ysjrhomqr8bx69l/AADZogeQFcE7zU2ip9YCtDlXa

[Kenny4343]

Just tried the latest build aviable to check on the issue and it seems to be fixed, I'll be closing this then.