Page MenuHome

Blender compositor infinite "Cancelling..." Loop
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1070 & GTX 970

Blender Version
Broken: version: 2.80 (sub 59), branch: master, commit date: 2019-04-26 06:00, hash: rB513b71c89ad0

Short description of error
When I tweak something in the compositor, it won't update and the loading bar shows "Cancelling..." While the bar itself repeatedly fills and resets. This happened in 2.79 as well.

Exact steps for others to reproduce the error

  1. Open file
  2. Render image (only takes like 2 minutes)
  3. Tweak something in compositor

I wish I could figure out what steps actually cause this because everything seems to work fine until one second it doesn't. When it happens there doesn't seem to be a way to fix it, meaning the file is now broken.

I also remember running into this same type of issue in the past when I plugged an "Mat Index," value into the compositor output once.



Event Timeline

Sebastian Parborg (zeddb) triaged this task as Needs Information from User priority.

Could you try to strip down the example file a little? It is quite big as it is and I suspect that you probably can make it much smaller.

Here is a smaller version of the file, but after experimenting I don't think it will help all that much.

Further details:

  • The issue occurs from the moment the file is opened
  • The file was created in 2.79, and the issue persists when it's opened in 2.8
  • When the file is opened on another windows machine (both 2.79 and 2.8) the error does not occur.
  • I can't figure out a reliable way to reproduce this error from a clean file. While it's happened to me before it seems to happen at random. I will try experimenting and see what I can do to reliably reproduce this bug, but I have a feeling my chances are slim.

I can't reproduce the issue on my end with that fine.

Does it happen if you use factory defaults or remove the 2.80 configuration directory (in your user home folder)?
%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\2.80\

Zach Hixson (zachThePerson) claimed this task.

Ok, after doing "blender --factory-startup" and enabling addons one by one, it seems like a bug with Animation Nodes. What was throwing me off was something very similar to this happened before I installed Animation Nodes, so I didn't think of checking it this time.

Problem solved, I will post this bug on Animation Nodes bug tracker. Changing status to "resolved"