Development version occasionally crashes while editing schema (Page 2 of 3)

Great
Tomorrow i will run 4740 some hour in qtdesigner debug mode

That commit fix only crash on diagram editor when you select all components in a area with mouse for deleting and provoke in the GraphicScene artefact like conductors and basic shapes ghosts elements.

GREAT
it was really a nasty bug!

https://svnweb.tuxfamily.org/log.php?re … dir=1&

or

https://listengine.tuxfamily.org/lists. … y.org/qet/

1) Tanks tor changelog links.

2) For bug tracking i agree not close until confirmed, but IMO it is good practice to update issues with a short note like
"we now made this change, see changelog URL xxx, hope it helps but not certain, so leaving bug open for a while"

3) Oops, i forgot to twist my fingers!

Running r4748 in qtcreator debug

I know that i never did a group delete this time.
I may have deleted some element.
I know i have deleted some conductors, especially the inferior one.

See image: at bottom there is a fat black conductor.  I never made it fat.  It was a normal default thin connector.  A while after i had group moved some elements around that conductor, i noticed the conductor right vertical part was touching the dotted oval, so I grabbed that part and dragged it left.

But it did not follow nicely, instead the top part was still sticking out at right like in the picture.  I then deleted it and made a new.  At that time it looked like old one was gone, and only the new one visible (In this screen-shot you see the right vertical part of the new conductor slightly left of the old (fat) ghost conductor.

The old ghost get visible when i select the area.

Then i realised it may be this bug again, saved and yes it crashed.

No source file visible, just disassembler.

qtcreator "Application output" window displays:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 34898, resource id: 43994263, major code: 40 (TranslateCoords), minor code: 0

...And then saves and exports every page, then:

pure virtual method called

terminate called without an active exception

EDIT: that code formatting function in this forum posting is a bit buggy, at least here on current Firefox... /EDIT

EDIT2: That ghost line shows in image exactly like when hoovering mouse over a conductor, but this is without hoovering the mouse over that ghost.  /EDIT2

I can confirm that the "ghost conductor" bug is not fixed   .
I got it for 10min with v0.51 svn4748 while I'm drawing schematics for a new CNC-machine.

HOORAY
By this method i can make it crash quickly and repeatable
https://qelectrotech.org/bugtracker/view.php?id=107

@Nuri

1) Strange! I repeat it every time, also with slight change in procedure, and also trying to follow you exactly (you use slight different position of valve and deselect conductor before drawing new - also when i do that here it fouls up.  What QET version, Qt, version etc.. do you compile locally?  Other difference?  My system is described @bug 107.

If you find some method to repeat the fault (any file or procedure) i will try here.

2) Regarding the sloped conductor i think it is a variant of bug 105 i reported, and i can repeat that exactly like you on this drawing too.   - could you add a comment and link to this video there please?   This .qet is a sister clone of what i used for that bug.  The pump from where the conductor is slanted is the same home-made .element.  I wonder if there is some oddness about it, like unusual placement of connector?

@developers

The bug behaves differently on different systems despite using same svn, and same file and procedure.
(i can repeat also on 4751, both standalone compiled and when running in debug mode from QtCreator)

So bug is dependant on build environment and/or where it executes.

If you want to try changing something i can try here immediately to see if it makes a difference.
Maybe there is some optimisations that can be switched off, or forcing to use more rigid but slowing options in compile?
Do it really initialise everything needed, always?
Or you maybe can flip some compile settings?
Or can you put in some kind of trap or logging feature explicitly to trap what happens when I perform the operations that trig the problem i see here when i follow the procedure described in the bug?

and with basic shapes too!

I have not seen that... yet... i think.
You mean when deleting lines, rectangles etc in schema editor, they have happened to become "ghosts"?

Revision: 4752
Author:   blacksun
Date:     2016-10-20 14:35:44 +0200 (Thu, 20 Oct 2016)
Log Message:
-----------
Probably fix the fucking crash of ghost conductor.