FWIW, I can't reproduce on my Debian Unstable x86-64. Also, to run GDM more directly, you can do `gdb -ex run --args geany -v`.
Anyway… looks very odd. Could you try and run under Valgrind? it looks like a memory corruption, so maybe Valgrind could help. It's fairly slow to run anything under Valgrind, but use `G_DEBUG="gc-friendly:resident-modules" G_SLICE="always-malloc" valgrind geany -v`. Also, you might want to install Geany's, Geany-Plugins' and WebKitGTK's (beware, there are many WebKitGTKs, it's *libwebkitgtk-1.0-0-dbg*) debugging symbols (-dbg packages) to see more meaningful traces with GDB and Valgrind. This said, I doubt it's actually WebHelper's fault. I could be wrong, but I doubt the plugin does anything odd enough to trigger something like that, and would rather imagine it's an obscure bug in libwebkitgtk going unnoticed because it's with the inspector. If I get a chance I'll try and setup a 32 bits Jessie VM, but it might not be tonight. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/412#issuecomment-197486839
