recondas wrote:
... just passin' thru both times.
So whadja think about the soil ?
diegel wrote: I uploaded neko_firefox3.0.19_beta3.tardist to incoming
Please report in this thread only severe issues in conjunction with the firefox3 build.
I will not fix problems with depending nekoware packages,
firefox extensions,
There really is a problem with https://
or broken Internet sites.
Code: Select all
urchin 3% firefox3
moz_run_program[36]: 1351 Memory fault
) And speed-wise, it's quite usable.
Code: Select all
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
moz_run_program[36]: 1417 Abort
This may be a version-specific problem ?
diegel wrote: I can't see any ssl problem here. Probably it is a packaging issue, I will test ssl with a fresh installation today. But if I don't see a problem, I am not able to debug it.
diegel wrote: Try moving your .mozilla to .mozilla.bak and start firefox3.
ajw99uk wrote: Changing .mozilla/firefox to .mozilla/firefox.bak
diegel wrote: Or copy libfreebl3.chk and libfreebl3.so from /usr/nekoware/lib/firefox-2.0.0.22pre to /usr/nekoware/lib/firefox-3.0.19. I will add the libraries to the next package.
Code: Select all
(firefox-bin:7001): Pango-WARNING **: shaping failure, expect ugly output. shape-engine='BasicEngineFc', font='Forefront Book 11.51953125', text='to http://mplayerplug-in.sourceforge.net/download.php.'
Code: Select all
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
moz_run_program[36]: 1948 Abort
canavan wrote: Additionally, beta3 crashes reliably ... when opening http://www.kickstarter.com/projects/wei ... -smbc-coll
canavan wrote: I haven't seen any glitches.
Code: Select all
moz_run_program[36]: 1868 Memory fault
Code: Select all
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
ClassicHasClass wrote: Are you running out of memory, perchance?
canavan wrote: You may be running out of address space, and a rqs/rqsall shuffle may be needed.
Code: Select all
rqs32: Fatal Error: A /usr/nekoware/lib/firefox-3.0.19/libssl3.so region with address 0x400000 (region end address is 0x43c000). Failed due to address overlap. Please check firefox-bin and its liblist to make sure that it and its NEEDED shared objects have no overlaps among them by running "elfdump -o" on each of them
Code: Select all
(stuff)
libpng.so.3 => /usr/nekoware/lib/libpng.so.3
5586:firefox-bin: rld: Warning: elfmap: running new 32-bit executable but finding old 32-bit shared object /usr/lib/libCsup.so in the search path. You may not have set the environment variables correctly, please set LD_LIBRARY_PATH for old 32-bit objects, LD_LIBRARYN32_PATH for new 32-bit objects and LD_LIBRARY64_PATH for 64-bit objects (e_flags 0x10000003) -- continue searching ...
libCsup.so => /usr/lib32/libCsup.so
(more stuff)
ShadeOfBlue wrote: Some of the old firefox2 libraries may still be present in that list, this will rebuild the entire index and hopefully solve the problem.
canavan wrote: Now I'll have to figure out how to configure fonts with subpixel antialiasing and no color fringing.
canavan wrote: Your screenshot looks like you have not configured fontconf at all. Try adjusting things in /usr/nekoware/etc/fonts/local.conf and adding some more fonts
recondas wrote: Just got done installing the latest revision ff3.0.19 on an Onyx350 with IP graphics (dual-pipe, 8P, 16GB).
One crash so far:....which is the same crash I'd get with neko_ff2 on a fairly regular basis.Code: Select all
|$(0x6dd)ALERT: Process [firefox-bin] 4512 generated trap, but has signal 10 held or ignored
So far, FF3 crashes about as frequently for me as FF2. But the page rendering is superior. And the crashes have been addressed in other versions of FF so there is a potential upgrade path, where FF2 was a dead end.
Update : I uninstalled ff2 and the issue with slow rendering went away. Since the uninstalling ff2 I also haven't been able to reproduce the trap error with ff3, so it looks like removing ff2 may have resolved the issues I experienced.
recondas wrote: Knock on wood - ff3 hasn't crashed since I figured out the remove-ff2-first part.
NS ( and the rest of the security add-ons I mentioned in the other ff3.0.19 thread ) are all up and running in ff3 w/o problem.
recondas wrote: You might want to consider re-adding noscript ... Read a couple of the articles on sfgate and even followed a couple the links - didn't experience any crashes.
Code: Select all
moz_run_program[36]: 2464 Memory fault
Code: Select all
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
moz_run_program[36]: 2661 Abort
robespierre wrote: The Personal DECstation was also a rare machine for the era that used one serial bus for all its input peripherals. At the time, only ADB (used by Apple and NeXT) had that architecture; other workstations used multiple rs232 or rs423 signals for each device, or, like PCs, had a single serial bus per device.
diegel wrote: I have seen a pango related error, I am quit 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?