duktape error NetSurf OS3

[chris]

@freeaks

The intention is the builds will be from CI, the current situation is an interim measure.  The build date is in Project=>About.

I'd like to know more about the crashing, I've not seen that here.

[utri007]

I'd like to know more about the crashing, I've not seen that here.

I haven't had that kind of problem ever.

I belive that scrolling is compromize between, speed, ram usage and useability.

UAE doesn't give right picture of it.

[freeaks]

@chris,

about the build date: the goal was to avoid unnecessary downloads and installs just to check freshness of the link..
what you say makes me as a user, download and install new copy of netsurf just to check if it was updated or not. this is not practical. better put a date string beside the download link.

about the crash, sur,e i'd be willing to give any output i could,
what tool do you suggest to get you more info ?
right now i can see the usual:

"NetSurf
Program failed (error #80000004)
Wait for disk activity to finish."

that probably won't help you much, i'm a bit rusty about amiga things,
what kind of tool was there, was it 'sashimi' that software that could give more detailled debug output ?

[chris]

about the build date: the goal was to avoid unnecessary downloads and installs just to check freshness of the link..

Yes, I know, but they are split over two different servers so I can't easily fetch the filedate.  This will be irrelevant when we get CI builds.

about the crash, sur,e i'd be willing to give any output i could,
what tool do you suggest to get you more info ?
right now i can see the usual:

"NetSurf
Program failed (error #80000004)
Wait for disk activity to finish."

that probably won't help you much, i'm a bit rusty about amiga things,
what kind of tool was there, was it 'sashimi' that software that could give more detailled debug output ?

Enforcer maybe?  80000004 is an illegal instruction error apparently.  It could be the CPU, memory or - if you're using UAE - an emulation error.

[freeaks]

yes i'm using uae at the moment,
this week i will switch to a600 + vampire (i'm waiting for parts)

i have mungwall, enforcer and sashimi running in the background.
when i quit netsurf, i get the crash, but nothing from those tools is reported.
whereas for the previous build that was direct p96 on rtg,
i had gfx corruption, but no crashs on exit.
i can reproduce this everytime.

[DNADNL]

Hello World !

@chris
I would like to activate the Debug commands (DUK_D, DUK_DD, DUK_DDD, DUK_DPRINT...), but what I tried didn't work. Could you please tell me how to do ?

[DNADNL]

yes i'm using uae at the moment,
this week i will switch to a600 + vampire (i'm waiting for parts)

i have mungwall, enforcer and sashimi running in the background.
when i quit netsurf, i get the crash, but nothing from those tools is reported.
whereas for the previous build that was direct p96 on rtg,
i had gfx corruption, but no crashs on exit.
i can reproduce this everytime.

I have the same kind of issue on Happiga for Raspberry Pi (the 8000-0004 Issue), even if I use Picasso 96 ; and the same issue comes sometimes to AmiKit. I think It's a memory leak here, as the RPi has "only" 1GB (and 8 MB allocated to The Amiga System), and AmiKit has 8 GB I think.

[freeaks]

i installed smartcrash, does this info helps ?
http://alturl.com/rc56g  (pic of smartcrash requester)

edit: i have 128mb allocated to amiga

[DNADNL]

i installed smartcrash, does this info helps ?
http://alturl.com/rc56g  (pic of smartcrash requester)

edit: i have 128mb allocated to amiga

I can't really help you on that point, sry !.
Did you use SnoopDOS, also ? This can log the whole activity done on your computer (for example, when you launch NetSurf), and you can obtain a TXT file, then, much easier to read ^^

[freeaks]

i don't think it will be useful for this but, here is the snoopdoslog:
http://paste.debian.net/789741/

[DNADNL]

i don't think it will be useful for this but, here is the snoopdoslog:
http://paste.debian.net/789741/

Well, it doesn't seem to be useful, yeah... Maybe chris will have an idea with all your files.

[chris]

Hello World !

@chris
I would like to activate the Debug commands (DUK_D, DUK_DD, DUK_DDD, DUK_DPRINT...), but what I tried didn't work. Could you please tell me how to do ?

Add the following at the top of duk_custom.h:

Code: [Select]


#define DUK_USE_DEBUG 1
#define DUK_USE_DEBUG_LEVEL 2
#define DUK_USE_DPRINT 1
#define DUK_USE_DDPRINT 1


You might want to fiddle with the value of DEBUG_LEVEL, and either add DDDPRINT or remove DDPRINT.  The debug defines don't seem to work entirely as documented.

[chris]

i installed smartcrash, does this info helps ?
http://alturl.com/rc56g  (pic of smartcrash requester)

Means nothing to me.  Maybe somebody with 68k knowledge can decode it?

i don't think it will be useful for this but, here is the snoopdoslog:
http://paste.debian.net/789741/

Would probably have been more useful if the text wasn't all truncated at U.

Anyway, a NetSurf log would be more helpful:
netsurf -v >ram:ns.log

There isn't too much logging on exit but it might help narrow down where the crash is occurring.  I (or DNADNL) can always add more.

[DNADNL]

Add the following at the top of duk_custom.h:

Code: [Select]

#define DUK_USE_DEBUG 1
#define DUK_USE_DEBUG_LEVEL 2
#define DUK_USE_DPRINT 1
#define DUK_USE_DDPRINT 1

You might want to fiddle with the value of DEBUG_LEVEL, and either add DDDPRINT or remove DDPRINT.  The debug defines don't seem to work entirely as documented.

OK, I did this, but it seems nothing appears between the famous rows "Creating new duktape javascript context" and FATAL 56... is it normal ?

Here is what I wrote in duk_config.h :

Code: [Select]

//DNADNL DEBUG
#define DUK_USE_DEBUG 1
#define DUK_USE_DEBUG_LEVEL 2
#define DUK_USE_DPRINT 1
#define DUK_USE_DDPRINT 1
#define DUK_USE_DDDPRINT 1


[chris]

OK, I did this, but it seems nothing appears between the famous rows "Creating new duktape javascript context" and FATAL 56... is it normal ?

Here is what I wrote in duk_config.h :

Code: [Select]


//DNADNL DEBUG
#define DUK_USE_DEBUG 1
#define DUK_USE_DEBUG_LEVEL 2
#define DUK_USE_DPRINT 1
#define DUK_USE_DDPRINT 1
#define DUK_USE_DDDPRINT 1


duk_custom.h, not duk_config.h
It works here, that's all I can say.

[DNADNL]

duk_custom.h, not duk_config.h
It works here, that's all I can say.

Woops ! Misreading, Sorry ! ^^'