Hello SPARK users,
I've begin to work on the cpu issue that affects some of you Windows users.
This is a behaviour that I unfortunately am not able to reproduce on my development machines so I'll need some help from you:
1- we'll need a "cpu log file" that can be generated "on demand" by a special debug version of SPARK
2- we'll need a report on your system generated when SPARK is running,
3- and finally we'll need some infos which are displayed by the standard Windows tool "Task Manager" while SPARK is running.
If you accept to give me your help just send me a private forum mail and I'll send you a package containing detailed instructions and the debug version of SPARK.
Here follows a brief description of the actions you'll have to execute.
1- you'll have to use a debug version of SPARK which has exactly the capabilities of the 1.6.1 version plus an additional toggle button on the GUI you can use to generate a log file of various CPU measurements. We'll need a log generated when the consumed CPU is normal, and a few more logs when SPARK shows this huge cpu behaviour.
2- the system report is built using a free tool named GetSystemInfo. You'll have to download this tool, run it, grab the report file and send it to me
3- when executing the step 1, you should have launched the Windows Task Manager and grab some infos displayed by this tool (Alt GR + print screen), and send me your screenshots.