News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

crash when double click the selected text!

Started by mikeandmore, April 01, 2006, 06:53:51 AM

Previous topic - Next topic

mikeandmore

1.select an part of text
2.double click on them
3.your cpu is ok,ram is ok,other app are ok,but CB made the whole sreen locked and no response at all.
4.restart your PC,and you have lost all the data which you didn't save.

takeshimiya

Let me guess... linux right?
That happened to me sometimes, and the 'double click' thing is probably a small drag&drop state.
Somehow dragging anything may cause segfaults. Dragging panels, dragging toolbars, dragging tabs. But the crashes are more often presented when dragging text. It's like it 'hangs' in a drag&drop state.

gfgfd

hapends to me atleast once every day :(
use shortcuts to save & quit when cb locks screen like that. ctrl+shift+s to save and ctrl+q to quit.. and if that fails use ctrl+alt+f2 to switch to console, login and 'killall codeblocks'.

[url="http://www.linux-stats.org/list-button.php?id=416"]http://www.linux-stats.org/list-button.php?id=416[/url]

takeshimiya

Quote from: gfgfd on April 01, 2006, 10:29:39 AM
hapends to me atleast once every day :(
use shortcuts to save & quit when cb locks screen like that. ctrl+shift+s to save and ctrl+q to quit.. and if that fails use ctrl+alt+f2 to switch to console, login and 'killall codeblocks'.
Heh, yes, most of times the keywoard still works, what seems to hand is the interface with the mouse (in a drag&drop state).

Pecan

Quote from: Takeshi Miya on April 01, 2006, 08:29:58 AM
Let me guess... linux right?
That happened to me sometimes, and the 'double click' thing is probably a small drag&drop state.
Somehow dragging anything may cause segfaults. Dragging panels, dragging toolbars, dragging tabs. But the crashes are more often presented when dragging text. It's like it 'hangs' in a drag&drop state.


Have you tried getting the crash with all but compiler
turned off. Is this a plugin problem?

thanks
pecan

takeshimiya

Quote from: Pecan on April 01, 2006, 04:41:56 PM
Have you tried getting the crash with all but compiler
turned off. Is this a plugin problem?

I think it's not only one problem, it's multiple problems.
I can reproduce the hang with SciTE when dragging text on linux, so that could mean that the problem is either in Scintilla, or GTK2.

BUT, I also get hangs when dragging toolbars/panels/tabs, so they could be the same bug, or different bugs, for instance in Scintilla, GTK, wxWidgets, wxAUI, C::B, ...

mikeandmore

it's the wxscintilla 's problem,i think

for scite and gtk apps works.
amule and other wx apps works.

for wxscintilla i dono.at lease CB "crash"

mikeandmore

i got it! :D

It is wxscintilla's bug,MingStudio also has that bug!!!
but SciTE and GTK apps is OK!

takeshimiya

Quote from: mikeandmore on April 01, 2006, 06:09:56 PM
i got it! :D

It is wxscintilla's bug,MingStudio also has that bug!!!
but SciTE and GTK apps is OK!

I have experienced it with SciTE too...

Again, it could be different unrelated (or related?) bugs.

Pecan

Quote from: mikeandmore on April 01, 2006, 05:59:33 PM
it's the wxscintilla 's problem,i think

Yep, wxScintilla.
Notice that when dragging, scintilla places a "page" cursor along with the "+" cursor of gtk when dragging a marked area.
Notice also, that the "page" cursor is missing when you double click on a marked area.

Scintilla and GTK are not in sync. GTK thinks the drag is occuring while scintilla thinks a double click is supposed
to unmark the marked area. No one is telling GTK the drag is over. Its a deadly embrace.

CB is running on 1.62 scintilla. What other version of scintilla are behaving correctly on GTK? That ought to give us a clue.

Michael

Quote from: Pecan on April 01, 2006, 08:12:54 PM
CB is running on 1.62 scintilla. What other version of scintilla are behaving correctly on GTK? That ought to give us a clue.

May be wxScintilla 1.68 would solve the problem.

Best wishes,
Michael
[url="http://img207.imageshack.us/img207/9728/411948picture4em.png"]http://img207.imageshack.us/img207/9728/411948picture4em.png[/url]

Pecan

Quote from: Michael on April 01, 2006, 08:21:09 PM
Quote from: Pecan on April 01, 2006, 08:12:54 PM
CB is running on 1.62 scintilla. What other version of scintilla are behaving correctly on GTK? That ought to give us a clue.

May be wxScintilla 1.68 would solve the problem.

Best wishes,
Michael


I looked over the bug list at http://scintilla.sourceforge.net/ScintillaHistory.html
and found nothing about the bug. Disappointing....


mikeandmore

confirm wxsintilla 1.67 also have this bug.(the sample program)

Allefant

I'm also seeing this, also filed a bug report about it: https://developer.berlios.de/bugs/?func=detailbug&bug_id=6884&group_id=5358

So, seems the reply in the bug report that a newer WX fixes it was just a guess? I wonder if the WxScintilla devs know about it..

Michael

Quote from: Allefant on April 03, 2006, 01:16:55 AM
[...]I wonder if the WxScintilla devs know about it..

Hello,

you can also try to post a bug report there.

Best wishes,
Michael
[url="http://img207.imageshack.us/img207/9728/411948picture4em.png"]http://img207.imageshack.us/img207/9728/411948picture4em.png[/url]