Hi, On Thu, Dec 14, 2017 at 4:22 PM Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > #9 xkl_process_error at xklavier_evt.c:541 > #14 XPending at Pending.c:55 > #15 gdk_check_xpending at gdkeventsource.c:269 > #16 gdk_event_source_check at gdkeventsource.c:306 > > (xklavier is to do with keyboards, IIRC). But in the first few "dupes", xklavier does deal with keyboards, but this crash may be completely unrelated to xklavier unfortunately. Because of the asynchronous nature of X errors, the error could be for some completely unrelated reason, and xklavier's error handler was just the first to catch it. > #8 x_io_error at wayland/meta-xwayland.c:418 > #10 _XReadEvents at xcb_io.c:400 > #11 XIfEvent at IfEvent.c:68 > #12 meta_display_get_current_time_roundtrip at core/display.c:1332 > #13 meta_wayland_surface_destroy_window at wayland/meta-wayland- > surface.c:430 > > #8 x_io_error at wayland/meta-xwayland.c:418 > #11 XPending at Pending.c:55 > #12 gdk_check_xpending at gdkeventsource.c:269 > #13 gdk_event_source_prepare at gdkeventsource.c:287 > #14 g_main_context_prepare at gmain.c:3450 These two mean Xwayland (or Xorg) tanked. x_io_error means disconnected from X server. > #8 object_instance_finalize at gi/object.cpp:1490 > #9 js::Class::doFinalize at /usr/src/debug/mozjs52-52.4.0- > 1.fc27.x86_64/dist/include/js/Class.h:816 > #10 JSObject::finalize at /usr/src/debug/mozjs52-52.4.0- > 1.fc27.x86_64/jsobjinlines.h:87 > #11 js::gc::Arena::finalize<JSObject> at /usr/src/debug/mozjs52- > 52.4.0-1.fc27.x86_64/jsgc.cpp:457 > #12 FinalizeTypedArenas<JSObject>(js::FreeOp *, js::gc::Arena **, > js::gc::SortedArenaList &, enum class AllocKind, SliceBudget &, > js::gc::ArenaLists::KeepArenasEnum) at /usr/src/debug/mozjs52-52.4.0- > 1.fc27.x86_64/jsgc.cpp:515 > > #8 g_malloc0 at gmem.c:129 > #9 blur_pixels at ../src/st/st-private.c:280 > #10 _st_create_shadow_pipeline at ../src/st/st-private.c:372 > #11 _st_create_shadow_pipeline_from_actor at ../src/st/st- > private.c:434 > #12 st_icon_update_shadow_pipeline at ../src/st/st-icon.c:278 These two could both be heap corruption of some sort. valgrind might help with them. Though the first one, might also be some sort of gjs bug. > #8 x_io_error at wayland/meta-xwayland.c:418 > #11 XPending at Pending.c:55 > #12 gdk_check_xpending at gdkeventsource.c:269 > #13 gdk_event_source_prepare at gdkeventsource.c:287 > #14 g_main_context_prepare at gmain.c:3450 another X server crash > #8 g_malloc0 at gmem.c:129 > #9 blur_pixels at ../src/st/st-private.c:280 > #10 _st_create_shadow_pipeline at ../src/st/st-private.c:372 > #11 _st_create_shadow_pipeline_from_actor at ../src/st/st- > private.c:434 > #12 st_icon_update_shadow_pipeline at ../src/st/st-icon.c:278 another heap corruption bug. > #8 x_io_error at wayland/meta-xwayland.c:418 > #10 _XReadEvents at xcb_io.c:400 > #11 XIfEvent at IfEvent.c:68 > #12 meta_display_get_current_time_roundtrip at core/display.c:1332 > #13 meta_wayland_surface_destroy_window at wayland/meta-wayland-surface.c:430 another X server crash --Ray _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
