Opened 11 years ago

Last modified 10 years ago

#113 assigned task

museeq randomly hogging cpu

Reported by: Cravings Owned by: lbponey
Priority: minor Milestone:
Component: museeq Version: 0.2prerelease (newnet2 branch)
Keywords: Cc:

Description

hello i often notice that museeq is using all my available cpu. i don't know what triggers this.. it can happen in a session where i've done so searches, had no active transfers in either direction, spoken in a room... it happens randomly. when it does, i used to think that disconnecting it from museekd and then reconnecting it did the trick, i've since noticed that even just clicking on the "file" menu will release whatever it is. because of this... i don't think the problem has anything to do with museekd, but is more likely something to do with qt. i wouldn't know though. is there a debug option or mode for museeq?

anything i can do to make things more verbose?

thanks if you can help.

generally up to date with svn.

Change History (9)

comment:1 Changed 11 years ago by Cravings

above should say "done no searches"...

comment:2 Changed 11 years ago by lbponey

Status: newassigned

Yes, this really seems like a Qt problem. Unfortunately there isn't that much debug output you can get from museeq. When this happens, is museeq minimized? Do you see any particular output in museekd log? Which version of Qt are you using? Does it happen whatever icon is selected (transfers/chat/rooms/...)? Thanks!

comment:3 Changed 11 years ago by Cravings

like i said, i haven't noticed any pattern to it.i'll update this ticket with any observations i have. not a big problem, it doesn't actually hinder anything and as i said it's very easy to have it "let go" of the cpu again.

comment:4 Changed 11 years ago by Cravings

well it happened once today. all i noticed was.. the chat tab was open, museeq was minimised, maximising it and switching between modes did nothing.. clicking once on "scripts" made it let go. and i'm installing museek with SeeSchloss' museekplus-svn aurbuild, on archlinux, with qt 4.4.3-2.

comment:5 Changed 11 years ago by lbponey

Milestone: Release 0.2.0Release 0.3

ok. I don't think it's a blocking for 0.2, so I'll try to find a solution for 0.3. Thanks!

comment:6 Changed 11 years ago by Cravings

no it's not critical. happened once again today, when museeq was maximised, and on chat tab. right clicking on the chat room background (main room window) let it go. (i'll just continue to put up random observations till i get a good one.. heh)

comment:7 Changed 11 years ago by cravings

ok, slightly new observation. just noticed (i use gkrellm) my cpu was maxed out, it was museeq process again. museeq was minimised. but this time, i was able to free it by hovering the mouse cursor over the trayicon till the "Museeq" tooltip came and went. i often see visual artifacts around the trayicon.... like remnants of the tooltip, or a previous background (does that make sense?).. i use fluxbox fwiw.

comment:8 Changed 11 years ago by Silver

Today I used Museeq 0.2 for the first time to search music. The result is that it's terribly slow and eating CPU especially while searching and filtering (the amount of usage actually depends on how many results the search gave). I'd say it's unusably slow on my machine (FreeBSD-7, 3 GHz CPU).

comment:9 Changed 10 years ago by lbponey

Milestone: Release 0.3
Note: See TracTickets for help on using tickets.