@NewSense:

Interesting! Just tried again, but in my case it still does not work (with JIT). OWB-JIT is from 28.06.2018, OWB is from the 3.11 iso. I'm on my PowerBook G4 5,8 now. Though the link you posted works, just the main page does not finish loading. Also I can't kill the frozen OWB-JIT from Task Manager.

Frozen applications AFAIK are never released, and usually that means a reboot is required if it's an application you need to use, as it's resources, and the systems resources it has allocated are all tied up/unavailable to anything else.

I also found the first website I cannot use with either v1.25 that came with v3.11 or the JIT version(s), that is:

the sign-up page for ITV.com - internet TV channel - Date Of Birth field inaccessible in that there is no way to input any data/text in the format required (dd/mm/yyy) even though the field can be highlighted with a mouse or Tab keypress, but no active cursor appears in the field so you cannot input data in it with OWB, and so the signup cannot be completed as this field is mandatory.

Yes, I did try spoofing, but that too does not allow the field to be accessed. I managed to signup, but I had to use my Windows system to manage it, which I really dislike having to use anyway, but needs must !!

[ Edited by NewSense 13.08.2018 - 01:49 ]

Another website which works with OWB and does not work with OWB-JIT: klick

OWB-JIT does display the graphics and text, but it freezes on showing the graph.

And another one which does work with OWB but freezes OWB-JIT: klick

Additional, to the issue I also reported with the ITV HUB # 127

I also cannot log in to my Adobe ID / amend/request a new password - OWB/CPU just goes into "overdrive" and nothing happens, the mouse cursor continues to be moveable, and screen swapping works OK, but the OWB window/program takes over the CPU and it ends up running at 98-99% activity, wit nothing happening for minutes on end, so I felt it required a warm reboot to start again, that's with OWB v1.25 either the v3.11 release or this later JIT enabled version.

Again, this task had to be handed over to my Windows browser to be able to manage the process of requesting/inputting a New Password @ Adobe

Quote:

Tested on PB with OWB-Jit - works without problems. Can see page without freezing and can even enter commend-section as well.

Two more years later...

I think it is time to close this bounty and do the payout. I just don't want to hold this cash anymore, considering that I'm not active here at all.

I've also emailed Mark to get his opinion on closing this bounty.

Any comments, suggestions?

Has any of the JIT work that Mark Olsen did already been able to be carried over to, or benefitted "Wayfarer" or is the new browser unlikely to need any JIT JavaScript implementation?

I believe jacadcaps stated that the "memory lock" we all experienced with OWB is not a factor with "Wayfarer", but we don't yet have access to "Wayfarer" to be able to confirm that.

I know Mark did all that work on JIT for OWB, but I was never sure it worked/enhanced browsing with OWB to offer any noticeable/significant benefit to OWB, though others may have a different opinion, or figures to back that up.

Not that I don't think that Mark should be denied the bounty as I believe all the work he has done in the past for the GFX cards deserves more funding sent his way in any case.

Actually, memory wise, Wayfarer isn't that much better from OWB. JIT or not. While bigfoot has shared his JIT diffs with me, I'm not entirely sure they can be applied without significant rework - work for which I have no time right now.

@ jacadcaps - So, I thought the RAM situation was improved dramatically, or is memory (RAM) still unreleased due to JavaScript, or some other part of Wayfarer code, while it is still running, but gets freed when it is quit?

Also, is a quit probably/definitely necessary during heavy browsing (all RAM becoming occupied/unreleased), or has this been eliminated?

I'd just like to know if this situation will be behind us, or if it is still going to be an issue?

If it's still an issue, then is it possible this RAM 'lock' issue might get eliminated in due course, or will we just have to live with it?

Hi folks

Didn't get too much feedback on this case so I think it's high time to close it. Today I've transferred 869.83 EUR to Mark's account. I believe he will be able to confirm funds arrival on Monday.

If someone from the donors disagree with bounty closure, feel free to contact me.
The list is still available here:

http://morphos.pl/jit-js-dla-odyssey-web-browser/