Video.js: Failed to execute 'replaceChild' on 'Node': The node to be replaced is not a child of this node.

[travisbader]

Description

Briefly describe the issue.
Include a reduced test case, we have a starter template on JSBin you can use.

Steps to reproduce

Explain in detail the exact steps necessary to reproduce the issue.

1. I am not sure the exact steps to repro, but I theorize this crash is surrounding disposing of the video player and the updating of the remaining time

Results

Expected

Don't throw errors

Actual

The error is thrown

Error output

Additional Information

Please include any additional information necessary here. Including the following:

versions

videojs

7.7.6

browsers

Chrome for sure, haven't seen in other browsers yet

OSes

unknown

plugins

"@silvermine/videojs-airplay": "^1.0.0",
"@silvermine/videojs-chromecast": "^1.2.1",
"videojs-contrib-quality-levels": "^2.0.9",
"videojs-hotkeys": "^0.2.25",
"videojs-vtt.js": "^0.12.6"

[welcome[bot]]

👋 Thanks for opening your first issue here! 👋

If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[travisbader]

PR submitted

[gkatsev]

Like https://github.com/videojs/video.js/issues/5706, it would be good to figure out the root cause. Often times these issues and fixes with null checks just hide a worse problem that would be better if it were fixed.

[dansgithub]

Hey everyone, is there any update on this issue? Currently we have many error logs coming from this one and there seems to be no fix!

[JustinMGaiam]

This is also the highest error rate in our NewRelic Browser monitoring (we use VideoJS through the Brightcove player specifically via the npm brightcove/react-player-loader npm package) so anything that moves towards fixing this error would be very helpful.

[travisbader]

Now three users all reporting high quantity of errors. Im ok if you don't merge my naive fix for reasons of wanting to find the root cause, but can you please find the root cause! We still have an enormous number of errors emitting out of this and would appreciate any attention you can give it

[gkatsev]

Are all of you using newrlic for error tracking?

Also, can you give me some more info about your environments? I've tried to reproduce it a bit but I've been unable to.

[travisbader]

We are using raygun as our error reporting tool. We use video.js in a react app similar to a netflix like product. I suspect that this issue comes up when the video.js player is disposed when swapping to a new video

[gkatsev]

Wonder if it's a react? Have a sample of how the player is disposed and a new source used?

[Darkein]

Hi there, we have exactly the same problem.

Our app use Angular 8, not react. We can't reproduce it, but some of our users have it (about 1%) whatever the browser or the OS.
We contacted a user who has exactly the same computer than me (macbook pro 13"2017). He has the problem everytime, with the latest version of Chrome.

Could we just suppress the error while we try to find why it crash? Because we can't catch the error ourselves, it crash the entire application. And like @JustinMGaiam we have homemade log/error tracking, filled by this error.

[sebastien-f]

We also have the issue on an angular 8+ application. We upgraded to the latest version of videojs and pushed to production on November 9. We got so many errors that we exceeded our Sentry quota due to it. You can see the grap of errors from the month :

Here it is compared to other issues so you can have an idea of what volume difference we are talking.

We are investigating the issue on our side (as we saw that our implementation was different than the one in the documentation) to see if can come from that.

[kontrollanten]

We're facing this as well, using PeerTube 2.4.0 (Angular 11). Our sentry quota was eaten up as well. PeerTube doesn't provide source maps so I can't dig deeper into where the actual source is (I just assume it is video.js since other people are facing the same issue here).

@sebastien-f @travisbader @JustinMGaiam @Darkein Do you have any stack traces from NewRelic/Sentry that you can provide?

PR created where the proposed change for #6700 is fixed: #6977

[sebastien-f]

@kontrollanten Sorry, can't provide any it's a project under a very strict NDA.
Also for what it's worth, we redid the integration to follow more closely one of the documentation and don't have any error or warning now. We will be reenabling Sentry at the start of next year after updating it again to be sure to include @gkatsev fix (thank you for that btw !)