I have now tried webkit-image-qt version and did not noticed any problem.

I have tried more web sites with webkit-image-gtk.

$ webkit-image-gtk http://slashdot.com >foo.png; file foo.png
foo.png: data
$ webkit-image-gtk http://github.com >foo.png; file foo.png
foo.png: data

$ webkit-image-gtk http://www.debian.com >foo.png; file foo.png
foo.png: PNG image data, 611 x 9207, 8-bit/color RGB, non-interlaced
$ webkit-image-gtk http://www.google.com >foo.png; file foo.png
foo.png: PNG image data, 938 x 469, 8-bit/color RGB, non-interlaced

I test some very simple HTML/XHTML pages and the problems appear to be javascript related.

Debugging info is included if   
<script type="text/javascript" src="mootools-1.2.4-core-nc.js"></script>
added between <head></head>.

Debugging info is not included if no javascript is present or with simple javascript between <script></script> tags.

Would you like to see these sample pages? Though, I think this debugging info is NSPlugin related and may be printed in other situations as well. But it should go to stderr not to stdout.

Next I have encountered problems with http://www.hanskalabs.net with both gtk and qt webkit version:

$ webkit-image-gtk http://www.hanskalabs.net > foo.png; file foo.png
The program 'webkit-image-gtk' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 216 error_code 11 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
foo.png: empty

$webkit-image-qt http://www.hanskalabs.net > foo.png; file foo.png
I get 100% CPU usage and never returns to console prompt. I have killed it after several minutes, output file is empty.


Pkg-grass-devel mailing list

Reply via email to