[Opera-Linux] Opera needs many re-loading before displaying pdf files.

[weesan at employees.org]

Hi,

I just cooked up a page on how to put Linux Acrobat Reader 7.0.X on diet, ie. 
uses less memory and loads much faster at start-up by turning off some or all 
plugins.  That might help with this problem.

 	http://www.cs.ucr.edu/~weesan/acroread_on_diet.html

Thanks,
-WeeSan

On Fri, 4 May 2007, Claudio Santambrogio wrote:

> On Fri, 04 May 2007 10:37:30 +0200, Keith Bates <keith at new-life.org.au> 
> wrote:
>
>> On Fri, 04 May 2007 13:17:46 +0530
>> "Parameshwara Bhat" <peebhat at gmail.com> wrote:
>> 
>>> Hello List,
>>> 
>>> The current version of Opera behaves strangely with respect to
>>> display of pdf files.The plugin is available and is correctly listed
>>> by opera.You click on a pdf link,it downloads and quietly sits with a
>>> blank.You reload 4-5 times again and again,pdf file is loaded and
>>> displayed.If the first document is displayed,in that session, no
>>> problem there displaying pdf files again .In the next session,problem
>>> repeats.
>>> 
>>> As I have faced the problem both at home and office on different
>>> computers and different OSes ( All Linux,but
>>> Fedora/Ubuntu/OpenSUSE ),I think the problem lies in Opera. In the
>>> same context,firefox has no problem at all and that excludes Acrobat
>>> Reader Plugin from sources of problem.
>>> 
>>> I have observed this problem for quite some time now, perhaps this
>>> has started with Opera 9.x series, but I cannot exactly tell.
>>> 
>>> Thanks,
>>> 
>>> Parameshwara Bhat
>>> 
>> 
>> I can confirm that.
>> 
>> I was thinking that it could not be right as I don't have problems
>> opening pdf files- but that's because I open them with the default
>> application for my system- gpdf. When I try to use the plug-in it
>> doesn't work. Using Debian- testing and Opera 9.20
>
> The problem is that Opera kills plug-ins that do not respond for 20 seconds, 
> as a prevention not to make them a resource hog to the system. Acroread 
> plugin takes ages to start up the first time(s), and Opera doesn't realize 
> the plugin is still starting - when it decides to kill it. There should be 
> code to allow for a longer timeout before killing it when starting the 
> plugin, but it is somehow broken at the moment.
>
> /c
>
>
> -- 
> claudio santambrogio
> qa desktop test manager - *nix
> opera software asa
> --
> Opera-Linux: http://list.opera.com/mailman/listinfo/opera-linux
> More lists: http://list.opera.com/mailman/listinfo/
> Unsubscribe: mailto:opera-linux-request at opera.com?subject=unsubscribe