Thanks, already downloaded via AmiUpdate!

Downloading from depot now. Didn't find it on his homepage.

Hello,

Installed and just searched a site with google and access this site and a DSI located around bsdsocket.

Reboot and try the same again and a recovery alert.

hum.......

EDIT:

in fact the same with OWB 3.31:

site: www.meteofrance.com

Symbol info:
Instruction pointer 0x6FC2871C belongs to module "bsdsocket.library" (HUNK/Kickstart)

Stack trace:
module LIBS:bsdsocket.library at 0x6FC2871C (section 5 @ 0x2A6FC)
module LIBS:bsdsocket.library at 0x6FC293E4 (section 5 @ 0x2B3C4)
native kernel module newlib.library.kmod+0x0003a71c
native kernel module newlib.library.kmod+0x00004794
native kernel module newlib.library.kmod+0x0002eba0
module OWB at 0x6EE9CC30 (section 5 @ 0xC22C10)
module OWB at 0x6EE9CE5C (section 5 @ 0xC22E3C)
module OWB at 0x6EE9D4C8 (section 5 @ 0xC234A8)
module OWB at 0x6EE9E478 (section 5 @ 0xC24458)
module OWB at 0x6EE9ED48 (section 5 @ 0xC24D28)
module OWB at 0x6EE8D6E8 (section 5 @ 0xC136C8)
module OWB at 0x6EE8E05C (section 5 @ 0xC1403C)
module OWB at 0x6E31AE44 (section 5 @ 0xA0E24)
module OWB at 0x6E31B6EC (section 5 @ 0xA16CC)
module OWB at 0x6E32666C (section 5 @ 0xAC64C)
module OWB at 0x6E2DF074 (section 5 @ 0x65054)
module OWB at 0x6E28533C (section 5 @ 0xB31C)
module OWB at 0x6E289964 (section 5 @ 0xF944)
native kernel module newlib.library.kmod+0x00001f4c
native kernel module newlib.library.kmod+0x00002be0
native kernel module newlib.library.kmod+0x00002d5c
OWB:_start()+0x180 (section 1 @ 0x180)
native kernel module dos.library.kmod+0x0001b524
native kernel module kernel+0x00036290
native kernel module kernel+0x00036310


PPC disassembly:
6fc28714: 3d405af7 lis r10,23287
6fc28718: 7fe3fb78 mr r3,r31
*6fc2871c: 91690000 stw r11,0(r9)
6fc28720: 816a0850 lwz r11,2128(r10)
6fc28724: 396bffff subi r11,r11,1

@Mrodfr

Stack-trace looks very-very close to the stack-traces which i have with Curl, when i build it with enabled DNS-resolver (what mean pthreads). In such crashlog there is not words about Pthreads (maybe Joerg remove them and replace them on Semaphores, dunno), but i also have crashes in bsdsocket library, and that was because of new curl with enabled threaded resolver.

Imho that can be the same problems.

Same problem here on Meteo France. I have also that stange bug making the CPU go as high as 100% for a while and then getting back to normal.

Thanks Jeorg

@kas1e

Yes, the libcurl threaded resolver does not work on AmigaOS 4.1 latest public version. Me and MickJT have both observed problems with it - crashes in bsdsocket.library.

It's possible the problem has been fixed either in libcurl or bsdsocket.library, but if Mrodfr is getting the problem then it hasn't been fixed in libcurl - which leaves bsdsocket.library, and any fix there won't be public yet.

I did not use AmiUpdate. Downloaded and unachived the lha file myself into its own drawer. Start up and quit are slow and closing a tab is very slow. Other than that I do not see any DSI errors or other problems at the website mentioned earlier.

I have decided to stay with OWB 3.31 for now, because it is much faster than OWB 3.32 on my system.

---
redfox
MicroA1 + OS4.1 Update 2 (public version)
Screenmode: Radeon 7000: 1024x768 ARGB32
compositing modes disabled

@crhis
As i understand it can work: need to ./configure curl with dns-threading enabled, but later, in the code change all the phtreads calls on semaphores, etc.

For muiowb fab do the same and it works fine looks like on mos. Of course it can be that our problems not exactly in the mixing of pthreads+curl code, but even in the bsdsocket itself (even with usage of semaphores), but will see (i hope to worring about all of this in next few days, so will have all the answers).

There is libcurl 7.21.6 for now , but dunno if any of the fixed can help us.

And that crashes are not the last problem with dns-resolver , its sometime just crash/drop connection and driver it to busy-loop.

In other words, its all should be carefull rewriting in the httpreso.c or how that file called in curl, without pthreads, with semaphores, etc, etc. As well as file.c, to make amiga pathes works :)

@K-L

Same here, atleast it doesn't freeze the entire GUI ...

I confirm the "meteofrance" website works on an up-to-date beta system.

I remember there was an update of Roadshow a while ago. I don't know if there's some relation.

where is available this RoadShow update?

@nubechecorre
:)) In the same place where is usb updates, warp3d updates, and new shell :) (2 more weeks)

Where can I get OWB 3.31? This new version sucks when closing Tabs or Exiting.

Can't wait for MUI-OWB.

Way to go djrikki - You sure know how to motivate people.

Thanks Joerg for another update. It is great to see OWB updated again. I havent notice any strange delays when closing tabs and that french metero-site worked here..

@Mikey_C
I don't think he said anything wrong - do you want him to praise v3.32 for being very slow to close/quit?!?

@djrikki
v3.29 can be found here, although I've got a note that it has a nasty window-resizing bug:
http://aminet.net/package/comm/www/OWB

v3.30 or v3.31 (or v3.28) were the best versions IMHO.

Not at all, but it could have been worded a bit better "Sucks" and wishing for the MUI version is just a bit of a slap on the face for poor Joerg who has been immense for the Amiga community.

IMHO of course.

Thanks Jeorg for this last version. Now on to trying it out :)

EDIT: Tried it out for about an hour and didnt have any crashes whatever. The BIG plus is facebook now works much better and all other pages i visit. No locks, i didnt had to restart OWB just to get facebook running again. Normally i would restart at least 10 or more times in a hour. Only negative thing is the long wait while closing a tab.

So thanks again :) Ill be more on amiga from now on hopefully. More daily try.

on my Sam460ex it works very well, not so fast but it seems to works correctly and stable

Weird with so many different results. To me it just works better, no crashes, no DSI errors and it feels faster.

Just using AOS 4.1 upd 2 on an A1 G4 XE. Haven't closed the browser yet but closing tabs works as usual, not slow.

Hmmm, maybe I ought to try v3.32 after all...

Well it wasn't meant to be a personal attack, but anyway since when is 'sucks' such a harsh word? Am sure Joerg is grown up enough to realise - yes that does suck Richard, am on the case.

@Mikey_C

I am sure I am not the only one who is more than a little surprised to see OWB still under development. Thought I'd read Joerg abandoned it months ago.

@djrikki

So if you put a lot of work into something and released it and someone said "it sucks" you wouldn't be hurt by it?

In case you don't understand, if you get a kid and he tries to play basketball someone says "he sucks" would it make you happy?

Are you able to understand this at all?

I was having the slow closing of tabs and/or closing OWB itself, with 100% cpu usage. I deleted the cookies file and it resolved this problem for me.

@hotrod Quote:
If you read what djrikki wrote, he did NOT say that OWB sucked. He said that it sucked *when* OWB took ages to close/exit. And I would agree with him. (The complaint he made was about the bug, not about OWB itself.)

I think about the only improvement he could have made to his post would be to have said "Thanks for the update... but it sucks when it takes ages when you close/exit. Any chance of a fix?"

Constructive criticism (as given by djrikki) should be acceptable, as long as it is not excessively harsh, nor repeated unnecessarily.

@Hotrod
But we not childs. We are grow up enough (i think) mans, who will not cry when we will see bad words :)
(and yes, if i put some work to some project, and someone will say that it suck, i will not cry as well, and be think that if someone say it, then looks like it mean sense in some way).

Maybe I overreacted, sorry about that. Critic is good, I agree but only if it's written in such a way that it isn't insulting. This isn't the worst that I've read by far but it could be improved.

@kas1e Regarding childs, that's not what I ment. Anyway I hope that noone will be harsh enough to make you cry about your ports . They are much appreciated by the way.

... and gif animation (emoticons for example) does not work in 3.32

@TheKorn
Quote:
Thanks, for the tip.

@ChrisH
Quote:
+1

@kas1e
Quote:
+1

@TSK
Quote:

How ironic, that was pretty childish right there...

@hotrod
Imho enough :) It all was about that tabs at closing 100% cpu loading for many users , and that are suck (not joerg work suck, but bugs are suck). When joerg will fix it, then tabs closing will not suck :)

@kas1e

I agree, I already apologized so I don't know why this is being discused further?

Thanks for this update Joerg!

Thanks TheKorn

Deleting the cookies file also resolved the slow closing of tabs and slow closing of OWB itself for me as well. Startup is still a bit slow though.

I also changed the options to match my current options for OWB 3.31,
such as using a different home page,
DOWNLOADDIR=RAM:
COOKIEDB=RAM:cookieCollection.db

I have also noticed (like some others) that the bookmarks act differently. If I open a new tab and use one of my bookmarks, it goes there rather quickly, but if I try to use a bookmark on the current tab, OWB seems to ignore the bookmark I have selected, and does not go to the bookmarked webpage.

---
redfox

Solved the bookmark issue by removing () from

(BOOKMARKCOMMAND=OWBAddressBook/AddressBook -%s) Tool type

Seems to work as expected if the Tool type reads as follows

BOOKMARKCOMMAND=OWBAddressBook/AddressBook -%s

---
redfox

Installed, and so far it does not seem or feel any worse than the previous version. THANK YOU very much, Joerg, for your effort and continued updates!

Thanx for the update!