tags 514435 + confirmed
thank you
On Sat, Feb 07, 2009 at 04:25:49PM +0100, Christoph Egger wrote:
> invoking midori while it is running crahses the browser. Reproducing is
> possible by:
>
> $ midori http://www.debian.org &
> $ midori http://www.debian.org &
>
> where midori will crash on the second call.
Hmm, you're right. Doing that causes the first one to segfault and
the second to popup a dialog saying that there is a midori running,
but won't respond, along with this on stderr:
(midori:11186): Unique-DBus-WARNING **: Error while sending
message: Message did not receive a reply (timeout by message bus)
This looks like a race condition, because
midori x.org & sleep 2 && midori x.org
doesn't result in a segfault here (you might have to change 2 to a
different number if you have a faster/slower machine).
I will forward this issue upstream. As a workaround, I suggest you
introduce a small delay when firing up a bunch of tabs, e.g. instead of
for i in *.html; do
midori $i &
done
wait
do
midori & sleep 5
for i in *.html; do
midori $i
done
wait
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
