Firefox 技術支援討論區

Hello,

I just upgraded to firefox 92. When I right click on a string I wrote such as : "zaiuryezoyhdsofh" with spell check enabled, Firefox hangs for minutes and my CPU is 100%. It happens only on a string and on every websites, even google search.

I'm able to reproduce in safe mode, but FF doesn't want to crash so no report.

System : Debian Buster 10.

Hello,

I'm using firefox-dev under linux debian buster and would like to keep it as my default browser and even more after all those recent articles in media where they say firefox is loosing its users.

I received the newletter from netflix and I tried to watch a trailer (https://www.netflix.com/watch/81387952?trkid=13710079&MSG_TITLE=81387952&lnktrk=EMP&g=79ECBFC7B02B1269F43D15B11C9BA9F56455502C&lkid=TRAILER_CTA) but even after i clicked on accept drm, the video was stuck nothing happened I just saw one single fixed picture of the movie.

Later, I was on facebook, trying to watch a video (https://www.facebook.com/demotivateur/videos/5009752875718446) and the same here without any DRM...

For both of the cases I opened chrome pasted the url and video played very well.

Is there something to tweak to make it work ? Is it because I'm under debian ?

I don't want friends to switch to chrome but I understand them sometimes.

Kr,

Eric

Hi. I'm having some issues to render CSS effects and videos after last update (version 91.4.1esr). Before that update everything was pretty smooth, but since the update the browser is getting very slow to render "everything that moves" on the screen. The movements are poor on CSS or videos, its like it was exceeding in any video/memory resources, get very slow and nothing smooth.

My system: - Linux Debian 11 (fully updated) 64bits; - Processor: Xeon 2670-v3; - Ram: 32GB; - Graphics: Quadro 2000; - Graphics Driver: official Nvidia 390.144 x86 with 32bits support downloaded by Nvidia's site.

Any hints on how can I solve this?

Very similar to posts in previous years that are archived and largely unanswered or not up-to-date.

I opened up my a Firefox session to find out I was logged out of sync and when I logged back in all my passwords where erased.

This has been stable for the last 10 months and Firefox has provided a reliable password archive with nice syncing features. However, this is a deal breaker, since I cannot loose the login credentials randomly.

No updates. No conscious logging out. No disregarding warnings etc.

Anyway to revert or retrieve?

Hi, I am running the french FF 79.0 64 bit I just started to download the latest iso of debian 10.5 from the official Mirror and got the FF warning that it contains a virus. I am not sure if you have a team to check false positive as this is the official site and that it was released only yesterday https://cdimage.debian.org/debian-cd/current/amd64/iso-dvd/debian-10.5.0-amd64-DVD-1.iso and I am getting worried after I got this message. Thank you in advance. Regards, Stephane

I am on Firefox 91.0.1 (64-bit) on Debian 11. As the example screenshot shows, UI on many webpages looks wierd and inconsistent. I also use Firefox on my work computer, which is on Windows 10 and has no such issues. So, I think this is because of some dependency issues with my Debian machine. How do I fix this?

I am running Firefox Browser 97.01 (64bit) Mozilla Firefox Snap for Ubuntu canonical 002-1.0 on Raspberry Pi Debian GNU/Linux 11 (bullseye) version ID 11.

I am trying to stream various TV services like CTV.ca, CBC.ca, etc. I am getting the following error message: This video file cannot be played.(Error Code: 102630)

I have tried the solutions recommended in the forum with no luck.

What am I missing?

Regards.

Hello. I want to report a performance issue (slowness) caused by the overexcesive virtual memory usage by Firefox sub-processess.

State description

After runing Firefox, I observed in the htop the process of Firefox (and it's sub-processes) and compared it with the about:processes

I had discovered that main Firefox process opens many sub-processess that aren't even used (they does not appear on the mentioned above "about" page).

Additionally, in some mement, at latest one of the created sub-process start to use 28.6 GB of virtual memory, like each of the created by it sub-process. This causes quite big loose of stability of the browser and even system

Hello, First let me thank Mozilla again for a great experience. I've been using Firefox as my main browser for many years and since some time I also started supporting Mozilla financially with whatever little I can with recurring payments. To the problem: since some time patch / commit view on HitHub with Firefox is broken. I guess many @mozilla have github accounts so you can open and read https://support.github.com/ticket/1318472 but to summarise: my first entry there was: ``` When viewing Linux kernel style Pull Requests on GitHub, using Firefox, TABs are displayed as 4 spaces, which is confusing, since the default is 8 spaces, which is also what is displayed in chrome and chromium. E.g. https://github.com/thesofproject/sof/pull/4747/commits/e9cc9312841a9329797b0b676335c8cb1a0dc779 ``` then a screenshot (attached) and a clarification to it: ``` As you can see there the patch area between lines 238 and 245 is wrongly indented by 4 spaces, whereas areas above and below are correctly indented by 8 spaces. ``` Then more: ``` No, space isn't used for indentation in that code. They can download raw code and verify, I'm sure they know how to do that. Why don't they just reproduce that themselves? Start Firefox, navigate to any PR commit like https://github.com/thesofproject/sof/pull/4884/commits/b19a64df2c2fcd63d7407ef500fd3312287c8995 and click arrows above and below the diff to display surrounding code. Then navigate to or download the raw patch https://github.com/thesofproject/sof/commit/b19a64df2c2fcd63d7407ef500fd3312287c8995.patch to see TABs used everywhere. Should be very easy to verify. ``` and their last reply was ``` From a technical standpoint this is not a regression. It's a problem with the way firefox interprets the combination of the tab-size css and the particular markdown we use for our diffs.

After reviewing the Issue in more detail there it has not been prioritized and will most likely not be addressed in the near future. ``` This is a deal-breaker for me. I spend hours daily reviewing GitHub pull requests. And I'd really not want to use a different browser just because of this... Please help! Thanks Guennadi