Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Request : C::B View::notebook enhancements
daniloz:
--- Quote from: oBFusCATed on January 26, 2011, 03:01:18 pm ---This looks like a CC problem.
Can you try to disable the CC and try to reproduce it.
--- End quote ---
Sorry, now I cannot reproduce it anymore, with or without CC enabled... it seems it's related with a very particular set-up, i.e. which tab was active and to which I go after...
But I'll keep in mind the suggestion and next time I try to disable CC....
Edit:
I was able to reproduce it again and it really seems that when CC is disable I have no bugs anymore... Since using C::B without CC is not an option, what would be the next step? Start another Post?
daniloz:
It really seems that when CC is disable I have no bugs anymore... Since using C::B without CC is not an option, what would be the next step? Start another Post?
oBFusCATed:
If you can provide a minimal sample + steps to reproduce, it will be best.
The other option is to build C::B with debug info and to start debugging in order to find the cause for the crash:)
Jenna:
What happens if you change the editor from the open files list ?
daniloz:
@jens:
I cannot reproduce the problem anymore now... It's really annoying because sometimes it's easily reproducible and sometimes it's not just happening for a long time... But I soon as I can reproduce it again, I'll try the open files list...
@oBFusCATed:
Right now, I cannot reduce the problem to a minimal sample...
@all:
One thing I noticed, though, is that when I have the freeze, it occurs before the line under caret gets highlighted in the editor. Maybe that gives you a clue... :-)
From my side, I'd be more than happy to help by doing some debugging, but I'm still not sure what I have to look for (and, of course, first I need to be able to reproduce the freeze again).
One more info: I've turned on the debug output on parserthread.cpp
--- Code: ---#define CC_PARSERTHREAD_DEBUG_OUTPUT 1
--- End code ---
and I see lots of messages in the DebugLog panel (as expected). If I change from one tab to another before waiting for *all* messages to show up, i.e. while the logging is in progress, it freezes here, no matter what!
I'm just not sure if this is because the parser hasn't finished and that causes the freeze or it's just a display problem, that the DebugLog is flooded with messages and moving to another editor tab just cannot be treated by the painting thread... Anyway, just FYI.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version