This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 915094 - ParaView hangs when toggling color legend
ParaView hangs when toggling color legend
Product: Fedora
Classification: Fedora
Component: paraview (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Orion Poplawski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-02-24 14:20 EST by Arno Mayrhofer
Modified: 2013-02-24 18:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-24 18:28:22 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Arno Mayrhofer 2013-02-24 14:20:54 EST
Description of problem:

When toggling the color legend ParaView hangs and uses 100% of the CPU

Version-Release number of selected component (if applicable): 3.98.0-enhanced 64-bit

How reproducible:

Steps to Reproduce:
1. open pv
2. create box
3. choose "Normals" as colouring mode
4. press "Toggle color legend visibility" button
Actual results:

pv hangs

Expected results:

pv displays color legend

Additional info:

When starting pv from console I get the following message:

  X Error: GLXBadRenderRequest 176
  Extension:    153 (Uknown extension)
  Minor opcode: 1 (Unknown request)
  Resource id:  0x6

Let me know if I can provide any further information and I'll happily do so.

Comment 1 Orion Poplawski 2013-02-24 14:31:19 EST
Can you try to reproduce with 3.98.1 from updates-testing?
Comment 2 Arno Mayrhofer 2013-02-24 15:14:04 EST
Exactly the same issue.
Comment 3 Arno Mayrhofer 2013-02-24 15:40:54 EST
The same happens when I press "Edit color map", except that Resource id is then 0x1
Comment 4 Arno Mayrhofer 2013-02-24 17:03:27 EST
Okay I got it. I tried to get a game running this afternoon and for some reason installed the AMD catalyst drivers. Now this one was called when rendering some Freetype stuff and it failed. This in turn triggered a chain reaction of X wanting to process this error which eventually got stuck. Installing debuginfo and running it through gdb gave me:

#0  0x00000032f104329b in _XReply () from /lib64/
#1  0x00000032f1039886 in XQueryTree () from /lib64/
#2  0x00000032f865a340 in QWidgetPrivate::updateFrameStrut() () from /lib64/
#3  0x00000032f860c25b in QWidgetPrivate::frameStrut() const () from /lib64/
#4  0x00000032f860c555 in QWidget::x() const () from /lib64/
#5  0x00000032f8a7f3e4 in QDialog::adjustPosition(QWidget*) () from /lib64/
#6  0x00000032f8a7f7ab in QDialog::setVisible(bool) () from /lib64/
#7  0x00007ffff710ab07 in show (this=0xb10ce0) at /usr/include/QtGui/qwidget.h:494
#8  pqOutputWindow::onDisplayErrorText (this=0xb10ce0, text=...) at /usr/src/debug/ParaView-3.98.1-source/Qt/Core/pqOutputWindow.cxx:149
#9  0x00000032f018cebf in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /lib64/
#10 0x00007ffff7164925 in pqOutputWindowAdapter::displayErrorText (this=<optimized out>, _t1=...) at /usr/src/debug/ParaView-3.98.1-source/fedora/Qt/Core/moc_pqOutputWindowAdapter.cxx:115
#11 0x00007ffff710937c in pqOutputWindowAdapter::DisplayErrorText (this=0xb0e1a0, text=<optimized out>) at /usr/src/debug/ParaView-3.98.1-source/Qt/Core/pqOutputWindowAdapter.cxx:91
#12 0x00000032f00714de in qt_message_output(QtMsgType, char const*) () from /lib64/
#13 0x00000032f00716e8 in qt_message(QtMsgType, char const*, __va_list_tag*) () from /lib64/
#14 0x00000032f0071e34 in qWarning(char const*, ...) () from /lib64/
#15 0x00000032f8632c30 in qt_x_errhandler () from /lib64/
#16 0x00000032f1045556 in _XError () from /lib64/
#17 0x00000032f10427a1 in handle_error () from /lib64/
#18 0x00000032f10427e5 in handle_response () from /lib64/
#19 0x00000032f10433d8 in _XReply () from /lib64/
#20 0x00007fffe72f7039 in ?? () from /usr/lib64/catalyst/
#21 0x00007fffed3837e6 in ConvertGlyph (context=0x0, this=0x2ed2d80) at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTPixmapGlyph.cpp:60
#22 ftgl::FTPixmapGlyph::ConvertGlyph (this=0x2ed2d80, context=0x0) at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTPixmapGlyph.cpp:23
#23 0x00007fffed3836a6 in ftgl::FTPixmapGlyph::Render (this=0x2ed2d80, pen=..., context=<optimized out>) at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTPixmapGlyph.cpp:145
#24 0x00007fffed383214 in ftgl::FTGlyphContainer::render (this=0x2ee9920, index=<optimized out>, next=0, pen=..., context=0x0)
    at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTGlyphContainer.cpp:65
#25 0x00007fffed382829 in ftgl::FTFont::doRender (this=this@entry=0x2edf9a0, chr=49, nextChr=0, context=context@entry=0x0) at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTFont.cpp:288
#26 0x00007fffed382926 in ftgl::FTFont::render (this=0x2edf9a0, string=<optimized out>, context=0x0) at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTFont.cpp:258
#27 0x00007fffed382d3d in ftgl::FTGLPixmapFont::RenderOpenGL (this=0x2edf9a0, string=0x2ed2bf0 <Address 0x2ed2bf0 out of bounds>, context=0x0)
    at /usr/src/debug/ParaView-3.98.1-source/VTK/ThirdParty/ftgl/src/FTGLPixmapFontRenderOpenGL.cpp:29
#28 0x00007ffff0bb245c in vtkOpenGLFreeTypeTextMapper::RenderOverlay (this=0x2ed2330, viewport=<optimized out>, actor=<optimized out>)
    at /usr/src/debug/ParaView-3.98.1-source/VTK/Rendering/FreeTypeOpenGL/vtkOpenGLFreeTypeTextMapper.cxx:396
#29 0x00007fffeb92454c in vtkActor2D::RenderOverlay (this=0x2ed6c50, viewport=0x16c4930) at /usr/src/debug/ParaView-3.98.1-source/VTK/Rendering/Core/vtkActor2D.cxx:122
#30 0x00007ffff264bfd3 in vtkPVScalarBarActor::RenderOpaqueGeometry (this=0x2e5f9e0, viewport=0x16c4930) at /usr/src/debug/ParaView-3.98.1-source/ParaViewCore/VTKExtensions/Rendering/vtkPVScalarBarActor.cxx:308

which clearly identifies the problem to be in the catalyst driver. Now uninstalling it removed the issue. Next time I will need to take more care when following tutorials. Cheers for the help Orion.

Note You need to log in before you can comment on or make changes to this bug.