Open GoogleCodeExporter opened 8 years ago
After hitting on rip CD the GUI hangs with latest master. commit d74cbef1641ac617fc13bb16673edcdb31a9d806 Author: Bouke Woudstra <boukewoudstra@gmail.com> Date: Thu Jan 24 21:46:08 2013 +0100 Move out of the loop when the iterator is deleted in the loop. Not sure, but running `top`, ruby shows up high on the list. Running `sudo perf record -a` and then `sudo perf report` I see the following. 11,11% ruby libruby-1.9.1.so.1.9.1 [.] 0x15886b 8,80% ruby [kernel.kallsyms] [k] system_call 6,06% ruby [kernel.kallsyms] [k] update_curr 4,39% ruby libc-2.13.so [.] __sched_yield 4,28% ruby [kernel.kallsyms] [k] __schedule 4,24% ruby [kernel.kallsyms] [k] sysret_check 3,83% ruby [kernel.kallsyms] [k] pick_next_task_fair 3,35% ruby [kernel.kallsyms] [k] rb_erase 2,88% ruby [kernel.kallsyms] [k] cpuacct_charge 2,42% ruby libpthread-2.13.so [.] pthread_mutex_lock 2,30% ruby libpthread-2.13.so [.] __pthread_mutex_unlock_usercnt 1,94% ruby [kernel.kallsyms] [k] trace_rcu_utilization 1,83% ruby [kernel.kallsyms] [k] sched_clock_local 1,82% ruby libruby-1.9.1.so.1.9.1 [.] rb_thread_schedule 1,79% ruby [kernel.kallsyms] [k] acpi_pm_read 1,71% ruby libc-2.13.so [.] __sigsetjmp 1,51% ruby [kernel.kallsyms] [k] put_prev_task_fair 1,43% ruby [kernel.kallsyms] [k] sched_clock_cpu 1,37% ruby [kernel.kallsyms] [k] set_next_entity 1,35% ruby libruby-1.9.1.so.1.9.1 [.] rb_thread_alone 1,34% ruby [kernel.kallsyms] [k] yield_task_fair 1,30% ruby [kernel.kallsyms] [k] system_call_after_swapgs 1,28% ruby [kernel.kallsyms] [k] do_raw_spin_lock 1,16% ruby [kernel.kallsyms] [k] rb_insert_color 1,09% ruby [kernel.kallsyms] [k] __enqueue_entity 1,04% ruby [kernel.kallsyms] [k] sys_sched_yield 1,00% ruby [kernel.kallsyms] [k] rb_next 0,98% ruby [kernel.kallsyms] [k] __cycles_2_ns 0,96% ruby [kernel.kallsyms] [k] native_read_tsc 0,91% ruby [kernel.kallsyms] [k] hrtick_start_fair 0,85% ruby [kernel.kallsyms] [k] update_min_vruntime 0,83% ruby [kernel.kallsyms] [k] pick_next_task 0,83% ruby libpthread-2.13.so [.] pthread_cond_broadcast@@GLIBC_2.3.2 0,81% ruby libc-2.13.so [.] __sigjmp_save 0,79% ruby [kernel.kallsyms] [k] update_rq_clock 0,75% ruby [kernel.kallsyms] [k] arch_local_irq_disable 0,71% ruby [kernel.kallsyms] [k] task_of 0,69% ruby [kernel.kallsyms] [k] arch_local_irq_enable 0,65% ruby [kernel.kallsyms] [k] clear_buddies 0,64% ruby [kernel.kallsyms] [k] arch_local_irq_disable 0,64% ruby [kernel.kallsyms] [k] rcu_note_context_switch 0,60% ruby [kernel.kallsyms] [k] schedule 0,53% ruby [kernel.kallsyms] [k] arch_local_save_flags 0,47% ruby [kernel.kallsyms] [k] account_group_exec_runtime 0,45% ruby [kernel.kallsyms] [k] native_sched_clock 0,41% ruby [kernel.kallsyms] [k] _raw_spin_lock_irq 0,41% ruby libpthread-2.13.so [.] pthread_mutex_unlock 0,35% ruby libruby-1.9.1.so.1.9.1 [.] rb_thread_alone@plt 0,31% ruby [kernel.kallsyms] [k] paravirt_read_tsc 0,31% ruby libc-2.13.so [.] _setjmp 0,31% ruby [kernel.kallsyms] [k] sched_clock My guess is, that is some kind of race.
Original issue reported on code.google.com by pm.deb...@googlemail.com on 22 Mar 2013 at 12:39
pm.deb...@googlemail.com
I forgot to say, the window is just grey and no status information were written to it for over ten minutes. So I assume it hung.
Original comment by pm.deb...@googlemail.com on 22 Mar 2013 at 12:44
Original issue reported on code.google.com by
pm.deb...@googlemail.com
on 22 Mar 2013 at 12:39