[indiana-discuss] evince hangs in b101 after suspend-resume

[Li Yuan]

> Jürgen Keil wrote:

>  where
> urrent thread: t at 1
> =>[1] _lwp_kill(0x1, 0x6, 0x80474dc, 0xceaf9f3a), at
> 0xceb017c5
> [2] thr_kill(0x1, 0x6, 0x80474dc, 0xceaaa02e), at
> 0xceaf9f5c
> [3] raise(0x6, 0x0, 0x804752c, 0xcea815ea), at
> 0xceaaa03a
> [4] abort(0x80c4630, 0x80dfcb0, 0xce927bb0,
>  0x393431, 0x8047564, 
> xcebc6234), at 0xcea8160a
> [5] g_assertion_message(0x0, 0xce7e536c, 0x95,
>  0xce7e5334, 
> x80dfcb0), at 0xce8b229e
> [6] g_assertion_message_expr(0x0, 0xce7e536c,
>  0x95, 0xce7e5334, 
> xce7e5338), at 0xce8b22e7
>    [7] do_unref(0x80c4630), at 0xce7c3fce
> [8] ORBit_RootObject_release(0x80c4630), at
> 0xce7c4086
> [9] CORBA_Object_release(0x80c4630, 0x804761c), at
> 0xce7c71bf
> [10] bonobo_object_release_unref(0x80c4630, 0x0),
>  at 0xcd3b7dd2
> [11] registry_filter_event(0x8076418, 0x8047670,
>  0x804788c), at 
> x80590e7
> [12] impl_registry_notify_event(0x807642c,
>  0x80cd57c, 0x804788c), at 
> x8059265
>    [13] 
> BIT_skel_small_Accessibility_EventListener_notifyEvent
> (0x807642c, 
> 0x0, 0x8047720, 0x8047740, 0x804788c, 0x805920c), at
> 0xcea0ed2e
> [14] ORBit_POAObject_invoke(0x809dfa8, 0x0,
>  0x8047720, 0x8047740, 
> x80477c8, 0x804788c), at 0xce7d3182
> [15] ORBit_OAObject_invoke(0x809dfa8, 0x0,
>  0x8047720, 0x8047740, 
> x80477c8, 0x804788c), at 0xce7d755d
> [16] ORBit_small_invoke_adaptor(0x809dfa8,
>  0x80c6228, 0xcea35790, 
> x80477c8, 0x804788c), at 0xce7c4f7f
> [17] ORBit_POAObject_handle_request(0x809dfa8,
>  0x80f116c, 0x0, 0x0, 
> x0, 0x80c6228, 0x804788c), at 0xce7d35ba
> [18]
> ORBit_POAObject_invoke_incoming_request(0x809dfa8,
>  0x80c6228, 
> x804788c), at 0xce7d39b4
> [19] ORBit_POA_handle_request(0x8072e80,
>  0x80c6228, 0x80c6240), at 
> xce7d3e36
> [20] ORBit_handle_request(0x8072e08, 0x80c6228),
>  at 0xce7d735f
> [21] giop_connection_handle_input(0x80a76e0), at
>  0xce7c1ee6
> [22] link_connection_io_handler(0x0, 0x1,
>  0x80a76e0), at 0xce7dd7ed
> [23] link_source_dispatch(0x80a7a00, 0xce7dd77c,
>  0x80a76e0), at 
> xce7df602
>    [24] g_main_dispatch(0x80722e8), at 0xce88e9dc
> [25] g_main_context_dispatch(0x80722e8), at
> 0xce88fadd
> [26] g_main_context_iterate(0x80722e8, 0x1, 0x1,
>  0x806d6a8), at 
> xce88fefa
>    [27] g_main_loop_run(0x80a49f0), at 0xce8904fc
> [28] bonobo_main(0x8047bfc, 0x8047b38, 0xcebfc7e4,
> 0xcebfc7e4, 
> 0x8047b44, 0xcebc6234), at 0xcd3b3671
>    [29] main(0x1, 0x8047b7c, 0x8047b84), at 0x80584ea
> x)
> 
> 
> i don't know what's at-spi-registryd, and i don't
> know how to restart 
> it, except logout from the current session and
> re-login?

I don't think a crash of at-spi-registryd will cause some of your applications hang. That ( some of your applications hang) normally means at-spi-registryd is hanging. Can you tell me if at-spi-registryd is still there when applications are hanging? And what are the traces of them? This would be very helpful.

Li
-- 
This message posted from opensolaris.org