Copying site address with pull down menu works magically now.

@kas1e

:)

@kas1e

In here fastfix3 is stablest version.

I get problems in low-memory conditions. Pretty normal I think, since swap is off. Problems start, when I have 5 megs of mem free.

Otherwise no problems atm. Not really extensive testing, but seems ok.

I test more today at evening, but Im away at weekend.

@sofistisoftware

I have same feeling. And other possible plasebo effect. I Think that it eats less memory.

@kas1e

It showed itself fast.

Clean, newly installed fastfix2, fails


Odyssey_curl7_28_1 over that clean fastfix2, works.

@kas1e

Ok.

@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.

@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.

@kas1e

Sorry, no freezes with 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 ::)

@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 .

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.

@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.

@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.

@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.

@Fab

Thanks.

@Phantom

Sounds like same symptoms here.

I get error message eventually, if I wait enought long.

If I try to refresh page, it stays just same, network is dead.

In same time other network related progs works ok and i can ping outside with names and IP addresses..

I can find some java reated error messages from windows menuitem under messages. Many of them seems wait network.

Now I disabled javascript and works much better. It was same in 1.16.

I just enable javascript to pages, wich really needs them, network banking, facebook, gmail.

I usually surf quite lot news sites and they use javascript heavily.

I test tomorrow without javascript and let see, if it still behaves well.

ATM 1.23 fix2

With original 1.23 I had network freezing but overall not so many system or Odyssey hangs.

@kas1e

I dont have mystic freezes with 1.23 from os4depot. I definetly have problem, where network stops working. All lamps down right are orange, and only restarting Odyssey helps.

I made fresh MUI installation.

With fix1 I had mystic freezes. Rolled back to original 1.23.

Will test fix2.

I can make fresh OS installation somewhere next week.

@kas1e

New port is magnitudes more stable and usefull than old, thanks all involved :)


Some situations here.

Only one crash. I have crashlog, if you want it?

Some system freezes. After some use. Maybe low memory conditions ?

Sometimes network gets dead and sites just dont load. Only shutting down/restart OWB helps. Other networking proggies works normally at time when OWB doesnt.

My system is Peg2 G4 1Ghz, Radeon 9250 128bit. Still even 240p youtube video eats processor 100%. Didnt find any solid answer, is that normal? Others speak 30-35% cpu. 360p wideos seems to play full speed still.

If I mark site address and try to copy it with pull down menu, it doesnt work. All other copying works from web side with pull down menu. With pop-up menus address copying works allso. This was same with 1.16 (?).

Pull down menu paste to address doesnt work either.


Anyway, it works pretty well :)

This is good and important, thanks :)