User forums > Nightly builds
The 21 July 2012 build (8150) is out.
Freem:
Code statistics seem to freeze C::B on whole workspace when it is summoned while CC is still parsing (at least, on Debian).
Steps to reproduce:
_ on a slow computer (a netbook in my case, did not try with a desktop PC)
_ open a workspace with enough projects and files so it will take time to CC to parse everything
_ use code statistics and select "entire workspace"
_ C::B will freeze, maybe when CC and code stat try to parse the same file. I have no more clue.
Apart from that, it is a great idea to allow to parse entire workspace. If I may suggest something, it could be useful also for refactoring: currently, there are only "opened files" and "project files" buttons. But when it is a library used by other projects, it is needed to use the replace function.
Jenna:
--- Quote from: Freem on August 16, 2012, 12:54:34 pm ---Code statistics seem to freeze C::B on whole workspace when it is summoned while CC is still parsing (at least, on Debian).
--- End quote ---
I can confirm this, but it happens not always.
I don't see a real cause, why this can happen, because the two plugins do not depend on each other.
Probably it is related to wxEVT_IDLE, which is used to parse the entire workspace.
I will try to dig into it deeper this evening.
oBFusCATed:
Hm, strange... ???
MortenMacFly:
--- Quote from: jens on August 16, 2012, 01:37:18 pm ---I will try to dig into it deeper this evening.
--- End quote ---
I'm afraid this won't be too easy. I am experiencing hangs very seldom, too in combination with files being opeend on project load. It might be it was a "hick-up" of CC causing to access std::maps in a wrong way, but I am not sure. I've already prepared a patch for CC that should "robustify" access to the internal maps accordingly - since that time it seems gone for me... but as I said: It is very rare and not reproducible.
Maybe I should provide a patch here for testing... (I need to clean it up a bit hough...)?!
Jenna:
--- Quote from: MortenMacFly on August 16, 2012, 08:46:20 pm ---
--- Quote from: jens on August 16, 2012, 01:37:18 pm ---I will try to dig into it deeper this evening.
--- End quote ---
I'm afraid this won't be too easy.
--- End quote ---
I run C::B in a debugger-session and if it hangs, I can pause the program.
I have several therads (between 22 and 35).
All threads are in wait-state (pthread_cond_wait), except for thread one (the main thread), which hangs in wxExecute, called from ExpandBackticks.
The process called by wxExecute is already finished, but stays in memory as zombie-process.
I attach a file, that contains a thread-list and two backtraces, that show that the hang always happens in the same function.
It happens in the timer event of cc's parser and it waits for the "answer" of wxExecute in ExpandBackticks.
All hangs that I was able to reproduce happened at the same function, but I did it only 6 or 7 times, so it might not be the only place.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version