Uzbl

Tasklist

FS#98 - uzbl crashes from follow_Numbers.js

Attached to Project: Uzbl
Opened by Josh Rickmar (jrick) - 2009-08-29 06:40:03 PM
Last edited by Anonymous Submitter - 2010-03-21 03:46:01 PM
Task Type Bug Report
Category uzbl-core
Status Closed
Assigned To No-one
Operating System All
Severity Low
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

% uname -a
FreeBSD FGD135 8.0-BETA3 FreeBSD 8.0-BETA3 #2: Wed Aug 26 09:31:29 EDT 2009 joshua@FGD135:/usr/obj/usr/src/sys/THINKPAD amd64
% pkg_info -IX '(webkit|libsoup)'
libsoup-2.26.3_2 A SOAP (Simple Object Access Protocol) implementation in C
webkit-gtk2-1.1.7 An opensource browser engine

When calling follow_Numbers.js (with the fl keybinding in the default config) uzbl crashes. Here's the error:

External JavaScript file ./examples/data/uzbl/scripts/follow_Numbers.js loaded
*** Signal 11

And the backtrace:

(gdb) bt
#0 0x0000000803badb9b in strlen () from /lib/libc.so.7
#1 0x00000008010336be in JSC::UString::Rep::createFromUTF8 () from /usr/local/lib/libwebkit-1.0.so.7
#2 0x0000000800f99c73 in OpaqueJSClass::OpaqueJSClass () from /usr/local/lib/libwebkit-1.0.so.7
#3 0x0000000800f9abd4 in OpaqueJSClass::create () from /usr/local/lib/libwebkit-1.0.so.7
#4 0x0000000800fa2423 in JSClassCreate () from /usr/local/lib/libwebkit-1.0.so.7
#5 0x000000000040825e in js_init () at uzbl.c:1039
#6 0x000000000040829f in eval_js (web_view=0x8075d0080,
script=0x808c82000 "/* This is the basic linkfollowing script.\n * Its pretty stable, only using numbers to navigate.\n *\n * TODO: Some pages mess around a lot with the zIndex which\n * lets some hints in the background.\n *"..., result=0x808b34500) at uzbl.c:1056
#7 0x00000000004085de in run_external_js (web_view=0x8075d0080, argv=0x808b34520, result=0x808b34500) at uzbl.c:1125
#8 0x0000000000409b0a in parse_command (cmd=0x807d79268 "script", param=0x807d617c0 "./examples/data/uzbl/scripts/follow_Numbers.js ", result=0x0) at uzbl.c:1561
#9 0x000000000040c056 in exec_paramcmd (act=0x807d55910, i=1) at uzbl.c:2341
#10 0x000000000040bf47 in run_keycmd (key_ret=0) at uzbl.c:2321
#11 0x000000000040bd94 in key_press_cb (window=0x807d34030, event=0x807d85aa0) at uzbl.c:2286
#12 0x000000080175097f in gtk_marshal_BOOLEAN__VOID () from /usr/local/lib/libgtk-x11-2.0.so.0
#13 0x00000008035b86ff in g_closure_invoke () from /usr/local/lib/libgobject-2.0.so.0
#14 0x00000008035cc187 in g_signal_parse_name () from /usr/local/lib/libgobject-2.0.so.0
#15 0x00000008035cd8e7 in g_signal_emit_valist () from /usr/local/lib/libgobject-2.0.so.0
#16 0x00000008035cdf93 in g_signal_emit () from /usr/local/lib/libgobject-2.0.so.0
#17 0x000000080184cf7e in gtk_widget_class_list_style_properties () from /usr/local/lib/libgtk-x11-2.0.so.0
#18 0x0000000801749a96 in gtk_propagate_event () from /usr/local/lib/libgtk-x11-2.0.so.0
#19 0x000000080174aa75 in gtk_main_do_event () from /usr/local/lib/libgtk-x11-2.0.so.0
#20 0x0000000801b3643c in gdk_add_client_message_filter () from /usr/local/lib/libgdk-x11-2.0.so.0
#21 0x0000000803826e52 in g_main_context_dispatch () from /usr/local/lib/libglib-2.0.so.0
#22 0x000000080382a02e in g_main_context_check () from /usr/local/lib/libglib-2.0.so.0
#23 0x000000080382a319 in g_main_loop_run () from /usr/local/lib/libglib-2.0.so.0
#24 0x000000080174ae43 in gtk_main () from /usr/local/lib/libgtk-x11-2.0.so.0
#25 0x000000000040e14a in main (argc=4, argv=0x7fffffffe758) at uzbl.c:2942

Note that I have manually defined ETIMEDOUT 60 in my uzbl.c so that it would compile on FreeBSD, so the line numbers are most likely bumped by one.

This never used to happen with older versions of uzbl, so I'm hesitant to conclude that it is a problem with webkit and amd64.
This task depends upon

Closed by  Anonymous Submitter
2010-03-21 03:46:01 PM
Reason for closing:  Works for me
Additional comments about closing:  Unable to replicate problem.
Comment by Josh Rickmar (jrick) - 2009-08-29 08:59:22 PM
I just tested with the same versions of all the above software on an i386 machine, and it works without any problems, so this seems to only affect the 64bit architecture.
Comment by Noel Maersk (veox) - 2010-01-01 11:13:00 PM
Cannot confirm on x86_64 ArchLinux.

Loading...