On 03/20/2011 02:06 PM, Dragan Noveski wrote:
On 20.03.2011 14:02, Magnus Hjorth wrote:
Hi,
On 03/20/2011 01:38 PM, Dragan Noveski wrote:
when the file is loaded and i press play in mhwave, looking into
htop, mhwave eats about 96% of cpu. this takes about 20-30 seconds
until mhwave starts to play. than the cpu goes down in the next 5
sec's while mhwave is playing to 13% .
Could you check if the 96% of cpu is in spent in user or system? I
don't know how to do this in htop but in normal top it is shown in
one of the heading rows as "Cpu(s): 7.0%us, 3.0%sy, 0.0%ni" ...
looks like this here:
Cpu(s): 97.4%us, 2.6%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi,
0.0%si, 0.0%st
Hmm this might be be a mhwaveedit bug..
Could you try running mhwaveedit inside gdb, open the ogg and press
play, press Ctrl-C when it hangs and then do a backtrace, like this:
$ gdb src/mhwaveedit
...
(gdb) run
...
^C
Program received signal SIGINT, Interrupt.
0x0012d422 in __kernel_vsyscall ()
(gdb) bt
#0 0x0012d422 in __kernel_vsyscall ()
#1 0x00dd3b86 in *__GI___poll (fds=0xe69ff4, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:87
#2 0x008c84eb in IA__g_poll (fds=0x8115d48, nfds=2, timeout=-1)
at /build/buildd/glib2.0-2.24.1/glib/gpoll.c:127
/Magnus
_______________________________________________
Mhwaveedit-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/mhwaveedit-discuss
