Direct link to YouTube video does not work

Bug #928086 reported by ebnf
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Lightspark
Confirmed
Medium
Unassigned

Bug Description

Flash plugin 11.1 r541 /usr/lib/mozilla/plugins/liblightsparkplugin.so

Url: http://www.youtube.com/v/Gg0pMbc7Opk?version=3&hl=en_US&rel=0

Unhandled ActionScript expcetion.

Running on chromium 17.0.963.26 (Ubuntu 11.10) with gpu accelerated compositing enabled.

Tags: youtube
Revision history for this message
Alessandro Pignotti (a-pignotti) wrote :

I've tried accessing the file from this url http://www.youtube.com/watch?v=Gg0pMbc7Opk and it seems to be working. So I guess the issue is with the direct link to the video

summary: - unsupported flash file on youtube (unhandled ActionScript exception)
+ Direct link to YouTube video does not work
Changed in lightspark:
status: New → Confirmed
importance: Undecided → Medium
tags: added: youtube
Revision history for this message
Jisakiel (jisakiel) wrote :
Download full text (46.2 KiB)

When using plugin-container I get this in dmesg when trying to view https://www.youtube.com/watch?v=KXCnuArj4b8 (episodes 3 and 4 for BSG blood and chrome),

 plugin-containe[19687]: segfault at 0 ip 00007f4f92bc0207 sp 00007f4f7e47f920 error 6 in libmozalloc.so[7f4f92bbf000+2000]

and this in the gdb output:

WARNING: waitpid failed pid:20488 errno:10: file /tmp/buildd/iceweasel-16.0.2/ipc/chromium/src/base/process_util_posix.cc, line 255
[New Thread 0x7fffbf9ff700 (LWP 20523)]
[Thread 0x7fffbf9ff700 (LWP 20523) exited]
WARNING: waitpid failed pid:20488 errno:10: file /tmp/buildd/iceweasel-16.0.2/ipc/chromium/src/base/process_util_posix.cc, line 255
WARNING: Failed to deliver SIGKILL to 20488!(3).: file /tmp/buildd/iceweasel-16.0.2/ipc/chromium/src/chrome/common/process_watcher_posix_sigchld.cc, line 118

When I try to get a backtrace without plugin-container -as indicated in the wiki- it is not always reproducible, often lightspark doesn't crash but stays on a loop (when I ctrl-C it prints pthread_cond_wait@@GLIBC_2.3.2 ). After starting in safe mode I managed to recover a crash trace (I suppress the huge nunber of NOT_IMPLEMENTED getProperty messages for sake of clarity).

GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/lib/iceweasel/firefox-bin...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/lib/iceweasel/firefox-bin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5bfe700 (LWP 21959)]
[New Thread 0x7fffe4fef700 (LWP 21960)]
[New Thread 0x7fffe43ff700 (LWP 21961)]
[New Thread 0x7fffe33de700 (LWP 21962)]
[New Thread 0x7fffe27d7700 (LWP 21963)]
[New Thread 0x7fffe19ff700 (LWP 21964)]
[New Thread 0x7fffe0eff700 (LWP 21965)]
[Thread 0x7fffe43ff700 (LWP 21961) exited]
[Thread 0x7fffe4fef700 (LWP 21960) exited]
[Thread 0x7fffe0eff700 (LWP 21965) exited]
[Thread 0x7fffe19ff700 (LWP 21964) exited]
[Thread 0x7fffe27d7700 (LWP 21963) exited]
[Thread 0x7fffe5bfe700 (LWP 21959) exited]
[Thread 0x7fffe33de700 (LWP 21962) exited]
process 21954 is executing new program: /usr/lib/xulrunner-16.0/xulrunner-stub
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe5c90700 (LWP 21968)]
[New Thread 0x7fffe5081700 (LWP 21969)]
[New Thread 0x7fffe44ff700 (LWP 21970)]
[New Thread 0x7fffe34de700 (LWP 21971)]
[New Thread 0x7fffe28d7700 (LWP 21972)]
[New Thread 0x7fffe1aff700 (LWP 21973)]
[New Thread 0x7fffe0fff700 (LWP 21974)]
[New Thread 0x7fffd91ff700 (LWP 21975)]
[New Thread 0x7fffd81ff700 (LWP 21976)]
[New Thread 0x7fffd79fe700 (LWP 21977)]
[Thread 0x7fffd91ff700 (LWP 21975) exited]
[New Thread 0x7fffd91ff700 (LWP 21978)]
[N...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.