HTML5 Video Test Crashes Browser (SOLVED)
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
HTML5 Video Test Crashes Browser (SOLVED)
This site crashes my Pale Moon when it didn't before, I'm not sure what changed? opening it in a terminal shows zero error's.
http://www.quirksmode.org/html5/tests/video.html
Can someone test this.
It might be something I changed in "about:config"
Thanks
Moderator Note: Changed thread title to not be exceedingly vague
http://www.quirksmode.org/html5/tests/video.html
Can someone test this.
It might be something I changed in "about:config"
Thanks
Moderator Note: Changed thread title to not be exceedingly vague
Last edited by troypulk on 2015-11-04, 14:44, edited 1 time in total.
Re: HTML5 Video Test Crashes Browser
Just crashes as it finishes loading?
I went to the link, and started playing all 3 Buck Bunny videos.
No crashes to be had.
I went to the link, and started playing all 3 Buck Bunny videos.
No crashes to be had.
Re: HTML5 Video Test Crashes Browser
Yes, as soon as it finished loading.megaman wrote:Just crashes as it finishes loading?
I went to the link, and started playing all 3 Buck Bunny videos.
No crashes to be had.
I'll try a new profile and see what happens.
Re: HTML5 Video Test Crashes Browser
I tried it on 25.7.3 and 26 Beta 3, they are both 64, but X32 and X64 shouldn't matter.
Edit: I have to take it back, I'm running Windows. Yikes, my mistake. You have to wait for someone else on Linux to report.
Edit: I have to take it back, I'm running Windows. Yikes, my mistake. You have to wait for someone else on Linux to report.
Re: HTML5 Video Test Crashes Browser
That test site opens fine for me once I allow it thru NoScript. Tested on two physical machines running LM 17.2 MATE 64-bit w/ Pale Moon 25.7.3 (x64). And. The three test vids play to end with no problems.troypulk wrote:This site crashes my Pale Moon when it didn't before, I'm not sure what changed? opening it in a terminal shows zero error's.
http://www.quirksmode.org/html5/tests/video.html
Can someone test this.
...
.
-
- Contributing developer
- Posts: 1742
- Joined: 2013-05-20, 18:19
- Location: Somewhere in Sector 001
Re: HTML5 Video Test Crashes Browser
No crashes here either. Maybe try a new profile?
Re: HTML5 Video Test Crashes Browser
I tried a new profile and that fixed it.
I'll have to migrate everything over because I'm not going to try and weed through all the changes made to try and find out what happened.
Thanks for the help.
I'll have to migrate everything over because I'm not going to try and weed through all the changes made to try and find out what happened.
Thanks for the help.
Re: HTML5 Video Test Crashes Browser (SOLVED)
UPDATE:
I finally stumbled on to why PM was crashing when trying this web page.
Because I'm using SolydX Testing which is Debian and they do not use ffmpeg I was playing around again to see if anything has changed because they said ffmpeg was coming back but what is really needed is gstreamer0.10-ffmpeg which they don't support.
Anyway, in about:config I enabled "media.gstreamer.enabled" to True, doing this crashed PM and false fixed it.
I finally stumbled on to why PM was crashing when trying this web page.
Because I'm using SolydX Testing which is Debian and they do not use ffmpeg I was playing around again to see if anything has changed because they said ffmpeg was coming back but what is really needed is gstreamer0.10-ffmpeg which they don't support.
Anyway, in about:config I enabled "media.gstreamer.enabled" to True, doing this crashed PM and false fixed it.