Regarding this endian issue...is it somekind of a fundamental issue, where somebody has to fix thousands of lines of code, or some sort of a needle in a haystack case where something has just got wrong and nobody knows where?
If it "just broke" at some point, is it possible to diff the source and try get closer to the problem?
16.01.2016: Update to Odyssey (only executable changed) - fixed messages console to display messages - made aligned allocation not take additional memory - made memory allocator work better with fragmented memory - fixed major memory leak where Frames were not released together with their JS data - memory no longer continously consumed while browsing - fixed a number of small memory leaks - implemented a more agreesive memory freeing strategy which keeps allocated memory as low as possible
This is exactly what i was waiting for...and probably others as well
Yep, that it. Sad to hear, as it mean we need to make a choice: or site for BillE will not works, but we will have your one works. Or for BillE it will works, odyssey will have last openssl, but your one didn't works :)
Probably we need to ask Mick to make some openssl tests. Mick, can you check that ?
Hmm, what's causing this? Is it the site that sends wrong SSL information? I thought with the latest OpenSSL "all" of the SSL problems are taken care of?
Which is probably "fixed major memory leak where Frames were not released together with their JS data - memory no longer continously consumed while browsing"
@BSZili Is your pthreads implementatio for aros/mos are the same by functionality as pthreads.library on os4 ? Why i ask, is that for building latest webkit, we need c++11 thread support in the GCC, but, that to be use pthread.library, and deadwood use your one, i want to know before start nagging everyone about if os4 one are the same and ok for, or, we need to backport your one to os4 :)
Quote:
It's not a fundamental issue, since WebKit used to work just fine on BE. It's just that nobody has looked into the issue.
We only know that Fab trying to deal with it, and can't at moment by some reassons. So probably hard one.
@kas1e I didn't mean to sound like it's a trivial thing to fix. The needle in the haystack analogy Capehill used was pretty accurate. Take into account that Fab has limited free time, so that's probably one of the reasons why he didn't fix it himself. My pthreads implementation aims to be as POSIX compatible as possible, nothing AROS/MOS specific. The OS4 pthread.library implements the most common ones, and the SDTC++ library only uses those, if I remember correctly.
Yep, that it. Sad to hear, as it mean we need to make a choice: or site for BillE will not works, but we will have your one works. Or for BillE it will works, odyssey will have last openssl, but your one didn't works :)
I am pleased to report that the Avios site still works perfectly with fix_v5.
Hmm, what's causing this? Is it the site that sends wrong SSL information? I thought with the latest OpenSSL "all" of the SSL problems are taken care of?
Probably too recent openssl give us new errors. In V3 i link againt last openssl build by Mick, and while site from BilliE start to work, site from Samo stop working. Then, Mick found that problem happens everywhere (on windows/linux as well), so we a bit downgrade. That fix problem with samo's site, while billie's one still works. Now, your one didn't , so, probably again something-somewhere in the openssl.
What about v5, is it indeed "fixed major memory leak where Frames were not released together with their JS data - memory no longer continously consumed while browsing" ?
Probably too recent openssl give us new errors. In V3 i link againt last openssl build by Mick, and while site from BilliE start to work, site from Samo stop working. Then, Mick found that problem happens everywhere (on windows/linux as well), so we a bit downgrade. That fix problem with samo's site, while billie's one still works. Now, your one didn't , so, probably again something-somewhere in the openssl.
Yeah, i talked to Mick about this and *i* think we shouldn't give in to broken sites or at least don't try to do the web admins work and workaround their faults.
If a site doesn't work with the latest openssl it's probably the site that is broken and should be fixed...at least, security is more important and i'd like to have the latest bugfixed releases of a security suite rather than be able to browse every broken site
Quote:
What about v5, is it indeed "fixed major memory leak where Frames were not released together with their JS data - memory no longer continously consumed while browsing" ?
Well, i haven't had the time to browse one of the ram eating sites i know yet, but at least it doesn't eat away that much memory under normal circumstances like it did before, so i guess it's working.
News feed
OS4 Feedback forum
OS4Depot Feedback forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
