Hide Forgot
Description of problem: I noticed Firefox using 100% of the CPU. Investigation shows it is GStreamer that is responsible. The stack traces from pstack show that it goes into a loop in gst_bus_timed_pop_filtered. Installing debuginfo and using GDB seems to show that it goes into a loop because it has a readable file descriptor in a poll call it seems to want to use as a timeout only. I have no idea how that came to be. It keeps calling gst_poll_wait, immediately returns, then checks for messages with gst_atomic_queue_pop, gets no messages, then repeats. The whole thing appears to be started from a call to mozilla::GStreamerReader::ReadMetadata Here is the full stack trace: (gdb) bt #0 0x00007f8aa938e83e in gst_bus_timed_pop_filtered (bus=0x7f8a79471c40 [GstBus], timeout=18446744073709551615, types=2097155) at gstbus.c:558 #1 0x00007f8acb023931 in mozilla::GStreamerReader::ReadMetadata(mozilla::MediaInfo*, nsDataHashtable<nsCStringHashKey, nsCString>**) () at /usr/lib64/firefox/libxul.so #2 0x00007f8acaf66648 in mozilla::MediaDecoderReader::AsyncReadMetadata() () at /usr/lib64/firefox/libxul.so #3 0x00007f8acaf69a19 in mozilla::detail::ProxyRunnable<mozilla::MozPromise<RefPtr<mozilla::MetadataHolder>, mozilla::ReadMetadataFa ilureReason, true>, mozilla::MediaDecoderReader>::Run() () at /usr/lib64/firefox/libxul.so #4 0x00007f8aca087ef6 in mozilla::AutoTaskDispatcher::TaskGroupRunnable::Run() () at /usr/lib64/firefox/libxul.so #5 0x00007f8aca0920f9 in mozilla::TaskQueue::Runner::Run() () at /usr/lib64/firefox/libxul.so #6 0x00007f8aca08d252 in nsThreadPool::Run() () at /usr/lib64/firefox/libxul.so #7 0x00007f8aca08ed31 in nsThread::ProcessNextEvent(bool, bool*) () at /usr/lib64/firefox/libxul.so #8 0x00007f8aca0a8f4e in NS_ProcessNextEvent(nsIThread*, bool) () at /usr/lib64/firefox/libxul.so #9 0x00007f8aca292ac1 in mozilla::ipc::MessagePumpForNonMainThreads::Run(base::MessagePump::Delegate*) () at /usr/lib64/firefox/libxul.so #10 0x00007f8aca27e02a in MessageLoop::Run() () at /usr/lib64/firefox/libxul.so #11 0x00007f8aca090a33 in nsThread::ThreadFunc(void*) () at /usr/lib64/firefox/libxul.so #12 0x00007f8ac6efb7df in _pt_root (arg=0x7f8a6de2ba40) at ../../../nspr/pr/src/pthreads/ptthread.c:216 #13 0x00007f8ad980358a in start_thread (arg=0x7f8aa96ff700) at pthread_create.c:333 #14 0x00007f8ad8a8c5cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Version-Release number of selected component (if applicable): firefox-45.0.2-4.fc24.x86_64 gstreamer1-1.8.1-1.fc24.x86_64 How reproducible: About twice a day, no discernible cause. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.