User forums > Using Code::Blocks
Code::Blocks slow as molasses
Clojster:
--- Quote from: Michael on March 20, 2006, 10:07:31 am ---
--- Quote from: Clojster on March 20, 2006, 09:57:57 am ---The problem I described above occurs in RC2. Yesterday I upgraded to SVN build 2211, but the problem is still there. Now I can see the mouse pointer while moving in editor, but typing is terribly slow...
I'm on Linux by the way. On Windows everything is fine (I have tried it in vmware). I have the same problem in wyoEditor too.
--- End quote ---
Try to de-activate some plugins or all and see if it works better. In your system work all other applications normally (fast)?
Best wishes,
Michael
--- End quote ---
Of course... everything is smooth and fast. Only this editor has this weird behavior...
And this slowdown persists even when every plugin has been deactivated and c::b restarted...
I really don't know where can be the problem... :/
Der Meister:
I remember a bug-report on sourceforge.net that said that this problem is related to the nvidia graphics driver. Unfortunately the bug tracker for the sourceforge-project auf Code::Blocks is disabled, so I can't show you this bug report.
Anyway, I didn't check if this bug could be reproduced. I have a nvidia graphics card (4200TI) and I'm using the nvidia graphics driver (I'm not sure which version I have installed - must be something like 6xxx.) but I don't have such problems. But the editor uses quite a lot CPU-power compared to other editors. But as it is not a problem for me I didn't deactivate this driver to see if the editor uses less CPU-power with another graphics driver.
Clojster:
Well, that was me myself who reported that bug. But even when I reported that bug I wasn't sure for 100% if it's related to graphics driver... I'll check it out. And I think that every other text editors works pretty good with this drivers so I wouldn't blame them. I think that bug is in the editor itself...
EDIT: Ok, now I have tested it with standard Xorg's "nv" driver. The problem isn't that markant as with nvidia drivers, but it's there too. CPU usage raises, but typing and moving with mouse has better responsibility with "nv" drivers.
Also by turning off all plugins help in therms of CPU usage while typing and moving cursor above the editor... So I think that responsibility problem might be in nvidia drivers, but that CPU usage is terrible...
What about let the users decide which editor they want to use? (Some option withl list of choices)? I'd prefer VIM (gvim)...
Der Meister:
Well, sounds like a nice idea but this would require a common interface for all editors. I'm not sure how much of Code::Blocks depends on scintilla but I don't think that you can just take another editor and replace the old one without at least some changes. I think it should be possible but the problem is: is it really worth the costs? The current editor works quite well (apart from this problem) and I don't believe that most other editors would be better. OK, you said you would prefer VIM. But do you really need it inside Code::Blocks? And how much other users would also choose a different editor? I don't believe that there are a lot of them. And to achive this you must create a common interface for all editors that shall be supported (if this interface is not already there) first and then you have to care about more than just one editor. You have to integrate and test new versions, etc.
As I said, it sounds like a nice idea but I don't think it is worth the costs. Just my opinion and not the opinion of a developer so don't take it into account to much ;)
PS: Sorry for OT...
Clojster:
Well ok, I think it would be great to have the possibility of choice :)
Maybe some developer could tell us what he thinks?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version