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 781515 - 100% cpu spin on shutdown
100% cpu spin on shutdown
Status: RESOLVED DUPLICATE of bug 784923
Product: gnome-boxes
Classification: Applications
Component: general
unspecified
Other Linux
: Normal normal
: --
Assigned To: GNOME Boxes maintainer(s)
GNOME Boxes maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-04-19 23:55 UTC by Christian Hergert
Modified: 2017-07-20 12:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Hergert 2017-04-19 23:55:53 UTC 
I tested out a VM last night, and then discarded it. I never installed it, so I assume it was in "live" mode.

I came back to the machine this morning and 1 CPU was spinning at 100%, presumably all night.

Thread 1 "gnome-boxes" received signal SIGINT, Interrupt.
0x00007fd4c764d98c in g_type_check_instance_is_fundamentally_a () from /lib64/libgobject-2.0.so.0
(gdb) bt

+ Trace 237380

  • #0 g_type_check_instance_is_fundamentally_a
    from /lib64/libgobject-2.0.so.0
  • #1 g_object_set_qdata
    from /lib64/libgobject-2.0.so.0
  • #2 gtk_widget_dispose
    from /lib64/libgtk-3.so.0
  • #3 g_object_run_dispose
    from /lib64/libgobject-2.0.so.0
  • #4 boxes_notificationbar_dismiss_all
  • #5 boxes_app_real_shutdown
  • #6 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #7 signal_emit_unlocked_R
    from /lib64/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #10 g_application_run
    from /lib64/libgio-2.0.so.0
  • #11 _vala_main
  • #12 __libc_start_main
    from /lib64/libc.so.6
  • #13 _start 






Comment 1


Christian Hergert





          2017-04-19 23:56:13 UTC
        



By "discarded" it, I mean i just shut the boxes window.






Comment 2


Bastien Nocera





          2017-07-19 19:48:14 UTC
        



Same here, gnome-boxes was running eating a whole core for a whole day here. I created a VM, installed it. Once I was done with it, I deleted it and didn't wait for the in-app notification to disappear before closing the app. This VM was the only one, so there should have been no VMs left running.

Backtraces:




+
Trace
    237677






    

  • 
#0
g_closure_ref

    • 

  • 
#1
g_closure_invoke

    • 

  • 
#2
signal_emit_unlocked_R

    • 

  • 
#3
g_signal_emit_valist

    • 

  • 
#4
g_signal_emit

    • 

  • 
#5
gtk_widget_dispose

    • 

  • 
#6
g_object_run_dispose

    • 

  • 
#7
boxes_notificationbar_dismiss_all

    
                at notificationbar.c
                  line
                  500

    

    • 

  • 
#8
boxes_app_real_shutdown

    
                at app.c
                  line
                  2567

    

    • 

  • 
#9
g_closure_invoke

    • 

  • 
#10
signal_emit_unlocked_R

    • 

  • 
#11
g_signal_emit_valist

    • 

  • 
#12
g_signal_emit

    • 

  • 
#13
g_application_run

    • 

  • 
#14
_vala_main

    
                at main.c
                  line
                  477

    

    • 

  • 
#15
__libc_start_main

    • 

  • 
#16
_start

    • 

  • 
#0
g_pointer_bit_unlock

    • 

  • 
#1
gtk_widget_real_destroy

    • 

  • 
#2
g_closure_invoke

    • 

  • 
#3
signal_emit_unlocked_R

    • 

  • 
#4
g_signal_emit_valist

    • 

  • 
#5
g_signal_emit

    • 

  • 
#6
gtk_widget_dispose

    • 

  • 
#7
g_object_run_dispose

    • 

  • 
#8
boxes_notificationbar_dismiss_all

    
                at notificationbar.c
                  line
                  500

    

    • 

  • 
#9
boxes_app_real_shutdown

    
                at app.c
                  line
                  2567

    

    • 

  • 
#10
g_closure_invoke

    • 

  • 
#11
signal_emit_unlocked_R

    • 

  • 
#12
g_signal_emit_valist

    • 

  • 
#13
g_signal_emit

    • 

  • 
#14
g_application_run

    • 

  • 
#15
_vala_main

    
                at main.c
                  line
                  477

    

    • 

  • 
#16
__libc_start_main

    • 

  • 
#17
_start

    • 








My guess is that this piece of code is the culprit:
 78     public void dismiss_all () {•
 79         // We destroy all active notifications, which will cause them to be dismissed•
 80         while (active_notifications != null) {•
 81             active_notifications.data.destroy ();•
 82         }•
 83     }•






Comment 3


Bastien Nocera





          2017-07-19 19:49:13 UTC
        



There are 2 backtraces above, but BZ made it into one.

Christian, did you close the window before the notification went away as well?






Comment 4


Christian Hergert





          2017-07-19 20:42:24 UTC
        



(In reply to Bastien Nocera from comment #3)
> Christian, did you close the window before the notification went away as
> well?

I don't remember for sure, but that sounds likely.






Comment 5


Bastien Nocera





          2017-07-20 12:25:26 UTC
        



Bug 784923 contains a patch for this.

Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 784923 ***