Skip to content
This repository has been archived by the owner on Sep 1, 2021. It is now read-only.

Segfault when copying molecule #336

Closed
cryos opened this issue Apr 16, 2009 · 3 comments
Closed

Segfault when copying molecule #336

cryos opened this issue Apr 16, 2009 · 3 comments

Comments

@cryos
Copy link
Owner

cryos commented Apr 16, 2009

Reproduce:

  1. Build molecule
  2. Select all
  3. Copy
  4. Paste
  5. Click anywhere inside the GL widget.

This is on kubuntu jaunty with threaded gl enabled. Backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb6476710 (LWP 1546)]
0xb6de7027 in XQueryExtension () from /usr/lib/libX11.so.6
(gdb) backtrace
#0 0xb6de7027 in XQueryExtension () from /usr/lib/libX11.so.6
#1 0xb6ddb631 in XInitExtension () from /usr/lib/libX11.so.6
#2 0xb6eb3d6f in XextAddDisplay () from /usr/lib/libXext.so.6
#3 0xb78c0a25 in ?? () from /usr/lib/libGL.so.1
#4 0xb78c0b3f in ?? () from /usr/lib/libGL.so.1
#5 0xb78bf0b5 in glXMakeCurrentReadSGI () from /usr/lib/libGL.so.1
#6 0xb78bf473 in glXMakeCurrent () from /usr/lib/libGL.so.1
#7 0xb79ce751 in QGLContext::doneCurrent () from /usr/lib/libQtOpenGL.so.4
#8 0xb799471a in QGLWidget::doneCurrent () from /usr/lib/libQtOpenGL.so.4
#9 0xb6a9677a in Avogadro::GLWidget::hits (this=0x8b7fb30, x=188, y=172, w=9, h=9) at /usr/src/avogadro/libavogadro/src/glwidget.cpp:1712
#10 0xb6a96d8b in Avogadro::GLWidget::computeClickedPrimitive (this=0x8b7fb30, p=@0xbfe28fa8) at /usr/src/avogadro/libavogadro/src/glwidget.cpp:1760
#11 0xb6a99086 in Avogadro::GLWidget::mousePressEvent (this=0x8b7fb30, event=0xbfe28f98) at /usr/src/avogadro/libavogadro/src/glwidget.cpp:1129
#12 0xb704fcd6 in QWidget::event () from /usr/lib/libQtGui.so.4
#13 0xb799799c in QGLWidget::event () from /usr/lib/libQtOpenGL.so.4
#14 0xb6a99284 in Avogadro::GLWidget::event (this=0x8b7fb30, event=0xbfe28f98) at /usr/src/avogadro/libavogadro/src/glwidget.cpp:1124
#15 0xb6ff8f2c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#16 0xb7001ba1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb6cc0a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#18 0xb7000c0e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#19 0xb7070a0e in ?? () from /usr/lib/libQtGui.so.4
#20 0xb706fd37 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#21 0xb709acfa in ?? () from /usr/lib/libQtGui.so.4
#22 0xb65cfb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb65d30eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb65d3268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb6cec438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb709a3f5 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb6cbf06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb6cbf4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0xb6cc1959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0xb6ff8da7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#31 0x080741c4 in main (argc=1, argv=0xbfe29b34) at /usr/src/avogadro/avogadro/src/main.cpp:186

Reported by: @dlonie

@cryos
Copy link
Owner Author

cryos commented Apr 16, 2009

I currently get segfaults even attempting to run threaded GL on Linux. So I cannot test. I will say that this code has been quite neglected in recent months and may not give us the pay offs that we initially hoped for. It looks like cleverer rendering and GLSL would likely net us more and be more compatible. Is anyone actively developing using these code paths?

Original comment by: @cryos

@cryos
Copy link
Owner Author

cryos commented Apr 16, 2009

Disabling threaded gl did fix the problem.

Original comment by: @dlonie

@cryos
Copy link
Owner Author

cryos commented May 16, 2009

I'm going to mark this closed. I think threaded GL has a bunch of bugs, and we're just not going to support it for the 1.0 release. (I'm going to create a master feature request to "support threaded GL for post-1.0 releases."

Original comment by: @ghutchis

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants