← Back to team overview

qpdfview team mailing list archive

Re: Testing browser plugin and bug about memory comsumption

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On 19.07.2012 05:47, Sandor Ortegon wrote:
> 
> Hello,
> 
> Just in order to make a correction in this message, after
> restarting the computer qpdfview PDF plugin was recognized in
> Mozilla Firefox. Still, it seems that it was more complicated than
> it should to make it work if Mozplugger was installed before.

Obviously not optimal, but Firefox seems to be known for having
problem updating its plug-in registry. Maybe
https://support.mozilla.org/en-US/kb/troubleshoot-issues-with-plugins-fix-problems#w_re-initializing-the-plugins-database
is helpful to make future testing of this easier. (I.e. just delete
"pluginreg.dat" in your Firefox profile.)

> Have a good day.
> 
> 
> On Wed, Jul 18, 2012 at 7:09 PM, Sandor Ortegon
> <sandortegon@xxxxxxxxxxx <mailto:sandortegon@xxxxxxxxxxx>> wrote:
> 
> 
> 
> Hello,
> 
> First, I can confirm there is a noticeable difference in the
> latest trunk, after I reported a bug about RAM memory. Of course,
> this could be improved to patch any memory leaks and make qpdfview
> as lightweight as possible.

Well, it was not really a memory leak. (The memory got released when
the tab was closed.) It was really really bad caching of rendering
results. ;-) From this, I also infer that the bug status "Fix
committed" is confirmed by you. And we will of course try to reduce
memory consumption as much as possible. Thanks for being so thorough
in testing, otherwise this might have slipped by.

By the way, if you completely disable caching the program hovers
around 50-60 MB for me (with a single tab). With short-lived increases
when rendering is done and the results are displayed. So this is
probably a minimum one could hope to achieve.

The only more or less simple way to reduce memory consumption I
currently see is to tile rendering instead of rendering whole pages at
once. But this might also reduce performance, I don't know until I
testing something which probably won't happen for some time.

But for now, fixing bugs in version 0.3.2 and then having lunch after
release is my priority. (Which sadly enough applies to the plug-in and
its interface as well.)

Best regards, Adam.

> Second, I considered this a good time to test the the browser PDF 
> plugin I suggested, using the latest trunk. Basically used the 
> following command to create a copy of the plugin in the standard 
> place for plugins (that is recognized by Opera, Mozilla and
> Chrome):
> 
> bzr branch lp:qpdfview trunk && bzr branch 
> lp:~adamreichold/qpdfview/plugin plugin && cd plugin && qmake && 
> make && sudo cp libqpdfview-plugin.so /usr/lib/mozilla/plugins/
> 
> (For other users: Of course, you can apply it in your directory of 
> choice and then you can delete the directories that are created if 
> you wish)
> 
> Well, the following are the conclusion of my testing so far:
> 
> 1) In Opera and Chrome, the plugin is recognized and if enabled 
> (actually it is enabled by default), it works correctly. Of
> course, it is quite basic at the moment; basically it looks like
> chrome PDF plugin (the original scale by default), but without the
> controls. I wonder, based on my comments about making qdfview work
> with mozplugger, if something else can be done at the moment; at
> least creating some controls (the way chrome PDF plugin does is
> wonderful, maybe something like that can be replicated or even
> improved allowing more ways to control the PDF, given the quality
> of qpdfview).
> 
> 2) In Mozilla, I had some problems to make the plugin work. It 
> didn't appear in the preferences menu (it appeared in the 
> about:plugins, but not in the preferences to choose if enable it
> or disable it). And it is always in second place of priorities
> behind mozplugger. So I had to disable mozplugger, remove some
> files to recognize mimetypes in my profile and start again. Once I
> was able to make it work, it worked like in the other browsers.
> 
> Kudos to Adam for this great program, and hopefully the browser 
> plugin idea can be realized in future releases, it would be very 
> good publicity and also a great addition. And I will continue 
> testing the best PDF viewer in Linux ... Thanks for your attention,
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQB6p8AAoJEPSSjE3STU34j8gH/36PXfhEEBDak4FLym5dkigf
qpCQm6vkZrRViRXPRksPZd8tKmzST84XKoNWBMGrwxlPuhH6HQb873zJU+th6qXP
GekmmaBpJFxLVDINo6sI2BztbQykAP/5buquOZDEhyqv9B0kwL14sl2TGMy4REJf
fbXFMgYi31rBFkLi5eJzxHEr3eTkfNHqNN6i1TeCD17ajwInnuRre8h0UK8EX6xY
hveTgyuMJjNZGQ1lG2HDtTW+Wuf0oBlbPDXAA4x0Den2OzaizXw0BjdcfojVg6p5
dPNr5V0BLjPZln4l5c/K3Lz7BwwI+RkqbNSid4CVANUvnCWzRt3ou5cpiovVsew=
=XXeR
-----END PGP SIGNATURE-----


References