Thanks for the detailed answer. We have a lot of multiprocessor machines here. Do you think
Code:
-ftree-parallelize-loops=4
makes any sense?
_________________
ajw99uk wrote: seems fine on http sites (though only tried a handful so far) but not https - I'm getting the error
Incorrect Response
Firefox doesn't know how to communicate with the server.
The site responded to the network request in an unexpected way and the browser cannot continue.
Perhaps bad preferences on my part?
Yes, both are working fine.hamei wrote: Can you connect to ixquick and duckduckgo without problems ? Also the mozilla extensions site refuses to connect.
firefox uses it's own libssl3.soI am using the neko_openssl 0.9.8x , don't know if that is a problem. Does Firefox use an external SSL library ? i didn't see anything about that in the configure settings but ... could there be a clash there ?
Yes, there are major differences. The javascript engine is new designed and contains a lot of C++ code, in 3.0 javascript is C only. Additionally a lot of media tools for sound and video are added in 3.5, but you can disable this of course. I tried to compile 3.5 and came to the same point dexter had reached. I decided to debug 3.0 first, because I was sure to run into this bus error problem again in 3.5. Probably my fixes in 3.0 will fix firefox 3.5 as well, but at this point we are debugging firefox 3.0.hamei wrote: diegel : is there a major change between 3.0 and 3.5 ? I know there was a big different at 3.6 but is it possible that 3.5 would solve a few more problems ?
I would try to reinstall all nekoware packages listed in the release notes. I did not see this error so far. Memory should not be the problem, firefox3 starts with about 130mb and if you open very much tabs you may need up to 300mb. I write this message on my fuel currently, so it should run on your fuel without problems.BetXen wrote: but I still have problems on my fuel (also 6.5.30). It is probably due to bad library paths and so on. I could identify pendant references to libgdk_pixbuf (now "ldd .../firefox'bin" gives no error anymore) and tried to renew .rqsfiles as ShadOfBlue suggested... without success for the moment. I always have the std::bad_alloc issue.
You can try it. It will compile with the included patch with mips pro. The javascript engine will not run at all, but you can move the gcc compiled libmozjs.so to the mips pro build. I didn't test it very much, because for me it was slower than the gcc build and it was very unstable. With firefox 3.5 the libmozjs.so workaround will not work anymore, since it contains c++ code.foetz wrote: i'm still somewhat skeptical about the gcc faster than mips pro builds but firefox3 is different so i'll see soon enough.
Yes, you can crash firefox with such kind of sites, but I did not see the errors you reported. I have seen a pango related error, I am quite sure this is a problem of the current pango package. I also have seen a bus error, but I was not able to reproduce it, so I can't debug it. There must be something different with your setup, are you using your firefox with a remote X11 server?hamei wrote: The interesting part is, if I stick to old-fashioned websites (nekochan, graphics magick, personal sites) this is not a problem at all. It's when you go to the javascript-laden advertising-driven "rich user experience" modern sites-of-shit that all hell breaks loose.
Okay, all this sites are ipv6 enabled.Voralyan wrote: These are the pages are affected by this:
http://www.google.com (also other TLDs)
http://www.bing.com
http://www.mozilla.org
And these sites are ipv4 only.
The patchfile is /usr/nekoware/patch/neko_firefox3.patch and it's not installed by default.telackey wrote: Hmm, I've got it installed and it runs fine, but I don't see the patch file under /usr/nekoware/patch[es] ]
I don't think this is a version problem. I can see the errors here as well. But I don't use very fancy sites with lots of adds, so this is not a real problem for me. For my daily work this version of firefox works without any crashes. I think there was an optimization problem within the xpcom libraries, that caused segmentation faults. I have seen the bus error hamei reported, but I don't have any idea how to debug it, since I was never able to reproduce it.foetz wrote: it might help if diegel could post the list of what he has installed on his dev machine. only a clean(!) and similar environment can yield proper results.
This issue has been discussed earlier. You need to configure /usr/nekoware/etc/fonts/local.conf see page 3 of this thread. I think I will add a configured version of this file in my firefox3 complete package.mapesdhs wrote: :D
I'd say the only thing that bugs me atm is the browser not displaying certain characters correctly,
especially the various kinds of quote marks.