View Single Post
Old 04-19-2018, 08:55 AM   #9
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,558
Karma: 5703586
Join Date: Nov 2009
Device: many
The only thing of interest in the backtrace is that both a mousepress event that will move the selected tab to the front, and at the exact same time a mousemove event happens on the same tab. This initiates a Tab drag and drop event and which is what causes the segfault deep inside Qt.

There really is not much to go on as to why this segfault occurs since it is deep inside Qt's code. Were you able to generate any other crash reports? If not, please try to intentionally cause a crash with by playing around with a copy of an epub until it crashs again and then save that crash report just to make sure the cause is simply not corrupted memory.

I never drag and drop tabs in the Tab bar, so I will give that try to see if I can recreate what you are seeing.

KevinH

Last edited by KevinH; 04-19-2018 at 11:04 AM.
KevinH is offline   Reply With Quote