@Capehill If only bug can be reproduced, then i can add gstabs just for single object surely to see line where it crashes, but, i think its the same kind of "random-rare-crasehes-dunno-when-dunno-how"..
Everyone who had crashes in cairo_clip_intersect_rectangle_box() as the last function in stacktrace (visually it first one at top of stack trace) plz check that binary at top of beta06 installation:
Confirmed this fixes the cairo crash on my X1000! Another bug squashed. Nice!
Btw. interesting that while an actual Firefox (that I use) tests better overall, Odyssey wins in some areas, like video, and both browsers have sections with zero points.
thanks for the new beta06! While downloading the beta release (with beta05) the download speed is relatively slow (200 kB/sec) while downloading similar sized files in OS4Depot is way quicker (1000 kB/sec) with my connection. Wondering, could you release these betas to e.g. OS4Depot for greater bandwith, even if these still are betas?
While downloading the beta release (with beta05) the download speed is relatively slow (200 kB/sec) while downloading similar sized files in OS4Depot is way quicker (1000 kB/sec) with my connection.
You mean that downloading from my site is slower than from os4depot ? Yes, but is it problem at all ?:) I mean, those betas are for betatesters who can live with such a small issues like how fast or slow they download betas. Actually the browser is important, not where it placed for betatesters (not for plain users), right ?:)
Quote:
Wondering, could you release these betas to e.g. OS4Depot for greater bandwith, even if these still are betas?
Plan is to make few more betas before os4depot upload. If you for real have issues with slow speed of downloading from my site, and those issues is important enough for you, then better wait os4depot upload which will happens once we migrate to all last 3d party libs and fix some more bugs. Not that soon probably, but at least you can download it not in 5 minutes , but in 10 seconds and then have updated version :)
@All
Anyone who have issues like "betas placed on site which is not as fast as i want" , or "betas placed on the place where i didn't want to go and don't want to remember new site" , or another really "important" issues, better to not use betas at all, but wait os4depot upload. That way only those ones will test beta releases who want to spend their time on and that including living with other issues in process on which there is really no needs to spend our time which can be spend on real issues.
Hi kas1e, Thanks for the latest beta and your work. And the latest spoffing added I don't really know the Odyssey story, having no hardware for amigaos4.1FE and before you started the new work on the new versions it was slow to be used with winUAE. Now he works very well.
I took a look at the Cygwin guide for how to compile the sources for amigaos-ppc, I used it a long time ago for other things.
Are the current sources in the public domain and freely editable? Thanks again for a possible reply.
@white I think it's a combination of various licenses, it's definitely not public domain. The WebKit browser engine is a combination of LGPL and BSD...
Thank you for your hard work and all the amigans involved. I`ve been using beta06 for a week now and is really faster than the old 1.23 (just like the other betas, after recompiling & updating the includes). I could not extensively test the player due to CPU limitations (Sam440Flex here), but it reproduces every video nicely (any hints/optimization settings for low CPU power? There was a script time ago, that optimized youtube settings).
I`ve noticed also a 100%CPU usage, when the OWB-Timer subtask runs.
Now a MUI thing maybe : I have Odyssey running on its own MUI screen. When switched to full screen, it stays on its own screen and returning to normal window goes to the Workbench screen automatically. It will not switch back to Odyssey screen even if I choose to do so directly, instead I have to choose WB screen first (the window is already there) and then its own screen.
Now a MUI thing maybe : I have Odyssey running on its own MUI screen. When switched to full screen, it stays on its own screen and returning to normal window goes to the Workbench screen automatically. It will not switch back to Odyssey screen even if I choose to do so directly, instead I have to choose WB screen first (the window is already there) and then its own screen.
I run Odyssey on it's own MUI screen as well and don't have this problem. For me it stays on the custom screen. Mabye it an MUI setting? I have my screen setup to be like Workbench.