Javascript evaluation wonky

[ahungry]

Link hinting mode runs the JS and then after a few seconds (15 or so) ends up locking up the browser. Again, not sure if this is an Arch Linux thing with the version of the .so's in use, but it happens on 3 different Arch machines I use.

Even a simple command such as:

(defcommand show-alert (browser)
  (eval-in-page-js browser "alert('hi');"))

Will show the alert and then lock up the browser.

Maybe it's a stumpwm issue...guess I can try a different window manager (will give dwm a go in a moment).

[ahungry]

Definitely locks up in dwm as well (running an alert javascript call).

Maybe it's an issue with the callback given to the run-javascript? (a null-pointer instead of something to actually handle the run-javascript-finish call at some point)

[AeroNotix]

I've seen this before specifically with alerts. Not had time to track it down. Could you try strace or something like that?

[ahungry]

Here is the resultant strace:

(eval-in-page-js *default-browser* "alert(1);")
) = 1
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0xb892064} ---
mprotect(0xb892000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
rt_sigreturn()                          = 17825803
read(0, "(eval-in-page-js *default-browse"..., 4096) = 48
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0xbab89fc} ---
mprotect(0xbab8000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
rt_sigreturn()                          = 192
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x911a5f0} ---
mprotect(0x911a000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
rt_sigreturn()                          = 2048
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x90cf044} ---
mprotect(0x90cf000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
rt_sigreturn()                          = 5328
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_ACCERR, si_addr=0x90aeba4} ---
mprotect(0x90ae000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
rt_sigreturn()                          = 0
futex(0xb75eecfc, FUTEX_WAKE, 2147483647) = 0
futex(0xb75eecfc, FUTEX_WAKE, 2147483647) = 0
write(13, "\1\0\0\0\0\0\0\0", 8)        = 8
futex(0xb0ce1288, FUTEX_WAKE, 1)        = 1
write(1, "\n", 1
)                       = 1
write(1, "* ", 2* )                       = 2
poll([{fd=0, events=POLLIN|POLLPRI}], 1, 0) = 0 (Timeout)
gettimeofday({1423841897, 185359}, {0, 0}) = 0
poll([{fd=0, events=POLLIN|POLLPRI}], 1, -1) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
--- SIGWINCH {si_signo=SIGWINCH, si_code=SI_KERNEL} ---

What I did was:

strace sbcl --eval '(ql:quickload :lispkit)' --eval '(in-package :lispkit)' --eval '(main)'

Then after the browser loaded I typed in the #'eval-in-page-js function call back in the straced sbcl REPL.

The alert pops up as expected, then when clicking it it never closes (nor do any additional traces get added to the strace output).

Only way to get rid of it is with a 'pkill -9 sbcl'.

[AeroNotix]

I think it's best to implement the link highlighting in plain Javascript and see if it still happens.