View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0015765 | VTK | (No Category) | public | 2015-10-09 11:54 | 2016-08-12 09:55 | ||||
Reporter | Luc Habert | ||||||||
Assigned To | Sankhesh Jhaveri | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0015765: OpenGL2: context clashes | ||||||||
Description | When an actor is removed from a renderer, the renderer calls the actor's ReleaseGraphicsResources which ends up deleting array objects whose opengl handles are context-specific. Therefore, the window should be made current beforehand, otherwise another window's objects will be affected. AFAIK, the documentation does not require calling MakeCurrent before removing an actor. I think it should either be made explicit, or RemoveViewProp should call MakeCurrent itself. Ideally, the previous current context should be restored upon exiting RemoveViewProp (*). Another instance of the same problem: calling vtkWin32OpenGLRenderWindow::Finalize will destroy the context. If the ReleaseGraphicsResources haven't been called first, they will when called affect an unintended context. (*) BTW: MakeCurrent is called from some places deep in the code (eg vtkWindowToImageFilter, vtkTextureObject::ReleaseGraphicsResources). I believe they should restore the previous context, or all hell could break loose in corner cases, like a vtkWindowToImageFilter used as input to a mapper in a different context. | ||||||||
Tags | No tags attached. | ||||||||
Project | TBD | ||||||||
Type | incorrect functionality | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0035276) Luc Habert (reporter) 2015-10-12 14:35 |
> calling vtkWin32OpenGLRenderWindow::Finalize will destroy the context. If the ReleaseGraphicsResources haven't been called first, they will when called affect an unintended context My bad, graphics releases are actually released after a make current during this call. |
(0036240) Sankhesh Jhaveri (manager) 2016-07-06 16:40 |
The following merge request fixes the issue: https://gitlab.kitware.com/vtk/vtk/merge_requests/1636 [^] |
(0037421) Kitware Robot (administrator) 2016-08-12 09:55 |
Resolving issue as `moved`. This issue tracker is no longer used. Further discussion of this issue may take place in the current VTK Issues page linked in the banner at the top of this page. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-10-09 11:54 | Luc Habert | New Issue | |
2015-10-12 14:35 | Luc Habert | Note Added: 0035276 | |
2016-07-06 16:40 | Sankhesh Jhaveri | Assigned To | => Sankhesh Jhaveri |
2016-07-06 16:40 | Sankhesh Jhaveri | Note Added: 0036240 | |
2016-07-06 16:40 | Sankhesh Jhaveri | Status | backlog => gerrit review |
2016-08-12 09:55 | Kitware Robot | Note Added: 0037421 | |
2016-08-12 09:55 | Kitware Robot | Status | gerrit review => closed |
2016-08-12 09:55 | Kitware Robot | Resolution | open => moved |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |