Hi. I'm a computer engineering student and use with Hugs98, which helps me a lot in learning fuctional programming. I've noticed that the WinHugs application eats 100% of the available CPU even when it isn't doing any work, just blinking the cursor!!! I use CPUIddle to cool-down my processor and I saw a noticeable increase in CPU temperature whenever WinHugs was opened, although out of focus and without any task running. This is not a major problem, but if it could be solved easily, overclocked CPUs would not crash under WinHugs and batteries in LapTops would last longer. Thanks !!!!!!!!! Roberto Barrios, Facultad de Informática, Universidad Complutense de Madrid
At 21:08 +0100 1-01-13, Roberto Barrios wrote:
Hi. I'm a computer engineering student and use with Hugs98, which helps me a lot in learning fuctional programming. I've noticed that the WinHugs application eats 100% of the available CPU even when it isn't doing any work, just blinking the cursor!!! I use CPUIddle to cool-down my processor and I saw a noticeable increase in CPU temperature whenever WinHugs was opened, although out of focus and without any task running.
This sounds as though it could be due to the fact MSOS uses cooperative multitasking, and WinHugs doesn't release any time to other programs. (In which case it is not a "bug", but a "feature".) Hans Aberg
Hi Roberto, | I've noticed that the WinHugs application eats 100% of the available CPU even | when it isn't doing any work, just blinking the cursor!!! This is a well-known problem with the WinHugs user interface, and is one of the reasons why use of WinHugs has been discouraged. The user manual comments on this, for example, but perhaps the wording should be stronger! WinHugs was even left out of the Hugs distribution at one stage because these problems were felt to be too severe. But people still asked for it and so WinHugs made it back into the distribution ... The WinHugs interface eats CPU because of the style in which it was written. The original author of the WinHugs GUI, Pepe Gallardo, did produce a newer version that avoided these problems, but I don't know what happened to it; I'm not aware of a source for it on the web. Pepe, if you're out there, I'm sure folks like Roberto would be happy to hear from you! In the meantime, I wouldn't recommend using WinHugs for everyday use. All the best, Mark
participants (3)
-
Hans Aberg -
Mark P Jones -
med018509＠nacom.es