I recently compiled NetSurf 3.9 on Linux and it was pretty bloody slow even on my PC so maybe the problem is that NetSurf has simply got too much for low powered machines?   

Unfortunately this tends to happen with large open source projects as more features are added it becomes harder to run ports on older machines, ScummVM is a good example of this (try running version 2.1 on an 030!).

I appreciate your AmigaOS porting efforts Chris 

Quote from: my_pc_is_amiga on August 20, 2019, 05:10:03 AM

I just did multiple double clicks of the CMD icon (i.e. enable/disable/enable/disable, etc), and eventually got the hit.  This is with MULTIPLE=TRUE and NOTIFY=TRUE tooltypes and FILE=ram:CMD_file

See above.  This hit is coming from a FreeEntry() call which releaes 18 bytes of memory from an AllocEntry() call of a corresponding size. There is no place in the CMD executable nor in the operating system where 18 bytes are allocated via AllocEntry() during the exeuction of a binary. In fact, AllocEntry() is not used by CMD at all, but only by Create(New)Proc of the Os, and there only with 20 bytes (for the seglist array) and not with 18 bytes.

I cannot reproduce this here. Hence, this is due to some other patch, hack or modification of the operating system. I cannot fix what does not come from Os components.

Thomas, thanks for checking this.   I wasn't tracing my steps carefully enough.  Enabling/Disabling CMD multiple times alone does not cause the hit as I originally posted.  I tried that alone and did not see it.   It is only after I do the "ECHO >PRT:" below and then remove CMD redirection that I get the hit.


1) Set these options in the ToolTypes for CMD:
MULTIPLE=TRUE
NOTIFY=TRUE
FILE=ram:CMD_
2) Double click CMD in workbench to install redirection.
3) In shell do this, ECHO >PRT: "Test"
4) Double click on "CMD" icon in workbench.  This will of course remove it.  It is at this point that I get the hit.


Could you check one more time if this is making any more sense or if you can reproduce?  I don't have any known patches in my system (just running LockSmith, MuForce, and MuGa). 

C, D and Python, in that order.

Further down the list, I probably like Javascript better than most, and Java somewhat less.

I just did multiple double clicks of the CMD icon (i.e. enable/disable/enable/disable, etc), and eventually got the hit.  This is with MULTIPLE=TRUE and NOTIFY=TRUE tooltypes and FILE=ram:CMD_file

See above.  This hit is coming from a FreeEntry() call which releaes 18 bytes of memory from an AllocEntry() call of a corresponding size. There is no place in the CMD executable nor in the operating system where 18 bytes are allocated via AllocEntry() during the exeuction of a binary. In fact, AllocEntry() is not used by CMD at all, but only by Create(New)Proc of the Os, and there only with 20 bytes (for the seglist array) and not with 18 bytes.

I cannot reproduce this here. Hence, this is due to some other patch, hack or modification of the operating system. I cannot fix what does not come from Os components.

four times was just a "Feeling". I Checked with Startpage of a1k.org ... in 3.7 it Needs 18 Seconds in 3.9 60,2.. so 4 times is not that much incorrect.... And on this page there is nothing Special....