Unity eats cpu after switching to the greeter/back in the session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Invalid
|
High
|
Andrea Azzarone |
Bug Description
That started in xenial, often Unity is eating cpu after going to unity-greeter/
gdb indicates that some code is "stucked" in pam (while the session is unlocked)
"Thread 2 (Thread 0xa881cb40 (LWP 26675)):
#0 0xb77c1c38 in __kernel_vsyscall ()
#1 0xb744d5d7 in syscall () at ../sysdeps/
#2 0xb75dd1b6 in std::__
#3 0xafa5af4f in std::__
__equal=
#4 std::__
this=<optimized out>) at /usr/include/
#5 std::__
#6 std::__
#7 std::__
at /usr/include/
#8 std::future<
#9 unity::
at /build/
#10 0xae955243 in pam_vprompt (pamh=0xb343d38, style=1, response=
#11 0xae95540c in pam_prompt (pamh=0xb343d38, style=1, response=
#12 0xaab2ca7e in _unix_read_password (pamh=0xb343d38, ctrl=276824064, comment=0x0, prompt1=0xac1c46fc "Mot de passe : ", prompt2=0x0, data_name=
pass=
#13 0xaab2a093 in pam_sm_authenticate (pamh=0xb343d38, flags=0, argc=1, argv=0xa9e2480) at pam_unix_auth.c:160
#14 0xae950450 in _pam_dispatch_aux (use_cached_
#15 _pam_dispatch (pamh=0xb343d38, flags=0, choice=1) at pam_dispatch.c:395
#16 0xae94fc7a in pam_authenticate (pamh=0xb343d38, flags=0) at pam_auth.c:34
#17 0xafa59892 in unity::
at /build/
#18 unity::
at /build/
#19 0xb45f365d in g_task_
#20 0xb707f9f4 in g_thread_
#21 0xb707ef9a in g_thread_proxy (data=0x9d28c00) at /build/
#22 0xb6fe818a in start_thread (arg=0xa881cb40) at pthread_
#23 0xb745200e in clone () at ../sysdeps/
Changed in unity (Ubuntu): | |
importance: | Undecided → High |
summary: |
- Unity eats cpu after switch to greeter/back to session + Unity eats cpu after switching to the greeter/back in the session |
tags: | added: rls-x-incoming |
Changed in unity (Ubuntu): | |
assignee: | nobody → Andrea Azzarone (azzar1) |
tags: | added: u7-trello-import |
tags: | removed: u7-trello-import |
it stopped doing it for me and there is no other report, let's close it