[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnash-commit] [bug #37077] segfault in libgnashplugin.so[a85b5000+47000
[Gnash-commit] [bug #37077] segfault in libgnashplugin.so[a85b5000+47000]
Sat, 27 Oct 2012 11:10:14 +0000
Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Follow-up Comment #4, bug #37077 (project gnash):
> 1. What version of Midori do you run? I am using a self-build from latest
> 2. Did you open like 20 tabs from Phoronix. That triggers this usually in my
Yes, lots of Flash activity seems to make it more likely to happen.
> 4. Any idea what I can do to provide more information to analyze the stack
Not really. When faced with memory corruption problems I normally use Valgrind
to find where the problem starts, but running Midori in Valgrind leads to an
early segfault on my system before we get to any Flash content.
> 5. Should not the library/plugin return an error instead of segfaulting?
Absolutely. It is possible though that the segfault is ultimately caused by
Midori due to a bug in their NPAPI implementation, though.
Reply to this item at:
Message sent via/by Savannah