Decided to go with a new thread on this one.


@FAB

Everytime I lock up using OWB it is while using the scroll wheel to scroll the screen.

Also, if I only keep one tab open and keep moving between pages, eventually I have no ram free anymore.

No memory is freed up for moving from a large web site to a web site with a few pieces of text.


P.S.

I just went back to 1.11 and for the most part the memory leak is gone.

Free ram stays fairly consistant.

I haven't seen any lockups with scroll wheel ever...

Memory leak is usually because of WebKit's Javascript engine, it's not Fab's fault. Every WebKit based browser leaks like hell with that and it probably gets worse with every new version :) It seems that modern coders don't care about memory consumption because they have more and more ram and virtual mem to waste :P Anyway, Fab has made what he can do for it, so at least memory gets free'ed when you quit the browser. So.. if you use javascript heavy pages, you'll have to restart browser sometimes. I made radical decision and disabled the javascript completely and only enable it for certain sites which really need it (for regular pages automatically from URL Settings and for occasional needs from Settings->JavaScript support menu). This way I don't need to restart OWB daily...

jPV

Since 1.18 it seems to release memory just by closing the relevant tab, not the whole browser.

@bash64

First, don't assume it leaks if it consumes more and more as you scroll. There's a x MB cache (depending on cache mode, up to 64MB or so) that will be filled progressively as it encounters new images to cache. When it's full, it won't seem to "leak" more.

However, there are also huge leaks in JavascriptCore, but they only happen noticably with specific pages like facebook for instance (and possibly guardian, from what i read in another thread). In this case, the memory could be depleted after some time or while you scroll. But when there's an out of memory situation, i show it explicitely with a requester, that even allows you to quit. So it doesn't qualify as a "lock up" at all. So are you sure it's a lock up?

Also, between 1.11 and 1.18, there were so many fixes (in webkit itself, but also odyssey) i wouldn't recommend it.

Thanks for the info.
I get the 'can't allocate 0 bytes' error and choose to exit.

Its ok, I'll stick with 1.11 for now.
I just upgraded from 512mb to 2gb of ram so not as big of a deal anymore.
but that is another thread.

Wow, 1.11 is now giving off 'fatal error' with a 'crash' button but cannot exit when "I click crash.
Once my backup drive arrives I am going to make a special OWB partition and keep OWB seperate from everything else.
I used to have such a large amount of file corruption when using Voyager that I eventually copied the SOB into a ramdisk on boot and ran the browser out of ram to keep it from trashing my filesystems.
I hope this is not what is happening again.

Just a note:

I have been running with 1.5gb of ram for a few days now.
OWB not only has stopped crashing but I can have 8 tabs open at the same time.
I am using 1.11.
I am ready to try 1.18 again.
It all appears to have been caused by a lack of memory.
I highly suggest that you max out your mem when running OWB.
L8r

I also switched back to version 1.17, because it is much more stable has
less memory leaks.
sourceforge.net eats the memory too.

I noted in another thread that I turned off Prefs->Debug->MUI->Errors and OWB 1.18 has stopped crashing.

I am crash free right now.

eliot,
Quote:

Huh, I guess what you see is simply the banner loading, which causes "memory leaks".

This is really insane. Detecting memory leaks is not as easy as you expect. MorphOS is caching stuff, OWB is caching stuff and if you check using the shell, then just remember even the shell is caching stuff.

Geit

@bash64

I doubt disabling this debug option affects OWB behaviour in any way, really.


Anyway, i've built a newer revision that apparently cures the reproducible crashes reported for a couple sites.
As for the insane amount of memory required by sites like facebook, it's another story, but i now call the garbage collector periodically to regain memory (otherwise it's only called for specific events).

(and by the way, you can call the GC manually in previous OWB versions by pressing F12).

thanks,
I will use F12 if need be.

I realize from a programmers perspective that turning of the debug should not have done anything but from the user perspective it has ended all most all of the crashing.
I still expeiernces crashing on drudgereport.com today though.
Considering this site is just a bunch of text links to news articles it is amazing that is does crash.
I really think that the Advertisement at the top of the page is the culprit and I'd like to enter this site as a torublemaker.

Sincerely, Roger.

@FAB

There are lots of other websites that demand shockwave flash besides youtube.
Could I make a copy of those scripts and change a few things and have it support other websites or is that not really possible.

bash64,
Quote:

It is not fabs job to fix the internet. Fab is doing a great job and especially fixing youtube all the time is much work.

I use stupid news sites requesting flash to play movies, too. But usually it is enough to simply type the topic into youtube search to find the similar video.

Just blame the page maintainer for not taking care of the millions of ipads and other mobile devices out there. If they continue to use flash, it is their problem getting less hits and less money for their banners,

Geit

@bash64

The youtube scripts only apply to youtube. Each site/flash video player is different.

Not sure why drudgereport would crash. It could of course be related to top ads and Flash. If you installed latest reggae classes, you should disable swfdec audio, since reggae audio output seems to have changed something in a nasty way for swfdec since MorphOS 3.1.

Oh, and by the way, you can disable top ads with the built-in adblocker, if you didn't know (settings->contents->content blocking) and the rules can be seen/edited in windows->content blocking if needed.

> There are lots of other websites that demand shockwave flash besides youtube.

The Youtube website doesn't "demand" Flash even without any userscript in use. You can watch virtually every video on the Youtube website, either in its "desktop" HTML5 mode or, when that fails, in its "mobile" HTML5 mode by spoofing as iOS browser.
There's really just a very small number of Youtube videos not working in "desktop" HTML5 mode that do not work in "mobile" HTML5 mode because the uploader for whatever reason decided to disable access from mobile devices (it's a shame that Youtube even allows such an option).

Drudge Report has always been "crashy" for me with Amiga browsers (including IBrowse) -- turning off javascript for the site fixed it here.

The crash at drudgereport seems to happen when it reloads automatically, and it's related to cookie handling, at least. So it's not javascript itself (but js probably updates the cookie, which is why disabling it hides the issue).

Andreas_Wolf,
Quote:


Those are videos with popup comercials and pre play commercial content. It is not in the interest of youtube and the respective channel owners not getting any money, because people like us are cheating around that content using greasemonkey scripts.

That is also one reason youtube changes the webpage so often. If you want some always working app, you need to licence the offical api.

Geit

>> the uploader for whatever reason decided to disable access from mobile devices
>> (it's a shame that Youtube even allows such an option).

> Those are videos with popup comercials and pre play commercial content.

Almost all such videos do work when spoofing as iOS browser. It's really just a tiny fraction that is being blocked from mobile platforms. That's why I figured there must be more to that issue.

> It is not in the interest of youtube and the respective channel owners
> not getting any money, because people like us are cheating around
> that content using greasemonkey scripts.

The issue I described occurs *without* using any scripts. Such videos that are blocked for mobile users still work *with* scripts.

Turned on Ad Block and drudgereport.com seems to have stopped crashing for good.
Thanks

@bash64

In a recent WebKit, i've investigated the issue, and the crash was related to cookie handling. I fixed it since (hopefully).

@Fab
If you are interested in wierdness check out THIS PAGE

I am quite happy with OWB, this is not a complaint. I just find this page a bit odd

@redrumloa

If you mean black rectangles at the top, it's probably a bug in webkit.

Is the fix for OWB concerning the cookie handling out yet? All I see is 1.18 still.
I don't need it right now. I turned on Ad block and the crashing is gone.
I have not crashed once since I did this.
I had to ALLOW some websites because AdBlock is a little too aggressive.
That and finding out usb hard drives need an external source of power has solved all of the wierd crashing that was happening to me.
I am quite happy with my miggy now.

I have a 2-bay firewire 800 external raid box on the way. It is nice and mac looking. Got it for $50 off of Amazon.
http://www.amazon.com/gp/product/B005GREVW0/ref=oh_details_o00_s00_i00

Too bad you cannot have amiga partitions on an MBR drive.
Having two drives, one for amiga, one for windows was not what i intended but at least this box doesn't need power if run on fw800 and has only one cable for the 2 drives.