OpenCL Compositing Bug #37832

Closed
opened 2013-12-16 16:32:49 +01:00 by Paul B. · 27 comments

{F41577}System Information
Windows 7 Professional x64, nVidia Geforce GTX 660

Blender Version
Broken: Blender 2.69 r60995, daily buid 2.69-740c7e6
Worked: Don't Know

Short description of error
On rendering any scene using the "Defocus" node some parts of the image that should be blurred aren't when OpenCL is checked{F41623}.

Exact steps for others to reproduce the error
Just hit render.

{[F41577](https://archive.blender.org/developer/F41577/opencl_bug.png)}**System Information** Windows 7 Professional x64, nVidia Geforce GTX 660 **Blender Version** Broken: Blender 2.69 r60995, daily buid 2.69-740c7e6 Worked: Don't Know **Short description of error** On rendering any scene using the "Defocus" node some parts of the image that should be blurred aren't when OpenCL is checked{[F41623](https://archive.blender.org/developer/F41623/opencl_bug.blend)}. **Exact steps for others to reproduce the error** Just hit render.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @Paul.Brachmann

Added subscriber: @Paul.Brachmann

Added subscribers: @Jeroen-Bakker, @monique

Added subscribers: @Jeroen-Bakker, @monique

Added subscriber: @maxint

Added subscriber: @maxint

Added subscriber: @cdog

Added subscriber: @cdog
Member

Hi paulb

Just some questions and checks:

  1. What resolution are you rendering in? (widthheightpercentage)
  2. Have you tried different tile sizes?
  3. What NVidia driver version are you working on?

Best regards,
Jeroen

Hi paulb Just some questions and checks: 1. What resolution are you rendering in? (width*height*percentage) 2. Have you tried different tile sizes? 3. What NVidia driver version are you working on? Best regards, Jeroen
Author

Hi jbakker

Thanks for your interest.

  1. I'm rendering in 1080p (19201080100%).
  2. Yes, I tried every tile size available but they all didn't work on my machine.
  3. The driver changed over the time of the tests (I have "GeForce Experience" installed so my driver is updated automatically) but at the moment I use the "GeForce R331 Game Ready Driver" Version 331.82.

One last thing: What's really strange is that when I recompose (shortcut: c) it sometimes works as expected and sometimes not (without changing anything in the scene or node-setup).

Hi jbakker Thanks for your interest. 1. I'm rendering in 1080p (1920*1080*100%). 2. Yes, I tried every tile size available but they all didn't work on my machine. 3. The driver changed over the time of the tests (I have "GeForce Experience" installed so my driver is updated automatically) but at the moment I use the "GeForce R331 Game Ready Driver" Version 331.82. One last thing: What's really strange is that when I recompose (shortcut: c) it sometimes works as expected and sometimes not (without changing anything in the scene or node-setup).

Added subscribers: @LukasTonne, @Sergey

Added subscribers: @LukasTonne, @Sergey

@LukasTonne, maybe you've got clues here?

@LukasTonne, maybe you've got clues here?
Member

Might be related to #38011, at least this skipping of later chunks (when starting in the middle) seems to indicate that. I think we have a problem in the compo scheduler ...

Might be related to #38011, at least this skipping of later chunks (when starting in the middle) seems to indicate that. I think we have a problem in the compo scheduler ...
Member

@Paul.Brachmann could you make a test file and attach it here? Neither @Sergey nor i could reproduce this bug so far.

@Paul.Brachmann could you make a test file and attach it here? Neither @Sergey nor i could reproduce this bug so far.
Author

I think I actually did upload the test file with the original description but here is it (again).

I think I actually did upload the test file with the original description but here is it (again).
Member

Thanks. I still can't reproduce the error with that file, but i did get a couple of OpenCL error messages (can't tie them to anything specific):

  • "CUDA cuInit: Out of memory"
  • " childs per node: 0/0 = -nan" with N between 0 and 15

This looks to me as if the OpenCL device is running out of memory, but i have to investigate this more. Given that i also have a GTX 660 this is a bit strange.

Thanks. I still can't reproduce the error with that file, but i did get a couple of OpenCL error messages (can't tie them to anything specific): * "CUDA cuInit: Out of memory" * "<N> childs per node: 0/0 = -nan" with N between 0 and 15 This looks to me as if the OpenCL device is running out of memory, but i have to investigate this more. Given that i also have a GTX 660 this is a bit strange.
Author

Hi @LukasTonne,
as far as I know there are different memmory configurations of the GTX 660 available.
You may have a different one than I have. I also mentioned that sometimes it works and sometimes not.
I don't know why this happens but it could be that you just had (bad-)luck an it worked.

Hi @LukasTonne, as far as I know there are different memmory configurations of the GTX 660 available. You may have a different one than I have. I also mentioned that sometimes it works and sometimes not. I don't know why this happens but it could be that you just had (bad-)luck an it worked.

I actually also encountered this bug. I have an AMD Radeon HD 6500M/5600/5700 Series . I suspect the defocus node is the cause, because it occurred when I used it. But it's not easily reproducible. I rendered an animation and most of the frames were fine, but several had this exact error.

I actually also encountered this bug. I have an AMD Radeon HD 6500M/5600/5700 Series . I suspect the defocus node is the cause, because it occurred when I used it. But it's not easily reproducible. I rendered an animation and most of the frames were fine, but several had this exact error.

Added subscriber: @MichaelParucha

Added subscriber: @MichaelParucha

I can also reproduce the error (Windows 7 64bit, NVIDIA GeForce GTX 760 2 GB, latest driver).

I can also reproduce the error (Windows 7 64bit, NVIDIA GeForce GTX 760 2 GB, latest driver).
Sergey Sharybin self-assigned this 2014-02-04 11:16:41 +01:00

Managed to reproduce using NVidia video card on windows. Seems i'm the only one developer wjo managed to reproduce it so assiginig to self :)

Managed to reproduce using NVidia video card on windows. Seems i'm the only one developer wjo managed to reproduce it so assiginig to self :)
Member

The culprit is here:
https://developer.blender.org/diffusion/B/browse/master/source/blender/compositor/operations/COM_VariableSizeBokehBlurOperation.cpp;7aa86ec243f92cee6f5de040f989fc7779f0e5a1$200

The sizeMemoryBuffer doesn't seem to be fully defined, it returns bogus values for the chunks in question, which leads to invalid results of the defocusKernel OpenCL code.

Have been trying all day to get my head around how the synchronization between OpenCL and CPU work packages is achieved, but this is really confusing code ...

The culprit is here: https://developer.blender.org/diffusion/B/browse/master/source/blender/compositor/operations/COM_VariableSizeBokehBlurOperation.cpp;7aa86ec243f92cee6f5de040f989fc7779f0e5a1$200 The `sizeMemoryBuffer` doesn't seem to be fully defined, it returns bogus values for the chunks in question, which leads to invalid results of the `defocusKernel` OpenCL code. Have been trying all day to get my head around how the synchronization between OpenCL and CPU work packages is achieved, but this is really confusing code ...
Sergey Sharybin removed their assignment 2014-03-27 09:50:04 +01:00
Jeroen Bakker was assigned by Sergey Sharybin 2014-03-27 09:50:04 +01:00

Re-assigning to @Jeroen-Bakker, hopefully he'll have more clues here.

Re-assigning to @Jeroen-Bakker, hopefully he'll have more clues here.
Member

Added subscriber: @JulianEisel

Added subscriber: @JulianEisel
Member

@Jeroen-Bakker, found any time to look into this?

@Jeroen-Bakker, found any time to look into this?

Added subscriber: @mano-wii

Added subscriber: @mano-wii

This bug is intriguing. It seems simple. But no one solved in 2 years

Edit: In the latest builds seems to have been SOLVED.

Edit2: No, now the image resolution must be 3840x2160 for the problem to can be seen.

This bug is intriguing. It seems simple. But no one solved in 2 years Edit: In the latest builds seems to have been SOLVED. Edit2: No, now the image resolution must be 3840x2160 for the problem to can be seen.
Member

Just for the clarity.

I would take effort to fix this, if I can reproduce it on one of my machines.

Just for the clarity. I would take effort to fix this, if I can reproduce it on one of my machines.
Jeroen Bakker was unassigned by Julian Eisel 2015-03-08 19:34:05 +01:00
Sergey Sharybin was assigned by Julian Eisel 2015-03-08 19:34:05 +01:00
Member

Quite frustrating to see that this still isn't resolved. @Sergey, maybe you could have another look as Jeroen isn't able to recreate?

Quite frustrating to see that this still isn't resolved. @Sergey, maybe you could have another look as Jeroen isn't able to recreate?

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#37832
No description provided.