| Summary: | www-client/firefox-37.0.1: crash when playing html5 media | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dimitrios Semitsoglou-Tsiapos <kmhzsem> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | aoaaxy+gentoobugzilla, zazdxscf+bugs.gentoo.org |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
last half second of strace asound.conf |
||
|
Description
Dimitrios Semitsoglou-Tsiapos
2015-04-18 10:00:37 UTC
Does this occur with both firefox and firefox-bin ? Could you attach your emerge --info so I can see what other flags you may have set on relevant packages? Created attachment 401706 [details]
emerge --info
I have moderately populated package.use and package.accept_keywords files as well, but nothing that i could identify as related. Let me know if you think they may be proven helpful. (In reply to Ian Stakenvicius from comment #1) > Does this occur with both firefox and firefox-bin ? Correct. Also, downgrading firefox to version 36 does not solve the issue. Created attachment 401752 [details]
last half second of strace
I found out that the crash only occurs when using my USB soundcard (1852:7022), instead of the on-board one. Note the SNDRV_* references in the strace. However, no other software that I use crashes because of it. I've come to the conclusion that this is not related to the sound card specifically, but to the fact that I was passing audio through mbeq_1197. The issue may still lie in firefox code, since I have not had any other application crash because of this. Created attachment 402052 [details]
asound.conf
Could be related to https://bugs.gentoo.org/show_bug.cgi?id=549612 but info comment2 here says: sys-devel/gcc: 4.8.4 It's been a very long time since this last happened. It's difficult to tell what the problem was at this point. Perhaps it's time to close this. Agreed, if the issue can't be reproduced on the latest firefox (45.x or 51+) then its time to close. Even then, the bug is likely different now than it was here. |