Closed Bug 496034 Opened 17 years ago Closed 17 years ago

crash on closing tab with html5 video

Categories

(Core :: Audio/Video, defect)

Product:
Core
Component:
Audio/Video
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: mozilla, Unassigned)

References

(
URL
)

Details

(Keywords: crash)

Attachments

(2 files)

Console log
20.85 KB, text/plain
Details
Stack
1.95 KB, text/plain
Details
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090601 Ubuntu/9.04 (jaunty) Minefield/3.6a1pre Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090601 Ubuntu/9.04 (jaunty) Minefield/3.6a1pre If i visit dailymotions html5 demo and close the tab showing the site the browser crashes. No crash reporter starts. Resuming crashes the browser again. Reproducible: Always Steps to Reproduce: 1. Open http://www.dailymotion.com/openvideodemo 2. Close the tab showing dailymotions html5 demo Actual Results: The browser crashes Expected Results: Closed the tab
Version: unspecified → Trunk
Could not reproduce in 32-bit version, same build, same OS (32-bit version) Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090602 Minefield/3.6a1pre Can you post the link to the crash? It's available when you go to the URL, about:crahes
I'm using Firefox from the ubuntu repository. It seems it does not include the about:crashes info. Should this be posted in launchpad instead?
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1pre) Gecko/20090602 Shiretoko/3.5pre Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090602 Minefield/3.6a1pre Both versions above work for me using the test video. I'm using Ubuntu 9.04 64-bit native (NOT A VM)
As reporter said, no crash reporter starts. So it will be a bit tricky. Reporter, does Firefox also crash when you run the video in a plain window? The video url is: http://www.dailymotion.com/cdn/OGG-320x240/video/x99gp5_transformers640_creation?key=1ad5daa3da8e487640d619c80837fe4213c67f0
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1pre) Gecko/20090602 Shiretoko/3.5pre Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090602 Minefield/3.6a1pre Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090601 Ubuntu/9.04 (jaunty) Minefield/3.6a1pre All three above builds on Ubuntu 9.04 64-bit native using the following URL work without problems: http://www.dailymotion.com/openvideoframe I can play, use controls, and close tab, all without crashing.
They create the video based on a uniqe key. So please check the source of the page and find the referenced video file. Open that on in a new tab and close it afterward. Does it crash too? Further please disable Javascript and re-run the test with the mentioned page from your comment 0.
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1pre) Gecko/20090602 Shiretoko/3.5pre Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090602 Minefield/3.6a1pre Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090601 Ubuntu/9.04 (jaunty) Minefield/3.6a1pre 1. Video from Source -> Works on all three builds [NO CRASH] 2. Video from Comment 0 -> Works on all three builds [NO CRASH]
Sorry, #2 should be: 2. Video from Comment 0 with JS disabled -> Works on all three builds [NO CRASH]
Henrik Skupin: The link you provided doesn't seem to work here. Aaron Train: Using your link the browser also crashes. I tested a bit more and i found that firefox also crashes if i go to a bookmark or type in another url (and hit enter). Also it only happens if i wait until the video is playing. Changing while it is buffering does not crash the browser. Showing the video directly from the link found in the source code also crashes it. With javascript turned off there's no problem changing away from the video.
TToft> I assume you have already tried running on a clean profile?
Reporter, given by the user agent string you are using a build from the ubuntu repository. Could you please try to run these steps with a nightly build of Minefield from ftp.mozilla.org? It could make the crash reporter working. http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2009/06/2009-06-02-04-mozilla-central/ Does it also happen with Shiretoko for you?
#11 yes i tried with a clean profile. I'll try a nightly build from the ftp.
Okay, with the build from ftp it does not happen.
(In reply to comment #14) > Okay, with the build from ftp it does not happen. Can you verify against latest-1.9.1?
I tried with the latest firefox 3.5 and it did crash in my first try. I can't seem to reproduce it though. There is a crash report here: http://crash-stats.mozilla.com/report/index/936c1f19-6484-4ede-a139-e3e1b2090602
That's a crash from Firefox 3.5b4. Did you try it with this build (1.9.1) branch? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
Looks like this is a crash in the http://packages.ubuntu.com/en/hardy/libpulse-browse0 package. You should probably report this to launchpad. Can you remove this package temporarily for tests?
Latest 1.9.1 works fine. I can't reproduce the crash in 3.5b4.
libpulse from hardy yet the reporter is using Jaunty. Maybe updating the libpulse would help the issue?
It is the newest in the Ubuntu repository. http://packages.ubuntu.com/en/jaunty/libpulse-browse0
(In reply to comment #21) > It is the newest in the Ubuntu repository. > > http://packages.ubuntu.com/en/jaunty/libpulse-browse0 Version numbers are different though: Hardy: 0.9.10 Jaunty: 0.9.14 You might want to verify that you have the most up to date version of libpulse running locally.
According to Synaptic i have 0.9.14.
(In reply to comment #23) > According to Synaptic i have 0.9.14. Then, as comment 18 says, I suggest filing a bug against libpulse in launchpad.
(In reply to comment #20) > libpulse from hardy yet the reporter is using Jaunty. Maybe updating the > libpulse would help the issue? Sorry, wrong link. Haven't taken a look at the internal version name.
I'll do that. Thank you. Do i report this bug in launchpad too as it only happens in the ubuntu version of minefield?
(In reply to comment #26) > I'll do that. Thank you. > > Do i report this bug in launchpad too as it only happens in the ubuntu version > of minefield? I would definitely link them back to this bug. Otherwise, they will be working from scratch on this issue. (Why repeat the history of this bug if you don't have to)
Component: General → Video/Audio
Product: Firefox → Core
QA Contact: general → video.audio
Due to this crash doesn't happen with any of our own recent builds I'll resolve this bug as invalid on our side. The Ubuntu team will probably get a full stack even with the library included to check for the real cause. Feel free to reopen when I was wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
I'm back.. I'm now running the build i got from FTP (and just updated it via automatic update) and now the problem is back. Only now i have removed the Ubuntu version and this is what I'm using now: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2a1pre) Gecko/20090603 Minefield/3.6a1pre Could something be left from the Ubuntu version causing this even though i use a clean profile?
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
reporter: we still need a crash report, like the one you gave us in comment 16.
It does not generate a report. The crash reporter doesn't show. It just closes.
about:crashes says The URL is not valid and cannot be loaded. Did i miss something when trying to start from scratch with the nightly build?
I believe you are using an optimized build but you could run Firefox with gdb and check if gdb is able to fetch the crash. (In reply to comment #32) > about:crashes says The URL is not valid and cannot be loaded. Did i miss > something when trying to start from scratch with the nightly build? Something seems to be really broken. Right now I don't have an idea what's going on here. What about the other about: pages like about:config, about:buildconfig. Do such pages work?
if about:crashes doesn't work, then it isn't one of our builds. if you're dying in pulse, you need to contact either pulse or pulse's distributor. if you aren't actually crashing, you should run firefox from a console to see the output. but please, if you want to report a problem here, either build your own binary --enable-debugger-info-modules --disable-strip and follow the hints in https://developer.mozilla.org/En/Debugging_Mozilla_on_Linux_FAQ or use our binaries and then about:crashes will work.
#33: Yes they work. about:buildconfig says: "Source Built from http://hg.mozilla.org/mozilla-central/rev/525a79aa1d44 etc." #34: As you can read in comment #29 I'm using the build i was told to get in comment #12: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2009/06/2009-06-02-04-mozilla-central/ If this is not the official binaries then i don't know what you mean I'm supposed to use. Sorry for any inconvenience.
If i run it from a console, when it crashes, it prints: "Illegal instruction"
We don't have Breakpad support for x86-64, so no 64-bit linux builds have crash reporting. They won't catch crashes, and they won't have about:crashes available. You'll have to get a debug build, or debug symbols for your build in order to get a stack.
Is there somewhere i can get a debug build for further testing? Unfortunately I do not think I would be able to compile it myself without a rather thorough guide.
Building is totally simple. You only have to do some steps. See the following link for the pre-requisites: https://developer.mozilla.org/en/Linux_Build_Prerequisites After that do the following: 1. Clone the mozilla-central repo: "hg clone http://hg.mozilla.org/mozilla-central minefield" 2. "cd minefield" 3. "vi .mozconfig" And place the following content into .mozconfig: mk_add_options MOZ_CO_PROJECT=browser ac_add_options --enable-application=browser mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../debug ac_add_options --disable-optimize ac_add_options --enable-debug ac_add_options --enable-tests mk_add_options RUN_AUTOCONF_LOCALLY=1 mk_add_options AUTOCONF=/usr/bin/autoconf2.13 CC=/usr/bin/gcc CXX=/usr/bin/g++ # for parity with cvs and buildbot configs, we're not currently generating # symbols on this platform #export CFLAGS="-gstabs+" #export CXXFLAGS="-gstabs+" 4. Start the build process with "make -f client.mk" 5. Start MinefieldDebug: "../debug/dist/bin/firefox"
There are also simple step-by-step instructions at https://developer.mozilla.org/En/Simple_build, hopefully they work for 64-bit builds too. :)
Okay I followed the instructions and this build crashes too. I'm not sure what information I'm supposed to collect since there's no breakpad but I have attached what was printed in the console. Let me know if you want me to do something else.
Attached file Console log —
Please start Firefox that way: "/home/dustie/debug/dist/bin/firefox -g". It will automatically attach the debugger. After a couple seconds you will see the prompt from gdb. Just enter "r" and press enter. Firefox should start and when the crash happens you see the prompt of gdb again. Enter "bt" and give us all the output. Next steps will follow.
bash: bt: command not found
I'm in over my head here. I get a SEGFAULT in DDD when trying to figure this out via the linked guide. I think I'll leave debugging to people who understand what they are doing. Fell free to close this unless you got some easier way to find out what's wrong.
Please don't use ddd. gdb is fully sufficient. I'll send you some instructions via email. Let us continue here when we have figured out the debugging problems.
Attached file Stack —
As talked with TToft via IRC this really looks like a libpulse bug. It should be filed in launchpad. Marking as invalid.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: