Midori 0.1.9 hangs up when user tries to start a second instance

[Angel Tsankov]

On Sun, 9 Aug 2009 11:19:06 +0200
Enrico Tröger <enrico.troeger at uvena.de> wrote:

> On Sun, 9 Aug 2009 08:55:31 +0300, Angel wrote:
> 
> Hi,
> 
> >Midori 0.1.9 hangs up when I try to start a second instance by doing
> >any of the following:
> >
> >* press Ctrl-N;
> >* click File -> New Window;
> >* execute "midori" in a terminal window.
> 
> 
> Easily reproducable.
> 
> 
> >I did not have this problem with version 0.1.7.  Then I upgraded to
> >0.1.9 by installing "over" 0.1.7.  Could this be the problem?  If not,
> 
> Unlikely.
> 
> 
> >how can I diagnose the problem?
> 
> E.g. run Midori in gdb, trigger the "hang" and then interrupt the
> execution with Ctrl-C and type "bt" in gdb.
> 
Well, I'm not very familiar with GDB yet, but following your instuctions (except that I attached to a running instance of Midori instead of running Midori from within gdb) I got this:

#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb69ceccc in poll () from /lib/libc.so.6
#2  0xb7eb944b in IA__g_poll (fds=0x869b988, nfds=4, timeout=120)
    at gpoll.c:127
#3  0xb7eac73b in g_main_context_iterate (context=0x81c9aa0, 
    block=<value optimized out>, dispatch=1, self=0x81c8e60) at gmain.c:2758
#4  0xb7eacd8f in IA__g_main_loop_run (loop=0x81ee9e0) at gmain.c:2653
#5  0xb7b5f1a9 in IA__gtk_main () at gtkmain.c:1205
#6  0x0807ea24 in main (argc=1, argv=0xbfc83fc4) at ../midori/main.c:1937