Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Pressing play on specific YouTube video causes tab to crash repeatedly, then causing every YouTube tab to crash repeatedly (/tmp directory full)

  • 3 fhreagra
  • 1 leis an bhfadhb seo
  • 31 views
  • Freagra is déanaí ó pavelpopov10

more options

Reproduction steps:

Scenario #1:

1. Go to https://www.youtube.com/watch?v=5EnZZGGxU-g

2. Press the play button in video iframe

3. See your tab crashing

Scenario #2:

1. Go to https://www.youtube.com/

2. Wait couple of seconds

3. See your tab crashing

Scenario #3:

1. Go to https://www.youtube.com/

2. Click on any video preview

3. See your tab crashing immediately

Scenario #2 follows Scenario #1. Scenario #3 being repeated even after restart.


Description:

Repeats each time I press play button on this video frame on that specific page. Tab crashes after such actions repeated after restoration of a tab, in a new tab, also in another window. After some single tab crashes, now any tab with YouTube that's being loaded crashes automatically after a while (DOM loaded as well as video previews, but after some time close to 1-2 sec tab crashes). Issue repeats in safe mode.


Environment details:

  • Firefox 73.0 mint 1.0
  • Linux Mint 19, Kernel 4.15.0-88, Cinnamon DE
  • GPU: Nvidia GTX 960 (driver version 418.87.00)
  • CPU/GPU/RAM/Swap/HDD are looking normal
  • /tmp directory is full!
  • One day I switched media.rdd-process.enabled option in about:config to false ( don't ask why ;) ). Even if I make it true as default, tabs are still crashing
  • Used that version of firefox for some time - worked perfectly. This issue revealed only today on that specific URL


My conjectures:

Conjecture #1: YouTube has broken something today

Conjecture #2: Some time related stuff (date is 28.02.2019 03:00:00 MSK - so by UTC it's 00:00:00 which is strange)

Conjecture #3: This video has a present from Mao with some malicious stuff inside ( still hope my PC won't blow up this morning :P )

Conjecture #4: Temp directory is full and that causes quite heavy YT tabs to crash (maybe, if firefox uses /tmp, idk)


Hope ur debugging gods will be with you. If you need any more info or help on this subject - do not hesitate to contact me.

- A happy user of multiple Mozilla products

Athraithe ag pavelpopov10 ar

Réiteach roghnaithe

pavelpopov10 said

Environment details:
  • /tmp directory is full!
My conjectures: Conjecture #4: Temp directory is full and that causes quite heavy YT tabs to crash (maybe, if firefox uses /tmp, idk)

I've emptied the /tmp directory and now YouTube videos are working fine. Every scenario mentioned does not end with a tab crash. It seems that conjecture #4 is right.

So it might be a temporary solution (hah, cleaning /tmp is a TeMPorary solution :P ). But it still seems to be an issue, since it's quite misleading.

From abstract side, OS should point a user that temporary directory is full, because it's operating systems' responsibility to make sure applications are supplied with available resources. But since it's not the case for most of Linux distributions (I bet Windows too, don't know for Mac and other OS), applications may develop their checks on resources they use to make user experience better. If I'm not a special type of guy who knows every bit that might go wrong, I won't be able to fix this. Better it to be saying that my /tmp is full in crash tab or at least in browser console, not just crashing with some memory allocation error (which ordinary user also won't be bothered with). Introducing a check on /tmp (where I suppose, on Linux, firefox should store it's temporary files) being full after allocation error happened (smallest possible overhead) might lead user to clean the directory, before proceeding with any type of temporary downloads. Recognizing such issues (laying out of app's scope, but blocking it's usage) and customizing crashed tab content when issue is recognized might help user to understand and solve those issues. And, by the way, give a sense of caring about users from product developers, which will hopefully make firefox even more popular and stable in it's user base.

Did some search on issues related to firefox & linux temp directory:

So it's kind of a problem to look when urgent are met. But now I'll just leave it to you, because I don't have much time right now and also not familiar with firefox development enough to make some pull request or smth. Thanks again for a good software

Read this answer in context 👍 0

All Replies (3)

more options

Do you always have multiple pages open with running videos when the crashes happen or can you play a YouTube video in a single tab ?

Any relevant messages in the Web Console or Browser Console ?

more options

cor-el said

Do you always have multiple pages open with running videos when the crashes happen or can you play a YouTube video in a single tab ? Any relevant messages in the Web Console or Browser Console ?

Running one tab in one window in safe mode is enough to make it crash using scenario #3. So I can't watch YouTube videos now - tab crashes instantly on loading a video page.

Browser Console does not change from startup to crash (screenshots attached).

Web Console has something, but after crash it's empty (screenshot attached). Btw, should I also try it with log persistence feature for Web Console?

Also, I would like to point to my crashes (from latest to first):

  • bp-09df8588-6a7d-42a6-81da-affc30200228
  • bp-2c1dbc58-e0d1-4a7d-8923-251b90200227
  • bp-ade3f1ac-dcd2-4739-887d-c60d50200228
  • bp-b7cb64e9-3423-49ef-918e-c12a80200228
  • bp-52411cbf-4573-45d5-9f16-a3f0e0200228
  • bp-b6c4df56-697e-4270-8d4e-44c190200228
  • bp-1104cb74-bd45-47b6-b68c-142bc0200228
  • bp-768b2fa8-d807-4f15-b7da-c70d70200228
  • bp-e85e4feb-d170-4288-b2ed-418e80200228
  • bp-5320775d-02a8-4d11-9672-207e20200228
  • bp-12d97348-7832-45eb-9e2b-db0d80200228
  • bp-26433d5f-6d4f-47ca-bd8e-fff620200228
  • bp-997fcb69-c817-40a4-b04e-4d1490200228
  • bp-aece09a2-7aac-4f99-a2cc-13c3d0200228
  • bp-4c876fa6-cbc5-4885-b49d-5fcdc0200228
  • bp-038d0aed-5b78-4e4b-9c7d-dc2d80200228
  • bp-49762f9d-b879-4e74-9c27-1872d0200228
  • bp-da30c838-956e-42de-a983-e88d70200228


So, it has to be this type of issue: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=__memmove_avx_unaligned_erms%20%7C%20libxul.so%400x256fc47%20%7C%20libxul.so%400x5e62264%20%7C%20libnspr4.so%400x2c665

Athraithe ag pavelpopov10 ar

more options

Réiteach Roghnaithe

pavelpopov10 said

Environment details:
  • /tmp directory is full!
My conjectures: Conjecture #4: Temp directory is full and that causes quite heavy YT tabs to crash (maybe, if firefox uses /tmp, idk)

I've emptied the /tmp directory and now YouTube videos are working fine. Every scenario mentioned does not end with a tab crash. It seems that conjecture #4 is right.

So it might be a temporary solution (hah, cleaning /tmp is a TeMPorary solution :P ). But it still seems to be an issue, since it's quite misleading.

From abstract side, OS should point a user that temporary directory is full, because it's operating systems' responsibility to make sure applications are supplied with available resources. But since it's not the case for most of Linux distributions (I bet Windows too, don't know for Mac and other OS), applications may develop their checks on resources they use to make user experience better. If I'm not a special type of guy who knows every bit that might go wrong, I won't be able to fix this. Better it to be saying that my /tmp is full in crash tab or at least in browser console, not just crashing with some memory allocation error (which ordinary user also won't be bothered with). Introducing a check on /tmp (where I suppose, on Linux, firefox should store it's temporary files) being full after allocation error happened (smallest possible overhead) might lead user to clean the directory, before proceeding with any type of temporary downloads. Recognizing such issues (laying out of app's scope, but blocking it's usage) and customizing crashed tab content when issue is recognized might help user to understand and solve those issues. And, by the way, give a sense of caring about users from product developers, which will hopefully make firefox even more popular and stable in it's user base.

Did some search on issues related to firefox & linux temp directory:

So it's kind of a problem to look when urgent are met. But now I'll just leave it to you, because I don't have much time right now and also not familiar with firefox development enough to make some pull request or smth. Thanks again for a good software

Athraithe ag pavelpopov10 ar