PointCloudLibrary / PointCloudLibrary/pcl

request resources in use error when using qvtkwidget on windows.

Open
#1,896 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: stale
Dominant language
C++
Stars
11.1k
Forks
4.7k
Avg merge
4d 10h
Merged PRs (30d)
6

Description

⚠️ This is a issue tracker, please use our mailing list for questions: www.pcl-users.org. ⚠️

Your Environment

  • Operating System and version: Windows 10
  • Compiler: Visual studio 2015
  • PCL Version: 1.8.0

Current Behavior

In the for loop, many calls of addText3D method leads the error, "the requested resources in use".
The problem was raised when using qvtkwidget on windows.

Possible Solution

The multiple addText3D calls are suspected. So, I removed/comment Render() of vtk renderer, which seems to request redraw entire scene. And the error disappeared.
I think it is unnecessary to redraw for the case of many addText3D calls.

Simple solution: In pcl_visualizer.cpp,
renderer->Render ();
=>
//renderer->Render ();

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in pcl_visualizer.cpp and trace the for-loop calls to addText3D and the renderer->Render() call when using QVTKWidget on Windows. Reproduce the resource-in-use error with the stated Windows 10, Visual Studio 2015, and PCL 1.8.0 environment, then verify the redraw behavior and confirm the error no longer occurs without breaking visualization updates.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-vision
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.