fastfix for 1.23

@kas1e

Im not betatester. Just normal peg2.

ATM it seems, that my network dies when I have approx 270 Mb free memory left. Sometimes to reach that point I need 10 tabs, sometimes 25. But it _may_ be there.

I made frsh install of MUI and this time I deleted MUI drawer from Prefs/Env

It made difference, now I get Could not connect to server requester at once.

More testing... disabled swap now.

I test with new package later and after that memory test.

I have one 1 gig crucial peg2 compatible stick. 2b3 mb revision, so it cant handle two.

@kas1e

I was wrong. 525 Mb free and fail. First 8-9 fails approx 270 mb and then...

No any additional progs loaded in startup.

@Mlehto
what about new binary with curl7.28.1 ? btw, i also have peg2 with 1gb memory and no freezes. as for backround apps : maybe you use some additional dockies ?

its all can be of course fault of port, but as it hapoens only for you and phantom (those network stalls) then we imho need to check fully your setup.

@kas1e & Fab

I am also having the network dying problem that Mlehto & Phantom are having. I am using the origional version from OS4 Depot, now with the Odysee executable build with the 7.32 libcurl. Both versions seem to have the problem after being used intensively for 20 min. to an hour. Also it does not seem to effect all sites open. This morning AmigaWorld would partially load (text only without graphics & if trying to follow a link I would get a message saying it could not "connect to the network" While the first site visited (Amigans) continued to work fine. This is on an X1000 with full 2 gigs of ram installed. Version 1.16 of Odysee does not have any similar problems. Other than this issuse 1.23 seems to be very stable.

Bryant P.
Indpls., IN USA

@kas1e

I thought dockies and removed whole amidock from startup. I mean, I removed everything wich is any extra to basic OS4 to start :)

With curl7.28.1 it seems to work.

I get fail when I really open many tabs.

Pls test www.ampparit com and feed to personointi box ml0 . It is my profile. Open 15-25 tabs to test build with newer curl.

I think that there is pretty many "bad" javascripts in these sites. I think, not know.

I just open one by one these tabs so, that they load all at same time.

I put some kind of "rapport" next.

Thats how I tested it.

Deleted all mui prefs
Clean mui install

I started to get "could not connect to server" requesters yesterday. Changed to static ip, because I wanted ISPs dns servers instead of ADSL modem address to dns. Forgot modem password...

Vanilla MUI settings, some Odyssey settings:

Java enabled
allow javascript to open new windows
Active connections 16
spoof as odyssey web browser (forgot to change)

Opened 15-25 links to tabs simultaneusly.

Tested fix2

Networking freeze: No
Random freeze: No
system lockup: No
weirdo tab behaviour: No
copy-paste from address bar: Doesnt work
network choching? Could not connect to server requesters


Still no network freeze. Just two sites doesnt load.

Restart Odyssey, all fine.

This was result from starting Odyssey, ampparit.com and 14 additional links from there.


If anyone want test : www.ampparit.com with personointi: ml0 , so one has same profile.

It is somehow stress-test, because many sites are heavily js-related.

Result, different than yesterday. No entirely dead network and could not connect to server requesters immediatly. So something was broken in MUI-settings.




Tested fix2

Next all programs away from wb-startup and user-startup:

Networking freeze: No
Random freeze: No
system lockup: No
weirdo tab behaviour: No
copy-paste from address bar: Not work
network choching? Could not connect to server requesters. In "low" memory conditions? More or less when 270 Mb free.



Tested fix2

Disabled swap...

Networking freeze: No
Random freeze: No
system lockup: No
weirdo tab behaviour: Not tested
copy-paste from address bar: Not work
network choching? Could not connect to server requesters

525 Mb free memory :(


Alltogether, after opening 15-25 tabs, Odyssey fails. Simultaneus loading.


Tested build curl7_28_1

Swap off, all additional programs not started.

Networking freeze: No
Random freeze: No
system lockup: No
weirdo tab behaviour: Not tested
copy-paste from address bar: Not work
network choching. Could not connect to server requesters nowhere.

All _seems_ to work ok. Stressed to as low as 150 mb free mem couple of times. Maybe 150 tabs alltogether opened.

Now more testing. It works anyway significally better now.

This is my only computer atm, so I can get final word pretty soon.

@mlehto
so with 7.28.1 no network freezes ? orno freezes at all even with 7.32.0 curl after you reinstal mui-odyssey ?

@bcp
try plz binary with curl7.28.1link on which i post in previous page, will you have network stalls or not

@BCP

I think that I had this kind of problem before I destroyed all old mui-settings from env-archive and reinstalling mui.

Maydee there is something wrong after all MUI updates. I installed MUI R3 when it was "broken". Or something.

Delete MUI folder from env and mui from sys: Then restart machine and reinstall MUI and test curl7_28_1 .

@kas1e

Right, no freezes now. I dont yet say, that it works, but it really seems to be better.

Sometimes bad and good luck mix strange way and everything seems to work ::)

@kas1e

Sorry, no freezes with curl7.28.1.

@Mlehto
but with fastfix2 now ? (ie curl 7.32.0). i just need to be sure if it curl or not

@kas1e

More info about pull down copypaste menuitem problem.

I get something, carriage return. No text.

Not high in list anyway. Can live without atm.

@mlehto
we can sort it later (probably again mui settings related), but now i need to know : do you have network stalls with fastfix2 binary (curl 7.32.0) and do you have freezes with 7.28.1. i mean now, after mui reinstall

@kas1e

Bit hard :)

I had network stalls with 1.23 version from os4depot, fastfix1 and fastfix2.

I dont have stalls with that:

As you write:

There is just a binary of odyssey build with curl7.28.1.
http://www.sendspace.com/file/56klqp

To test it normally, plz, just install fastfix2 to fresh directory (and that include everything, bookmarks, passwords, doesn't matter what : all should be just fresh without your old files from any previous installs, to exclude any possible and impossible problems) , and then, just overwrite binary by that new binary. Reboot must too. Preferable to not have anything in background which may cause problems too

And I made just that, reinstalled fastfix2 and copied over odyssey build with curl7.28.1.

And that last one works.

@mlehto
ok, now just try again plz fastfix2 : if therewill beno stalls then it was settings, if it will stals, but 7.28.1 not, then its curl and i will rebuild odysset with. i just need to know roots, so if ypu can test both fastfix2 without changes and fastfix2 with new binary thatwill help

@kas1e

Ok.

@kas1e

As I noted in my first post, I am using the 7.32 curl version binary (with the origional OAS4 Depot download) and am still having the stalling/freeze problem. I will try the fastfix2 with curl 7.28.1 binary version this evening.

Thanks,

Bryant P.

@kas1e

It showed itself fast.

Clean, newly installed fastfix2, fails


Odyssey_curl7_28_1 over that clean fastfix2, works.

@Mlehto
ok good, so its curl

@Phantom , BCP
can you confirm that only with binary builded with curl 7.28.1 you also have no stalls, but have with 7.34.0 and 7.32.0 ?

@kas1e

I've been using the origional version of Odyssey with the curl 7.28.1 binary all day without any stalling or other issues. So it does seem to be the Curl 7.32 & 7.34 versions that are the culpret. I'll try it with fastfix2 tomorrow.

I want to thank you and the others involved in bringing Odyssey 1.23 to OS4. Its a tremendus improvement over version 1.16. Its much more stable & does'nt seem to have the javascript related memory loss issue that I had with v.1.16.

Thanks again,

Bryant P.