User forums > Nightly builds
The 28 march 2006 build is out.
sethjackson:
So why does removing the flag make the 99% CPU bug go away then? :? I'm not trying to be argumentative just wondering...... Umm so what is my problem? Why can I not start C::B without default.conf?
EDIT:
This build works fine without default.conf.... Unfortunately my version compiled from SVN doesn't. :P
Pecan:
--- Quote from: sethjackson on March 29, 2006, 09:03:44 pm ---So why does removing the flag make the 99% CPU bug go away then? :? I'm not trying to be argumentative just wondering...... Umm so what is my problem? Why can I not start C::B without default.conf?
EDIT:
This build works fine without default.conf.... Unfortunately my version compiled from SVN doesn't. :P
--- End quote ---
I can confirm the 99% cpu bug is still present. I deleted my
*.conf, started CB. After choosing gcc at the compiler dlg, CB
went into a 99% cpu loop displaying the splash.
sethjackson:
Thanks Pecan. At least I'm not alone in this big big world. :lol: Anyways I wonder how to fix it??
If I download the nightly (this one), then delete my default.conf, the nightly runs fine. However, my SVN version doesn't. :shock:
thomas:
Well, look at app.cpp, line 575. Whatever is in that header, the default value is not used. Changing the default value in the header does not fix anything.
Yiannis was working on the startup problems yesterday afternoon, I thought he had fixed everything. Maybe there's more than one thing. Whatever it is, it is not the wxSTAY_ON_TOP flag, however. :)
Pecan:
--- Quote from: Pecan on March 29, 2006, 09:11:47 pm ---I can confirm the 99% cpu bug is still present. I deleted my
*.conf, started CB. After choosing gcc at the compiler dlg, CB
went into a 99% cpu loop displaying the splash.
--- End quote ---
However, clearing the STAY_ON_TOP flag did not solve the problem.
sorry
pecan
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version