CEF3 crash when running with --single-process

[rdowdall]

Hello

cef3 revision: 1450
chromium revision: 220934

Running on Archlinux, with KDE 4.11.

I am trying to run the cef3 client with the --single-process option. It is crashing with the following back trace:

#0 0x00007fffeae44224 in pthread_mutex_lock () from /usr/lib/libpthread.so.0
#1 0x00007fffef517d8c in XrmQGetResource () from /usr/lib/libX11.so.6
#2 0x00007fffef4f56a2 in XGetDefault () from /usr/lib/libX11.so.6
#3 0x00007fffedf1b96f in ?? () from /usr/lib/libcairo.so.2
#4 0x00007fffedf1e290 in ?? () from /usr/lib/libcairo.so.2
#5 0x00007fffedef07e7 in cairo_surface_get_font_options () from /usr/lib/libcairo.so.2
#6 0x00007fffedeb026f in ?? () from /usr/lib/libcairo.so.2
#7 0x00007fffedeb3d65 in ?? () from /usr/lib/libcairo.so.2
#8 0x00007fffedea6552 in cairo_show_glyphs () from /usr/lib/libcairo.so.2
#9 0x00007fffee3cde33 in ?? () from /usr/lib/libpangocairo-1.0.so.0
#10 0x00007fffee3ce144 in ?? () from /usr/lib/libpangocairo-1.0.so.0
#11 0x00007fffed4cb51f in pango_renderer_draw_glyphs () from /usr/lib/libpango-1.0.so.0
#12 0x00007fffed4cbea8 in pango_renderer_draw_layout_line () from /usr/lib/libpango-1.0.so.0
#13 0x00007fffed4cc205 in pango_renderer_draw_layout () from /usr/lib/libpango-1.0.so.0
#14 0x00007fffee3ce2ea in ?? () from /usr/lib/libpangocairo-1.0.so.0
#15 0x00007fffe03e98d6 in drawLayout () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
#16 0x00007fffe03bf6c9 in ?? () from /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so
#17 0x00007fffee9a77ad in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#18 0x00007fffee8f709c in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#19 0x00007fffee9b2345 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#20 0x00007fffed2653d2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#21 0x00007fffed2761cb in ?? () from /usr/lib/libgobject-2.0.so.0
#22 0x00007fffed27de52 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#23 0x00007fffed27e462 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#24 0x00007fffeeac1a14 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#25 0x00007fffee93b9b8 in gtk_container_propagate_expose () from /usr/lib/libgtk-x11-2.0.so.0
#26 0x00007fffee93a544 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x00007fffee9c00d5 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#28 0x00007fffee9b2345 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#29 0x00007fffed2653d2 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#30 0x00007fffed2761cb in ?? () from /usr/lib/libgobject-2.0.so.0
#31 0x00007fffed27de52 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#32 0x00007fffed27e462 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#33 0x00007fffeeac1a14 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#34 0x00007fffee93b9b8 in gtk_container_propagate_expose () from /usr/lib/libgtk-x11-2.0.so.0
#35 0x00007fffee9c2175 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#36 0x00007fffee93a544 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#37 0x00007fffee9bda2e in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#38 0x00007fffee9b2345 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#39 0x00007fffed265458 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#40 0x00007fffed2761cb in ?? () from /usr/lib/libgobject-2.0.so.0
#41 0x00007fffed27de52 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#42 0x00007fffed27e462 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#43 0x00007fffeeac1a14 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#44 0x00007fffee9b1140 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#45 0x00007ffff3caddc7 in base::MessagePumpGtk::DispatchEvents (this=0x7ffff7e570f0, event=0x7fffffffd1f0) at ../../base/message_loop/message_pump_gtk.cc:81
#46 0x00007ffff3cadfed in base::MessagePumpGtk::EventDispatcher (event=0x7fffffffd1f0, data=0x7ffff7e570f0) at ../../base/message_loop/message_pump_gtk.cc:111
#47 0x00007fffee61483f in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#48 0x00007fffee6147e5 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#49 0x00007fffee61147e in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#50 0x00007fffee611d68 in gdk_window_process_all_updates () from /usr/lib/libgdk-x11-2.0.so.0
#51 0x00007fffee93a231 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#52 0x00007fffee5f16a7 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#53 0x00007fffec8a3d96 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#54 0x00007fffec8a40e8 in ?? () from /usr/lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#55 0x00007fffec8a418c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#56 0x00007ffff3cabdcf in base::MessagePumpGlib::RunWithDispatcher (this=0x7ffff7e570f0, delegate=0x7ffff7ed1020, dispatcher=0x0)
at ../../base/message_loop/message_pump_glib.cc:205
#57 0x00007ffff3cac308 in base::MessagePumpGlib::Run (this=0x7ffff7e570f0, delegate=0x7ffff7ed1020) at ../../base/message_loop/message_pump_glib.cc:302
#58 0x00007ffff3d15342 in base::MessageLoop::RunInternal (this=0x7ffff7ed1020) at ../../base/message_loop/message_loop.cc:436
#59 0x00007ffff3d151e8 in base::MessageLoop::RunHandler (this=0x7ffff7ed1020) at ../../base/message_loop/message_loop.cc:409
#60 0x00007ffff3d4d00a in base::RunLoop::Run (this=0x7fffffffd950) at ../../base/run_loop.cc:45
#61 0x00007ffff3d14af8 in base::MessageLoop::Run (this=0x7ffff7ed1020) at ../../base/message_loop/message_loop.cc:307
#62 0x00007ffff356142a in CefBrowserMessageLoop::RunMessageLoop (this=0x7ffff7ed1020) at ../../cef/libcef/browser/browser_message_loop.cc:27
#63 0x00007ffff3572882 in CefRunMessageLoop () at ../../cef/libcef/browser/context.cc:162
#64 0x00007ffff00ff487 in cef_run_message_loop () at ../../cef/libcef_dll/libcef_dll.cc:260
#65 0x0000000000430697 in CefRunMessageLoop () at ../../cef/libcef_dll/wrapper/libcef_dll_wrapper.cc:252
#66 0x000000000042adf2 in main (argc=2, argv=0x7fffffffe028) at ../../cef/tests/cefclient/cefclient_gtk.cpp:371


Also, is the --single-process option a viable option? Are there plans to drop it as an option in the near future? It would seem that it's main use is for debugging purposes.

Thanks,
Rodney

[magreenblatt]

The crash is https://code.google.com/p/chromiumembed ... ail?id=976

Also, is the --single-process option a viable option? Are there plans to drop it as an option in the near future? It would seem that it's main use is for debugging purposes.

It is intended for development purposes. It is unlikely to be dropped. It is unlikely to become as stable as the multi-process option.