Netsurf and RISC OS 5.19 Beagleboard crash
Chris Dewhurst (1709) 167 posts |
Please redirect me if this is or has been covered; have posted on the Netsurf site too as not sure if RISC OS specific or Netsurf specific. Using RISC OS 5.19 (23-Dec-12) on Beagle and Netsurf 2.9 (27-Feb-12). Machine crashes on certain pages for example going to this forum page. “Internal error on data transfer at &xxxxxxxx” then “Filecore in use” which stiffs the machine. Turning off Alignment Exceptions seems to prevent the problem but not sure if this is sensible in the long term as it could interfere with other apps running. thanks |
Keith Dunlop (214) 162 posts |
Have you got Netsurf → Choices → Images set to “Use OS”? Just a thought… |
Steve Pampling (1551) 8170 posts |
As Keith said – change the image processing options. Tinct needs a rebuild, but it’s third party. |
Chris Dewhurst (1709) 167 posts |
Sorry chaps – tried setting “Use OS” in both Foreground and Background under Choices but…same result. Even after reboot. Netsurf crashes with error messages reported before :( Any other ideas? thanks. |
Chris Johnson (125) 825 posts |
Well, the latest json and jsoff versions of NetSurf work fine with AEs on. I have never had any trouble with it since I got the BB 18 months ago or more once Tinct was disabled. |
Keith Dunlop (214) 162 posts |
What else have you got running? I need to do more research but I have found that !DigitalCD and !Netsurf cause each other (as in one or the other) to crash when they are both loaded… |
Chris Dewhurst (1709) 167 posts |
Nothing else running and nothing extra (as far as I am aware) added to the Boot sequence to be initialised on start up. |
Chris Dewhurst (1709) 167 posts |
I’ve tried the test version of Netsurf with JS from http://ci.netsurf-browser.org/builds/riscos/NetSurf-gcc-json-739.zip and here that doesn’t even start up without AEs switched off. (The link above is as given over in the “General > Netsurf with javascript” forum) |
Steve Pampling (1551) 8170 posts |
http://ci.netsurf-browser.org/builds/riscos/ might be a better link to publish. Note that since the link(previous) is to a specific nightly build it is likely to be superceded at regular intervals by more capable and probably bug fixed versions. Equally the latest could have some bug that needs fixing. You take a chance with bleeding edge versions, just as people are doing with the majority of the Pi, beagle, pandora OS revisions. |