Re: Ubuntu 12.04: Serious problems with operapluginwrapper-native

Agon Buchholz <[email protected]> writes:

> Eirik Byrkjeflot Anonsen wrote:
>
>> If the plug-in itself freezes or crashes, the pluginwrapper will freeze
>> or crash.  But opera will keep running.  Unfortunately, if the
>> pluginwrapper freezes, opera will freeze until it decides that the
>> pluginwrapper is unlikely to come back to life.  This is because of the
>> way plug-ins are designed.  Once opera decides not to wait for the
>> plug-in any more, it can no longer let the plug-in run, so it kills it.
>
> Basically there's nothing wrong with this design; my point was simply,
> that something is not working as it should; this "something" could be
> either in Opera or the components it utilizes (which would be
> desastrous), *or* in my system (which would be my individual
> problem). If Opera's bug tracker isn't flooded with complaints, it's
> probably more or less a problem of a limited number of individual
> systems (probably 64bit, maybe Nvidia GPU).
>
> However, the issue is *not* that specific web pages make a (Flash)
> plugin crash; this behaviour is systematic and occurs on *every* page
> load where Flash or other multmedial content is embedded. If a website
> has, for example, an image slideshow on top of all pages, the browser
> will freeze on every page load, icluding "back" navigation; this
> includes also wide areas of Amazon's shop, where MP3 tracklistings
> also trigger those freezes.
>
> And, again, this is not a problem of the web content itself; browsing
> the same pages with Chromium is smooth, and Opera has become usable
> again for me - after disabling those plugins in Opera.
>
> Greetings, -A.

Clearly we're doing something that makes flash freeze (or possibly,
makes our own code freeze).  I haven't heard that we have such a problem
in general, and I think I probably would have heard about it.

I find it isn't entirely unusual that such problems is limited to only
some systems.  And it is usually hard to track down what the problem is.

I think what really complicates things is that there are two
applications (the browser and the plug-in), both of which can be rather
complex and has varying sets of bugs.  When these two pieces becomes
joined together as a single application, the set of little things that
can break becomes much greater than the sum of the parts.

(Also, having to deal with the interface makes both parts quite a bit
more complex than they would otherwise have to be.)

eirik
--
Opera-Linux: https://list.opera.com/mailman/listinfo/opera-linux
More lists: https://list.opera.com/mailman/listinfo/
Unsubscribe: mailto:[email protected]?subject=unsubscribe