Firefox renders text incorrectly.
This is a 2019 bump to https://support.mozilla.org/en-US/questions/1221476 . Firefox renders text incorrectly. It uses DirectWrite, which is incorrect, it should use GDI … (funda kabanzi)
This is a 2019 bump to https://support.mozilla.org/en-US/questions/1221476 .
Firefox renders text incorrectly. It uses DirectWrite, which is incorrect, it should use GDI to render text. In all the next updates please immediately rewrite the Microsoft Windows renderer sourcecode to render all text with GDI.
I-Firefox
Firefox "updated in background" forces restart that leaves new instance bricked, must reboot. ubuntu 16.04, firefox 68.0.1
ubuntu 16.04, firefox 68.0.1. New instance started after "updated in background" restart just sits there. Add-ons are not started, tabs are not restored as promised. T… (funda kabanzi)
ubuntu 16.04, firefox 68.0.1. New instance started after "updated in background" restart just sits there. Add-ons are not started, tabs are not restored as promised. Typing in URL bar and hitting enter does nothing. No response to attempt to open a bookmark. Typing "about:support", no response. I tried removing and re-installing firefox with "sudo apt", no help. Starting firefox without addons, no help. The "about:firefox" display shows no change in version number. A reboot is the only thing that cures this. It has now happened 8 times (8/2, 8/5, 8/9. 8/16 and 4 times earlier). I have about-buildconfig, about-firefox and about-support from 8/2 and 8/5 if they would be helpful.
File upload causes Firefox to be unresponsive and must close browser to continue. Tried all the fixes. Other browsers fine. Several computers.
Please if you have any suggestions, I'll try them. I thought a new clean computer might solve the problem, but no luck there either.
Firefox 68.0.1 crashes on startup | Ubuntu 18.04
Hello everyone, I've recently had to recover my home directory on a machine running Ubuntu 18.04 from a backup... Everything works fine BUT Firefox which keeps crashing r… (funda kabanzi)
Hello everyone, I've recently had to recover my home directory on a machine running Ubuntu 18.04 from a backup... Everything works fine BUT Firefox which keeps crashing right at startup. Nothing happens until the report window opens up.
What I've tried so far:
trying to run it from terminal, trying to run it from terminal in safe-mode, purging and reinstalling it via apt, purging it again and reinstalling via downloaded tar.bz2 from mozilla website
When running from terminal I get the following:
ExceptionHandler::GenerateDump cloned child 5853
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Failed to open curl lib from binary, use libcurl.so instead
Report ID: bp-efb679bf-6ac0-4c24-9996-c0f3b0190803
I'd be glad for any help, thank you very much! Please let me know if you need more details. :)
Poor multi-tab user responsivness is caused by primitive FF multi-tasking/ threading.
Could this note be referred please, to the FF programming manager? First my congrats on FF overall of course, to you and your many volunteers. But I notice a large phil… (funda kabanzi)
Could this note be referred please, to the FF programming manager? First my congrats on FF overall of course, to you and your many volunteers. But I notice a large philosophical programming problem which you might consider.
This problem mostly shows with multiple tabs open. Web servers certainly are slow, and many pages' Html etc poor. This all results in lots of delays such as reported during:
Waiting for () Read () Transferring data from () Performing a TLS handshake to () Connecting to ()
These display the moving "working" dot in the left of the affected tab title. And less often, "(not responding)" in FF's title bar, which eventually gets cleared automatically.
I have reviewed all 17 screens, and a number of the individual results, from today's FF forum search of:
169 results for (not responding) for Firefox
None address the lack of prioritized co-operative multi-tasking/ threading, DURING such delays as "Waiting for ()". During such a necessary wait, it is very slow at best, e.g. for a user to switch tabs. Even to one which is ready for display.
Responsiveness to user input should be the top multi-tasking priority. Tab switching. Rendering/ display of the foreground tab. Scrolling that down. Tab closing by user!, and "X" to STOP a page from loading -- give those user clicks priority. Let's not have to wait 10 seconds for a right-click to open its option box. Let the other busy tabs finish up their work, overlapped in the background priority-wise.
This could be done now, but perhaps it would be difficult for volunteer programmers. Worse case might require a custom replacement, for the effective TCP part of the default vanilla TCP/IP stack. However I suspect a lot could be fixed short of that, with the correct management encouragement and guidelines. At least if the continuous motion of the "busy dot" indicator in the tab title is a task, just change that to something like just gray-ed out while busy.
My experience is with much headroom: CPU (50%), memory, disk, and network bandwidth, per Task Manager. NO McAfee. Mainly just ZoneAlarm taking 30% of that CPU 50% usage. This is not a problem with start-up delay. And delays within only one open tab are necessary, of course. Cheers