Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

CodeCompletion freezes C::B after project drag'n drop

<< < (3/3)

MortenMacFly:

--- Quote from: ollydbg on January 20, 2012, 02:52:44 pm ---That revision rewrite the locker in many files, I guess there are some dead locks.

--- End quote ---
Either that, or (in combination) could you check if you have enabled "parse while typing" in the CC settings? If so, turn it off and try again. I experienced some issues with that feature recently - probably we should remove it or at least disable it by default.

ollydbg:

--- Quote from: MortenMacFly on January 20, 2012, 03:05:34 pm ---
--- Quote from: ollydbg on January 20, 2012, 02:52:44 pm ---That revision rewrite the locker in many files, I guess there are some dead locks.

--- End quote ---
Either that, or (in combination) could you check if you have enabled "parse while typing" in the CC settings? If so, turn it off and try again. I experienced some issues with that feature recently - probably we should remove it or at least disable it by default.

--- End quote ---
Enabled "parse while typing" is always ON in my c::b, sometimes, c::b hangs for a while(1 second maybe) after I enter some characters. Did you have such issue?

I have no idea to catch such issue. I'm thinking that the lockers should be removed totally.
The new method looks like:
The thread Pool can have a function: Pause and Resume. When we pause it, it just finish the currently running thread, and no new thread should be started. When we resume it, it can continue running.

So, we can do some UI related work when we pause the parserthread pool. This way, we can remove all the lockers. There is an assumption that one parserthread should no taking too long time to finish its parsing work.

oBFusCATed:

--- Quote from: ollydbg on January 20, 2012, 03:23:52 pm ---The thread Pool can have a function: Pause and Resume. When we pause it, it just finish the currently running thread, and no new thread should be started. When we resume it, it can continue running.

--- End quote ---
Please don't waste time on such a scheme, because it will fail pretty miserably.

ollydbg:

--- Quote from: oBFusCATed on January 20, 2012, 04:15:26 pm ---
--- Quote from: ollydbg on January 20, 2012, 03:23:52 pm ---The thread Pool can have a function: Pause and Resume. When we pause it, it just finish the currently running thread, and no new thread should be started. When we resume it, it can continue running.

--- End quote ---
Please don't waste time on such a scheme, because it will fail pretty miserably.

--- End quote ---
Ok, but can we have a better scheme then current "many locker" scheme?

oBFusCATed:
I don't know.

Navigation

[0] Message Index

[*] Previous page