MantisBT - DriverPacks BASE
View Issue Details
0000095DriverPacks BASEGUIpublic2006-07-27 05:232006-07-27 06:30
Helmi 
BashratTheSneaky 
immediatetrivialalways
resolvedfixed 
6.07 b1 
6.07 b2 
not applicable
not applicable
not applicable
not applicable
not applicable
0000095: BASE takes up /view.php?id=6#c45% CPU load directly after having been launched
Directly after launching, BASE will utilize as much as 45% of CPU usage, while it just sists there idling.
I have NOT commenced any slipstream processes yet, so there is really nothing to compute.
Granted, this is on my Pentium M and the 45% are while it is clocked at only 800MHz but I still can't figure out what it is doing.
After closing BASE, CPU load will immediately go back to 0%, just as it should be (ie not other background processes take up any CPU cycles).
No tags attached.
Issue History
2006-07-27 05:23HelmiNew Issue
2006-07-27 05:23HelmiStatusnew => assigned
2006-07-27 05:23HelmiAssigned To => BashratTheSneaky
2006-07-27 05:23HelmiDestination OS Platform => wnt5_x86-32 (Windows XP)
2006-07-27 05:23HelmiInstallation Platform => not applicable
2006-07-27 05:23HelmiDriverPacks => not applicable
2006-07-27 05:23HelmiDriverPacks Method => not applicable
2006-07-27 05:23HelmiDriverPacks Finisher Method => not applicable
2006-07-27 05:38BashratTheSneakyDestination OS Platformwnt5_x86-32 (Windows XP) => not applicable
2006-07-27 05:38BashratTheSneakyNote Added: 0000254
2006-07-27 05:38BashratTheSneakyStatusassigned => confirmed
2006-07-27 05:39BashratTheSneakyPrioritynormal => immediate
2006-07-27 05:39BashratTheSneakyETAnone => < 1 day
2006-07-27 06:30BashratTheSneakyStatusconfirmed => resolved
2006-07-27 06:30BashratTheSneakyFixed in Version => 6.07 b2
2006-07-27 06:30BashratTheSneakyResolutionopen => fixed
2006-07-27 06:30BashratTheSneakyNote Added: 0000255

Notes
(0000254)
BashratTheSneaky   
2006-07-27 05:38   
Reproduced.
(0000255)
BashratTheSneaky   
2006-07-27 06:30   
This was due to an inefficient way of checking for new GUI messages specific for the current page. Now it's back to 1-3% in my VM testing environment.