To test this feature, visit your live site.

Having plugins installed may be causing crashes?

I am trying to to figure this out, but I have been rarely got able to render pics using crowdrender because the secondary node I have (a ubuntu machine with a gtx 1080) crashes as soon as I press "render"

followed the documentation to render still images, but load balancing only shows my local machine unless I hit render on local and cancel the render then I can see my secondary node, plus, sync never really succeeds, it always says "sync failed" or "repairing X_Material" or "IK", I have all my resources packed in the files and both machines are running Blender 3.1 (the version I currently use for most of my work)

I attach a cr_log, I am starting to think having addons installed might have something to do with the crashes, I just find weird yesterday I was able to render flawlessly on both machines having manual load of .85/1 and now only local appears to render and my secondary node pushes a crash message on my mac

12 comments

12 Comments

James Crowther

Aug 09, 2022

Ok, found this, its something to try

/var/folders/wg/r4n5x_0n0_gcbggjzgpphdnh0000gn/T/blender.crash.txt

you had a crash dump file, it might be gone, but if the same thing happens, take a look and search for "crash.txt" in your /var/folders location.

another thing was this, python reported a crash, but it was from another addon

Fatal Python error: Segmentation fault

Current thread 0x00007000061a1000 (most recent call first):
  File "/Users/Drigo/Library/Application Support/Blender/3.1/scripts/addons/cats-blender-plugin-master/tools/common.py", line 2144 in toggle_mmd_tabs
  File "/Users/Drigo/Library/Application Support/Blender/3.1/scripts/addons/cats-blender-plugin-master/tools/common.py", line 2119 in toggle_mmd_tabs_update
  File "/Users/Drigo/Library/Application Support/Blender/3.1/scripts/addons/cats-blender-plugin-master/tools/settings.py", line 222 in apply_settings
  File "/Users/Drigo/Library/Application Support/Steam/steamapps/common/Blender/Blender.app/Contents/Resources/3.1/python/lib/python3.10/threading.py", line 946 in run
  File "/Users/Drigo/Library/Application Support/Steam/steamapps/common/Blender/Blender.app/Contents/Resources/3.1/python/lib/python3.10/threading.py", line 1009 in _bootstrap_inner
  File "/Users/Drigo/Library/Application Support/Steam/steamapps/common/Blender/Blender.app/Contents/Resources/3.1/python/lib/python3.10/threading.py", line 966 in _bootstrap

charmandrigo

Aug 11, 2022

Replying to

Ok never mind, it crashed, but strangely it crashed over a packing file error (some textures not found on my folders which I usually dismiss), the message and crash appeared right after clicking Sync on my secondary node.

The crash of the addon is persistent even if I close and reopen Blender on factory-startup, the addon still is unresponsive. I mean, it loads, I can see the crowdrender options on the render tab but nothing responds, adding a new node but trying to connect to it does nothing, not even a status message, the name remains gray, my cloud account doesn't let me log in, can type my credentials but the login button does nothing.

Blender info.log shows only this:

I will attach the current cr_log, I don't know what could be this time, the crash can happen even if I click anywhere on the CR options, nodes appear as "ready" and suddenly go all gray without any error warning on the info.log

James Crowther

Aug 11, 2022

Replying to

Thanks, maybe try turning auto pack off, we fixed a bug related to auto pack a while back, and your version of the addon definitely has that fix, so a bit puzzled if that is the cause, still, please test with autopack disabled, if it stops crashing then at the very least that lets me know where to look for the problem.

charmandrigo

Aug 11, 2022

Replying to

Same result, this time happened after I stopped a render because my secondary node got stuck on 38%, cancelled the render, tried to resync and crashed

James Crowther

Aug 09, 2022

Thanks for letting us know, having a look at the logs you posted :)

charmandrigo

Aug 09, 2022

a bit of an update but I have installed some more addons mostly to create landscapes and libraries, it often crashes the addon after making one render, all my nodes get grayed out and it appears to log me off the "My Cloud Account", adding my credentials does nothing, restarting blender does not help, only thing that works is rebooting my mac to get the addon working again.

Is there a list of addons that can potentially break crowdrender?

James Crowther

Sep 06, 2022

Replying to

Not a list as such, but you can try starting Blender in factory startup mode. You can do this pretty easily by pressing cmd + space and then typing "terminal"

then enter the following

cd /Users/Drigo/Library/Application Support/Steam/steamapps/common/Blender/Blender.app/Contents/MacOs

and then

./Blender -b --fatory-startup

this will start Blender with all the addon's disabled. You can then enable Crowdrender and try to recreate the crash. If it still happens, then you can be sure its not another addon you have installed.

If it no longer crashes, then its likely another addon, happy to look into it either way. Also, make sure you can reproduce the crash reliably. If there's a sequence of steps that usually causes the crash, try to write these down and be certain that they can force the crash.

Without a reliable process to recreate the crash, its super hard to fix. About as hard as asking a building to repair a hole in the wall that isn't there to be honest. Can't fix the problem if it doesn't happen.

charmandrigo

Jul 29, 2022

Could be also have something to do with the docker container? I was again able to render after stopping and removing the container via ssh and install it again, I have used parameters such as "-d --restart unless-stopped" so the nodes start on boot without having to get into ssh

Support Crowdrender!

Having plugins installed may be causing crashes?

Terms of use

Privacy Policy