Thanks for the memory leak fix, that was really annoying, which you had to restart Odyssey after a while.
Is there any possibility to fix the proxy server settings?
What Thore told me:
Quote:
Looking at the Odyssey source all I can tell is that two string objects are created and their contents are read out when ever the a configuration is loaded, saved or reset. Each string object in the window gets a unique ID to automatically set the contents, i.e. after loading a new configuration. However, I just noticed that in contrast to all other string objects the two in question get the same ID. This definitely causes all the trouble, because one setting will be applied to two objects with different tasks and hence cause the trouble you are experiencing. This can only be fixed in Odyssey. Here are the some lines from prefswindowclass.cpp:
Thore always was good at help to find bugs (you can't imagine how much he help us at begining with first version of odyssey port).
As for your issues : yeah, i checked and its the same and for old 1.23 code, and for latest one on github, so i redirect it all to deadwood so he can fix code on github, and i in meantime will fix it in our current 1.23
First, let me post my THANKS to kas1e, Mick and anyone else that decided to jump back into the work on odyssey. It's great to see something happening again.
I've been running the new releases of odyssey on my SAM, X1K and X5K and there does seem to be some boost in speed. Nice to see.
I was most curious to see whether the new versions (especially v5) might have fixed odyssey's memory glutony.
Unfortunately, it's still there. This morning I surfed a couple js/css/gfx heavy sites and ran free memory down to ~620MB and then jumped to this relatively light site. No memory was freed.
I know someone said that odyssey/webkit doesn't deallocate unused memory, but that's not the same as freeing it. Odyssey is not the only app running.
With where AmigaOS is today, it doesn't deal well with low memory situations.
At the very least, would it be possible to add a minimum free memory setting in odyssey?
Finally, I'm noticing more lockups when the new odysseys are running. Unfortunately, I've not seen a repeatable test case, it just happens after having surfed a while. More memory issues?
Before, when you restarted Odyssey, password field copied itself in the username field, now it doesn't happens, but it doesn't work; it says: "couldn't connect to server".
Although I tried the previous version and the proxy server works.
Just I'm here I've a question...recently my bank have updated his website and now it complains to me that my browser havent TLS protection secuiry we have any chanche to get that on OWB soon?
I have WebKit contacted. But in my opinion it make no sense that user contact other developers. What I can ask? I can put only simple question. For me is very strange that no Amiga developer have asked WebKit about support for 3 years. I think you have right, we should ask someone from Linux PPC community, but isn't it better when questions come from Amiga developer? We have problem that nobody cares about Odyssey... We don't have one team to lead this project, so no one knows who should ask question or try to get support from others platforms. We should have leader to manage such big application. Or I'm wrong?
@radzik That's something, but since the WebKit team no longer supports big endian platform, the chances of that achieving anything was slim. This is a problem that affects the users the most. It's in their best interest to band together, organize, and try to find someone who is willing to do the job. Just waiting and expecting someone to do it for them will lead nowhere.
@Capehill While that's true to some degree, that's not what I meant. They have to find programmers and ask them whether they are interested in fixing JavaScriptCore to work on big endian platforms again. This only requires no programming skill, just free time. I'll stop offing this thread, I've ranted long enough :)
Thanks for all the updates. I haven't been responding here, but I've used 3,4,6, and 7 with good results. The only glitch I've had was one time with 6 getting the "child process" window when exiting, with an "Acknowledge" button to click it away. This response is being done with revision 7.
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
