Hi,

conkeror is a xulrunner based web browser which means that it's
started as "xulrunner /usr/share/conkeror/application.ini". In the
Debian package this is done inside a wrapper script at
/usr/bin/conkeror.

The wrapper script before conkeror 0.9~git080629-2 catched all
conkeror output to change a few things in xulrunner's --help message
(e.g. the binary path and some options not applying to conkeror).

This had some unexpected side effects, because it also consumed all
conkeror output during normal usage, too, and accumulated it in memory
until conkeror exits:

+ It catched all debug messages from the configuration or extensions
  and printed them only after exiting which makes debugging of
  extensions impossible. (Details in http://bugs.debian.org/498515)

+ All output of conkeror is stored in a shell variable before it is
  parsed and printed out again. This can lead to high and unwanted
  memory consumption of the wrapper script in case of long browser
  uptimes and unexpected (and unseen) output, e.g. debug output from
  some extension.

+ Four levels of processes (wrapper script and three levels of
  xulrunner processes) were running when conkeror was running.

The solution[1] is simple and much safer: The wrapper script in
0.9~git080629-2 checks if the first parameter is --help and if so
calls xulrunner as before, and otherwise (normal usage) it "exec"s
xulrunner directly which reduces not only the memory usage but also
the number of processes running during usage to what is necessary by
xulrunner (usually three). So the cases where the "cosmetic feature"
described above gets called have been reduced to the minimum.

  [1] http://noone.org/hg/conkeror/debian/rev/a8c690eb65bd

The conkeror users (including me) would be happy if the fixed version
0.9~git080629-2 is allowed to enter Debian Lenny.

                Thanks in advance, Axel
-- 
Axel Beckert - [EMAIL PROTECTED], [EMAIL PROTECTED] - http://noone.org/abe/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to