After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782464 - Crash: gjs_object_from_g_object → gjs_value_from_g_argument
Crash: gjs_object_from_g_object → gjs_value_from_g_argument
Status: RESOLVED INCOMPLETE
Product: gjs
Classification: Bindings
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: gjs-maint
gjs-maint
Depends on:
Blocks:
 
 
Reported: 2017-05-10 17:06 UTC by Jeremy Bicha
Modified: 2017-08-07 15:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeremy Bicha 2017-05-10 17:06:38 UTC
Ubuntu has received a few semi-automated error reports from Ubuntu 17.04 with this crash signature. The crash appears new to gnome-shell 3.24.1.

This error is one of several keeping gnome-shell 3.24.1 from reaching all Ubuntu 17.04 users because Ubuntu has a phased-update system for users who install updates using Ubuntu's update-manager tool.

gnome-shell (6) g_assertion_message → g_assertion_message_expr → get_object_qdata → gjs_object_from_g_object → gjs_value_from_g_argument

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 58
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
  • #4 get_object_qdata
    at gi/object.cpp line 220
  • #5 gjs_object_from_g_object
    at gi/object.cpp line 2197
  • #6 gjs_value_from_g_argument
    at gi/arg.cpp line 2840
  • #7 gjs_invoke_c_function
    at gi/function.cpp line 1079
  • #8 function_call
    at gi/function.cpp line 1341
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??

Comment 1 Jeremy Bicha 2017-05-10 17:07:42 UTC
.

Thread 11 (Thread 0x7fe49cc04700 (LWP 2291))

  • #0 syscall
    at ../sysdeps/unix/sysv/linux/x86_64/syscall.S line 38
  • #1 g_cond_wait_until
    at ../../../../glib/gthread-posix.c line 1442
  • #2 g_async_queue_pop_intern_unlocked
    at ../../../../glib/gasyncqueue.c line 422
  • #3 g_async_queue_timeout_pop
    at ../../../../glib/gasyncqueue.c line 543
  • #4 g_thread_pool_wait_for_new_pool
    at ../../../../glib/gthreadpool.c line 167
  • #5 g_thread_pool_thread_proxy
    at ../../../../glib/gthreadpool.c line 364
  • #6 g_thread_proxy
    at ../../../../glib/gthread.c line 784
  • #7 start_thread
    at pthread_create.c line 456
  • #8 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 105

Thread 1 (Thread 0x7fe50c138ac0 (LWP 1507))

  • #0 __GI_raise
    at ../sysdeps/unix/sysv/linux/raise.c line 58
  • #1 __GI_abort
    at abort.c line 89
  • #2 g_assertion_message
  • #3 g_assertion_message_expr
  • #4 get_object_qdata
    at gi/object.cpp line 220
  • #5 gjs_object_from_g_object
    at gi/object.cpp line 2197
  • #6 gjs_value_from_g_argument
    at gi/arg.cpp line 2840
  • #7 gjs_invoke_c_function
    at gi/function.cpp line 1079
  • #8 function_call
    at gi/function.cpp line 1341
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??

Comment 2 Philip Chimento 2017-05-14 23:22:20 UTC
Any info on what triggers this crash?
Comment 3 Jeremy Bicha 2017-05-15 14:23:30 UTC
Philip, I don't really have any additional info. The error signature was reported 4 times with gnome-shell 3.24.1 and gjs 1.48.2.
Comment 4 Jeremy Bicha 2017-05-16 14:24:51 UTC
I filed bug 782692 and GNOME's bug tracker suggested that it might be a duplicate of this one. I'm not so sure…
Comment 5 Philip Chimento 2017-06-16 01:11:45 UTC
This may have been solved with the patches released in GJS 1.48.4. Without `gjs_dumpstack()` or some reproducer info I can't really tell, though. Feel free to reopen this if the problem reoccurs with 1.48.4.