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

YouTube videos stop after 25 minutes XP

  • 15 replies
  • 1 has this problem
  • 89 views
  • Last reply by Hunterwh

more options

So, this began a few years ago. Apparently connected to the codec issues surrounding XP and YouTube's choice to change how their videos play back, namely to the exclusion of flash. I can get the flash player going but that lacks the nice video quality of 1080x720. So not much point there.

It happens at any quality setting. Videos stop at 25:21, or in other cases 23:18. The sound keeps playing, the video freezes. Moving the timeline will allow the video to play for another 25/23 minutes. This of course does not happen in Chrome, but the reason I don't watch videos in chrome is a different color saturation issue; the videos are washed out there and I suppose that is a separate thread on another forum.

Here's some evidence that this is widespread.

https://productforums.google.com/forum/#!topic/youtube/ViiQ_4nNXn8

I'm guessing I will get more attention complaining about Chrome's color saturation, but my preference is to resolve this issue in Firefox.

All Replies (15)

more options

I see you have installed;

Flash-HTML5 for YouTube™ 0.1.8 (jid1-o2qEVrZ4t5FJWu@jetpack)

YouTube High Definition 63.1.5 ({7b1bf0b6-a1b9-42b0-b75d-252036438bdc})

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

more options

FredMcD said

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

Playback froze at 25:21 in safe mode.

more options

Could be a memory issue.

What is the Firefox memory usage when this happens?

See also the about:memory page.

more options

cor-el said

Could be a memory issue. What is the Firefox memory usage when this happens? See also the about:memory page.

Thanks for your reply. Here is some basic information about what was going on after a video froze with no other tabs or windows open.

Process 1: 340,xxx K Process 2: 372,xxx K

Commit charge 2134/4953MB

Memory report: http://www.filedropper.com/memory-reportjson

I also thought it was a memory issue, but the fact that this happens in all resolutions at the same time confused that idea.

more options

Yep...this sucks.

more options

Hunterwh said

http://www.filedropper.com/memory-reportjson

This link is no good. It redirects back to the sites main page.

more options

It must have expired. I uploaded it again, though. Check now.

more options

It's back, but the file could not be opened by my program.

more options

Which file? The .json? What can I do about this?

more options

I could not open the .gz file because of an error.

more options

This memory file is not compressed, but is a normal .json file. I can't open the file via about:memory though because the file is not complete (only 1801 lines).

SyntaxError: JSON.parse: end of data when property name was expected at line 1802 column 3 of the JSON data

Modified by cor-el

more options

I have no idea why. I just opened it and it works normally.

So, I took the file out of the "gz" container and uploaded that. Don't ask me, that's exactly how Firefox produced the report.

http://www.filedropper.com/memory-report

See if that will work.

Modified by Hunterwh

more options

For anyone who wants to check out the file, you need to use a 'word' type program.

more options

No, you do not need a 'word' type program. Firefox has a builtin viewer fot this kind of information.

To use such a file you need to open the about:memory page in Firefox via the location/address bar and click the "Load..." button and browse to the file.

more options

So, I am gathering that

1. Mozilla is not interested in solving any longstanding issue present in its ESR.

2. Nobody knows what exactly caused this to begin, but even if they did,

3. There is no solution besides the browser handling HTML5 differently than it does, and since #1 exists, the solution is to delete Firefox and use a browser that works. Once I figure out why browsers that work have washed out color compared to Firefox. *sigh*