Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU-count Bug #30

Open
Dieter9 opened this issue Sep 3, 2016 · 4 comments
Open

CPU-count Bug #30

Dieter9 opened this issue Sep 3, 2016 · 4 comments

Comments

@Dieter9
Copy link

Dieter9 commented Sep 3, 2016

There is a bug in aqemu 0.9.3 from actual github.
If you set the number of CPUs to 2 or more and switch between different VMs, the number
it always set back to 1.

I had a look at the code and found the reason for that behavior:
file: Main_Window.ccp
subroutine: Main_Window::Update_Disabled_Controls()
line 1695: ui.CB_CPU_Count->clear();

When I deleted this line, everything works fine.

Perhaps the line is at the wrong place and should be inserted in the nearby block
if( curComp.PSO_SMP_Count == 1 )
{
But I don't know what the block is for and how to test it.

@tobimensch
Copy link
Owner

Thanks for reporting this, I'll look into it.

@lv-zheng
Copy link

lv-zheng commented Nov 4, 2016

Confirmed on v0.9.2.
In function void Main_Window::Update_VM_Ui(bool update_info_tab)
line 1589 on v0.9.2 (or 1646 on master): Update_Disabled_Controls(); // FIXME
Why FIXME here?

@watchix
Copy link

watchix commented Nov 24, 2016

Same problem with the cpu count : 0.9.2-2 (Debian stretch/sid)

@stef204
Copy link

stef204 commented Jan 8, 2017

Same. I commented out the offending line
// ui.CB_CPU_Count->clear();
and the "number of cpu's" now "sticks".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants