Odyssey 1.23 progress: r5 RC2

I find a sure way to the GR - which is still there with the new version - is to use the Show Unread feature on Amiga.org (requires being logged in permanently) and then click on the little "new" icons next to each one. It often results in a DSI, which can sometimes be ignored, sometimes not (and often it results in the CPU going to 100%). And once it has happened, none of the unread threads are shown any more, although I can still use the "new" icons from the forum overview.

Anybody else see this?

Apart from this, I agree that the new one is faster and probably also more stable. Thanks to everyone involved in getting the work rolling!

Best regards,

Niels

@nbache

After a moment, I only had two new messages, but clicking on these only worked as if intended.

@thread

Where are the temporary files going to ?

I think everything should be done in RAM since its 100x + faster.

Has anyone used RAD: RAM: combo ? just wondering speeds and data alignment.

@Kas1e

One of the usual crash I get with any version of Odyssey, without any know reason and in a random way.

https://amiga-ng.org/resources/CrashLo ... y_2020-03-05_21-12-39.txt

@K-L
While crash is null-pointer one, all the crashes where you see lot of "WEBCORE" in stacktrace mean bugs in webkit's core. This one through ends with cairo+pixman, so maybe using more fresher ones will help, but i doubt.

Dind't have reproducable site so i can try to build with fresh cairo+pixman to see if it helps ?

@kas1e

Nope, it's totally random. This time it crashed while opening AmigaWorld (but only this time).

@kas1e

Ok finally got the first one .. a bit strange as it wasnt happened loading a page or browsing internet .. but just when i selected the owb window (i was using another software)--- aniway it's a stop one that force me to reboot amigaos still works but the application freezed

-------------------
Crash log for task "Odyssey"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x01848010
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003

Register dump:
GPR (General Purpose Registers):
0: 01847E88 53A4AE80 00000000 00000001 53A4AE88 53A4B178 53A4B178 53FF0000
8: 00000000 00000002 00000000 02030000 48424884 53C6DD7C 00000000 54C16D00
16: 536F4028 53A4B0E8 01A6DF74 53FF528C 5FFFAC00 53A4B180 00000000 8042545B
24: 8042D777 00000001 8042C008 00000001 80422DA9 804237F9 53A4AE88 5FFF9300


FPR (Floating Point Registers, NaN = Not a Number):
0: nan nan 9 nan
4: nan 0 0 0
8: 4.5036e+15 nan 378.5 128
12: 7.63399e-305 0 0 -0
16: 1.32625e-315 0 0 0
20: 0 0 0 1.61895e-319
24: 0 0 2.65249e-315 0
28: 0 1.35808e-312 1.3581e-312 -2.15904e-78

FPSCR (Floating Point Status and Control Register): 0xA2008100


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x50736DA0
Instruction Pointer (ip) : 0x01848010
Xtended Exception (xer) : 0x018233AC
Count (ctr) : 0x00000000
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x01842B34
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 5857158E 00000003 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 53A4B1B0
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x01848010 belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
native kernel module kernel+0x00048010
native kernel module kernel+0x00047dc0
LIBS:muimaster.library:GroupDispatcher()+0x464 (section 1 @ 0x46ED0)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x000218c8
native kernel module intuition.library.kmod+0x00009ee4
native kernel module intuition.library.kmod+0x0000a184
LIBS:mui/Title.mui:_Dispatcher()+0x1b1c (section 1 @ 0x72B8)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0000a2d8
native kernel module intuition.library.kmod+0x00009f8c
LIBS:muimaster.library:SendIMsgs()+0x22c (section 1 @ 0x7DED0)
LIBS:muimaster.library:m_Window_Input()+0xa7c (section 1 @ 0x83D58)
LIBS:muimaster.library:WindowDispatcher()+0xdc (section 1 @ 0x885F0)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0000a2ac
Odyssey:_ZL8dispatchP6IClassPmP4_Msg()+0x438 (section 1 @ 0x2EE54)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0000a3f4
LIBS:muimaster.library:m_Application_NewInput()+0x84c (section 1 @ 0x28898)
LIBS:muimaster.library:ApplicationDispatcher()+0xd34 (section 1 @ 0x2DCAC)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0000a2ac
Odyssey:_ZL8dispatchP6IClassPmP4_Msg()+0x128 (section 1 @ 0xF92C)
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0000a3f4
native kernel module intuition.library.kmod+0x0000a034
Odyssey:_Z9main_loopv()+0x168 (section 1 @ 0x13A0)
Odyssey:main()+0x1f0 (section 1 @ 0x1680)
native kernel module newlib.library.kmod+0x000020ac
native kernel module newlib.library.kmod+0x00002d5c
native kernel module newlib.library.kmod+0x00002ef0
Odyssey:_start()+0x170 (section 1 @ 0x214)
native kernel module dos.library.kmod+0x000255c8
native kernel module kernel+0x0003e7b4
native kernel module kernel+0x0003e7fc

@samo79

That one surely mui or mui-code of odyssey. I catch the same kind of crash (also coming from title.mui) and report it to Thore few days ago:

http://muidev.de/ticket/428

Seeing crashlogs, it all seems about the same.

It would be nice if someone could try to reproduce the crash using the supplied binaries with debug symbols included. That way the crashlog contains file names and line numbers.

@Thore
Already got debug crashlog, but was in hurry to go, once will back (few hours) will upload it

@Thematic

(re. my crashes with the Unread feature on Amiga.org)

Quote:Hmm, interesting.

This made me try it out under a clean "public" installation of 4.1FEu1, and there I couldn't reproduce it (so far). It seems it only happens under OS4 beta. I have seen it for a long time, though, so it's not anything that arrived with the latest beta components (nor with the new Odyssey release).

I'll research more and follow it up internally on the beta ML.

BTW, it doesn't happen every time, possibly more often when clicking quickly after the page has loaded. And it also only happens on Amiga.org, not on other sites with that feature (Hyperion's forum, OS4Welt etc.)

Best regards,

Niels

@kas1e

Got another kind of crash, this time when browing the HunoPPC site by opening a page (on same site) in a new tab ... the crash was a DSI one, but for some reason the crashlog cannot be saved at all .. so i saved a grab, ask if you need

Probably the site visited is not so important, but the relevant part of the crash is:

Type: DSI
Pointer instruction: 0x081653C
Alert: 80000003
Module: kernel

@samo79
Quote:

On that grab no stack trace visibly ? I.e. is it the same as you have one time when de-iconify with mui things in stack trace ?


Quote:

You mean this it _not_ relevant part of the crash :) Because without stack trace it show nothing interesting. From all the crashes relevant parts for real is stack traces and disassembly.

@All
So as seems all fine with new curl & openssl, i update those libs also on github, so they are default now.

@kas1e

Quote:

Don't know if it's the same, but maybe that one was different ... today i got the same kind of crash try loading another page

About the crash above, here is the grab with the only informations i was able to catch

https://imgbbb.com/image/TLScYR

I choose the way of the grab because when i press the "write crashlog" button nothing happened, aka the crashlog file will NOT be saved at all and the Grim GUI freezed !
When this happens, in reality the Grim Reaper will save something, and you can see that only after a reboot, but pratically this file is almost useless because its merely an empty file with only the name of the crashlog :-/

@samo
On your screenshot there no stack trace shown sadly (its another tab of GR), which mean we even didnt know in which part it crashes.

@kas1e

Ok, next time i'll got it i will switch the tab first :))

@all
I want to add new agents to made "spoof as" menu to have more modern things, and so far localy i have that (that list of new ones and old ones):




Should we still keep old ones too (like, ie6, firefox25, safari6.0.2, chrome32, etc) together with new ones, or ditch old ones in favor of new ones ? I for myself think that having more choice is always better and we can keep all of them.

What you think ?

@kas1e

I will mantain everything if you ask me

Aniway, are you open enough to accept also a couple of feature request for the MUI GUI ?
Still a couple of things still annoying me since age

@kas1e

Quote:That would be really nice.

Is it possible to let the user define their own agent string in addition? Then it wouldn't get outdated again like the former ones did.

It could e.g. be done in a tooltype or something, not necessarily in the prefs GUI - partly because I assume it would be easier for you, partly because it would be less tempting for novice users to play around with (mess up ).

Best regards,

Niels