Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "Curves sculptmode: Slide tool with Pressure Sensitivity always resets at the end of the stroke\nOperating system: Linux-5.18.16-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0 Beta\n\nCurves will snap back to it's original coordinates after the stroke. Turning off the pressure sensitivity will allow the hair curves to stay.\n\n*Use a pentablet or a screen display with pressure sensitivity*\n - Load Factory Settings\n - Go to 3D Viewport\n - Add mesh primitive\n - Add curve hair object while mesh primitive is active\n - Go to sculpt mode\n - Add some hair with the [**Add**] tool\n # Slide hair with the [**Slide**] tool\n\n----\n**Pentablet:** XP-Pen Deco 01 V2\n\n", "Sculpt brush with texture breaks sculpt tiling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.93.0 Alpha\n\nIf the sculpt brush has a texture enabled with mapping set to *Area Plane*, then tiled strokes break up and do not match properly at the seams.\nIn this example the original stroke is on the right.\n\n\n1 Add texture to a brush\n2 Set mapping to area plane\n3 Enable tiling in the Symmetry drop-down menu\n4 Try sculpting at the seams\n\nOr use the file\n[tiling_bug.blend](tiling_bug.blend)\n\n", "Most sculpt tools do not work while model is animated\nLinux 64-bit\n2.93.2\nMost sculpt tools do not work as expected when the object is spinning like it's on a pottery wheel. Some tools like the clay tool work okay, but other tools like smooth and scrape do not. I think it has to do with the stroke method; the stroke accounts for screen space but not the local transform of the object if it's moving during a stroke. Video of my attempt here:\n[pottery.mp4](pottery.mp4)\nI made this as a joke and it looks like garbage, but unfortunately it went viral and everybody thinks it's a great idea so now more people are gonna try it and complain that it doesn't work. It's a valid workflow that you have to account for now apparently. I'm really sorry.\n - Open the attached file\n - Play the animation\n # Try to sculpt the thing while it spins\n[bowl.blend](bowl.blend)\n", "Line Art Thickness doesn't consider Render Resolution Percentage\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 620 Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.2\nBroken: version: 3.4.0 Alpha\nBroken\n\nWhen using Line Art Modifier, on a Grease Pencil Object in Screen Space Mode, Line Thickness doesn't scale with resolution as expected. \n\n1. Open new General Startup File\n2. Create New Object>Grease Pencil>Scene Line Art\n3. Under Object Data Properties>Strokes>Stroke Thickness and set to World Space\n4. Set Render Resolution % to a factor. line thickness will be different than expected\n\n\n\n\n\n", "bpy.ops.paint.image_paint with a texture requires initialization with manual paint stroke otherwise color not quite right\nWin 10 5820K GTX 970\n\n2.79b and latest daily build\n\nbpy.ops.paint.image_paint with slightly wrong colors when painting on object with texture on brush before a manual paint stroke applied\n\n1. Load attached file\n2. Run script\n3. With mouse over the cube - press space and type Simple Modal Operator to activate modal paint operator\n4. move mouse about to paint. \n5. left click to stop modal paint operator\n6. now paint on the cube normally by holding mouse button down\n7. you will see this is a slightly different color \n8. press space and type Simple Modal Operator to activate modal paint operator again\n9. move mouse around\n10. you should now see modal operator painting correctly\n\nThis seems to happen each time I change the texture on the brush to a new one (with obviously different colors on it)\n\nImage is attached showing this.\n\nPossibly something not being initialized properly?\n\nThanks you in advance for any work on this.\n\n[modal_paint.blend](modal_paint.blend)\n\n\n", "Multi-Object-Mode: EditMesh Vert/Edge Slide (transform) incorrect orientation for non active objects\nVert/Edge slide calculates the closest edge, then a screen space vector to move the cursor along to perform the slide.\n\nThis currently is only correct for the active object.\n\nIt's possible to have multiple objects rotated differently so the slide vector will be wrong on some objects.\n\nNote that performing vert/edge slide on multiple loops (while supported) is not all that common.", "New Dyntopo Functionality\nThese are the features planned after the new Dyntopo optimisations and features in #82121 are done. The idea is to fully support Dyntopo in all features that were introduced in the last 5 versions of Blender, while introducing some new features that only make sense with Dyntopo.\n\n- Make geometry undo steps compatible with Dyntopo for\n - Voxel/Quadriflow\n - Trimming tools\n - Delete Face Set\n - Mask Slice\n\n- Make mask extract work with dyntopo.\n- Add an option to skip dyntopo topology updates per brush\n- Detail Flood Fill by Face Set.\n- Make Trimming tools flood fill the new face set with dyntopo detail size.\n- Investigate a new algorithm for smooth that has consistent strength between different mesh densities.\n- Option to enable Dyntopo in Draw Sharp, Grab and Smooth (if possible, these brushes needs original coordinates).\n- Option for the cloth, pose and boundary brushes to update the topology of the deformed area after the action is finished.\n- Unify the detail size of dyntopo and voxel to make them generate detail at similar resolutions.\n- Make project gesture tools update the topology after the action, making them automatically collapse the highly deformed edges.\n- Face Set extrude tool (can be mode option of Face Set edit, but I would rather have a separate operator).\n- Mask by detail size tool.\n- Init Face Sets by detail size.\n- Detail flood fill to average detail size.\n- Face Set split option for the Face Set line gesture tool.\n- Geometry Eraser brush (investigate if it is possible to make it erase from the center of the mesh, not only from the silhouette boundaries).\n- Insert geometry brush.\n- Edit Dyntopo detail size operator \n- Make Dyntopo generate geometry based on Sculpt Vertex Colors instead of edge length (areas with more color detail will have more geometry)\n- Dyntopo simplify by Sculpt Vertex Colors\n \n", "Color space seems wrong while painting in image editor.\nIn the image editor add a new image and with default settings just do a red line paint over a green line paint.\nDark zone appear in the falloff between red and green. it should not be there and should stay clear, not dark. \nI don't know why, but it looks like a color space issue. \n\ndark falloff not ok in blender:\n\n\nclear falloff ok in gimp:\n\n\nblender 2.8\nWindows 7 \n\n\n", "Paint Mode: Masking Modes\nThis is an important task related to the implementation of Paint Mode and #96225.\n\n# Painting Modes & Selections\n\nIn the current painting modes there are various ways of masking. Including all of these in their current form in a single Paint Mode would lead to a muddled and confusing design.\nBut still, these ways of masking should be supported:\n\n- Masking per vertex (Like Sculpt Mode masking)\n- Masking per face (To achieve sharp edges on face corner color attributes and image textures)\n- Masking based on selection (Synched with edit mode)\n- Masking based on a texture (Stencil Mask)\n\n# Issue\n\nThese ways of masking are very different and currently implemented as completely separate features.\nMoving all of these with their current design to a new Paint Mode would lead to multiple masks and selections having to be enabled and managed at the same time, each with their own overlay.\nThis issue can already be observed in the current Texture Paint Mode when enabling any of the selection masking modes and stencil masking at the same time.\n\nThe ideal way moving forward in Paint Mode has to be by combining these masking methods into a single cohesive design without regression in functionality.\n\n# Proposal\n\n### Masking Modes\n\nThe proposal is to add three easily accessible “Masking modes” to choose which data is being used for the masking operations in Paint Mode.\nThese should be easy to switch between via the number keys. \nThis directly parallels the selection modes in edit mode, grease pencil and the UV editor. And just like in these other modes they should be interchangeably usable for intuitive and fast masking.\n\n\n\nThe 3 modes would let you:\n\n- **Mask Vertices** (Vertex float)\nSame behaviour as sculpt mode.\n\n- **Mask Faces** (Face bool)\nWill restrict the masking to only fill in entire faces as completely masked or unmasked. This is far more useful than trying to paint face float values, which will almost always result in a stepping effect.\n\n- **Mask Pixels** (Greyscale image texture))\nThis feature should replace the current “Stencil Mask”.\n\n### Converting Masks\n\nThese masking features are meant for loose and temporary masks, similar to selections in other modes. \nFor more permanent masking for material and texture mixing it would still be preferred to paint image textures and use them as masks in the material.\n\nWith that use case in mind, it would be easiest to implement to convert the mask to another domain and data type every time the masking mode is changed (Similar to selection modes in Edit Mode).\n\nAlternatively we could test a way of abstracting/propagating the selection between those modes but that could just end up as far more complicated, less predictable and for questionable advantages.\n\n### Edit Mode Syncing\n\nAn important task that is tied to this is to convert the mask of Paint Mode to the Edit Mode selection (and vise versa).\nThis way masks can be much more precisely created in Edit Mode.\nWhile switching between Edit Mode should not be required - masking in Paint Mode should be intuitive enough for most cases - some workflows rely on this for painting precise attributes and technical textures.\n\nSo keeping this functionality will be a priority!\n\n(There are even other potential advantages from considering a Paint Mode mask an Edit Mode selection, like assigning materials directly in Paint Mode. \nThe design of #97903 could help in making this more clear.\n\n# Sculpt Mode\n\nIf these masking modes should be included in Sculpt Mode as well is questionable. \nMasking faces and based on an image texture is no use if you are only able to affect vertices with all tools available.\nThe only advantage would be to avoid mask conversion on mode switching (Which shouldn't be a problem) and to allow painting face corner color attributes with the Sculpt Mode painting toolset (Which is not what Sculpt Mode is for. For sharper edges you should increase the amount of geometry or use the bigger Toolset of Paint Mode).", "Vertex Paint bug with Falloff Angle\nBroken: 2.79.x, Win32 & Mac\n\nSee video below.\n\nTo reproduce, set Falloff Angle to 45, and paint (one continuous stroke)\nwith the brush radius approximately equal to the object.\n\nAll by default (2D Falloff and Accumulate is OFF).\n\n[vertex-paint-falloff-angle-bug.blend](vertex-paint-falloff-angle-bug.blend)\n\n---\n\nSmall brush size is ok:\n\n\nIncreased size produces artifacts:\n\n\n---\n\n[vertex-paint-falloff-angle-bug.mp4](vertex-paint-falloff-angle-bug.mp4)", "Max brush radius is too small for 4k screens\nThe maximum brush radius (500 pixels) is too small when working on 4K monitors. Possible solutions:\n\n - Increase maximum to 1000. Not a generic solution and could make the radius slider less usable (Krita's radius slider suffers from this).\n - Scale brush radius by DPI. Need to investigate if the existing DPI can be used or if we need a separate one for the 3D viewport.\n", "Texture paint Backface culling option does not work if symmetry is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.1\nWorked: never since implemented in e2d60d180ed8 afaict\n\nWhile in the texture paint mode, the backface culling option of the brush is sometimes ignored, allowing painting onto backfaces. It only seems to affect certain objects. I could not discern why. See the attached blend file.\n\n1. Open attached blend file.\n2. Paint on the backfaces of the mesh; observe bug.\n3. Select cube\n4. Paint on the backfaces of the cube; observe no bug.\n\n", "Find solution to unify color picking methods with options for sample space\nReopened as, though the initial issue is invalid, the current solution, as it is, is problematic.\nThe sample_color paint operator {key S} has a problem with discoverability and is separate from both the general UI color picker and the sample tool. This needs a better design solution.\n\n**Old Description** (resolved by sample_color operator)\n\nRight now all color picking is using the display space, which usually makes it (almost) impossible to accurately pick colors from an image that is not sRGB for texture painting.\nSimilarly, for texture painting in the 3D viewport the picked color is that after shading and display transformation. This can be useful, but it should be optional. In a lot of cases the user wants to pick and draw a color from within the same image texture, without any additional color space conversion.\n\nThe View mode of the image editor already has a sample tool, which has the functionality to show the color data in image space without additional color management. So simply using this tool in paint mode for picking color with the option to select the color space would already be a huge benefit.\n\nFurther, having a similar tool for 3D texture painting would be even better, but I assume that this might have more difficult implications for the implementation. Tackling this for the image editor first using the Sample tool, might me a good trade-off for investing a small amount of work for maximum impact.\n\n[color_picker_behaviour-2021-03-02_15.50.34.mp4](color_picker_behaviour-2021-03-02_15.50.34.mp4)\n[non-color_picker.blend](non-color_picker.blend)", "Unify Interpolation In Vertex Paint And Sculpt Mode\nVertex paint squares colors when it interpolates, while the paint tools in sculpt mode do not. This should really be made consistent across both modes. \n\n\n", "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it" ]

[ "Improved Rake functionality\nFor now it would be best to focus this implementation on Sculpt Mode, since this will be the basis of the upcoming Paint Mode.\n\n## Issue\n\nWhen using an image texture in a brush you can enable the option \"Rake\" so that the texture rotation is following the direction of the stroke.\nThis has a huge issue that it stamps the entire texture repeatedly which makes it impossible to create a smooth curved texture that accurately follows the stroke.\n\n\n\n\n\n## Proposal\n\nEssentially we need to implement a way to split up the brush texture into many thin slices and apply them to the stroke incrementally.\nThis way it will have the visible effect of putting the texture on a paint roller and rolling it over a surface.\nThis would also make it possible to assign a very wide texture to a brush and paint it in a curved way on the surface.\n\n[roll brush mockup.mp4](roll_brush_mockup.mp4)\n\nAdjusting the texture size should help to redefine how stretched the used texture is:\n\nSize = 1\n\n\nSize = 0.25\n\n\nSize = 2 \n\n\n### Open Questions\n\nIt still needs to be discussed how this setting will be exposed and how it relates to the mapping, stroke and rake setting." ]

[ "Output UVs from mesh primitive nodes with anonymous attributes\nInstead of creating a named `uv_map` attribute on the geometry, they should be anonymous attribute field outputs. This brings up a few complications.\n- Currently we have no 2D vector socket. We probably want to avoid adding this for 3.0, so a 3D vector can be used for now. Automatic conversions will make versioning simple when we add a 2D vector socket, hopefully for 3.1.\n- The BMesh mesh primitive icosphere creates an `MLoopUV` attribute, this should be converted into a 3D vector anonymous attribute.\n\nThe output should be called \"UV Map\"", "Delete geometry node performance regression writing to multiple vertex groups in 3.1\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0\nWorked: 3.0.1 and older\n\nCaused by f5e5a0987a\n\nUsing a combination of Delete Geometry node along side the Armature modifier makes the node run slower and slower the more vertex groups armature is using. The difference is an immense drop from 144fps back to 8fps using the same .blend file in 3.0.1 and 3.1\n\n[Delete Geometry + Armature 3.0.1.blend](Delete_Geometry___Armature_3.0.1.blend)\n\n[Delete Geometry + Armature 3.1.blend](Delete_Geometry___Armature_3.1.blend)\n\n**.blend file overview**\n\n\nI would argue that this bug is a high priority issue and makes a lot of the character animation workflows impossible to use in 3.1 .\nDelete Geometry Node has been a replacement for the Mask Modifier ever since Geometry Nodes was introduced, it is a crucial part of a lot workflows. \n\n\n\n**More information if needed :**\n\n- Order of the modifiers does not matter\n- Vertex groups on the mesh have to be used by the armature for it to take an affect, however the vertex group used to delete the geometry is not being used by the Armature\n- The issue seems to be that the Node is now checking every single vertex group instead of the single attribute given to it\n- The more vertex groups used by the armature the worse the performance\n\n\n\n", "Node group inputs and outputs have incorrect \"name\" property\nOperating system: Linux-5.8.0-44-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.42.0, 5.8.0-44-generic, LLVM 12.0.1) AMD 4.6 (Core Profile) Mesa 21.2.0-devel\n\nBroken: version: 2.93.7 3.01 3.1 3.2\n\nWhen adding new Input or Output Sockets in the Group Node Properties Tab, the selected Input or Output Socket name is duplicated.\nTwo issues:\n- - [x] the socket name is not unique (this can get problematic since entries in node.outputs are name based)\n- - [x] design question: should the new name default to either \"Input\" or \"Output\"?\nShould Default to Input or Output. ( Only Defaults to Input or Output if there are no Sockets except the Default ones )\n\nIn the Node Editor add Input or Output Sockets to a nodegroup in the sidebar, change the name and try adding more Inputs or Outputs, the System will assign the name of the selected sockets. \n\nSeems like there are muliple functions handling new sockets\n- `make_socket_interface` [in affect when adding a new socket through the UI] gives a unique identifier (but copies the name exactly -- no uniqueness)\n- `nodeAddSocket` or `make_socket` take care of making the name unique as well\n\n{[F12842289](image.png) size=full}\n\n{[F12842292](image.png) size=full}\n\nref #91826 (just to show that unique names are important).\n", "Including node group attribute into NodeTreePath\nAt this moment `SpaceNodeEditorPath` has method append with parameters `node_tree` and `node`. This method is adding `NodeTreePath` into path. But event if `node` parameter was added into `append` method the `NodeTreePath` object does not have any information about root node of group tree.\n[bpy.types.SpaceNodeEditorPath](bpy.types.SpaceNodeEditorPath.html#bpy.types.SpaceNodeEditorPath.append), [bpy.types.NodeTreePath](bpy.types.NodeTreePath.html)\n\n\n\nAccording the fact that one group tree can be used by many group nodes it quite important to have information about via which group node the group tree is eddited. Sverchok addon is used to color problem nodes. Without information about group nodes in path it is impossible to mark such nodes.\n\nI would not bother if there was any workaround. What I actually was trying:\n```\nnode_tree_path.name = 'group_node'\nAttributeError: 'NodeTreePath' object has no attribute 'name'\n\nbpy.types.NodeTreePath.node = bpy.props.StringProperty()\nnode_tree_path.node = 'name'\nAttributeError: 'NodeTreePath' object attribute 'node' is read-only\n\nnode_tree_path['node_name'] = 'name'\nTypeError: bpy_struct[key] = val: id properties not supported for this type\n\narea_names = {}\narea_names[node_tree_path] = 'my_name'\n```\nEven last example would not work for several reasons. ID of path can be changed on undo event for example. If area is splitting into two I'm not able to update second area in the dictionary.\n\nI think, for API consistency, either `node` parameter should be removed out from the `update` method or `node` attribute should be added to `NodeTreePath` object. I would prefer second choice.", "Geometry Nodes: volume output shows as cube in eevee rendered view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nVolumes outputted via geometry nodes appear as a cube when rendering in eevee\n\n - Solid viewport: Looks ok\n - eevee material preview/rendered: Volume appears as a cube\n\t\nThis affects volumes from the Points To Volume node as well as when using a volume via a Object Info node. Cycles seems ok once the material has been assigned to the object instead of the data.\nI did try some debugging for this issue and it appears that the volume is setup correctly but the rendering code seems to be called twice once for the real volume and again for an empty mesh which obscures the real volume. \n\n\nOutput a volume with geometry nodes and switch to the eevee rendered view (Right side of picture below)\n\n\n", "Blender FBX won't export Mesh Geometry converted from Curve with geometry nodes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\n\nWhen creating meshes procedurally using geometry nodes modifier on a curve object, this object won't get exported by FBX exporter even if the result is a mesh, not a curve.\n\n1. Create a curve object\n2. Add geometry nodes modifier, create new GN node network \n3. Convert the curve to a mesh and add some topology (for example using curve fill)\n4. Export this object using FBX\nResult: The mesh is not exported\nExpected: The mesh is exported\n\n", "Some areas do not use modified (by geometry nodes) curve\nOperating system: Windows 10 - Probably irrelevant.\n\nBroken: 3.0.0 (not checked earlier versions).\nWorked: (none)\n\nThe Curve modifier on mesh objects does NOT use the modified version of a curve\n\nSee attached blend file for easy example: [bug - curve with modifier.blend](bug_-_curve_with_modifier.blend)\nExample screenshot of that blender: \nThe thin line is the curve, which has geometry nodes modifying it.\nThe thick (square) line is the mesh, which targets the curve but doesn't use the modified version.\n\n - Add BezierCurve, with a few points.\n - BezierCurve: Add geometry nodes (or any other modifier, like wave or whatever) that changes the curve.\n - BezierCurve: (for visibility) add geometry.\n - Add Cube .1m \n - Cube: Add Array modifier and Curve modifier, targeting the BezierCurve\n\n**Expected result**: Mesh follows modified curve.\n**Actual result**: Mesh follows original (unmodified) curve.\n\nThe blender file shows this very easily, the modified curve is round, the mesh is in the \"old location\" that the curve would have without the modifier on the curve.\n\n\nYes, this is a duplicate of: 93702/ - Where apparently there is confusion on what the issue is. I could not find a way to un-archive a ticket.\n\n\n**Areas Affected**\n- Curve modifier\n- Spline IK", "Shader node connections in v3.0 file broken in v3.3\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.3.0\nWorked: 3.0\n\nRendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80.\n\nAttached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3\n\n\n[REVISED sample file 300.blend](REVISED_sample_file_300.blend)\n\nOpen \"sample file 300.blend\" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected. \n\n\n", "Node Operators: Show node group inputs in redo panel\n_No response_\n\n", "Geometry Nodes: Simulation nodes cache assert\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 527.56\n\nBroken: version: 4.0.0 Alpha\n\nSee attached stack trace file.\n\nDebug build.\n1. Geometry nodes:\n a. Add Simulation nodes.\n2. Quickly and randomly move time cursor on timeline by hands.\n\n", "Geometry Nodes does not work with Rigid Body correctly\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel 4.5.0 - Build 26.20.100.7925\n\nBroken: version: 3.5.1\n\nI have seen that Geometry Nodes does not work with Rigid Body correctly.\n\nI join you and example with two flags and two dominoes pieces.\n[Bug Gemoetry Nodes and Rigid Body 1.blend](attachment)\n\nA flag traditionally rotates on the \"Z\" axis and pushes the domino piece.\nThe other flag uses the geometry nodes to rotate and instead of pushing the domino, it through it.\n\n\nThe Geometry Nodes only did a 'Transform Geometry' to rotate the flag.\n\nI opened the issue on https://blender.stackexchange.com/ and no one could did it work. \nI don't know if is a bug or that it still not deployed.\n\nI hope this is helpful and that you can fix it.\n\n", "Geometry Node: Viewer output for instance domain ignore if value nearest to 0.01\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4, 3.5\n\nGeometry Node: Viewer output for instance domain ignore if value nearest to 0.01\n\nIf you explicitly specify the instance domain, then with a value nearest to 0.01, the viewer will ignore the value input\n\n[2022-11-11 23-41-29.mp4](2022-11-11_23-41-29.mp4)\n\n\n- Put some intance to Viewer\n- Connect Float Value to Viewer set to instance domain\n- Test various floats (0.01 and 0.3)\n\nOr in attached file switch between couple of Viewer nodes\n[gn_viewer_value.blend](gn_viewer_value.blend)", "Solidify Node\nWe will drop support for Simple mode since the difference is hard to tell and performance-wise better to optimize the Complex mode than maintaining both.\n\nFill and Only options are a bit confusing in the modifier since fill refers to the fill of the rim and has to be checked on to make Rim Only work.\nInstead, I suggest making Fill refer to the part that is not the rim and Rim refer to the rim and make them independent from each other and both true by default.\n\nThe modifier has options for a vertex group as a factor for the thickness and two vertex groups to store the fill and rim geometry.\nvertex groups will be replaced by two attribute string fields for the factor and to tag the rim geometry\n\n", "Usability issues with old group operators\nBroken: 2.79, 2.8x\n\n\nWhen using linked objects, all the Group commands [Remove From Group / Remove From All Groups / Add Selected To Active Group / Remove Selected From Active Group] except [Create New Group (Ctrl G)], do nothing\n\n\nIn my particular usage, I link a scene from one file into my main scene, afterwards I create a [New scene with Link Objects] from the Linked scene. \n\n [GroupsFail.blend](GroupsFail.blend)\n [GroupsFail-MainScene.blend](GroupsFail-MainScene.blend)\n\nI can Create Groups by selected objects, and I can remove the group from the object in the Object Properties tab but the only way to remove multiple groups is through python script or deleting the group itself.\n\nSince this report is used to more generally handle issues with the old group operators and other reports have already been merged here, will also list these:\n- Ctrl G is placing new collections inside \"Orphan Data\"", "Snapping collision object to particle emitter not working\nOperating system: Linux-5.9.3-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.9.3-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.2.1\n\nBroken: 2.79 - version: 2.92.0 Alpha\nWorked: -\n\nIt is impossible to snap an object with Collision to an object with a Particle System (not event the snapping circle showing up), but it works the other way round (SnapTo set to everything but Increment). This seems to have been around for a long time, but I can't find any report regarding the issue.\n\nAdd a particle system to the default cube (P)\nAdd another primitive, activate collision in the physics settings (C)\nTry snapping C to P, it won't work\nBut snapping P to C works and collision objects can be snapped to each other. C to P only works if you remove the collision or the particle system.\n\n" ]

[ "Issue with Connecting Group Input and Group Output in Geometry Nodes in Blender 3.6.1 and above\nContent:\n\nHello,\n\nI am experiencing an issue with a Python script that worked fine in Blender 3.4.1 but is causing problems in Blender 3.6.1 and 4.0 alpha. The script connects the Group Input and Group Output in Geometry Nodes, but the connection is shown in red, and the vertex information in the Spreadsheet is displayed as 0.\n\nHere is a part of the Python script I used:\n\npython\nCopy code\n# Node connection\nnode_group.links.new(group_output_node.inputs[0], curve_to_mesh_node.outputs[0])\nnode_group.links.new(resample_curve_node.inputs[0], group_input_node.outputs[0])\nThis code connects the first input of the \"Group Output\" node to the output of the \"Curve to Mesh\" node, and the first input of the \"Resample Curve\" node to the output of the \"Group Input\" node.\n\nI have tried several things to solve this problem, but I have not found a solution yet. I have checked that the inputs and outputs of the nodes are correctly connected, and that the inputs and outputs of the nodes have compatible data types. Also, I have checked that the settings of the nodes are correct. Despite checking these things, the problem has not been solved.\n\nI would appreciate any information on this issue. Also, please let me know if this issue is a bug in Blender 3.6.1 and above, or if there is something I missed.\n\nThank you.\n\n", "Geometry Nodes: link to output inside node group is invalid when created from Python\nOperating system: Linux-5.19.0-35-generic-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03\n\nBroken: version: 3.5.0 Beta\nWorked: 3.4.1\n\nWhen using Python to create a new link between a node and a new socket in a Group Output node, the resulting link is invalid.\n\n\n\n- Open the attached blend file.\n- Run the script. It creates a new link between the second Math node and the Group Output node. \n- The following message is printed in the terminal, meaning that the link is invalid: `Valid: False`.\n\n-----\n\nThis issue breaks the Lazy Connect feature from Node Wrangler.\n\nReported by @genesis2303 in blender/blender-addons#104470.\n\n" ]

[ "vertex group re-appears, after it was previously removed via the API\nOperating system: Linux-4.15.0-175-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.3.1\n\nI have an object with 2 bevel modifiers. Each one uses it's own vertex group to control the beveling.\nI have a script that applies the first mod in the stack, and then removes its vertex group as well.\nIf you run this script 2 times, both mods, and both vertex groups should be removed. \nCuriously, while the modifiers are both removed successfully, the first vgroup will reappear after the second run of the script, so after the 2nd mod and vgroup have been removed.\n\nTo workaround this, you can toggle into edit mode and back into object mode at the beginning of the script.\n\nPossibly related to the commits mentioned here: T93896 ? \n\n[video demo ](BNwfPiyczdg)\n[bevel_vgroups.blend](bevel_vgroups.blend)\n\n* open the attached blend file\n* verify how each bevel mod is related to a vertex group sharing its name\n* run the script two times, and notice how the first vgroup reappears at the end\n\n", "Edges created by a bevel modifier are visible even for hidden items in edit mode (in wireframe display)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I did not follow it back to n previous versions.\nThe Problem is also reproducable in the latest nightly e362a2f0d41f\n\n\nIn mesh editting mode, if you hide an edge that is affected by a bevel modifier, the edges created by the bevel modifier are still visible. I expect them not to be visible because the edge is hidden.\n\n\n1. Open the attached file.\n2. There is one mesh in edit mode. One of the edges is affected by a bevel modifier.\n3. One face is already selected. Press Shift+H to hide all unselected items, including the aformentioned edge.\n4. You still see the result of the bevel modifier even if the edge is hidden. I expect it not to be visible. \n\nIn practice, this caused many confusing \"ghost\" lines of invisible items.\n\n", "Armature driving other object visibility gets out of sync if the parent collection is hidden/shown again in viewport\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.25\n\nBroken: version: 3.3.1\nWorked: Never\n\nWith a linked override library with some driver on some linked object (render or viewport visibility), if you disable viewport visibility for one parent collection of that object, when the file went open again the changes made to the linked armature gets messy and a resync is needed.\nNote that it happens only if there is some driver on one of the linked objects.\n\n\nOriginal file:\n[override_driver_original.blend](override_driver_original.blend)\nLinked file:\n[override_driver_linked.blend](override_driver_linked.blend)\n\n - Open the file named \"override_driver_linked.blend\"\n - Move \"Armature\" somewhere\n - Enter in Pose Mode and move the Bone somewhere, exit from Pose Mode\n - Disable from viewport the parent collection, named \"Collection.001\" (Globally disable in viewport)\n - Save the file and exit\n - Re-open the file\n - Make the \"Collection.001\" visibile again, note that both the armature and the object are misplaced!\n - Enter in Pose Mode, note that the object move but the armature is still misplaced!\n - Make a Resync on the armature to replace all in the right position\n\n \n\n\n\n", "VSE: Retime tool not available in \"Sequencer & Preview\" mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 4.0.0 Alpha\n\nWhile the Blade tool is available in both the \"Sequencer\" and \"Sequencer & Preview\" modes, the Retime tool is only available in the \"Sequencer\" mode. I'm not sure this inconsistency is intentional.\n\n(Apart from this, most of the tools in the \"Preview\" mode are also not available in \"Sequencer & Preview\", but I'm guessing that's intentional to avoid confusion - after all, users might expect the transformation tools to also work on strips in the timeline, not just on items in the preview. Is that correct?)", "Regression: Visual bug when using the object gizmos\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\nCaused by 917a972b56\n\nDifferently from using the transform tools in the toolbar, when activating the object gizmos that stay visible also with the select tools, a strange bug occurs that the e.g. moving the object on an axis keeps a grey axis where it was before, the gizmo is always present (differently again from using the transform tools), and if you switch from this to the transform tools to the selection with gizmo again, it messes the origin of the object.\n[2021-09-20 14-59-52.mp4](2021-09-20_14-59-52.mp4)\n\n\nI'm pretty sure that this is caused by the recent change of keeping the viewport gizmo visible when doing these operations.\n\nUse the select tool in the toolbar, activate on or more object gizmos that stay always visible, do a transform operation.\n[Based on the default startup]\n\n", "Disable Constraint Drivers Not Visible When Opening Older Files in 3.0\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\nWorked: (before 3.0)\n\nCaused by d6891d9bee\n\nDrivers put on the \"Disable Constraint\" switch are no longer accessible in the viewport.\n\n**`2.93`**\n\n\n[Constraint Driver Bug 2.93.5.blend](Constraint_Driver_Bug_2.93.5.blend)\n\n**`3.0`**\n\n\n[Constraint Driver Bug 3.0.blend](Constraint_Driver_Bug_3.0.blend)\n\nDriver does still work and is visible in the Driver Editor window, however it appears invisible on the constraint, Right Clicking the icon where the Driver is supposed to be does not come up with options to delete or edit that driver, button itself cannot be manually turned On or Off either.\n\nIn any Blender before 3.0 Add a driver to the \"Disable Constraint\" button on any of the constraints. Save the file and open it in 3.0.\n\n", "Operators for visibility on active face set missing from menus\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nThe default hotkey to show or hide the active face set does not appear in the menus.\n\n\n- Open Blender\n- Switch to Sculpt Mode\n- Use the Draw Face Set brush to create some face sets\n- Use the shortcut `H` and `Shift H` to control the visibility of the active face set\n- Search for the mneu entires of these shortcuts", "Modifiers added in edit mode are undone out of order if you go back to object mode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 13)\nWorked: Never (2.8+)\n\nModifiers added in edit mode are undone out of order if you go back to object mode and then start undoing.\n\nAffects both old and new undo system. There's often mentions of edit<->object transitions being problematic but just in passing; I think this is a long standing issue. Just wanted to note it down as I test out the undo systems.\n\nHoping the new undo system can account for this now.\n\n- Default scene\n- Go to edit mode on the default cube\n- Add any modifier (bevel, subdivision, etc.)\n- Add any loop cut 1\n- Add another loop cut 2\n\n- Go to object mode\n- Undo --> Modifier is removed first (out of order)\n- Undo --> Loop cut 2 is removed\n- Undo --> Loop cut 1 is removed\n\n\n", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Collection usability\n- [ ] Viewport UI\n- [ ] Shortcuts to toggle visibility?\n[ ] . . .\n\nNeed a clear design on what to do.", "Opening of a new/recent file interrupted with saving current file\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n1. create new file, make changes\n2. try to open recent file\n3. agree to save current file with new name\nfile saved but new one not opened.\n\n[2021-04-24_07-58-40.mp4](2021-04-24_07-58-40.mp4)\n\n", " Verts/Faces instantiation recursion: child items reappear if they are collection instances\nOperating system: kubuntu\nGraphics card: nvidia\n\nBroken: 2.82a - 2.90.1\nWorked: I don't think it did in the 2.8 series\n\n\nThe lower plane is the face-instancer of a blue sphere, and a collection instance that consists only of the peg (the one to the right). When the plane gets instantiated, the sphere is hidden (as expected) but the collection instance of the peg appears.\n\n\n\n\n\n[instantiating-a-collection-vs-object.blend](instantiating-a-collection-vs-object.blend)", "Image Editor in Mask mode: Toolbar broken \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nImage Editor in Mask mode: Toolbar broken \n\n- Open the Image Editor\n- Change the UI mode to Mask.\n- Add a new mask.\n- Toggle Toolbar(T).\nNotice that the Adjust Last Operation pop up i moving but no Toolbar becomes visible.\n{[F11089235](mask.gif),size=full}\n\n\n", "sculpt mode: invert visible hides all faces with Multires modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.0 Beta\n\n`Invert visible face sets` hides all faces with Multires modifier.\nOperator is expected to only hide visible faces (and unhides hidden faces)\n\n- Open .blend file\n- Use box hide brush to hide vertices\n- {nav Face sets > Invert Visible Face Sets}\n\nTest File:\n[#95419.blend](T95419.blend)", "There is no undo on linked data for the very few editable properties of linked data-blocks\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nWhen you __link an armature from other file__, then go to pose mode and __hide a bone__ and __undo the hide operation__, nothing happens.\n\n1) Create __a file with a simple armature__ (at least one bone).\n2) Open another project and __link the armature from before__.\n3) __Enter pose mode__.\n4) __Hide__ a bone.\n5) __Undo__ the hide operation. -> **nothing happens**\n\nI have added two files to reproduce the bug:\n(in the example I linked a whole collection and created a proxy to enter the __pose mode__ **but nothing changes if you link just the armature**)\n- `main.blend` - contains a proxy of the armature from __bone.blend__\n- `bone.blend` - contains just an armature used by __main.blend__\n\n[hide undo bug.zip](hide_undo_bug.zip)" ]

[ "With hidden region header, tool settings are unhidden after reopening file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nWhen disabling a region header, tool settings disappear as well (as they should). After saving and reopening the file, the tool settings are visible again, while the rest of the header stays hidden. \n\n - Right click the viewport header and uncheck Show Header. Make sure Show Tool Settings is checked.\n - Save the file and reopen it.\n - The header itself is still hidden, but the tool settings are back.\n - To hide the tool settings again, the header must be re-enabled and disabled." ]

[ "Regression: Crash when sculpting shape keys in 3.6.2 release\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 3.5 did not crash, I'm told.\n\n**Description**\nA user in a Discord community shared a file which was crashing for them while in Sculpt mode. I could reproduce the crash, so I simplified the file and found repro steps.\n<video src=\"attachment\" title=\"2023-09-14 00-35-34.mp4\" controls></video>\n\nAs you can see, it takes a few seconds of aggressively dragging the shape key value to get the crash to occur.\nAnother way to get the crash is to just make sculpt brush strokes. I found the shape key slider dragging easier, but I could get it to crash with sculpt strokes too, which was the original complaint from the user.\nMaybe worth noting that, as far as I can tell, if the shape key is not this extreme in its effect, then it seems even harder or impossible to produce the crash.\n\n- File: [Vessa_clean5.blend](attachment)\n- Make sure you're in sculpt mode (I don't think it can crash otherwise)\n- Drag the shape key value around for several seconds, or make a few dozen sculpt strokes\n- Should crash eventually.\n\n", "Drag data-block into \"Current File\" asset library to create local asset\nIt's not obvious to users how they can create assets. One thing many seem to expect is that they can drag a data-block into the Asset Browser. We can easily support this for the *Current File* repository. For others, we'd have to error out for now.", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "Crash creating \"position\" attribute with the wrong type while in Edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: 3.5.0 and 3.6.0 Alpha\nWorked:\n\nWhile in Edit mode, attempting to create an attribute called `\"position\"` that has type not set to `\"FLOAT_VECTOR\"` will crash Blender.\n\nI couldn't get any other attributes to crash when added while in Edit mode.\nCreating the `\"position\"` attribute with the correct type, but incorrect domain does not cause a crash either.\n\nI can't imagine a use case for users wanting to do this, but it came up while I was determining the extent of 107228 and isn't really the same issue.\n\n1. Select a mesh object\n1. Enter Edit Mode\n1. Either:\n 1. Run `bpy.context.object.data.attributes.new(\"position\", \"FLOAT\", \"POINT\")` from the Python Console\n 1. Create a new attribute called \"position\" using the `bpy.ops.geometry.attribute_add` operator and set the `Data Type` to anything other than `Vector`: ", "Some icons cannot be overriden from python (e.g. 'Constraint.mute', 'use_fake_user')\nBroken: version: 3.3.0 Alpha\nWorked: Looks like this was once working in 2.80 (but has stopped working in 2.81)\n\nSome boolean properties apply an offset to their icon depending on the state of the boolean. This offset is applied even when an icon override is used, like so: `UILayout.prop(icon=whatever)`.\n\n**Workaround**\n```python\ndef get_icon_value(icon_name: str) -> int:\n icon_items = bpy.types.UILayout.bl_rna.functions[\"prop\"].parameters[\"icon\"].enum_items.items()\n icon_dict = {tup[1].identifier : tup[1].value for tup in icon_items}\n\n return icon_dict[icon_name]\n\ndef draw_with_icon_fix(layout, prop_owner, prop_name, icon: str, offset=1, invert_checkbox=False, **kwargs):\n \"\"\"Drawing some booleans in the UI with a custom icon can be \n annoying because Blender might offset the icon based on the boolean state.\n You can use this function to counter that offset. To find the offset, you have to \n trial and error, it's either 1 or -1. (Or 0 but then you don't need this)\n \"\"\"\n\n bool_value = getattr(prop_owner, prop_name)\n offset = offset * int(bool_value)\n if invert_checkbox:\n offset = 1 - offset\n icon_value = get_icon_value(icon) + offset\n layout.prop(prop_owner, prop_name, icon_value=icon_value, invert_checkbox=invert_checkbox, **kwargs)\n```\n\n- File with script within: [icon_madness.blend](icon_madness.blend)\n- Script should self-execute, look for a \"FixMe\" panel in the sidebar.\n\n\nSo this file works in 2.80 and is broken in 2.81:\n[icon_madness_2.blend](icon_madness_2.blend)", "Blender Crashes on Render (Save As), then refuses to start\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: 3.6.1\nWorked: N/A\n\nFirst observed with the attached file. I tried to save a png image render from it; when I clicked \"Save As,\" Blender crashed and then... wouldn't open. It seemed to initiate startup, because the little black window that usually notified me that it was reading my userprefs.py file would blink into existence just long enough for me to register what it said, then close itself and act like I hadn't clicked it.\n\nRestarting my computer fixes the problem temporarily, until the next crash. The crashes are inconsistent, but seem to happen only when I hit main menu items like Open or Save. This includes previous versions, apparently, as I still had 3.5 installed and it does the same quick blink.\n\nThe only thing I could think of was that that Read line in the black window referred to finding the userprefs file in C:\\ when I installed everything into M:\\, but I tried copying the required path over to C:\\ with no effect and also it gives me that same message when it's working and starts up fine.\n\nI also tried repairing the 3.6.1 install, and uninstalling/reinstalling, to no effect.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Crash when loading a geometry nodes asset into itself\nOperating system: Win 11\nGraphics card: 2070\n\nBroken: 3.4, 4.0\nWorked: none\n\nWhen working on an geometry nodes asset in an asset library - if you search for the name and adding it to the graph it causes a crash. \n\nDrag n drop from the asset browser behaves correctly here - so I think its just the node search code which is missing the check for self referencing.\n\n1. Download the blend file.\n2. Put into a folder.\n3. Add folder as asset library in prefs -> file paths -> asset libraries.\n4. Open the blend file from that folder.\n5. Go to the geometry node graph (should be open already).\n6. `Shift` + `A` to add new nodes.\n6. Search \"noop\" and press enter.\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "bpy.ops.constraint.apply crashes when owner='BONE' and in object mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nWorked: unknown\n\nThe bpy.ops.constraint.apply operator crashes blender when targeting a bone constraint while in object mode. The attached blender file reliably causes the crash. It also seems to crash in pose mode at times, but I've so far been unable to recreate this in a small example file. See also [#97640](T97640) where a crash relating to the operator being used on objects has seemingly been fixed between 3.1.2 and 3.2\n\nto recreate simply open the blender file and run the script.\n[apply_bone_constraint_crash.blend](apply_bone_constraint_crash.blend)\n[apply_bone_constraint_crash.crash.txt](apply_bone_constraint_crash.crash.txt)\n\n", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\n\n", "2.8: Python API: Changing area type on frame change crashes Blender\nOperating system: Windows 10\nGraphics card: Quadro P4200/PCIe/SSE2\n\nBroken: 2.81a (also crashes in 2.79 and 2.80)\n\nI am attempting to sample the individual frames of an image on frame change, using a solution similar to the one described here: 5. I cannot seem to set the viewer area, however, from this context, as `bpy.context.screen` is `None`, and `bpy.context.window_manager.windows- [x].screen` seems to crash Blender in some situations.\n\nFrom the default startup file, run the following basic code:\n\n```\nimport bpy\n\ndef on_frame_change(scn):\n bpy.context.window_manager.windows[0].screen.areas[0].type = \"IMAGE_EDITOR\"\n\nbpy.app.handlers.frame_change_pre.append(on_frame_change)\n```\n\nRun the `Render Animation` operator to crash Blender.\n\nNote: This code runs fine when playing the animation in the 3D Viewport. It seems that this bug relates to the render context only.", "ops.paint.image_paint() crashes blender with brush texture\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.1\nWorked: unknown\n\n\nWhen using bpy.ops.paint.image_paint() in a addon and use a brush texture, blender crashes on the first stroke with a EXCEPTION_ACCESS_VIOLATION\n\n\n\n1. load the paintstroke addon \n```\n {F10253953}\n```\n\n2. load the blend file\n[paint_crash.blend](paint_crash.blend) \n3. go into texture paint mode\n3. make sure the brush texture is assigned\n\n4. paint on the object with (LEFTMOUSE)\n5. crash\n\n\n**addon code:**\n\n```\nbl_info = {\n 'name': 'paintstroke',\n 'description': 'Paint Material image channels at once',\n 'author': 'Daniel Grauer',\n 'version': (2, 0, 0),\n 'blender': (2, 92, 0),\n 'location': \"View3D > Sidebar > Edit Tab\",\n 'category': 'Image Paint',\n 'wiki_url': 'blender_Material_Brush',\n}\n\nimport bpy\nfrom bpy.utils import register_class, unregister_class\nfrom bpy.types import Operator, Brush\n\n \nclass PaintStroke(Operator):\n '''paintstroke'''\n bl_idname = \"paint.paintstroke\"\n bl_label = \"paintstroke\"\n bl_options = {'REGISTER', 'UNDO'}\n \n \n @classmethod\n def poll(cls, context):\n return bpy.ops.paint.image_paint.poll()\n \n def modal(self, context, event): \n #print(\"MB keybinding test modal\")\n if event.type in {'MOUSEMOVE'}: \n brushstroke = {\n \"name\": \"defaultStroke\",\n \"pen_flip\": False,\n \"is_start\": False,\n \"location\": (0,0,0),\n \"mouse\": (event.mouse_region_x, event.mouse_region_y),\n \"pressure\": 1,\n \"size\": bpy.context.tool_settings.unified_paint_settings.size,\n \"time\": 0,\n \"mouse_event\": (0.0, 0.0),\n \"x_tilt\": 0,\n \"y_tilt\": 0,\n }\n stroke = [brushstroke] \n bpy.ops.paint.image_paint(stroke=stroke, mode='NORMAL') \n\n elif event.value in {'RELEASE'} or event.type in {'ESC'}:\n return {'FINISHED'} \n return {'PASS_THROUGH'}\n \n\n def invoke(self, context, event):\n if event.type in {'LEFTMOUSE'}: \n #self.paint(event) \n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n \n\nclasses = (\n PaintStroke, \n )\n\n\naddon_keymaps = []\n\ndef register(): \n [register_class(c) for c in classes]\n \n # Keymapping\n kc = bpy.context.window_manager.keyconfigs.addon\n km = kc.keymaps.new(name=\"Image Paint\", space_type='EMPTY', modal=False)\n kmi = km.keymap_items.new(\"paint.paintstroke\", type='LEFTMOUSE', value='PRESS', shift=False, ctrl=False , alt=False)\n kmi.active = True\n addon_keymaps.append((km, kmi))\n \n\ndef unregister(): \n # remove keymaps\n for km, kmi in addon_keymaps:\n km.keymap_items.remove(kmi)\n addon_keymaps.clear() \n \n [unregister_class(c) for c in classes]\n \n\nif __name__ == \"__main__\":\n register() \n```\n", "Icon Alpha property also affects the thumbnails of matcaps/studio lighting...\nOperating system: Win 10\n\nBroken: blender-2.91.0-68797982025c-windows64\nWorked: ?\n\nThe \"Icon Alpha\" property in the Themes settings also affects the thumbnails of stuff like matcaps/studio lights....\n\nGo to: Edit -> Preferences -> Themes -> User Interface -> Styles; now try to adjust the \"Icon Alpha\" property while the matcaps panel is open to see the effect...\n", "Expand asset drag & drop support to more cases\nUsers expect a number of use-cases for asset drag & drop to work. Dropping an asset means appending it currently, but what happens then varies.\n\nThe following drag & drop operations should be supported:\n\n| | Asset Type | Drop Action | Notes \n| ---- | ----| ---- | ---- | ----\n| General UI | | | |\n| ---- |\n| {icon square-o} | Any | Dropping onto data-block selector: Assign data-block if applicable | \n| {icon square-o} | Scene | Change to dragged in scene | \n| 3D View | | | |\n| ---- |\n| {icon check-square-o} | Object | Add Object in Object mode | \n| {icon square-o} | Object | Add mesh (or strokes, curves, meta-ball element, ...) in edit mode (to the active object?). | Append in edit mode not supported. Postponed for now.\n| {icon check-square-o} | Object-data | Adds object in object mode using appended object-data | \n| {icon square-o} | Object-data | In edit mode: Same as dropping object in edit mode | Append in edit mode not supported. Postponed for now.\n| Node Editor | | | \n| ---- |\n| {icon check-square-o} | Node Group | Create Node Group node | \n| {icon check-square-o} | Image | Create Texture/Image node | \n| Geometry Nodes | | | |\n| {icon check-square-o} | Object | Create Object Info node | \n| {icon check-square-o} | Collection | Create Collection Info node | \n| {icon check-square-o} | Texture | Create Attribute Sample Texture node | \n| Compositor | | | |\n| {icon check-square-o} | Masks | Create Mask node | \n| Outliner | | | |\n| ---- |\n| {icon square-o} | Any | Assign to drop target (e.g. assign dragged material to object under cursor on drop) | \n| Text Editor | | | |\n| ---- |\n| {icon square-o} | Text | Change to dropped text | \n| UV/Image Editor | | | |\n| ---- |\n| {icon square-o} | Image | Change to dropped image | \n| Dopesheet | | | |\n| ---- |\n| {icon square-o} | Action/Pose | Change to dropped action (if the context mode allows it, e.g. in Action Editor mode) | \n| NLA | | | |\n| ---- |\n| {icon square-o} | Action/Pose | TBD | \n| VSE | | | |\n| ---- |\n| {icon square-o} | Media | Add strip for media type (image, video, sound) | \n| Movie Clip Editor | | | |\n| ---- |\n| {icon square-o} | Video/Image/Clip | Add clip for media type and change to it | \n\nNote that drag & drop support for assets also brings drag & drop support for local data-blocks. So for example by adding drag & drop support for node group assets, dragging a node group from the Outliner to a Node Editor is also added." ]

[ "Crash when changing asset icon\nBroken: version: 3.5\nWorked: - (never, it is related to \"All\" which was introduced in 3.5)\n\nBlender crash guide during ASSET open .png\n\n\n* Set `Interface > Temporary Editors > File Browser` to open in maximized area\n* Mark cube as asset\n* Open Asset Browser\n* In side panel, change asset icon (any should do)\n\nIt will crash.\n\nNote: It will only crash if library is \"All\"." ]

[ "Shader to RGB node is ignoring shading and just using color socket data directly\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.4\n\n\nIf you have a Shader that is converted with the Shader to RGB node, and then the resulting Color is plugged into another shader node and rendered, the output of Eevee's Color pass for that shader shows color plugged to socket of shader that is converted to RGB. In example file it is pure white, when you would expect to see the converted shader to RGB.\n\nProblem exists with Diffuse, Glossy, and Emission shaders and passes with the exception that an Emission converted to RGB going into another Emission will show up properly in the emission pass.\n\nSee Node graph in attached image, or attached file.\n\n\n[shader_to_rgb_eevee_pass.blend](shader_to_rgb_eevee_pass.blend)", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "Scroll direction Natural doesn't work on node canvas views on macOS\nOperating system: macOS-12.6.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.3.1\n\n**Short description of bug**\nI have scroll direction natural enabled for the my mouse and node views like shader editor, geometry, compositor etc ignore this setting and the direction of scroll is incorrect where scrolling down zoom out but it should be apposite and zoom-in.\n3D viewport behavior is correct and works as expected.\nI also tried to reset factory settings, and clean uninstall this issue still exists.\nThis issue I think is linked to this about invert direction scroll: T89906\n \n\n\n - On macOS make sure Scroll Direction: **Natural** is enabled. (by going to system preferences > mouse/trackpad > scroll & zoom)\n - Scrolling down using Magic mouse or Trackpad on on 3D viewport. and it should zoom-in. (expected behavior)\n # Repeating the step 2 in Shader editor. and it will zoom-out. (incorrect behavior)\n\n\n", "EEVEE image sequence frame offset not working [in multiple image texture nodes having the same image datablock]\nOperating system: WIN 10\nGraphics card: RTX 2070\n\nBroken: 2.81 date 2019-09-08\nWorked: none\n\nif I use one video texture in different materials, I only change the frame offset of the texture node\n- CYCLES: work as expected ( image is offset in time)\n- EEVEE: all materials use the same frame of the video texture\n\n\n\n\n\n[test_offset_blender-02.zip](test_offset_blender-02.zip)\n\n\nset viewport to \"rendered\" mode. just switch from EEVEE to CYCLES to see the difference (the number displayed on the texture is the frame number of the texture)", "Switch View Node does not get updated when clicking `update views` button\nOperating system: MacOS Ventura 13.4\nGraphics card: M2 Max\n[system-info.txt](attachment)\n\nBroken: 3.6 LTS\n\n## Not sure if it is a bug, or it is just my misunderstanding.\nSwitch View Node does not get updated when clicking `update views` button. (I expect that there should be a new input socket `RenderView`)\n\n\n1. Add a switch view node and (optinally connect it into the node tree)\n2. Check stereoscopy and add a view.\n3. click the `update views` button in the side panel.\n\n<video src=\"attachment\" title=\"Screen Recording 2023-07-09 at 5.10.54 PM.mov\" controls></video>\n\n", "Skin modifier does not work on meshes created from scratch during evaluation (primitives, etc.)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.0.0 Alpha\nWorked: NA\n\nSkin Modifier does not work with Geometry Nodes Mesh Primitives, see attached blend file.\n\nOpen attached file, note that Skin Modifier has no effect.\n\n[GN_skin_modif_bug.blend](GN_skin_modif_bug.blend)\n", "Clang on windows\nWhile we have supported building with clang on windows for a while, support has deteriorated a little due to it not getting regular exercise also not all features were supported this is a list of outstanding issues with clang on windows.\n\nOrder of importance:\n\n- {icon circle color=red} **Very Important** - *These we should handle before the next release.*\n- {icon circle color=yellow} **Somewhat Important** - *These issues would be nice to do as soon as possible*\n- {icon circle color=green} **Less Important** - *Extra polish, nice to have*\n- `?` **Incomplete** - *Tasks needing more details before implementing.*\n \n- {icon circle color=green} Better documentation on how to build, [the initial commit ](rB81060ff6b26c22331d2066bb83d492bbe61e936c) had instructions but some of those instructions are no longer applicable \n- {icon circle color=green} [D5962: Fix: Building quadraflow with clang on windows.](D5962)\n- {icon circle color=green} ~~Building with clang+ninja is broken~~ fixed:34bd23dbb7\n- {icon circle color=gray} VS2019 IDE support is broken due to the llvm integration addon, VS2017 IDE works, ninja work for both 2017/2019 \n- {icon circle color=green} [D5976: Add support for building with OpenMP support for clang on windows.](D5976)\n- {icon circle color=green} [D6012: Fix: BLI_expr_pylike_eval_test test failing with clang on windows](D6012)\n- {icon circle color=green} Cycles had a broken AVX2 kernel when running the benchmarks on EC2 \n- {icon circle color=green} Too many warnings a full build log is over 1GB \n- {icon circle color=green} cycles kernels get fed clang flags which it does not recognize `-fno-trapping-math`, `-fno-math-errno` , `-fno-signed-zeros`", "VSE: Cycles displayed as Rendered in Scene strip makes Blender hang - and other Scene strip bugs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nThe Render modes of Scene Strips are either missing or broken:\n- When Cycles is set as render and Rendered set as display, it'll make Blender hang.\n- Wireframe and Rendered doesn't work with any Render. \n- The only thing working is Eevee with either solid or Material Preview. \n- Workbench and Cycles settings seems to just use the Eevee render, since these are producing the same results in Solid and Material Preview.\n\n{[F10177251](scenestrip.gif),size=full}\n\nTest file:\nCycles is set up as render in the 3D Footage scene. In the Master Edit scene, switch display mode to Rendered. Blender will hang.\nTry the various other display modes and renders(by changing the render in the 3D Footage scene), to see wireframe and rendered doesn't work with any render. \n[multicam_3d_c.blend](multicam_3d_c.blend)\n\n\n", "CommandBuffer Failed: cycles metal integrator_ shade_volume --MacOS--\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nStarts rendering fine until the error. About 2-3 min. into the render.\n\n\nOpen the ziped blend file with 'Intel MacOS' blender 4.0a and hit render in the compositor!\n\n\nProbably related to: 104744\n\nPS: MacOS blender fails with most Volumes on latest major addons like PureSky, CloudScapes, etc... since blender 3.x .... ! The same applies when creating Volume emtys and volume Modifiers (mesh to volume & volume displace). At some point, blender will quit when clicking on the data tab (cloud icon) for volumes, as reported before.\n\n", "Sculpting using EEVEE\nThis keeps track of the patches and tasks needed for improving sculpting with EEVEE/Lookdev enabled\n\n[D8558](D8558) Fix EEVEE not using the PBVH for rendering in Sculpt Mode\n[D8564](D8564) Sculpt: Use Simplified Materials option\n[D8566](D8566) LookDev: Lock HDRI rotation to View", "Cycles rendered 3DViewport massive performance drop, using lights with node groups. --Intel MacOS--\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 4.0.0 Alpha\n\nSee screenrecording video! \nWhen switching to a light with nodegroups in Cycles rendered 3DView, performance drops a big time. (~50%).\n\n1. Open the performance.blend file with Intel MacOS blender 4.0, switch to cycles rendered 3DView, select the cube and rotate the view.\n2. Then switch to the caustic light and try to rotate the view again.", "Keyed Particles don't render as expected\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5069\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n[KeyedParticlesJL.blend](KeyedParticlesJL.blend)\n\n- Open file\n- Go to frame 105\n- Render\n- Compare render to viewport\n\nRender is different to viewport\n\nThat's what I expected:\n[ViewportRender.mp4](ViewportRender.mp4)\n\nThat's what I get when rendering with Eevee:\n[EeveeRender.mp4](EeveeRender.mp4)\n\nThat's what I get when renderng with Cycles:\n[CyclesRender.mp4](CyclesRender.mp4)\n", "Grid doesnt show\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "EOL GPU problems tracking report\nThis is a task to keep track of End Of Life GPU problems with blender 2.8\n\n(Note that closed issues at time of writing is not because they are resolved but because of lack of respons from reporter)\n\n**AMD**\nHD 8670M #64469 (UI and 3D viewport doesn't update visually unless mouse hovers over other UI elements)\nHD 8550G #58544 (White Viewport in [Object Mode])\nHD 7730M {#63243\nHD 7600 {#70091}}\nHD 7600 #70146 (hair eevee rendering broken.)\nHD 7450M #61890 (AMD Radeon HD 7450M. Exit before splash screen. 4-component vector of vec4 to: 4-component vector of uvec4)\nHD 7420G #63149 (Interface and vertices flickering)\nHD 7160M #61165 (Blender 2.8 beta doesnt start)\nHD 6870 #64081 (Eevee glitching [Linux, Radeon GPU])\nHD 5700 #62572 (unwrapping bug )\nHD 5700 #62701 (Hair edit mode crashes with AMD Radeon HD 5700)\nHD4870 #65721 (Crash on start)\nHD 4850 #61206 (Linux and AMD RV770 interface glitches)\nHD 4600 #59738 (Buggy GUI) #61896 (UI graphic glich) #63850 (Icons bug)\nHD 4550 #60104 (Blender's visuals go transparent and spasms )\nHD 4500M #63661 (Unstable back color in menues/ titlescreen. shifting Transparency /black )\nHD 4350 #59635 (blender 2.80.0 beta wont open on windows machine)\nHD 4300 #65075 (blender interface background of menus and every element in ui flickers (transparent and not))\nHD 3650 #60681 (Blinking menu and other menu)\nHD 3450 #63751 (when i open blender beta it chashes at start)\nHD 3200 #62543 (Crash at startup)\nHD 2600 #59738 (Buggy GUI)\n\n**NVIDIA**\nGTX 9800 #60425 (EEVEE objects black when using shadows, on 9800 GTX)\nGTX 9800 #65250 (Slackware, Blender 2.8 UI fonts glitch with nouveu driver.)\n\n**Intel**\n\nHD GFX (Baytrail) #65138 (Intel HD Graphics bone selection problems in edit mode/pose mode)\nHD 4000 #58938 (Crash when using EEVEE and Intel HD 4000) #65666 (Blender not responding a lot of time, especialy when working with texture and materials)\n\n**macOS**\n(AMD)\nHD 6750 #62072 (Princioled BSDF and Indirect Lighting BUG ) #65453 (Bake indirect lighting turns irradiance volumes into black areas)\nHD 4870 #62982 (Blender 2D draw mode shows as corrupted screen)\nHD 4670 #66014 (Blender 2.8 using Mac OS, all objects turn black in Lookdev mode)\nHD 2400 XT #60979 (2D Animation view goes crazy when trying to use brush)\n(NVIDIA)\nGS 8800 #59955 (Blender starts with totally corrupted graphics)\nGT 9600M #61844 (User interface looks very weird when starting Blender 2.8 with older MacBook Pro (Mid 2009))\nGT 130 #61551 (macOS 10.11 and NVIDIA user interface display broken)\nGT 320M #60179 (Bad render of default scene Mac OSX)\n780M #62578 (Eevee Screen Space Reflections crashes on OSX 10.9 / 10.11)\n640M #63018 (macOS 10.10 / NVIDIA: missing letters in 2.80 UI)\nQuadro 4000 #62766 (Eevee DOF cut plane)\n(Intel)\nHD 3000 #65551 (Bad shading on LockDev on Macbook 11\")\n", "Wireframe opacity slider does not work.\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 3.1\nWorked: \n\nWireframe opacity slider does not work if smooth wires is turned off.\n\nopen preferences>viewport\ndisable smooth wire overlay\nsave preference\nset viewport to wireframe shading\nin the overlay panel in viewport drag the wireframe opacity slider, the wire color will fade to black, the opacity won't change." ]

[ "Invalid (pink) shader when using wireframe node [ Eevee ]\nOperating system: MacOS 10.15 Beta (19A526h)\nGraphics card: Radeon Pro 560\n\nBroken: 2.81, 2019-08-19, 10001d909905\nBroken: 2.80, 2019-07-29, f6cb5f54494e\n\nWhen using wireframe input node shader becomes invalid (pink) when using Eevee. I think this is a MacOS specific issue given that a user with exactly the save version of Blender was not able to replicate this on Windows.\n\nSwitch to Eevee renderer.\nCreate a shader which uses the \"Wireframe\" node. A shader that I have found to definitely be broken is this:  .\nTry to view an object with that shader in either Look dev (  ) or Rendered (  ). I have only found the shader to work when using Cycles." ]

[ "Additional unwanted objects being created when asset browser asset is used\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.0\n\nAdditional duplicate (unwanted) objects being created when using assets from the asset browser.\n\nI haven't managed to consistently reproduce how I get this issue to happen. However, I have attached files which are guaranteed to demonstrate it.\n\n1. The oxford-straps-demo.blend file contains the source meshes which are placed in a collection and marked as asset called \"Source Asset\"\n\n2. The test-asset.blend file contains the \"Source Asset\" dropped in as Linked then Library Overridden. That itself is then marked again as an asset called \"Test Asset\". (This is my workflow - I would do this, then add materials at this stage).\n\n3. Open a new blend file and drop in the \"Test Asset\" (with Append). You will see the appended asset plus two other unwanted objects which are duplicates of the objects contained within the sealed asset.\n\nI have to delete these every time the asset is used.\n\n", "Code cleanup\n- [ ] Directly pass `params` to `filelist_setfilter_options()`.\n- [x] Port new asset files to C++.\n- [ ] Port `filelist.c` to C++? Think this file could be greatly cleaned up by using some simply C++ features (like simple inheritance for the individual list types).\n- [x] Remove unused asset code from old design (e.g. `AssetUUID`, `AssetUUIDList`, etc) (88c855174d4)\n- [ ] Add runtime struct to `SpaceFile`. Eventually could store: `rebuild_flags`, file-list, `folders_prev`/`folders_next`, active operator pointer, timers and layout.\n- [ ] Either remove `FileDirEntry.description` or use it for asset file tooltips (taking the description from `AssetMetadata`).\n- [ ] Check disabled assert in `BKE_object_copy_particlesystem()` with Sergey. *(Okay not really a cleanup...)*\n- [ ] The file browser and `ED_OT_lib_id_load_custom_preview` use \"active_id\" for the focused data-block context member name should be just \"id\".", "Asset Browser: Material preview with black background when Cycles is disabled\nBroken: version: 3.0.0, 3.4.0\nWorked: Never\n\nWhen a scene was saved with Cycles but I disable the Cycles add-on the material previews get a black background.\n\n* Disable Cycles add-on.\n* Click on any (e.g., the Yellow) material asset and update its preview.\n[black_preview.blend](black_preview.blend)\n", "Properties Editor Popover\nWith properties search and outliner to properties tab switching we need a place in the properties editor for various settings. These options may include:\n* Outliner Tab Switch. There isn't an automatic solution that works well enough, so an explicit toggle is needed. [Auto, Enabled, Disabled]. Auto will keep the current behavior of only switching tabs on shared borders\n* Property search: Full tooltip text search would be useful, but could make performance suffer so a toggle would be useful\n* Tab hiding. Some workspaces don't need to display certain tabs and they can be hidden by default", "Drag data-block into \"Current File\" asset library to create local asset\nIt's not obvious to users how they can create assets. One thing many seem to expect is that they can drag a data-block into the Asset Browser. We can easily support this for the *Current File* repository. For others, we'd have to error out for now.", "How to keep asset viewer options and the search field in view?\n\n\nIt's annoying that animators have to scroll up all the time to access these (or down for the search field).", "Brush Asset Project\nNOTE: WIP...\n\n--------------------------\n\nThis task is a general overview of the proposed new 'Brush Asset' system, aiming at offering a better brush management in Blender. Technical design will be done in sub-tasks.\n\nThe short-term flow of work is not organized here, but on the dedicated \"Taiga\" platform: julianeisel-blender-brush-assets\n\nIssues With Current Brush Management\n****\n\nCurrently brushes are essentially handled like any other data-block. However, they are not really data, more some sort of complex presets affecting sculpting or drawing tools.\n\nTheir coupling with editing modes and tools is also flaky, in most cases (besides Grease Pencil modes), selecting a tool also select a brush, and often there is only one default brush per tool. So having to select a tool automatically select a 'default' brush for it, this is redundant and not so clear for the user.\n\nBeing regular local data-blocks, they are hard to share:\n* Linking them is essentially useless, since one cannot edit their parameters then.\n* Appending them fully breaks any link to their source, and makes these brushes purely local data.\n\nFurther more, any edit to the brush settings is stored in the current file, making the concept of 'default' brush essentially nonexistent. Typical brush usages implies lots of frequent changes for a few properties, which should not be stored/kept across editing sessions.\n\nNew Proposal\n****\n\nGeneral Ideas\n----------------\n\nBrushes define the type of edit mode and action they perform. Selecting a brush automatically enable its relevant 'tool'. Consequently, there is only one drawing or sculpting tool left, per edit mode.\n\nBrushes are assets, stored in asset repositories. Either regular repositories, or a few special ones (like one shipped with Blender, currently called 'Essentials'). There are no more brushes stored in a regular working .blend file.\n\nIn regular working files, brushes are runtime-only data, their settings can be edited, but all changes are lost by default when closing Blender. Users can see (and reset) the edited values.\n\nChanges to brushes can be saved into the 'draft'. Draft is a special asset repository that acts as some kind of advanced per-user copy-paste buffer (similar to e.g. User Preferences: several instances of Blender ran by the same user would have access to the same draft data, but it would not be shared between different users).\n\nDraft data can either be independent (i.e. a full duplicate of the original brush data), or a library override of the original asset, to allow draft brushes to be updated if their original source is modified.\n\nAuthoring of brushes assets happens in the asset .blend files. Brushes can be either created from scratch, or duplicated from the draft or other assets. This process needs to be clearly separated from brush usage in the UI (probably done in different editors, Asset and/or Properties ones?).\n\nUI/UX Mockups\n------------------\n\nThis is a mockup of the new asset region for accessing as many or as few brushes as needed, as well as catalogs.\nFrom the bottom, the user would access and use their brushes. Meanwhile the brush settings would still be accessed in the tool settings.\nBasic drafting and saving of a draft would happen in the sidebar, but possibly in a different tab.\nThe Toolbar would keep a single brush tool, which activates if a brush is selected. \n\nIf there is a strong need for multiple tools for brushes in the Toolbar is still open.\n\n\n\n\n\nLike the name implies, this region would be used for more assets than just brushes, and could be used in various different editors.\nThe basic interaction with assets would be the same as the current Pose Library implementation, which this region aims to build upon and replace.\n\nUsing a new horizontal region is a more efficient and intuitive use of space, while saving space in the toolbar and sidebar for other important content.\n\nMore open questions and details in a different design task.\n\nTechnical Aspects\n---------------------\n\nMain points:\n* Brushes are linked and overridden. Allows user to be able to edit their settings, see which settings are modified, reset to default (i.e. linked data) values, etc.\n* No changes are expected for now in the existing brush/stroke/draw/sculpt code.\n* Clicking on the brush asset has to enable the relevant tool, do the linking & override action (or find existing override), and assign the override as active brush.\n* Draft support needs ability to create, manipulate, open and save additional Mains databases in Blender.\n\nOpen Questions:\n* Asset System: How to handle updates to the draft repository? User would expect to see these changes immediately in their UI.\n* Brushes: How to handle `BKE_paint_toolslots_brush_get` and the toolslot system? Pre-load brushes from the essentials there? Otherwise hook this code into the new brush loading system.\n\nIssues Not Tackled Here\n****\n\nThere are several other issues with Brushes and Sculpt/Paint modes that are not meant to be tackled by this proposal:\n* General technical debt (code severely lacks of proper design, and is very hard to understand, maintain and extend in its current state).\n** Somewhat related, serious lacking in things like tablet pressure control etc.\n* Unified Settings should be stored per edit mode, it makes little sense to share unified settings between sculpt and paint mode e.g.\n", "UI: sidebar tabs look for region overlap editors\nFor 3.0 we now have panels thinner than the area in which they are drawn. \nWhile this looks nice in most situations it's not the case for the category tabs in editors where region overlap is active, where they look arguably worse than before since there is now a visible gap between them and the panels.\n\nThis is he current look in 3.0 *(left is 3D viewport which has region overlap on, right is node editor which doesn't)*:\n\n\n---\nThese are some short-term possible solutions that I've tried, but there might be others:\n\n1. Draw all the tabs fully rounded and change the theme accordingly:\n * Possible theme change A\n```\n {F11800641}\n```\n * Possible theme change B\n```\n {F11800643}\n```\n\n\n2. Force no background and fully rounded tabs for overlap regions, keep the current look for the other ones *(this doesn't require theme changes)* [P2595](P2595.txt):\n \n\n\n3. Mix between 1 and 2, fully rounded tabs for all the editors and completely remove `tab_background` from the theme options *(would probably require updates to the themes)*\n\n\n4. Restore 2.93 look with full width panels for overlap region, keep the current look for the other ones [D12971](D12971):\n \n\n---\nWhile all the options proposed have their disadvantages, I'd personally go for option 2, until a better solution is found for the future.\nIMHO it looks fairly nice, it's not intrusive code-wise, and it doesn't require changes to any of the default or community themes, so it could be applied to 3.0 without further complications.", "UV space aware triangulation\nPlease see #102683 for details, since the issue is described and discussed there. The basic suggestion is:\n\n> Add an option to the \"Triangulate Faces\" operator. It currently has Quad/N-gon methods for Beauty, Fixed, Longest edge etc. It seems reasonable to add options for \"Prevent UV overlaps\" and specify the source UV map.\n\n", "Only Render visibility for 3D viewport\nIt should be possible to show only objects that will be in the final render in the 3D viewport.\n\nCurrently disabling the overlay only does half of what the old Only Render option did, which is to hide non-geometry objects. The visibility part is important too, though more complicated now since the regular viewport depsgraph will not evaluate objects that are not visible in the viewport.", "3D Texturing: When changing the texture resolution, the pixel data isn't recreated\n* Start painting\n* Change image resolution\n* Continue painting.\n\nWe have a safe guard for this, but it doesn't seem to work anymore.\n", "No \"affect alpha\" in brush settings in the Image Editor\nOperating system: Linux-5.3.0-40-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 7)\n(as well as the latest alpha: version: 2.83 (sub 5))\nWorked: 2.80 (Checkbox existed in Image Editor brush settings, but had NO effect on brush behavior)\n\nIn the 3D Viewport as well as the Properties Editor while in Texture Paint mode, all brushes offer the \"affect alpha\" option in the \"Advanced\" section of the Brush Settings. In the Image Editor that option is missing from the \"Advanced\" section for no apparent reason.\n\n\nOpen Blender with factory settings. Switch to \"Texture Paint\" tab. Compare the \"Advanced\" section of the active brush's tool settings in the Image Editor to that in the 3D Viewport or Properties Editor.\n\nSurely this has to be a well-known issue and exists only due to technical limitations of some kind.\nWhat should I tell my students why this inconvenience exists and when it will be addressed?", "Use new file-list design in the File Browser\nThis will be a rather complex task.\n\nFor this we'll need some kind of `uiModelView` for the File Browser, to handle filtering, sorting and lazy-cached previews. This may be the same (base?) view we use for the asset view as well.\n\nWe can either add C wrappers for the C++ functions, or compile the File Browser files in C++ (preferred).", "Asset drag & drop snapping: Limitations\nLimitations for the drag & drop snapping implemented in the `asset-browser-snap-dragging` branch.\n\n* - [x] The bounding box drawing uses bounding box based snapping, actually dropping the object uses the origin. (279f271a0a)\n* - [ ] No way to select an up-axis (e.g. for putting frames on a wall).\n* - [ ] No way to rotate the object while or after dragging.\n* - [ ] Rotation of the dragged object is not applied.\n* - [ ] Snapping uses rotation of the snapped to object.\n* - [ ] Snapping uses normals of the snapped to surface, which are often flipped. Should probably work in both positive and negative normal direction?\n* - [ ] Not implemented for collections yet.", "StringProperty search only works the first run when using regex search\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.1,\n3.4.0 Alpha\nWorked: Never\n\nWhen using python's re(gex) library for the new search callback results do not show up after the initial click and change of `edit_text`\n\nOpen included blend file\nExecute the script\nThere should already be search term there in the 'DEBUG' panel in the tool shelf (N Panel) after execution. If not I've been testing with 'do.*g' which should bring up 2 results.\nIf you click into the string property the correct results are there, but if you edit the search string all results disappear\nI've included a print statement that prints out the results of the _search_func_broken and you'll notice that the results are correctly being found and printed in the console but the UI does not represent these results\nThis does not happen if not using the re library as represented by the function `_search_func` and using a non-regex search item\n\n[search_regex_debug.blend](search_regex_debug.blend)" ]

[ "Support Filtering by Tags\nTags are important for managing assets. Users may want to have access to filtering by them from the get-go.\n\nThis is not a hard requirement for milestone 1, but I think it makes sense to have this." ]

[ "Hiding a nested collection doesn't immediately update its parent instances in the scene\nBroken: 483ae407d9d1 (blender2.8 HEAD)\nWorked: ?\n\nHiding a nested collection doesn't immediately update its parent instances in the scene.\n\n\n[outliner-deg.blend](outliner-deg.blend)\n\nHide the `Torus` collection (via the screen icon), this should hide this collection objects in the `B - I Instanced a torus` collection, however it doesn't unless you save and re-open or force depsgraph update in other ways.\n\n\n\nIf you toggle the `A - I have a torus` collection off, this one affects the instanced visibility immediately.\n\n*Note 1: The file only has Empties because I was looking at the depsgraph image and it was giving me a simpler depsgraph this way.*", "GPU: Design topic for displaying outline for instances\nSee 2 for discussion on devtalk\nWe might have technical reasons, but we don't need to distract users with drawing an outline around each instance.\n\nDesign topic could be should we group the outlines per original object (when using multiple objects to instance) or should we outline the object that creates the instances (eg contains the node group).\n\nPersonally I think we should have a single outline for an object. Not taking into account that it draws instances or not.\n", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up.", "Hair particles won't follow instaced position under 2 level nested collections.\nOperating system: Linux-5.11.0-7620-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 2.93.3\n\nHappens when you have an object with hair as instanced collection (A) inside another collection (B). Then, when you instance (B) the hair particle from (A) will not follow the relative position correctly.\n\n\n- Open .blend file\n- Select \"Cube\"\n- Object -> Quick Effects -> Quick Fur\n- {key Shift A} -> Collection Instance -> Collection\n- Move the instanced collection little away\n- {key M} -> New Collection -> Ok\n- {key Shift A} -> Collection Instance -> Collection 2\n- Move the instanced Collection 2 little away\n- You will notice the hair particle with a wrong position in relation to the original emitter Cube.\n\n1 min video here:\n[bugOrFeature.mp4](bugOrFeature.mp4)\n\nblend 2.93 here:\n[#91008.blend](T91008.blend)\n\n---\n\nNote that the concept works under 2.7 using Instaced Groups:\n\nblend 2.7 here:\n[ConceptWorks_b27.blend](ConceptWorks_b27.blend)\n", "Line Art doesn't exclude object's instanced by geo node\nOperating system: Linux-6.0.6-76060006-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.3.1\nBroken: version: 3.5.0 Alpha\n\nCollection Line Art includes instances that are distribute my geometry nodes, even if that object is not within the Line Art target collection.\n\n\n[Line_art_Geo_Nodes_instance_bug.blend](Line_art_Geo_Nodes_instance_bug.blend)\n**Exact steps for others to reproduce with example file**\n1. Open Attached File \n2. Observe Line Art is on objects outside target collection\n\n**Exact steps for others to reproduce the error from Startup**\n1. Distribute Objects from a collection with Geo-Nodes\n2. Create a second collection with a Line Art Target Object only\n3. Add Collection Line Art and target collection from step 2\n4. Line Art will be drawn on Geo-Nodes instanced objects\n\n\n\n", "Broken Twist on meshes deformed with Particle Instance Modifier with Along Path\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\n\nThe twist of a mesh deformed with the Particle Instance Modifier with the Along Path option seems broken, more noticeable with steep curvature in hairs. I compare it to the Curve Deform modifier as an example of proper deformation. Now, you may say it's an unfair comparison given that curves have an explicit twist that you can modify, unlike hairs. But even without controlling the initial twist of the hair, it's broken in a couple of ways.\n\nFirst, it deforms the mesh unevenly, with some vertices twisting more than others, even in a case where vertices are completely equidistant around the origin and both origins are aligned, like the cube in this image. The selected face and the edgeloop here should be squares but aren't, unlike in the curve deform modifier \nSecond, when changing the length with the Position Slider, the whole thing seems to change twist at once. Instead of having a consistent twist on each point of the path [Particle Instance Mod bug2.mp4](Particle_Instance_Mod_bug2.mp4)\nAs a side note, when using Along Path, finding how to orient your mesh to the hair is unintuitive, always using the global Y axis as the length axis in which I added subdivisions but then twisting weirdly when changing the Axis option in the modifier, I settled for Z in this example.\n\n\nAttached is the same file used in the video, you can open it and move the Position slider in the Particle Instance Modifier, the scale of the Curve Deform modifier example is driven by it so you can see both changing in real time.\n\n[ParticleInstanceTwistBug.blend](ParticleInstanceTwistBug.blend)\n\nWhy do I think this is happening? Well, if you select the object with the particle system, go to the particle properties, and change the length of the hair under the Render>Timing>End subpanel, you can see the problem is the same, basically the twist changes with length. Maybe the modifier should do something different and get the twist from the whole length particle and then scale the mesh instance before deforming or something like that, idk\n\n", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "Subdivision surface modifier creates self-overlapping geometry on coplanar non-triangulated face\nOperating system: Linux-5.15.5-76051505-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics (ICL GT2) Intel 4.6 (Core Profile) Mesa 21.2.2\n\nBroken: version: 2.93.4 -- confirmed in 3.1a 12/20/2021\nWorked: Unknown\n\nWhen set to simple, the subdivision surface modifier creates self-overlapping geometry with certain concave polygons on non-triangulated coplanar face:\n\nCan be related to #61145. See steps for more details.\n\nThis affects the `Subdivide` node in Geometry Nodes as well. \n\nAttached file have needed objects to reproduce.\nIn image is different examples of issue, from left to right then top to bottom:\n1. Plane with `Simple` subdivision surface modifier, works as expected.\n2. Plane with top-left vertex moved so that it's edges have angle >180 degrees. When moving either right, down or towards bottom right vertex issue will show itself. In this working state sum of this vertex angle and it's neighbors is strangely close to 270 degrees (with remaining bottom-right vertex having 90 degrees).\n3. Vertex moved close to opposite one. In `Top` view it shows that this unnecessary face have back normal but if you move viewport aroung you'll see it's gliching, overlapping with another face that have forward normal.\n4. Case where top edge of a plane is subdivided and created vertex moved to center to the point of glitching. See that on the right it shows back face normal but on the left it shows different color which I don't really know what it means.\n5. Showcasing slightly different glitch. When troubled vertex moved top/right face with back normal will disappear. That might be filed as separate report.\n6. Same as - [x] but bottom-right vertex also moved close to top-left one. Notice that while top-left vertex not moved from it's \"glitchless\" position in - [x] there is still bug.\n\nIssue is gone if face is non-coplanar. That can be seen if in attached file second collection made visible:\n\nThat is same meshes as before but with troubled vertices moved down Z axis. If view is rotate the cause for self-overlapping geometry can be seen. That's example [3]:\n\nWith that topology it's clear that if you move vertex so that face becomes coplanar you'll get self-overlapping geometry. \n\n`Simple` mode of subdivision surface definitely doesn't befave like `Subdivide` in Edit mode. You can see that in non-coplanar example [1]:\n\nWhen entering Edit mode transparent initial mesh without modifier is shown. If it behaved like `Subdivide` then it would not be shows because of full match with modified geometry.\n[examples subdivision coplanar non-triangulated.blend](examples_subdivision_coplanar_non-triangulated.blend)", "Fade Inactive Geometry: Objects with the same object data are faded\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 3.0.0 Alpha\n\nThe \"Fade Inactive\" Geometry\" overlay is supposed to fade out any object that is not affected by the currently active object in any mode that is not object mode.\nBut if any other object has the same object data linked (same geometry) it will be faded out anyway.\n\n In this example the quad-sphere in the center is active in edit mode. The one to the right has the same linked object data, which is why it also shows the edit mode overlays as it is the same geometry.\nBut since it is another object it is greyed out.\n\nThis is related to #87704 since the overlay seems to prioritise objects that are in the same mode instead of objects that share the same geometry.\n\n- Duplicate an object multiple times to have more than 2\n- Duplicate one of them with Alt + D to have their object data linked\n- Enter Edit Mode on one of those objects\n\n", "Support for tools with interactive geometry preview\nSome of the current or planned tools (add object tool, insert mesh brushes...) and other functionality requested project members require adding new geometry to the scene. \n\nAs far as I know, these tools can't render new geometry without creating a new object or adding that geometry to an existing mesh. This makes the gizmo previews of the add object tool not ideal and some of the requested functionality for sculpt mode is not possible to implement. It would require to modify the mesh and rebuild the PBVH in real time each time geometry changes. \n\nThe only tool so far that requires this functionality in sculpt mode is a limited version of the insert mesh brush in [D9380](D9380). That tool joins the insert mesh to the active mesh using BMesh when the stroke starts and then rebuilds the PBVH so the new geometry can be rendered. This makes the tool lag each time a stroke starts in a high poly mesh, and it limits the functionality to only an insert operation per stroke. (The ideal behavior should be that the insert mesh brush should insert a new mesh per stroke step, so you can insert meshes with spacing over the mesh). \n\nThe main goal of this design of to have a fast way to create previews for tools that modify geometry which look like the mesh is actually being modified. This is just a implementation detail, so the user should not know if the mesh geometry is actually being modified or if it is just a preview, as both options should ideally look the same. \n\n## Proposed solution\n\nThe ideal solution would be to have a generic function(s) that can render arbitrary geometry using the current scene shaders and render mode (as it was a new mesh object). This function should be possible to use from any operator and mode. \n\nIn the case of the insert mesh brush, the tool can manage a list of triangles and indices created by combining the geometry of the insert mesh and use this function to render them in real time without modifying the PBVH or the active object geometry. Then after the stroke finishes, all the new geometry can be joined to the active mesh in a single operation.\n\n## Workarounds\nIf implemented that functionality is not possible, some workaround for sculpt mode could be:\n- When PBVH rendering is used, add a \"fake\" node to the PBVH and add the new geometry there. If this fake node exists, render it as a normal node. When the operation finishes, delete this node, join the meshes and rebuild the tree. This approach won't work when PBVH rendering is disabled, so these tools will still lag.\n- Exit sculpt mode when the operation starts and create a new temporally object to do the geometry preview there. After the operation finishes, join the geometry, delete the preview object and enter sculpt mode in the initial object. Not sure what potential problems this approach could have (like undo). \n", "Mesh calc_smooth_groups(use_bitflags=True) issue\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2070S\n\nBroken: 3.0.0\nWorked: \n\nIf use_bitflags is True calc_smooth_groups returns only 1 smoothing group for opposingly facing faces when they share a vertex, see attachment. \n[flip.blend](flip.blend)\nIf use_bitflags is False calc_smooth_groups returns 2 smoothing groups in this case which is fine.\nIf use_bitflags is True and the 2 faces share an edge it returns 2 smoothing groups which is also fine.\n\nbpy.data.collections- [x].objects- [x].to_mesh().calc_smooth_groups(use_bitflags=True)\nreturns ((1, 1), 1) instead of ((1,2), 2)", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden", "Intersecting Meshes are not marked as overlapping anymore when selected\nOperating system: Linux-5.4.0-48-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.90.1\nWorked: 2.83.x\n\nIn blender 2.83.x Solid View intersecting objects had, if selected, the otherwise hidden parts shown in a more muted color when overlapping. with 2.90.x this is no longer the case. \nI hope this did not get removed intentional but is a missing feature.\n\nDuplicate the default Cube, move it a bit so that is still intersects with the first cube and confirm movement. \nWatch the outline in Solid View be the same color and thickness all around the mesh. \nin 2.83 while moving the white outline turned light grey when intersecting and the selected object outline turned a darker orange. This is very helpful for positioning elements.\n\n", "Alembic Render Procedural is not working in \"Viewport Render\" and \"Normal Render\" and with \"Collection Instances\"\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Beta\n\nAlembic Render Procedural not working in \"Viewport\" and \"Render\" and with \"Collection Instances\"\n\n\n- Import Alembic file\n- Duplicate it \"Shift+D\" or \"Alt+D\", or use it inside collection through\"Instance Collection\"\n- turn on \"Use render Engine Procedural\"\n in the viewport it will display as boxes, but in \"Viewport Render\" will disappear, in \"Normal Render\" will disappear also.\n\n@kevindietrich", "Multi-Object-Mode: EditMesh Vert/Edge Slide (transform) incorrect orientation for non active objects\nVert/Edge slide calculates the closest edge, then a screen space vector to move the cursor along to perform the slide.\n\nThis currently is only correct for the active object.\n\nIt's possible to have multiple objects rotated differently so the slide vector will be wrong on some objects.\n\nNote that performing vert/edge slide on multiple loops (while supported) is not all that common." ]

[ "Instances of Edge-only objects do not appear in 3D viewport until Realised\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen instancing a mesh line or an object containing only edges, only the first instance appears in 3D until realised.\nSame applies to only-vert objects.\n\nAdd a plane with a Distribute Points node, add an Instance on Points node and instance a mesh line.\n\n" ]

[ "EEVEE crash while rendering animation, cycles works.\nOperating system: Win10\nGraphics card: GTX1070MAX-Q\nCPU : i7-6700HQ\nRAM : 32GB DDR4\n\nBroken: 2.90\nWorked: -\n\nBlender crashes w/o any errors when I started to rendering animation in Eevee. \nIt happens on 2 laptops and it always happen in 154 or 155 frame while rendering.\nIn attachment you can download the project which gets this error. \nWhen I use cycles rendering it works perfect.\n\n[#80740.blend](T80740.blend)\n\n- Open file\n- Render frames 154 and 155\n", "Bake diffuse causes exits the program and core dump\nOperating system: Ubuntu 20.04.1\nGraphics card: Sapphire RX 5700 XT with latest drivers 20.45\n\nBroken: 2.83.10, 2.83.9, 2.83,8, 2.90.1\nWorked: \n\nI have cube with simple material. When I hit bake (diffuse), Blender exits immediately.\nInfo from terminal: \n\"Memory access fault by GPU node-1 (Agent handle: 0x7f9faac09b00) on address 0x7f9e1782c000. Reason: Page not present or supervisor privilege.\n./apps.sh: line 34: 84735 Aborted (core dumped) /home/karol/port_apps/blender-2.83.10-linux64/blender\"\n\n", "The program crashes when texturing \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nWhen try texture object in texture paint mode, and there are another map in shader tab. Program crashes. \n\n1. In default (or other) scene go to Texture paint window, create new texture for paint. \n2. Apply this texture to diffuse color object in shader editor. (or in object properties)\n3. Go back to texture window. We make sure that everything is painted correctly\n4. Go to shading window and drag&drop any other texture to node window. (NOT APPLY TO DIFFUSE COLOR (or APPLY))\n5. Go back to texture paint window. For some reason, the dragged texture itself was assigned to the duffuse color.\n6. Change linced texture in image editor (in left window)\n7. Try paint on RIGHT window (3D viewport)\n8. Click on left texture editor (try paint in 2D ) program crash. \n\nVideo steps: 0Ophy4Lmx0A\n\nDebug logs:\n[blender.crash.txt](blender.crash.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Blender_crash.webm](Blender_crash.webm)\n\n", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Crash when shading\nModel: HP Probook x360 435 G7 (independently upgraded SSD and RAM)\nOperating system: Windows 11 Pro 22H2 22621.1555\nGraphics card: AMD Radeon Graphics (Built-in graphics of AMD Ryzen 5 4500U with Radeon Graphics)\n\nBroken: 3.5.1 and 3.3.1 were tested, both had this issue.\nWorked: 3.1.2 – At the time of issue creation, there are no newer versions that have worked, including the latest build of 3.6.0 Alpha.\n\nBlender freezes for a second or so, and then crashes.\n\nI don't know if it *is* reproducable, but I have tested multiple conditions under which it crashes. These conditions are accompanied with the crash logs of that test. The problem does not seem to be (V)RAM usage, as the usage remains constant from before Blender is opened to long after.\n- Press F12 to Render Image: Crash [Log](itihmb)\n- Select Default Cube, Click on Shading workspace: Crash [Log](nxyeck)\n- Select Default Cube, Go to Materials tab: Crash [Log](ixgrhp)\n- Change Viewport Shading mode to Material Preview: Crash [Log](diwmma)\n- Change Viewport Shading mode to Render Preview: Crash [Log](ztajes)\n- DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: Crash [Log](gcaded)\n- Change Render Engine to Cycles, Press F12 to Render Image: **No** crash\n- Change Render Engine to Cycles, Click on Shading workspace: Crash [Log](chmkgj)\n- Change Render Engine to Cycles, Go to Materials tab: **No** crash\n- Change Render Engine to Cycles, Change Viewport Shading mode to Material Preview: Crash [Log](fhfyfo)\n- Change Render Engine to Cycles, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Cycles, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\n- Change Render Engine to Workbench, Press F12 to Render Image: **No** crash\n- Change Render Engine to Workbench, Click on Shading workspace: **No** crash\n- Change Render Engine to Workbench, Go to Materials tab: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Material Preview: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Workbench, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\nThank you for your help.\n\n", "Blender crashing while baking Smoke Domain\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.0 & 3.2.0 Alpha\nWorked: NA\n\n\nBlender Crashes while baking smoke domain\n\n- open Project \n- Select smooth domain from outliner\n- {nav Physic properties > Bake All} (crash between frame 60 & 70)\n\n\n\n\n", "Smoke and Fire simulation bug\nOperating system: Mac osx 10.15.6\nGraphics card: AMD Radeon Pro 5500M 8 GB\nIntel UHD Graphics 630 1536 MB\n\nBroken: 2.90.0 (202-08-31)\n\n\nBlender crashes while trying to bake a fire + smoke simulation in 128 resolution divisions... Sometimes it works. Mostly it doesn't.\n\nAttaching the file.\n\n[Blender Bug copy.rtf](Blender_Bug_copy.rtf)\n\n[fire.blend](fire.blend)", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>", "Frequent render crashes in 3.5\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5500M 1.2\n\nBroken: version: 3.5.0\n\nI've been encountering a lot of crashes in 3.5 when rendering in the background. Meaning I start a rendering, and move over to something like a browser. At random time Blender 3.5 just crashes. I've included a crash log file.\n\n\n", "Particle Edit mode for non hair particles - particles viewport display option crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.79\n\nIn Particle Edit mode, you can enable Particles display in Tool Properties > Options > Viewport Display. Pressing this toggle crashes Blender.\n\nFor convenience use this Blend file:\n[particlespath.blend](particlespath.blend) \n\n - Press the toggle in Tool Properties > Options > Viewport Display called 'Particles'\n - Crash\n\n\n\n", "Render crash\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon RX 560X ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.1.220810\n+ AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx\n\nBroken: version: 3.3.0 Beta\nWorked: 3.2.2\n\nBlender every time crash when switch to render mode in viewport.\nRender set to Cycles with GPU Compute.\nVega 8 selected as device in preferences.\nIf I select RX 560X in preferences, GPU Compute is greyed in Render preferences (also interesting why).\n\nAny project with simple cube crashed.[test11.crash.txt](test11.crash.txt)\n", "Bake fluid domain simulation crashes when using a depsgraph poll\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.92.0\n\nWhen using bpy.context.evaluated_depsgraph_get() in a poll and then baking a fluid blender crashes\n\n1. use the provided file with a fluid prepared to bake data or create a fluid domain and a fluid source\n[mantaflow.blend](mantaflow.blend)\n\n2. make sure the chace type is set to modular\n\n\n3. run the simple operator script (should come with the blend file)\n[operator_simple.py](operator_simple.py)\n\n4. press the bake Data in the Fluid domain settings and blender should crash\n\n\n\n", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "Blender 2.9 crashes during texture bake\nOperating system: Mac OSX Catalina version 10.15.7 (2,3 GHz Quad-Core Intel Core i7)\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.92.0 Alpha\nWorked: Blender 2.83\n\nBlender 2.9 crashes during texture bake\n\nUV unwrap an object\nCreate a material with principled shader\nAdd an image texture \nSwitch to cycles render engine\nWith the texture selected in the node editor click the bake button\nBlender crashes immediately." ]

[ "GPencil: Modifiers don't work after separate strokes and use hide in outliner [issue with multiuser gpencil objects and modifiers]\nOperating system: Ubuntu 20.04\nGraphics card: Mesa Intel® HD Graphics 620 (KBL GT2\n\nBroken: (2.83.3)\n\n\nThe mirroring of a grease pencil object briefly stops being visible after performing a stroke separation.\n\n1. Boot up Blender's default 2D animation workspace\n2. Draw a stroke on the GP object \"Stroke\"\n3. Add a mirror modifier to the object.\n3. Draw another stroke\n4. Change to edit mode and select the new stroke\n5. separate said stroke with P, creating \"Stroke.001\"\n6. Still on edit mode, click on the 'eye' icon on the outliner to make \"Stroke\" invisible\n7. Click on the eye icon again, the mirroring will have stopped being visible.\n8. Clicking twice on the \"Display modifier on viewport\" button in the modifier tab fixes the issue.\n\n**Status**\nThe \"wrong usercount when separating\" is fixed, see 4251a87bf6, however the underlying issues with multiuser gpencil and modifiers still remains.\nTo reproduce:\n- add a gpencil stroke\n- {key Alt + D} duplicate linked\n- add a Thickness modifier.\n- Hide/Unhide the object in outliner.\n", "Grease Pencil drawing sticks to Camera (when stroke placement is Surface and drawing outside of camera border)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nGrease Pencil drawing sticks to Camera (when stroke placement is Surface and drawing outside of camera border)\n\n[#92351.blend](T92351.blend)\n- open .blend\n- start a stroke inside camera bounds and end it outside camera bounds\n- stroke will stick to the camera on the end\n\n\n", "Semitransparent grease pencil covers wireframe. Bug or limitation?\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nit looks like this \n\n[untitled3.blend](untitled3.blend)\nAnd it is difficuilt sometimes to work with wireframe and GP-sketch when I don`t see vertices\n", "Grease Pencil wrong Cursor Size Smooth Brush when accesed with the [SHIFT] key\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 460M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.3.1\nWorked: \n\nThe On Screen **Smooth Brush Cursor Size** is inaccurate when using the Smooth Brush with the **[SHIFT] **key while using any other brush of a different radius setting.Grease Pencil > Draw any curve \nGrease Pencil > Sculpt > **Smooth Brush**> Make the Smooth **Brush Radius VERY SMALL** (10).\nGrease Pencil > Sculpt > **Grab Brush** (or **ANY OTHER BRUSH**) > Make the **Brush Radius HUGE**(150). \nUse the **Grab Brush** as you wish.\nPress **[SHIFT]**to activate**Smooth Brush**while in Grab Brush (or**ANY OTHER BRUSH**)\nThe on screen cursor Radius while the [SHIFT] key is pressed does not reflect the VERY SMALL Brush Radius (10) that we set earlier. This is constantly confusing. Can you please make the radius display correctly based on the actual Smooth Brush Setting?\nattached scene: GreasePencil_SmoothBrush_CursorSize_bug.blend\n[GreasePencil_SmoothBrush_CursorSize_bug.blend](GreasePencil_SmoothBrush_CursorSize_bug.blend)\nThank you!", "gpu.types.GPUOffscreen renders nothing when samples > 0\nOperating system: Linux-5.3.0-55-lowlatency-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83.0\nWorked: None known 2.90 alpha has same issue\n\nOffscreen rendering from Python fails if GPUOffscreen buffer is created with any number of of samples > 0. If samples > 0, nothing is drawn (nor is there any error)\n\nRun the small script in the attached .blend (it is the sample script for offscreen rendering from the documentation but with samples>0)\nThe generated image is empty.\n\n(full system info also in .blend in text buffer system-info.txt)\n[MSAA bug.blend](MSAA_bug.blend)\n", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up.", "Texture Paint - Clone tool not working when clone source area out of viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nTexture Paint - Clone tool not working when clone source area out of viewport\n\nImport image as plane- select part of image to clone in bottom part of image. Scroll up to the top part of image so the bottom is not visible = clone tool doesnt draw anything.\n\n\n\n", "GPencil: Screen-space stroke size incorrect\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTS 450/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.92.0 Alpha\nWorked: none found\n\n**Description**\n\nWhen drawing a stroke with a defined pixel size and stroke-thickness-space is set to screen space, the radius of the drawn stroke should measure the set pixel size. This is not the case. The strokes radius measures half the size.\n\n**Steps to reproduce**\n\n - Create a grease pencil object\n - Set the stroke-thickness-space to screen space in objects grease pencil settings\n - Set the brush size to 100px\n - Draw a single dot.\n - Print the screen\n - Measure the dot size in any image editing app.\n # You will see that the radius of measures 50px and the diameter measures 100px. Instead of 100px and 200px respectively.\n\nThis issue can be further seen by trying to change the brush size using the `f` key. The brush size cursor is drawn at the correct size but is double the size of the stroke.\n\n**Investigations**\n\nThis relates to my original report #82707 wherein I thought the cursor size was incorrect. I have now had time to review the code enough to understand how the cursor is drawn; and how the brush size is defined and passed to the rendering engine.\n\nI have confirmed that the brush size takes the following path.\n\nBrush.size user setting: RADIUS → bGPDstroke.thickness: RADIUS → gpencil_vert.glsl thickness: RADIUS\n\n*Simplified for explanation purposes. Path steps missing.*\n\nI originally thought thickness was defined as a diameter but this is not the case.\n\nI also thought this would be a noticeable fix but I haven’t found where the issue lie yet so I thought I would report again. \n\nNote: When drawing a stroke with stroke-thickness-space set to world space the stroke is mapped to the users screen correctly. When world space is used a stroke with a brush size of 2000px is drawn with a radius of 1m in world space as defined internally. \n\n[Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4](Bug-GPencil-Screen-Space-Stroke-Size-Incorrect-Report-VID.mp4)\n", "Greasepencil z fighting alpha issue\nHi,\nnot too sure if this is known issue or any fix but I am getting this alpha issue from certain angle when I have 2 different grease object. \n\n", " Greasepencil Hue/Saturation modifier\nOperating system:windows 10\nGraphics card:GTX 1060\n\nBroken:2.93beta\n\nHue/Saturation modifier can not take effect on fill-gradient", "Dot dash modifier not working with time offset modifier (grease pencil)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\nWorked: not sure\n\nWhen time offset modifier is in the modifier stack before or after dot dash, dot dash has no effects{[F12118899](dot-dash-time-monkey.blend)}\n\nSee attached file\n\n", "Blender 2.90/ 2.91 Sculpt Vertex Paint - Stencil not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta, branch: master, commit date: blender-2.90.0-0e280b96ca82-windows64\nWorked: I think this last work in 2.83.2 or 2.83.1\n\nSculpt Vertex Paint - Stencil not working\n\n\n[BlenderBug.blend](BlenderBug.blend)\n\nAdded colored image to texture\nChange texture mapping to stencil\nImage is coming out as black and white on the screen and image is not being transferred on the object.\n\nI have tried changing Blender Mode and Color Space but it didn't work.\n\nAlso I am not sure if this suppose to happen but the image for stencil disappears when I tick Color Ramp under Color in Texture Panel.\n\n", "GP brush pin for fill only, makes both stroke and fill\nHi \nI want to have fill and stroke in different color but if I pin, I get both color same.\nSo that I cannot make custom brush, or I have to change it vertex mode every time.\nCan you please check?\n\n[image](attachment)\n\n", "Weight Painting intermittent issues with brush, not adding or subtracting weight, not influencing correct areas\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080ti + 3x GTX 1080Ti - Running 4 monitors and a pen tablet at three different resolutions using outputs from two GPUs (4k, 1440p, 1080p)\n\nBroken: 2.81 stable\nWorked: 2.80\n\n\nI have had numerous issues with weight painting in 2.81, however duplicating them has been problematic as this crops up intermittently. In this example, I saved this working file right at the moment I started having problems. Here I can neither add nor subtract weight with the brush in Weight paint mode from a certain distance from the model. \n\nIn other instances, I've had issues with the brush *not painting over the vertices it's over*. I use a hard falloff brush, so anything inside the circle gets painted, anything outside gets nothing. Essentially, it acts like the circle where the brush is being displayed, is not where the circle actually is, if that makes sense.\n\n\n*I tried exporting this to it's own file, but that seems to fix it. It has to be in the full working file I'll provide here. You should hopefully be able to open the file, already be in weight painting mode, with the brush set up, over some masked vertices ready to add or subtract. Try switching the brush to add, and zoomed in fairly close, add some weight, and nothing happens. However, zoom out and do the same thing, and watch weight be added.*\n\nYou can kind of jump around and try rigging other parts of the car, I've been having issues with it off and on for the past few days.\n\n[70sNewYorkers.blend](70sNewYorkers.blend)", "Greasepencil effect error\nOperating system:windows10\nGraphics card:GTX1060\n\nBroken: 2.93\n\n\n\nIf Greasepencil enters a 3D object\n\n1, A small part of the BLUR effect will overflow and the join part will be a little transparent\n2.The FILP effect will lose part of the image\n3.The RIM effect will change as the 3D object changes.\n4.The shadow effect overlays 3D objects and is partially missing\n5.The wavedristution effect will overwrite the 3D object in horizontal mode.Vertical is normal\n6.The swirl effect will lose some of its effect and will overwrite the 3D object\n\n[rim.blend](rim.blend)" ]

[ "Grease Pencil Fill option when drawing no longer works in latest nightly\nOperating system: MacOs 11.2\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: Version 2.93.0 (2.93.0 2021-02-17)\nWorked: Version 2.93.0 (2.93.0 2021-02-16)\nCaused by 09f7c93858\n\nThe Fill option when drawing does not fill.\n\n. Create GP.\n. Go in Draw mode.\n. Check Fill option in Material.\n. Draw on canvas. The stroke is drawn but not filled.\n[Kapture 2021-02-18 at 14.13.02.mp4](Kapture_2021-02-18_at_14.13.02.mp4)\n\nThis might be a Mac issue although the same steps on my Win10 machine is also acting a bit funky..." ]

[ "F12 render all 600 frames complete cause crash.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.14.1\n\nBroken: version: 3.6.3 Release Candidate\n\nF12 render all 600 frames complete cause crash.\n\n\n\n\nBlender 3.6.0 crash\nBlender 4.0.0 is fine\n\n", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Particle Edit mode for non hair particles - 2 Crashes\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n\nParticle Edit: 2 Crashes\n\nParticle Edit: 2 Crashes\n\n- Open the blender file and click on the buttons \"Particle select and display point\"\n- Crash 1 (Screenshot)\n\n- Open the blender file and click on the tool \"Weight\" and click into the particles\n- Crash 2 (Screenshot)\n\n- Also had a crash with \"Puff\" \n- file not included\n\n- There are some tools that do nothing while others work\n- User gets no feedback / error message but give no feedback\n\n\n\n[2019-05-19-particle-edit-crash.blend](2019-05-19-particle-edit-crash.blend)\n\n", "Blender Crash by doing 2d animations\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 500 Intel 4.5.0 - Build 31.0.101.2111\n\nBroken: version: 3.6.0\n\nWhenever I draw with a line, circle, arc, curve, interpolate, and box tool, my drawings disappear and reappear and then it suddenly crash.\n- 2D animation Draw Mode\n[\nPlease describe the exact steps needed to reproduce the issue]\n\n", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\n", "Mode locked and crash if objects become disabled in viewport while not in object mode\nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.1.0 Alpha\nWorked: didn't crash but showed an error message in 2.91.2\n\nObjects that are in a mode which is not Edit Mode nor Object Mode, will lock the mode setting (so the mode options are greyed out and unusable) if they get disabled in the viewport. Hiding will not cause the this bug, it needs to be disabled in viewport using that display icon in the outliner, not the eye.\n\nThe solution for this is probably to make the disable in viewport action switch the mode to object mode if the active objects gets removed (much like delete from outliner). Another solution would be to still allow the mode switch.\n\nMuch worse though! Blender crashes sometimes when it gets into this state. I can reliably crash blender as described below.\n\nGo into weightpaint mode of the default cube and disable it in the viewport using the outliner (you need to enable the option first). Now you are stuck and have to enable it in the viewport first to be able to edit anything.\n\nNow restart blender etc. and try this:\n1. Go into Vertex Paint Mode of the default cube\n2. Hit Tab to go into Edit Mode\n3. Disable the cube in the viewport using the outliner as above\n4. Hit Tab to switch out of Edit Mode -> Crash", "Blender randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\n", "Render crash when using Python API to modify object Attribute data in frame_change_pre handler\nOperating system: Windows 10 Home\nGraphics card: GTX 1070 8GB\n\nBroken: Blender 2.93.0 84da05a8b806 (2021-06-02 11:21)\nWorked: n/a\n\n\nThis issue was discovered during development of an addon that generates procedural meshes in a `frame_change_pre` handler. When adding attributes to these meshes in the `frame_change_pre` handler, Blender can crash during render on random frames.\n\nThe `Render → Lock Interface` option is enabled as per the note in the [handlers documentation ](bpy.app.handlers.html#note-on-altering-data).\n\nI have created a simplified script that reproduces this crash during render, typically within a minute of starting the render. This script randomly generates triangles and attribute values in a frame change handler:\n\n```lines=5\nimport bpy, random\n\n\ndef frame_change_pre(scene):\n n_triangles = 10000 # number of triangles to generate\n n_attributes = 10 # number of attribute 'layers' to generate\n \n tsize = 0.1\n vertices = []\n triangles = []\n for i in range(n_triangles):\n xshift, yshift, zshift = random.uniform(-3, 3), random.uniform(-3, 3), random.uniform(-3, 3)\n vertices.append((-tsize + xshift, -tsize + yshift, zshift))\n vertices.append((tsize + xshift, -tsize + yshift, zshift))\n vertices.append((0 + xshift, tsize + yshift, zshift))\n triangles.append((3 * i, 3 * i + 1, 3 * i + 2))\n\n object = bpy.data.objects[\"Cube\"]\n object.data.clear_geometry()\n object.data.from_pydata(vertices, [], triangles)\n \n for i in range(n_attributes):\n attribute_name = str(i)\n try:\n object.data.attributes.remove(object.data.attributes.get(attribute_name))\n except:\n pass\n \n attribute = object.data.attributes.new(attribute_name, \"FLOAT\", \"POINT\")\n for value in attribute.data:\n value.value = random.uniform(0, 1)\n \n \nbpy.app.handlers.frame_change_pre.append(frame_change_pre)\n```\n\nIncreasing the number of triangles and/or number of attribute layers seems to increase the frequency of crashes. The crashes do not seem to occur when rendering from the command line.\n\nThis is the error reported after the crash:\n\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7736C6490\nModule : blender.exe\nThread : 00000814\n```\n\nAttached is the crash log: [attribute_crash_example.crash.txt](attribute_crash_example.crash.txt)\n\n\nAttached is a .blend file including the script that reproduces this issue.\n\n1. Open the .blend file\n2. Press 'Run Script'\n3. Begin rendering the animation (Blender > Render > Render Animation)\n\n[attribute_crash_example.blend](attribute_crash_example.blend)\n\n-----\nSeems easier to reproduce on a debug build since it hits an assert (although i'm not sure who is at fault there, could be the script, could be blender, @HooglyBoogly will likely know since he worked in this area recently) \n\n1) Make a debug build\n2) Load up the .blend above\n3) Hit the Play button on the Python script\n4) Rather than render, just his play on the timeline\n5) Boom!\n\n```lines=10\nBLI_assert failed: K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361, BKE_mesh_vertex_normals_ensure(), at 'CustomData_has_layer(&mesh->vdata, CD_NORMAL) || mesh->totvert == 0'\n\nStack trace:\nblender.exe :0x00007FF783355EA0 bli_windows_system_backtrace_stack_thread K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:233\nblender.exe :0x00007FF783354F30 BLI_windows_system_backtrace_stack K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:320\nblender.exe :0x00007FF783354900 BLI_system_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:386\nblender.exe :0x00007FF783359730 _BLI_assert_print_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:50\nblender.exe :0x00007FF777848300 BKE_mesh_vertex_normals_ensure K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361\nblender.exe :0x00007FF7778467E0 BKE_mesh_calc_normals K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:475\nblender.exe :0x00007FF77951DC80 ED_mesh_update K:\\BlenderGit\\blender\\source\\blender\\editors\\mesh\\mesh_data.c:1106\nblender.exe :0x00007FF77885B520 Mesh_update_call K:\\BlenderGit\\2022_full_with_tests\\source\\blender\\makesrna\\intern\\rna_mesh_gen.c:7350\nblender.exe :0x00007FF778528720 RNA_function_call K:\\BlenderGit\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:7336\nblender.exe :0x00007FF778A024F0 pyrna_func_call K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_rna.c:6304\npython310_d.dll :0x00007FFA32E09B40 _PyObject_MakeTpCall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:215\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:112\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4232\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E0EAC0 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:114\npython310_d.dll :0x00007FFA32E0ED10 method_vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\classobject.c:53\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:115\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4183\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E07FD0 PyVectorcall_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:255\npython310_d.dll :0x00007FFA32E086F0 _PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:290\npython310_d.dll :0x00007FFA32E07680 PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:318\nblender.exe :0x00007FF778A12F20 bpy_app_generic_callback K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_app_handlers.c:354\nblender.exe :0x00007FF776ECF220 BKE_callback_exec K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:51\nblender.exe :0x00007FF776ECF400 BKE_callback_exec_id K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:67\nblender.exe :0x00007FF7776D5C60 BKE_scene_graph_update_for_newframe_ex K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2648\nblender.exe :0x00007FF7776D5C10 BKE_scene_graph_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2712\nblender.exe :0x00007FF778A46A10 ED_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_edit.c:1729\nblender.exe :0x00007FF778A70B30 screen_animation_step_invoke K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_ops.c:4754\nblender.exe :0x00007FF777D74A30 wm_operator_invoke K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:1339\nblender.exe :0x00007FF777D6FE10 wm_handler_operator_call K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2340\nblender.exe :0x00007FF777D72F10 wm_handlers_do_keymap_with_keymap_handler K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2693\nblender.exe :0x00007FF777D720D0 wm_handlers_do_intern K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3020\nblender.exe :0x00007FF777D70B70 wm_handlers_do K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3161\nblender.exe :0x00007FF777D6A440 wm_event_do_handlers K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3775\nblender.exe :0x00007FF777D3EB60 WM_main K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm.c:642\nblender.exe :0x00007FF776EB2C60 main K:\\BlenderGit\\blender\\source\\creator\\creator.c:564\nblender.exe :0x00007FF7837A1B00 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7837A18B0 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7837A1890 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7837A1BC0 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFAE8F27020 BaseThreadInitThunk\nntdll.dll :0x00007FFAE9062630 RtlUserThreadStart\n\n```\n\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Painting across different resolution UDIM tiles in image editor crash.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\n\nIf you have UDIMs of different resolutions, and you paint in the Image editor window across the tiles, you get a crash.\nIf you do the same thing in the 3D viewport, there is no problem.[CrashFile.7z](CrashFile.7z)\n\n\nCreate a UDIM texture, with at least two tiles, of different texture resolutions. \nIn the image editor in paint mode, draw a line across the tiles and it will crash. Sometimes I need to draw two lines crossing the tiles for it to crash.\n\nThat's all, you don't need to apply the textures to a model or anything else.\n\n\n", "Huge memory usage when trying to paint on UVs far ouside the 0-1 range\nBroken: version: 2.82a (sub 7)\nWorked: Never\n\nBlender freezes when I attempt to use the paint options, after adding an image to Texture Paint. Memory will skyrocket from 150MB to 13GB and does not un-freeze.\nYoutube tutorial I'm following trying to learn to paint textures, bug happens after adding the image at 2:35, and I attempt to paint the model: watch?v=lmbAs9jE1vI\nI am very new to Blender, but pretty sure it shouldn't be doing that when attempting to use the Paint tools.\n\n\n\n- Open attached file\n- Try to paint the mesh\n\n[texture_paint_huge_memory_usage.blend](texture_paint_huge_memory_usage.blend)\n\n" ]

[ "wireframe/orthographic/front/side/topview crash 2.8\nOperating system: Windows 10\nGraphics card: gtx 1060 3gb\n\nBroken: 2.8, blender-2.80-c1f6ecdfabf-win64\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nblender crashes when in wireframe, front/side/topview and orthographic at the same time\n\n\nGo ino wireframe, go into front/side/topview and toggle orthographic.\n\nBased on the default startup or an attached .blend file (as simple as possible).[BlenderBug.blend](BlenderBug.blend)\n\nI updated my Nvidia drivers to the current release and my Blender version was downloaded today.\n\nHere's a Google drive Link to a video I made of the bug: \n\nview?usp=drivesdk\n" ]

[ "Box select shortcut is missing deselect tool tips\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\n\nBroken:\nBroken: 2.80, 2018-11-30\n\n\nThe circle select shortcut shows tool tips for deselect, the box select does not despite having the functionality.\n\n\n* Open blender, select new and pick \"General\".\n* Select the cube. (left click)\n* Enter edit mode. (tab)\n* Deselect all. (alt-a)\n* Enter box select mode. (b)\n* Select a vert (left click and drag)\n* Enter box select mode. (b)\n* Deselect a vert (shift left click or middle click)\n* Notice the vert has been deselected despite there being no tooltip\n\n", "3D Cursor tool todo\nIn Blender 2.80, we now have a special tool for transforming the 3D Cursor. The issue is that it's not easy to move it visually, using gizmos, to set a certain pivot point for transforms. We can support this via a toggle in the tool settings, enabled by default for the 3D Cursor toolL\n\n\n\nThis makes it so you can reposition and rotate the 3D Cursor using gizmos, like so:\n\n\n\n---\n\n * - [ ] {icon circle color=green} Add button in the Tool Settings to reset the Cursor position to 0,0,0\n * - [ ] {icon circle color=green} Add XYZ controls for 3D Cursor next to it\n * - [x] {icon circle color=yellow} Add Rotation XYZ controls for 3D Cursor in the Sidebar, next to location.\n\n", "The SHIFT key, mapped on my graphic tablet is not working in Blender 2.80\nOperating system: Windows 10\nGraphics card: NVidia GeForce GTX 1070\n\nBroken: 2.80 25-12-2018\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nI own a Huion NEW 1060 PLUS 8192 graphics tablet. One of my keys is mapped as SHIFT, but Blender doesn't recognize it at all. As one of the pen keys is mapped as the Middle Mouse Button.\nAnother key on the tablet is mapped as CTRL, another as ALT etc. and they all work with the MMB on the pen, but the SHIFT key is not recognizable to Blender. I can zoom, I can rotate, I can change views but i cannot pan nor select multiple objects. Basically, everything that is connected to the SHIFT key is dead.\nBlender recognizes the keyboard SHIFT key, as well as a mapped SHIFT shortcut on the mouse, but not on the tablet.\nAll around the OS and in Rhino, Photoshop, Illustrator, the Shift key from my tablet is working perfectly, but inside Blender no.\n\nOh, and this is the first time I'm trying 2.8. \nEverything works fine in 2.79.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Redo panel disappears during edits in Tweak tool\nOperating system: Win10 x64\nGraphics card: Nvidia 1070\n\n**Blender Version** \nblender-2.80.0-git.26d5a3625ed-windows64\n\nThe info panel for move disappears in edit mode if tweak mode is in action. This does not seem to happen if one uses \"g\" for grab instead.\n\n\n- Enable left click select, optionally select all toggles\n\n- In your space bar menu turn the select mode (W) on\n\n- Create a mesh and move into edit mode \n\n- Start grab and drag of verts and watch the move info panel at the left bottom\n\n- Now try the same thing with selecting a vertex then press \"g\" to move.\n\n", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n", "Switching collections does not work in Local mode.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 5)\nWorked: 2.81\n\nIn Local mode, switching collections with hotkeys (1, 2, 3 ...) does not work.\n\nWhen I select several objects from different collections, and go into local mode, switching collections through hot keys (1, 2, 3, etc.) stops working.\n\n", "Sample color add to palette, works for mouse click but not key press only\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA GeForce GTX 960M\n\nBroken: 2.80 2019-02-05 23:34\nWorked: (optional)\n\nUsing the **sample color** tool, **add to palette** option does not work properly.\n\n1. Press S+LMB with cursor on any color. The option **add to palette** is checked automatically(at the tool properties panel at the bottom left) and the color is actually added to the palette(tool properties bar at the top > brush).\n2. Press S with cursor on any other color(do not click). The option **add to palette** is still checked(because it remembers the last operation). new color is extracted and is now the foreground color. However it does not add the new color to the palette. Strange.\n3. Press S with cursor on any other colors(do not click). It behaves the same. **Add to palette** is checked but is not working.\n\n**Extra bug**\n1. Press S with cursor on any color(do not click). The option **add to palette** is not checked automatically.\n2. Try to enable the checkbox **add to palette**.\n3. Blender crashes.\n\nMaybe the solution is just to get rid of the checkbox **add to palette**.\nS is sampling color to foreground color, S+LMB is sampling color to palette. Why would we need the checkbox?\nIt is also possible to add the color to palette after sampling(to foreground color). This option doesn't seem necessary to me...\n\n[bug-samplecolortool-addtopalette.blend](bug-samplecolortool-addtopalette.blend)", "Timeline > Playback > Follow Current Frame Does not work if you drag the frame number widget.\nOperating system: Win 10\nGraphics card: AMD R7 200\n\nBroken: Blender 3.61 release.\nWorked: never, checked back till 2.83.20\n\nFollow Current Frame only works with keyboard arrow keys and ALT+Middle mouse button dragging in the timeline editor area\nDoes not work with the click and drag area of the Timeline header current frame box, or its arrow buttons\n\nAs show in attached video\n1. Open Default General file\n2. In the Timeline, Click on Playback > Follow Current Frame\n3. Drag the frame number widget, the frame indicator will go outside the region, while if use play or keyboard arrow keys, region follows the frame indicator.\n4. Expectation is that it should follow the frame, regardless of where the current frame is being changed from.\n\n", "Can't create a working shortcut for Extract Face Set\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\n\nCan't create a working shortcut for Face Set Extract. Creating one does appear in the Keymap, but not in the Face Sets menu. Can only manually use the operator in the menu to make it work.\n\n[Desktop 2021.09.05 - 05.28.09.02.mp4](Desktop_2021.09.05_-_05.28.09.02.mp4)\n\n1. Create a shortcut for Extract Face Set.\n2. Check that it is in the Keymap to be sure it's there.\n3. Pressing the keys to perform the shortcut will not work. The shortcut text will not appear in the menu as other shortcuts do in Blender.\n", "Eyedropper in object selection box doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce 920M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nBroken: version: 2.83 (sub 17)\n\nBroken: version: 2.90 (sub 2)\n\n\nI click on a specific eyedropper and then it doesn't work. Other eyedroppers that I know seem to work fine.\n\n3D Viewport > Sculpt Mode > Top Header Panel > Options > Orientation > Eyedropper in object box selection > Click on it\n\n[Based on the default startup]\n\n[2020-05-17 13-21-02.mp4](2020-05-17_13-21-02.mp4)\n\n", "error in custom view3d.move Keymap Setting\nOperating system: Windows11\nGraphics card: It doesn't matter\n\nBroken: up to 3.5.1\n\n\n\nBecause I often use the 2D features in Blender, and the pan view function in Blender is not very convenient (requires using Shift + MMB), I made the settings as shown in the picture to add a new pan view keymap to Spacebar + LMB. In the normal object mode, I can indeed pan the view by using the new shortcut, but once I switch to any other mode, this shortcut key will be disabled. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "NLA: Active Strip State lost when dragging Strip between tracks\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: Never Worked\n\nClicking on a strip and dragging or G dragging the Strip on the timeline on the same Track and then hitting TAB to enter tweak mode is working, but if I do the same thing but drag it to another TRACK then hit TAB I get an error\n\nOpen my example Blend file and select the \"Click and Drag Me to the Drag Strip Here track\" STRIP and drag it to \"Click and Drag Me to the Drag Strip Here track\" then hit the TAB key to enter tweak mode, you should see an error as shown in the image. \n\"No active strip(s) to enter tweak mode on\n\"\n\n\n\n", " Annotations are blended incorrectly (looks like added?) on viewport backgrounds in viewport renders\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER\n\nBroken: version: 3.0.0\n\nBlender renders colorful annotations as white while using the viewport render function, when the viewport background is set to be completely white.\n\n- Draw an annotation (e.g. blue)\n- Set the viewport background (via Viewport Shading) to \"Viewport\" and set it to be red (could be world as well if you like).\n- 3D Viewport > View > Viewport Render Image.\n- notice the blue annotation being added to red background (resulting in pink)\n- if you do this with a white background, you will think the annotations are gone (all strokes add to white... giving.... white :)\n\n[#93748.blend](T93748.blend)\n\n\n", "With ThinkPad keyboards Zoom does not work with the trackpoint and middle button\nOperating system: Linux ubuntu 22.04\nGraphics card: Intel HD4600 + NVidia GT730M\n\nBroken: 3.4.1\nWorked: Works correctly until Blender version 3.3.1\n\n\nIn previous versions of blender moving the trackpoint and pressing the center button of the trackpack on thinkpad keyboards blender zooms in and out. In version 3.4.1 it no longer does. In 3.4.1 rotates the wiev. Does not work with or without 3er button emulation. In previus versions it works correctly, does zoom in and out. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nStart blender move the track point while cicking the middle button on the trackpad.\nUntil blender 3.5 it does zoom, in 3.4.1 rotates the view. (I think in some alpha 3.4 it works but not in 3.4.1)", "Circle Select on a Curve in Edit Mode = _BLI_assert_abort for Pydebug of Blender 3.2\nOperating system: Windows 11\nGraphics card: Nvidia 3070ti\n\nBroken: 3.2 pydebug\nWorked: unknown\n\nIf you use circle select to click in viewport in edit mode of a curve object in Blender 3.2 Pydebug in VS 2019 (python/native debugging) it will crash and give you _BLI_assert_abort.\n\n```\nucrtbased.dll!issue_debug_notification(const wchar_t * const message) Line 28\n\tat minkernel\\crts\\ucrt\\src\\appcrt\\internal\\report_runtime_error.cpp(28)\nucrtbased.dll!__acrt_report_runtime_error(const wchar_t * message) Line 154\n\tat minkernel\\crts\\ucrt\\src\\appcrt\\internal\\report_runtime_error.cpp(154)\nucrtbased.dll!abort() Line 61\n\tat minkernel\\crts\\ucrt\\src\\appcrt\\startup\\abort.cpp(61)\nblender.exe!_BLI_assert_abort() Line 47\n\tat E:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c(47)\nblender.exe!BKE_editmesh_from_object(Object * ob) Line 59\n\tat E:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\editmesh.c(59)\nblender.exe!em_setup_viewcontext(bContext * C, ViewContext * vc) Line 4359\n\tat E:\\blender-git\\blender\\source\\blender\\editors\\mesh\\editmesh_select.c(4359)\nblender.exe!view3d_circle_select_recalc(void * user_data) Line 4614\n\tat E:\\blender-git\\blender\\source\\blender\\editors\\space_view3d\\view3d_select.c(4614)\nblender.exe!view3d_circle_select_modal(bContext * C, wmOperator * op, const wmEvent * event) Line 4639\n\tat E:\\blender-git\\blender\\source\\blender\\editors\\space_view3d\\view3d_select.c(4639)\nblender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties, const unsigned char * kmi_idname) Line 2327\n\tat E:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c(2327)\nblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3227\n\tat E:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c(3227)\nblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3279\n\tat E:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c(3279)\nblender.exe!wm_event_do_handlers(bContext * C) Line 3869\n\tat E:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c(3869)\nblender.exe!WM_main(bContext * C) Line 626\n\tat E:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c(626)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 551\n\tat E:\\blender-git\\blender\\source\\creator\\creator.c(551)\n[External Code]\n\n```\n\nDefault startup, object mode, add bezier curve, go into edit mode, switch to circle select, click viewport. Also happens with circle, nurbs curve, nurbs circle, and path." ]

[ "Annotations (D) do not work with 3d cursor tool (keymap issue)\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 MB\n\nBlender 2.80 Alpha 2\nHash: c94f806dc73\n\ndate: 2018-11-14 22:51\n\nAnnotation tool does not work when pressing D and LEFT MOUSE BUTTON.\n\nAnnotation tool will work when searching with CMD+F; but also within the search, if you click ENTER the annotation tool will pop up for a split second and disappear. \n\nAttaching a short video.\n[Annotation Bug.mov](Annotation_Bug.mov)\n" ]

[ "Dynamic Paint evaluated even when disabled\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 473.04\n\nBroken: version: 3.3.1\nWorked: (Unknown)\n\nAfter disabling the Viewport Display and Render options for both the Canvas and the Brush in the Dynamic Paint settings, the system continues to be evaluated during timeline playback, resulting in a very low frame rate. The only way to fix this is to completely delete the **Dynamic Paint modifier** from **both** the Canvas **AND** the Brush. This is not ideal, as settings need to be tweaked in between testing an animation, so the system **should be properly bypassed** when the Viewport Display and Render options are disabled.\n\nThanks very much for looking into this!\n\n**[exact steps needed to reproduce the issue]**\n\nPlease see example .blend file. The landscape mesh is used as a proximity brush to paint \"shoreline\" interaction onto an animated canvas. The project exhibits the same low frame rate even when the Dynamic Paint modifiers have their Visibility and Render settings disabled. Only by completely deleting the modifiers, does the the frame rate return to normal.\n\n\n\n[DYNAMIC PAINT TEST FILE.blend](DYNAMIC_PAINT_TEST_FILE.blend)\n\n", "GPencil: Texture Image Alpha pass through grease pencil strokes\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83.1\n\nContext: Using texture image to make some kind of 2d fur on top of a GPencil Object\n\nThe Image Texture used to make some fur is mostly transparent and the brush used to make the colored part is a texture paint brush with Cloud Mask (it was made entirely in Blender with Blender tools).\n\nWhen on top of the GPencil object, the part of the Image Texture that is only half transparent(between 99%-1% transparent), makes the GPencil color disappear, even when moving the center point behind the one of the fur images.\n\nOn the contrary, when on top of another Image Texture (imported to be used as camera mapping), the Image Texture of the fur doesn't impact the transparency of that one.\nNotice that the Image texture boundary, even from the imported one, has problems with clipping and always makes a white line appear.\n\n- Open attached .blend file\n- Zoom in and out to notice the alpha transparency influencing the GP object\n\nThanks for your help!\n\n\n\n\n\n\n\n[bug_alpha.blend](bug_alpha.blend)", "custom brushes icon won't show up is some cases\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.91.0\n\nIn some cases the custom icon of the brushes won't load properly. Even by reassigning it it doesn't work.\n\nOpen the attached file and try to assign the accatech custom icon to the active brush (but anykind of image won't load)\n\nThankyou\n\n\n\n[icon.blend](icon.blend)", "Modifier sub-panel drawn over selection outline\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.1.0 Alpha\n\nThis is just a visual bug and nothing serious, but I wanted to point out that the sub-panel background is drawn on top of the selected modifier outline, which causes it to look broken up when expanded. This is visible but not obvious in the default theme, but very obvious in custom themes where the sub-background alpha is set to 1. \n\n\n\n1. Add a Bevel or Subdiv modifier\n2. Expand a sub-panel \n3. Set the properties editor Sub Background theme color to an alpha of 1 \n\n", "Weight Paint gradient operators wait for mouse input\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nThis is based on feedback from #108791\nWhen using the gradient operators in weight paint mode, they don't start on shortcut press but require a mouse press to start and release to confirm.\n\nThis worked well with the previous default shortcut with mouse clicks but when reassigned to keyboard shortcuts this is very inconsistent with other operators in Blender and seems unintentional or outdated.\n\nA good counter example for a better behavior is \"Expand by Topology\" in sculpt mode, which only waits for mouse input if started from a menu. If executed with the keyboad shortcut `Shift A` it will start and then confirm with `LMB`.\nIf the shortcut is remapped to a mouse press, it will start on press and confirm with release. \n\n- Enter Weight Paint Mode\n- Press `Shift A` and use the operation\n- Try the same in Sculpt Mode\n\n", "Grease pencil. Mask not working when masking layer has more than one keyframe\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nWhen my masking layer has only one keyframe, masked layers display as expected. When my masking layer has more than one keyframe expected masking doesn't happen.\n\n* open .blend (the mask layer has two keyframes, both having the same filled shape)\n* expected result: the strokes on the 'marks' layer that intersect the shape on the mask layer are always visible\n* actual result: the strokes on the 'marks' layer that intersect the shape on the mask layer are only visible after i delete the second keyframe on the 'mask' layer\n\nWhile dragging the timeline play head the marks layer appears as expected, correctly masked. But when i release the mouse button the marks layer disappears entirely again.\n\n[isthisamaskbug.blend](isthisamaskbug.blend)", "Grease Pencil Erase /Tablet\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.1\n\nWhen i use the eraser in dissolve mode strength 0.5 with the mouse it has a very soft effect.\nDoing the same with the Stylus(Cintiq Pro 24) the effect is very harsh even with pressure disabled. To have the same effect like with the mouse i have to reduce the strength to a tiny amount. Like 0.01 . I seems like the tablet input is retrieved at a higher rate then the mouse input . Maybe it's the same problem with tint, as i described in my last report.\n\nJust erase at the current layer in the attached file\n\n", "Grease Pencil Draw Tool Settings displayed in the wrong context\nversion: 2.80 (sub 74), branch: master, commit date: 2019-07-05 21:52, hash: a0f3...\nbuild date: 2019-07-06, 01:03:01\n\n\n\n**To reproduce:**\n\n - Create a Grease Pencil Object\n - Enter Draw Mode\n - Display tool settings, either in the header or the properties window\n - In the toolbar, click on the Erase or Fill tool\n - Now click on one of the Add tools (Line, Arc, Curve, etc.)\n - Look at your tool settings\n\nNote that when you switch from the Erase or Fill tool to an Add tool, the settings do not change to the correct ones! Instead, the settings or the Erase or Fill tools remain. You have to select the draw tool before selecting an add tool in order to refresh the settings. \n\nThis bug appears for the tool settings in both the properties window and the header.", "Grease Pencil problem (especially soft pencil) \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nSince couple version of Blender I cannot use a soft pencil (mainly) brush in Grease Pencil 2D animation mode. The issue depends on how much You zoom. When You zoom in and use same size it's not visible. When You zoom out and draw with same size dots are visible. \nIt's behavior is very strange now and produces bad results (visible dotted lines or other which are visible on attached file. Some of these issues occur when the brush is small (line type set as dots). This is much more more visible when stroke stabilization is on. The bug was not there about 2 years ago and I was able to use the soft pencil without such problems. When line type is set to line the pencil stroke has strange contour around and when self overlap is off it produces artifacts on edges. \n\n\n\nJust choose a soft pencil and make it small. Check it with stroke stabilization as well. Then change the line type to line with self overlap on and off. \n\n", "Draw Face Set brush bug\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 3.0.0 Alpha\n\nDraw Face Set brush doesn't work properly and select faces randomly\n[DjHiCdF9fE.mp4](DjHiCdF9fE.mp4)", "Update \"Input Samples\" settings as brush data\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\nCurrently the brush setting \"Input Samples\" (`tool_settings.sculpt.input_samples`) is stored in `bpy.data.scenes[\"Scene\"]`.\n\nTo follow useful conventions with other brush settings, this should be updated to be stored in `bpy.data.brushes[\"Brush\"] instead. For the use case of having the input samples unified between all brushes, an additional scene property `bpy.data.scenes[\"Scene\"].tool_settings.unified_paint_settings.use_unified_input_samples` should be added, including a a button to toggle it in the UI.\n\nA mockup:\n\n\n\n", "Duplicate Shortcut, Smooth Brush and Stabilize Stroke (Sculpt Mode)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\n\nSmooth Brush and Stabilize Stroke use the same \"Shift + S\" shortcut. And only the smooth brush shortcut works.\n\n\n\n", "Grease Pencil ignores collection Line Art usage settings\nversion: 3.3.0 Beta, branch: master, commit date: 2022-07-28 22:39, hash: 6ca602dd9fa1, type: release\nbuild date: 2022-07-29, 00:21:12\nplatform: 'Windows-10-10.0.22000-SP0'\n\nrenderer:\t'NVIDIA GeForce RTX 3090/PCIe/SSE2'\nvendor:\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 516.59'\n\nGrese Pencil ingnores Collections Line Art usage settings. See my attachment and screenshot.\n\nOpen the attached file and check the line art settings in the torus collection.\n\n\n\n[gpencil_outlines-test-3_3.blend](gpencil_outlines-test-3_3.blend)", "Dot dash modifier not working with time offset modifier (grease pencil)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\nWorked: not sure\n\nWhen time offset modifier is in the modifier stack before or after dot dash, dot dash has no effects{[F12118899](dot-dash-time-monkey.blend)}\n\nSee attached file\n\n", "Brush icons show all the same under Draw\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-10.14.74\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79\n\n\nWhen choosing a brush type under draw, all icons show the same. \n\n1. Select Weight Paint\n2. Select Draw Brush\n3. In the properties panel choose Tools\n4. Select Brush type\n\nIn 2.79 there would show different icons for different types. This new method is a bit confusing now but also shows the same icon for eah and every type. Not sure why these havent been update before the UI Freeze\n\n\n\n\nAlso Smear uses a copy brush, its shows as Smear.001\n\n\nSame as in workspace, there are quite a couple of names which should not be there. This is the default startup file, notice those default.00 numbered screens. Seems like old leftovers. Ive noticed them for months now.\n" ]

[ "Grease pencil: top bar draw tool settings don't appear until material properties tab is clicked\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\nCaused by e3faef686d\n\nOn a new blank grease pencil object, the top bar draw tool settings don't appear until material properties tab is clicked. Expected behaviour: top bar draw tool settings are always visible in draw mode.\n\n\n\n* open new 2d project\n* delete default 'stroke' grease pencil object\n* add new 'blank' grease pencil object\n* select draw mode - top bar settings are missing\n* click material properties tab, top bar settings appear.\n" ]

[ "Viewport gizmos in selection tools not updating.\nOperating system: Windows 10 64Bits\nGraphics card: GeForce GTX 1050 Ti latest driver\n\nBroken: version: 2.80.69 hash:4f6e25280558\n\nswitching between Active tools gizmos and viewport gizmos keeps the manipulators in it's previous position until a second selection...i assume because we have two different and unrelated gizmos!! \n\n\n- Activate transform gizmos in the gizmo popover.\n- Use Active tools manipulators and do transformation.\n- Switch to the selection tools.\n\nThe gizmo center is not updated.\n\n**Attachment**\n", "UI: Gizmo's tooltips appear after pressing\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 2.92.0 Alpha, branch: master\nWorked: none\n\nClicking on button, or pressing and holding - prevents the tooltips from appearing.\nBut it doesn't work that way for gizmos. This leads to an annoying flickering of tooltips.\n\nSo, you hover and press on the gizmo - a tooltip appears;\nyou move, stop and release - tooltip appears again.\n[#83589.mp4](T83589.mp4)", "Copy/Paste Behavior in Viewport\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M390 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.15\n\nBroken: version: 2.91.0 Alpha\nWorked: Never worked in 2.8+\n\nWhen pasting an object, the gizmo is not positioned at the newly created object, where you would expect it to be. Instead, there are two cases - both seem to be not intended.\nThe pasted object also is not active for direct manipulation despite the visual indication with the gizmo.\n\nIf there is a selection somewhere else before pasting, the gizmo ends up in the wrong position. Example:\n\n\nIf there is no selection before pasting, there is no gizmo appearing at all. Example:\n\n\nA directly interconnected problem is that pasted objects are not made active despite having an attached Gizmo. Example:\n\n\n**Potential fix**\n1. The gizmo could always appear and show where the object is pasted (belonging to the new object).\n2. The pasted object could become active. When multiple objects are pasted, the selection and active states of the copied objects could be transferred to the newly pasted ones. Also, all previous selections could be deselected after pasting.\n\nThank you :)\n", "'Solve Camera Motion' operator sometimes prevents Auto Save from running\nBroken: 3.5.1, 3.6\nWorked: maybe 3.4\n\nInvestigated in #107421 by @3di.\nIt's still unclear when this happens, but it could be replicated with the attached file.\nThe function `void wm_autosave_timer(Main *bmain, wmWindowManager *wm, wmTimer * /*wt*/)` in `wm_files.cc` skips AutoSave if any modal operators are running.\nIn this case, this can happen with the `\"CLIP_OT_solve_camera\"` operator even after the operation is theoretically completed.\n\n- Unzip attached .blend file\n- Go to \"Motion Tracking\" workspace\n- In the solve tab, press `Solve Camera Motion`\n\nAuto Save stops saving or saves very late.\n\nno%20autosave.zip?dl=0\n\n", "Sculpting - Cloth brush - Snake Hook deformation not working\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\n\nBroken: version: 3.5.0 Alpha\n\nThis is the image I got after kept dragging my cloth brush around the same spot for a few times:\n\n\nand this is the file I'm using:\n[20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend](20221206_sculpt_cloth_brush_snake_hook_donot_work_0001.blend)\n\nI personally think the option is 'wired' to a wrong block of code.\n\n", "EEVEE-Next: Known Issues\nThis task lists the minor missing features that are known for not yet working with EEVEE-Next.\n\nPriority of each task needs to be assessed and assigned.\n\n# LookDev\n- [ ] camera world alignement isn't working.\n- [ ] blur background isn't working.\n- [ ] diffuse contribution isn't taken into account.\n\n# Shadow\n- [ ] big performance bottleneck caused by rendering method\n\n# Hardware support\n- [ ] Metal backend doesn't support shadow rendering and GI baking yet", "Blender crashes when using temp_override on 'UV' area with transform.translate, transform.resize\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.3.5\nBroken: version: 3.4.1\nBroken: version: 3.5.0\nWorked: none\n\nWhen executing `transform.resize` or `transform.translate` with `context.temp_override(area=uv_area)` Blender crashes. This happens when the area.ui_type is UV, with VIEW_3D is works fine.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF72DEF3C80\nModule : blender.exe\nThread : 000009dc\n```\nthe complete crash file is attached\n\n1. create a new Text and paste the below code into the text (the attached file issue.blend can also be used)\n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nwith context.temp_override(area=area):\n bpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n bpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n2. run this text, Blender will now crash\n\n**Note**: not using `temp_override()` and executing these operators in the current context with the ui_type set to UV works fine. Like this: \n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nbpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\nbpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n\n", "HDRI animation bug in eevee\nThe HDRI illumination shouldn't change on the cube, because every thing including the HDRI is rotating at the same speed. \nHowever, this went wrong in EEVEE... It seems that in Cycles everything went on so well.\n\nThis is a simplified bug presenting file of a complex scene which I found this bug, in which I have to rotate an object, a HDRI and camera together, and I'm struggling to get rid of this bug...\n\n[BugReport.blend](BugReport.blend)\n\n[0001-0096.mkv](0001-0096.mkv)\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.1\n\n\n\n", "Spin Duplicate Tool gizmo uses the wrong operation\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nThe gizmo of the Spin Duplicate tool in the toolbar uses executes the wrong operation. Instead of using the Spin Duplicate operation it will use the Spin operation.\n\nTo get the correct behaviour, try changing the \"Drag\"setting in the header tool settings to \"Active Tool\".\nThen click and drag anywhere.\n\n----\n\nI also want to include the proposal to just merge the Spin and Spin Duplicate tools and instead add an option in the tool settings called \"Use Duplicates\".\nBoth tools use the same operator anyway with the only difference that this one option is toggled.", "Sculpt mode pivot ignores object transform when pivot mode is \"Active Element\"\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 3.4.0\nWorked: unknown\n\nWhen the pivot mode is set to \"Active Element,\" the sculpt mode pivot location ignores the transform of the object.\n\n- move and/or rotate default cube\n- Set `Transform Pivot Point` to `Active Element`\n- To see the pivot position, enable `Move` Object Gizmos (in popover of `Viewport Gizmos`)\n- enter sculpt mode. (note that the pivot has moved back to origin)\n- Go to {nav Sculpt > Set Pivot} and run any of the `Set Pivot Operation` operators (such as `Pivot to Origin`, `Pivot to Unmasked`, `Pivot to Mask Border`, etc)\n\nThe pivot location will be relative to the world origin, not the transformed object (which is also active).\n\n---\nTo be honest, it's strange to me that operations such as \"Set Pivot -> Pivot to Mask Border\" generate a pivot that's different for different pivot selection modes in the first place --- it's very unintuitive for the pivot location to not appear at the actual (world space, post-transform) mask border when you run an operation that's supposed to set it to that location. I haven't thought through the nuances of sculpt pivot vs 3d cursor vs pivot mode interaction, though, so maybe there's a good reason for this --- in which case take this as UX feedback that I spent an hour trying to figure out why my pivots weren't working before finding this issue :)\n\nAt any rate, the Active Element behavior seems broken", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)", "Limit scale bone constraint: \"affect transform\" doesn't seem to work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: **2.83**LTS from steam, **2.92**release and **2.93.0**Alpha\nWorked: don't know\n\nContrary to the manual, the \"affect transform\" option does not limit the transform values (not visible).\nAlso when using limit scale as a bone constraint the minimum scale is not used, instead uses maximum as both being the min and max exactly the same number but in negative value.\n\n- Open attached file\n- Scale the bone beyond the limits\nNote that the scale values in the transform panel have not been clamped.\n[scale bone.blend](scale_bone.blend)\n", "Rotation/Move support for Transform Cage\nThe idea is have a Transform Cage to move, rotate and scale in the 3D viewport (similar to the gizmo that exists for 2D UV editing).\nThis is will be realy useful for Grease Pencil and 2D animation workflow and is common in other 2D animation programs.\n\nPlease, check this video for more info:\n[Tramsform Cage2.mp4](Tramsform_Cage2.mp4)\n\n\nDaniel\n\n----\n\n\n****is this just the current scale cage with rotation handles added?***\nYes, basically. It would be nice if you grab an edge of the cage you have a skew transform (see the video)\n\n[2020-02-13 01-53-56.mp4](2020-02-13_01-53-56.mp4)\n\n***Would the pivot point be used only for rotation or scale as well?***Yes, for all tranformations***Would it be possible not to use this pivot point, and use the 3D cursor instead?***It´s is possible but I think that is more convenient and easy for the user***How this is accessed (As a sub-tool of transform? like scale cage?)***\nYes, as a sub-tool of transform\n\n", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Crash Python API - GPUOffScreen.draw_view3d() crashes blender with draw_type = POST_VIEW but works with draw_type = POST_PIXEL\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.1\n\nWhen using [GPUOffScreen.draw_view3d() ]] in a [[ https:*docs.blender.org/api/current/bpy.types.Space.html?highlight=post_view#bpy.types.Space.draw_handler_add | draw_handler ]], blender crashes when running the [[ gpu.shader.html?highlight=gpu+shader+from_builtin#built-in-shaders | 3D_IMAGE builtin shader ](https:*docs.blender.org/api/current/gpu.types.html?highlight=draw_view3d#gpu.types.GPUOffScreen.draw_view3d) if the draw_type was set to POST_VIEW but works if the draw_type was set to POST_PIXEL.\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script Crash3D and blender will crash\n\n\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script NoCrash2D, and it will draw the camera view in the viewport without crashing\n\nAttachments:\n\n[CrashScriptDrawView3D.blend](CrashScriptDrawView3D.blend)\n[blender.crash.txt](blender.crash.txt)\n\n\n\n\n\n\n" ]

[ "Blender 3.2 Beta Area & Spot Light gizmos not working as expected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0 Beta\nWorked: I think 3.2 Alpha, and even 3.2 Beta week ago was OK.\nWhen interacting with Area and Spot light, gizmos don't work. Arrows of transform gizmo seem to be inactive. Only after using \"G\" keyshortcut and moving the light around, gizmos activate, and yuo are able to operat normally.\nBefore that with Area Light, translate gizmo resizes the shape of the area light.\n\nAdd area light nad try tu use gizmo (any) to interact with it.\nActually only Point and Sun Lights react instantly. But when user changes the type of the light from these to to Area or Spot, gizmos become inactive.\n\nBased on the default startup, empty, new blend file.\n\n[2022-05-03 14-28-28.mp4](2022-05-03_14-28-28.mp4)" ]

[ "Adjusting spotlight blend using gizmo does not register undo\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nThe gizmo control is introduced in 3c8c0f1094.\n\nAdjusting spotlight blend using gizmo does not register undo\n\n[SpotlightBlendGizmoBrokenUndo.mp4](SpotlightBlendGizmoBrokenUndo.mp4)\n", "Mesh-based armature interaction (\"Mesh Gizmos\", \"Face Maps\")\n# Preface\n\nThe current way of interacting with bones in a production environment is based on Custom Shape Objects, which can disappear inside the mesh, be at a completely different place from the area they control, and in general require a fair bit of design from the rigger and learning from the animator to efficiently use.\n\nUsing the Python Gizmo API, I created a prototype of an alternative system, where we can click on geometry on the deformed mesh itself to select bones and control said mesh.\n\nThe goals of this task are:\n- Gather feedback from animators and riggers.\n- Finalize a design, to the extent that is possible within the limitations of a Python prototype.\n- Find developers who could implement this in core Blender.\n\n### The Prototype: \"Bone Gizmos\" add-on\n\n[Video: Setting up a single bone gizmo](attachment)\n[Video: The add-on in use](attachment)\n\n\nYou can [download the addon](bone_gizmos) as part of the Blender Studio Pipeline. You have to download the whole repository from the repo's home page, then extract the `bone_gizmos` folder into your addons folder.\n\n### Features\nA list of proposed features, partially working in the prototype, although there is plenty of space for UX discussions.\n\n- A gizmo's shape can be:\n - An entire object (in the bone's local space, with the already existing transform offset options applied)\n - A vertex group/face map/any attribute of an object (in world space).\n- Gizmo Colors:\n - There are three states to worry about: Unselected, selected, hovered.\n - Currently, user can specify two colors: Unselected and Selected. Hover-state is indicated by opacity ONLY. Having only one color, or three colors, is something to discuss.\n - The colors can be taken from the bone group's colors, if the bone has a group assigned, or set uniquely on a per-bone basis.\n - Colors should actually NOT be this customizable. Instead, users should be forced into a set of pre-defined colors, that can only be customized at the Theme level.\n- Gizmo Display:\n - A gizmo's visibility is based on the bone's visibility; From user POV, a bone and its gizmo should be a single entity.\n - If the selected object/vertex group cannot be used to construct any faces, draw the edges with line drawing instead.\n- Interaction:\n - Since it's just a prototype, it's currently left-click only, and doesn't account for mouse drag threshold, which is very bad for auto-keying. In the final implementation, it should behave the same way as bones do now, except:\n - Default transform mode: Translate/Rotate/Scale, including trackball rotation, rotating along view, and locking any transformation to 1 or 2 axes. These defaults are defined by the rigger on a per-bone basis, and can be bypassed by the animator with a button press, or in a nuclear fashion by disbaling them altogether as a user preference.\n - Snapping: It is possible, only through Python, to specify an operator name and parameters that should be executed when a gizmo is touched. This can be used for automatic IK/FK snapping. But it would need an interface similar to a Keymap entry, where we can pick an operator and feed it parameters.\n\n\n**Design Questions**:\nWhile making the prototype, I ran into some design questions where the answers aren't so simple:\n- Ways to minimize set-up time? Currently, each gizmo needs a vertex group. That's fine, but may need workflow operators to quickly switch from Pose Mode to Edit Mode on the relevant mesh.\n- How to avoid overlapping gizmos? I think there are cases where they might be necessary, and a system that allows the rigger to create bone layers that are mutually exclusive, would be a potential solution.\n- If there is more than one way to deform some geometry (eg.: Shape Key, Armature, Lattice), how to communicate which out of several potential controls was used to achieve the current shape?\n\nThere might be no perfect answer to all of these, but they are things to keep in mind and mitigate.\n\n### Prototype Limitations\nThese issues are listed just to clarify that these behaviours are known, and would most likely be easy to fix/avoid in the final implementation, but can't really be addressed in the prototype:\n\n- - [ ] Mouse hovering does not take depth into account. This was fixed! [#94794]\n- Visual depth culling stops working when gizmo is being hovered. [#94792]\n- Transparent lines appear between the triangles. [#94791]\n- Currently the mouse movement threshold user preference is not being taken into account, which is terrible when trying to use the system with auto-keying enabled.\n- Performance is poor; Grabbing the vertex positions from the evaluated mesh takes about 2ms per gizmo.\n- Interaction is always with left click and cannot be customized.\n- Gizmo can not be visible during interaction.\n- When the mesh is modified, user must press a Refresh button to synchronize the gizmos.\n- Renaming bones will leave a gizmo orphaned, don't do it! :D \n\nFeedback and discussion welcome! Also about how to structure this document.", "Light of 'Area' type lamp presents artifacts when placed at great distances\nOperating system: macOS-13.4.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: versions: 3.1 to 4.0a \n\nArtefact's appearing with bigger Arean Light distances and spread angle 0.1 to 20~ \n(Like for space scenes with bigger distance Area lights for better sun effects...)\n\nJust open one of the files or follow the image below to set up the light.\n\n", "GizmoGroup with setup_keymap() doesn't work if addon is enabled by default\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: all versions so far\nWorked: never\n\nIf an addon is enabled by default, any of its GizmoGroup with setup_keymap() classmethod won't react to user input (if they are registered in the register() function). However, if they are registered during the normal operation (i.e. after Blender initializes and draws the first frame), the problem does not appear.\n\n1. Install the attached addon.\n2. Enable the addon (it's called \"!Gizmo test!\").\n3. Save Blender preferences.\n4. Close Blender.\n5. Open Blender.\n6. Select a camera and try dragging the circular gizmo. The gizmo won't react to the input.\n7. Disable the addon, then enable it again.\n8. Select a camera and try dragging the circular gizmo. Now it will rotate the camera.\n[gizmo_test.py](gizmo_test.py)", "Selection to Active doesn't work when the selected object is a child of the active object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0 Beta\n\n\nSelection to Active operator doesn't work when the selected object is a child of the active object.\n\n\n1. Add 2 cube.\n2. Parent one of the cubes to the other.\n3. Select both cubes such that the parent is active. \n4. Use the Selection to Active operator.\n5. The operator has no effect.\n\n", "Annotations (D) do not work with 3d cursor tool (keymap issue)\nMacBook Pro (Retina, 15-inch, Mid 2015)\n2.5 GHz Intel Core i7\n16 GB 1600 MHz DDR3\nAMD Radeon R9 M370X 2048 MB\nIntel Iris Pro 1536 MB\n\nBlender 2.80 Alpha 2\nHash: c94f806dc73\n\ndate: 2018-11-14 22:51\n\nAnnotation tool does not work when pressing D and LEFT MOUSE BUTTON.\n\nAnnotation tool will work when searching with CMD+F; but also within the search, if you click ENTER the annotation tool will pop up for a split second and disappear. \n\nAttaching a short video.\n[Annotation Bug.mov](Annotation_Bug.mov)\n", "Sculpt mode: Pose/Cloth gizmos/cursors remain visible when switching to other tools \nOperating system: Win 10\n\nBroken: blender-2.92.0-165b4f85ec23-windows64\nWorked: 2.90\n\nThe gizmos/cursors of tools like Pose and Cloth remain visible when switching to other tools that shouldn't have cursor... which wasn't the case in 2.90...\n\n[2020-10-24_21-16-50.mp4](2020-10-24_21-16-50.mp4)", "The Shortcut keys of Play Aniamtion not work in Spreatsheet Editor\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nThe Shortcut keys of Play Aniamtion({key Space}) not work in Spreatsheet Editor\n\n[play animation bug.mp4](play_animation_bug.mp4)\n\n", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "Sculpt mode pivot ignores object transform when pivot mode is \"Active Element\"\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102\n\nBroken: version: 3.4.0\nWorked: unknown\n\nWhen the pivot mode is set to \"Active Element,\" the sculpt mode pivot location ignores the transform of the object.\n\n- move and/or rotate default cube\n- Set `Transform Pivot Point` to `Active Element`\n- To see the pivot position, enable `Move` Object Gizmos (in popover of `Viewport Gizmos`)\n- enter sculpt mode. (note that the pivot has moved back to origin)\n- Go to {nav Sculpt > Set Pivot} and run any of the `Set Pivot Operation` operators (such as `Pivot to Origin`, `Pivot to Unmasked`, `Pivot to Mask Border`, etc)\n\nThe pivot location will be relative to the world origin, not the transformed object (which is also active).\n\n---\nTo be honest, it's strange to me that operations such as \"Set Pivot -> Pivot to Mask Border\" generate a pivot that's different for different pivot selection modes in the first place --- it's very unintuitive for the pivot location to not appear at the actual (world space, post-transform) mask border when you run an operation that's supposed to set it to that location. I haven't thought through the nuances of sculpt pivot vs 3d cursor vs pivot mode interaction, though, so maybe there's a good reason for this --- in which case take this as UX feedback that I spent an hour trying to figure out why my pivots weren't working before finding this issue :)\n\nAt any rate, the Active Element behavior seems broken", "Gizmo and transform direction does not align with Normal Orientation and Individual Origins\nOperating system: Linux-5.15.0-41-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.4.0 Alpha\nWorked: 2.83\n\nThe gizmo axes orientation should give a preview of the transform direction of the selected elements.\nBut the behaviour is breaking when using **Normal** orientation and **Individual Origins** for the pivot point.\n\nIn Object Mode when selecting a single object it behaves like expected. But when selecting multiple objects, the gizmo and transforms will use the Median Point pivot point instead. I don't know if this is the intended behaviour.\n\nMore striking is the behaviour in Edit Mode. If a single vertex is selected, the behaviour is as expected. The gizmo and transforms will use the normal orientation of the individual single vert.\nBut once more verts are selected the gizmo no longer matches the transforms.\nThe gizmo seems to match the median point orientation. But once a gizmo handle is dragged, it will use something else.\nThis often leads to flipped directions on transforms.\n\n**Note on behaviour in Blender 2.83**\nWhile this behaviour worked as expected in that version and earlier, it still failed to show the correct orientation when more than 2 verts were selected.\nOf course not all individual orientations can be displayed with 1 axis. But when the selected individual elements are connected, they will move as one. This behaviour should be reflected in the gizmo orientation as well.\nIf the selected individual elements would not move in unison, the gizmo could show the combined average as a good enough estimation.\n\n- On the default cube, enter edit mode\n- Set orientation to Normal and pivot point to Individual\n- Make the Move Tool active in the Toolbar\n- Select 2 vertices that form an edge and drag along the X handle\n- If it moves as expected, select the 2 vertices again but in the reverse order\n- Then repeat", "modifier display/render driver not responding.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\nWorked: unknown\n\nIf I have my Mask display/render driver from another objects display/render setting, changing controlling obj disp/render doesn't take effect without coaxing.\n\n1. Open the attached file. \n2. In outliner, disable the viewport display of the Cube object (drives Mask visibility of part of Sphere object)\n3. For the Mask modifier, slide the Threshold a little. Display effect now takes place.\n\nThis all works without a problem if I animate the Cubes visibility. This appears to be a problem for any/all modifier display drivers (e.g., Subdiviison). Sometimes I just need to hover over a value like Threshold, or just over time it responds to the change.\n\n", "Modal keymap for snapping in the `Corner Pin` widget has no effect\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bottom bar states that pressing ^ will enable snapping, but it seems it does nothing.\n\n\n\n1. Create a new default file;\n2. Go to the compositor;\n3. Enable nodes;\n4. Add a viewer node (this allows you to resize and test different sizes for the `Corner Pin` Gizmo);\n5. Add a `Corner Pin` node;\n6. Edit the `Corner Pin` widget and try to snap.\n", "Mirror UI in does not update immediately when a shortcut is assigning \nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: NVIDIA GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.2.0\nWorked: for sculpt mode it used to work in blender 2.80-2.92, broke in blender 2.93 and up. \n\nAssigning a shortcut to the mirror widget in any mode does not immediately trigger a ui update when pressed.\n\n- Enter sculpt or any other mode\n- Assign shortcut to the mirror x widget, v for example since its unassigned by default \nUI does not update immediately when pressing the shortcut, mouse cursor need to hover over the ui to trigger the update, this used to work in 2.80-2.92, but since 2.93 and up the ui does not refresh after pressing the shortcut. \nVideo of the issue:\n[Blender 2022-07-02 14_30_21_Trim_Trim.mp4](Blender_2022-07-02_14_30_21_Trim_Trim.mp4)", "Gizmo shifting to different value after release with tablet input.\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16\n\nBroken: version: 2.90.0\nWorked: 2.79 (haven't tested this extensively)\n\nWhen using a tablet to manipulate objects, the gizmo will often pop to a different location. A similar thing happens in the dopesheet when moving the playhead, it will pop to a different (usually very close) frame. I assume this is due to how the tablet input is being interpreted but after exploring and changing every setting I can find, the problem still persists to a certain degree. \n\nBasically, just select an object, choose the rotate tool (not the r shortcut) and use a tablet to rotate on an axis. I've attempted to record this issue in the attached video. [tablet issue.mp4](tablet_issue.mp4)\n\n" ]

[ "Gizmo Bug\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 525M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.2.0 Beta\n\n[The transform gizmos won't work on some objects like Camera and Area Light]\n\nOpen Blender, create a area light, try to move, rotate, or scale with the respective gizmos\n[{[F13049867](Bug.blend)}]\n\n" ]

[ "Blender freezes when calling an operator after a dialog window.\nOperating system: Windows 10 x64\n\nBroken: 2.80 win64, 2019-04-01 19:15\nWorked: 2.79b win64, release\n\n\nIf an operator from `bpy.ops` is called after a dialog window / popup is closed, Blender freezes and has to be manually terminated. A script to reproduce the error is located at the bottom of this task description.\n\n\n - Copy / Paste the code at the bottom of the task description into Blender's text editor\n - Press \"ALT P\" to run the script\n - Place the mouse cursor over a 3D Viewport\n - Select any object in the 3D View (for example the default cube)\n - Press \"F3\" to bring up the search bar\n - Type in \"Popup Input Test\" to launch the script\n - Press \"P\" to generate a popup dialog\n - Click the \"OK\" button in the dialog\n # Watch Blender freeze and stop responding to input.\n\n**Additional Notes**\n\n - The freeze happens at the `bpy.ops.transform.translate` call in the `run_transform` function. The following `print(\" after bpy.ops.transform\")` statement never executes.\n - The freeze up when executing the `run_transform` function does not happen if...\n - a popup dialog is not opened first (Press \"T\" instead of \"P\" when the script is running).\n - the `run_transform` function is called from the `execute` method in the `POPUP_OT_input_panel` class instead of the `draw_callback_px` function.\n - the contents of the `draw_callback_px` function (`if self.wait_for_popup` ...) are relocated inside the `modal` method in the `POPUP_OT_main` class.\n - the script is run in Blender 2.79 instead of 2.80 (the script below can be run in both 2.79 and 2.80).\n\n```\nimport bpy\nprint(\"\\nLoaded add-on.\\n\")\n\n# globals\npopup_active = False\npopup_cancel = False\n\n\ndef run_transform():\n print(\"before bpy.ops.transform\")\n bpy.ops.transform.translate(value=(0.0, 0.0, 1.5))\n print(\"after bpy.ops.transform\")\n\n\nclass POPUP_OT_input_panel(bpy.types.Operator):\n bl_idname = \"object.popup_input_dialog_op\"\n bl_label = \"Popup Input Dialog Panel\"\n bl_options = {'INTERNAL'}\n\n def execute(self, context):\n print(\"\\nPOPUP_OT_input_panel: exec\")\n global popup_active\n popup_active = False\n #run_transform()\n return {'FINISHED'}\n\n def invoke(self, context, event):\n print(\"\\nPOPUP_OT_input_panel: Invoke\")\n return context.window_manager.invoke_props_dialog(self)\n\n def cancel(self, context):\n print(\"\\nPOPUP_OT_input_panel: Cancelled\")\n global popup_active, popup_cancel\n popup_active = False\n popup_cancel = True\n\n\ndef draw_callback_px(self, context):\n if self.wait_for_popup:\n global popup_active, popup_cancel\n if not popup_active:\n if popup_cancel:\n popup_cancel = False\n self.wait_for_popup = False\n elif not popup_active:\n run_transform()\n self.wait_for_popup = False\n\n\nclass POPUP_OT_main(bpy.types.Operator):\n bl_idname = \"view3d.popup_main_op\"\n bl_label = \"Popup Input Test\"\n\n @classmethod\n def poll(self, context):\n return context.mode == 'OBJECT' or context.mode == 'EDIT_MESH'\n\n def exit_addon(self):\n bpy.types.SpaceView3D.draw_handler_remove(self._handle, 'WINDOW')\n print(\"Exiting addon\")\n return {'CANCELLED'}\n\n def modal(self, context, event):\n context.area.tag_redraw()\n global popup_active\n\n if event.type in {'A', 'MIDDLEMOUSE', 'WHEELUPMOUSE',\n 'WHEELDOWNMOUSE', 'LEFTMOUSE', 'TAB'}:\n return {'PASS_THROUGH'}\n\n if event.type == 'P' and event.value == 'PRESS':\n if not self.wait_for_popup and not popup_active:\n self.wait_for_popup = True\n popup_active = True\n bpy.ops.object.popup_input_dialog_op('INVOKE_DEFAULT')\n\n if event.type == 'T' and event.value == 'PRESS':\n if not self.wait_for_popup and not popup_active:\n run_transform()\n\n elif event.type == 'D' and event.value == 'RELEASE':\n # start debug console\n __import__('code').interact(local=dict(globals(), **locals()))\n\n elif event.type == 'ESC' and event.value == 'RELEASE':\n return self.exit_addon()\n\n elif self.force_quit:\n return self.exit_addon()\n\n #if self.wait_for_popup:\n\n return {'RUNNING_MODAL'}\n\n def invoke(self, context, event):\n if context.area.type == 'VIEW_3D':\n args = (self, context)\n self._handle = bpy.types.SpaceView3D.draw_handler_add(\n draw_callback_px, args, 'WINDOW', 'POST_PIXEL')\n self.force_quit = False\n self.wait_for_popup = False\n context.window_manager.modal_handler_add(self)\n print(\"Add-on running\")\n return {'RUNNING_MODAL'}\n else:\n self.report({'WARNING'}, \"View3D not found, cannot run operator\")\n return {'CANCELLED'}\n\n\ndef register():\n bpy.utils.register_class(POPUP_OT_input_panel)\n bpy.utils.register_class(POPUP_OT_main)\n\ndef unregister():\n bpy.utils.unregister_class(POPUP_OT_input_panel)\n bpy.utils.unregister_class(POPUP_OT_main)\n\nif __name__ == \"__main__\":\n register()\n```\n", "Python scripts calling bpy.ops.paint.image_paint operates undo steps for \"individual calls\" rather than \"all calls\" during modal operation\n5820K and GTX970\nWindows 10\n\nLatest daily build (but same problem in earlier ones too)\n\nI have a modal operator which uses image_paint function.\nAfter using it, if I do an undo, I would expect all paint operations during modal operation to be undone.\nHowever every call to image_paint adds another item to the undo list which means I have to undo through every mouse move.\nIf I have moved the mouse more than (max undo items) then I can't get back to the position before I started the operator at all (making the undo pointless)\n\nThis doesn't seem to be the consistent with other modal operator. For example, in the docs [bpy.types.Operator.html ](URL) the modal excecution example (with the addition of UNDO added to bl_options) moves a cube. Many changes can be made to the position of the cube during the modal operation. However one undo (correctly in my option) puts the cube back in the original place before the operator is run.\n\nI did try using UNDO_GROUPED in my bl_options as well as UNDO - neither worked.\n\nIf I am doing something wrong or stupid in my code - sorry!\n\nLoad the attached scene. \nPress Run Script\nHover over cube. \nRight click\nPress space\nType in Simple Paint Operator <return> to activate operator\nPress mouse button to stop the operator\nTry Undoing - it undo things one mouse move at a time\n\n[modal_paint.blend1](modal_paint.blend1)", "Ability to cancel viewport operations (rotate/pan/zoom)\nSince most transforming view-port operations can be cancelled, it would be useful if viewport operations such as rotate/pan/zoom could be cancelled by pressing Escape. [See request ](showthread.php?392619-Call-for-Quick-Hack-ideas-(for-beginner-students-to-complate-in-a-day)&p=3010312&viewfull=1#post3010312).\n\nWhile not high priority, this is nice to support for consistency with other parts of Blender.", "It is not possible to set a hotkey to Transfer Sculpt Mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIt is not possible to set a hotkey to Transfer Sculpt Mode. Neither using the right-click menu nor via the Settings (including using the Python command)\n\n- Open default scene\n- Switch to Sculpt mode\n- {nav Sculpt > Transfer Sculpt Mode > Right click > Remove Shortcut}\n- Now try to assign shortcut\n\nThe shortcut wasn't saved.", "Usability issues with old group operators\nBroken: 2.79, 2.8x\n\n\nWhen using linked objects, all the Group commands [Remove From Group / Remove From All Groups / Add Selected To Active Group / Remove Selected From Active Group] except [Create New Group (Ctrl G)], do nothing\n\n\nIn my particular usage, I link a scene from one file into my main scene, afterwards I create a [New scene with Link Objects] from the Linked scene. \n\n [GroupsFail.blend](GroupsFail.blend)\n [GroupsFail-MainScene.blend](GroupsFail-MainScene.blend)\n\nI can Create Groups by selected objects, and I can remove the group from the object in the Object Properties tab but the only way to remove multiple groups is through python script or deleting the group itself.\n\nSince this report is used to more generally handle issues with the old group operators and other reports have already been merged here, will also list these:\n- Ctrl G is placing new collections inside \"Orphan Data\"", "Sculpt Mode - Using Mask while Multiress active = Crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.2\n```\n Tried also with\n```\n 2.83LTS\n 2.92beta 77f73a928439\n 2.93.0 ae1e68f5146d\n\nWorked: None\n\nWas working in Sculpt mode, tried to hide the arms and the program crashed.\nI tried with another objects with multires and it doesn't happen\n\nHere the .Blend with the problem\n [Multires prueba.blend](Multires_prueba.blend)\n\nGo to Sculpt Mode -> Try to mask with mask brush, Mask Lasso or Mask Box", "Improve MemFile Undo (for general use)\n**Motivation:**\n\n- Resolve bugs where changes to data outside a 'mode' are ignored by the undo system.\n- Unify logic and reduce code duplication.\n\n**Description:**\n\nCurrently we have a blend file based undo system (internally called 'MemFile').\n\nWe could use this almost everywhere (edit-modes for example), it would be sub-optimal at the moment.\n\nThis project would involve optimizing the case when only a limited set of data-blocks change - so we can skip writing all other data-blocks into the memfile.\n\nIt may also involve using better binary diffing for `MemFile` undo (as edit-modes currently use).\n\nThis would most likely not cover image painting and sculpting.\n\n**Estimated Time:** possibly 2-4 weeks *(hard to know)*.", "EXCEPTION_ACCESS_VIOLATION when baking between linked objects\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nWhen experimenting with the idea of having linked duplicate objects and bake materials between them I found a reproducible crash.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF63BB28F6E\nModule : C:\\Program Files\\Blender Foundation\\Blender 2.82\\blender.exe\n```\n\n- Oppen attached file\n- Try to bake the textures (blender crashes)\nSometimes it doesn't crash the first time but always atleast on the second or third attempt.\n\n[mushroom.blend](mushroom.blend)\n", "Adjust Last Operation: Other changes outside that panel are reverted back automatically\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\nHere the demo and file\n[2020-06-23_20-30-11.mp4](2020-06-23_20-30-11.mp4)\n[Scene state reset.blend](Scene_state_reset.blend)\n\n1. Add some objects, add last one\n2. Change visibility for other objects via outliner\n3. Change property in adjustment popup\n4. Scene settings resetted to previous", "Remeshing object with subdivision modifier hangs Blender\nOperating system: macOS 10.14.6\nGraphics card:\n\nBroken: All versions of Blender but tested on Version 2.93.0 (2.93.0 2021-02-25) & Version 2.92.0 (2.92.0 2021-02-25)\nWorked: ?\n\nRemeshing object with subdivision modifier hangs Blender\n1 Add a subdivision modifier to the default cube, set it to 2 or more.\n2 Jump into Sculpt mode and remesh with default voxel settings, it should work fine.\n3 Undo the last remesh and now change the voxel size to 0.002 m and remesh again, it hangs.\n\n\nDo step 1 again, this time apply subdivision modifier and then try to remesh with voxel size of 0.002 m, it should work\n\n\n\n", "Knife tool fails on a non-planar n-gon\nBroken: 2.74 up to and including 2.92 master\nWorked: 2.73 (yes, I bisected that far back ;) )\n\n\nKnife tool fails to cut between verts in n-gons of certain configuration.\n\n\nLoad the attached .blend and try to make a knife cut between the two selected verts (i.e. try to create an edge connecting them).\n\n[knife_fail.blend](knife_fail.blend)\n\n(If you want to test in 2.73 yourself, copy the object from a running instance of 2.9x into 2.73 using ctrl+c/ctrl+v, then replace the mesh in another existing mesh object).", "Expand face sets freeze blender when cursor is on mesh boundaries\nOperating system: Linux (Mint 21) \nGraphics card: RTX 3070 Ti\n\nBroken: 4.0.0 alpha, 12f51bd1c77b, master, 2023-09-21, as found on the splash screen)\nWorked: 3.6\n\nTry to create new face sets from first or last face loops on a cylinder.\nBut expand Face Set from boundaries is frozen in 4.0 alpha.\n\n\n- Open the blend file\n\n- Switch to Sculpt mode\n\n- Move your cursor outside boundaries and press Expand Face Set (Shift +W). (See on pictures)\n\nAt this point, Blender freeze, not crash. No more info in console.\n\nBug :\n\n\nExpected (3.6 version): \n\n\nThanks for your help.\n\n", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "Hide by face set and switch between objects not working in SCULPT Mode INDUSTRY COMPATIBLE\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.4.0\n\nHide by face set and switch between objects not working in SCULPT Mode INDUSTRY COMPATIBLE\n\nOpen blender, switch to industry compatible keymaps, and then if you try to hide faces by face sets, you don t have that option. The same goes for switching objects in sculpt mode. Further more, mask pie doesn't exist in sculpt mode in industry compatible version.\n\n", "Python API: TRANSFORM_OT_resize unrecognized in bpy.ops.mesh.extrude_region_move (macros can change their operators during execution)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.76\n\nBroken: version: 2.91.0\nWorked: (newest version of Blender that worked as expected): don't know\n\nError displayed in the system console: \"Converting py args to operator properties: : keyword \"TRANSFORM_OT_resize\" unrecognized\n\nIn a blank view \n- add a circle (with 'bpy.ops.mesh.primitive_circle_add(radius=1, enter_editmode=True, align='WORLD', location=(0, 0, 0), scale=(1, 1, 1))' in the Python console)\n- then extrude it toward the center by typing {key E}, then {key S} to create an annulus. \n- The command shown in the Info window is: \n\n```\nbpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={\"use_normal_flip\":False, \"use_dissolve_ortho_edges\":False, \"mirror\":False}, TRANSFORM_OT_resize={\"value\":(0.560534, 0.560534, 0.560534), ...etc\n```\n\nSo `TRANSFORM_OT_translate` (in a \"normal\" extrude_region), became `TRANSFORM_OT_resize` (by hitting {key S})\n\nThis same command pasted into the Python Console or in the text editor gives the error shown above.\n\n\n" ]

[ "Crash after undo \"Mask slice to new object\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\nWorked: This problem happens to me with 2.92, the pc that I use now I formatted it, unfortunately before I used version 2.82\n\nMy problem is that when I use the option \"mask slice to new object\" and then I use ctrl + Z the blender closes !! I formatted the PC a few weeks ago, unfortunately I didn't use version 2.92 before. What I realized is that when I use the \"mask slice to new object\" option and then go to edit mode, I can use control + Z without any problem, that is, it does not close.]\n\nThis happens to me in any file:\n\n1. Sculpture mode.\n2.Use the \"mask\" or \"box mask\" brushes\n3. I paint the mask.\n4.I go to the \"MASK\" menu.\n5. I click on \"mask slice to new object\".\n6. Press CTRL + Z.\n7. Blender closes.\n" ]

[ "Frame counter while rendering does not respect blender's DPI setting\n4K screen, Windows 10, GEFORCE 960M\n\nBroken: bac1279\n\nThe cursor frame counter that displays while rendering is minuscule on a 4K screen, regardless of the DPI setting in Blender", "GPencil: Buffer stroke is only visible in the area that originated the drawing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.1 26.20.15019.1003\n\nBroken: version: 2.90 (sub 0)\n\nWhen creating two viewport, you can't watch the lines drawn at the same time\n\nCreate two viewport and move a little on the screen. Then start drawing. You will notice that the lines are not visible at the right time\n[bandicam 2020-04-21 14-03-29-287.mp4](bandicam_2020-04-21_14-03-29-287.mp4)", "Batch Rendering Crashes if EEVEE set in scene\nOperating system: Windows 10\nGraphics card: Any or None\n\n2,83, 2,90, 2.92\n\nEEVEE is set as renderer in the scene file.\nThe scene is send to the render farm. \nOpenGL is not available as render farm is running as background service OR blades machines do not have any GPU at all.\nBlender in Commandline Crashes.\n\n(Side Note: Cycles works fine as CUDA is available within background service)\n\n\n**Expected Behavior**\nReport an error \"EEVEE requires OpenGL. Unable to find/initialize openGL32.dll\"\n\nTo reproduce the issue, you either need some helper service that starts Blender in commandline mode (I can provide one) OR you can use any machine that does not have a GPU installed.\nCreate a new scene with EEVEE as renderer.\nTry to commandline-render the scene.\n\nCommandline that we used:\n\"C:\\renderer_exe\\blender\\win_x64\\Blender_2.90\\blender.exe\" -b \"\\\\isilonai\\woodspeople\\Boar (With fur).blend\" -o \"\\\\isilonai\\woodspeople\\Boar (With fur)\\Brawler####\" -F PNG -x 1 -s 10 -e 10 -j 1 -t 24 -a -y\n\n\nCommandline output:\nR 6| >\"C:\\RR_localdata\\renderer_exe\\blender\\win_x64\\Blender_2.92\\blender.exe\" -b \"C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\" -o \"C:\\RR_localdata\\renderout\\A\\3D\\Blender\\render\\myOut####\" -F PNG -x 1 -s 2 -e 3 -j 1 -t 24 -a -y \nR 7| Blender 2.92.0 Alpha (hash 719bea0d6d06 built 2021-01-12 23:10:47)\nR 8| Read blend: C:\\RR_localdata\\cachedscenes\\Home_3D\\Blender\\cube.blend\nR 9| Writing: C:\\RR_localdata\\temp\\A\\cube.crash.txt\nR 10| StdErr: Warning! Using result of ChoosePixelFormat.\nR 11| StdErr: Warning! Using result of ChoosePixelFormat.\nR 12| StdErr: Warning! Using result of ChoosePixelFormat.\nR 13| StdErr: Warning! Using result of ChoosePixelFormat.\nR 14| StdErr: Warning! Using result of ChoosePixelFormat.\nR 15| StdErr: Warning! Using result of ChoosePixelFormat.\nR 16| StdErr: Warning! Using result of ChoosePixelFormat.\nR 17| StdErr: Warning! Using result of ChoosePixelFormat.\nR 18| StdErr: Warning! Using result of ChoosePixelFormat.\nR 19| StdErr: Warning! Using result of ChoosePixelFormat.\nR 20| StdErr: Warning! Using result of ChoosePixelFormat.\nR 21| StdErr: Warning! Using result of ChoosePixelFormat.\nR 22| StdErr: Warning! Using result of ChoosePixelFormat.\nR 23| StdErr: Warning! Using result of ChoosePixelFormat.\nR 24| StdErr: Win32 Error# (127): The specified procedure could not be found.\nR 25| StdErr: Error : EXCEPTION_ACCESS_VIOLATION\nR 26| StdErr: Address : 0x00007FFF8DBA1C81\nR 27| StdErr: Module : VCRUNTIME140.dll\nR 28| StdErr: Thread : 00001c94\n[Boar.crash.txt](Boar.crash.txt)\n\n\n", "Change GLSL library handling.\nFor 3.2 I want to change the way how we do the color space conversion in the fragment shader. Currently including gpu_shader_colorspace_lib.glsl undefines the blender_srgb_to_framebuffer_space macro.\n\nWhen converting the overlay engine we should copy the shaders we need to the draw engine.\n\nNOTE: A solution needs to be implemented before migrating the overlay engine to use GPUShaderCreateInfo.\n\n", "Sequencer: Driver on any strip property does not invalidate its cache [prefetch frames]\nOperating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.9.22\n\nBroken: version: 2.83.9\n\nSequencer: Driver on any strip property does not invalidate its cache [prefetch frames]\nThis can be any driver on any driven strip property:\nDoes not matter which property is the driving property (could be x Location of default cube as well)\n\n\n[#82776.blend](T82776.blend)\n- Open file\n- `driven` strips opacity is driven by Cube 's X location\n- change Cube 's X location --> driven strips opacity value changes, but the cache is not invalidated\n\n---\n\nOriginal report:\n\n Driver on `wipe.effect_fader` doesn't invalidate cache for driven wipe sequences. It's only invalidates the cache of the currently displayed wipe. This leads to display errors.\n\nNB: The issue is the same for any other parameter (e.g angle, blur...)\n\n- Open this file: [Bug_Wipe_Driver.blend](Bug_Wipe_Driver.blend)\n- There are two wipes, the first is the driver, the second one has the `effect_fader` value driven. Prefetch is enabled.\n- Move the `effect_fader` value of the driving wipe, its cache is reloaded, but not the cache of the driven one.\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "Crash after copy pasting a material onto itself and switching to render\nOperating system: ArchLinux\nGraphics card: NVIDIA 3090\n\nBroken: Current main.\nWorked: Never.\n\n\nBlender crashes when copy pasting a material onto itself (via UI), then creating a new material slot, and then switching to the rendered view.\n\n1. Open a new scene in blender.\n2. Select the cube and go to its material tab.\n3. Next to the material list, on the right, click the down arrow and do Copy Material.\n4. From the same menu now do Paste Material.\n5. Add a new material slot using the + in the materials tab.\n6. Switch to rendered view.\n\nAttached a crash stacktrace taken with gdb, and main build with debug.\n\nIf it's useful, the crash was taken with a manually built blender, so it was a factory startup with Eevee as a renderer, but it also crashes when using Cycles.\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Weird VSE crash\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) blender 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) no clue\n\nBlender crashes on opening file. Was trying to make an alternative caption that gets around the Multiply color issue #112267 but came across a new bug.\n\nBased on the default startup or an attached .blend file (as simple as possible).\nOpen the file I've attached\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "stack_overflow exception while rendering with viewport render on\nOperating system: win10\nGraphics card: 2070super\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 2.83.4, 2.91 6fe609d4c3\n\n\nwhen pressing f12 in render mode, blender crashes,\nwhen pressing render in solid mode, blender doesnt crash\n\n[blender_debug_output.txt](blender_debug_output.txt)\n```\nError : EXCEPTION_STACK_OVERFLOW\nAddress : 0x00007FFF42963FDB\nModule : C:\\Windows\\system32\\DriverStore\\FileRepository\\nv_dispsi.inf_amd64_6af46268c19e4980\\nvcuda64.dll\n```\n[2.blend](2.blend) \n1. switch to render mode\n2. press f12 & watch task manager.\n3. blender will close", "Custom render engine is unable to create gpu context\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 14.0.6, DRM 3.47, 5.19.17-2-MANJARO) AMD 4.6 (Core Profile) Mesa 22.3.1\n\nBroken: version: 3.5.0 Alpha\nWorked: Blender 3.4\n\nUnable to perform background rendering using `gpu` module in custom render engine.\n\nRun the script in background mode: `blender -b -P background-gpu.py`. Blender throws: `SystemError: GPU API is not available in background mode`, despite the line `bl_use_gpu_context = True` in custom render engine. Worked perfectly fine in blender 3.3 and 3.4. Not in 3.5 though.\n[background-gpu.py](background-gpu.py)\n\n", "Segfault pasting stale driver.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\nDrives copied and pasted with significant change in file data in between can trigger segfaults. \n\n```\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nblender(BLI_system_backtrace+0x34) [0x55dfd70fd084]\nblender(+0xe151bd) [0x55dfd4bd41bd]\n/usr/lib/libc.so.6(+0x3cf80) [0x7f9b26870f80]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder26build_object_data_geometryEP6Objectb+0x170) [0x55dfd7000380]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder17build_object_dataEP6Objectb+0x54) [0x55dfd6ffb4b4]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x1d3) [0x55dfd6ffe2c3]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder22build_driver_variablesEP2IDP6FCurve+0x77) [0x55dfd6ffad87]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder14build_animdataEP2ID+0x1f9) [0x55dfd6ffe8b9]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder12build_objectEiP6ObjectNS0_26eDepsNode_LinkedState_TypeEb+0x228) [0x55dfd6ffe318]\nblender(_ZN7blender3deg20DepsgraphNodeBuilder16build_view_layerEP5SceneP9ViewLayerNS0_26eDepsNode_LinkedState_TypeE+0xb2) [0x55dfd7003892]\nblender(_ZN7blender3deg23AbstractBuilderPipeline16build_step_nodesEv+0x76) [0x55dfd6fea296]\nblender(_ZN7blender3deg23AbstractBuilderPipeline5buildEv+0x42) [0x55dfd6fea4b2]\nblender(DEG_graph_build_from_view_layer+0x33) [0x55dfd6fd24e3]\nblender(+0xef501a) [0x55dfd4cb401a]\nblender(wm_event_do_depsgraph+0xc5) [0x55dfd4f59245]\nblender(wm_event_do_refresh_wm_and_depsgraph+0x92) [0x55dfd4f593b2]\nblender(wm_event_do_notifiers+0x36a) [0x55dfd4f6055a]\nblender(WM_main+0x2b) [0x55dfd4f5532b]\nblender(main+0x367) [0x55dfd4b9da67]\n/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f9b2685bb25]\nblender(_start+0x2e) [0x55dfd4bd056e]\n\n# Python backtrace\n```\n\n\n* Add a custom property to the Scene.\n\n* Right click on its value field, and run \"Copy as New Driver\".\n\n* Run `CTRL`+`N` or \"File\" —> \"New\" —> \"General\".\n\n* Right click on any value field, and run \"Paste Driver\".", "bake operator reports uninitialised image that isn't even in use in the shader..\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\ncan't bake due to strange error\n\nopen blend file\nselect object\nselect the baked image texture node in the shader editor\nclick bake in the render setting (leave settings as is)\n\nstrange error pops up saying \n\"uninitialised image \"nightmare0134.png\" from object 'pavement.002'\n\nThis image isn't even in use by the shader.\n\nPS, it seems intermittently not possible to paste screengrabs into this new bug reporter. Also, how to do bullet points and embed video?\n\n", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n" ]

[ "MacOS OpenGL error in initializing offscreen context\nHi.\n\nThe first time when an offscreen OpenGL context is created with `GHOST_ContextCGL::createOffscreenContext()`, `glClear(GL_COLOR_BUFFER_BIT)` is called while `glCheckFramebufferStatus(GL_FRAMEBUFFER)` is `GL_FRAMEBUFFER_UNDEFINED`, resulting in an glError in `GHOST_Context::initClearGL()`.\n\nWhen a new window with an (onscreen) OpenGLContext is created, `initClearGL()` is OK, because `makeCurrentContext` did set the gl-context. \n\n```\nvoid GHOST_Context::initClearGL()\n{\n ** Add this to confirm the error:\n //\n GLint status = glCheckFramebufferStatus(GL_FRAMEBUFFER);\n if (status != GL_FRAMEBUFFER_COMPLETE) {\n printf(\"Framebuffer not complete!\\n\");\n printf(\"OpenGL error: 0x%x\\n\", status); \n }\n \n glClearColor(0.447, 0.447, 0.447, 0.000);\n glClear(GL_COLOR_BUFFER_BIT);\n glClearColor(0.000, 0.000, 0.000, 0.000);\n}\n```\n\nSome possible (although maybe incorrect) fixes:\n\n1. \tOnly call `initClearGL()` when a window is created.\n\n```\n** This function is called for both on- and offscreen gl context\n*GHOST_ContextCGL::initializeDrawingContext() {* ...\n\n *if (m_openGLView) is the check for on- or offscreen* version 1a\n if (m_openGLView) {\n initClearGL();\n }\n [m_openGLContext flushBuffer];\n\t \n *or this?* version 1b\n if (m_openGLView) {\n initClearGL();\n [m_openGLContext flushBuffer];\n }\n\n // ...\n}\n```\n\n2. \tI think a better solution would be to move the gl-commands (`initClearGL` and `flushBuffer`) to another part in the initialization, after `GHOSTContextCGL::activateDrawingContext()` is called, so every operating system has the same initialization. This requires more code-refactoring, creating possible bugs at other operating systems, and I can only test MacOS.\n\n```\n Removing both `initClearGL()` and `[m_openGLContext flushBuffer]` from `GHOST_ContextCGL::initializeDrawingContext()` in a simple test didn't show any errors (for both on- and offscreen gl-contexts) and it looks like everything is still working OK.\n```\n\n\nI think fix #1 is simple, solves at least a single glError and doesn't break anything. Not sure if `[m_openGLContext flushBuffer]` should also be disabled when creating an offscreen gl-context, but the flushing would be useless when nothing is done on this gl-context, right? \n\nBoth possible fixes in #1 (version 1a or 1b) don't generate a glError.\n\nAlso fix #2 (remove both functions for on- and offscreen context) don't generate a glError.\n\nOS: MacOS Mojave (10.14.1)\nGPU: AMD Radeon RX 560" ]

[ "Blender randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\n", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Blender 3.3 crashes on importing external .exr file on compositor\nOperating system: Windows 11 x64\nGraphics card: gtx 650 ti\nprocessor ryzen 9 5900X\n\nBroken: tried 3.3 LTS (september 7, 2022 release) and also 3.2.1, but had this failure before in previous builds.\n\n**Short description**\nBlender immediately crashes after importing a multilayer .exr (generated in Houdini's Karma renderer) to the compositor. Example files attached\n\nOpen new blender scene, switch to compositor tab and check \"use nodes\". Then the error happens after either dragging and dropping the images or using the image node for import.\n\nThe crash seems to occur only when importing images with AOVs packed in, I attached one example that works perfectly but only has the color layer. I know this is a niche workflow but I'm out of options for compositing until I can upgrade my graphics card, sorry if this isn't really worth looking into.\n\n\n\n", "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "Blender 2.8 and 2.81 (ab519b91b2c4) has high chance of crashing when using Python to create a new node-tree link.\nOperating system: Windows 10 (x64) v1903 Build 18362.356\nGraphics card: Nvidia GeForce GTX 1060 6GB\nCPU: Intel Core i5 7600K\n\nBroken: 2.81-ab519b91b2c4 **AND** 2.80 release\n\nCreating a new node-tree link via Python sometimes causes Blender to crash with the error \"EXCEPTION_ACCESS_VIOLATION\".\nI have attached a .blend file that will cause the crash, just by clicking \"Run Script\" once or twice. \nWhen I found the bug, I spent some time making the script as small as possible while still causing the crash, so the script is less than 30 lines.\n\nI also installed Blender 2.81-ab519b91b2c4 on a Windows 10 laptop that had never seen Blender before, and the bug was present on there too, so I'm confident the issue isn't specifically due to my hardware.\nI've also included blender_debug_output.txt and blender_system_info.txt, generated by the blender_debug_log.cmd file included in the Blender 2.81 download.\n\n1) Open the attached .blend file.\n2) Click \"Run Script\" in the bottom right of the text editor pane.\n3) Repeat 2 until crash (should only take 1 or 2 tries)\n\n[Crashy crash.blend](Crashy_crash.blend)\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Regression: Image rendering fails while viewport rendering is in progress\nOperating system: OSX Ventura Version 13.3\nGraphics card:AMD Radeon Pro Vega II Duo 32 GB\n\nBroken: 3.5.0 Date 2023-03-29 02:56 Hash: 1be25cfff18b \nWorked: 3.4.1 Date 2022-12-19 17:00 Hash 55485cb379f7\nCommandBuffer Failed: cycles_metal_integrator_compact_shadow_states\n\n* Load file provided\n* Set ViewPortShading to MaterialPreview\n* Then select ViewPortShading to Rendered\n* While the viewport is rendering Select Render Image.\n\nThis will often cause the error. It may take an attempt or two but more likely to happen after at least one attempt.\n\nIn some case blender will throw the error in both the viewport and in the image window. In some cases...Blender will hang and require you to force quit. At other times it will crash the OS. \n\nThe larger the scene the more drastic the failure. In this simplified file it typically will recover.\n\n", "adding drivers in the compositor always results in a dependency cycle which often causes blender to hang when reopening the saved .blend file.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90.0 Alpha\n\nadding drivers in the compositor always results in a dependency cycle which causes blender to hang when reopening the saved .blend file.\n\n\nJust to clarify, the append issue I mention in the video only happens if you copy and paste 3d objects from a file with the dependancy cycle problem into a new file, save the new file, and then try and append that new file into another new file, in this instance it also results in a missing data block if trying to re-open the file you copied into.\n\n[compositor dependancy cycle on all drivers.blend](compositor_dependancy_cycle_on_all_drivers.blend)\n\n[2020-06-02 17-50-21.mp4](2020-06-02_17-50-21.mp4)\n\n", "Freeze on performing any operation when compositor tab is open\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.3.1\n\nFreeze on performing any operation when compositor tab is open.\nSubsurf modifier seems important for redoing the issue \n\nThis is the continuation of #99695 \n\nThe Bug in #99695 was fixed, but there seems to be more conditions which make the Compositor slow.\n\nDorian from Scatter5 was so nice and made again a simplified version of a secene with the bug.\n\nThe slowdown caused by an unkown combination of geometry nodes, which makes the Compositor unusable slow.\n\n1. Open the attached file\n2. Go to the Compositor\n3. Enjoy the freeze\n4. Try to disconnect a node in the Compositor\n5. Again, enjoy the freeze\n\n[COMPOSITOR SLOW.blend](COMPOSITOR_SLOW.blend)\n", "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Crash when scrubbing the timeline when using the line art modifier\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.0\nWorked: 3.4.1\n\nWhen scrubbing the timeline, blender will crash. This happens frequently when I have a project of sufficient complexity that uses the line art modifier. The provided blend file has been simplified as much as possible while still reproducing the crashing behavior.\n\n1. Open line_art_crash.blend\n2. Scrub the timeline. Jumping between frames makes it less likely to crash, but holding onto the playhead and slowly moving should have it crash in a few seconds.\n\n", "Error: Illegal address in CUDA queue copy_from_device\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\nWhen rendering in GPU mode, Render crashes.\n\nAttached Blend File\nAny frame after 1150 crashes on render with the title error for us.\nTry rendering frame 1160 - This one crashes for me all the time.\n\n", "Blender crashes as soon as an image texture is plugged in the material BSDF node\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\nSee attached log for more detail\n\nBroken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions\nWorked: ??? The earliest available build, 2.93.18, also causes the same crash\n\nThe second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes\n\n**Similar tickets**\n#76193\n#76377\n\n1. Start Blender.\n2. Create new default file.\n3. Select the default cube.\n4. Switch to Shading workspace.\n5. Add Image Texture node.\n6. Create new image or select an existing one.\n7. Plug Color output to the Base Color input of the Principled BSDF node.\n8. Watch Blender shut down.", "Crash when switching from solid to rendered view\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\n\nI have a scene about 1.7GB in size with 4K textures but renders in 2K using simplify, blender crashes when I open the file > hit F12 and render the scene then close the render windows and switch to render view > it starts compiling then blender closes, in the past it would show out of memory this report: \n\n105522#issuecomment-904934 \n\nThis issue happens only when persistent Data is active\n\nunfortunately I can't share the file at the moment. \n\n\n\n\n" ]

[ "Enabling compositing nodes after enabling Real-time compositor - crash\nOperating system: macOS-12.5-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Pro Apple 4.1 Metal - 76.3\n\nBroken: version: 3.4.0 Alpha\n\nEnabling compositing nodes **after** enabling Real-time compositor causes a crash.\n\n\n\n - Start up blender, default file. \n - Go to preferences, and enable real-time compositor. \n - Enable \"compositor\" in the viewport window.\n - Change timeline to compositor window.\n - Click on Use Nodes.\n - Booooooooom!\n\nGet a beachball, when Doen't stop until I kill Blender. I have a video if you'd like to see...\n\n\n\n\n\n\n\n" ]

[ "Crash (memory use after free) on freeing RigidBody world\nReproducible with current master, probably there since forever.\n\n# Steps\nWith an ASAN build:\n\n- Open `rigid.anim.blend`\n- Close Blender\n\n[rigid.anim.blend](rigid.anim.blend) \n\n(Case found while working on #86379 (When using \"Append\" rigid body objects + empty constraint, none of its constraints work.))\n", "output_node.inputs.new() crash blender\nOperating system: Linux-5.15.0-57-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.86.01\n\nBroken: version: 3.4.1\n\ninput = output_node.inputs.new(type = 'RGBA',name = 'bob_sfog',identifier='bob_sfog') \ncrash blender\n\nOpen blender \nexecute line by line this srcript:\n\n```\nscene = bpy.data.scenes[0]\nscene.use_nodes = True\noutput_node = scene.node_tree.nodes.new(type='CompositorNodeOutputFile')\noutput_node.inputs.clear()\ninput = output_node.inputs.new(type = 'RGBA',name = 'bob_sfog',identifier='bob_sfog')\n```\n\n", "FFMPEG Output allows invalid format/codec combinations\nOperating system and graphics card: any\n\nBroken: all\n\nAny video file format combination with video and audio codecs can be selected, but not all work.\n\nThe encoding UI panel when selecting a Movie File Format allows different Formats (Flash, Matroska, Ogg, ...), Codecs (PNG, Theora, H.264, DV, ...) and Audio Codecs (PCM, FLAC, Vorbis, MP3, ...) to be selected in pretty much any combination. The (video) Codec is only hidden for Formats that only support one single Codec.\n\nThe same is true for the Python API, any combination of values for ffmpeg.format, ffmpeg.codec and ffmpeg.audio_codec can be set (ffmpeg = context.scene.render.ffmpeg).\n\nOne failing combination for example is setting H264 as Format and FLAC as Audio Codec. Another example is Quicktime as Format and Theora as Codec.\n\nThe problem is that FFMPEG has no API that tells us whether a specific combination works and encoding doesn't fail either. It outputs a file that simply cannot be played back (trying with VLC for example). So the big question is how to deal with this problem? Leave it up to the users to figure out possible combinations? Hardcode possible combinations in the UI or lower at RNA level so that Python API users are also \"protected\"?", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "adding a movie strip to the video sequence editor changes the scene frame rate, this breaks all alembic currrently in use by the scene if they have a different framerate\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nadding a movie strip to the video sequence editor changes the scene frame rate, this breaks all alembic files currrently in use by the scene if they have a different framerate\n\n", "Blender crashes: OpenVDB math::Transform::read throws exception. \nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.2\n\nBlender keeps crashing.\n\nI have a project were I created an animation of modified arrays. Everytime I play it it crashes\n\nCrash report: P1536\n\ncrashed thread: \n```\n\tThread 35 Crashed:\n0 libsystem_kernel.dylib \t0x00007fff726c733a __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff72783e60 pthread_kill + 430\n2 libsystem_c.dylib \t0x00007fff7264e8a2 __abort + 139\n3 libsystem_c.dylib \t0x00007fff7264e817 abort + 135\n4 libc++abi.dylib \t0x00007fff6f8ae458 abort_message + 231\n5 libc++abi.dylib \t0x00007fff6f89f8bf demangling_terminate_handler() + 262\n6 libobjc.A.dylib \t0x00007fff713da5b1 _objc_terminate() + 104\n7 libc++abi.dylib \t0x00007fff6f8ad887 std::__terminate(void (*)()) + 8\n8 libc++abi.dylib \t0x00007fff6f8b01a2 __cxxabiv1::failed_throw(__cxxabiv1::__cxa_exception*) + 27\n9 libc++abi.dylib \t0x00007fff6f8b0169 __cxa_throw + 113\n10 org.blenderfoundation.blender \t0x0000000110291c61 openvdb::v7_0::math::Transform::read(std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 4801\n11 org.blenderfoundation.blender \t0x000000011026082b openvdb::v7_0::io::Archive::readGrid(std::__1::shared_ptr<openvdb::v7_0::GridBase>, openvdb::v7_0::io::GridDescriptor const&, std::__1::basic_istream<char, std::__1::char_traits<char> >&) + 1787\n12 org.blenderfoundation.blender \t0x0000000110286589 openvdb::v7_0::io::File::Impl::unarchive(openvdb::v7_0::io::File const&, std::__1::shared_ptr<openvdb::v7_0::GridBase>&, openvdb::v7_0::io::GridDescriptor const&, openvdb::v7_0::io::File::Impl::NoBBox) + 57\n13 org.blenderfoundation.blender \t0x0000000110282c91 openvdb::v7_0::io::File::readGridByName(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, openvdb::v7_0::math::BBox<openvdb::v7_0::math::Vec3<double> > const&) + 465\n14 org.blenderfoundation.blender \t0x0000000110282ab6 openvdb::v7_0::io::File::readGrid(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 54\n15 org.blenderfoundation.blender \t0x00000001128a2cc9 MANTA::updateGridFromVDB(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 361\n16 org.blenderfoundation.blender \t0x0000000112890985 MANTA::updateGridFromFile(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, float*, bool) + 869\n17 org.blenderfoundation.blender \t0x0000000112890cee MANTA::updateNoiseStructures(FluidModifierData*, int) + 558\n18 org.blenderfoundation.blender \t0x000000011287e2b5 manta_update_noise_structures + 21\n19 org.blenderfoundation.blender \t0x000000010df34cd0 BKE_fluid_modifier_processDomain + 3168\n20 org.blenderfoundation.blender \t0x000000010df316ce BKE_fluid_modifier_do + 142\n21 org.blenderfoundation.blender \t0x000000010e3ad4f6 applyModifier + 54\n22 org.blenderfoundation.blender \t0x000000010dea5b0a mesh_calc_modifiers + 2778\n23 org.blenderfoundation.blender \t0x000000010dea4d6b mesh_build_data + 123\n24 org.blenderfoundation.blender \t0x000000010dea4035 makeDerivedMesh + 133\n25 org.blenderfoundation.blender \t0x000000010dfe1281 BKE_object_handle_data_update + 1089\n26 org.blenderfoundation.blender \t0x000000010dfe1704 BKE_object_eval_uber_data + 52\n27 org.blenderfoundation.blender \t0x000000010e9f36ba DEG::(anonymous namespace)::deg_task_run_func(TaskPool*, void*, int) + 138\n28 org.blenderfoundation.blender \t0x00000001142cadbc task_scheduler_thread_run(void*) + 364\n29 libsystem_pthread.dylib \t0x00007fff72784109 _pthread_start + 148\n30 libsystem_pthread.dylib \t0x00007fff7277fb8b thread_start + 15\n```\n", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "GPencil: Add option to jump to scene from Video Sequencer Strip\nNeed a way to jump from the strip to the scene edition directly.\n\nIt's necessary to define in some place what it's the layout to use.", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "Rigidbody crash undoing while animation plays (which was started at frame 1 or below)\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[animation_john2.blend](animation_john2.blend)\n\nOperating system: Windows 10\nGraphics card: Nvidia 2070 Super\n\nWorked: -\n\nBlender crashes when object is rotated to a steep vertical angle and animation player is run.\n\nFor animation_john2.blend\n- Play Animation\n- Select a bone (could be any other operator as well I think)\n- Undo (this will also jump back to frame 0 -- where we started -- which is the important part, starting animation at frame 2 or higher does not result in the crash)\n- Redo\n\nRepeat until crash. Occurs between 2-5 repeats.\n\nAlso occurs at other similar high angles.", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "Crash when auto script execution is enabled\nOperating system: Windows 10 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: Blender 4.0.0 7372b3bdda35 and later\nWorked: never? 2.93 fails too\n\nBlender daily build crashes immediately on launch. The blender start screen isn't shown at all, only a grey window which then immediately closes. The crash log indicates that it is a memory EXCEPTION_ACCESS_VIOLATION (see log file attached).\n\n- Open preferences, enable `auto script execution`\n- Save prefs and close blender\n- Rename attached file and replace it with existing startup file\n- Launch blender (crash)\n\n- - -\n<details>\n <summary> Original report </summary>\nStart Blender through Steam, Blender Launcher, blender_debug_log.cmd, blender_debug_gpu.cmd, or blender_debug_gpu_glitchworkaround.cmd.\nA grey window opens with the Blender logo in the top bar.\nThe window closes as Blender crashes.\n\n[ Crashing_4-0-0_daily.blend](https://projects.blender.orgattachment)\n</details>", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script" ]

[ "VSE: Crash When Trying to add Image Sequence / Movie [if based on file opened from pre 2.8]\nOperating system: Linux-4.15.0-140-generic-x86_64-with-glibc2.23 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha (and 2.92.0)\nWorked: 2.91.2\n\nCaused by 5713626422\n\nAdding an Image/Sequence in the video sequence editor crashes blender\n\nFurther investigation reveals that .blend files created with versions prior to 2.8, which used the Factory Default Startup file, are affected.\n\nTo reproduce :\n\n1. Start blender 2.79b\n\n2. Click 'File | Load Factory Settings'\n\n3. Save the file.\n\n4. Start blender 2.92.0 or later. \n\n5. Open the file saved in step 3.\n\n6. Switch to the VSE and click 'Add | Image/Sequence'\n\n" ]

[ "Crash (Seg Fault) When Rendering Grease Pencil Stroke on Render Farm\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.83.1\n\nOur render farm of 70 iMacs has been running for 3 years through the 2.7x series up till 2.81a.\nWhen we switched to 2.83 last week it started crashing consistently when rendering Grease Pencil strokes.\nThe crash occurs when using Blender to do command line rendering via an SSH session on a machine without the user physically logged in. (Crashes on Mac and Linux)\n\nCommand Line Rendering on my own machine works fine.\nCommand Line Rendering on a remote machine via SSH works fine if I'm also logged into that machine.\nBut as soon as I log out of the machine so that the SSH session is the only active user on the machine, then the error shows up.\n\nI tested this on 2.81a and the error (below) shows up there too, but in 2.81a it doesn't also lead to the Segmentation Fault that crashes Blender.\nIt's only in 2.83 (and 2.83.1) that the error is followed by the Seg Fault 11\n\n\n**_RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.\nWriting: /var/folders/jk/7b488ncn6c13t515bnt6q_8w68xcj1/T/test.crash.txt\nSegmentation fault: 11**\n\non Linux the error message is slightly different, but still a crash:\nUnable to open a display\nAborted (core dumped)\n\nContents of test.crash.txt (from the Mac crash)\n# Blender 2.83.1, Commit date: 2020-06-25 09:47, Hash 8289fc688b3e\n\n# backtrace\n0 Blender 0x00000001079eb9d7 BLI_system_backtrace + 55\n1 Blender 0x000000010159ddb8 sig_handle_crash + 392\n2 libsystem_platform.dylib 0x00007fff5db5fb3d _sigtramp + 29\n3 ??? 0x00007f8594802010 0x0 + 140211698802704\n4 Blender 0x0000000101a39da2 DRW_opengl_context_create + 66\n5 Blender 0x00000001018f47d5 WM_init_opengl + 37\n6 Blender 0x0000000101a374ff DRW_render_gpencil + 127\n7 Blender 0x0000000105de5ef4 RE_engine_render + 1156\n8 Blender 0x0000000105df06d3 do_render_all_options + 387\n9 Blender 0x0000000105df2a14 RE_RenderAnim + 2260\n10 Blender 0x000000010159c9dd arg_handle_render_animation + 141\n11 Blender 0x000000010797880d BLI_argsParse + 173\n12 Blender 0x000000010159a497 main + 855\n13 libdyld.dylib 0x00007fff5d974ed9 start + 1\n14 ??? 0x000000000000000a 0x0 + 10\n\n\n\n1) Make a new default file.\n2) Delete the Cube\n3) Add->Grease Pencil->Monkey\n4) Save as test.blend\n5) Copy test.blend onto a remote machine\n6) Make sure the machine is at the login prompt (showing the username password boxes).\n7) ssh into the remote machine\n8) command line render one frame from test.blend something like:\nBlender -b /test.blend -s 1 -e 1 -a\n\n", "If Grease Pencil is set to \"Stroke Depth Order: 3D Location\", blending always with the background and not with previously painted strokes\nOperating system: Ubuntu 20\nGraphics card: GT 1030\n\nBroken: 3.0\n\nIf Grease Pencil is set to \"Stroke Depth Order: 3D Location\", brush color blending seems to use only 1-bit transparency in many cases.\n\nIt is a known issue (see T75684). The linked bug is closed as a presumed limitation of Grease Pencil. However, what the dev calls a limitation there seems to be an unrelated feature (from user perspective, possibly not from a technical perspective). Namely, \"the strokes are always drawn as a billboard face to point of view\" prevents them from looking flat, despite being drawn with a brush defined in 2d space.\n\nI do not know Blender internals, but visually it looks like the problem is elsewhere: blending of colors in \"Stroke Depth Order: 3D Location\" binarizes (at least in some cases) the brush' alpha (opacity) channel. In effect, a hardly visible pixel may completely replace what is behind it. Possibly there is a way to make the scene look correctly at least when rendered.\n\nSee the model attached to the linked bug.", "Collection holdout on grease pencil objects\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.4\nWorked: unknown\n\nHoldout option on collection doesn't work, if objects it is containing are grease pencil objects. Alpha of contained GP objects remains on 1 / solid in viewport as well as in render.\n\nPS: This behavior would help a lot with compositing linework made with \"linework modifier\" of grease pencil. In shots where characters are obscured by objects linework should obscure them as well but if in the same shot character comes in front of the object suddenly the opposite is needed.\n\nsample .blend file (steps included):\n[collection holdout grease pencil bug.blend](collection_holdout_grease_pencil_bug.blend) \n1. create GP drawing (GP Suzanne will work fine)\n2. create collection for it and move it in the colection\n3. repeate first two steps but move the new GP object in front of the first one (Default GP stroke might be mor suitable in this case)\n4. in collection settings of the collection made for second object (the stroke) check the holdout option.\n5. render image and you should see the second gp object remaining opaque.\n\n**given result**\n\n\n**expected result**\n[achieved by converting GP stroke to curve and extruding the curve]\n\n\n", "Grease Pencil Vibrating Contours\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 740/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.83.4\n\nHi, i i have bug on Grease Pencil contours. When i move camera in animation contours vibrate, changing size. This is not problem with my PC, because i tried it on another and problem is the same. I tried Anit-Aliasing, change render engine (Cyles and Evee), the same bug is in viewport and in render animation. I'm attach the video of this bug. This bug occurs just with camera or object move. \n\n1. Create Grease Pencil object.\n2. Move camera to \"zoom\" it.\n\n[vibrating contours.mp4](vibrating_contours.mp4)\n\n[vibrating contours.blend](vibrating_contours.blend)\n", "Grease Pencil datablock property 'use_onion_skinning' doesn't work\nOperating system:\nGraphics card:\n\nBroken: 3.4\nWorked: \n\nThe datablock-level property \"use_onion_skinning\" on the Grease Pencil datablock doesn't seem to do anything. Toggling the property with Python doesn't affect the visibility of onion skinning.\nWorking as expected, this property will be useful when drawing among multiple Grease Pencil objects.\n\nOpen attached blend, toggle use_onion_skinning in the Python console: bpy.context.object.data.use_onion_skinning = False [onion_bug.blend](onion_bug.blend) ", "Displacement distorts textures\nOperating system: Windows 10\nGraphics card: RTX 3060Ti \n\nBroken: 3.6.0\nWorked: Never\n\nAll textures are distorted where displacement texture is greater than 0.\n\nWhen you plugin displacement as 'bump only' the box projected textures glitch out and start to stretch.\nSee attached file.\n", "GPencil: Canvas Overlay becomes inconsistent when both Object and Layer are transformed\nOperating system: Windows\nGraphics card:\n\nBroken: 3.4.1\nWorked: never?\n\nModifying Grease Pencil Layer transforms affects the Canvas overlay, but when both the Object and Layer have transforms the overlay does not describe the drawing plane actually being used by tools.\n\n- Open attached .blend\n- Draw new strokes into the Lines layer\n- Rotate the viewport to view the stroke placement.\n\n", "Grease Pencil shimmers in the viewport and renders\nOperating system: Windows 7 Ultimate\nGraphics card: Nvidia Quadro 2000\n\n2.92.0\n\nI have a video below, If you see carefully the lines are shimmering, Is there any way to avoid that? watch?v=aBIJbTTiLlU \nAttached a blender file as well.\nI tried \n- increasing samples of viewport \n- increasing anti-aliasing of grease pencil. \n- different render systems 'eevee' and 'cycles'. \n- Tried all possible file exports but the problem is in the viewport itself.\nShould I try denoising it? although that didn't work so well either.\nThe problem just isn't going way. Is it my system? Could you help?\n\n[room fix.blend](room_fix.blend)", "GP transparent layer doesn't blend with background object \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.0.0 Alpha\n\nI have a foreground grease pencil object, and a background grease pencil object (yellow blob).\nThe foreground object contains a layer set to 0 opacity.\nWhere this layer overlaps the background object in the viewport, the background object is invisible.\nExpected behaviour: the visibility of the background grease pencil object isn't affected by transparent layers in a foreground object.\n\n\n\n\n\n[#89286.blend](T89286.blend)\n\nForeground object \"makes hole\" in background, doesn't blend. Rotate viewport camera, suddenly it blends correctly.\nWhen foreground location is set to 0,0,0 it blends correctly too.", "Grease Pencil - drawing preview ignores canvas settings\nOperating system: Windows 10 Pro 64-bit operating system, x64-based processor\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nBroken: 2.83 and 3.5 latest\n\nWhen previewing grease pencil (before pen release), the Stroke Placement settings do not render properly. It looks like the preview is stuck on \"View\" but renders correctly on pen release. In my GIF you can see the strokes clipping, but appear correct after pen release. Can this be fixed? It's easily repro'd and consistent in multiple versions\n\n1. Create basic Mesh.\n2. Create Grease Pencil object above Mesh.\n3. Set Stroke Placement to \"3D Cursor\" or \"Origin\" and set Drawing Plane to anything but View.", "Mask from Cavity blurring artefacts\n## The Issue\n\nThis is a limitation of how this new feature was implemented, but I'm still adding this to the bug tracker so we are aware that this is meant to be fixed at some point.\nWhen adding blurring steps to the cavity masks in sculpt mode, either with the \"Mask From Cavity\" menu operator or via the auto-masking options, it will not lead to an ideal result.\nThe blurring very strictly follows the triangulation of the mesh causing streaks along the surface, and poles grow into star patterns.\n\n\n\n| Smooth Mask Filter | Cavity Blur | \n| -------- | -------- | \n|  |  | \n\n\n\n\n\nThis needs a deeper look into alternatives to blur the mask in the operator.", "LineArt: New module to generate lines over meshes using grease pencil as target\nThis is the main Line Art task, includes the implementation of following functions:\n\n- Line Art cpu calculation code and UI.\n- Line Art modifier for Grease Pencil.\n- Other additional data structures in Object/Collection/Materials.\n", "Grease Pencil wrong Cursor Size Smooth Brush when accesed with the [SHIFT] key\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 460M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.3.1\nWorked: \n\nThe On Screen **Smooth Brush Cursor Size** is inaccurate when using the Smooth Brush with the **[SHIFT] **key while using any other brush of a different radius setting.Grease Pencil > Draw any curve \nGrease Pencil > Sculpt > **Smooth Brush**> Make the Smooth **Brush Radius VERY SMALL** (10).\nGrease Pencil > Sculpt > **Grab Brush** (or **ANY OTHER BRUSH**) > Make the **Brush Radius HUGE**(150). \nUse the **Grab Brush** as you wish.\nPress **[SHIFT]**to activate**Smooth Brush**while in Grab Brush (or**ANY OTHER BRUSH**)\nThe on screen cursor Radius while the [SHIFT] key is pressed does not reflect the VERY SMALL Brush Radius (10) that we set earlier. This is constantly confusing. Can you please make the radius display correctly based on the actual Smooth Brush Setting?\nattached scene: GreasePencil_SmoothBrush_CursorSize_bug.blend\n[GreasePencil_SmoothBrush_CursorSize_bug.blend](GreasePencil_SmoothBrush_CursorSize_bug.blend)\nThank you!", "Make Thumbnail Dragging More Reliable\nOn some systems, the dragging is very glitchy and keeps invoking box selection instead.", "Blender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb (Idk if this is very relevant lol)\n\nBroken: 2.82 BETA, 689a873029b9, master, 2020-01-15 21:07\nWorked: -\n\nBlender 3D shift+RMB \"set 3D cursor\" not sensing strokes made with the grease pencil nor strokes made with the annotation tool\n\nAdd a stroke, hover it with your mouse and press your \"Set 3D cursor\" hotkey combination (by default Shift RMB).\n\n**Expected result**\nWhen doing just this, but when hovering your cursor/mouse over a mesh object instead, the 3D cursor will be set on the surface of the mesh object right where the cursor/mouse is hovering over that mesh/object. As the grease pencil is rather new, Im guessing making this react with the grease pencil strokes were just something that was forgotten when implementing it." ]

[ "Grease Pencil: Better render Anti-Aliasing\n## Motivations:\nThin lines are correctly rendered using grease pencil with the currently implemented post process Anti-Aliasing. This is done by making sure the line width is not less than 1.3 and by modulating its opacity.\nHowever, there is cases where this is not enough. For instance really dense drawings with small lines with little to no curvature still tends to flicker a lot.\nAnother case is when the gpencil strokes intersects the scene geometry. This makes the line less thick to the post process which makes it too small.\n\n## Proposed solution:\nWe propose to implement a Temporal AntiAliasing solution. It is robust and will match Cycles & EEVEE's film filtering if using the same filtering function. This only adds one temporary buffer (low VRAM usage compared to rendering at higher resolution) and is completely self contained (works with transparency and don't interfere with other features).\n\nI propose to only implement this for final rendering since it might introduce flickering that might be annoying while drawing.\n\nHowever this wouldn't solve the issue of gpencil strokes intersecting geometry.\nFor this I propose to erode or reproject the render's depth to match the render sample of the new AA scheme. This should fix the second problem completely.\n\n## Technical details:\n- Implementation just need to be ported from Workbench which has a lighter form of TAA than EEVEE. Also [D10414](D10414) can be of great help to reduce render/convergence time.\n- Depth buffer modification can be implemented after new AA is in." ]

[ "Crash guide during render complete August 29, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.44\n\nBroken: version: 3.3.0 Beta\n\nBlender 3.3 Beta crash guide during render August 29, 2022\n\n\nNot matter all version 3.0 to 3.4 keep me crash. Do not use Windows. Only for Macintosh.\n\n\n\n[Blender-2022-08-29-092340.ips](Blender-2022-08-29-092340.ips)\n\n[Armor wear 1.0.0.blend](Armor_wear_1.0.0.blend)\n\n\n\nT100328\n@Nurb2Kea\nRender 600 (complete render cause crash guide)\n", "Autosmooth + Custom Normals is slow\nOperating system: Windows 10\nGraphics card: Nvidia mx230\n\nBroken:\nmaster\n\n\nUsing autosmooth and custom normals at the same time is slow, even in situations where you wouldn't\nexpect normal calculation to happen (like moving an object in object mode).\n\n\n[normal_autosmooth_slow.blend](normal_autosmooth_slow.blend)\n\n - Load the .blend file. Move the object around, it should be slow. \n - Either disable autosmooth, or clear custom split normals.\n # Moving the object should now be a lot faster\n\n", "EEVEE: Reduce viewport render time by only render needed draw passes.\nCurrently all material + effect passes are rendered even when eventually they aren't needed. This can happen when viewing a render pass in the viewport. For example:\n* Mist\n* AO\n* Shadow\n* AOV (after [D7010](D7010) has been comitted)\n* etc\n\nWe should see how we can optimize the rendering pipeline so that only the passes that are needed are drawn. This would lead to a more responsive viewport in these cases.", "Crash to login screen on macOS Ventura when enabling caustics and smooth shading.\nOperating system: macOS 13.1\nProcessor: 2.6GHz Intel Core i7\nGraphics card: AMD Radeon Pro 5500M 8 GB\nMemory: 16GB 2667MHz DDR4\n\nBroken: 3.4.1\n\nBlender/macOS crashes to login screen when enabling smooth shading on an object with \"Cast Shadow Caustics\" enabled.\n\nCreate a scene with:\n\n - A light with \"Shadow Caustics\" enabled\n - An object with \"Cast Shadow Caustics\" enabled and a transmissive material applied\n - An object with \"Receive Shadow Caustics\" enabled\n\nSet render engine to Cycles and device to GPU compute (crash does not occur with CPU compute).\nSwitch viewport mode to Rendered.\nSelect the cast shadow caustics object and enable smooth shading.\n\nmacOS will hang before crashing to a login screen.\n\nsystem.log reports:\n\nsessionlogoutd[4795]: DEAD_PROCESS: 3681 console\n\nConsole.app also lists a crash report for WindowServer (example crash report is attached).\n\n[Caustics-Crash-on-Shade-Smooth.blend](Caustics-Crash-on-Shade-Smooth.blend) [WindowServer-2023-01-19-171731.ips](WindowServer-2023-01-19-171731.ips)", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Flickering UI on MacBook M1 or external monitor MBP 13 M1\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 2.93.5\n\nWhen any action in blender (move viewport or oblects) - there is flickering UI. Not way to burn eyes, but noticeable. Problem happens only on external monitor that worked absolutely fine in any other apps.\n[IMG_2758.MOV](IMG_2758.MOV) - video in slow motion showing the problem. Some times it flicks a lot, some times not much.\n\nJust moving view point is enough to flick UI.\nThat happens with my first of two files. Second doesnt have that. Attach the file with problem.\n[domik.blend](domik.blend)\n", "Unable to output pictures correctly when rendering version 3.2 demo with 65536*65536 resolution\nOperating system:win11 -workstationedition\nGraphics card:4090\n\nBroken: 3.4.0 release\nWorked: \n\nUnable to output pictures correctly when rendering version 3.2 demo with 65536 * 65536 resolution.\nWhen nearly 4 hours of rendering ends, blender does not work any picture out, as the picture atteched. And the image attribute say this image is 32768 * 32768.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\nusing the dome file for blender3.2\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "just activating osl, without using it, makes any render 3 to 4 times slower\nWin7 x64\n\nBroken: 2.76b\n\nTake any prodution render with CPU, just activate osl in the render tab, it will render \" to 4 time slower, without using it in the scene. Compared to GPU render wich is already 5 times faster than a cpu render, it is = 15 to 20 times slower. OSL is unusable with this bug. Note that other renderer with OSL don't have this speed hit.\n\nWith CPU and 16x16 tiles, render this scene: pabellon_barcelona_v1.scene_.zip\nthen just activate osl, render again and compare times. although there isn't any use of OSL in the scene, the render times crawls down.\n(you can also lower the samples to 10 to make it faster for both render)", "Cycles GPU crash when switching to Rendered 3DViewport --MacOS 13.1--\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.5.0 Alpha (works fine)\n\nInstant crash of blender when switching to rendered 3DView.\n\nCompile latest 3.5 version as of 2022-12-18 20:06, hash: `50c7eb14f4`\nopen empty scene provided below and switch to rendered 3DView.\n[gpu.blend](gpu.blend)\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nPS: When switching to CPU there is no crash. Only GPU !", "Faster Animation Playback\n**Status:** Discussing Designs\n\n---\n**Team**\n**Commissioner:** @Mets @Hjalti\n**Project leader:** @Jeroen-Bakker\n**Project members:** @Sergey\n\n**Description**\n**Big picture:** Animators should be able to work in an interactive environment.\n\n**Non functional requirements:**\n\n* Animation playback in the viewport should play at constant framerate at 24fps.\n* `?` Motion curves should be update-able in realtime\n* Playblast shouldn't take much more than regular viewport playback.\n\n**Work plan**\n\n\n**Milestone - Animation Playback/Render Performance**\n\n**Status:** Execution\n**Time estimate:**: \n**Design:** #73429 (Approach Faster Animation Playback)\n**Engineer plan:** Will be created per improvement.\n**Related Tasks**\n* {icon circle color=red} #75134 (TaskScheduler Improvements)\n* {icon circle color=red} #75120 (DrawManager: Improved Task Scheduler)\n* {icon circle color=red} #75208 (Dependency Graph Evaluation Optimizations)\n* {icon circle color=yellow} F-Curve Evaluation Optimizations\n* {icon circle color=yellow} Profile and optimize modifiers (some suggestions are archived in #75207)\n* {icon circle color=yellow} Motion Path Performance\n* {icon circle color=yellow} Optimize VSE Playback for Animators\n* {icon circle color=green} #75124 (ActionEditor: Keyframes Drawing)\n* {icon circle color=green} #75127 (ActionEditor: Add callback function to ANIM_animdata_filter)\n\nThese tasks are ordered in priority. The changes to the task scheduler has most technical impact so we should execute that task with highest priority so we have more time to fix any related issue. The Draw Manager changes rely on features that will be realized by the task scheduler. (@Jeroen-Bakker will do the developments)\n\nChanges to the dependency graph can start from the beginning. Most likely they will be executed by @dr.sybren or @sergey.\n\nThe rest (modifiers, action editor) can be executed afterwards. This is also the time to look at improving motion curves (if this is still needed). (@Jeroen-Bakker will do the developments)\n\n**Milestone - GPU Subdivision**\n\n**Status:** Initial\n**Time estimate:**: \n**Design:** To be completed\n**Engineer plan:** To be completed\n**Related Tasks**\n\n* #68996 (OpenSubdiv GPU acceleration)\n\nThe final design for subdivision (part of the modifiers optimization) needs more collaboration between the GPU/Viewport team and @Sergey to come with an realistic approach.\n\n\n**Milestone - Animation Cache**\n\n**Status:** Needs Design and engineering plan to proceed\n**Time estimate:**: To be determined after Design/EngineeringPlan\n**Design:** #73481 (Design: Animation Caching)\n**Engineer plan:** Not started\n\nAnimation Caching Mechanism: RAM/Disk cache mechanism that can cache the output of an animation. During the animation the cache is invalidated.\nThis cache can also be used for viewport playback and viewport animation rendering.\n", "VSE Render time increases for scenes containing scenes\nOperating system: Linux-5.10.57-antix.1-amd64-smp-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4400 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 20.3.5\n\nBroken: version: 3.4.1\nWorked: 3.1.0\n\nWhen rendering a scene using FFmpeg with the Video Sequence Editor, if it contains a scene strip with \"Sequencer\" input then the rendering time increases dramatically. If that contained scene also contains a scene strip, then rendering time increases even more. I have tested up to 5 levels deep and the render time keeps increasing.\nThe VSE preview speed is not affected by the inclusion of scene strips.\n\n1. Start a new project for Video Editing\n2. In the VSE, rename the scene as \"Full video\". Add any movie file\n3. Configure the scene: set frame range for 10 seconds; match output resolution to movie dimensions\n4. Configure Output Properties to use FFmpeg Video with the \"H264 in MP4\" presets\n5. Render animation and note the time taken\n6. Create a new Scene using the \"Copy Settings\" option. Call it \"Scene of scene\"\n7. In this scene, add a Scene strip and select the original \"Full video\" scene. Set Input = Sequencer\n8. Render animation and note the time taken\n9. Create a new Scene using the \"Copy Settings\" option. Call it \"Scene of scene of scene\"\n10. In this scene, add a Scene strip and select the \"Scene of scene\" scene. Set Input = Sequencer\n11. Render animation and note the time taken\n\n", "Sculpt performance warnings in the UI\nMultiple options in Blender can cause performance drops in sculpt mode (using modifiers, shape keys, EEVEE, dyntopo). Most of these options are handled in the code in ##BKE_sculptsession_use_pbvh_draw##\n\nUsers often report poor performance in sculpt mode because there is currently no information in the UI when the object is not using the sculpt mode optimizations. We have the ##use_deform_only## option to partially fix these problems, but new users are not aware of it and it only covers the modifier stack, but not EEVEE or dyntopo. \n\n**To be decided**\n - How and where to show these warnings\n - Should we include an operator to disable all settings (modifiers, viewport, shape keys...) that are causing the performance problems?", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "Slow EEVEE timeline scrubbing when using Scene World material\nOperating system: Arch Linux\nGraphics card: Intel UHD 620 (`iris` with `INTEL_DEBUG=reemit`)\n\nBroken: `0781c22ceedc`, `2.90`\nWorked: \n\n\nScrubbing through the timeline on an empty scene is slow when viewing through EEVEE and Scene World enabled, even though the node graph for it is a simple Background Shader node.\n\nThis also happens when *nothing* is connected to World's material output.\n\n[slow_scrub.mp4](slow_scrub.mp4)\n\nYou can see in the first part of the video, when using LookDev and have Scene World disabled, the scrubbing is relatively fluid and very close to the cursor. After enabling Scene World you can see that the scrubbing is lagging behind the cursor.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Create a new scene\n2. Delete everything (not really necessary)\n3. Try scrubbing the timeline without Scene World in LookDev\n4. Try scrubbing the timeline *with* Scene World in LookDev\n5. Notice that the latter is less responsive\n\n**Note**\n\nI have only experienced this on this GPU (probably due to its low-performance), however I still feel this is a weird bug." ]

[ "Cycles render time regression with AMD GPUs on macOS\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4\n\n-------------------\n\n3.5.0 Alpha\n\n\n 3.5.0 Alpha\n\n\n3.4.0 Alpha\n\n\nThat is 54 sec against 2.02 min. \nPS:: That's a huge render time difference (100%+) and drawback (like usual) for us MacOS users !! :-(\n\n\nxcode 14.1\nlatest brew updates\n(cycles-cache & build-darwin folders deleted before compiling )\n\nEDIT: Here are examples from earlier versions:\n\n\n\n\nDownload and open BMW GPU scene file in blender 3.4 & 3.5 and hit render ! \n" ]

[ "Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0\n\nNeeds two clicks with Ctrl or Shift key to deselect an item from a list of selected items.\n\n\n* Open the project file “OutlinerSelectItemWithCtrl.blend” in attachment as a starting point.\n\nThe same problem happens in different views with different details.\n\nOutliner:\n* Select the entire collection of objects from the collection “Item List”. You can click the “Cone” object, hold the Shift key and then click the “Torus” object to select the entire list.\n* Then hold the Ctrl key and click the Cylinder object to deselect.\n* The item’s color get a lighter color, but it is still not excluded from the whole selection.\n* Clicking a second time on the object really deselects the object.\n* If clicking the first item of the selection (which is the Cone is this example), it is deselected properly.\n\n3D View:\nThe Shift key is used to select/deselect objects individually. It is pretty much the same issue. It requires two clicks on the same object to really deselect the object, whatever the order of the object in the selection. However, if one object has already been selected before deselecting everything, then the same object gets selected with an additional highlight from the new selection (dragging the mouse cursor in the viewport).\n\nShading view:\nPretty similar to the 3D view.\nIf I deselect all the nodes (Alt + A for example) and I drag the mouse cursor to select all nodes, the last selected node is highlighted in white. If I click the node highlighted in white while holding the Shift key, the node is deselected. However, if I do the same thing for the other nodes, it selects the node with a white highlight and I have to click a second time on the same node to really deselect it. The behavior of the last selected item is also present in the 3D View, but not for the Outliner.\n\nThe Compositing view has the same problem and I suspect that the Geometry Node view has the same too (I haven’t tested the last one).\n\nIn general, it requires two clicks to deselect an object with the normal behavior.\n\nThe first click behaves as an “add to selection” click unless the object already had a selection before completely creating a new selection.\n\nIn all cases, there is an issue with deselecting (or excluding) and single object from a selection of objects in different views. As a reference how it should behave correctly, the Windows Explorer in Windows is able to deselect a single item on the first time it is clicked.\n\n[OutlinerSelectItemWithCtrl.blend](OutlinerSelectItemWithCtrl.blend)\n\n[Deselect_Issue.mp4](Deselect_Issue.mp4)", "Undo/Redo shortcut still active in the Blender File View window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Beta\n\nUndo/Redo shortcut still active in the Blender File View window\n\n* Open Blender with the default cube.\n* Move the cube a few times.\n* Open the “Preferences” window in the menu “Edit | Preferences...”\n* Then do Ctrl + Z to undo. The undo shortcut still works. It is the same for the redo shortcut.\n\nThe undo/redo is also active from any other windows of the “File” menu like “Open”, “Link”, “Save”, “Append”, etc. All links showing the “Blender File View”.\n\nIn the “Blender File View” window, I noticed that the buttons at the bottom disappear when doing the undo shortcut.\n\nI tried a few other shortcuts like Tab to go to edit mode and G to move the cube. They do not seem to be active when the focus is on the “Preferences” or “Blender File View” window.\n\nThe undo/redo is also active when the “Blender Render” has the focus.\n\nAs a consequence, someone accidentally hitting the undo shortcut will get his work being modified behind the window and probably will not notice.\n\n\n{[F9111517](BlenderFileView_Open.jpg) size=full}\n\n{[F9111519](BlenderFileView_AfterShortcut.jpg) size=full}", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Crash on sculpt mask brush when Multiresolution modifier is copied from another object\nOperating system: Windows 11\nGraphics card: GTX 1060\n\nBroken: 3.3.0 / 3.2.0 / 2.93.10\nWorked: (First time trying multires hasn't worked on any of the versions I've tested on)\n\n\nCrash on sculpt mask brush when Multiresolution modifier is copied from another object.\n\n\nReplicate problem 1:\n\n - Add a Cube (#1)\n - Add Multiresolution modifier to Cube (#1)\n - Subdivide 4 times\n - Add a Cube (#2)\n - Copy Cube (#1)'s modifier onto Cube (#2) through the use of Link/Transfer Data > Copy Modifier\n - Select Cube (#2) and enter sculpt mode\n - Select Mask Brush\n - Use Mask Brush (Should crash blender)", "Adding hotkey to modes, Keymap manager item, several identical entries in the Mode dropdown menu\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\nWhen you add a hotkey to the object modes, then you cannot distinguish the mode entry for the different object types. The Mode dropdown menu in the keymap manager shows three sculpt mode entries, two Vertex Paint entries, two Weight Paint entries and two Edit Mode entries. And it is a guessing game which entry is for what. You need to open the keymap python file to have a look which object type is meant here. Sculpt mode exists for meshes, empty hair and grease pencil for example.\n\n\n- Add a hotkey to let's say Object mode.\n- Switch to Keymap manager and search for the new entry.\n- Open the Dropdown menu for the Mode.\n- Have a look at the entries.\n\n\n\n", "Applying Data Transfer Modifier - only the active Shape Key is taken into account\nOperating system: Win 10 x64\nGraphics card: 3080 TI\n\nBroken: 3.3.2, 86abbf717691, master, 2022-11-28\nWorked: ??\n\nWhen applying data transfer modifier to an object (to transfer vertex groups), it only takes into account the selected shape key, not all others too.\n\nExample:\n\nDownload test Blend:\n[datatransfer_shapekeys.blend](datatransfer_shapekeys.blend)\n\nThis is the cube's vertex group:\n\n\nPlane is moved down by shape key \"Key 1\". All looks good in the viewport, this is how the vertex group should look when you apply it:\n\n\nBut if the 'Basis' shape key is selected instead of 'Key 1' when you apply the modifier, it ignores Key 1.\n\n\nSee how the position of the vertex weight is off as compared to the first picture, as if Key 1 were disabled.\n\n\nBut if you were to have Key 1 selected when you apply the modifier, it works as expected:\n\n\nThis is troublesome with objects that have many shape keys, all with different influences on the affected area. When you apply the modifier, it should take into account every active shape key.\n\nThis gets even less predictable if you have multiple shapekeys besides the `Basis` shapekey.\nHere I have two (both with 0.5 weight).\nYou get different results selecting `Key 1` or `Key 2` and none look like what you had in the viewport:\n[datatransfer_shapekeys_multiple.blend](datatransfer_shapekeys_multiple.blend)", "unsubdivide of Multires bug\n**Blender Version**2.91\n\nI try to use unsubdivide of Multires function in blender ,but the result is error.So I test in Zbrush with same modle, it work rightly.\n\nThe thing is,I want sculpt with tank top with no thickness,and add thick ness at last.So I first sculpt with Multires (3 level subdivide),and apply it,and I loop cut the edge with 7 loop cut.After that I add Multires,and use unsubdivide,the result go wrong.\n\nI use the same modle in Zbrush,it work rightly.[unsubdivide error.zip](unsubdivide_error.zip)", "Modifying Basis shape key .co via script in Object mode desyncs from mesh vertices causing new from_mix=False shape keys to revert script changes\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: 2.79.0, 2.80.75, 2.93.7, 3.0.0, 3.2.0, 3.3.0 Alpha (branch: master, commit date: 2022-06-07 18:08, hash: 173a15bcda) (I have not tested any versions older than 2.79.0)\nWorked:\n\nModifying the Basis shape key of a mesh via script in Object mode does not update the mesh vertices to match the changes to the Basis shape key.\nWhen creating a new shape key with `from_mix=False`, the newly created shape key matches the positions of the mesh vertices instead of the Basis shape key, making the new shape key effectively undo the modifications via script.\nThis is confusing because there is no way to tell through the UI that the mesh vertices and Basis shape key have become desynchronised due to a script.\nFixing the desynchronised state is at least fairly simple, going into Edit mode and back out to Object mode will cause the mesh vertices to update to match the basis shape key, fixing the desync (of course, the script could also be modified to propagate the changes to the mesh vertices too).\nI'm unsure if the issue here should be considered the desync between basis shape key and mesh vertices, the behaviour of creating new shape keys with `from_mix=False` or a fault with the script for not also updating the mesh vertices, causing the desync in the first place.\n\n- Add a shape key to the default Cube so that the Cube now has a Basis shape key\n- Modify any of the .co of the Basis shape key's .data while remaining in Object mode by using a script or the Python console, e.g. `bpy.context.object.data.shape_keys.reference_key.data- [x].co.x += 1`\n- Add a new shape key to the default Cube with `from_mix=False` (either the UI, the operator used by the UI or the shape_key_add method of the Cube Object)\n- The newly created shape key will match the original cube shape instead of the basis shape key shape, so when activated (value -> 1.0) it will revert the mesh's shape back to the original cube shape\nAlternative steps to reproduce only the desync without creating a new shape key with `from_mix=False`:\n- Add a shape key to the default Cube so that the Cube now has a Basis shape key\n- Modify any of the .co of the Basis shape key's .data while remaining in Object mode by using a script or the Python console, e.g. `bpy.context.object.data.shape_keys.reference_key.data- [x].co.x += 1`\n- Remove the basis shape key from the Cube such that it no longer has any shape keys, the mesh will revert back to the original cube shape when doing so\n - If you were to instead go into Edit mode and back out to Object mode before removing the Basis shape key (thus fixing the desync), the Cube will remain in the shape of the Basis shape key when the Basis shape key is removed.\n\nModifying the Basis shape's .co via foreach_set('co', my_co_array) has the same issues, but note that it does not update the visuals of the cube in the 3D view immediately so it can appear as if it has done nothing until something else causes the visuals to update e.g.\n```me = bpy.context.object.data\nme.shape_keys.reference_key.data.foreach_set('co', [0,] * 3 * len(me.vertices))```\n\nIn both of these sets of steps, you can instead modify the .co of the mesh vertices to achieve the same issue, but with a reversed effect.\n\n----\nIf you select the default Cube as the active object, the following script will run through the first set of reproduction steps, creating shape keys with both `from_mix=True` and `from_mix=False` and printing whether they match the basis and if not, printing whether they instead match the mesh vertices:\n```import bpy\n\ndef cos_equal(shape_data_or_vertices1, shape_data_or_vertices2):\n```\n for data1, data2 in zip(shape_data_or_vertices1, shape_data_or_vertices2):\n if data1.co != data2.co:\n return False\n return True\n \n```\n\ncube = bpy.context.object\nme = cube.data\n\n# Remove all shape keys if the script has been run previously\nif me.shape_keys:\n```\n bpy.ops.object.shape_key_remove(all=True)\n```\n\nprint(\"\\nTesting shape keys in {}:\".format(bpy.app.version))\n\nbasis_shape = cube.shape_key_add(name='Basis')\n\nassert me.shape_keys.reference_key == basis_shape\n\n# Newly created Basis shape key should match the mesh vertices\nfor v, b in zip(me.vertices, basis_shape.data):\n```\n assert v.co == b.co\n```\n\n# Modify the basis shape key via script in some way\nbasis_shape.data- [x].co.x += 1\nprint(\"Modified basis shape key via script\")\n\nif cos_equal(me.vertices, basis_shape.data):\n```\n print(\"Basis shape key matches mesh vertices\")\n```\nelse:\n```\n print(\"Basis shape key does not match mesh vertices, there is desync!\")\n```\n\n# Create new shape key, from mix, using the shape_key_add funtion\nnew_shape_from_mix = cube.shape_key_add(name='from_mix=True', from_mix=True)\n\nassert new_shape_from_mix.relative_key == basis_shape\n\nif cos_equal(basis_shape.data, new_shape_from_mix.data):\n```\n print(\"from_mix=True matches basis shape key\")\n```\nelse:\n```\n print(\"from_mix=True does not match basis shape key!\")\n```\n # Compare against the mesh vertices instead\n```\n if cos_equal(me.vertices, new_shape_from_mix.data):\n print(\" from_mix=True matches mesh vertices\")\n else:\n print(\" from_mix=True does not match mesh vertices\")\n```\n\n# New shape key, not from mix, created using the shape_key_add funtion\nnew_shape = cube.shape_key_add(name='from_mix=False', from_mix=False)\n\nassert new_shape.relative_key == basis_shape\n\nif cos_equal(basis_shape.data, new_shape.data):\n```\n print(\"from_mix=False matches basis shape key\")\n```\nelse:\n```\n print(\"from_mix=False does not match basis shape key!\")\n```\n # Compare against the mesh vertices instead\n```\n if cos_equal(me.vertices, new_shape.data):\n print(\" from_mix=False matches mesh vertices\")\n else:\n print(\" from_mix=False does not match mesh vertices\")\n```\n```\nExample script output in the System console:\n```Testing shape keys in (3, 0, 0):\nModified basis shape key via script\nBasis shape key does not match mesh vertices, there is desync!\nfrom_mix=True matches basis shape key\nfrom_mix=False does not match basis shape key!\n```\nfrom_mix=False matches mesh vertices```", "Inset faces and Bevel Edge command has bugged interaction with Undo command and shape keys\nOperating system: Windows-7,10\n\nBroken: version: 2.83 (sub 2)\nBroken: version: 2.82 (sub 6)\n\n\nIn edit mode, while selecting a shape key, the Inset operation (I) followed by any other operation (Translating vertices or extruding or whatever), followed by an Undo (Ctrl-Z) command causes the shape key selector to hop to the \"basis\" shape key. This also occurs when using the `Bevel` command.\n\nFrom Default Startup:\n1. Create two shape keys: \"Basis\" and \"Key 1\"on Default Cube. Selection will be on \"Key 1\"\n2. Go into edit mode\n3. Inset a face on any of the existing faces with \"I\"\n5. Do ANY other operation or operations, such as moving a vertex or extruding. The bug occurs with any number of operations done after the Inset command.\n6. Undo (Ctrl-Z)\n7. Observe Shape key information as the undo command causes the selection to switch from \"Key 1\" to \"Basis\".\n8. Keep `Undoing` until you `Undo` the `Inset` operation.\n9. Notice that the shape key selection jumps back to \"Key 1\" as you `Undo` the `Inset`. \n", "Regression: Sculpt mode Annotation tool cursor conflict\nOperating system: Win 10\n\nBroken: 2.91, 3.4\nWorked: 2.90\nCaused by b9e4696641\n\nThe Annotation tool in sculpt mode is not using it's proper cursor. It's using the regular sculpting cursor instead.\nWhen you start drawing, the original cursor shows up on top of the regular sculpting cursor. \nThe end result is two cursors displaying at the same time and the original one flickering sometimes...\n\nTry to use the Annotation tool in sculpt mode....\n\nHere 2.90 (working fine)\n\n\nHere 2.91 (broken)\n\n", "Fade Inactive Geometry: Objects with the same object data are faded\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 3.0.0 Alpha\n\nThe \"Fade Inactive\" Geometry\" overlay is supposed to fade out any object that is not affected by the currently active object in any mode that is not object mode.\nBut if any other object has the same object data linked (same geometry) it will be faded out anyway.\n\n In this example the quad-sphere in the center is active in edit mode. The one to the right has the same linked object data, which is why it also shows the edit mode overlays as it is the same geometry.\nBut since it is another object it is greyed out.\n\nThis is related to #87704 since the overlay seems to prioritise objects that are in the same mode instead of objects that share the same geometry.\n\n- Duplicate an object multiple times to have more than 2\n- Duplicate one of them with Alt + D to have their object data linked\n- Enter Edit Mode on one of those objects\n\n", "Multires: Missing updates are not communicated in the UI\nIntel Core i7, 16 Gb RAM, NVidia GeForce 2070 RTX\nWindows 10 x64\n\nBroken: 2.8x up to 6fff73e3f001 from 2020-01-23\nWorked: 2.79b\n\nCurrently it’s not possible to use Shrinkwrap (modifier and constraint) and Walk Navigation with Gravity (toggling Gravity causes you to fall through the floor, teleporting doesn't work) with object that has subdivided Multires and is in Sculpt Mode. In 2.79 Shrinkwraps are not updating during sculpting but it's still possible to see where objects are being shrinkwrapped. Not being able to see shrinkwraps becomes problematic in a very similar way as not being able to see textures while sculpting.\n\n\n1.\tOpen provided file in 2.79 and observe that Road and House objects are shrinkwrapped to the Landscape object while subdivided Multires is in Sculpt mode. You can use Walk Navigation with Gravity to walk or teleport over the surface.\n2.\tOpen provided file in 2.8, both Shrinkwraps will be disabled and you will not be able to teleport or walk across the surface in Walk Navigation mode.\n[No_Shrinkwrap_and_Walk_Gravity.blend](No_Shrinkwrap_and_Walk_Gravity.blend)", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "Mask brush stops working in tiling sculpting mode after changing its size through \"F\" hotkey\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 2.93, 3.3.0\nWorked: -\n\nWhen an object has the Multires modifier, mask brush stops working in tiling sculpting mode after. (See video below)\n[Desktop 2022.09.17 - 21.18.10.07.mp4](Desktop_2022.09.17_-_21.18.10.07.mp4)\n\n- Open attached file or\n - Add a grid object\n - Add a multires modifier\n - Subdivide Simple a few times\n - Select mask brush in sculting mode\n - set tiling on x and y axis to 1 or 2m \n- try paint mask (sometimes the tiling doesn't work at this stage, you need to paint again and undo)\n- change brush size through F hotkey\n- try paint mask (tiling stops working)\n- press undo\n- try paint mask (tiling works again)\n\n[tiling_sculpt_bug.blend](tiling_sculpt_bug.blend)\n\n", "Disabled Selectability: it is still possible to enter other modes (The new Switch Objects operator, py API, ...) - should this be prevented?\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\n\nAfter trying the new Switch Objects operator in Sculpt Mode and Edit Mode, I noticed that the operator completely ignores if an object has Disable Selection active or not in the Outliner.\n[Desktop 2020.09.19 - 22.58.16.01.mp4](Desktop_2020.09.19_-_22.58.16.01.mp4)\n\n1. Have two separate objects in your scene. Go into Sculpt Mode or Edit Mode with one object.\n2. Use Disable Selection in the Outliner on the object you are not selecting in Sculpt Mode/Edit Mode.\n3. Click on the object that uses Disable Selection. You will be able to select it regardless." ]

[ "Multires & Undo & Frame Change causes weird behaviour with shapekeys\nOperating system: Kubuntu 19.10\nGraphics card: Nviia GTX 1080 (driver 440)\n\nBroken: 2.90.2; 20202-05-15 19:12\nHash eaf7d36d66e5\nBuilt by running \"make full\"\n\nWhen using a multi-res mesh with certain shape-keys, bad results may occur. Create a multi-resolution modifier and subdivide with at least one shapekey active. While subdividing, artifacts may appear in the multiresolution levels. Even if they do not appear, sculpting, undo-ing, then changing frame causes a multi-res explosion.\n\n\n[bug0001-2952.mp4](bug0001-2952.mp4)\n\n1. Create a mesh and do some editing.\n2. Create a shapekey and do some editing. Modify the topology of the mesh in the shape key. (This bug seems to occur even if you don't modify the topology, but doing this seems to make it worse).\n3. Repeat step 2 as desired. The more, the messier!\n4. Optional: now edit the topology of the basis shape.\n5. Exit edit mode -- make sure at least one shapekey is enabled.\n6. Create a multiresolution modifer and subdivide a few times.\n7. Enter sculpt mode and do some sculpting.\n8. Undo\n9. Change frames\n\n\nIn Sculpt mode with multi-resolution, if I sculpt a bit, undo, then change frame, I get a multi-res explosion.\n\nAdditionally, the transform tools seem to cause the same explosion, without changing frame\nI think that it's just any update to the depsgraph\nSo I want to know: Is it user error to use a mesh with shapekeys in Multires, especially a mess of broken shapekeys caused by editing the mesh/topology?\nOr should Blender support even this case?\nplease @ me\nThis bug does not seem to occur if none of the shapekeys are enabled/ if their influence is set to 0.\n\n**My Observations:**\nIt doesn't seem to matter what kind of shape keys are present- weird results will occur. The weirder the shape-key, however, the weirder the result.\nAfter playing around with it, it even seems like causing a depsgraph update (in this case, by changing frame) simply causes Multires to add the shapekey's displacement to the current sculpt level. I do not know why undo is necesary to create the bug. Perhaps it is creates an outdated depsgraph? This doesn't seem to be related to the new undo system; I was able to get the bug with \"Undo Legacy\" enabled. I have not, however, tested this in older versions of Blender. I would be happy to do so.\n\nI think the explosions that occur are not so much the product of bad shape-key handling, but rather, editing shapekeys in destructive ways is a good way of producing bad geometry that confuses multi-res. Have I found two bugs, then?\n\nmaybe related? #76769 #76313\n" ]

[ "Panel order is not saved when preferences window closes\nWindows 10, GTX 1660\n\nversion: 2.83 (sub 7), branch: master (modified), commit date: 2020-03-10 07:58, hash: 1aa7c4c28a06, type: \nbuild date: 2020-03-10, 08:52:15\n\nWithin the Preferences Editor, you can change the ordering of various sections but the changes are not retained when you close the Preferences Editor.", "Segfault on unregistering operator/menu with open props dialog.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92, 2.93\n\n\nWhen an operator currently has a `wm.props_dialog_(self)` open, unregistering it will cause a segfault.\n\nThis only seems to happen reliably when the module it's from has at least one `bpy.types.Menu` subclass that's also been registered.\n\nThe displayed values of property fields in the dialog will sometimes flicker and switch values with each other for a split second before the segfault.\n\n\n[InvokeSegfault.blend](InvokeSegfault.blend)\n\n1. Open the attached file.\n\n2. Invoke the operator from the 3DView toolbar.\n\n3. Use a system hotkey (E.G. `ALT`+`TAB`) to switch to the window with the text editor space while leaving the props dialog open.\n\n4. Run the script again from the text editor window.", "Improve unclear/broken File Browser User Preferences\nThe current File Browser settings are a mess and/or don't work.\n\n# Problems\n\n## 1) \"Show Hidden\" space parameter conflicts with user preference\nWhether to show hidden files is determined by a per-space flag, which is automatically saved (see `PARAMS_FLAGS_REMEMBERED`). But this flag also tries to get initialized with the userpref flag `USER_HIDE_DOT`.\nThe former **overrides** the latter, meaning the option does nothing when using temporary windows (which is factory default).\n\n## 2) Hidden Data-Blocks is confusing (and broken)\nFor those who don't know, this is a feature which hides dot-prefixed data-blocks not only from file browser, but also when searching in any ID selector.\nHowever, for the file browser, it's (confusingly) not tied to this user preference, but to the \"Show Hidden\" flag of the editor (the tooltip of which does not mention data-blocks at all)!\nAdditionally, this feature does not work in the file browser on Windows due to an `#ifndef WIN32`.\n\n## 3) Unnecessary \"Filter Files\" user preference\nSince the file browser already has the capability to remember its settings (see point 1), it seems reasonable to remove the explicit user preference and use `PARAMS_FLAGS_REMEMBERED`.\n\n## 4) \"Show Recent/System Locations\" are hard to discover\nOther editors (e.g. status bar sections, or Navigation Bar of the preferences editor) allow configuring directly in the editor, either via right click or in the editor's header.\nThese two file browser settings are only found in the preferences.\n\n---\n\n# Proposed Solutions\n\n## 1+2) Cut \"Show Hidden Files/Data-Blocks\" preference in half\n[D14650](D14650)\n- Rename the preference to \"Show Hidden Data-Blocks\" and put it into e.g. the Editing user preferences section.\n - Moving this setting makes it clear it doesn't only affect file browser, but also ID selectors.\n- Consequently, this user preference will no longer affect the \"Show Hidden\" flag of file browsers (this is already handled via `PARAMS_FLAGS_REMEMBERED` anyway).\n- For file browser, show dot-prefixed data-blocks if either this user preference is set *or* the file browser show hidden flag is set.\n - Update the tooltip of the file browser flag, to clarify that data-blocks can also be hidden.\n- Fix hidden data-blocks for file browser not working on Windows.\n\n## 3) Remember \"Filter Files\" automatically\n[D14650](D14650) (can be split into another commit, since it doesn't strictly belong to this patch)\n- Remove \"Filter Files\" user preference and corresponding userpref UI flag `USER_FILTERFILEEXTS`.\n- Instead remember the flag via `PARAMS_FLAGS_REMEMBERED`, making this completely transparent to the user.\n\n## 4) Add \"Show Recent/System Locations\" to file browser\n[D14649](D14649)\n- Include in either the right click menu, or the header menu, options to toggle these two user preferences.\n - It might be worth storing them as per-editor parameters at this point, though I personally don't see much of a desire to have these differ per editor.", "Missing visual representation of multiple selected color channels (`Blender Light` theme)\nOperating system: win10 64\nGraphics card: 1050ti\n\nBroken: (example: 2.91, default light theme)\nWorked: (2.79b)\n\nThis is how it was in 2.7x when selecting multiple RGB channels:\n\n In recent versions it misses visual representation of how many channels are selected until changing values to see if slider has been updated (left - nonselected, right - all channels are selected):\n\n\n\n - Open default scene\n - Go to material tab\n - Left mouse click any color slot\n - Left mouse click first color channel and hold it\n # While holding, slide cursor below to cover all channels\n\n\n", "gpu.types.GPUOffscreen renders nothing when samples > 0\nOperating system: Linux-5.3.0-55-lowlatency-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83.0\nWorked: None known 2.90 alpha has same issue\n\nOffscreen rendering from Python fails if GPUOffscreen buffer is created with any number of of samples > 0. If samples > 0, nothing is drawn (nor is there any error)\n\nRun the small script in the attached .blend (it is the sample script for offscreen rendering from the documentation but with samples>0)\nThe generated image is empty.\n\n(full system info also in .blend in text buffer system-info.txt)\n[MSAA bug.blend](MSAA_bug.blend)\n", "Autoscroll not working in lists that can be text searched (template_ID), works in others (e.g. template_node_view)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.4.0\n\nUnlike other similar places in Blender, the Scenes list does not autoscroll when hovering the mouse over one of the direction triangle icons.\n\n\n\n\n", "3D Connexion Space Mouse Pro - Blender 2.82a on macOS\nmacOS Catalina 10.15.4 (19E287)\n3D Connexion 3dWare10 10.6.5\n\nBlender 2.82a\n\n\nThe mouse appears to almost match the 3D Connexion training app in terms of movement when in object/edit mode but it would appear that none of the buttons & especially the MENU do not work. \n\nI have installed the 3D Connexion drivers a second and third time with firewall and anti-virus off and the problem with these mice seem to persist. \n\n>> This has been edited by another but im wondering if there is some resource file missing where keys are mapped, either this is a 3D Connexion plug in or something to do with Blender?\n\n\nI've seen these tasks; It's still a problem for me. \n#67686 (NDOF mouse not working in code signed macOS builds)\n#67971 (3D Connexion Space Mouse Enterprise Custom Buttons 1-10 Not working in Blender 2.8 (macOS))", "shift+key with option click\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7262\n\nBroken: version: 2.90.0 Alpha\n\n[problem with a key set to 'CLICK' and with shift=True]\n\nIf I do a shortcut with e.g: km.keymap_items.new('wm.call_panel', 'S', 'CLICK', shift=True)\nI need to press and hold Shift and then press and release S. \nI mean if you do a click on a key without shift or ctrl or alt, the option is respected. but adding a Shift for example the property is not working the same anymore.\napparently in the programing of this click option the presence or not of another key has not been considered.\nthe interest of a click as it is explained in the blender help is when you add another key with the same shortcut but with the option 'CLICK_DRAG'\n\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "Brush Management: setting a brushes tool [vertex_tool, weight_tool, ...] may leave you with unaccesible tools (when no corresponding brush is left)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.83.2\n\nSee attached gif. Scene is the default scene without camera and light. Once I start switching tools in Weight Paint Mode through the different methods shown in the gif, I eventually reach a point where I lose access to some tools. Notice that even though the brush menus initially show the expected brush as the one currently selected, it isn't the one performing the painting (shown in the gif as the desync between \"Active Tool\" and the brush that appears as selected). As the gif also shows, the side menu doesn't select the expected brush either. \n\nAs a side question: why is the Smear brush named \"Smear.001\"? instead of just \"Smear\" like the other brushes?\n\nSee gif. \n\nThanks.\n\n\n\n\n", "How to keep asset viewer options and the search field in view?\n\n\nIt's annoying that animators have to scroll up all the time to access these (or down for the search field).", "select interior faces doesn't support some kinds of interior geometry\nwin 7 pro\n\nBroken: (example: 2.76.1 bfdb420)\nWorked: (optional)\n\nwhen you try to check if there are some interior faces, from menu you select interior faces in face mode. but it does not show them. you only can do this by select non manifold in egde mode and then find the wrong ones. \nwhen you open file, there is black frame where interior faces are. change to face mode, then select interior faces from menu. nothing happens. change to egde mode and select non manifold, and there are 2 interior faces which were not selected earlier.\n[interior faces_bug.blend](interior_faces_bug.blend)\n", "3.4.1 Not Displaying GTX 1660 TI\nOperating system: Windows 10 Home 22H2\nGraphics card: GTX 1660 TI\n\nBroken: These versions do not display my GPU under CUDA/OptiX: 3.4.1, 3.4.1, 3.3.4, 3.3.3 and 3.3.2 (I was also getting Python errors when trying to install addons. (This is true whether they are installed or run from the unzipped .rar downloads.\n\nWorked: blender-2.93.15 candidate+v293.400f35914421-windows.amd64-release is the most recent version that works - everything works as it should!\n\n\nI tried uninstalling/installing the latest Nvidia game ready drivers, the studio drivers, the CUDA Toolkit (which asked for me to install Visual Studio, C++, etc... 🤦‍♂️ ), tweaking the registry settings etc... none of these things worked. \n\nOnly using the older version would detect my GPU. A user on the Discord forum asked me to run the GPU debugger in the latest version 3.4.1 and when I open the program that way, my GPU was finally showing! I sent him the error reports (I can post them below) and he said that Blender IS SEEING my GPU, it's just not displaying it for use.\n\n", "Assign shortcuts: add support for enum menus\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nFor group menus, can't assign shortcuts by right click, and no python tooltips on this. maybe it's not bug, but really need it.\n\n\nscreenshots:\n\n\n\n\n\n\n", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n" ]

[ "Preference not shown in Edit Menu (nor any other menu)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\nLaptop with 17.3\" screen. \n\n\nBroken: version: 2.80 (sub 64)\nWorked: (optional)\n\n\nUser Preference option not shown in Edit Menu. \nHowever, F4 shortcut key still shows it. \n\nDownload and extract that version. \nRun blender.exe\nPreference not found. \n\n\n\n\n" ]

[ "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "Expose debug flags in User preferences\n**Description**\nThis is nice to have feature for enabling disabling debug flags in User Preferences\n\n**Design:**\n* expose checkboxes in user preferences\n* we can show it only when developer extras are enabled\n\n**Engineer plan:**\n* there are ~24 `G_DEBUG*` flags in global structure `G.debug`\n* we already expose debug flags in `bpy.app` in `blender-src/source/blender/python/intern/bpy_app.c`:\n\n```debug\ndebug_depsgraph\ndebug_depsgraph_build\ndebug_depsgraph_eval\ndebug_depsgraph_pretty\ndebug_depsgraph_tag\ndebug_depsgraph_time\ndebug_events\ndebug_ffmpeg\ndebug_freestyle\ndebug_gpumem\ndebug_handlers\ndebug_io\ndebug_python\ndebug_simdata\ndebug_value\ndebug_wm```\n\n* I am not sure how to implement buttons, I would appreciate feedback:\n * is it possible to bind api to button?\n * should I create RNA entry for each flag? how to bing RNA to global structure? how does RNA relates to api?\n\n* as a bonus I would like to expose running depsgraph graphing tool\n\n\n\n", "VSE UI: Change Path/Files is over exposed \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nChange Path/Files is exposed in four places. \n{[F10401818](image.png),size=full}\nAs this function is only working(afaik) on the active strip(why Files in plural?), it should only be exposed in the strip sidebar. See: #91306 If the function is basically the same as changing the path to the source file then the folder button next to the path should be enough. \nAlso, having it as a secret pop-up menu, shortcut key \"C\", is inconsistent with anything in Blender and this should be removed. \n\n\n", "Microsoft store: Blender cannot be used in terminal\nWindows 11\n\nBroken: 3.4\nWorked: 3.3\n\n**Short Description**\nEver since blender 3.4 released, I have been unable to use blender in the command line. Running just the command \"blender\" gives error 0xc0000022 and whenever I try to run any actual command like \"blender -b untitled.blend -a\" nothing happens. I have never had any issues like this in versions prior to 3.4. I am running the Microsoft store version.\n\nIssue only happens with blender from Microsoft store\n\n**Steps to Reproduce**\n * Assuming that blender is already in your system path, which it should be by default,\n * open a terminal in absolutely any folder;\n * run absolutely any blender command;\n * for example, run \"blender -E help\"\n\n- - -\n!!For now, workaround is to type \"blender-launcher\" instead of \"blender\" to launch blender from command line (but that won't accept any arguments)!!", "Menu Editor for Quick Favorites\nCurrently users can only manage menu items in the quick-favorites menu by adding/removing items.\n\nThis task proposes to: \n\n- Create a generic menu editor in the user preferences.\n\n - Add/remove menu items\n - Re-ordering menu items.\n - Operators options should be able to be changed or unset - as we have with the keymap editor.\n\n**Implementation**\n\n- This could share UI code with the keymap editor for adjusting operator settings, since internally they are very similar.\n- We may support multiple kinds of menus, besides \"Quick Favorites\", internally there is support for this. Even if this isn't exposed to users initially.\n\n```\nThis would be useful for declaring user defined toolbars for example.\n```\n\n**User Interface**\nHere's how the UI could be organized: \n\n{[F8282863](Screenshot_2020-01-17_at_11.08.58.png), size=full}", "Regression: Themes: Highlight color in the text menus\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.6.2\n\nThe highlight color is not longer adjustable by the Selected color in the User Interface / Menu Item panel. But changes with the Inner color. This breaks theming.\n\n\n- Enter Preferences. \n- Navigage to Themes tab, User Interface, Menu Item panel.\n- Play around with the Selected and Inner color\n\n", "The Shortcut keys of Play Aniamtion not work in Spreatsheet Editor\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Beta\n\nThe Shortcut keys of Play Aniamtion({key Space}) not work in Spreatsheet Editor\n\n[play animation bug.mp4](play_animation_bug.mp4)\n\n", "GPencil: W shortcut in Draw mode not working and displays error\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.1\n\nThe W shortcut used to display the Context menu, the same summoned with RMB, but it's not working & displaying this error message:\n```\nTool 'builtin.select_box' not found for space 'VIEW_3D'\n```\nOpen a new 2D Animation file and press W.\n\n", "Restore Key Map Item does not restore the `active` property.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nRestore Key Map Item (`bpy.ops.preferences.keyitem_restore`) takes into account the presence of kmi.active, but does not change it during restore.\n\n\nCopy script and run.\n```python\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'node.op'\n bl_label = \"Op\"\n def execute(self, context):\n return {'FINISHED'}\n\nbpy.utils.register_class(Op)\nnewKeyMap = bpy.context.window_manager.keyconfigs.addon.keymaps.new(name=\"Node Editor\", space_type='NODE_EDITOR')\nkmi = newKeyMap.keymap_items.new(idname=Op.bl_idname, type='A', value='PRESS')\nkmi.active = False\n```\n\n", "Particle edit mode - Hide hairs doesn't work\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.81\n\n\nBroken: version: 2.80 (sub 50)\nWorked:\nThe \"hidden\" hairs can't be selected or edited\n\n\nThe hidden hairs are still visible.\n\nAdd a hair system to the default cube \nSwitch to particle edit mode and then switch to point display/select mode\nSelect any number of particles, press H to hide\n- >The hairs are only locked, not hidden\n\n\n", "Invisible color picker in the preferences menu\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\n\n**Short description of error**\nDepending on your position in the preferences menu the colour picker becomes invisible\n\nDepending on your position in the themes menu (preferences/themes), the colour picker may be above or under the setting you want to change, but there is a specific position in which the colour picker becomes invisible. This bug only occurs if there are multiple settings above, at least one submenu open and you edit one of the settings in the middle. E.g. \"Inner\" and \"Inner selected\" in the user interface section. The colour picker is not only invisible but also not functioning. The \"RGB\" and \"HSV\" sliders work as well as the \"HEX\" section.\nClosing the picker and scrolling down the page, only by a single line (up or down) fixes the glitch, also resizing the window works. \n\nBased on the default startup\n\n", "Float slider in the redo panel of the \"add object\" operator does not hide the mouse cursor\nBroken: 2.79b, 2.83\nWorked: (None)\n\nThe problem is not seen in editing mode, but in object mode when adding an object\nand changing the properties in the redo panel, the mouse cursor does not disappear.\n\n\n", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "Selection problem on new 'add modifier' menu\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nin new 'add modifier menu' which introduced in Blender 4.0 if you hover your mouse over a main menu items like 'edit' to open edit's submenu then move your mouse diagonally from top right to bottom left on main menu, other main menu items not highlighting or selecting.\nI attach a video take look at it, in this video I move my mouse from edit(while it's open) to physics , non of menus open, not even physics which I stop mouse there no matter how much time my mouse stay there it will not open.\nalso I moved my mouse from edit to generate and also menu did not open.\n\n", "Panel order is not saved when preferences window closes\nWindows 10, GTX 1660\n\nversion: 2.83 (sub 7), branch: master (modified), commit date: 2020-03-10 07:58, hash: 1aa7c4c28a06, type: \nbuild date: 2020-03-10, 08:52:15\n\nWithin the Preferences Editor, you can change the ordering of various sections but the changes are not retained when you close the Preferences Editor." ]

[ "No menu entry for the preferences\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 64)\nWorked: (optional)\n\n\nthere is no entry in one of the menus for the preferences\n\nOpen Blender\nI can search for the preferences and open them with \"Screen: Show Preferences\", but there isn't an entry for the preferences in any of the menus.[system-info.txt](system-info.txt)\n" ]

[ "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Blender 2.82: Fails to immediately report information to XServer on Linux\nOperating system: Manjaro Linux 5.6\nGraphics card: GTX 1070 ti\n\nBroken: 2.82, found as soon as app is open.\nWorked: 2.81\n\nIn Linux, if an app doesn't report anything to the Xserver, but still specifies window dimensions, it leads to a sort of awful stuttery broken effect while said app is loading. This is visible in 2.82, where, upon opening and loading, it fails to report to Xserver, and looks like this:\n\nIt looks like this while the app is loading (that is, only a title bar) and produces an odd effect if the window is dragged around during loading, and I can confirm that it lasts longer if Blender is put on a mechanical hard drive VS an SSD. This doesn't occur launching any other apps, nor even a binary of 2.81, which instead displays a gray screen while loading. This is obviously just an aesthetic problem, but it can (rarely) cause issues. \n\n\nOpen Blender. ", "Reading from old 2.79 file. Mesh deform broken.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0 Beta\nBroken: 2.83\nBroken: 2.82\nBroken: 2.81\nBroken: 2.80\nWorked: 2.79b\n\n\nOriginal (2.79)\n\n\nAfter loading to 2.83.8+ versions\n\n\nFile\n[MD.blend](MD.blend)\n", "Child Of vertex group fails when controled by Particle System\nWin10 64bit\n\nBroken: 2.79\n\nChild Of constraint fails on rotation from PS\n\nOpen file, play animation on every layer\n\nFirst layer: *Empty* with *Child Of* constraint is controled by Plane's transform animation -> works OK\nSecond layer: *Empties* with *Child Of* are controled by Plane's *Particle System* (via *Explode*) -> Location is maintained, but **rotation is non-synchronized**\nThird layer (example of how previous case is expected to work): Empties parented to *3 vertices* are controled by same PS - OK\n[Child_Of_test.blend](Child_Of_test.blend)\n", "Unusable display with AMD driver errors.\nOperating system: Ubuntu 22.04.2 LTS/Kernel version 5.15.0.75/FOSS amdgpu driver(default)\nGraphics card:MSI Radeon RX580 8GB\n\nBroken: 3.5.1, 3.1.0\nWorked: 3.1.0(Did not experience this until recently)\n\nWhen editing UV GPU gets reset after errors, the compositor does not recover. Garbled image on the screen with displays unusable. Log data attached.\n\nThis happens when pressing .(dot) on the keypad, selecting or moving a UV.\n\n", "Blender crashes when click on shading tab \nOperating system: Windows 10, 64-bit\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 4.5.0 NVIDIA 445.87\n\nBroken: \n - version: 2.81 (sub 16), branch: v2.81_octane2019 (modified), commit date: 2020-02-11 11:57, hash: 81ff79b8cdb7, type: build date: 2020-02-11, 12:22:28\n - version: 2.90 (sub 0), branch: master, commit date: 2020-04-18 16:48, hash: 1f1520a04503, type: Release\n\nBlender crashes when clicking on the shading tab. It closes and goes back to the desktop.\n\nSee short description.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Edge Sliding with subdivision surface is extremely laggy (caused by \"bad\" UVs and UV Smoothing in the modifier)\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0\n\nSo I've been modelling a raptor the last week and I noticed that viewport performance in edit mode was extremely laggy with subdivision surface modifier enabled. I checked the face count and it was just 150k faces which is not a lot at all. It's definitely a modifier problem because when I apply the subd modifier the lag goes away completely even when sliding twice the amount of edges around. I thought that was maybe a hardware issue so I opened task manager and while sliding edges with subd on I get like 4 fps with severe stuttering to top it off. All that while the cpu was at 10% usage and 5% gpu usage with memory barely touched (6gb used out of 64gb). I have nothing else running in the background like an ativirus or music app, I have the latest version of windows 10, latest gpu and chipset drivers, latest bios etc... I even have gpu subdivision enabled without autosmooth to make sure it actually works properly. I even run an sfc/scannow to check for other kinds of issues but nothing changed. Subd in edit mode however is not only slow when sliding edges and vertices but also in adding loop cuts or insetting faces. It is extremely frustrating so it would be great if you could fix this. I know edit mode was not made to handle massive polycounts but 150k is again not a whole lot and definitely comfortable to run on my PC. Here is the file to see for yourselves.\n\n- Open attached .blend\n- Execute Edge slide/loop cuts/inset faces\n[Broken Subd.blend](Broken_Subd.blend)\n\n", "Blender 4.0.0 - Armature Rig with IK broken\nOperating system: MacOs Ventura 13.4.1\nGraphics card: Radeon Pro\n\nBroken: version: 4.0.0 Alpha, branch: main, commit date: 2023-08-23 19:52, hash: 7c2dc5183d03, type: release\nCaused by 6b872079fec9336865638ad9cfa76e37e8e627c5\n\nI have rigged mesh, commercially available at ArtStation. It worked well up until now. In 4.0.0 it is broken:\n- shapes not rendered until i switch to wireframe mode and back\n- IK ignored\n\nLook at video - i open the file in 3.6.3 and in 4.0.0. In 3.6.3 everything fine, in 4.0.0 the problem mentioned occur.\nBlend file also attached\n\n", "Disk Cache combined with Cache Step does not work\nOperating system:\nGraphics card:\n\nBroken: blender-2.80.0-git.8d95dcd87dbb-windows64\nWorked: Blender 2.79 b f4dc9f9d68b\n\nBaking a particle system with *Disk Cache* checked and *Cache Step* set to greater than 1 results in the baking failing.\nNo error is reported, but the bake is obviously corrupt.\nIt worked in 2.79.\n\n[bake.zip](bake.zip)\n1. Extract the archive and open the *.blend* file. (in 2.80)\n2. Playback works at this point. (Particles fall down from the plane.)\n3. Click *Delete Cache* and then *Bake*.\n4. Try playback again. It's not incorrect. (Particles appear at the bottom and don't move. If you check the cache folder, you will see it cached every second frame---instead of every 10th as configured, except for the first step.)", "USD import: investigate texture color space conversion issue\n\n@brurpo Reported the following issue:\n\n> When exporting USD from maya to blender none of the textures comes with the correct color space, they are all srgb.\n> Importing on maya again, on a clean scene, does not have this issue, all textures are loaded with the correct color space.\n> Is there a workaround for this, or is this planned?\n\n\nI'll be looking into this.\n\n\n", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "race_spaceship.blend demo file renders empty result (no renderlayer selected in Render Layers node dropdown)\nOperating system: Windows 11\nGraphics card: Radeon Graphic\n\nBroken: 3.6\n\nScene not display well as final render (demo file).\n\n1. Start Blender File.\n2. Check if Viewport working (all great).\n3. Render (seems going well).\n4. Final image (no image, trasparent background).\n\n", "Some Cycles nodes are active when muted (RGB To BW, Math, vector Math, Separate RGB)\nWin10 64bit\n\nBroken: 2.79\n\nRGB To BW node is active when muted\n\nOpen file and render\n[RGB_BW.blend](RGB_BW.blend)\n\n", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "Cycles - AO Shader node causes infinite \"loading render kernels\" and crashes on return to solid mode view\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.2.0\n\nAO Shader node causes infinite \"loading render kernels\" and crashes on return to solid mode view\n[AO BUG Test.blend](AO_BUG_Test.blend)\nAttaching Sample file.\nJust render the scene in viewport (doesnt render, just \"loading render kernel\" message)\nTry to go back to solid view - results in freeze/crash\n\nregards\n" ]

[ "Error when adding a Torus to the scene\nWin 64\n\nBroken: 2.80 2c2c996a1b2\n\nLaunch Blender, Add menu -> Mesh -> Torus and it will give us:\n" ]

[ "Dyntopo: detail flood fill ruins initial curvature\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 17)\n\n\n[2020-05-23_12-30-55.mp4](2020-05-23_12-30-55.mp4)\n[detail flood fill ruins curvature.blend](detail_flood_fill_ruins_curvature.blend)\n\nSubdivide quad shape few times.\nApply Dyntopo flood fill.\nCondition: initial detail density should be higher (2x) than flood details\n", " Greasepencil Hue/Saturation modifier\nOperating system:windows 10\nGraphics card:GTX 1060\n\nBroken:2.93beta\n\nHue/Saturation modifier can not take effect on fill-gradient", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Very high or low values in the exponent parameter of the minkowski voronoi texture causes parts to become completely black\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using the minkowski voronoi texture completely black spots appear when the input values are outside of a ~0.3,~40 range.\n\nTest file:\n[Test.blend](Test.blend)\n\nPlease open the shader editor to see all nodes.\n\nThank you and have a great day!\n\n", "Bevel modifier - Clamp Overlap broken\nWindows 10\n\nBroken: 2.79.0-git.43a6cf1-windows64\nWorked: 2.79 RC2\n\n\n\nSee attached blend file.[clamp.blend](clamp.blend)", "Geometry Nodes \"On Cage\" modifier option does not adjust the editcage to the modifier result (instead, it modifes the result to the original editcage)\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44\n\nBroken: version: 3.3.0 Alpha\nWorked: never\n\nGeometry Nodes \"On Cage\" modifier option does not adjust the editcage to the modifier result (instead, it modifes the result to the original editcage)\n\n[GN_OnCage_option.blend](GN_OnCage_option.blend)\n- open .blend\n- we have two modifiers doing the same thing:\n - a GN modifier that just translates 2 along the X axis\n - a \"traditional\" displace modifer doing the same thing (could be achieved differently)\n\n- now toggle the `On Cage` option in the modifier for the GN modifier (it puts the result in the space or the original editcage -- wrong)\n\n- disable the GN modifier, enable the displace modifier, toggle its `On Cage` option (it puts the editcage in the space or the result -- expected)\n\n", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Bevel vertex weight problem with Solidify modifier in simple mode\nOperating system: Win10\nGraphics card: 1050ti\n\nBroken: (3.2.0 Alpha from 2022-02-21 23:28)\n\nSolidify doesn't create beveled edge from extruded points in simple mode\n\n\n # Open file and switch between *complex* and *simple* modes inside Solidify modifier -> extruded edges got beveled or not\n\nFrom scratch:\n - Create a plane\n - Assign full bevel weight for both verts and edges\n # Add Solidify and Bevel modifiers (weight mode)\n\n[solidify+bevel_weight_problem.blend](solidify_bevel_weight_problem.blend)\n", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\n", "Geometry Nodes Baking\nAs mentioned on the [blog]() the goal is to support the following features:\n* Editing procedurally generated geometry destructively in the viewport.\n* Prepare and manage simulations for the render farm which shouldn't need to run the simulation itself.\n* Explicitly cache parts of the node tree to avoid recomputing them after every change.\n* Re-time animated geometries, i.e. access geometry generated on one frame in another frame.\n\nAt a high level these goals are achieved by allowing the user to bake still or animated geometry at arbitrary positions in a geometry nodes tree using a new Bake node. The baked data can then be used without having to recompute the inputs of the Bake node. It can be edited destructively using Blender's existing edit modes. Furthermore, the baked data can be imported at specific frames.\n\nImplementing all of these features in one go would be too big of an undertaking, so below are smaller releasable milestones that can be worked on one after another.\n\n## Milestone 1: Bake Node\n\nAfter this milestone users will be able to bake still or animated geometries at arbitrary positions in the node tree. The main use cases are:\n* Prepare simulations (with optional post-processing) for a renderfarm.\n* Speedup working with very heavy node trees (e.g. static landscape generation) by explicitly caching the generated data.\n\nThere are a few requirements for this milestone:\n* New Bake node with a dynamic number of sockets for geometries and their attributes.\n* Baking works by pressing on a bake button in the node itself.\n * For baking the user has to choose between still or animated geometry and optionally a frame range.\n * A bake directory on disk has to be choosen.\n* Deleting the baked data should be possible from the node as well.\n* Potential settings and the baked data are stored per Bake node instance. A Bake node that is in a reused node group is counted as multiple Bake node instances. The actual data per Bake is stored in the geometry nodes modifier on the object.\n\nIt may be enough to keep UI changes local to the new Bake node.\n\n## Milestone 2: Manage Bakes\n\nIn production files, there are typically many simulations and other heavy effects that require baking. The goal of this milestone is to give the user tools to manage many bakes.\n\nThere are multiple parts to this which could potentially be split up into somewhat independent tasks, but I keep them together until further discussion happened:\n* Support naming Bake node instances.\n * While working with just Bake nodes in the node tree, this is less important, because the location of the Bake node in the tree \"identifies\" it to the use. When dealing with many Bake node instances at once, one can't rely on their location but needs to use names.\n * Just using node names does not work well for this, because a node only has one name but might be reused many times.\n* Support tagging Bake node instances.\n * As we've seen in the intro, not all baking happens for the same reasons. Therefore it is important that tools that work with multiple bakes can filter what bakes to work on.\n * Supporting custom tags can help the user organize baked data.\n* UI for dealing with all bakes in a scene or file.\n * There should be some kind of UI list that shows all the Bake node instances.\n * It should show which data is currently baked and which not.\n * Filtering can happen using tags and object selection.\n * Various new operators can work on multiple bakes at the same time: bake, delete bake, set bake directory.\n* Python API for dealing with baked data.\n * While the UI we provide for managing baked data should be good enough for most use cases, it seems unrealistic that we can provide all the tools that a larger production needs out of the box. Therefore, it is necessary to make it easy to manage bakes from addons as well.\n\n## Milestone 3: Import Bake\n\nThe Bake node does two things implicitly, it indicates where in the node group the baking happens and it also imports the baked data. Having both of these in the same node is desirable for most use cases, but sometimes it's benefitial to split both tasks. For example:\n* Baking an animated geometry and the loading it at different frames for re-timing.\n* Load multiple baked frames of the same Bake within the same frame.\n* Baking a geometry in one .blend file and then loading it as a cache in another.\n\nAll of these use-cases turn our baking format into a more general purpose interchange format like Alembic that is Blender specific. Baking into other formats will be possible eventually as well, but it not part of this project. Using a custom format allows us to optimize it for our needs and avoids the problem that Blenders data does not always map 1 to 1 to how data is stored in common formats. Also see [this](105251) task.\n\nThe import can be done with a new Import Bake node which takes a (file) path and a frame as input and outputs the geometry. There are some problems that need to be overcome:\n* The Import Bake node ideally has the same sockets as the corresponding Bake node, but this can't be guaranteed when they are in separate .blend files.\n* While not supported yet, it will be possible to pack baked data into the .blend file. Therefore, the path input is sometimes a path on disk and sometimes some internal identifier.\n* It should be possible to use the combination of a Bake node with one or more Import Bake nodes within a node group without having to hard code the file path for all of these nodes. Therefore, it seems reasonable that the Bake node also outputs where the baked data is stored. Also see [this](29266) older proposal.\n\n## Milestone 4: Editing Baked Data\n\nThe idea is that the user can just go into edit, sculpt or other modes on the baked data and edit it in place. For animated geometries, every frame can be destructively edited separately. The goal here is not to record all manual edits the user did. After baking again, the edits will generally be gone.\n\nWhile this might seem like a small feature, if done right, it can have huge impacts on the way people work with geometry in Blender in the long-term. That is because it could theoretically allow us to get rid of the idea of \"original geometry\" in Blender (e.g. the mesh referenced by `object->data`). To give a glimpse into what could become possible: Adding a cube object could just add an \"empty\" object with Cube node in geometry nodes. This allows the primitive mesh to remain procedural. Going into edit mode could implicitly (or explicitly) add a Bake node and bake the cube so that it can be edited destructively.\n\nAs for this milestone, the target use cases are more minor and mostly revolve around fixing up \"bad\" data in animated geometry. For example, in a particle simulation, a single particle got too close to the camera and blocks the entire view. It should be possible to just delete it manually. \n\n## Parallel Track 1: UI for Unused Nodes\n\nThere are various situations in which nodes in a node group are unused:\n* Nodes not connected to the output.\n* Nodes that would compute the unused input of a Switch node.\n* Nodes that were used to compute a simulation that is now cached.\n* Nodes that compute the inputs to the Bake node which is now baked.\n\nCurrently, there is no obvious way for the user to determine which nodes have been evaluated by the last evaluation. However, this information would be very useful because it allows seeing at a glance when data is cached/baked.\n\nLogging the set of nodes that has been evaluated is relatively [straight forward](107780). However, we still need the a good UI for these nodes. The obvious solution is to just gray out these nodes. While that can work, it's not ideal because the nodes can and should still be editable and graying out usually indicates that the user is not expected to edit them.\n\n## Parallel Track 2: Store Baked Data in .blend File\n\nWe already support packing external files into .blend files. That system just needs to be enhanced to also support baking entire folders full with baked data. Ideally, it is possible to load the baked data lazily when loading a .blend file, but that's probably quite a bit more challenging. It remains to be seen how much of a performance hit loading all frames at once has.\n\n", "Applying bevel modifer changes vertex group\nOperating system: Linux-5.4.0-120-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\nWorked: unknown\n\nApplying bevel modifier changes vertex group\n\n- Create a cube\n- Subdivide\n- Assign a vertex next to an edge that would be affected by an bevel to a vertex group\n- Add a bevel modifier\n- Apply bevel modifier\n- -> the vertex group is changed\n\nThe vertex group is only changed by applying the bevel modifier.\nAn active bevel modifier dont modifiy the vertex group which can be checked with an modifier that uses a vertex group placed after the bevel modifier.\n\nExample:\nUsed vertex group before apply bevel modifier\n\n\nVertices in group\n\n\nUsed vertex group after apply bevel modifier\n\n\nVertices in group after applying bevel modifier\n\n\nSimple example\n[bevel_modifier_apply_bug.blend](bevel_modifier_apply_bug.blend)\n\nComplex example\n[steam_traveller17.blend](steam_traveller17.blend)", "Advancing Displace and Solidify modifiers to handle overlaps\nI briefly discussed this with C. Barton. I often I solidify and displace surfaces in the processes I work on -- recently for 3d printing custom assistance devices including molds for casting rubber, customized computer peripherals, etc. Whether or not they use clear-cut geometric forms, or are of organic nature, they often succumb to the issue of intersections with displace/solidify. I've wanted to work out some details on processes which would enhance these modifiers, but need some help. I'd attempt to implement it so it would be inactive normally, and use thresholds when enabled, so as not to slow down the normal modifier functionality, and a require a minimum processing when the features are used.\n\nThe main issue I'm having is that the modifiers do not presently have access to information on adjacent vertices, and my first approach to an algorithm would examine, with some function fn(vertex_normal, displacement_amount), if there would be a crossing (e.g. if faces would intersect). Then the simplest method would angle the normals away from each other. However, this does all require the ability to examine adjacency, and I'm relatively inexperienced in blender internals, having only contributed minor bits to sculpting tools and physics code. Your guidance would be appreciated.\n\n", "Pinching effect when using bevel and bevel modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\nWhen using bevel in editing mode or bevel modifier sometimes a pinching effect happens at the beveled corners.\n\nWhen using bevel in editing mode or bevel modifier sometimes a pinching effect happens at the beveled corners.\nThis is particularly visible when using many segments.\n\nTest file:\n[Bevel_test_file.blend](Bevel_test_file.blend)\n\nAt first I thought, that this was some kind of limitation of the bevel operation/modifier, however after observing the top part of the test file mesh i'm very sure that this is a bug, because the left part of the topmost face of the test file mesh has a correctly beveled corner, whileas on the other side there is a clearly visible pinching effect despite the local topology of both sides of the topmost face being indentical.\n\nThank you and have a nice day!", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "Node muting connects mismatching sockets\nBroken: 3.2.0 beta\n\n\n - Add *Float Curve* node in any editor (*Shader, Geometry Nodes*) and connect output to anything else\n - Plug *Value* nodes into input sockets (both factor and value)\n - Mute *Float Curve* -> inner noodle connects Factor to Value\n\nOr in provided file mute *Float Curve*\n\n[wrong_mute.blend](wrong_mute.blend)\n" ]

[ "Geometry Nodes \"Curve to Mesh\" \"Fill Cap\" Option Crashes Blender\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Beta\n\nWhen you have a \"Curve to Mesh\" node with Fill caps on, adding a bevel modifier to the stack crashes Blender3D.\n\n- Create a Geometry node tree with any curve primitive\n- Add a \"Curve to Mesh\" node\n- Turn on \"Fill cap\" \n- Add a \"Bevel\" Modifier to the Modifier Stack\n[Based on the default startup][bevel curve.blend](bevel_curve.blend)\n" ]

[ "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)", "Node Socket Name Change results in Cycles Material Rendering Black (name is also identifier, should be read-only?)\nWindows 10\nIntel Core i7-5820k 4.1GHz\n2x Nvidia GTX 970\n\nBroken: 2.79 5bd8ac9\n\nIf you change the name of a Node Socket (not the socket's identifier) of a Cycles Shader Node during execution of a python script, Cycles will render the Material black. \n\nDownload the blend file below:\n[socket_naming_bug.blend](socket_naming_bug.blend)\n\nRun the code in the text editor. \nSwitch to viewport preview.\n\nTo fix the problem, simply reset the two nodes, or add a new Material Output Node and a new Principled Node to the Node Tree. Connect the new nodes together and delete the old ones. \n", "Random Walk SSS in Principled BSDF gives very dark result for small subsurface inputs\nOperating system: NixOS 19.03, Linux 4.19.36\nGraphics card: NVIDIA 970 GTX\n\nBroken: 2.79, 2.80 git (93cabce3a156a07a76c26d7f3e78c3bc3212f623)\n\n\nUsing the Principled BSDF's \"Random Walk\" subsurface scattering method, if the \"Subsurface\" input is set to a low, non-zero value (e.g. < 0.01), you get a very dark looking object. For example, the following image shows three Suzannes with the same material except a different \"Subsurface\" value, from left to right 0, 0.0001, and 0.1:\n\n\n\nThe Blender manual (principled.html) somewhat cryptically states that the Subsurface input acts both as a mix factor between Diffuse and SSS *and* as a multiplier for the subsurface radius, but either way this doesn't seem like expected behaviour. It doesn't occur with the Christensen-Burley method.\n\n\nBlendfile: [random-walk.blend](random-walk.blend)", "Cycles: point cloud geometry improvements\n[D9887: Cycles: pointcloud geometry type](D9887)\n\nImprovements:\n- [x] Point Info node with radius, position, random\n- [ ] Backfaces are ignored (like curves), which means e.g. volumes inside points don't work.\n- [ ] Render as normal or ray oriented disc (see [D9887](D9887)#289012, [P2125](P2125.txt))\n- [ ] Baked shadow transparency support like hair? But must be optional since texturing alpha across the sphere/disc is useful.", "Tangent node used as a vector on Texture Nodes yields nothing through a Bump Node\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nIf you plug a tangent node into any procedural noise texture as the vector, it will work, however once you plug the result into a vector bump node it will draw as an empty bump map. \n\n1. In the shading workspace, grab a noise texture\n2. Grab the tangent node and plug it into the noise textures vector input. Any tangent mode will do fine (x,y,z)\n3. Grab a vector bump node and plug the noise texture into height. \n4. View the resulting bump, nothing will be yielded (however if plugged into the normal input it will)\n[Example.blend](Example.blend)\n", "Material Preview (and final render in EEVEE) purple\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 26.20.100.7263\n\nBroken: version: 2.83.0\nWorked: I don't remember this bug occuring in previous versions.\n\nI know, that materials should become purple when the texture is missing.\nBut the problem is that they not behave as they should even without applying textures and also with the default material.\nThis bug occurs in EEVEE:\n1) In material preview in properties\n2) In render\n3) Sometimes - in viewport\n\nIn a render, it is also a problem with the scene surface material.\nI attach some screenshots from material preview: they are all the same default material.\n\n\n1) Open Blender\n2) Press F12 or go to material preview in object settings.\n3) ... see the bug\n\n\n\n\n\n\n\n\n", "Blender 3.6 problem by rendering scene on EEEVEE (Freeze and crash GL_INVALID_FRAMEBUFFER_OPERATION : Cubemap Workaround End9)\nOperating system: Windows 11 Home\nGraphics card: Radeon Graphics\n\nBroken: (example: 3.6, as found on the splash screen)\n\n\nBlender 3.6 doesn't render the scene as blender demo file in EEVEE\nOpen Blender splash fox of blender 2.90\nRender the scene\nFreeze and crash of blender when rendering on EEVEE\n\n", "Displacement in a shader on volumetrics starts to work only after connecting a shader into the surface output socket\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.119.03\n\nBroken: version: 3.0.0 Alpha\n\nDisplacement in a shader on volumetrics starts to work only after connecting a shader into the surface output socket.\nI do preview switching to an emission shader, but you can use any other shader in the surface socket and then disconnect it.\nIf you change any values, displacement will disappear again.\n[2021-05-08_15-40-44.mp4](2021-05-08_15-40-44.mp4)\n\nOpen the file and reproduce the steps from the video.\n\n[volumetric_displacement_bug.blend](volumetric_displacement_bug.blend)", "Shader node connections in v3.0 file broken in v3.3\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.3.0\nWorked: 3.0\n\nRendering in 3.3 a file created in 3.0 (using both Cycles & Eevee) showed major differences from rendering made in 3.0. Investigation showed that critical node connections in multiple shader trees were broken when opening file in 3.3. Unable to determine if broken connections are consistent in terms of node type. Which nodes have broken connections seems consistent from file to file using the same shaders -- sample .blend was constructed with shaders used in file where bug was first observed. All shaders were originally created in versions prior to 3.0 but later than 2.80.\n\nAttached GIMP .xcf file has exemplary renderings and explanatory screenshots from file where bug was first identified. Sample .blend file was created in v3.0 using shaders from this file. Bug does occur in other files which render fine in 3.0 but have broken shaders in 3.3\n\n\n[REVISED sample file 300.blend](REVISED_sample_file_300.blend)\n\nOpen \"sample file 300.blend\" in v3.0 and inspect shader trees. Open in 3.3 and inspect shader trees, some nodes of which are now disconnected. \n\n\n", "Looks like an eevee limitations with UV maps and attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\n\nWhen working with multiple UVs and attributes, eevee disables some normal/bump maps.\nThere is an error in the console:\n```\nGPU_material_compile: Attribute \"nor\" overlap one or more index from another attribute. Note that mat4 takes up 4 indices. While merging eevee_legacy_material_surface_frag_opaque\n```\nIn 3.4, the shader cannot compile at all (pink texture).\n\nThis is not documented anywhere and it is not clear to me how it works, because until I connect nodes with attributes in Base Color, all normals are displayed.\n\n1. Open .blend file.\n2. Turn on the eevee render.\n3. Look, all normals are displayed.\n4. Connect nodes with attributes to Base Color.\n5. One normal map is missing. An error appeared in the console.\n\n", "World with HDR renders different in EEVEE from 2.82 and 2.83\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.83 (sub 17), branch: blender-v2.83-release, hash: `1d2b89304a`\nWorked: 2.82\n\nIn the viewport or render the result I get is different from 2.82 and 2.83. If I remove the HDR image from the world nodetree, the issue seems to disappear.\n\nNote: Because of another bug (#73131?) you need to save and re-open the file to be sure the results are still different.\n\nThis is a simplified version of the Mr Elephant EEVEE demo:\n\n[simplified.blend](simplified.blend)\n\n\n**2.82:**\n\n\n\n**2.83:**\n\n\n**diff:**\n", "Blender-3.1 (git) boolean in Geomenty Nodes issue\nOperating system:\nGraphics card:\n\nBroken: All\n\nBulean issue like T91889\nbut now in GN\n[2021-11-25_22-29-42.mp4](2021-11-25_22-29-42.mp4)\nTest Scene\n[parktronic1-Blender-3.blend](parktronic1-Blender-3.blend)", "Regression: Vertex colors are now broken in hair strands\nOperating system: Gentoo Linux kernel 5.18.0-gentoo\nGraphics card: RX 480\n\nBroken: 3.2.0, 3.3.0\nWorked: 3.1.0\n\nCaused by b9799dfb8a\n\n\nVertex colors are strange and patchy when moving from 3.1.0 to 3.2.0 or later: \n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Make something with vertex colours and a hair system which utilises them in Blender 3.1.0. In my instance I used geometry nodes to generate them; this may differ when making them manually as one of my other projects which does it manually does not seem to exhibit this issue. \n2. Open file in Blender 3.2.0. \n\nI created the following .blend file to demonstrate the issue: [Color_test_3s.blend](Color_test_3s.blend)", "A combination of shader nodes causes lack of material emission at any brightness (Cycles)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.0(tested as well on 3.3.0 and 3.5.0 alpha)\nWorked: (none)\n\nA difference of bevel node and normal coordinates produces no light at any emission level. Clipping the result due to suspicion about negative brightness has no result.\nNote: adding any value to the result adds corresponding emission, but despite visuals, brightness from combination above does not.\n\n\n- Open attached file\n[cycles_where_is_emission__bug.blend](attachment)\n\n\n", "Noise Texture Fac output fails when using exact unit inputs and exact scale values\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.92.0\nBroken on the latest 2.90, 2.93 and 3.0.0 commits I could find.\nAlso broken on 2.80.75 but there was no W input back then.\nAlso broken on 2.79b\n\nThe Noise Texture Node exhibits weird values for its Fac output (and by extension*, the Red channel of it Color Output) when using default properties. The Green and Blue channels seem to work properly though.\nThe Fac output of the Noise Texture Node produces unexpected results on discrete unit inputs, and on exact unit scales. The W seed also has an effect when it's set to an increment of 0.5.\n\n*As you may know the red channel of the color output of the noise texture contains the same values as the Fac output.\n\nDefault Scene. Create a cube and scale it way up in edit mode.\n\nCreate a new material, Texture Coordinates node > Object Output > Separate XYZ > Z Output > Math node set to Ceil, Round, Floor, or Truncate > Noise Texture > Fac Output\n\n\nProblem : If you keep the noise texture at the default scale of 5, the shader will produce a continuous value of 0.5 on the whole mesh\n\n\n\nExpected result : Get a different value for each subsequent strata of the material, as exhibited if you plug in the color output or try out the green or blue channel of the color output.\n\n\n\nTroubleshooting : If you change the scale of the noise texture node, the behaviour of the randomization seems to work again.\n\n\n\nBut, there is a band that consistently stays at exactly 0.5 value whatever the scale. \nThis may be intended behaviour since the input / output values at Z = 0 is the same whatever the scale. However the same behaviour isn't shown on the Green and Blue channels of the color output...\n\n\n\nAnd, every time the scale is set to a precise unit, (1.000, 2.000, etc.) the continuous value of 0.5 appears again.\n\n\n\nAlso, there is a weird banding of exactly 0.5 output values when using scales of *.500, *.250,*.125, scale values :\n\n\n\n\nMoreover, if the user chooses to use 4D input, and tweaks the W value to something other than 0 (I assume it is the default seed value even when using 1D), the random expected behaviours is again present.\n\nBut there are certain combinations that produces an unexpected number of values that are exactly 0.5. Example :\n\n\n\nAlso, if the W value is set to an increment of a half unit (0.5, 1.0, 1.5, etc.), this happens.\n\nFor Pair scale unit size (eg 46), continuous grey (0.5) value\n\n\n\nFor odd scale unit size (eg 45), unexpected number of exactly 0.5 value bands.\n\n\n\nMaybe this is intended behaviour but it seems odd that the Fac outputs returns a single value when the Green and Blue channels act \"truely\" randomly in this case.\n\n[noise_fac_test.blend](noise_fac_test.blend)" ]

[ "Eevee Specular BSDF shader compile error\nOperating system: Windows [errorteststone.blend](errorteststone.blend)\nGraphics card: RTX 2060 (optix on\n\nBroken: 2.93 alpha\nWorked: 2.92 beta\nThe shader doesn't work in 2.93. The same setup produces a pink error shader.(No image textures.) Attached blend file.\n\nCaused by 7f7e683099\n\nNode-setup\n \n\n2.92 Output\n \n\n2.93 Output\n" ]

[ "Sculpt Mode Painting\nThis task outlines the remaining To Do's for fundamental sculpt mode painting.\n\n### Color Swapping\n\n- `X` for switching primary and secondary color\n- The current shortcut for `X` for the draw brush will be removed.\n\nIn one of the upcoming releases all brush shortcuts in sculpt mode will be removed anyway, for maximum user customization.\n\n### Canvas Picker & Viewport Color\n\nSince painting is something optional in sculpt mode we need to make sure that:\n- Color Attribute shading isn't enforced\n- Color attributes will be displayed when using painting tools\n- A fast way of choosing color attributes in the UI\n- An optional & discoverable way of switching the viewport shading for all objects (optimal painting scenario)\n\nThe proposal for this is:\n- Use [D16241](D16241) canvas picker UI in sculpt mode. Always visible but grayed out if viewport shading color is not `Attribute`\n- Whenever a painting tool is active, the canvas picker is no longer grayed out and the color attribute viewport shading is enforced in workbench shading on the active object only\n- In the canvas picker popover, add a message or button to switch the viewport color to Attribute if this is not yet the case, so that colors stay visible between brushes/tools. \n- Remove the current behavior of automatically switching the viewport color when a painting tool is used\n\nTo make sure the sculpting experience is already taking color attributes into account, the default sculpting template and workspace should use color attributes for viewport shading.", "Weight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\nOperating system: Linux-4.15.0-147-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.1\n\nWeight paint mode can show influences of non selected vertexgroups (if weight is controlled by multiple dynamic paint brushes)\n\n[PBdynamicPaint_check.blend](PBdynamicPaint_check.blend)\n\n- open .blend\n- go to weightpaint mode\n- play animation\n- in the mesh properties, change from one vertexgroup to the other back and forth\n- influence of one group is (partially) still visible when switching to the other\n\n", "Texture properties not working with OSL enabled and unpacked textures\nOperating system: Linux-5.11.7-arch1-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 520 (SKL GT2) Intel Open Source Technology Center 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.92.0\nBroken: version: 2.93.0 Alpha\n\nI have a texture with RGB channels set to 1 and alpha set to 0. When trying to use this texture with OSL, the alpha property (at least) of the image texture node does not work when the texture is unpacked. I set it to channel packed, expecting the color data to be always white. The problem is that when the texture is unpacked, the color data is black.\n\n1. Open the attached file.\n2. Set viewport shading to rendered.\n3. The plane shows as white (as it should).\n4. Unpack the texture.tga file.\n5. Toggle between preview and rendered viewport shading to refresh.\n6. The plane now shows as black.\n7. Pack the texture again.\n8. The plane shows as white again.\n\n[bug.blend](bug.blend)", "Undo Makes Completed Renders Disappear From View Render Window Slots\nOperating system: Windows 10 Build 19043\nGraphics card: Nvidia RTX 3090\n\nBroken: 2.92\nWorked: Can't remember, but I don't recall this happening before\n\nUndo makes completed renders disappear from other slots in the View Render window. Some of them are preserved, but the more you undo, the more disappear from other slots.\n\n1. Load default scene (with the cube)\n2. Render scene\n3. Go to the cube's shader and change its base color\n4. Switch to next unoccupied slot in the View Render window\n5. Render scene\n6. (optional) Repeat steps 3-5 as many times as you like\n7. Go to View Render window and scroll through slots to verify all renders are there (with J key)\n8. Activate undo (ctrl+z)\n9. Go to View Render window and scroll through slots. Some will be missing.\n10. Activate undo again and more will be missing.\n\nThis doesn't seem like intended behavior, and I've replicated this issue on a different machine. Hope this helps!\n\nEdit: I've replicated this issue in 2.91, 2.90 and the latest LTS release. I assume intended behavior is for undo to change the shaders back, but for renders you've completed to remain in their slots.", "Blender 2.90/ 2.91 Sculpt Vertex Paint - Stencil not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Beta, branch: master, commit date: blender-2.90.0-0e280b96ca82-windows64\nWorked: I think this last work in 2.83.2 or 2.83.1\n\nSculpt Vertex Paint - Stencil not working\n\n\n[BlenderBug.blend](BlenderBug.blend)\n\nAdded colored image to texture\nChange texture mapping to stencil\nImage is coming out as black and white on the screen and image is not being transferred on the object.\n\nI have tried changing Blender Mode and Color Space but it didn't work.\n\nAlso I am not sure if this suppose to happen but the image for stencil disappears when I tick Color Ramp under Color in Texture Panel.\n\n", "Viewport render gives black background when overlays are turned off.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: \n - 2.92.0 Beta\n - 2.92.0 Beta \nWorked: \n - 2.92.0 Beta\n - 2.91\n\nviewport render gives black background, this happens only when the overlays are turned off.\n\nopen the file, go to view/viewport render image.\n\nthank you\nMax\n\n\n[black_bg.blend](black_bg.blend)\n\n\n", "Curves don't have 'All Edges' option for wireframe\nBroken: 2.80\n\nMesh objects have the toggle for its viewport display wireframe to render all edges, but curve objects don't.\n\n\nOpen the attached file and look for the 'All Edges' option.\n[Wiref.blend](Wiref.blend)\n", "Object properties In-front doesn't work in viewport shading\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nObject properties In-front doesn't work in viewport shading\nAll the other options works in Object properties/viewport display, except for In-front \n\n\n- Open attached file\n- Go to Viewport Shading\n[lookdev_in_front_bug.blend](lookdev_in_front_bug.blend)\n", "Alembic doesn't import vertex colors for meshes made of only vertices\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.125.06\n\nBroken: Version: 3.6.0\nWorked: Never.\n\nWhen importing Alembic caches, vertex colors are only imported correctly when the imported geometry is made of faces.\nWhen the geometry is only vertices, no vertex colors are imported. (ex. point clouds)\n\nI suspect this has to do with vertex colors encoded as a point attribute instead of a face corner attribute.\nI've checked both provided alembic files in other software to make sure they're not the issue and they work fine everywhere else.\n\n1. Import mesh.abc.\n2. Vertex colors are read correctly and are stored and accessible as a Face Corner attribute.\n3. Import `points.abc`.\n4. Vertex colors aren't read at all, expected behavior is that they're stored stored as a Vertex attribute.\n", "The viewport grid is visible over the curves hair \nOperating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46\n\nBroken: version: 3.3.0 Beta\n\nThe viewport grid is visible over the curves hair with cycles render engine.\n\nWith cycles > Press render preview on the viewport.\n[grid_cycles_and_hair_bug.blend](grid_cycles_and_hair_bug.blend)\n\n{[F13429852](image.png) size=full}", "Retopology Overlay Color Location\nA user noted that the overlay can be difficult to see when using random object colors: 15\n\nOne solution would be to move the color from the theme to the workspace, and expose it in the overlays popover.\nI think that just exposing the color isn't enough, because editing a preference outside of the preferences window does not autosave.\nMeaning that if you change the color in the popover, save your project, and restart Blender, the color would be back to default.", "Diffuse Direct, Indirect Bake to Vertex Color Artefacts\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nWorked: This has never worked properly (At least in my experience)\n\nWhen baking Diffuse light to vertex color, black triangles and random dark spots appear in vertex color. This effect is more apparent with:\n- Area lights.\n- Emissive surfaces.\n- Lights with very high power.\n\n1. Create geometry and give each a byte_color vertex color channel.\n2. Place area lights in scene with high power.\n3. Bake diffuse direct and indirect to color attribute.\n\nSee .blend of my project attached. In the file i've already baked the emissive light to vertex color where you can see the artefacts. Switch to cycles live render view to see the correct output. I think the tiled texture may have something to do with it. I've added a tiled texture and packed it in the example.\n\n", "Material setting \"show_transparent_back\" (Show Backface) gives weird results\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nMy materials are messed up by having blend mode set to \"Alpha Blend\" and \"Show Backface\" set true.\n(The checkbox for \"Show Backface\" pops up if a materials blend mode is set to Alpha Blend\")\n\nIs this normal behaviour?\nThe intend here was to see every side of the cube with a bit of transparency.\n\n[ShowTransparentBackBug.blend](ShowTransparentBackBug.blend)\n1. Add a Cube (subdivide a few times) and give it a material\n2. Go to material settings and set the materials...\n- Blend mode to \"Alpha Blend\"\n- Backface Culling to False\n- Show Backface to True", "EEVEE: Reduce viewport render time by only render needed draw passes.\nCurrently all material + effect passes are rendered even when eventually they aren't needed. This can happen when viewing a render pass in the viewport. For example:\n* Mist\n* AO\n* Shadow\n* AOV (after [D7010](D7010) has been comitted)\n* etc\n\nWe should see how we can optimize the rendering pipeline so that only the passes that are needed are drawn. This would lead to a more responsive viewport in these cases.", "No visible mesh on Viewport Screenshot in sculpt mode with Multires\nOperating system: Linux-6.2.11-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits, X11 UI\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhat the title says.\n\n- Add a cube\n- Enter sculpt mode\n- Add a multiresolution modifier and subdivide\n- Use the operator: Header -> View -> \"Viewport Render Image\"\n\n" ]

[ "Fourth and subsequent vertex color / UV layers displayed black\nOperating system: Ubuntu 18.04\nGraphics card: GeForce GTX 1070\n\nBroken: 2.8 2019-01-19 b0dee09a6d55\nWorked: 2.79\n\nAfter creating more than 3 vertex color layers on an object, the fourth and all of the following are displayed completely black.\n\n1) Start blender with the default startup. \n2) Switch to Vertex Paint Mode.\n3) Open the \"Object Data\" Tab in the Properties Editor\n4) In the Vertex Colors Panel, add three more Vertex Color layers -> The fourth is displayed black.\n\n", "Vertex Color Layers support only 3 layers (in Viewport)\nOperating system: Win 7 Ultimate 64 SP1\nGraphics card: GTX 1060 6GB\n\nBroken:\nblender-2.80-dc3b5024be1a-win64\nblender-2.80-96f762500ef9-win64\nWorked: works on 2.79 (just tested it). Haven't had the need on 2.80 prior to couple of days ago ... so don't know if it ever worked.\n\nOnly 3 Vertex Color Layers can be seen in the Viewport. You can blind paint more then 3, and it does work when used in the ShaderEditor. But only 3 can be viewed in the viewport. The 4th one is displayed as all black.\nSo if you have 4 of them and forth one is displayed as black, if you delete one of the other 3 VertexColorLayers - then the forth one is displayed (because now you have only 3 of them again)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n- Creat a Cube\n- Add SubdivisionModifier with 5 levels. Apply the Modifier. (This is to create enough vertices for painting)\n- Enter VertexPaint and scribble something.\n- in ObjectData Tab, under VertexColors add another Layer. Scribble some more\n- Repeat previous step one more time ( you will now have 3 layers and everything works fine)\n- Repeat previous step one more time. Now you have 4 VertexColor Layers and this is where the bug kicks in. That fourth layer is going to be displayed in viewport as Black.\n\n- If you delete one of the first 3 layers, that fourth one is now displayed in the viewport (because the total of VertexColorLayers is gonna be 3)\n\nIf you can not reproduce this. I can provide a startup file with the default cube and 4 VertexColorLayers\n" ]

[ "Clicking \"Particle Edit\" mode causes Blender to crash\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.89\n\nBroken: version: 3.5.0\nWorked: I dunno\n\nCan't enter into the Particle Edit mode.\n\nThis issue is probably related to: 106927#issue-96303\n\nIn the sample file, in the Curves Sculpt mode, after converting my Curves (name of the layer: \"my_test_4\") to a particle system, then select the newly converted particle system and enter into the Particle Edit mode, and Blender crashes.\n\n\n\nA sample file is attached. Thank you!\n\n", "simulation in new scene causes crash in original scene's simulation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 6)\nWorked: (optional)\n\n**steps**\n- make cube an active rigid body. \n- play simulation\n- then click on new scene button and on full copy.\n- in the new scene, rewind playhead to frame 0\n- run the simulation.\nBlender should crash.\n\nThere are more ways to cause crash when full scene copy is done (see comments), but I guess these will stem from single issue.", "Crash using blender_debug_log.cmd and \"Reload Scripts\" in Cycles preview render\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.91\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nLoading Blender with blender_debug_log.cmd, it crash immediately when I try to reload the scripts if Cycles is running. This is not happening when launching blender.exe \n\nLaunch blender 2.8 using blender_debug_log.cmd.\nIn the view 3d, choose Cycles as render preview.\nIn the search bar, look for \"Reload Scripts\" and click on it.\nBlender Crash.\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n", "BMesh.free causes crash under curtain conditions\nOperating system: Linux-5.16.16-200.fc35.x86_64-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.0 Alpha\n```\nall 3.x versions are broken, 3.0.0 sometimes works\n```\nWorked: 2.93.8 LTS\nOn Fedora also some 2.91 versions have been affected, according to rebuild agains newer pythons.\nReported on redhat bugzilla: show_bug.cgi?id=1872980\n\n[blender.crash.txt](blender.crash.txt)\nUsing my python addon blender crashes on _PyEval_EvalFrameDefault or _Py_Dealloc.\n\nUnable to describe simple steps to reproduce. This happens using my python addon, but if a bug is in addon, still shouldn't crash blender but throw an python traceback.\nWhen I delete line describen in crash log's backtrace, then another row is marked as a problem, so unable to identify exactly what's happening.\nPlease, let me know, if you need more information.\n\n----\n\nEdit, run this script with the following command line arguments: [boxmaker_crash_single_script.py](boxmaker_crash_single_script.py)\n`blender -b --factory-startup --python boxmaker_crash_single_script.py`\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Old blend file corrupts to crash blender, I guess\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 20.11.2 27.20.14540.4003\n\nBroken: version: 3.0.0\n\nCrashes here and there. RN I witness crush form select/deselect. help plz ;c\n\nI do, tho, have installed two PROBABLY outdated addons BUT in new file crash doesn't seem to happen.\n\nThe problem is - Idk exact steps, but overall it takes to select/deselect all/smth at all few times\n\nSteps\n- Open the provided .blend below\n- Enter edit mode on the main SN4K3Mesh\n- Select-All, De-Select-All (Repeat)\n\n[#94213-asan.txt](T94213-asan.txt)\n\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF715993808\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF71599380C\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n\n[SN4K3.blend](SN4K3.blend)\n\n[SN4K3.crash.txt](SN4K3.crash.txt)", "Blender Crashes when deselecting Name-fields\nOperating system: Windows-10\nGraphics card: NVIDIA GeForce RTX 3070\n\nalso tested on:\nOperating system: Windows-11 Home - Microsoft Surface\nGraphics card: - / 11th Gen Intel(R) Core(TM) i7-1185G7\n\nBroken: (tested with)\n- version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a, type: release\n- version: 3.5.1, branch: blender-v3.5-release, Date: 2023-04-24 18:11, hash: e1ccd9d4a1d3\n\nWorked: -\n\nFor a specific project, if I select any Text field that contains the name of an asset (texture, object, scene, ...) and click anywhere else within the Blender window, Blender will crash. \n\nThis error does not appear for other projects of mine or a new one.\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open file\n2. Navigate to Texture\n3. Create a new Texture\n4. Select Texture name (no need to alter the name to reproduce the error)\n5. Click into e.g. Viewport or hit Enter\n\nI created a copy of the problematic project, deleted all of its content and used the Blender cleanup feature to remove any remaining data blocks. Still the issue persists. Except for the missing shutdown logs due to the crash, the Debug Log doesn't show any differences to a normal file AFAIK.\n\nBlender does NOT crash when I use \"Escape\" to exit the field.\nTo be precise, the crash happens when deselecting \"Name Fields\" in the outliner, the Properties Panel or similar.\nThis doesn't happen in Search fields or Value fields that take e.g. floats for properties like \"Strength\" etc.\n\nThe project (used as asset library) worked fine yesterday and as far as I'm aware no updates were installed. I tried updating my NVIDIA driver but to no avail.\n\nNext, I'll try to copy my assets to a new file.", "Blender 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "Crash at the end of preview generation for a deleted datablock\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: -\n\nBlender crashes if you trigger the generation of a preview for a data block and then delete the data block itself. Obviously, the preview data is generated, but since the datablock itself no longer exists, I get an `EXCEPTION_ACCESS_VIOLATION` and a crash.\n\n\nRun simple script in attached *.blend file.\n\n", "Crash of simulation demo file related to bevel modifier on a simulated mesh\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Beta\n\nin the file, play the Animation, and move \"Empty\". It should crash within 1 second.\nI find no crash when there's no bevel modifier.\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Splash Screen: \"Updated Preferences\" Infobox\nFor Blender 4.0 there will be various default keymap updates (#105298) that users should be aware of when loading their 3.6 preferences.\nThis task will become necessary once those patches are merged.\n\nThe idea is to add a popup to make users aware and point them towards resources to inform themselves. This will avoid frustration and many invalid bug reports.\n\n### Mockups\n\nThe addition of an info icon to the operator button that loads the previous preferences (As an indication that this will open a popup with more info).\n\n\n\nA possible layout for the main popup.\nThis info might be very important for some users, so the popup can only be closed with an explicit button press.\n\nThis also includes a an operator button \"Read more...\" that links to the relevant release notes page without closing the popup itself. An added border would make this more recognisable as a button.\n\n\n\nThis popup could then be used for future releases and other important changes (only if absolutely needed).\n\n", "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "Crash when run the script code follow\nOperating system: Mac 11.4\nGraphics card: Intel Iris 1536 MB\n\nBroken: 3.0.1(2022-01-26)\n\nBlender crashed when running the script followed in \"Scripting Window\":\n\n```\nimport bpy\n\nfor obj in bpy.data.collections['Bg_objects'].all_objects:\n obj.is_holdout = True\n```\n\nAddressSanitizer error log:\n```lines=20\n==34714==ERROR: AddressSanitizer: heap-use-after-free on address 0x00015d792c38 at pc 0x00010523645c bp 0x00016fdfa1d0 sp 0x00016fdfa1c8\nREAD of size 8 at 0x00015d792c38 thread T0\n - 0 0x105236458 in rna_iterator_listbase_next rna_access.c:4677\n - 1 0x1053cc940 in Collection_all_objects_next rna_collection_gen.c:209\n - 2 0x105234920 in RNA_property_collection_next rna_access.c:3690\n - 3 0x105f6c330 in pyrna_prop_collection_iter_next bpy_rna.c:7107\n - 4 0x11366ad40 in _PyEval_EvalFrameDefault ceval.c:4001\n - 5 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 6 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 7 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 8 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 9 0x10a275444 in text_run_script text_ops.c:773\n - 10 0x10a275284 in text_run_script_exec text_ops.c:812\n - 11 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 12 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 13 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 14 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 15 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 16 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 17 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 18 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 19 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 20 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 21 0x1030043ec in WM_main wm.c:623\n - 22 0x10000ba94 in main creator.c:544\n - 23 0x1454710f0 in start+0x204 (dyld:arm64e+0x50f0)\n\n0x00015d792c38 is located 8 bytes inside of 80-byte region [0x00015d792c30,0x00015d792c80)\nfreed by thread T0 here:\n - 0 0x145a890f0 in wrap_free+0x98 (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d0f0)\n - 1 0x1151b28e8 in MEM_lockfree_freeN mallocn_lockfree_impl.c:116\n - 2 0x114b67940 in BLI_freelistN listbase.c:463\n - 3 0x1003acbf8 in collection_object_cache_free collection.c:816\n - 4 0x1003aca74 in BKE_collection_object_cache_free collection.c:826\n - 5 0x100e4b080 in BKE_main_collection_sync_remap layer.c:1366\n - 6 0x1059bcf0c in rna_Object_hide_update rna_object.c:370\n - 7 0x105257fa8 in rna_property_update rna_access.c:2069\n - 8 0x105257bac in RNA_property_update rna_access.c:2138\n - 9 0x105f50268 in pyrna_py_to_prop bpy_rna.c:2083\n - 10 0x105f54308 in pyrna_struct_setattro bpy_rna.c:4453\n - 11 0x1135de558 in PyObject_SetAttr object.c\n - 12 0x113667dd0 in _PyEval_EvalFrameDefault ceval.c:2850\n - 13 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 14 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 15 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 16 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 17 0x10a275444 in text_run_script text_ops.c:773\n - 18 0x10a275284 in text_run_script_exec text_ops.c:812\n - 19 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 20 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 21 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 22 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 23 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 24 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 25 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 26 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 27 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 28 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 29 0x1030043ec in WM_main wm.c:623\n\npreviously allocated by thread T0 here:\n - 0 0x145a89380 in wrap_calloc+0x9c (libclang_rt.asan_osx_dynamic.dylib:arm64e+0x3d380)\n - 1 0x1151b13b8 in MEM_lockfree_callocN mallocn_lockfree_impl.c:222\n - 2 0x1003b5754 in collection_object_cache_fill collection.c:754\n - 3 0x1003b5d20 in collection_object_cache_fill collection.c:775\n - 4 0x1003b53b0 in BKE_collection_object_cache_get collection.c:786\n - 5 0x1053cc5d8 in rna_Collection_all_objects_begin rna_collection.c:54\n - 6 0x1053cc2d0 in Collection_all_objects_begin rna_collection_gen.c:200\n - 7 0x105233a88 in RNA_property_collection_begin rna_access.c:3674\n - 8 0x105f6c158 in pyrna_prop_collection_iter_CreatePyObject bpy_rna.c:7076\n - 9 0x105f67ef0 in pyrna_prop_collection_iter bpy_rna.c:7083\n - 10 0x11357f400 in PyObject_GetIter abstract.c:2813\n - 11 0x11366ac34 in _PyEval_EvalFrameDefault ceval.c:3958\n - 12 0x113664fe0 in _PyEval_Vector ceval.c:5065\n - 13 0x113664f38 in PyEval_EvalCode ceval.c:1134\n - 14 0x105f1812c in python_script_exec bpy_interface_run.c:121\n - 15 0x105f18d5c in BPY_run_text bpy_interface_run.c:216\n - 16 0x10a275444 in text_run_script text_ops.c:773\n - 17 0x10a275284 in text_run_script_exec text_ops.c:812\n - 18 0x103035044 in wm_operator_invoke wm_event_system.c:1335\n - 19 0x103033cf4 in wm_operator_call_internal wm_event_system.c:1530\n - 20 0x10303ad6c in WM_operator_name_call_ptr wm_event_system.c:1577\n - 21 0x10303b978 in WM_operator_name_call_ptr_with_depends_on_cursor wm_event_system.c:1765\n - 22 0x109722ff8 in ui_apply_but_funcs_after interface_handlers.c:1008\n - 23 0x10971b1d4 in ui_handler_region_menu interface_handlers.c:11383\n - 24 0x10304ab2c in wm_handler_ui_call wm_event_system.c:698\n - 25 0x103047864 in wm_handlers_do_intern wm_event_system.c:3025\n - 26 0x1030426f4 in wm_handlers_do wm_event_system.c:3145\n - 27 0x1030406f0 in wm_event_do_handlers wm_event_system.c:3675\n - 28 0x1030043ec in WM_main wm.c:623\n - 29 0x10000ba94 in main creator.c:544\n```\n\n- Open attached file\n- Go to Scripting workspace\n- Run the above script\n[bug.zip](bug.zip)" ]

[ "Mac Blender 2.83 (2.83 2020-02-22) immediate crashes after clicking on \"New File > General\" in the splash screen.\nMac OS X 10.15.3 (19D76)\n\nBlender 2.83 (2.83 2020-02-22) immediately crashes after clicking on \"New File > General\" in the splash screen. Clicking outside the splash screen opens Blender with the standard cube. Opening the splash screen from within Blender does not crash Blender when clicking on \"New File > General\".\n\nAttached is the crash report.\n\n[Blender283CrashReport.txt](Blender283CrashReport.txt)", "Crash when click on recent files (splash screen)\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130\n\nBroken: version: 2.83 (sub 4)\nWorked: (optional)\n\nWhen click on recent files option (splash screen) Blender crashes.\n\nI open Blender. Then click on a recent file from splash screen. Blender closes automatically.\nBut if I close the splash and re-open this from main menu, this works properly.\n\n", " 2.83.4 Immediate crash upon using splash screen to open Recent/ New files.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nWorked: (in prior build)\n\nLoad attached file after opening. Immediate crash. Did do this prior build.\nJust double checked. Crashes immediately if loaded from my Most Recent List, but doesn't crash if I just use Open. Tried it twice??\n\nLaunch Blender 2.83.4, (this build) Open attached file. Save. Close. \nRestart Blender, click on Most Recent record of this file, Crash. Did not do this on prior build. \nOpens just fine in 2.82.6\n[boy_v11full.blend](boy_v11full.blend)\n\n", "Exit from Blender when opening a blend from the Splash Screen\nOperating system: Linux-5.3.0-41-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.50\n\nBroken: version: 2.83 (sub 4)\nWorked: (optional)\n\nExit from Blender when opening a blend from the Splash Screen\n\nWhen launching Blender I open a file from the Splash Screen.\nBlender closes.\nThe same file opens if I do File / Open Recent.\nMany thanks to all of you for your fantastic work. \n[ {[F8362545](Bug_Ouverture_Depuis_SplashScreen.blend)}]\n\n", "Crash to desktop when opening recent files from splash screen\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 4)\nWorked: b8567b704bb9\n\n\n - Start Blender\n - Chose a file from a list on a splash screen.\n\nThis happens only when you try to open a file from a splash screen and only on fresh start. Opening files from **File > Open Recent** works fine. When you close the splash screen and then reopen it again from **Blender > Splash Screen** then you can open files from it normally.\n[recent_files_crash_test.blend](recent_files_crash_test.blend)" ]

[ "Origin calculate incorrect normal orientation by snap to face\nOperating system: Windows 11, MacOS\nGraphics card: Nvidia RTX 3060TI, M2\n\nBroken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b, type: release\nbuild date: 2023-03-29, 06:36:20\nWorked: Doesn't works since origin edit was relesed\n\nOrigin calculate incorrect normal orientation by snap to face, after you apply object rotation.\n\nLet's imagine you have object with random orientation in world space and then rotation was applied. And i need restore this orientation. In this case you can activate ORIGIN edit tool and snap it to face with rotate align active and as result you expected origin orietn will be calculated by vector of face normal. \n\nBut as we can see orient not calculates properly in this case. This is very old bug which live in part of 3d cursor as well, but this is other story.\n\nI've attached .blend file and video demostaration of issue.\n\n", "Stereoscopic render - Convergence Plane doesn't show in the cameraview while in viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.0\nWorked: version: 3.4.1\n\nConvergence Plane doesn't show in the cameraview while in viewport. It work when the mode is in Toe-in but not in off-Axis.\nI made the exact same steps in 3.4 and it works.\n\n- Render engine : Cycles\n- Output properties : stereoscopy\n- Objecte data properties : \n - Lens type : panoramic \n - Panorama type : Equirectangular\n -Stereoscopy \n - Mode : Off-Axis\n -Convergence Plane : doesn't change in the cameraview but we can see the plane in the viewport\n\n\n[Based on the default startup .blend file (as simple as possible)]\n\n", "Viewport Tools Settings panel appears after reload\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\n- 2.92 - 2.8x\nWorked: Never\n\nI don't know, if this is intended. I unchecked Header in a viewport and everything disappeared. But after reloading file, \"Tools Settings\" panel was still present, even though Header is unchecked.\n\n- Uncheck Header\n- Save file and close Blender\n- Open Blender and load that file \n\nThe header itself is still hidden, but the tool settings are back.\nTo hide the tool settings again, the header must be re-enabled and disabled.", "Camera texture coordinate output in orthographic view is different from orthographic camera\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.0.0\n\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode\n\nTexture coordinate camera output does not give expected results in the z component when viewing through the viewport in orthographic mode.\nTo see this seperate the z component and the problems will be directly visible.\nThis issue does not appear when viewing through a camera.\n\nTest file:\n[Camera_test.blend](Camera_test.blend)\n\nThank you and have a nice day!\n", "Statistics Viewport Overlay Showing Incorrect Value\nOperating system: Windows 11\nGraphics card: Nvidia GeForce RTX 1650\n\nBroken: 3.6\nWorked: Every other version I've used so far\n\nWhile working in the viewport, the \"Viewport Overlay: statistics (edges count)\" glitches out and shows the wrong number. Sometimes being absurdly high. The image shows the main objects in my scene with the most geometry, mostly being 2k to 10k faces each. It gets a bit annoying when I can't see the right count. I'm not sure how to reproduce the error on command, but I'll keep looking!\n\nBased on the default startup or an attached .blend file (as simple as possible).\nIt happens mostly while I swap in and out of pose mode but then again, I'm not too sure. However, this is usually the last action I take before I notice. I'm sorry for the insufficient information, but I hope you find the problem.\n\n", "The viewport grid is visible over the curves hair \nOperating system: Linux-5.15.14-1-lts-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.46\n\nBroken: version: 3.3.0 Beta\n\nThe viewport grid is visible over the curves hair with cycles render engine.\n\nWith cycles > Press render preview on the viewport.\n[grid_cycles_and_hair_bug.blend](grid_cycles_and_hair_bug.blend)\n\n{[F13429852](image.png) size=full}", "Wrong reflection in Reflection Plane when Ambient Occlusion is also turned on\nIntel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB\nWindows 7 x64\n\nBroken: 2.8, 2.9\nWorked: n\\a\n\nReflection Plane object produces wrong reflections when Reflection Plane is nearly perpendicular to camera and Ambient Occlusion is turned on.\n\n1. Open provided Blender file, switch to Rendered view and observe how Reflection Plane reflects the opposite wall as almost black.\n2. Disable Ambient Occlusion and reflection will become normal.\n3. I have also noticed that if you change Ambient Occlusion value to something like 40 mm, reflection will be turned into a gradient.\n4. Moving Reflection Plane away from the wall does absolutely nothing, if you switch to the second camera that faces Reflection Plane straight on, back wall will look normal but side walls will become dark.\n[WrongReflection.blend](WrongReflection.blend)\n\n", "Inconsistencies between 3D Viewport and Viewport Render Image using the GPU Shader Module\nOperating system: Ubuntu 18.04, Windows 10\nGraphics card: GeForce GTX Titan X, GeForce GTX 1080 Ti\n\nBroken: \n2.83.0\n2.90.0 Alpha\nWorked: Never\n\nRendering the `3D Viewport` with `3D Viewport/View/View Render Image` (i.e. OpenGL rendering) does not render elements drawn with the [GPU Shader module ](gpu.html).\n\nThe problem is illustrated in the following example, which shows the `3D Viewport` (left) and the rendered result of `View/View Render Image` (right).\nThe points drawn with the GPU shader module are neglected during OpenGL rendering.\n\n\nExcecute the [3D Lines with Single Color ]] example of the [[ https:*docs.blender.org/api/current/gpu.html | GPU shader module documentation ](https:*docs.blender.org/api/current/gpu.html#d-lines-with-single-color).\nThen, render the results with`View/View Render Image` as shown in the image below.\n\n\nThe lines visible in the 3D Viewport (left) are missing in the rendered result (right).\n ", "Viewport render still cannot render \"non-antialiased\" Outline overlay.\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHi, I'm trying to get a non anti-aliased image out of the viewport render option, but the final image is still anti-aliased.\n\n\n\nUsing these settings in the preferences:\n\n\n\n\n", "'Frame selected' with 'Lock To 3D Cursor' sets weird focus\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0 Alpha\nand 3.1\n\nIf you select something and do 'view3d.view_selected' while View Lock is set to 'To 3D Cursor', the view will focus on the cursor instead of the selected object and if you pan and do 'Frame selected' again, you will get somewhere near the cursor instead of the selected object.\n\nAlso, calling 'view3d.view_center_cursor' won't do anything while 'To 3D Cursor is active'.\n\n1. activate 'Lock': 'To 3D Cursor'\n2. select an object\n3. View -> 'Frame Selected'\n[Video.mp4](Video.mp4)\n\n\n", "Bug with environment texture\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 3050 Laptop GPU\n\n3.6.2\n\nAfter I checked and unchecked \"Open Shading Language\" checkbox Blender crashed, after that I opened my project and turned rendered viewport the environment texture become a one solid color, and as I was rotating my camera it was changing the color.\n\nBased on an attached .blend file you can go to the Render viewport and take a look at this error.\n\n", "Animation workspace: Switching between tabs causes viewport to change\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.0\nWorked: Not sure\n\nChanging between the Texture Paint tab and Animation tab causes the Animation viewport to take on properties of the Texture Paint viewport. If this is working as expected it's not ideal.\n\nOpen a new General 3D project. (Or use attached blend)\nSelect the Animation tab. The viewport should look normal.\nNow go to the Texture Paint tab.\nGo back to the Animation tab.\nThe viewport has taken on the properties of the Texture Paint tab.\n\n(A similar issue with the UV editor and Animation tab also occurs.)\n\n[TexPaintToAnimationTab.blend](TexPaintToAnimationTab.blend)\n\n\n", "Eevee alpha blend mode bug\nOperating system: Linux-5.4.0-74-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\n\nThis bug happened since blender 2.90\n\nIn the scene the two objects with alpha blend mode, flip the transparency depending on the point of view.\n\n[0000-0050.mp4](0000-0050.mp4)\n\nTest file:\n[Ui1.blend](Ui1.blend)\n", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n", "Enable pen tilt support by default\nThis task keeps track of the tested devices in order to enable pen tilt support by default.\nThe reason this feature was committed as experimental was because it is not clear what devices and OS configurations are supported and what devices we are planning to support. \nRight now the feature can be enabled in alpha builds as a experimental feature and used in some sculpt tools (draw sharp, scrape, clay strips...). \n\n\nWorking:\n- Wacom Cintiq Pro 16 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Manjaro 19 GNOME \n- Wacom Intuos Pro M - Ubuntu 20.04\n- Wacom Intuos Pro M - Pop OS 20.04\n- Wacom Intuos Pro M - Windows 11\n\n- XP-Pen Artist 13.3 Pro - Windows 10\n- XP-Pen Artist 15.6 Pro - Windows 10\n\n\n\nNot working:\n- Wacom Mobilestudio Pro 16 - Windows 10 (y tilt axis is inverted)\n- Huion Kamvas 13 - Windows 10 (y tilt axis is inverted)\n" ]

[ "Startup File Viewport view is tilted by around 0.8 degrees since 2009 (Blender 2.5)\nNow, before you click away, I know what you're thinking, how can the default 3D View be tilted? This guy must have messed something with his camera, or activate the trackball views settings by mistake right?\nWell believe it or not, the default 3D view (as in, the view of the default 3D viewport in the blender startup file) is tilted by around 0.8 degrees.\n\nHere is a quick proof I just threw together, I believe it's important for you to watch it until the end, as the main proof really comes around 0:40.\n\n[tiltedview.mp4](tiltedview.mp4)\n\nAs you can see, when trying to align your view with the cube, it doesn't lined up, this can be seen by the jagged selection edges, and of course with the Camera aligned to view.\nYou can also see at 0:35 that when switching to the Front Orthographic viewpoint the view gizmo itself is rotating on the X axis a little bit.\nAnd of course, when switching back to the normal Perspective view, the viewport view is realigned, enhance why the Camera that's been re-aligned with the view is now sitting properly on the X axis. (see 1:10)\n\n**Now, why is this happening?**\n\nAfter a bit of investigating, I discovered that the issue as been around since **Blender 2.5**, which is now more than **10 years ago**\nBlender 2.5 was the first version to have the default startup file view not lined up with one of the orthographic axes. But it also had the Trackball orbiting style as default instead of Turntable. This might explain why, 10 years ago, a blender dev might have tried to get the view somewhat lined up in trackball mode, and got it almost right.\nHere's a quick demo of the same problem on 2.5 Alpha 0:\n\n[tilted25.mp4](tilted25.mp4)\n\nNow, while this isn't a top priority issue, this as been around for quite some time now, so this is not really an inquiry for an immediate fix, but more of a way too long report I did since I couldn't find anything on it online, and it drove me crazy for a few hours when I first discovered it.\n\nBroken: 2.5 Alpha0 and beyond\nWorked: 2.49b, where the view was orthographic by default\n\nStart Blender, use the viewport (Will disappear if snapping to an Orthographic axis)", "Default 3D view is tilted slightly\nOperating system: Windows 10 21H2\nGraphics card: Nvidia GTX1080\n\nBroken: 3.0\nWorked: Not sure if this ever worked after 2.8\n\nBlender's 3D view camera (NOT the camera in the scene) seems to be slightly tilted to the left by factory default.\nThis can be tested by changing mode into Orthographic and rotating the view to an approximate side view (NOT by going into an exact side view).\nGoing into an exact orthographic view (Front, Side, Top etc. using the numpad) rectifies the issue and the view camera has correct leveling for the rest of the session.\n\nSwitch into Orthographic perspective mode and rotate the view to an approximate side view. The tilt is clearly visible in the default lamp's pole. Turning Anti-Aliasing off may make the tilt more apparent on the cube itself.\n\n**EXAMPLES:**\nTilt present in a fresh scene: [Image 1 ](Blender-Tilt01.jpg)\nTilt fixed by going into an exact orthographic view, and then exiting it to return to the approximate angle in Image 1: [Image 2 ](Blender-Tilt02.jpg)" ]

[ "Blender Crash. Code marked as unreachable has been executed.\nOperating system: Windows-11-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.67\n\nBroken: version: 3.6.1, 4.0.0 Alpha\nWorked: didn't test\n\nOpen the .blend and go to frame 60. Crash\n\nThis is a .blend from a random user. So, sadly, I don't know the exact steps to reproduce.\nIt just said: \"Code marked as unreachable has been executed. Please report this as a bug.\"\n\n", "Blender crashes when using bpy.ops.view3d.view_orbit with a custom context\nOperating system: Linux-5.15.11-arch2-1-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD RENOIR (DRM 3.42.0, 5.15.11-arch2-1, LLVM 13.0.0) AMD 4.6 (Core Profile) Mesa 21.3.2\n\nAlso tested on WIndows:\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14756 Core Profile Context 20.40.32 27.20.14032.8\n\nBroken (Linux): version: 3.0.0\nBroken (Windows): version: 3.0.0\nWorked: Never, the crash happens in 2.7 and 2.6 doesn't seem to support the override thing (I haven't tested subversions)\n\nBlender crashes when using `bpy.ops.view3d.view_orbit` with a custom context\n\nRun this in the Python console:\n```\narea = [n for n in bpy.context.screen.areas if n.type == \"VIEW_3D\"][0]\noverride = bpy.context.copy()\noverride['area'] = area\nbpy.ops.view3d.view_orbit(override, type='ORBITLEFT')\n```\n\n[blender.crash.txt](blender.crash.txt)", "Crash when rendering a specific 4k scene with Cycles Metal\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M2 Pro Apple 4.1 Metal - 83.1\n\nBroken: version: 3.5.1\n\nWhen I render with Blender 3.5.1 on a MacBook 16\" with an M2 Pro chip at a 4K quality, Blender closes before finishing the rendering process.\"\n\n- Open attached .blend file\n- Make sure you have enabled Metal GPU+CPU in the Preferences\n- Render the scene\n\nIt should crash about halfway through the rendering process.\n\n\n", "Crash Python API - GPUOffScreen.draw_view3d() crashes blender with draw_type = POST_VIEW but works with draw_type = POST_PIXEL\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.1\n\nWhen using [GPUOffScreen.draw_view3d() ]] in a [[ https:*docs.blender.org/api/current/bpy.types.Space.html?highlight=post_view#bpy.types.Space.draw_handler_add | draw_handler ]], blender crashes when running the [[ gpu.shader.html?highlight=gpu+shader+from_builtin#built-in-shaders | 3D_IMAGE builtin shader ](https:*docs.blender.org/api/current/gpu.types.html?highlight=draw_view3d#gpu.types.GPUOffScreen.draw_view3d) if the draw_type was set to POST_VIEW but works if the draw_type was set to POST_PIXEL.\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script Crash3D and blender will crash\n\n\n\n\n\n - Open CrashScriptDrawView3D.blend\n - Run the script NoCrash2D, and it will draw the camera view in the viewport without crashing\n\nAttachments:\n\n[CrashScriptDrawView3D.blend](CrashScriptDrawView3D.blend)\n[blender.crash.txt](blender.crash.txt)\n\n\n\n\n\n\n", "Crash on deleting driver\nOperating system: Linux neo 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux\nGraphics card: nvidia GTX 970\n\nBroken: (\n```\n3.0.0-alpha+master.a3027fb09416-linux.x86_64\n```\n)\nWorked: (?)\n\nI duplicated a Text strip via <shift><D>. I don't know where that driver on Location X came from. The original didn't have one. I then wanted to delete that driver. After deleting it and moving the current frame blender crashed.\n\n- Load attached file\n- Delete driver of 'Location X'\n- Press Cursor keys Left/Right a few times till crash.\n[crash.blend](crash.blend)", "Asset Browser don't show my asset's and crash Blender\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: 3.4, 3.5.0\nWorked: \n\n\nI created my asset browser and at first it worked well. But after it's worked strange. Then i opened asset browser i don't see my assets, but after refreshing Blender was crashed. I tried to re-specify the path to the library, but was changed nothing. I tryed to install new Blender (3.5) and it take change but don't fix it. I can't see assets in asset browser, but then a refresh it, Blender don't crash.\n\n\n- Download and extract the attached .zip file\n- In Preferences -> File Paths -> Asset Libraries, add the directory of the unzipped file\n- Go to Asset Browser an look for the assets in the added library - You cannot find then\n- Refresh - crash", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Background scene cause a crash in render animation\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: \n - 2.92.0 Alpha\n - 2.91.0\n - 2.90.1\nWorked: 2.83.9\n\nBackground scene makes blender unstable and cause a crash in render animation\n\n- Open default startup file.\n- Create a new scene named \"Scene.001\".\n- Assign default scene \"Scene\" as the background scene of \"Scene.001\" in scene properties.\n- Assign default camera as the camera of \"Scene.001\" in scene properties.\n- Hit render animation from render menu.\n- After a couple of frames rendered, blender crashes.\n\nTested in different situations i had some problems.\nI think assigning a background scene makes blender unstable in general.\nOccasionally crashes when opening a file which has background scene.\nThe worst case is render animation.\n\n[Background_Scene_Crash.mp4](Background_Scene_Crash.mp4)\n\nReproduction steps with this file:\n1. Open file.\n2. Start Render Animation.\n[#83852.blend](T83852.blend)\n", "Script node with shader output crashes Eevee\nOperating system: OSX Monterey (12.6)\nGraphics card: Radeon Pro Vega 20\n\nBroken: git versions: blender-v3.2-release, blender-v3.3-release, master\nWorked: 3.2 release\n\nI'm testing the MaterialX standard surface shader. It seems to work when in Release versions, but in a debug build, it crashes when you connect the output of the shader to 'surface' in the terminal node.\n\nUsing the default scene, switch from Eevee to Cycles + Open Shading Language. Select the Cube, switch to Shading tab. Create a new material, and add a new Script node. Load the attached .oso file (to compile the attached .osl, you need to have MaterialX installed. I'm using 1.38.5). Attach the output of the script node to the 'Surface' input of the terminal. Boom! Where the crash occurs depends on whether your in Eevee preview, or Cycles preview.\n\n[out.osl](out.osl)\n\n[out1.oso](out1.oso)", "Cycle gpu rendering crashes randomly\nOperating system: Win11\nGraphics card: Nvidia RTX 3070 Ti\n\nbroken: all 3.0 versions\n\nRenders keep crashing randomly when I’m using my gpu with cycles, I updated my drivers, my memory use is okay, I tried to not use denoiser, lower my samples, resolution etc but nothing works, sometimes it render 10 frames sometimes 100 but it can't render my whole animation without crashing (also for animations with low poly count and small textures tiles) \nDon't know how to read the crash log file.\n\n", "Sculpt mode - program crash: brush smooth + graphics tablet\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.30\n\nBroken: version: 3.6.0\n\nUnless explicitly specified in \"preferences > input > tablet > tablet API > wintab or windows ink\", it crashes when using smooth brush. If I use the \"automatically\" setting.\nFor the bug to recur, the brush must take a force or size parameter from the pressure force on the graphics tablet. If I use the mouse, the error does not occur.\nThis error is repeated in any scene and with any object. I created a cube, remesh it and used a smooth brush in sculpt mode. Blender crashes to completion.\n\ngraphics tablet: xp-pen star 06\n\n", "Crash when adding materials\nOperating system: Linux-5.18.9-200.fc36.x86_64-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 22.1.3\n\nBroken: version: 3.2.0\n\nBlender crashes when adding a second material (sometimes you need to add some more to crash it)\n\n1. Open the appended .blend file.\n2. Select the object.\n3. Go to material tab.\n4. Try to add a second material.\n\n[crash.blend](crash.blend)", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "Blender 3.5.0 Win11 RTX3090 Fatal Crash on activating Cycles\n@deadpin thanks for replying.\n\nDriver Version: 31.0.15.3161 (NVIDA 528.24) DCH Win1164 installed\n\nCycles now working without issue thank u.\n\n_Originally posted by @Jaymi-McManus in /blender/blender/issues/106953#issuecomment-923094_\n\n>>>>>\n\nUpdate: \n\n1. Closed the ticket too soon, after adding some simple color, specular, metallic, changes in BSDF and then navigating between layout and other tabs, fatal crash occurs again\n\n2. Updated NVIDIA drivers to 31.0.15.3161 (NVIDIA 531.61) DHC / Win11 64 the issue still persists\n\nUpdate logs attached.", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at [email protected]\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file" ]

[ "Close Area crashes Blender (3.0.0 and 3.0.1)\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n\nHello,\nusing the new \"Close Area\" command causes blender to crash. At first I thought it was closing blender but it doesn't prompt for an unsaved file to be saved either.\n\n[Area Close Crash.mp4](Area_Close_Crash.mp4)\nOpen Blender 3.0.0. Split the viewport horizontally, and try using the Close Area command on the bottom half from the menu: View -> Area -> Close Area.\nBlender will crash.\n\nYou can also view the attached video for a screen recording of the issue.\n" ]

[ "Realtime Compositor - Crash on Mac when using Map UV node\nOperating system: macOS Ventura 13.3.1\nGraphics card: AMD Radeon Pro 5700 XT 16GB\n\nBroken: 3.6 alpha cef128e68af5 (2023-04-13 16:06)\n\nConnecting a Map UV node in Compositing will crash on macOS\n\nIn Blender's startup scene, enable Compositing by checking \"Use Nodes\".\nConnect a Map UV node between the Render Layers node and the Composite node.\nIn a 3D view, turn on Rendered viewport and set Viewport Compositing to Always.\nThis will crash (100% reproducible).\n\nPlease contact summary if more information is required.\n\n", "3D cursor doesn't precisely follow mouse pointer when Transform Pivot Point is Active Element\nOperating system: Fedora Linux (Wayland)\nGraphics card: AMD\n\nBroken: at least from 2.93 to 4.0 all broken\nWorked: never?\n\nWhen moving the 3D cursor, it's moved distance is multiplied by some value depending on the view orientation. \n\n\n- Move the default cube and rotate the viewport orientation\n- Select Active Element as the Transform Pivot Point\n- Move the 3D-Cursor with shift+RMB\n\n", "Gpencil: dopesheet selection issues [clicking in summary deselects corresponding ID channel, e.g. breaking \"Jump to keyframe\"]\nBroken: version: 2.92.0 Alpha\nWorked: n/a, tested with 2.91 and didn't work\n\nJump to keyframe command & shortcut doesn't work anymore when you duplicate a keyframe.\nDoesn't matter what amount of layers there are.\n\n1) Draw a keyframe\n2) Draw a nother keyframe at another time = works\n\nDuplicate 1) keyframe = doesn't work, please see the video\n\n\n[gp_duplicate_keyframe_jump.mp4](gp_duplicate_keyframe_jump.mp4)\n\nReason why this happens: clicking in the summary will deselect the corresponding greasepencil ID channel [on which the \"Jump to keyframe\" operator relies]\nClicking in the summary should not deselect every channel there is, but keep the channel representing the selected greasepencil object selected as well [same as for other object types such as meshes].\nThis goes hand in hand with selecting a grease pencil object in the 3DView or Outliner not selecting the corresponding ID channel [this should also be the case (same as for other object types such as meshes)]", "Shape keys for surface not working - no active option\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.17\n\nBroken: version: 3.5.0\nBroken: version: 3.6.0\nWorked: don't know any version where this working, but last time no option for use this doing hard work\n\nShape keys for surface not working - no active option. \n\nThis not working like expected as typical object have verts. See screen.\n\n", "Panning with spacebar in clip editor stops after some movement\nOperating system: Windows-10-10.0.22581-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 8 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.10.00.22 30.0.21000.22018\n\nBroken: version: 3.1.0\n\nWhen I set the spacebar to pan (disabling the play animation, tools, or search options for the same keymap), in all windows the shortcut works properly - when I press spacebar and move the mouse, the screen pans, but the clip editor window. It works for a second and then it stops working. It only works if right after pressing spacebar, I press ctrl, shift or alt, or any other key in fact. I think it causes a reset and it forgets to cancel the shortcut. Also, if I put the shortcut to be release sensitive (not press), it also works, but there's no point in making that, cause I'd have to press spacebar again in another window to apply the pan.\n\n- In default scene, switch to clip editor\n- From preferences tab, Set the spacebar as shortcut for panning in clip editor\n- Pan around by Holding `spacebar` key (stops after some movement)\n\n", "When loading factory defaults, Render Dimensions preset dropdown menu is not reset\nOSX\n\n2.73a\n\nWhen loading factory defaults, Render Dimensions preset dropdown menu is not reset\n\n\n- Change Scene Dimensions to a preset\n- Maybe change a couple of settings like x resolution to see changes later on\n- Reset to factory default\n- Observe change of X, Y Scale etc of Scene Dimensions Resolution to default\n- Observe Preset dropdown choice still on previous setting before factory default..\n\n\nJust a little teenie weenie thingie.. I know, but thanks for looking into it!\nCheers and thanks again for developing worlds' greatest application!\n\nRoel\n", "Outliner: Alt+disable is work for all selected, but Alt+Enable is not\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n{key Alt LMB} generally enables a feature that repeats the operation on all selected items in the outliner.\nBut that seems to work only if the object is selected in 3d View.\n[2020-01-12_20-44-23.mp4](2020-01-12_20-44-23.mp4)\n\nOpen:\n[untitled4.blend](untitled4.blend)\n- select the three objects (either in 3d view or outliner).\n- {key Alt LMB} click on the icon that disables object in viewports.\n- {key Alt LMB} again to try to enable them all.\nOnly one object is enabled, because the others are not selected in 3dview.\n\n", "Space Mouse not working properly\nOperating system: Mac OS Ventura 13.3.1 (a)\nGraphics card: Apple M1 Max\n\nBroken: 3.5.0\nWorked: 3.0.0\n\nNo buttons of the Spacemouse work anymore.\nEverything worked with Blender 3.0.0 and 3D Connexion Driver 10.7.0.\n\n1. Install latest 3D Connexion Driver 10.8.0.\n2. Set up some buttons in 3DxWare 10 like:\n a. \"Button 1\" = Keystroke \"Tab\".\n b. \"Button 2\" = Keystroke \"1\".\n c. \"Button 3\" = Keystroke \"2\".\n3. Start Blender.\n4. Try to switch between Edit and Object mode with \"Button 1\":\n a. No Function.\n5. Try to switch between select Modes with \"Buttons 2-3\":\n a. No Function.\n6. Try to select more Objects with holding \"shift\" on Space Mouse:\n a. No Function.\n\nI miss the combination so hard, it's impossible to work without my space mouse, I'm used to it for a decade. :(\nThe Space Mouse works fine in all other Programms, its an Blender Issue exclusively.\n\nAdditional Infos:\nSometimes restarting Blender multiple Times, re-installing it, fixes temporary the function of the basic Keys \"shift, cmd, etc\". The other buttons never work. They worked always in the past and still work in all other programs where I use the mouse. ", "Blender 4 Alpha Won't Open\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: I tried opening Blender 4.0.0 - Alpha\n August 30, 13:25:10\n e071288ab290\n tar.xz\n 250.91MB\n\nWorked: Blender 4 Alpha from July 15 opens, though.\nBlender 4.0.0 - Alpha\n July 15, 02:35:02\n d8e4fe320784\n tar.xz\n 249.01MB\n\n\n\n- I tried opening Blender 4 Alpha, latest version, and nothing happens.\n- I also tried an earlier version from August 15, and another from July 15.\n- August 15 wouldn't open. I made sure it was set to \"run as executable\".\n- July 15 opens, though.\n- I might check other versions. They take a while to download, though (I live in Canada).\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n - Not sure how others can reproduce this unless they have my pc, or are having the same problem.\n - If there's some kind of terminal window thingy that writes down info while trying to open Blender, let me know how to do that, and I'll copy and paste whatever it says.\n- Note: sometimes Blender 3.6 doesn't open at first. But if I try again, it opens just fine.\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "Pin Scene to Workspace doesn't work (when multiple blender windows are open)\nOperating system: Linux-5.15.0-53-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.4.0 Alpha\nBroken: version: 3.3.0\n\n\nPin Scene to Workspace doesn't work\n\nOpen file, observe that scene.002 is active and pined.\n\n[switch scenes.blend](switch_scenes.blend)\n\nSwitch to Modeling tab then back to Layout.\n\nObserve that instead of scene.002, scene.001 is active. \n\nNOTE: this is only failing with multiple blender windows open (if the second window is closed, it works as expected)", "NDOF buttons no longer programmable with Blender commands\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: 2.93.4\nWorked: 2.92\n\nNDOF (3D Connexion Space Navigator) has two programable buttons which are programmed in the 3D Connexion software. The button settings have a dropdown where one can select a 'Blender' drop down which lists a number of possible Blender functions for that button. Now, none of them work. It appears that only the 'Blender' dropdown is not functioning. Other dropdowns still work, so I know the Space Navigator is operating well. I particularly use the 'Fit' option in the 'Blender' dropdown, but I tested others and none of the Blender functions work now.\n\nThey did in previous versions (2.92) Beginning in 2.93, there were other problems with the Space Navigator that I did not report, but they were fixed in 2.93.4. Now this new problem of being unable to program either of the two side buttons with any of the 'Blender' functions has appeared.\n\nI contacted 3D Connexion Tech Support but they could find no solution. The problem appeared with the older device driver, but installing the newest driver did not solve the problem.\n\nError can be reproduced with Space Navigator and Blender 2.93.4\n\nThanks for Blender and all the time you spend perfecting it. ", "Viewport Render crashes on macOS 12.3\nOperating system: macOS-12.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Beta\n\n\nUpdated MacOS to 12.3 (Beta) and going to Viewport Render will cause a full Mac freeze then crash. A hard reboot is the only resolution.\n\nNot sure if this is caused from the latest version of MacOS (12.3 Beta) or if it's the latest version of Blender (3.1Beta). \nI haven't tried with the latest Blender 3.1 Beta build with Monterey 12.2 Beta as this would require me to wipe the computer and reload all apps and files in the OS downgrade process.\n\nOpen default scene and toggle the Viewport Render button.\n\n", "Problem with mouse walk navigation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.90\n\nBroken: version: 2.91.2\n\nWalk navigation breaks when key map is changed for Up and Down operation.\n\n- Load blender with factory settings\n- Open keymap from `Edit -> Preferences`\n- `3D View -> View 3D Walk Modal`\n- Change key value for Up and Down\n- In viewport `View -> Navigation -> Walk Navigation`\n- Use updated keys to move Up and down\n\n\n\nAs far as i could see, the problem happens when instead of the q down and e keys we put the midle mouse roll up or down. As you can see in the picture. I have tried with other keys and each time there is a problem with the middle mouse button. Simply the middle mouse button goes up, but when it turns so rool down it doesn't work?\nDoes it fix it or do you have an idea how to fix it?\n", "Remove/Update \"Emulate Middle Mouse\" preference\nThis task is to check if it is reasonable to remove the emulate middle mouse option.\n\nBlender 2.7x didn't allow left-click-select and emulate middle mouse to be enabled at once, this never worked - it's just that in 2.8x we allow both options to be enabled at once with key-conflicts.\n\nSince I don't use a touch-pad on macOS / ms-windows, I'm not sure how common it is that middle-click gestures are enabled without having to manually configure it.\n\nAre there systems where using a middle-click still isn't practical?\n\nOptions could be:\n\n- Remove this preference.\n- Remove the keys that use Alt-LMB *(means re-working the keymap in some places)*.\n- Use an alternative shortcut that doesn't conflict, eg: OSKey (Cmd / Super / Windows-Key).\n\n *(By default this conflicts on Linux with many window-managers, these would need to be re-configured not to use Super-LMB).*\n\nUnless this is given some attention it's likely Alt-LMB will be used more, to the point Emulate-Middle-Mouse preference isn't useful and we'll need to remove or document all it's known limitations and accept Blender isn't fully usable with this enabled. \n\n----\n\nThere are currently conflicts using with emulate middle mouse\n\n- Number Button Alt-Drag to change all other selected items #69053 (Emulate 3 Buttons doesn't work with ALT Modifier key on UI buttons)\n- Edit-Mesh: Edge-ring de-select isn't possible.\n- Alt-MMB-drag to change views.\n- Un-clamped vertex slide can't be confirmed.\n- Grease Pencil, Circle Primitive\n- Weight Paint Gradient\n- Loop select *(Worked around with double-click, but not very convenient since selecting boundaries requires quad-click).*\n\nHere is a full list of potential conflicts in the default keymap.\n\nAre we serious about resolving these or would it be better to drop this option? \n\n----\n\nFrom a search of the code:\n\n```\ncat release/scripts/presets/keyconfig/keymap_data/blender_default.py | \\\n pcregrep \"(LEFTMOUSE|TWEAK_L|params.select_mouse|params.action_tweak|params.action_mouse).*alt\\\":\"\n```\n\n```\n (\"uv.select_loop\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"alt\": True},\n (\"uv.select_loop\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"shift\": True, \"alt\": True},\n (\"uv.select_edge_ring\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"ctrl\": True, \"alt\": True},\n (\"uv.select_edge_ring\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"ctrl\": True, \"shift\": True, \"alt\": True},\n (\"uv.select_loop\", {\"type\": params.select_mouse, \"value\": 'DOUBLE_CLICK', \"alt\": True},\n (\"mask.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True},\n (\"mask.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"graph.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"alt\": True},\n (\"graph.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"shift\": True, \"alt\": True},\n (\"graph.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"ctrl\": True, \"alt\": True},\n (\"graph.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"node.select_lasso\", {\"type\": 'EVT_TWEAK_L', \"value\": 'ANY', \"ctrl\": True, \"alt\": True},\n (\"node.select_lasso\", {\"type\": 'EVT_TWEAK_L', \"value\": 'ANY', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"node.backimage_sample\", {\"type\": params.action_mouse, \"value\": 'PRESS', \"alt\": True}, None),\n (\"node.move_detach_links_release\", {\"type\": params.action_tweak, \"value\": 'ANY', \"alt\": True}, None),\n (\"action.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"alt\": True},\n (\"action.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"shift\": True, \"alt\": True},\n (\"action.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"ctrl\": True, \"alt\": True},\n (\"action.clickselect\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"sequencer.select\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"alt\": True},\n (\"sequencer.select\", {\"type\": params.select_mouse, \"value\": 'PRESS', \"shift\": True, \"alt\": True},\n (\"clip.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True},\n (\"clip.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"gpencil.annotate\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True, \"key_modifier\": 'D'},\n (\"gpencil.annotate\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"shift\": True, \"alt\": True, \"key_modifier\": 'D'},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"gpencil.select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"alt\": True},\n (\"gpencil.select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"shift\": True, \"alt\": True},\n (\"gpencil.draw\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.draw\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"paint.weight_gradient\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"paint.weight_gradient\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"ctrl\": True, \"alt\": True},\n (\"mesh.loop_select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"alt\": True},\n (\"mesh.loop_select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"shift\": True, \"alt\": True},\n (\"mesh.edgering_select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"ctrl\": True, \"alt\": True},\n (\"mesh.edgering_select\", {\"type\": params.select_mouse, \"value\": params.select_mouse_value, \"shift\": True, \"ctrl\": True, \"alt\": True},\n (\"mesh.loop_select\", {\"type\": params.select_mouse, \"value\": 'DOUBLE_CLICK', \"alt\": True},\n (\"gpencil.primitive_line\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.primitive_box\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.primitive_circle\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.primitive_curve\", {\"type\": 'LEFTMOUSE', \"value\": 'PRESS', \"alt\": True},\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n (\"gpencil.select_lasso\", {\"type\": params.action_tweak, \"value\": 'ANY', \"ctrl\": True, \"alt\": True}, None),\n```\n\n" ]

[ "3D Connexion Space Mouse Pro - Blender 2.82a on macOS\nmacOS Catalina 10.15.4 (19E287)\n3D Connexion 3dWare10 10.6.5\n\nBlender 2.82a\n\n\nThe mouse appears to almost match the 3D Connexion training app in terms of movement when in object/edit mode but it would appear that none of the buttons & especially the MENU do not work. \n\nI have installed the 3D Connexion drivers a second and third time with firewall and anti-virus off and the problem with these mice seem to persist. \n\n>> This has been edited by another but im wondering if there is some resource file missing where keys are mapped, either this is a 3D Connexion plug in or something to do with Blender?\n\n\nI've seen these tasks; It's still a problem for me. \n#67686 (NDOF mouse not working in code signed macOS builds)\n#67971 (3D Connexion Space Mouse Enterprise Custom Buttons 1-10 Not working in Blender 2.8 (macOS))" ]

[ "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "Crash when updating image pixel data through python API\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.83.0, 2.90\nWorked: N/A\n\nBlender crashes with apparent memory corruption, when image pixel data and previous are updated frequently with python script.\nStack traces give no obvious answer, i have seen it happen in depsgraph eval, node graph code, imbuf, etc.\n\n*Note: i could not reproduce this issue in debug mode so far, only release or RelWithDebInfo seems to work.*\n\n 1. Open attacehd file\n - Run the script\n - Make sure the scene properties are visible (it seems to only crash when displaying image previews).\n - Grab the default cube and wiggle it around to force depsgraph updates.\n - If it doesn't want to crash, re-open Blender, it seems to be quite random.\n\nI'm using a node group to access image data blocks, so they can be displayed in a panel as pointers. The code generates data to replace the image pixels as well as the preview.\nI have also tried running a timer and deferring pixel updates using a queue as suggested [here ](bpy.app.timers.html#use-a-timer-to-react-to-events-in-another-thread), just in case the depsgraph post update is somehow not safe, but this doesn't change anything substantially. The bug happens in both cases.\n\n[crashtest.blend](crashtest.blend)", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n", "My Blender won't open anymore\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3060\n\nBroken: Every version\n\nWhen I try to open Blender the terminal appears then disappears and nothing else happens.\nBlender worked until today in all its versions, but now it no longer opens.\n\nI tried opening it as administrator, on different versions. I restarted my PC. I updated my drivers. There no bug/crash report or anything.\n\nI don't know what to do.\n\n", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "Regression: Crash on Start Up\nOperating system: Mac OS 12.6.9\nGraphics card: AMD FirePro D500 3 GB\n\nBroken: blender-3.6.3-stable+v36.d3e6b08276ba-darwin.x86_64-release.dmg\nWorked: blender-3.6.3-candidate+v36.71b55b491e9c-darwin.x86_64-release.dmg\n\nApp crashes at start up.\n\nClick on App icon, app attempt to start, crash. I restarted my computer with same results. Not opening app from a .blend file. Tried opening default app with same result.\n\n", " Startup File: Header Collapse Menu not restored after restarting blender\nOperating system: windows 10 64bit\nGraphics card: Nvidia gtx m860\n\nBroken:\nversion: 2.80 (sub 37), branch: blender2.8, commit date: 2018-12-16 00:27, hash: 4488056f3d9, type: Release\n\nWorked: (optional)\n2.79b\n\nwhen using Collapse Menu on the header and restarting blender the setting is ignored and the header menu is expanded again.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. open blender 2.8\n2. collapse the header menu\n \n3. save startup file so we save the header configuration\n\n4. restart blender\n5.the Header menu is expanded again after a restart, other headers like the editor menu stay collapsed after a restart.\n\n", "Debug information not generated upon crash.\nOperating system: Arch Linux 6.4.12-arch1-1\nGraphics card: AMD ATI Radeon 680M\n\nBroken: 3.6.2\nWorked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade)\n\nBlender crashes immediately upon launch.\n\nLaunching from the command line, I get this:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\nThe contents of /tmp/blender.crash.txt are this:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nPassing the --debug-all flag, I get no errors. I attached the output of this command as a text file.\n\nWhile Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here.\n\nLaunch blender.\n\n", "Crash opening file using Clump Curves on Particle Children \n****\n\nversion: 2.81 (sub 16), branch: master, commit date: 2019-12-04 11:32, hash: f1aa4d18d49d, type: Release\nbuild date: 2019-12-04, 14:30:40\nplatform: Windows\n\n***********************************************************\n\nWhen I worked on a project using particles, after a short break I wasn´t able to reopen the project. The project crashed right after opening. When starting Blender from console the only error I could find was:\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF706DC271E\n\nno Blender log file was written!\n\nEven in debug mode there were no more hints but his one. I opened the project in an Ubuntu VM and it also crashed there. No chance to recover the file.\n\n\nUsing Particle following a nurbspath with Force Field \"Curve\".\nParticles rendered as objects.\nUsed Simple Children.\nWhen ticking the box: Use Clump Curve it crashes.\n\nEither Blender crashes right after ticking the box or when reopen the project. The latter then means that I´m not able to recover my work at all.\nI might have to do with particles already baked or not. Not sure. \n\n[T72763_crash_log.txt](T72763_crash_log.txt)\n\nfile written from c2a37867f2 that crashes on file read:\n[#72763.blend](T72763.blend)\nfile written from 2.79b that crashes on file read:\n[T72763_279.blend](T72763_279.blend)", "Blender segfault if Bake Line Art\nOperating system: Debian Linux Stable 11\nGraphics card: Intel internal UHD Graphics 630 (driver: i915)\n\nBroken: 3.2.2 - 3.6.1 official releases\n\nBlender segfault if Bake Line Art.\n\nConsole:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault\n```\n\nFile /tmp/blender.crash.txt:\n```\n# Blender 3.2.2, Commit date: 2022-08-02 18:15, Hash bcfdb14560e7\nbpy.ops.object.delete(use_global=False, confirm=False) # Operator\nDeleted 1 object(s) # Info\nbpy.ops.object.gpencil_add(align='WORLD', location=(0, 0, 0), scale=(1, 1, 1), type='MONKEY') # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.gpencil_modifier_add(type='GP_LINEART') # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xc1619d0]\n./blender() [0x11da18d]\n/lib/x86_64-linux-gnu/libc.so.6(+0x38d60) [0x7f97f7664d60]\n./blender(MEM_lockfree_allocN_len+0x7) [0xc16e1e7]\n./blender(MEM_lockfree_dupallocN+0x14) [0xc16e624]\n./blender(BKE_gpencil_stroke_duplicate+0x1a) [0x11f926a]\n./blender(BKE_gpencil_frame_copy_strokes+0x42) [0x11f94c2]\n./blender() [0x1207d97]\n./blender(BKE_gpencil_prepare_eval_data+0x1b7) [0x1208b07]\n./blender(BKE_object_handle_data_update+0x2fe) [0x12af9ae]\n./blender(BKE_object_eval_uber_data+0x2f) [0x12afc7f]\n./blender() [0x1913f22]\n./blender() [0x19140f2]\n./blender() [0xc16574d]\n./blender() [0x1796a35]\n./blender() [0x1796ceb]\n./blender() [0x1783d27]\n./blender() [0x1790720]\n./blender() [0x179275c]\n./blender() [0x1792959]\n/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7) [0x7f97f807aea7]\n/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f97f7727a2f]\n\n# Python backtrace\n```\n\n1. Open Blender\n2. Click to default box and delete it (press del)\n3. Press Shift+A\n4. Select \"Grease Pencil\" - \"Monkey\"\n5. At right area select \"Modifier Properties\"\n6. Click \"Add Modifier\"\n7. Select \"Line Art\"\n8. At bottom of this area click \"Bake\" - \"Bake Line Art\"\n9. Segfault here\n\n", "Crash on startup with 2.82 and Intel HD + Windows\nOperating system: Windows 10 Pro (1909)\nGraphics card: Intel(R) HD Graphics 630, version 4.5.0 - Build 26.20.100.6951\n\nBroken: 2.81, 2.82, downloaded from blender.org\nWorked: 2.80 worked.\n\nBlender crashes on start:\n\n```\nC:\\Program Files\\Blender Foundation\\Blender 2.81>blender.exe\nGPUTexture: create : TEXTURE_1D, RGBA8, w : 1, h : 0, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 1, h : 1, d : 0, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nGPUTexture: create : TEXTURE_3D, RGBA8, w : 1, h : 1, d : 1, comp : 4, size : 0.00 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.00 MiB.\nfound bundled python: C:\\Program Files\\Blender Foundation\\Blender 2.81\\2.81\\python\nGPUTexture: create : TEXTURE_2D, RGBA8, w : 3435, h : 26, d : 0, comp : 4, size : 0.34 MiB\nGPUTexture: texture alloc failed. Likely not enough Video Memory.\nCurrent texture memory usage : 0.34 MiB.\nGPUTexture: create : TEXTURE_2D, R8, w : 16384, h : 128, d : 0, comp : 1, size : 2.00 MiB\n```\n\nThis appears to be similar to #69594.\n\n\n\n1. Download 2.81.\n2. Launch 'blender.exe'\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "(Linux; AMD Radeon GPU) Rendering a complex scene with eevee crashes desktop environment / causes rendering and viewport artifacts\n```\nOperating system: EndeavourOS Linux / Fedora Linux (Same issue on both distros)\nGPU: AMD Radeon RX 6800 XT (16 GB VRAM)\nCPU: AMD Ryzen 5 3600\n```\n\n```\nrenderer:\t'AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64)'\nvendor:\t\t'AMD'\nversion:\t'4.6 (Core Profile) Mesa 22.3.7'\ndevice type:\t'AMD'\nbackend type:\t'OPENGL'\n```\n\nBroken: 3.4.1, 55485cb379f7, blender-v3.4-release; 3.5.0 Release Candidate, d5d8246441a5, blender-v3.5-release (both version exhibit the issue)\n\nWhen rendering complex scenes in Eevee (Scenes with many different objects), one of the following occurs:\n\n 1. On **X11**: Computer freezes for about 5 seconds before all monitors cut to black. After about 5 seconds on a black screen, the login screen appears and I can log in as normal, as if I logged out. All of the applications have closed.\n 2. On **Wayland**: Render finishes rendering, but many of the objects appear broken; they are semi transparent or appear as if they were using the holdout shader. Returning to the viewport causes all objects with transparency to flicker randomly and appear distorted. Occasionally, the desktop of the computer itself will become broken and artifacted, only logging out or restarting fixes it. This usually isn't possible, however, as after a short while everything all displays cut to a black screen. Unlike X11, however, the only way to recover from this is to restart the PC by holding down the power button.\n\nThis issue **only occurs on linux and does not occur on my Windows 10 partition**, even with the exact same settings and scene. It also only occurs when actually trying to render the scene. In the viewport everything works just fine, even on rendered view where everything looks the same as it should in the render.\n\nThis issue seems to occur regardless of the GPU Usage; even when I limit the GPU clock and power draw significantly it still happens.\n\nThe attached .blend file is an example of a simple scene which triggers the bug. It seems to occur no matter what the render settings are set to.\n\n", "Blender 2.8 Splash Screen Design\nFor Blender 2.8, we want to make some improvements to the splash screen. \n\nOne of the main things we want to do here, is to provide an easy way to get started with various *types* of projects. You'll want a different setup if you are doing a 2D animation project, than if you are doing sculpting. That means, both some different objects in your scene, but also a different starting Workspace, and perhaps other things too.\n\nThe other thing we want to include, are links to tutorial videos about learning Blender, and also about new features for each release.\n\nLastly, Blender has many obscure features that even many seasones Blender users don't know about. We want to surface those by showing users various random tips.\n\n\n\n\n\nVisual Example:\n\n\n\n\n## First Launch Setup Screen\nThe splash screen could also help making the setup process smoother when first launching Blender. There are several options and settings that users will want to easily configure once, such as the keymap, the language and GPU rendering. We want to make these settings more discoverable and accessible.\n\nThis means we can remove these items from the normal splash screen, to make it cleaner and simpler.\n\nPressing the Done button would lead users into the regular splash screen.\n\n\nOutline:\n\n\nVisual example:\n\n\n\nWe could then lead new users to a screen with several links to start learning Blender:\n\n" ]

[ "Blender 2.8 crash on startup on Linux\nUbuntu 18.04.1\nGeForce GTX 460\nDriver: 340.107\n\nBroken: blender-2.80-a2922f98400-linux-glibc224-x86_64 (from\tOct 18 2018 00:01:19)\nWorked: (optional): the daily version a few days before (and all of the last couple of weeks) worked.\n\nBlender crashes immediately after startup (empty black windows visible for a few ms). Segmentation fault (core dumped)\n\nStart Blender after unpacking by double click or via CLI\n\n**Logs**\n*/tmp/blender.crash.txt*\n\n```\n# Blender 2.80 (sub 26), Commit date: 2018-10-17 18:46, Hash a2922f98400\nTool 'Cursor' not found. # Warning\nTool 'Cursor' not found. # Warning\nTool 'Cursor' not found. # Warning\n\n# backtrace\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(BLI_system_backtrace+0x1d) [0x1b64e2d]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender() [0x113aab9]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fb19e166f20]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(GPU_shader_get_uniform_block+0x4) [0x17223f4]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender() [0x173b7b3]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(DRW_shgroup_create+0x1c) [0x173cc4c]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender() [0x174e382]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender() [0x173809f]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(DRW_draw_render_loop_ex+0x17e) [0x173985e]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(view3d_main_region_draw+0x77) [0x121b367]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(ED_region_do_draw+0x811) [0x143bbe1]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(wm_draw_update+0x421) [0x113d1d1]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(WM_main+0x30) [0x113b470]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(main+0x327) [0x10a1857]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fb19e149b97]\n/home/togro/Desktop/blender-2.80-a2922f98400-linux-glibc224-x86_64/blender(_start+0x2a) [0x113764a]\n```\n\nOutput on STDOUT and STDERR attached as carsh.out\n[crash.out](crash.out)\n\nAll the best,\nThomas", "Blender 2.8 crashes on start up\nWindows 8.1 Professional 64 bit\nNvidia Quadro FX 3800 Graphics card.Driver version 342\nOperating system and graphics card\n\nBroken: (2.80.0-git.a30c9f710a6-windows64)\nWorked: (2.79)\n\nUpon attempting to open Blender comand box shows but too quick to read anything.Then grey window opens for a couple of seconds,followed by Blender crashing\ndownload zip file.Unzip to desk top with winzip. Attempt to open Blender with Application file.\n", "Blender 2.80 crashes on start\nWindows 7 and Quadro K2100M\n\nBroken: 2.8-7756973b0c3\nWorked: (2.8-bb0b4b008ed)\n\nWhen I start blender the application paints the borders and the title bar then the application disappears.\nThis happens every time I attempt to open the application.\n\nI have reverted to 2.8-bb0b4b008ed which starts normally.\nI've attached the output from starting blender from the command prompt.\n\n[Win7-Crash.txt](Win7-Crash.txt)\n" ]

[ "Dead particles are unexpectedly rendered\n## Simplified Report\n\n- The following file contains a simple particle system and a collider that kills some of the particles.\n- Bake the particle system simulation.\n- Go to the end frame and render.\n- Notice that killed particles still appear in the render.\n\n[killedParticles.blend](killedParticles.blend)\n\n## Original Report\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 3.3.1\n\n\nI use particle system and mesh that kills particle. In preview dead partcles aren't rendered \nWhen I press f12 I see this . Cycles and eevee doesnt consider these as dead. It's very old bug, also information about death isn;'t saved in cache\n[report.blend](report.blend)\n", "Particle Edit mode for non hair particles - Not working\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\nWorked: can not find one\n\n\nCan not edit a baked particle simulation's particle paths in Particle Edit mode\n\n\n- Delete all object from the original scene\n- Create a plane\n- Add a particle system. For the sake of testing with 20 particles,\n- Bake the simulation (not in disk)\n- Switch to Particle Edit mode\n- Select Point select mode\n\n- > There is no particle path in the view-port to be edited.[path not showing in particule edit .blend](path_not_showing_in_particule_edit_.blend)\n", "Interface. Sculpt mode, checkbox title not react to click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: since 2.83.9, checked with version: 2.93.0\n3.0 alpha broken too\n{[F10178598](изображение.png) size=full} — here\n\n\n[2021-06-18_00-08-00.mp4](2021-06-18_00-08-00.mp4)\n", "Crash on applying boolean modifier\nOperating system: Linux Fedora V35\nGraphics card: Nvidia 3070TI\n\nBlender 3.1.2 and Blender 3.2.0 both crash\n\nI created a mesh object, then used boolean modifier to create a hollow center. I applied the modifier. When I go into edit to clean it up, it crashes.\n\napply the boolean modifier to the mesh \"Bottom\" with object \"Plug\" in the included blend file using all defaults. Enter edit mode and see the mesh is badly corrupted.\n\n[part7.blend](part7.blend)\n[printReady1.blend](printReady1.blend)", "Sculpt Mode Painting\nThis task outlines the remaining To Do's for fundamental sculpt mode painting.\n\n### Color Swapping\n\n- `X` for switching primary and secondary color\n- The current shortcut for `X` for the draw brush will be removed.\n\nIn one of the upcoming releases all brush shortcuts in sculpt mode will be removed anyway, for maximum user customization.\n\n### Canvas Picker & Viewport Color\n\nSince painting is something optional in sculpt mode we need to make sure that:\n- Color Attribute shading isn't enforced\n- Color attributes will be displayed when using painting tools\n- A fast way of choosing color attributes in the UI\n- An optional & discoverable way of switching the viewport shading for all objects (optimal painting scenario)\n\nThe proposal for this is:\n- Use [D16241](D16241) canvas picker UI in sculpt mode. Always visible but grayed out if viewport shading color is not `Attribute`\n- Whenever a painting tool is active, the canvas picker is no longer grayed out and the color attribute viewport shading is enforced in workbench shading on the active object only\n- In the canvas picker popover, add a message or button to switch the viewport color to Attribute if this is not yet the case, so that colors stay visible between brushes/tools. \n- Remove the current behavior of automatically switching the viewport color when a painting tool is used\n\nTo make sure the sculpting experience is already taking color attributes into account, the default sculpting template and workspace should use color attributes for viewport shading.", "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "Multires disp bake doesn't smooth UV\nOperating system: Windows 10\nGraphics card: RTX 3060ti\n\nBroken: 2.92, 02948a2cab44\nWorked: Don't know\n\nWhen baking a multires sculpt it will bake the disp towards a subdivided mesh but not a smoothed UV.\n\nGuess the best way is just to download my attached .blend, make sure the image texture is selected, that the Level Viewport on the multires modifier is at 0 and use the bake under Render properties. The resulting texture should not have this clear square in the middle as in my example picture below, but it do because the UV ain't getting smoothed. I did make sure that I had UV smooth enabled when I first subdivided the mesh.\nAlso added an example from what happens when I do this on a real project. This is baked and then applied to a subdivded mesh, look at the wrinkles below the eye.\n[multires_bug.blend](multires_bug.blend)\n\n", "The viewport may update at 0 FPS while navigating, until the mouse is released.\nOperating system: Windows 10\nGraphics card: RTX 3080 Ti\n\nBroken: 3.0.0\nWorked: 2.92.0\n\nWhen working in sculpt mode on a model with multires modifier, the viewport may update at 0 FPS while navigating, until the mouse is released.\n\nUsually when navigating in sculpt mode on a model with multires modifier, the model will switch to a low poly version while navigating. When this bug is happening, the viewport remains frozen and the high poly model remain on screen until mouse is released.\n\nThe bug will be temporarily fixed upon clicking on another application or resizing the blender window.\n\n1. Shift+A to create a plane\n2. Ctrl+E and subdivide it 4 times.\n3. Attach multires modifier onto the plane.\n4. Subdivide it 6 times with the multires modifier.\n5. Use sculpt mode and sculpt without moving the view for around 1~2 minutes (I used a wacom tablet. Using the sculptDraw brush, I added / subtracted (hold ctrl) from the mesh, also using smoothing brush (hold shift) to smooth certain parts, and undo (ctrl + z) multiple times to simulate a normal working environment.)\n6. Try to pan or rotate the view around.\n\n\n\n**I found another way to trigger this bug, and it's not strictly related to sculpt mode.**\n(Tested on blender 3.1.0 beta 03b57d3973)\n\n1. Click around with a Wacom tablet.\n2. Pan the camera around with a Wacom tablet.\n3. Pan the camera around with a mouse.\n\n\n[sculpt mode bug.blend](sculpt_mode_bug.blend)\n\n[2022-01-17 04-48-11_Trim.mp4](2022-01-17_04-48-11_Trim.mp4)", "Crash entering editmode on an object with particles and ridgidbody parented to another rigidbody\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nThe hair particles are facing the opposite direction and blender crashes, trying to solve this.\n\n\n[Donut2-1.blend](Donut2-1.blend)\n\n[Donut2-1.blend1](Donut2-1.blend1)\n\nCreated a donut according to site watch?v=jNmnPXY9UQA\n\nSteps:\nParticle Properties\n+\nHair (Not showing ?!?)\nFirst frame -> Hair showing downwards!\nTab\nBlender crashes repeatable.\nSteps:\nParticle Properties\n+\nHair (Not showing ?!?)\nFirst frame -> Hair showing downwards!\nTab\nBlender crashes repeatable.\n\n", "Multi-object mode support (parent task)\nThis is a parent task to manage to todo's for multi object editing.\n\nThere are many small todo's.\n\n### Reference Patches:\n\nFor anyone interested in helping out, here are some example commits which can be used as a reference.\n\n- Edit Mesh Face Poke - 3a9669bfff *Committed without indentation, so you can see lines changed more easily.*\n- Edit Mesh Flip Normals - 4704f2687a\n- Pose Mode: Flip Quaternions - 7560aabf71\n\n\nOther commits may be useful too.\n\n### Object Loops\n\nThere is some duplicate code for looping over objects.\n\nWe'll keep the option of having a way of simplifying the looping open.\n\n----\n\nNote: to collect operator ID's.\n\n- this script helps copy them from menus: [P656](P656.txt)\n- this is a more efficient version that watches the x11 clipboard so you can hover over items and press Ctrl-C: [P657](P657.txt)", "Sculpt mode. Switching back to tool with brushes from tool without brushes rolls to next brush.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken 2.83.*, 2.91,\nBroken: version: 2.92.0 Alpha\n\nSculpt mode\nCreate 2 grab brushes 1 and 2, that can be switched with G\nSelect Grab 1\nSwitch to mesh filter.\nPress G.\nNow you switched to Grab2 instead Grab1, that was selected before.\nExpected: return to same brush, that was selected before.\n\nIssue appears with:\nLine project, [Box] mask, Box hide, [Box] faceset, [Box] trim, Mesh/Cloth/Color filters, Mask by color, Edit faceset, all transform tools, annotation.\nAffects all tools, who can have few brushes.\nTested with factory startup too.\n\n[2020-12-10_03-13-39.mp4](2020-12-10_03-13-39.mp4)\n[grabroll.blend](grabroll.blend)", "UV: (investigate) Render UVs of selected object in UV Editor while in Object Mode\nCurrently, the UV Editor only works while in \"Edit\" mode.\n\nHow firm is that restriction?\n\nIt would be nice if we could view UVs in the UV editor, even in \"Object\" mode.\n\nIf would be even nicer if we could use the basic edit tools, such as move, scale and rotate on those UVS, again, even in Object mode.\n\nUVs can be generated and adjusted procedurally, but there's no good way to see them. It would be nice to allow displaying (not editing) evaluated UVs. Combined with features like visualizing overlapping faces, this could save a lot of time.\n\nThis is an *investigate* task, to see if such a thing is even possible. If we discover it's possible, we'll then need to decide if it's desirable.\n\nThanks @BlenderBob for the inspiration!\n\n", "Multires: Duplicating objects sets the viewport level to sculpt level\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.1.0 Alpha\n\nWhen sculpting on an object with a multiresolution modifier there are 3 sliders to define the level of subdivision.\nWhen duplicating the object right now, it will set the viewport level to the same value as the sculpt level.\n\n- Add a multires modifier\n- Subdidive the object\n- Set the viewport level to soemthing other than the viewport value\n- Duplicate the object\n\n", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "Sculpt Mode Multires Design\nThe purpose of this task is to describe the main uses cases and functionality that should be provided by a Multires sculpting system, as well as to discuss a plan on how to implement that in Blender.\n\n\n## The main use case of Multires\n\n### The problem Multires solves\n\nWhen you are working on any art medium (this also applies for painting), you should always try to work from the general shapes to the details. In case of digital sculpting, this means that you should always try to work with the minimum number of vertices that represent the level of detail you are trying to add to the model.\nThis is also true for the current workflow we have implemented (The Voxel remesher). By default, it provides a low poly mesh (about 10K vertices), that you should deform trying to get main shape of the object you want. After that, you increase the resolution of the remesher until you have enough vertices to represent the next level of detail you want to work on, and you continue from there.\nThe reasons you want to work this way are:\n\n- Performance: It is faster (more responsive, without lag) to deform a mesh with 10K vertices than a mesh with 25M vertices. If you use a big brush size needed to modify the object proportions on 25M vertices at the same time, it is going to lag. (Unrelated note, but we should not try to optimize Sculpt Mode to support these kind of operations as they don’t make any sense with a Multires system in place).\n\n- (Most important) Noise: If you sculpt with more vertices than needed for the size of details and shapes you are trying to get, you are going to end with a lot of uncontrolled shape noise produced by the tools. This is not a specific problem with Blender brushes and tools, this happens in any software and in every sculpting system. If you use the Draw brush to add some volume on a big area directly onto a 25M vertices mesh, you are going to need need to clean manually all small uncontrolled imperfections that big stroke stroke produced if you want that to be the final surface. If you start sculpting from a sphere with 1M vertices, you are going to spend more time cleaning shape noise than sculpting or the sculpt is just going to look bad. This is why nobody works this way. You don’t generate unintended shape noise if there aren’t enough vertices to represent it.\n\n\nThat is the main problem Multires sculpting solves. With Multires, you are able to choose at any moment the level of detail that is appropriate for the change you want to make in you model, solving both the performance and the noise issues. This gives an artist a huge amount of freedom as you know you can always go back to tweak low frequency details (proportions, general volumes) after sculpting mid/high frequency details (wrinkles, skin alphas...) if you consider that they don’t look right, without loosing any work.\n\nWithout this, the rest of the sculpting workflows (the Voxel remesher, Dyntopo) are the same as sculpting with real clay or marble, you can only sculpt bigger first shapes, then mid details and them the small details. If it does not look right, there is not way to fix it, you need to delete what looks wrong and start again. This is why those workflows are often used for concepting general shapes, and you want two switch to Multires as soon as you can. Sculpting a complex model without using Multires, on any software, is extremely (and unnecessarily) hard and it requires an insane amount of skill from the artist to workaround the limitation. It is like sculpting without using undo. It is too risky to create a high poly sculpt with projected alphas without this feature.\n\nIn order to solve this problem, the main thing Multires needs to guarantee is that when you sculpt shapes on your model in the appropriate resolution level, all the other levels are updated accordingly to reflect the changes you did. This is what people often refer as ¨detail propagation¨.\n\n### Multires Design\n\nWhen designing a sculpting Multires system that provides the previously mentioned functionality, We need to take the following points into consideration:\n\n1. All Multires subdivision levels contain valid information (sculpted shapes, mask, colors...) that should never be lost or damaged. \n\n2. The user wants to modify any subdivision level, at any time, without restrictions (there should not be limits of how much the mesh should be deformed or “not allowed modifications”).\n\n3. The user wants to delete and rebuild higher/lower subdivision levels in he/she considers that the shape information that level contains is not longer relevant. \n\nFor example, if the user wants to do a high poly sculpt, he/she switches to the higher level subdivision possible that the computer allows to create the high frequency detail projecting alphas. When that is done, the user may want to switch to a lower level to tweak proportions, or to a mid level to tweak small volumes with a soft brush. All the work the user put into applying the alphas should be propagated with the lower subdivision level changes with the Multires functionality and the model should look fine.\n\nIf, for some reason (a bug or an design issue in the implementation that did not consider point 1), switching and modifying lower levels may introduce mesh artifacts in the higher ones (the ones that contains the alpha projections and high frequency details), it will destroy all the work done previously by the user in that levels. \n\nIn that case, the user is again limited to not going back to select the mesh resolution needed for the modifications he/she wants to make in the mesh. A Multires system like this is not solving the intended problem and there is no reason to use it. It provides the same functionality as any of the other sculpting workflows (Voxel, Dyntopo), but even more limited as the user can’t modify the base topology to adapt it to a new shape. It does not have any reason to exist.\n\nIf you project requires you to use a fixed predefined topology in your model (for animation, for example), subdividing the mesh manually and deforming it with a cage or a datatransfer provides the same functionality. You can also get a lower subdivision level by duplicating the model and using unsubdivide if you need it for texture baking or animation. This is not the main problem Multires should be trying to solve.\n\n \n**Any unwanted mesh artifact in the detail propagation, no matter how small it is, invalidates all Multires sculpting features and makes it not functional for its intended use case, as it leads to irreparable data corruption.**\n \n\n### Current Multires Modifier\n\nConsidering the previously design and use case description as valid Multires sculpting system:\n\n1. Multires in 2.81 does not support switching levels. This invalidates the feature completely and makes it not functional, but prevents the users to corrupt the mesh data if they use it. This is like not having Multires sculpting at all.\n2. Multires in 2.80 creates artifacts and vertex explosions when modifying any level, creating irreparable mesh data corruption. Releasing Blender with Multires in this state and without any visible UI warning could have destroyed the projects of many users in an irreparable way. Luckily, most users were not using it to create their models in the previous versions because it was also not working as intended. \n3. Multires in 2.79 and before creates a visible grid pattern on higher levels when modifying lower ones. This introduces unwanted shape noise and effectively destroys valid sculpted information, making it not functional for its intended use case. Users are limited to work considering of how much they can deform lower levels by the amount of noise they are predicting Multires will produce in the higher ones. This is not something that should be happening in a production ready implementation of the feature.\n\nThe most advances tools Blender has right now that were added in the last releases (Quadriflow, Elastic deform, IK Pose brush...) are designed to work with a Multires system:\n\n- The main purpose of Quadriflow is to produce subdividable geometry for a Multires. When you are done sculpting with Dyntopo/Voxel remesher, where you can’t have the freedom to choose the level of detail you want to work on, you can quickly generate a base mesh, subdivide it and reproject the details back. That way you can tweak again general proportions and low frequency detail.\n\n- These brush tools are designed to tweak proportions/big shapes of models, which is something you most likely want to do after sculpting more detail to have an idea of how your model looks like. Multires solves that problem.\n\n- These brushes can’t be used directly on high poly meshes. These tools needs to have disabled some sculpt mode optimizations in order to work, so they are much slower than regular brushes. In fact, if you try to use the IK pose brush directly on a high poly mesh, most likely you are going to run out of memory. If you don’t, it is going to create terrible artifacts between each segment. In order for these brushes to work as intended on high poly meshes, you need to use Multires to switch to a lower level, use the brush, and then switch to a higher level again to get the intended result.\n\n## Multires implementation reference\n\nSculptGL contains a valid and functional Multires sculpting implementation. You can try it by sculpting different details at different levels and switching between them, as well as creating and deleting subdivision levels:\n\nsculptgl/\n\nThis implementation of Multires provides:\n\n- Detail propagation that works across all levels. You can choose the desired level you want to sculpt on and that deformation is propagated correctly to all subdivision levels. There are not visible artifacts of any kind.\n\n- You can both create and delete levels in both directions (higher levels and lower levels) with subdivide/delete higher and reverse/delete lower. \n\nThese features are the minimum and required a Multires implementation in Blender should provide, as they are pretty much the definition of a Multires sculpting system. Any other Multires related feature or optimization (being part of the modifier stack, baking, shape keys, layers, exporting, reprojection, tool compatibility, Quadriflow...) should always come later. There should not be a design decisions that prioritize any other Multires feature or optimization without having those minimums perfectly working, bug free and functional.\n\n\n## Proposal\n\nGiven the fact that, as described here, Multires was never a functional feature for its intended purpose and:\n\n- The code is extremely hard to read and maintain. I still can’t understand what it is doing in some places or what was the reasoning to make it work that way in the first place. \n- New features are planned that require Multires support (masking tools, vertex colors, visibility operators). Adding Multires support for those features should not be a project bigger than the feature itself. This was the case with most of the 2.81 tools, and probably with the future planned features (Sculpt vertex colors or visibility management, for example)\n- We already have and sculpt tools abstraction layer in place. Making changes on the underlying data structures of sculpt mode should be easier than before\n- The original Multires comes from before 2.5. The basics of how it should works were never correct and a lot of features and modifications were added during the years. We are now trying to build state of the art sculpting features on top of a broken foundation that has more than 10 years. \n\nSome options are:\n\n\t- Replace Multires modifier with a simple implementation based on the SculptGL code (something we know it works) and start again from there. We can keep the current Multires modifier for compatibility, but we need to evaluate if supporting the features and fixes described in this task on the current code (and make it work exactly as the SculptGL Multires) is going to take more time than implementing something based on the SculptGL code from scratch. We also need to look that the new features that are planned and evaluate how hard they are going to be to add to the current Multires code (colors, per face data...) knowing that the SculptGL implementation already supports them.\n\t\n\t- Try to add this functionality to the current Multires modifier. In that case, the priority should always be supporting the functionality described in this task first, and the bring all the rest of the features back. In that case, it would be needed better documentation and code organization to be able to integrate new features into it easily. " ]

[ "Sculpting mesh with multi resolution modifier and particle system causes crash\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.8 All releases tested to today's build \nversion: 2.80 (sub 41), branch: master, commit date: 2019-01-17 10:44, hash: ad707115d5bc, type: Release\nbuild date: 17/01/2019, 03:08\n\nWorked: 2.79\n\n**Problem**\nWhen an object has a multi resolution modifier with at least one subdivision, and a particle system also added (normal particle system or hair, does not matter) and sculpt mode is entered and a sculpt stroke is attempted, Blender will almost always immediately crash. One time in a test, my mesh's vertices randomly went everywhere resulting in a pokey sphere. A second sculpt stroke then once again crashed Blender.\nI spent hours tracking this down on one of my models, and it turned out to be fairly straight forward! (in terms of steps to create the crash)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n- Add any mesh (or just use default cube)\n- Add multi resolution modifier\n- Add a subdivision level\n- Add a particle system. (Parameters do not seem to matter, default will produce error)\n- Enter sculpt mode\n- Attempt to make a sculpt stroke.\nThis should produce a crash. Sometimes the mesh does simply disappear or get a very strange deformation (all vertices shoot out to random positions) but either making another stroke (if vertices are still visible but crazy) or toggling out of sculpt mode and back in and making another sculpt stroke has produced the error. It seems more vertices/subdivisions means a more guaranteed crash.\n\nI have tested this with a completely fresh install with no extra add-ons beyond the defaults and it has produced this error as well.\n\nThank you so much, Blender team for your hard work and dedication to Blender. I have enjoyed countless thousands of hours in Blender, and every time a bug that I submit is fixed, I am humbled by your efforts. What is the best way to donate directly to developers? Thank you again.\n" ]

[ "Assert duplicating a collection in a linked scene\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.1.0 Alpha\n\nAssert duplicating a collection in a linked scene\n\nfrom the default startup:\n- 1) `Scene` > `Linked Copy`\n- 2) select the collection `Collection` in the Outliner\n- 3) context menu > `Duplicate Collection` or `Duplicate Linked` (does not matter which)\n\n```\nBLI_assert failed: source/blender/blenkernel/intern/collection.c:184, collection_owner_get(), at '(id->tag & LIB_TAG_NO_MAIN) == 0'\n```\n\nIf the file is saved (and reloaded) before step 3), the above assert does not happen", "VSE: The blend and opacity settings that strips are created with does not match the default values they revert back to\nOperating system: Linux-5.4.0-80-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce 9800 GT/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.108\n\nBroken: version: 3.0.0 Alpha\nWorked: Unsure\n\nStrips are created by default with blend method \"Cross\" and blend opacity \"1\", however reverting to default values results in \"Replace\" and \"0\".\n\n- Open VSE\n- Add/create any strip\n- Under strip properties in sidebar, note that blend method is \"Cross\", and opacity value is \"1\"\n- Choose \"Reset to default value\" from context menu for both of these settings\n- Blend method will change to \"Replace\"\n- Opacity value will change to \"0\"", "Workspace duplicate resets my tweak tool back to default select box\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 11)\nWorked: ???\n\nAnd EACH time I create new workspace I forced to change it back to tweak, because i prefer it.\nIt is a pain in the … code.\n\nWhy do I think it is a bug? Because scale cage or annotation are saved.\n[2020-04-02_16-44-41.mp4](2020-04-02_16-44-41.mp4)\n\n", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "Modifiers which deform spline points propagate across all users of the same data unexpectedly\nVersion: 2.81 build Oct 23 (Linux 64)\n\nWhen a Curve Object Modifier uses the \"Apply On Spline\" setting, it seems to affect the curve data directly. This means that if a curve data block is used by multiple objects, a modifier on one of those objects will affect all the others.\n\n[curve_modifier_bug.blend](curve_modifier_bug.blend)\n\nTo reproduce, open and inspect the attached file. Notice that the objects on the left both have deformation modifiers, while their clones on the right do not. However, the curve object still appears to be modified because it uses the same data as the modified curve object. This is not how modifiers are supposed to behave. \n\nThe expected behavior is demonstrated by the two mesh objects. Like the curve objects, they also share the same data, but the effect of the modifier is limited to the owner of the modifier.", "Duplicating hair particles from one file to another is not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.25\n\nBroken: version: 3.3.0\nWorked: I don't know. And at least, v3.2.1 is also affected.\n\nFor Eevee rendering, duplicating the hair particles within the same file is working as expected, because the duplication and the original hair look exactly the same. \nHowever, duplicating the hair particles from one file to another is not working for Eevee rendering, because they do not look identical. \nMoreover, under the Eevee rendering, the duplicated hair can no longer be controlled by the particle system. (In comparison, Cycles rendering is not affected by this problem.)\n\nThe video to reproduce the error:\n[Duplicate hair under Eevee.mkv](Duplicate_hair_under_Eevee.mkv)\n\n**Steps to reproduce**\n[eevee hair test3.blend](eevee_hair_test3.blend)\n\n- Open file\n- Copy objects `LLonglash` and `LLonglash.001`\n- Open new file\n- Paste objects\n# Inspect hair shape\n\n", "Graph Editor menu item Key -> Clean Channels and Key -> Clean Keyframes have the same descriptive text\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0 Alpha\nWorked: none\n\nThe graph editor menu item Key -> Clean Channels and Key -> Clean Keyframes have the same descriptive text when they do two different things.\nKey -> Clean Channels help text should be changed to Clears keyframes on channels that have default values.\n\nCreate some animation on the default cube\nopen the graph editor\nselect the curves\nChoose the Key menu\nHover over the Clean Channels and Clean Keyframes menu items to see the text.\n", "Spin Duplicate Tool gizmo uses the wrong operation\nOperating system: Linux-5.15.0-27-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.3.0 Alpha\n\nThe gizmo of the Spin Duplicate tool in the toolbar uses executes the wrong operation. Instead of using the Spin Duplicate operation it will use the Spin operation.\n\nTo get the correct behaviour, try changing the \"Drag\"setting in the header tool settings to \"Active Tool\".\nThen click and drag anywhere.\n\n----\n\nI also want to include the proposal to just merge the Spin and Spin Duplicate tools and instead add an option in the tool settings called \"Use Duplicates\".\nBoth tools use the same operator anyway with the only difference that this one option is toggled.", "VSE annotations not \"per scene\"\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90 (sub 3)\n\nVSE annotations are not \"per scene\". When creating a new scene, the VSE still see the same annotations.\nAlso, in 3D, annotations are per scene, but all scene's annotations are visibles in the dopesheet, though only the correct one is visible in the viewport.\n\n- in Video Sequence Editor, create a few anotations (several frames), add a new strip (color for exemple)\n- create a new scene, VSE gets a fresh timeline, but the annotations are still here. you can edit them, go back to the previous scene, and bam, the annotations are the same.\nI put further ideas for improvement here : [https:*blender.community/c/rightclickselect/WCfbbc/ ](https:*blender.community/c/rightclickselect/WCfbbc/)", "Impossible to copy/paste data between different Blender instances that are using different temp directories\n|Operating system:|Linux-5.8.16-2-MANJARO-x86_64-with-glibc2.2.5 64 Bits\n| -- | -- |\n||Windows 10\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.16-2-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.8\n\nBroken: version: 2.92.0 Alpha\nWorked: Never\n\nIt is not possible to copy/paste data between two Blender instances that use a different `Temporary Files` path.\n\n- Open two instances of Blender (regardless of whether they are the same version or different versions)\n- In the destination instance, delete all objects and set a custom path for Temporary Files (in Blender Preferences - File Paths)\n- In the other instance, Ctrl-C to copy default cube, \n- In the destination instance, Ctrl-V to paste,\nIt is not pasted, message \"no objects to paste\"\n\n", "\"Repeat\" property of NLA action strips not updated when splitting\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.49\n\nBroken: version: 2.93.2\nWorked: (exists at least since 2.6)\n\nThe \"Repeat\" property under the Action Clip panel is not updated when splitting strips. So changing the repeat value after a split will cause the strip to \"jump back\" to the original length.\n\n\n- Open blender, switch to the animation workspace, pull up the NLA editor.\n- Add two keyframes to the cube.\n- In the NLA editor, press the \"push down action\" button to make the animation an action strip.\n- Select the action strip, change the \"repeat\" property to 3 (or any number).\n- Move the time cursor to the middle of the strip and press Y to split the strip.\n- Select one of the two strips, now the \"repeat\" property is still 3, which should be something close to 1.5\n- Drag the \"repeat\" property to change the value. Now the strip jumps back to the original length.\n\n\n", "Copy and Pasted framed nodes jitter around when grab and drag\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0\nWorked: N/A\n\n\nWhen copy pasting framed nodes with Ctrl + C then Ctrl + V, then G to move by mouse, many nodes appeared to be jittering for unknown reasons.\n\nThis behaviour doesn't exist when G to move existing framed nodes or when duplicating via Ctrl + D.\n\n(the video compared the behaviour \"ctrl + c / ctrl + v / g to drag\" with \"ctrl + d drag\")\n\n[blender_1n2MKEk5wo.mp4](blender_1n2MKEk5wo.mp4)\n\nThis is important because I have a reasonable doubt that copy pasting framed nodes from 1 node graph to another will sometimes erroneously create invalid socket link due to this jitter. This larger problem is very difficult to reproduce, BUT here is a case where I believe such behaviour result in a \"2 link in 1 socket\" invalid setup (when grab them over other frame nodes).\n\n\n\n- Download the blend,\n- Use Select Box to select the Frame and all nodes inside,\n- use {key Ctrl C} then {key Ctrl V} to duplicate framed nodes in GN view,\n- {key G} to move nodes to see the then swimming.\nTry varying the Zoom if the problem is not noticed.\n\nNOTE: The problem is more noticeable by setting the `Noodle Curving` in Theme to 0\n\n[frame-group-jitter.blend](frame-group-jitter.blend)\n", "Duplicating a node with a driver loses the driver\nWindows 10 Pro, GTX 1060 6 GB\n\nBroken: 2.79b\nWorked: (optional)\n\nDuplicating a node with a driver (e.g. an RGB mix with a driver for the factor) causes the driver to be lost from the duplicate. This makes node setup more tedious than it needs to be.\n\nAdd an empty to the scene.\nSet up an RGB mix node with two color inputs.\nCreate a driver on the factor that uses the empty Y world position.\nWith the node selected, shift-D to duplicate.\n\nThe duplicate will have lost the driver.\n", "Animated curves flickers when Motion Blur and Persistent Data are enabled\nIf there is an animated curve and Motion Blur + Persistent Data are enabled, the curves will randomly appear and disappear. Here is a simplified file that reproduces the issue on master. Render the animation an notice how the curves flicker.\n\n[curvesAnimatedCyclesIssue.blend](curvesAnimatedCyclesIssue.blend)\n\n### Original Report\n\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nDisplay Graphics card: Radeon RX 580 Series 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\nCUDA enabled Graphics card: NVIDIA GeForce GTX 1650 Driver version. DCH 472.12\nCPU: Ryzen 7 2700 (16 threads, 8 cores) \n\n\nBroken: version: 3.2.0\n\n**Description of error**\nObjects disappear from what seems to be random frames close to the beginning of keyframed object transformations in renders produced with Cycles (only).\nThis appears to be the same bug as archived [#40313 ](T40313).\n\n\n\nBug is more prevalent in blender version: 3.1.2 however is still present.\nRender Examples:\n3.1: \n[3.1 build.mkv](3.1_build.mkv)\n3.2: \n[3.2 build.mkv](3.2_build.mkv)\n\nThis Project was using AnimAll addon to animate some of the objects featuring the glitch, these appare to be the only ones still glitching in 3.2. However testing this Addon in a controlled environment does not feature this behaviour, which might suggest its cause is elsewhere, but might be aggravated by animating individual vertices. \n\n* Open Attached Blend file\n* Render Animation in Cycles using files settings.\n\nThis render was made using GPU Compute with CUDA and CPU enabled in system preferences.\nEdit: works on CPU only also. Updated .Blend file with packed textures.\n\nFile removed now simplified is available\n", "Simplify duplication options in user preferences.\nCurrently we have one duplicate option for each and every object data type (in user preferences, 'Editing' section, 'Duplicate Data' panel).\n\nTopic of this task is whether we should keep things like that, or if we should rather simplify options by defining 'categories' instead.\n\nCategories could be:\n* Geometry *(meshes, curves, surfaces, fonts, mballs, lattices, armatures, gpencil)*\n* Physics *(hair, pointcloud, volume, particles)*\n* Lights *(lamp, lightprobe)*\n* Actions *(actions)*\n* Shading *(materials)*\n* Camera *(cameras)*\n* Speaker *(speakers)*\n\nThis could also include better handling of 'new' things, e.g. duplicating (deep copy) of geometry nodes when 'Geometry' is enabled, duplicating (deep copy) of shading nodes when 'shading' is enabled, and so on.\n\nNOTE: this was triggered by #90638 (Inconsistent object data behavior when link-duplicating collections.) and its fix 65dbeb1d81, which required adding three new options there to fully cover all current object types..." ]

[ "VSE Regression: Duplicating grouped strips does not maintain F-Curve keyframes\nOperating system: Ubuntu 21.10\nGraphics card: Mesa Intel Xe Graphics (TGL GT2)\n\nBroken: 3.1.0\nWorked: 3.0.1\n\nWhen you duplicate a grouped strip that have some element with F-Curve keyframes, they are lost.\n\nIn the video you can see the steps:\n\nCreate a strip and add some animation to it. For example, add Translate and set some X values.\nDuplicate them. You can see that the animation is correctly duplicated.\n\nNow group the initial strips and duplicate it. You can see that the duplicated strip loses the animation.\n\n[#96861.blend](T96861.blend)\n[blender_bug.webm](blender_bug.webm)" ]

[ "2.80 Pose Breakdowner doesn't work in Add NLA Strips\nOperating system: ubuntu 18.04\nGraphics card: gtx1080ti\n\nBroken: (2.80)\n\nPose Breakdowner doesnt work when editing NLA Tracks \n\n\nOpen attached file and use Pose Breakdowner\n[broken .blend](broken_.blend)", "Baked Particles are rendered incorrectly on frame 0 and below\nOperating system: Windows 10\nGraphics card: Geforce RTX 3070\n\nBroken: Blender 3.3.5, 3.3.8 ,3.3.7, 3.6\nWorked: Unknown\n\nWhen rendering baked particles systems that have a baked frame on Frame 0 (or below) particles are rendered incorrectly.\nParticles are rendered on the emitter instead of their correct position.\n\n\n- Open the attached blend file (Note: Particles are now displayed incorrectly even in Viewport on Frame 0)\n- Skip 2 Frames ahead in Timeline\n- Go back to Frame 0 (Note: Particles are now displayed as expected)\n- Render Frame 0, Note: Particles are rendered on the surface of the emitter, which is different from what can be observed in the viewport.\n\n", "Mantaflow rendering unstable (when using multiple fluid domains)\nOperating system: Ubuntu 18.04\nGraphics card: Radeon R9 FURY\n\nBroken: 2.83.5\nWorked: none\n\nMantaflow seems unstable during rendering of 6 simultaneous domains and it relates to the cycles AA samples.\nThe error it shows:\n```\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```\n\n1. Open the example file [mantaflow-render-test.blend](mantaflow-render-test.blend)\n2. Bake the domains one-by-one\n3. Run the `Render Animation`\n4. It's quite a random, so could take some time\n5. on ~160 frame the blender will fail and close with the next error:\n```\nSaved: '/home/user/tmp/mantaflow-render-test-scene/out/0161.png'\n Time: 00:03.10 (Saving: 00:00.08)\n\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```\n```\nSaved: '/home/user/tmp/mantaflow-render-test-scene/out/0051.png'\n Time: 00:01.78 (Saving: 00:00.09)\n\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in /home/sources/buildbot-worker-linux_centos7/linux_lts_283/blender.git/extern/mantaflow/preprocessed/fluidsolver.cpp:33\n```", "Render procedural crashes Blender when trying to render\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: version: 3.2.0 Alpha\n\nRender procedural crashes Blender when trying to render\n\nLoad the attached alembic in the file, go Cycles experimental, turn on Use Render Engine Procedural and render.\n\n[Particles_BlastV_v01.abc.zip](Particles_BlastV_v01.abc.zip)\n\n", "Evee crashes when rendering \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.3\n\nRendering this file with evee causes a crash. Cycles is able to render the file.\nThe mesh was originally created in blender 2.6x with blender internal textures down loaded from blend swap 6618\nI was updating the textures for 2.9.3. \n\nRender the image.[crash.txt](crash.txt)\n\n[debug.blend](debug.blend)\n\n", "Render crashes – metal related\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.2\n\nI get some of these intermittently: `Context leak detected, msgtracer returned -1`\nrender ultimately fails (always at around frame 400) with this:\n\n```\nCommandBuffer Failed: cycles_metal_integrator_reset\n\nRefer to the Cycles GPU rendering documentation for possible solutions:\ngpu_rendering.html\n\nCommandBuffer Failed: cycles_metal_integrator_init_from_camera\n``` \n\n- download and extract the files attached to this issue\n- run `render.sh` + wait until blender crashes\n\n~~using the opengl backend, it works just fine~~\n\n", "Blender 2.8 and 2.81 (ab519b91b2c4) has high chance of crashing when using Python to create a new node-tree link.\nOperating system: Windows 10 (x64) v1903 Build 18362.356\nGraphics card: Nvidia GeForce GTX 1060 6GB\nCPU: Intel Core i5 7600K\n\nBroken: 2.81-ab519b91b2c4 **AND** 2.80 release\n\nCreating a new node-tree link via Python sometimes causes Blender to crash with the error \"EXCEPTION_ACCESS_VIOLATION\".\nI have attached a .blend file that will cause the crash, just by clicking \"Run Script\" once or twice. \nWhen I found the bug, I spent some time making the script as small as possible while still causing the crash, so the script is less than 30 lines.\n\nI also installed Blender 2.81-ab519b91b2c4 on a Windows 10 laptop that had never seen Blender before, and the bug was present on there too, so I'm confident the issue isn't specifically due to my hardware.\nI've also included blender_debug_output.txt and blender_system_info.txt, generated by the blender_debug_log.cmd file included in the Blender 2.81 download.\n\n1) Open the attached .blend file.\n2) Click \"Run Script\" in the bottom right of the text editor pane.\n3) Repeat 2 until crash (should only take 1 or 2 tries)\n\n[Crashy crash.blend](Crashy_crash.blend)\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)", "Blender baking's margin overlap if multiple meshes are selected\nBasically just a duplicate of T51134 that Aaron Carlisle asked me to send as a new report.\n\n\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: AMD RAVEN (DRM 3.35.0, 5.4.0-58-generic, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.8\n\nBroken: version: 2.90.1\nWorked: never with Cycles as far as I know.\n\nCycles overlap the region margin on other islands in the final result.\n\nCycles will bake an object/island, apply the margin, then proceed to do the same to the next one on top of the previous and they will overlap if the margin is bigger than the distance of the UVs, instead of applying to the finished bake and having the margins having an equal distance between islands, as Blender Internal used to do.\n\nJust press bake on the file. Or any multiple objects with a margin bigger than the UV islands.\n\nAs far as I know this has always been a problem with the Cycles baking implementation, besides some other issues of performance and usability. For instance if baked with multiple objects selected it is much, much slower than if I collapse them and merge, as I mentioned in the previous bug report.\n\nI understand it should be slower if they are separated, but I don't imagine it should be that much slower.\n\n\n\n", "Artifacts appear in texture bakes [stripe pattern]\nOperating system: Windows 10 Pro 64-bit\nCPU: i7 4790\nGraphics card: GTX 1050\n\nBroken: Every Blender Build on this PC, Baking.\nWorked: never\n\nWeird artifacts appear in bakes, especially visible in the AO bakes (see attached images)\n\n\n\n\n\n[AOArtifacts_Test.blend](AOArtifacts_Test.blend)\n- Open blend\n- hit `Bake`", "No way to edit baked cloth simulation with particle edit mode.\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 680\n\nBroken: 2.82\n\nCan not edit the cloth cache inside of particle edit mode. I am aware of the fade time error inside of options, I am not using fade time I am purely just seeing if what the manual says is possible, editing a cloth sim cache\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. add a cloth sim\n2. Bake cloth sim\n3. go into particle edit mode\n4. no way to edit cloth sim\n\n[ClothEditTest.blend](ClothEditTest.blend) I have uploaded the file I am testing it with", "Blender crashing while baking Smoke Domain\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.0 & 3.2.0 Alpha\nWorked: NA\n\n\nBlender Crashes while baking smoke domain\n\n- open Project \n- Select smooth domain from outliner\n- {nav Physic properties > Bake All} (crash between frame 60 & 70)\n\n\n\n\n", "Baking of normals show different results between versions\nOperating system: Win 10\nGraphics card: Geforce 3060\n\nBroken: 3.5.1\nWorked: 3.4.1\n\nThis changed in 75ad8da1ea6799e3983e4146f4b20dc4bfbb8415\n\n\nBaking of normal map differnet between Blender versions\n\nThe Attached blend file will output differnt result when trying to bake the normals.\nThe Mesh is part of a comercial mesh I use, therefore I cannot share the whole mesh, but in the blendfile you just need to bake the normals in blender 3.4.1 and then in 3.5.1\nThe results are differnet.\n\nBlender 3.5.1 seams to have some bug in the baking or handles the baking differnt.\n\nEdit:\nSeams like the Auto-Smooth of meshes bauses this difference between the versions", "Baked Normal Map Is Not Equal To The Original Normal Map.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.Q4.221025\n\nBroken: version: 2.93.2\n\nThe problem that after I bake the normal it appears different than the original\n,Is this a bug ? , and why it appears different .\n\n1. Open blender\n2. Go to the shading window\n3. Select The cube \n4. Add normal map image connect it to the normal map after you add it , Then to the BSDF node \n5. create image to bake to it and select it \n6. bake the normal and see the result\n\n", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Baking API: remove non-working baking to external image, also cleanup misleading error messages\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0\n\nWhen baking for example an AO map, on a mesh, with no materials. You'll get an error stating you can bake to an external file [which was never implemented fully]\nSo that means the API would need to be cleaned up [non-working external save_mode removed, warning-/error messages adjusted]\n\nLoad new file,\ngo to bake tab\nselect ambient occlusion\nHit bake.\nNotice error, It suggests to save to an external file. But there is no option to select an external file.\n\n" ]

[ "2.8 GPU texture baking is broken ?\nOperating system: Windows 10 64bit Version 1803\nGraphics card: nVidia GTX1070 Driver version 417.35\n\nBroken:\n(2.80 beta, 4488056f3d9, 2018-12-16)\nWorked: \n(2.79, 2017-09-11 )\n\n\n\nWhen setting Cycle device to GPU, if you bake a texture for the 1st time it works, if you do it for the 2nd time, you'll get this error:\n**Cuda error at cuCtxCreate: Illegal Address** And the viewport Render view doesn't work at all (everything is gray) and pressing F12 to render also doesn't work.\n\n\n\n\n - based on the simple scene: \n\n - Unwrapped the cube,\n\n - created a texture,\n\n - saved it,\n\n - added Image texture Node to the cube material\n\n - assigned the created texture to it\n \n - selected the cube\n\n - hit Bake\n```\n\n```\n\nEverything worked as expected until i go back to the viewport (rendered mode) and start moving around, nothing works, everything is either gray or \"stack\" in a glitchy way.\n\nI hit Bake again, and the baked textured is now all empty (transparent) and i get this message:\n**Baking map saved to internal image. save it externally or pack it**\n\nfollowing by this error:\n\n**Cuda error at cuCtxCreate: Illegal Address**\n\n\nAnd the only way to fix this is to change the rendering Device from \"**GPU Compute**\" to \"**CPU**\", once am at \"**CPU**\" everything works perfectly fine, i can bake as much as i want.\n\nthanks" ]

[ "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "\"Updating Objects Flags\" Stalling Blender\n{[F10130762](22_Nautilus_through_City_-_Cycles___Eevee.zip)}Operating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 2.92.0\nWorked: Not working down to 2.83 LTS\n\nThis file will not render the Scene named \"Cycles\" with the Cycles render engine. \n\n\n1. Open attached blend file. Note everything except camera and lights are turned off.\n\n2. Using command line, attempt to render a single frame (say 130).\n\n3. Result = Everything initialises but the render stalls on \"Updating Objects Flags\".\n\n4. Open the file in UI\n\n5. Render image renders a blank image (expected).\n\n6. Turn on Buildings and Landscape, 9 collections from the top, and Nautilus and Submarine Search Lights at the bottom. \n\n7. Render a single frame, or the cycles render layer in the compositor.\n\n8. Result = A single image may render in cycles (followed by the second scene in Eevee that composites).\n\n9. Render animation\n\n10. Result = Blender hangs on \"updating objects flags\" and it does not render, and it is not possible to cancel the render.\n\nIt may be possible to get back rendering by saving the file as a new file. But as soon as rendering an animation as attempted, \"updating objects flags\" hangs Blender either in command line or in UI mode.\n\nNotes: \n\n1. I have tried the same file on multiple machines and multiple Operating Systems with the same result.\n\n2. Quite a number of files have similar kinds of problems. Most commonly, the files will not render in UI mode. Usually though, rendering in command line works. In this case it does not.\n\n3. I have tried every permutation of trouble-shooting I can think of. I have added meshes back in one by one, re-baking ocean modifer, particles, everything. Trying recently, I had to re-bake the particles after which rendering stopped working in any configuration. The particle systems have been baked to a disk cache.\n\n4. Reconstructing from a new blend file is pointless - new blend files are fine and I do not know what is happening to bring about the bug.\n\n5. It may be necessary to re-send the file in its state when it cannot render. Please let me know if anymore information is required.", "GPU Subdivision: Wrong objects statistics information\nWindows 10\ni7-4790\n16 GB RAM\nRTX 2070\n\nBlender v3.4.1 (Steam)\n\nWrong objects statistics information in object mode when GPU Subdivision is enabled\n\n- Open `Rat.blend` file\n- Enable GPU subdivision\n- Rotate/move the bone\n- Switch to object mode (notice the viewport statistics)\n\n\n\n", "Use after Free (according to asan) while baking.\nOperating system: Linux-5.4.0-90-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked:Don't know\n\nWhen pressing 'bake' in the attached (simple) blend file blender crashes when compiled with address sanitizer. Strangely only when in the UV-editor workspace, and not in the shading workspace.\n\n\n- build blender in debugmode with developer options\n- open the attached .blend\n- press bake\n\n\n[printuvs.blend](printuvs.blend)\n\nOr else from default startup:\n- build blender in debugmode with developer options\n- add a noise texture + colorramp to the base color input of the default material\n- add an image texture (sized 128x128) to the material and make it active\n- switch to uv editor workspace\n- switch renderer to cycles\n- open bake tab, choose diffuse bake\n- press bake\n\nASAN output:\n```\n\n==30632==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000566c90 at pc 0x000006232e48 bp 0x7fff79d57550 sp 0x7fff79d57540\nREAD of size 4 at 0x613000566c90 thread T0\n - 0 0x6232e47 in paint_object_is_rendered_transparent /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:52\n - 1 0x62333f5 in OVERLAY_paint_init /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:75\n - 2 0x61e20f1 in OVERLAY_engine_init /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_engine.c:138\n - 3 0x60336a7 in drw_engines_init /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1037\n - 4 0x60394be in DRW_draw_render_loop_ex /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1641\n - 5 0x6038abd in DRW_draw_view /home/martijn/progs/blender-git/blender/source/blender/draw/intern/draw_manager.c:1571\n - 6 0xadf0436 in view3d_draw_view /home/martijn/progs/blender-git/blender/source/blender/editors/space_view3d/view3d_draw.c:1573\n - 7 0xadf05bf in view3d_main_region_draw /home/martijn/progs/blender-git/blender/source/blender/editors/space_view3d/view3d_draw.c:1595\n - 8 0x7f2353c in ED_region_do_draw /home/martijn/progs/blender-git/blender/source/blender/editors/screen/area.c:564\n - 9 0x53d6339 in wm_draw_window_offscreen /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:730\n - 10 0x53d7569 in wm_draw_window /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:880\n - 11 0x53d89d8 in wm_draw_update /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_draw.c:1081\n - 12 0x53c5120 in WM_main /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm.c:658\n - 13 0x34c4239 in main /home/martijn/progs/blender-git/blender/source/creator/creator.c:558\n - 14 0x7f41af1ae0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n - 15 0x34c35bd in _start (/mnt/fast/martijn/progs/blender-git/build_linux_debug/bin/blender+0x34c35bd)\n\n0x613000566c90 is located 208 bytes inside of 360-byte region [0x613000566bc0,0x613000566d28)\nfreed by thread T20 here:\n - 0 0x7f41af9ef1c7 in __interceptor_free ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:123\n - 1 0x1bb10832 in MEM_lockfree_freeN /home/martijn/progs/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:130\n - 2 0x5f86383 in blender::deg::IDNode::destroy() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/node/deg_node_id.cc:143\n - 3 0x5e21387 in clear_id_nodes_conditional<blender::deg::Depsgraph::clear_id_nodes()::<lambda(ID_Type)> > /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:162\n - 4 0x5e1e4c0 in blender::deg::Depsgraph::clear_id_nodes() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:173\n - 5 0x5e1cdf8 in blender::deg::Depsgraph::~Depsgraph() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:89\n - 6 0x5e20080 in DEG_graph_free /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:325\n - 7 0x9ca04e1 in bake /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1608\n - 8 0x9ca3d40 in bake_startjob /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1775\n - 9 0x5461946 in do_job_thread /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:393\n - 10 0x1bae287e in tslot_thread_start /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 11 0x7f41af920608 in start_thread /build/glibc-YbNSs7/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread T20 here:\n - 0 0x7f41af9ef6f7 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154\n - 1 0x1bb10f20 in MEM_lockfree_callocN /home/martijn/progs/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:236\n - 2 0x370cccf in BKE_libblock_alloc_notest /home/martijn/progs/blender-git/blender/source/blender/blenkernel/intern/lib_id.c:1095\n - 3 0x5f84eff in blender::deg::IDNode::init_copy_on_write(ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/node/deg_node_id.cc:114\n - 4 0x5e1e02c in blender::deg::Depsgraph::add_id_node(ID*, ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph.cc:127\n - 5 0x5fa14e5 in blender::deg::DepsgraphNodeBuilder::add_id_node(ID*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:178\n - 6 0x5fcd141 in blender::deg::DepsgraphNodeBuilder::build_material(Material*) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1797\n - 7 0x5fcdee5 in blender::deg::DepsgraphNodeBuilder::build_materials(Material**, int) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:1819\n - 8 0x5fb47b3 in blender::deg::DepsgraphNodeBuilder::build_object_data(Object*, bool) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:941\n - 9 0x5fb0010 in blender::deg::DepsgraphNodeBuilder::build_object(int, Object*, blender::deg::eDepsNode_LinkedState_Type, bool) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes.cc:787\n - 10 0x601516d in blender::deg::DepsgraphNodeBuilder::build_view_layer(Scene*, ViewLayer*, blender::deg::eDepsNode_LinkedState_Type) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/deg_builder_nodes_view_layer.cc:117\n - 11 0x5f19f8e in blender::deg::ViewLayerBuilderPipeline::build_nodes(blender::deg::DepsgraphNodeBuilder&) /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline_view_layer.cc:35\n - 12 0x5f06808 in blender::deg::AbstractBuilderPipeline::build_step_nodes() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline.cc:72\n - 13 0x5f058af in blender::deg::AbstractBuilderPipeline::build() /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/builder/pipeline.cc:51\n - 14 0x5e2ff1d in DEG_graph_build_from_view_layer /home/martijn/progs/blender-git/blender/source/blender/depsgraph/intern/depsgraph_build.cc:259\n - 15 0x9c9c19e in bake /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1236\n - 16 0x9ca3d40 in bake_startjob /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1775\n - 17 0x5461946 in do_job_thread /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:393\n - 18 0x1bae287e in tslot_thread_start /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7f41af920608 in start_thread /build/glibc-YbNSs7/glibc-2.31/nptl/pthread_create.c:477\n\nThread T20 created by T0 here:\n - 0 0x7f41af996a65 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216\n - 1 0x1bae2aa8 in BLI_threadpool_insert /home/martijn/progs/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x546296a in WM_jobs_start /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:488\n - 3 0x9ca69f8 in bake_invoke /home/martijn/progs/blender-git/blender/source/blender/editors/object/object_bake_api.c:1938\n - 4 0x53e6d36 in wm_operator_invoke /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1347\n - 5 0x53e8c9e in wm_operator_call_internal /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1554\n - 6 0x53e8ef9 in WM_operator_name_call_ptr /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1602\n - 7 0x53ea323 in WM_operator_name_call_ptr_with_depends_on_cursor /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1790\n - 8 0xa4d665e in ui_apply_but_funcs_after /home/martijn/progs/blender-git/blender/source/blender/editors/interface/interface_handlers.c:1030\n - 9 0xa565bfd in ui_handler_region_menu /home/martijn/progs/blender-git/blender/source/blender/editors/interface/interface_handlers.c:11435\n - 10 0x53e0497 in wm_handler_ui_call /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:690\n - 11 0x53f88dc in wm_handlers_do_intern /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3052\n - 12 0x53f99d3 in wm_handlers_do /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3166\n - 13 0x53ffb0e in wm_event_do_handlers /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3656\n - 14 0x53c5108 in WM_main /home/martijn/progs/blender-git/blender/source/blender/windowmanager/intern/wm.c:652\n - 15 0x34c4239 in main /home/martijn/progs/blender-git/blender/source/creator/creator.c:558\n #16 0x7f41af1ae0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/martijn/progs/blender-git/blender/source/blender/draw/engines/overlay/overlay_paint.c:52 in paint_object_is_rendered_transparent\nShadow bytes around the buggy address:\n 0x0c26800a4d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4d70: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd\n 0x0c26800a4d80: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n=>0x0c26800a4d90: fd fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4da0: fd fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa\n 0x0c26800a4db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4dc0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c26800a4de0: fa fa fa fa fa fa fa fa fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n Addressable: 00\n Partially addressable: 01 02 03 04 05 06 07 \n Heap left redzone: fa\n Freed heap region: fd\n Stack left redzone: f1\n Stack mid redzone: f2\n Stack right redzone: f3\n Stack after return: f5\n Stack use after scope: f8\n Global redzone: f9\n Global init order: f6\n Poisoned by user: f7\n Container overflow: fc\n Array cookie: ac\n Intra object redzone: bb\n ASan internal: fe\n Left alloca redzone: ca\n Right alloca redzone: cb\n Shadow gap: cc\n==30632==ABORTING\n```\n\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "Textures messed up when rendering with Cycles HIP on AMD Radeon RX 7900 XTX\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (I'm actually using Windows 11 22H2 22621.1265 by winver)\nGraphics card: AMD Radeon RX 7900 XTX ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.2.230217\nCPU: AMD Ryzen 9 7950X\n\nBroken: version: 3.4.1\nWorked: None. I've tried *3.3* (GPU rendering is not working, blender said like a HIP binary is missing, sorry I forgot the details), *3.4.1* (GPU rendering is working, but has this issue) and today's *3.5.0 beta v35.83f28793c0b3* (same as 3.4.1)\n\nWith Cycles HIP, when rendering a basic scene (any mesh, simple Principled material with 1 albedo and 1 normal map) on an AMD Radeon RX 7900 XTX, the rendered result is totally wrong: either 1) the mesh appears that it's wrongly colored by the normal map, the albedo is missing, or 2) has no normal maps, only base color is showed.\n\nHere's a scene I made, rendered with CPU (same result on a RTX 2060 Super GPU):\n\n\n\nHere's one possible GPU rendered result (missing albedo, case 1 above):\n\n\n\nHere's another possible result (missing normal map, case 2 above):\n\n\n\nBoth of the 2 cases above are possible, and may change to the other each time you start rendering.\n\nThis issue also happens when environment texture (HDRI) is used. Simply put: it seems to me that only one \"randomly chosen\" texture can be handled at a time, and all other textures in the scene are replaced by that.\n\nTurning off Smart Access Memory does not help.\n\nOn a computer with RX 7900 XTX, and with blender Cycles Render Devices > 7900XTX ticked:\n\n1. Open [project.blend](attachment)\n2. Press F12 to render the scene\n\n---\n\nWith regards,\nOasin\n\n", "Blender will not use new GPU for rendering or recognize it for OpenCL or\nOperating system: Windows 10, all up to date\nGraphics card: msi 4070ti (brand new)\n\nBroken: 2.93.18 as well as the most recent 3.5 on the splash screen, tried most of the in-between builds on clean reinstalls but same issue on all of them.\nWorked: no version\n\n**Error**\nAfter getting a new 4070ti, blender started crashing every 5-10mins or so while moving around a simple scene in the viewport set to material shaders mode, not render mode. The scene consisted of a couple of primitives with very simplistic wood, glass, and metal shaders. When I tried rendering as is it also crashes immediately upon rendering no matter what I use. GPU wasn't greyed out in render settings initially (though it now is), but only showed in preferences under CUDA, and wasn't recognized in OptiX or OpenCL (in newer blender models it also wasn't recognized by anything but CUDA). \n\n1. tried to render a simple scene with render settings set to new gpu\n2. render crashes immediately\n3. move around in viewport on material mode, barely move and blender crashes\n4. check Blender preferences <system <cycles rendering devices: gpu is visible in CUDA but not in any other options (originally was working on 2.93 where I wanted to use OpenCL, I know this isn't in the newer versions with OptiX/all non-CUDA options). Try unchecking CPU hoping to force blender to actually use the GPU and have tax manager up to see if gpu is even being used\n5. blender crashes without rendering, no sign of gpu being used on task manager but CPU usage spikes to 100%\n\n**What I've tried so far that might be helpful**\n\n- tried clean reinstalling different versions of blender, both newer/experimental and older/more stable builds\n- made sure I reset BIOS in case this is a new component/migration error\n- made sure the settings for blender in NVIDIA control panel were all compatible or high performance \n- made sure NVIDIA drivers are all studio version and up to date\n- made sure blender cache folder didn't have any kernel errors\n- installed any updates to windows, this did make the gpu visible in OptiX but unfortuantely the same issue persists even with OptiX on any version where blender just won't use it and uses only cpu (despite being unchecked)\n- double checking how much memory I have on my new gpu vs the old one - yup it does\n- benchmarked my gpu using port royal and making sure I could render a project in Premiere. GPU did fine on the benchmark test and was able to render a 20min video fine. Only blender seems to be the problem\n- noticed today in stackexchange there are a lot more reports with others having the same issue, even with equivalent AMD gpus, and all comments said this seems to be a bug\n\n", "Cycles and Eevee Significant Difference in Texture Output\nOperating system: Ubuntu 20.04\nGraphics card: GTX 1060 3Gb\n\nBroken: 2.80 and on (3.0.0 is still affected)\nWorked: 2.79\n\nFrom Blender 2.80, Cycles produces incorrect output for some procedural textures, while Eevee produces correct ones.\n{[F12696991](Cycles.png)}\n\nTest file (I assume there might be other files affected too). [Carbon_90.blend](Carbon_90.blend)", "Regression: GPU Subdivision: EEVEE doesn't refresh viewport correctly with Armature modifier\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3LTS, master\nWorked: 3.2.2\n\nGPU Subdivision doestn't refresh viewport correctly an object when Armature and Subdivision Surface Modifiers are used.\n\n1) Start Blender.\n2) Add Armature object\n3) Switch to \"Shading\" workspace.\n4) Select the Cube and add `armature modifier` then `Subdivision Surface Modifier`.\n5) Switch to Properties Editor to \"Modifier Properties\"\n6) Add armature in armature modifier's object property. \n7) Switch between object-edit mode\nIt works fine when \"GPU Subdivion option\" is turned OFF (Prefrences > Viewport > Subdivision > GPU Subdivision)\n\nI added \"BeforeGPUSubDBug.blend\". You can reproduce this issue by loading the blend file and doing step 7)\n", "Cycles box mapping not working with rotated texture coordinates\nubuntu 14.04, 630GT, 4930k\n\nBroken: 2.74\n\n\nbox mapping doesn't work with object mapping (object) if the object is rotated (only 1 side is properly projected)\n\n\n1. open the blend file\n2. copy \"Cube\" and rotate it (90 degress)\n3. render\n\n\n\n\n\n\n\n\n", "Baked cache files should not depend on blend file name\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 4.0.0 Alpha\n\nBaking eg. Dynamic Paint will create a folder with .bphys files. When I save the scene under a new name and reload the scene the baked files will be ignored. I need to delete the cache and Bake All Dynamics again.\n\nThe baked result should be independent of the scene filename.\n\nMaking the baked files internally independent of the scene filename is important for our render management with CGRU because CGRU will save a specific filename for the clients. Then the clients can't render the baked result.\n\nWorkaround in my case:\n\n- Submitting job\n- Stopping job\n- Loading scene\n- Delete All Bakes\n- Bake All Dynamics\n- Save scene\n- Restart the job\n\nBake something with Dynamic Paint. Save a new scene, reload and check if the baked result will be rendered.\n\n", "Baked Normal Map Is Not Equal To The Original Normal Map.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.Q4.221025\n\nBroken: version: 2.93.2\n\nThe problem that after I bake the normal it appears different than the original\n,Is this a bug ? , and why it appears different .\n\n1. Open blender\n2. Go to the shading window\n3. Select The cube \n4. Add normal map image connect it to the normal map after you add it , Then to the BSDF node \n5. create image to bake to it and select it \n6. bake the normal and see the result\n\n", "Collada import/export: transparent textures don't work\nOperating system: Linux\n\nBroken: blender-3.3.0-alpha+master.dfb8c90324c0, probably all versions since 2.8\nWorked: 2.79\n\nCollada cannot import or export transparent (alpha) textures.\n\nImport this .dae\n\n[BlenderLogoDae.zip](BlenderLogoDae.zip)\n\nThe result (with 2.79 for comparison).\n\n\n\nManually hook up the alpha in the node graph and export. Open the .dae in a text editor and confirm there is no <transparent> element (which sets the alpha texture). You can confirm exporting works in 2.79 by exporting and reimporting.\n\n**Other**\nNote that OpenCollada's parsing of transparency is weird and buggy, see [D11259](D11259) and 651.", "Custom render engine is unable to create gpu context\nOperating system: Linux-5.19.17-2-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon Graphics (renoir, LLVM 14.0.6, DRM 3.47, 5.19.17-2-MANJARO) AMD 4.6 (Core Profile) Mesa 22.3.1\n\nBroken: version: 3.5.0 Alpha\nWorked: Blender 3.4\n\nUnable to perform background rendering using `gpu` module in custom render engine.\n\nRun the script in background mode: `blender -b -P background-gpu.py`. Blender throws: `SystemError: GPU API is not available in background mode`, despite the line `bl_use_gpu_context = True` in custom render engine. Worked perfectly fine in blender 3.3 and 3.4. Not in 3.5 though.\n[background-gpu.py](background-gpu.py)\n\n" ]

[ "Cycles baking in 2.8 fails and reports CUDA errors\nOperating system: Windonws 64\nGraphics card: GTX 1080 ti + GTX 980\n\nBroken: 2.80, d415b5c7b85, 2018-12-11\n\nWorked: 2.79\n\n\nWhen trying to bake a mesh in 2.80 using Cycles and GPU the console reports many CUDA errors and no map is baked or saved\n\n\nLoad attached 2.8 file in 2.8, select the Monkey mesh (also make sure the texture node called \"Monkey_Lightbake\" is selected in the shader editor) then press \"Bake\" in the render tab. (Also make sure you are using GPU not CPU in cycles). The baking might report that it finishes however no progress bar was shown and not map is rendered. On subsequent bake attempts the console window will show many CUDA related errors (Screen shot attached)\n\n\n\n[Monkey_28_bake_test.blend](Monkey_28_bake_test.blend)\n\n[Monkey_279_bake_test.blend](Monkey_279_bake_test.blend)\n\n[system-info.txt](system-info.txt)" ]

[ "Custom data split normals are taking active object from the area even if the active object is overriden\nBlender 3.5\n\n\nOperators `customdata_custom_splitnormals_add` and `customdata_custom_splitnormals_clear` if called from properties panel seem to take active object from currently active area even if you `context.temp_override(object=obj)` or `context.view_layer.objects.active = obj` to change active object which is counterintuitive and contradicts with how other operators active object override work.\n\nFound a workaround - if you `context.temp_override(area=None, object=obj)` it will take active object into account.\n\n\n1. Open attached .blend file\n2. Run the script\n3. (Make sure all objects are selected)\n4. Go to Custom Split Normals section (in Object Data Properties after Geometry Data).\n5. Try \"Add CSN\" - it wouldn't work\n6. Try \"Add CSN override area\" - it doesk work.\n\n", "Python API: Mesh editing: Editing uvs after normals with a previously assigned variable doesn't work\nBroken: 3.5.1\nWorked: 3.4.1\n\nCaused by 6c774feba2\n\nHolding on a variable referencing the uv layer data for later uv editing, doesn't work when normals are edited in between\n\nRun the attached python script in Blender 3.5.1\nThis creates three objects, all should have all their loop uvs as 0,0:\n\n- no_set_normals (should have default normals, sideways)\n- with_set_normals_and_reaccess_uv (should have upwards +z normals)\n- with_set_normals_but_no_reaccess_uv (should have upwards +z normals)\n\nGo in edit mode on each generated object, look at the normals and uvs\nThe results are only correct for no_set_normals and with_set_normals_and_reaccess_uv\nFor with_set_normals_but_no_reaccess_uv, neither the uvs nor normals are correct. Both appear to be defaults\n\nIn Blender 3.4.1 this works as expected, i.e. with_set_normals_and_reaccess_uv and with_set_normals_but_no_reaccess_uv are identical\n\nAttached are also screenshots in 3.5.1 of the normals and uvs of each object\nAnd a screenshot in 3.4.1 showing the expected results\n\n**Guess at what's happening**\nOn more complicated cases (actual meshes with hundreds of triangles), the normals are messed up (seemingly random instead of defaults) and Blender is prone to crashing. This leads me to believe holding on the uv layer data after normal editing accesses freed memory or something like that?\n\n", "Bake of the second particle system after duplication and making it unique makes mess.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: version: 2.79 (sub 7), branch: blender2.7, commit date: 2019-05-23 08:19, hash: 054dbb833e15, type: Release\nbuild date: 24/06/2019, 17:18\n\nIf you duplicate particle settings, make them unique, and tune, bake of dynamica will broken.\n[2019-07-16_10-03-29.mp4](2019-07-16_10-03-29.mp4)\n\nFinally I found how to reproduce it.\n\nCreate plane, \nCreate particle system that emits cubes (color A) from -50 to 50 frame with short lifetime (20).\nDuplicate particle settings, make settings unique, rename it.\nChange instance to another cube (color B), change working period to 50 — 100 frames.\nCheck work in the viewport. Bake all dynamics, Revert file.\n\nMessed:\n[duplicated particle settins.blend](duplicated_particle_settins.blend)\n\nBug is not appere only if you create separate fully independent settings in the fresh file.\nWith independently created particles systems\n[fresh separate created.blend](fresh_separate_created.blend)\n\n\nPerhaps it can be connected with #61963\nLooks like some data just stucks\n\n\n", "Causing other objects to be named .001 doesn't immediately update the Viewport Name Display\nI found this in 3.0.0 but happens the same in 3.1.0.\n\nWhen you turn on Viewport Name Display:\n\n\nAnd then you rename a new object the same as object that was already in the scene:\n\n\nThe name of the original doesn't update until you somehow \"touch\" the object by moving it, entering Edit Mode etc.\n\nIt doesn't get fixed by simply affecting something else.\n\nIn the .blend you need to select the object with name \"Plane.001\" and rename it to \"Plane\" then the object on the left stays named as Plane until you somehow affect it.\n[Bug-ViewportDisplayName.blend](Bug-ViewportDisplayName.blend)", "Assert duplicating a collection in a linked scene\nOperating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.31\n\nBroken: version: 3.1.0 Alpha\n\nAssert duplicating a collection in a linked scene\n\nfrom the default startup:\n- 1) `Scene` > `Linked Copy`\n- 2) select the collection `Collection` in the Outliner\n- 3) context menu > `Duplicate Collection` or `Duplicate Linked` (does not matter which)\n\n```\nBLI_assert failed: source/blender/blenkernel/intern/collection.c:184, collection_owner_get(), at '(id->tag & LIB_TAG_NO_MAIN) == 0'\n```\n\nIf the file is saved (and reloaded) before step 3), the above assert does not happen", "Regression: Crash when sculpting shape keys in 3.6.2 release\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 3.5 did not crash, I'm told.\n\n**Description**\nA user in a Discord community shared a file which was crashing for them while in Sculpt mode. I could reproduce the crash, so I simplified the file and found repro steps.\n<video src=\"attachment\" title=\"2023-09-14 00-35-34.mp4\" controls></video>\n\nAs you can see, it takes a few seconds of aggressively dragging the shape key value to get the crash to occur.\nAnother way to get the crash is to just make sculpt brush strokes. I found the shape key slider dragging easier, but I could get it to crash with sculpt strokes too, which was the original complaint from the user.\nMaybe worth noting that, as far as I can tell, if the shape key is not this extreme in its effect, then it seems even harder or impossible to produce the crash.\n\n- File: [Vessa_clean5.blend](attachment)\n- Make sure you're in sculpt mode (I don't think it can crash otherwise)\n- Drag the shape key value around for several seconds, or make a few dozen sculpt strokes\n- Should crash eventually.\n\n", "Avoid creating doubles in UV-Sphere primitive\nCurrently some new mesh operators are creating meshes with duplicate geometry, then removing it. This can cause problems - see: [D6001: Fix #70560: Large cones are created with double vertices (even though the radius is zero)](D6001).\n\n\nIt would be more elegant not to create duplicate geometry to begin with.\n\n- Committed fix for cone 5c8ccad652, while it still creates doubles, they are removed without relying on removing doubles.", "\"Slice String\" field input shows as error, but works (lack of string fields)\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.1\nBroken: version: 4.0.0 Alpha\nWorked: /\n\nA field can be connected to \"Slice String\" node \"Position\" input, and while it shows as red error, it does work. In the attached files, the connection between \"Duplicate Elements\" and \"Slice String\" is shown in red, despite node tree working as expected (tested in Blender 3.5 + current 4.0 daily-build).\n\nAlso note the lack of fields between the \"Slice String\" and string \"Equal\" nodes.\n\nSee attached files.\n\n---\n\nIn the example file, each symbol in a string is an instruction for creating an object at a specified position.\nThe instructions implemented here are \"T(op)\", \"C(enter)\" and \"B(ottom)\".\nI therefore take the input string and create an object for each symbol in the string, then use the geometry index to find the corresponding string symbol to do modifications on the geometry.\n\nFor this to work, \"Slice String\" needs to accept the field input (from \"Duplicate Elements\" field \"Duplicate Index\") so each geometry duplicate gets its own symbol from the input string. This works, but the connection is shown as error in red.\n\nIdeally \"Slice String\" would accept a field for \"Position\" and \"Length\", so arbitrary parts of the string can be extracted for each geometry duplicate. The output of \"Slice String\" should also be a field.\nI'm not sure if there's a way to handle this without an error in the geometry nodes.\n\nOverall, it seems Blender is lacking string-fields, because the \"Equal\" node also defaults to fields for all types except strings. Yet, fields also seem to work here, too?\n\nNot needed here, but the \"String Length\" node also doesn't seem to explicitly support fields.\n\n", "Support separate mesh/curve loose parts looses hooks\nWhen running separate on a mesh with hooks, the newly separated objects hooks are no longer working.\n\nIn this file: [sep_test.blend](sep_test.blend)\n\n- enter editmode\n- press P\n- choose loose parts.\n\nNotice hooks no longer work for 2 of the 3 cubes.\n\nTested with `b72a3146eb56dc021241594525848d41149044cf`", "After swapping the basis shape key to another one, the former basis key still affects the new one\n2.91.0\n\nWhat I try to do: I would like to make a later created shape key the basis one. \nI can do it with moving it to the top, and setting the former basis key's \"Relative To\" setting to this new basis one.\nIt works as expected until I'd like to make further changes in the old basis key (now just a regular shape key)\nIt affects the current basis, where - by definition - there's no \"relative to\" setting, so it shouldn't be affected by anything.\n\nI noticed that it does work as expected if I'm using the \"shape key in edit mode\" option - BUT it only behaves well until I come back to object mode. Then the new basis key instantaneously gets all the modifications I just made on the old basis.\n\nThe steps are below on an image with descriptions, but I attached the blend file too. Just change the shape key called \"starting basis\" and check what happens with the real basis one.\n\n\n[shapekey_error.blend](shapekey_error.blend)\n\nNote: there was one time when I created a shape key pair where this whole thing worked as intended. But out of (literally) 6 tries, only one worked and I couldn't pinpoint what I did differently in that case.", "Visualized face normals are duplicated when Edit Cage is enabled in subdivision modifier (GPU subdivision turned OFF)\n### Simplified Report\n\nHaving Edit Cage on subdivision modifier enabled causes visualized face normals to be duplicated started from the origin. Here is a simplified file with a single face:\n\n\n\n[editCageWrongNormalDisplay.blend](editCageWrongNormalDisplay.blend)\n\nThis issue exists back to 2.83.\n\n### Original Report\n\nOperating system: Ubuntu 22.04 LTS\nGraphics card: Nvidia Quadro M4000\n\nBroken: 2.93.10, 2.83\nWorked: Unknown.\n\n\"Flying\" normals everywhere\n\nI have not discovered a correlation. The alignment of the normal is random, it changes when you exit edit mode and return.\n\n\n\n\n\n\n\n\n\n", "GPencil: Layer transform is duplicated when duplicating object\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.25\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't believe this has ever worked as expectated\n\n\nIf there is a transformation under the object data properties for a layer and the user duplicates the greasepencil object, the duplicated object will offset the greasepencil points by the vector specified in the layer transformation. It will retain the layer transformation from duplication, and will reapply the same transformation.\n\nIf I have a layer transformation of (0, 0.1, 0), the duplicated greasepencil object will have all points displaced by the (0, 0.1,0), but will still have an active layer offset of (0, 0.1, 0) which will cause a total of (0, 0.2, 0) displacement.\n\nThe only way to make the duplicated greasepencil object the same as the original, is to 0 out all the transforms on the duplicated object or go edit mode and correct the offset there. \n\nThis is more of an issue when overriding a library, since I can not 0 out the linked object layers without making them local to the file. The moment I override a linked greasepencil object/collection, the same issues as duplicating appear. \n\n\nIn the test file, duplicate the greasepencil object. Note how the 0.1 Transform Layer will translate 0.1 units on y after each duplication. This will occur if you make a library override of this object in another file.\n[Blender Bug with Layer Transform.blend](Blender_Bug_with_Layer_Transform.blend)\n", "Multi-Object Properties Editing\nIn Blender, we want to make it easier to set values for multiple objects, bones, strips, keys and other items at once. \n\nCurrently you can do this in limited circumstances, but you have to right-click on a value after you've changed it and pick Copy to Selected from the menu or hold Alt while editing values. This not only slow, but also very hidden, and the Alt-key conflicts with Emulate 3 Button Mouse. Lastly, it isn't clear at all to users which values work for multi-editing, and which values don't.\n\nHere's how we would like to solve it:\n\n\n## Selection vs Active\n\nThe concept of ***active*** in Blender means that we only show properties and only affect the active object or item. However, if we want to better support multi-item editing, we must start by making it so the Properties reflects the ***selection*** rather than the ***active*** item, of which there can only be one. Going forward, by default the Properties will be set to reflect the selection instead. This could be controlled in the Properties like so:\n\n{[F8363009](Screenshot_2020-02-22_at_17.34.54.png), size=full}\n*(The search box is added here to reflect how the Properties will be updated when that item is also added, but is a separate feature)*\n\nIf set to ***Active***, the Properties will continue to function as it does today, only showing properties for the active item.\n\n## When there are multiple selected items\n\nWhen the user has selected multiple items, a few things change:\n\nInstead of showing the name of the object at the top, Blender tells the user how many items are selected:\n\n\nIn the list of tabs, only properties sections are shown that are common among the selected items. For example, if you select a text and a mesh object, we don't show Modifier, Mesh or Curve Properties, since these properties only exist on a subset of the selected objects:\n\n\nThis rule also goes for individual panels. Here, both a Sun and Spot light are selected, and we only see properties that are shared between them. A note at the bottom clarifies that you are only seeing the shared subset:\n\n{[F8364914](Screenshot_2020-02-23_at_18.49.33.png), size=full}\n\n## When values differ\nWhen multiple items are selected, Blender will compare values to check if they are the same, or if they are different. If they differ, we change the way properties are displayed, like so:\n\n{[F8363037](Screenshot_2020-02-22_at_17.52.51.png), size=full}\n\n\n\n## Manipulating values across multiple items\n\n\n\nFor simply setting a value to be the same. you would simply type a new value, hit Return, and that value is then propagated to the selection.\n\nFor manipulating numbers and sliders relatively, you can just drag on them (like Alt-dragging today), or type the character '=', so the user can type '= -3' to subtract 3 from the value on all selected items.", "Curve to Mesh node causes other objects to edge split when not shaded smooth\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0 Beta\n\nWhen using a Curve to Mesh node, it causes other objects joined to it to be read with each face as a separate mesh island by Cycles (using the Random per Island socket of the Geometry node in shaders). This only happens while using Flat shading AND the Curve to Mesh is plugging into the first position of the Join Geometry node. In any other order it will not happen.\nAlso happens with more mesh objects as long as the Curve to Mesh object is the first on in the Join node.\n\nThe edges aren't actually split, it just seems to be Cycles that thinks they're individual mesh islands.\n\nAdd a grid node and join it to a curve going through a Curve to Mesh node.\nEnsure the Curve to Mesh is the first connection into the Join Geo node.\nAssign a material to the grid and in the shader, view the Random Per Island output of the Geometry node.\n\n[2021-11-06 18-08-29.mp4](2021-11-06_18-08-29.mp4)\n\n[Mesh Island Bug.blend](Mesh_Island_Bug.blend)", "Outliner doesnt preserve selected or active state when clicking mesh twice (objectmode -> editmode -> objectmode)\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version: 2.81 (sub 3)\nWorked: (optional)\n\nExport selected object export empty file if object have only mesh selected in outliner.\n\nProbably this is more UX bug than exporters problem.\nCreate default object: Cube or Suzanne.\nExpand Object tree and select mesh in outliner. Blender will switch to mesh edit mode.\nClick one more time to mesh in outliner. BLender will switch to Object editing mode.\nViusually Object still looks selected because mesh still highligted but in 3D viewport object is unselected.\nNow try export as OBJ, enable Export Selected only.\nBlender correctly will export empty OBJ file because there is no any object actually selected.\n\n\n\nThis UX bug quite confusing, and i catch it almost every time i need export files.\n" ]

[ "Shape keys missing from `bpy.data.meshes.new_from_object()` even when the mesh Object is not evaluated\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 4.0.0 Alpha\nWorked: 2.79 (sort of, the API was a bit different due to the depsgraph not existing)\n\nCreating a new Mesh from a mesh Object with `bpy.data.meshes.new_from_object` removes the shape keys (or simply does not copy the them in the first place), even when the Object is not evaluated.\n\nThe API in 2.79 is a little different to 2.80+, since there is no depsgraph; you choose with the function arguments whether or not to apply modifiers:\nWhen using `apply_modifiers=True`, the new mesh has no shape keys as expected. Providing an evaluated Object to the function in 2.80+ is equivalent to this.\nWhen using `apply_modifiers=False`, the new mesh retains its shape keys as expected. In my opinion, providing a non-evaluated Object to the function in 2.80+ should be equivalent to this.\n\n2.79 API docs: bpy.types.BlendDataMeshes.html#bpy.types.BlendDataMeshes.new_from_object\nCurrent API docs: bpy.types.BlendDataMeshes.html#bpy.types.BlendDataMeshes.new_from_object\n\nSince the API changed between 2.79 and 2.80, it's not clear whether this is a bug or intended behaviour.\n`Object.to_mesh()` and `BlendDataMeshes.new_from_object()` appear to have identical behaviour in 2.79, though this is again a bit different in 2.80+ because `Object.to_mesh()` now creates a temporary mesh owned by the Object that is not added to `bpy.data.meshes`.\n\n1. Create a mesh Object\n1. Add a shape key (other than the 'Basis')\n1. Enter Edit Mode\n1. Modify the shape key so that it noticeably moves the mesh\n1. Exit Edit Mode\n1. Change the value of the shape key to 1.0\n1. Run in the Python Console:\n 1. `new_mesh = D.meshes.new_from_object(C.object, preserve_all_data_layers=True, depsgraph=C.evaluated_depsgraph_get())`\n 1. `C.object.data = new_mesh`\n1. Observe that the new mesh has no shape keys (and is not evaluated as expected)\n\nAttached are some .blend files created in different Blender versions that have a script and three Objects that go over different cases (has modifiers/no modifiers/has modifiers but they're disabled) of creating meshes with both `BlendDataMeshes.new_from_object` and `Object.to_mesh` as well as making a copy of an evaluated mesh with `Object.copy` in 2.80+.\n\nThe 2.79 version is a bit different due to the different API, but the 2.80+ version in 4.0.0a results in this:\n(the .to_mesh().copy() behaviour of evaluated Objects has been reported separately as 109327)\n\n\n" ]

[ "Blender crash on combining textures (intel)\nOperating system: Windows 10\nGraphics card: Intel HD Graphics 4400\n\nBroken: 2.93.2\nWorked:\n\nWhen I tried to combine 2 textures like this blender is crashing.\n  \n\n[Test.blend](Test.blend)\n[Test.blend1](Test.blend1)\n[system-info.txt](system-info.txt)\n[Test.crash.txt](Test.crash.txt)\n[2021-11-12 09-11-32.mp4](2021-11-12_09-11-32.mp4)\n", "data transfer breaks if more than one remesh is above it in the stack.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nSometimes the `DataTransfer` modifier doesn't work for no apparent reason.\nIn the attached file, putting a `Boolean` modifier after the `Remesh` makes `DataTransfer` work again.\nThis isn't anything to do with differing topology between the hidden and unhidden monkey, otherwise it wouldn't work with only one remesh modifier in the stack.\n\n- Open the file bellow\n- with the monkey selected, turn off the boolean modifier in the stack. \nThe uvs which are being transferred from the hidden monkey will disappear (making the monkey all black).\n[simplified data transfer.blend](simplified_data_transfer.blend)\n\n---\nOriginal file:\n\nOne remesh modifier works fine:\n\n\n\ntwo remesh modifiers break the data transfer:\n\n\n[terminator.blend](terminator.blend)\n", "Multi-Object-Mode: EditMesh Tools\nNote, while these follow menus, duplicates have been removed.\n\n## Remaining\n\n- MESH_OT_select_similar_region ([D3672](D3672))\n- MESH_OT_knife_project (leave aside for now, too complex - see [D3637](D3637))\n- MESH_OT_knife_tool (leave aside for now, too complex - see [D3637](D3637))\n\n\n## Mesh Menu:\n\n- ~~MESH_OT_duplicate_move~~ 1ade071052\n- ~~MESH_OT_extrude_edges_indiv~~ d8f70a26fd\n- ~~MESH_OT_extrude_faces_indiv~~ 07774d4860\n- ~~MESH_OT_extrude_verts_indiv~~ 7c415e6fd7\n- ~~MESH_OT_extrude_edges_move~~ 1d7bdbd273\n- ~~MESH_OT_extrude_vertices_move~~ 1d7bdbd273\n- ~~MESH_OT_delete_loose~~ bfc9d426bb\n- ~~MESH_OT_decimate~~ 5b45d32f3a\n- ~~MESH_OT_dissolve_degenerate~~ (initial comsmit) bfc9d426bb\n- ~~MESH_OT_dissolve_limited~~ 09e14cb5bc\n- ~~MESH_OT_face_make_planar~~ 0e5a4f927a\n- ~~MESH_OT_vert_connect_nonplanar~~ b942106c73\n- ~~MESH_OT_vert_connect_concave~~4043e4b820\n- ~~MESH_OT_fill_holes~~ 69b95b45f4\n- ~~MESH_OT_symmetrize~~ 03a916e5b5\n- ~~MESH_OT_symmetry_snap~~ 7f9768cb80\n- ~~MESH_OT_bisect~~ f9eb2f29fe\n- ~~MESH_OT_sort_elements~~ ffb424c85f\n\n## Snap Menu:\n\n\n- ~~VIEW3D_OT_snap_selected_to_grid~~ 016ba0f38b\n- ~~VIEW3D_OT_snap_selected_to_cursor~~ ec3357e03a\n- ~~VIEW3D_OT_snap_selected_to_active~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_selected~~ ec3357e03a\n- ~~VIEW3D_OT_snap_cursor_to_center~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_grid~~ (no change required)\n- ~~VIEW3D_OT_snap_cursor_to_active~~ (no change required)\n\n\n## Vertex Menu:\n\n- ~~MESH_OT_merge~~ b73c7381cc\n- ~~MESH_OT_remove_doubles~~ 22b2bab702\n- ~~MESH_OT_rip~~ 9d0d7c375e\n- ~~MESH_OT_rip_edge~~ 6539c1fc41\n- ~~MESH_OT_split~~ fc8d903000\n- ~~MESH_OT_separate~~ 5e915baec4\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_vertices_smooth~~ d915aa57f8\n- ~~MESH_OT_vertices_smooth_laplacian~~ 1f30232aa7\n- ~~MESH_OT_blend_from_shape~~ 6ae09dfcad\n- ~~OBJECT_OT_vertex_group_smooth~~ 3dee8b4a12\n- ~~MESH_OT_shape_propagate_to_all~~ 3a43528274\n\n## Edge Menu:\n\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_subdivide~~ (initial patch)\n- ~~MESH_OT_subdivide_edgering~~ 853e55b043\n- ~~MESH_OT_unsubdivide~~ e245f7c09c\n- ~~TRANSFORM_OT_edge_crease~~ (initial patch)\n- ~~MESH_OT_mark_seam~~ 61f0608b4a\n- ~~MESH_OT_mark_sharp~~ 0ac3d5f7db\n- ~~MESH_OT_edge_rotate~~ 66ffbf9b7d\n- ~~MESH_OT_edge_split~~ 207b549d40\n- ~~MESH_OT_bridge_edge_loops~~ eb2226dde2\n- ~~TRANSFORM_OT_edge_slide~~ (wrapper to other operator, working)\n- ~~MESH_OT_loop_multi_select~~ df49155cfb\n- ~~MESH_OT_loop_to_region~~ 8b41999ea0\n- ~~MESH_OT_region_to_loop~~ 56d65719b3\n\n\n## Face Menu:\n\n- ~~MESH_OT_flip_normals~~ 4704f2687a\n- ~~MESH_OT_edge_face_add~~ de2d642c84\n- ~~MESH_OT_fill~~ b726ff4fc4\n- ~~MESH_OT_beautify_fill~~ e42b8c32ab\n- ~~MESH_OT_inset~~ 570455fb83\n- ~~MESH_OT_bevel~~ d9e04cb594\n- ~~MESH_OT_solidify~~ f309c34cfe\n- ~~MESH_OT_intersect~~ dffd37877d\n- ~~MESH_OT_intersect_boolean~~ 46aec45b2a\n- ~~MESH_OT_wireframe~~ a0a78f6da4\n- ~~MESH_OT_poke~~ 3a9669bfff\n- ~~MESH_OT_quads_convert_to_tris~~ (initial patch bfc9d426bb\n- ~~MESH_OT_tris_convert_to_quads~~ (initial patch bfc9d426bb\n- ~~MESH_OT_face_split_by_edges~~ b6a822d726\n- ~~MESH_OT_faces_shade_smooth~~ e4c4e8566f\n- ~~MESH_OT_faces_shade_flat~~ 9fc0c0c3de\n- ~~MESH_OT_uvs_reverse~~ 63951bc987\n- ~~MESH_OT_uvs_rotate~~ faaffc4011\n- ~~MESH_OT_colors_rotate~~ 42c5c20e54\n- ~~MESH_OT_colors_reverse~~ 753be0a2a5\n\n## Mesh Toolbar: (should be added to menu)\n\n- ~~MESH_OT_loopcut~~ e87dd9aa00\n- ~~MESH_OT_convex_hull~~ e1cee0ac71\n- ~~MESH_OT_delete~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_delete_edgeloop~~ 49be803ad6\n- ~~MESH_OT_dissolve_edges~~ 7f5c469716\n- ~~MESH_OT_dissolve_faces~~ 848d9cda0e\n- ~~MESH_OT_dissolve_mode~~ (wrapper of vert/edge/face dissolve)\n- ~~MESH_OT_dissolve_verts~~ 5f59a8bb11\n- ~~MESH_OT_drop_named_image~~ b4d23818c8\n- ~~MESH_OT_dupli_extrude_cursor~~ 68a719f1ea\n- ~~MESH_OT_duplicate~~ 1ade071052\n- ~~MESH_OT_edge_collapse~~ 2349b9777a\n- ~~MESH_OT_edgering_select~~ 7fa77cd31d\n- ~~MESH_OT_edges_select_sharp~~ dd93c80747\n- ~~MESH_OT_extrude_region~~ 1d7bdbd273\n- ~~MESH_OT_extrude_repeat~~ 9a125ca5fe\n- ~~MESH_OT_faces_select_linked_flat~~ 1bb9ccf887\n- ~~MESH_OT_fill_grid~~ 1cbe3b6e03\n- ~~MESH_OT_hide~~ 5d8937e8ba\n- ~~MESH_OT_loop_select~~ 7fa77cd31d\n- ~~MESH_OT_normals_make_consistent~~ 266638d783\n- ~~MESH_OT_offset_edge_loops~~ efd843b51c\n- ~~MESH_OT_reveal~~ f4c1685a16\n- ~~MESH_OT_screw~~ badd88ca02\n- ~~MESH_OT_select_all~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_axis~~ c899f21800\n- ~~MESH_OT_select_face_by_sides~~ 90c9458b2f\n- ~~MESH_OT_select_interior_faces~~ e161c51e7f\n- ~~MESH_OT_select_less~~ b6a7fa1880\n- ~~MESH_OT_select_linked~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_linked_pick~~ (initial commit) bfc9d426bb\n- ~~MESH_OT_select_loose~~ eacb2eb423\n- ~~MESH_OT_select_mirror~~ 3ebe389605\n- ~~MESH_OT_select_mode~~ (initial patch bfc9d426bb)\n- ~~MESH_OT_select_more~~ 2309131b4d\n- ~~MESH_OT_select_non_manifold~~ 4da2aec2bb\n- ~~MESH_OT_select_nth~~ 63c2397171\n- ~~MESH_OT_select_random~~ 847f028b71\n- ~~MESH_OT_select_similar~~ 75b2091d42\n- ~~MESH_OT_select_ungrouped~~ 1d8e6c5cd0\n- ~~MESH_OT_shortest_path_pick~~ c32cc3e43e\n- ~~MESH_OT_shortest_path_select~~ 5a431be629\n- ~~MESH_OT_spin~~ ab8dded330\n- ~~MESH_OT_vert_connect~~ 944054fbb6\n- ~~MESH_OT_vert_connect_path~~ fc7316fb54\n", "Join Palettes\nActually is impossible to Join several Palettes and a operator to do that is needed.", "Edge/Vert Slide fail to properly \"redo\"\nCurrently vertex & edge-slide use the mouse input to calculate which edge to slide, the direction to slide, and the **Even** toggle is set at runtime.\n\nUsing operator redo is not re-running with the same options, so redoing the action fails.\n\nWe could simply disable redo with this operator, however being able to toggle **Correct UV** is important.\n\nAdding this report to merge in duplicates, since there are various reports on this, which all have the same root-cause.", "Multi-User Action keeps moving object after deleting all keyframes until reloading file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\n\nDeleting keys from action with several users doesn't update correctly.\nActions without any keyframes keep changing the object until you revert the file.\n\n1. Add two keyframes to the default cube. (Scale it up and move it to the side)\n2. ALT+D to create a linked copy.\n3. On the linked copy, go to the dopesheet (e.g. action editor)\n4. Delete the keys. Because the action has two users, the keys should be deleted for all users.\n5. Play the animation. You'll see the original copy still moves according to the original keys.\n\n[#88208.blend](T88208.blend)\n\nThank you for taking a look at this! :)\nSeems like a bug to me.\n", "Show warning when saving a .blend file with that has been saved with a newer version before\nThe following scenario is a big difficult with our versioning code:\n1. Save file in new version of Blender.\n2. Load and save the same file in an older version of Blender.\n3. Load the file again in the new version.\n\nNot all our versioning code is idempotent and it can lead to hard to detect bugs when some versioning code runs twice. Showing a warning when saving a .blend file in an older version of Blender might help mitigate that issue a bit.\n\nE.g. #93252.", "Remove unused slots fails with non-mesh objects\nOperating system: all\nGraphics card: all\n\nBroken: 2.83 2.93 3.0daily \n\nwhen object type is Volume or metaball click remove unused slots button.\nWill delete all material slot whether the material been used.\n\nbut if object type is mesh, this action will keep the used \n\n- Open .blend file\n- Material properties tab -> materials specials -> remove unused slots button\n\nTest File:\n[#90338.blend](T90338.blend)", "Merge By Distance Node breaks Motion Blur in Cycles\nOperating system: Win 10 Pro / Version: 10.0.19043 Build 19043\nGraphics card: Nvidia 3080Ti / Driver Ver: 511.79\n\nBroken: 3.1.0 Stable & 3.2 master_f6b73966101d\n\n\n\nGeometry Nodes -> Merge By Distance Node breaks motion blur in Cycles. Works fine in EV. \n\n\n1: Take a mesh, split edges, \n2. Set Position to give faces motion along their normal vector, \n3. Extrude Mesh by faces, \n4. Join Geometry with original faces, \n5. Merge By Distance\n6. Render in cycles with Motion Blur, Mesh Explodes. Now Remove Merge By Distance and render again.\n\n\n[MBTest.blend](MBTest.blend)", "Geometry Node: Order of connection to Join Geometry node affect on shader local space\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: Main\nWorked: Never\n\n\n### Simplified report:\nOrder of connection to Join Geometry node affect on shader local space:\n| | |\n| -- | -- |\n|  |  |\n\n\n\n1. On default cube:\n a. Created shader with noise.\n b. Create geometry node tree.\n2. Create other cube, trhansform that.\n3. In first cube, add `Object Info` node for represent second cube.\n4. Add `Join Geometry` node, connect `Object Info` and `Group Input` nodes in `Join Geometry` node input.\n5. Try to render this object. Switch connection in `Join Geometry` node.\nExpect: Local space of noise used only for one of joined objects and depend of connections order.\n\n\n\n### Original report:\nThe way how normals are rendered are affacted when I use a geometry node with delete and join.\n\n\nSetup:\n\n\n\n\n\n\nOutput without geometry node:\n\n\n\nOutput with geometry node:\n\n\n\nThe normals seems to have a different scale.\n\nThis is the follow up of #102189, which fixed the uv maps. These are working now as expected, seems to be a normal only issue.\n\n", "UV: Modified Edges UV overlay don't show on generated Mesh from Geometry Nodes\nBroken: version: 3.6.0\n\n\"Modified Edges\" UV Option does not work when there is Join Node or primitives is used to generate geometry.\n\nIn setup like this, where we generate UVs in GN, and have \"Modified Edges\" overlay work correctly.\n\n\n\nWhen we generate geometry eg. by using Join Node, or Primitives. Overlay no longer works (even in UV sync mode where all UVs should be shown)\n\n\n\n\nI'm not sure if its desired behavior because eg. some setup do work when we modify and not generate new geometry.\n\n\n--\n\n(that's the overlay if someone is not aware of its existence :p)\n\n\n- Open attached .blend file. (Note that the UV for \"Modified Edges\" is showing as expected)\n- Unmute `Join Geometry` node. (UV for \"Modified Edges\" no longer appears)", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Crash when trying to show a Workspace using a deleted Screen.\nIf a Screen ID is deleted, and one then try to show a Worspace using it, Blender will crash.\n\nSetting to low prio since deleting a Screen ID is not easy to do for end user currently (you'll have to use py console, e.g. `bpy.data.batch_remove(ids=(bpy.data.screens- [x],))`), but still, this is violating general design and expected sane behavior of ID handling.\n\nThink solution should be either:\n* Deleting Screens IDs should be forbidden (not ideal, since it kind of breaks general ID design, but should be doable).\n* Deleting Screens IDs should also delete matching Workspace (not ideal either, there should not be that kind of relationships between IDs, but we already have similar things between objects and obdata...).\n* Or (probably the sanest thing to do) a Workspace should handle gracefully the case where it has no assigned Screen.", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "Cannot Apply Multi Objects\nOperating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 2.92.0\n\nWhen I try to apply scaling, rotation or location to a linked object (Alt+D) I get this error message:\n\"Cannot apply to a multi user: Object \"Cube.001\", Mesh \"Cube\", aborting\"\n \n- Scale the cube \n- Link it with Alt+D,\n- Apply scaling, location or rotation to one of the two cubes.\n\n[Blender 2021-05-30 00-10-18.mp4](Blender_2021-05-30_00-10-18.mp4)" ]

[ "One UV map destroyed when two objects joined\n%%%--- Windows 7 64 ---\n\n\n - 2.69 RC2 and 3 ---\n\n\n - When have two objects with separate UV maps. If you Cntrl J to join the objects. one of the objects looses it's UV map and all the uv verts default on top of each other into the lower left hand corner. The original object's UV Map remains intact. Behaviour does not occur in 2.68---\n\n\n - Open the file, select the head, then select the body and Cntrl J to join them to one object. Go into edit mode and check out the UV map of the body. ---\n\n\n%%%", "Joining two objects with different UVs destroys UVs of one object in some specific, reproducable, cases\nWinXP, nvidia 9800GT\n\nBroken: Blender 2.69 (r60995)\nWorked: Blender 2.69RC1 (r60597)\n\nJoining two objects with different UVs resets the UVs of one or more objects to (0,0) in some specific cases (see below)\nNote that this bug is an attempt to more specifically describe the (uncorrectly rejected) bug T37182\n\n\nI consistently get this bug when I do the following steps:\n- create a cube (or any other mesh primitive)\n- go to edit mode and unwrap the cube (for this bug the kind of unwrapping does not really matter)\n- go back to object mode and duplicate the cube (using shift-d)\n- go to edit mode, and unwrap the second cube in a different way (so it has different uvs)\n- go back to object mode, Shift-select the first cube, and press Ctrl+J\n- in edit mode, the uvs of one of the two cubes appear as expected, the uvs of the other have gone to the lower-left corner of the uv layer. There is still only one UV layer, called \"UVMap\" (as it was in each of the two cubes before joining)\n\nOther cases:\n- same as above, but then with three copies. when joining, only the active object loses its UVs. The uvs of the other two objects are preserved\n- a python script of mine which creates piles of objects by copying them and joining them. (have not been able to create a simplified version to add to this bug)\n\nCases when this behaviour **does not** occur:\n- When I ctrl-Z until just before the join, and then join again, it works as expected (both cubes keep their UV layout). So there is something weird and buggy and inconsistent going on.\n- When I separately create two cubes, unwrap each, and join them\n" ]

[ "Rigid Body Constraints break when copying its empty object\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nCopying a rigid body constraint via CTRL+C / CTRL+V breaks it permanently (you have to remove and re-add the constraint to make it work again).\n\n- Create a simple rigid body constraint setup. You can use this file to start: [bug_rigidbodyconstraints_copy.blend](bug_rigidbodyconstraints_copy.blend)\n- Select all objects\n- CTRL+C to copy\n- CTRL+V to paste\n- Move the new objects a bit to avoid clipping, and play the animation - the active object just falls down\n- Fixed by removing and manually re-creating the constraint on the Empty.001 object\n\nThis does not happen when using SHIFT+D to duplicate.\n\n---\n\nSeems like the dependency graph loses the connections between the constraint and the rigid body objects after copying.\n\nWorking (before copy): \n\nBroken (after copy): ", "Multiresolution sculpting broken after change in base geometry\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14802 Core Profile Context 22.1.2 30.0.14023.3004\n\nBroken: version: 3.1.0 Beta\n\nThe file was created at 3.1.0, but the model in 3.0.1 also has the same problem.\n\nafter deleting edges from a loop and recreating them in a different arrangement, some parts of the model cannot be sculpted with multiresolution on.\n\n\nIn a model with multiresolution, I deleted and recreated some edges of the topology and this broke the sculpt mode of the multiresolution: \n- In the sculpt mode, whenever I was getting close from the model, it simply dissappeared, reapearing after zooming out.\n- When hovering the mouse over some areas of the model, doesn't change the brush gizmo, and I can't sculpt on those areas neither.\n- If there is a area that you can interact/sculpting, by doing it the areas that you were unable to sculpt will become sculptable again.\n- In the areas that you can sculpt, the brush gizmo rotation doesn't match the surface sometimes.\n- baking normals from this multiresolution causes blender to crash\n\nI splited the model in some parts trying to remove the defective part, but this only changed the areas the bug was occuring, and I also tried to re-sort the vertices of the model, which had the same effect\n\nIn this video, the upper part of the leg is sculptable, but the rest of the leg is not \n[2022-02-06 14-33-33.mp4](2022-02-06_14-33-33.mp4)\n\nThis model is from a commission so I had to fair the upper part of it\n[broken multires.blend](broken_multires.blend)\n\n", "Update sculpt mode symmetry options as properties of meshes\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere have been multiple patches to improve the symmetry behavior on painting/sculpt modes:\n- 5502517c3c\n- fa9b05149c2ca3915a4fb2670c87a648d927336c\n\nSome `bpy.data.scenes` properties have been left out of this and still need to be unified as a mesh property instead:\n- `tool_settings.sculpt.lock_x`\n- `tool_settings.sculpt.lock_y`\n- `tool_settings.sculpt.lock_z`\n- `tool_settings.sculpt.use_symmetry_feather`\n- `tool_settings.sculpt.radial_symmetry[0]`\n- `tool_settings.sculpt.radial_symmetry[1]`\n- `tool_settings.sculpt.radial_symmetry[2]`\n- `tool_settings.sculpt.tile_offset[0]`\n- `tool_settings.sculpt.tile_offset[1]`\n- `tool_settings.sculpt.tile_offset[2]`\n- `tool_settings.sculpt.symmetrize_direction`\n\n", "Cycles: Viewport rendering is restarted when selecting bone in a rig with drivers\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: Unsure, possibly never\n\nWhen selecting bones or objects in very simple cases, the Cycles viewport rendering is not interrupted.\nHowever, if the armature has any drivers on it, selecting a bone will restart the viewport rendering.\n\n- File: [re_render_on_bone_select_with_drivers.blend](re_render_on_bone_select_with_drivers.blend)\n- Start viewport rendering.\n- Select one bone or another.\n- Viewport rendering is restarted on every selection.\n\n- Remove the driver from the bone's X location.\n- Issue is gone.", "Crash after undo \"Mask slice to new object\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.92.0\nWorked: This problem happens to me with 2.92, the pc that I use now I formatted it, unfortunately before I used version 2.82\n\nMy problem is that when I use the option \"mask slice to new object\" and then I use ctrl + Z the blender closes !! I formatted the PC a few weeks ago, unfortunately I didn't use version 2.92 before. What I realized is that when I use the \"mask slice to new object\" option and then go to edit mode, I can use control + Z without any problem, that is, it does not close.]\n\nThis happens to me in any file:\n\n1. Sculpture mode.\n2.Use the \"mask\" or \"box mask\" brushes\n3. I paint the mask.\n4.I go to the \"MASK\" menu.\n5. I click on \"mask slice to new object\".\n6. Press CTRL + Z.\n7. Blender closes.\n", "Changing Resolution Preset doesn't allow to Undo\nBroken: 3.6.0\n\nChanging Resolution Preset and then trying to undo doesn't work, like if the action is not registered.\n\n\n- Open Blender\n- Click on the Format panel on the right icon to change preset\n- Select a preset\n- Undo\n\n", "Mirror Paste for pose bones also copies custom properties\nBroken: 2.80, 02581a7ef819\n\nI'm making a rig where I store some custom properties in my face bones which I make use of with a script.\n\nWhen using Ctrl+C to copy a pose, then Ctrl+Shift+V to Mirror-Paste, the values of the custom properties of the copied pose bone(s) get pasted into the opposite bone **if** said opposite bone had custom properties with the same name.\n\n[mirror_paste_pastes_custom_props.blend](mirror_paste_pastes_custom_props.blend)\n- Download attached blend\n- Note that left_bone has a property called \"prop\" and its value is the string \"left bone's info\"\n- Note that right_bone has a property called \"prop\" and its value is the string \"right bone's info\"\n- press Ctrl+C then Ctrl+Shift+V\n- right_bone['prop'] now reads \"left bone's info\".\n\nOne might argue that this is an intended feature, but then the operator should be called \"Copy Pose and Properties\" not \"Copy Pose\"! :P (Realistically, \"Copy Properties\" could be added into the Copy Attributes addon.)\n\n**Workarounds**\nThe bone-specific custom properties can be stored in the edit_bones but this is problematic since edit_bones can only be accessed when the skeleton is in edit mode.\nAlternatively, the custom properties names can be pre/suffixed with the bone's name, which is ofc pretty redundant, but it prevents the bug since the property names will no longer match.", "Bendy Bones Head swing gradually locks up, when Tail handle vector approaches Head-inverted rotation, resulting in Bone swing flipping.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.1.0\n\nIn Bendy Bones, the closer end Handle vector gets to reverse orientation of Bone Head, the more bone head swing locks up, resulting in swing flipping.\nIn theory this could be a feature, if the lock-up would be relative to the bone head roll. Unfortunately direction of the lock is practically unconstrollable. In practice this means flipping of horizontal character necks when looking back, flipping of no-joint bendy knees/elbows etc.\n\nPlay animation, swing flipping is visible on the rightmost sample.\n[bendy-test.blend](bendy-test.blend)", "Armature > Symmetrize doesn't symmetrize Inverse Kinematics constraints correctly\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.93.0\nWorked: non\n\nWhen one Armature > Symmetrize a bone, the IK constraints aren't correctly symmetrized. For example, IK constraint Limit Z (Min -180°, Max 10°) is symmetrized as (Min -180°, Max 10°), while the proper symmetrized result should be (Min -10°, Max 180°). Note that this behavior is inconsistent with how Limit Rotation constraint works. When using Armature > Symmetrize, Limit Rotation Z (Min -180°, Max 10°) is symmetrized as (Min -10°, Max 180°), which in my opinion, is the correct result.\n\n\n1. Create an armature\n2. Create a bone at (1, 0, 0)\n3. Set Bone Properties > Inverse Kinematics > Limit Z (Min -180°, Max 10°)\n4. Enter Edit Mode\n5. Armature > Symmetrize\n\n", "Undoing using undo history in sulpt rendered mode won't work.\nOperating system: Linux-5.8.0-53-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD RAVEN (DRM 3.38.0, 5.8.0-53-generic, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 3.0.0 Alpha\n\nUndoing using undo history in sculpt rendered mode doesn't work. This doesn't seem to be a problem in workbench i.e in solid and wireframe mode, bug only happens in rendered and material preview mode. In both cycles and evee \n\n1) Open default startup file.\n2)Go to sculpt mode\n3)Switch to rendered mode\n4)Make any number of brush strokes\n5)Undo to any step after the 'Original' step for example to the 'Sculpt Mode' step.\n\nIt is important that the undo history menu is used as opposed to ctrl+Z, even if you undo only one step back with the undo history menu. Also note that if you make any edits in edit mode before entering sculpt mode and making edits there and then undo back to edit mode everything looks the way it should but if you then redo to sculpt mode the same problem appears\n\n[#88330.webm](T88330.webm)", "Armature Symmetrize silently does nothing when no bones are selected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 27.20.100.8729\n\nBroken: version: 3.5.0 Alpha\nWorked: never AFAIK\n\nArmature Symmetrize does nothing when there are no bones selected.\n\n1. Open the attached blend file\n2. In the Armature menu, choose Symmetrize.\n3. See nothing happening. This is what this report is about.\n4. Press {key A} to select all bones.\n5. Run the Symmetrize operator again.\n6. See that the armature is now symmetrized. This is what I'd expect to happen when no bones are selected.\n\nExpected behaviour would be that when nothing is selected the armature gets symmetrized as if all bones are selected.\n\n[symmetrize-bugreport.blend](symmetrize-bugreport.blend)", "Fix bad behavior of Armature Join operator\nCurrently, armature 'Join' operator empties its source Armature IDs, while not deleting them. This is both fairly useless, and inconsistent with other 'Join' operations on e.g. Meshes, which do leave source obdata untouched.\n\nIt should instead probably operate on temporary out-of-main copies of the source armatures data, and also leave the original data unchanged.\n\nAlternative option would be to effectively delete the emptied source armature IDs, together with all the objects using them, but this is probably not the desired behavior either.\n\nIssue revealed while investigating #96452 (Armature corrupted after undo), see also [#96452.blend](T96452.blend) for a reproducible case.", "Pinning Bones/Constraint Tabs in Properties Editor doesn't work\nBroken: 2.76 - master (1283c66)\nWorked: Unknown\n\nThe context pinning functionality in the Properties Editor doesn't work for Bones and Constraints. There may be a few others too that I haven't noticed yet, but these are the biggest ones.\n", "GP: Time offset and Armature modifier causes glitches\nOperating system:WINDOWS10\nGraphics card:GTX1060\n\nBroken: 2.93LTS\n\n\n[#89433.blend](T89433.blend)\n\n- Open file\n- Move selected bone to left until it hits constraint, and then a bit randomly\n\nGP object will keep rotating in one direction and can be reset only by changing frame.\nSame happens when scrubbing in negative frame range.\n", "Pose mode, Hotkey conflict between Bend and Bone Settings\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-05-16 05:49, hash: \nThe Bend tool has the same hotkey than calling the Bone Settings menu.\n\nPose mode, Hotkey conflict between Bend and Bone Settings\n\n- Create an armature\n- Enter Pose mode\n- Go to Pose menu, expand Transform menu\n- Have a look at the Bend hotkey and the hotkey for the Bones settings menu.\n\nRelated task. T88342\nResolving this task may make this task here invalid. \n\n\n\n\n\n" ]

[ "Undoing delete bone will not restore constraints.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.12\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n\nUndoing delete bone will not restore constraints.\n\n- Add empty\n- Create armature\n- Add constraint to bone in pose mode - copy rotation with empty as target for example.\n- Check constraint by rotating empty\n- Delete bone with constraint in edit mode.\n- Undo.\n# Check constraint by rotating empty\n\nBone constraint is lost.\n\n[#74486.blend](T74486.blend)" ]

[ "Regression: Crash when sculpting shape keys in 3.6.2 release\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 3.5 did not crash, I'm told.\n\n**Description**\nA user in a Discord community shared a file which was crashing for them while in Sculpt mode. I could reproduce the crash, so I simplified the file and found repro steps.\n<video src=\"attachment\" title=\"2023-09-14 00-35-34.mp4\" controls></video>\n\nAs you can see, it takes a few seconds of aggressively dragging the shape key value to get the crash to occur.\nAnother way to get the crash is to just make sculpt brush strokes. I found the shape key slider dragging easier, but I could get it to crash with sculpt strokes too, which was the original complaint from the user.\nMaybe worth noting that, as far as I can tell, if the shape key is not this extreme in its effect, then it seems even harder or impossible to produce the crash.\n\n- File: [Vessa_clean5.blend](attachment)\n- Make sure you're in sculpt mode (I don't think it can crash otherwise)\n- Drag the shape key value around for several seconds, or make a few dozen sculpt strokes\n- Should crash eventually.\n\n", "Running multiple instances of Cycles HIP ends in segfault\nOperating system: Windows 10\nGraphics card: 2x Radeon W6800 32GB\n\nBroken: 3.0.0, 3788003cdaeb, master, 2021-11-30\nWorked: Never\n\nWhen I have 2 instances of Cycles rendering using HIP at the same time on a particular production scene, one instance will crash with the following error: \n\n\n```\n...\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.57 | Mem:1469.81M, Peak:1469.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Furniture_Roughness.png\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.70 | Mem:1533.81M, Peak:1533.81M | Scene, View Layer | Updating Images | Loading Metal02_nrm.jpg\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.73 | Mem:1569.81M, Peak:1569.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Objects_normal.png\nFra:441 Mem:9030.99M (Peak 9030.99M) | Time:00:21.73 | Mem:1570.69M, Peak:1570.69M | Scene, View Layer | Updating Images | Loading Tires_rough.png\nMalloc returns null: len=37748736 in Cycles Aligned Alloc, total 1149156740\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFED98C853D\nModule : amdhip64.dll\nThread : 00000734\n\n```\nI was unable to reproduce it in a simple scene or any commonly available demo scenes such as classroom or Barbarshop. And unfortunately I cannot share the particular scene that's causing the issue. But the scale of the scene that's crashing should easily fit onto the GPU vram three times.\n\nI've attached the crash report. If more info is needed I will try to create a dummy scene that show the same behavior.\n\n[Anim-A-Garage.crash.txt](Anim-A-Garage.crash.txt)", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "Rendering instability from Blender 3.5 to 36+\nOperating system: macOS 13.4.1\nGraphics card: Apple/AMD W6800X Duo\n\nBroken: 3.6 to 4.0\nWorked: 3.5.1\n\nI get substantial instability when rendering animation sequences in Blender 3.6 and above, compared to 3.5. For example, I've built a large scene with lots of assets and displaced ground material. Today I left Blender 3.5 rendering and have outputted all 250 frames without a single issue using the GPU.\n\nBut previously in 3.6 I get a variety of frames – sometimes 30 or 40, sometime just a single frame – before I have to reboot Blender and start the rendering process again. I've tried all sorts of tricks, like using tiling to render and even switching to CPU-only, but in all cases, the animation process will eventually crash Blender. I thought it might be a VRAM issue, but my dual card has 32GB! My Mac Pro is a standard system with 64GB RAM and no strange or non-Apple additions – it should be rock solid.\n\nI don't have one specific scene to give you, but I've experienced all manner of instability since 3.6 came out – there is obviously a core difference in the app from 3.5 to 3.6+. However, I am really keen to help find the culprit. If you let me know what you need, I can provide crash reports or debug information, just point me in the right direction. Thanks!\n\n", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "Crash when rendering (Apple M2)\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 3.6.2\n\n[Rendering with GPU (metal) works fine without fire simulation, with fire simulation the render crashes, while rendering in the viewport is no problem.]\n\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "Debug build BM_mesh_triangulate() will hang forever if mesh face count is high.\nOperating system: Xubuntu 20.04\nGraphics card: NVidia K5100M\n\n\n**Broken ONLY WITH `Debug` build**: Blender 3.0.0 Alpha (It should have been broken way earlier)\nWorked only with `Release` and 'RelWithDebInfo' build: Blender 3.0.0 Alpha\n\n\nThe call to `BM_mesh_triangulate(bm, quad_method, ngon_method, 4, false, NULL, NULL, NULL)` does not exit on some bigger meshes. Specifically, it seems to have been stuck inside `BM_face_kill(bm, faces_double->link);`.\n\n(if you call it with bmesh `op` and `slot_in/out` arguments it will run properly)\n\n\n1. Open 0_rougue_bucket.blend provided below.\n2. Add -> GPencil -> Scene Line Art **OR** go into sculpt mode and enable dynatopo (where it uses the same triangulation call).\n\nOn my machine the bucket runs fine with subdiv levels 1-2 and above 3 the bug shows. The subdiv value in that file is 3.\n\nNote that the bug is only reproducible in `Debug` build. Seems that function doesn't like meshes that has face count higher than a certain amount...\n\nMy guess would be there's a lot of checks in debug code path in the function, somewhere it reaches a case where the memory pool gets corrupted. It never quits, in the task manager, memory doesn't show any changes at all. (It's way below my 32G system memory so it can't be there being not enough memory).\n\nSince this triangulation call is related to sculpt as well so I'm gonna ask if this happens to @PabloDobarro in debug build...\n\n[0_rouge_bucket.blend](0_rouge_bucket.blend)\n\n", "Metal Backend causes UV editing to glitch out, crash Blender\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 3.5.1, 3.6.3, 4.0 alpha\n\nTrying to do UV editing with the Metal backend causes unexpected UI behavior. Islands will glitch out, disappear, randomly stretch and contort, or Blender will crash entirely. It makes Metal useless for work and requires a switch to OpenGL to have expected performance. This happens on my M1 Air, M1 Pro MacBook Pro, and M1 Max Mac Studio. They all had to be switched back to OpenGL.\n\n<video src=\"attachment\" title=\"error.mov\" controls></video>\n<video src=\"attachment\" title=\"Screen Recording 2023-09-09 at 5.50.49 PM.mov\" controls></video>\n\n- Open the included Blender file with Metal backend\n- Make sure the 3D viewport has either Material Preview or Rendered View enabled.\n- Start UV editing on the `Azumi` object (go to Object Mode > Select the Azumi object > go to UV Editing Workspace)\n- Zoom, pan, scale, rotate...\n\nIt'll happen eventually.\n\nEDIT: This issue seems to stem from having multiple UV Maps on the model somehow. If the additional UV Maps are removed, the issue stops occurring.\n\nEDIT 2: Further digging seems to show that it specifically has to do with the texture atlas expression swapping using the UV Map and Mapping Nodes in the \"Colors.001\" material. Clearing the field in the UV Map node also immediately resolves the issue.\n\nI've attached two screen recordings of some of the behavior, as well as the error log when Blender crashed, and the file I'm working with.\n\nEDIT 3: Uploaded a simple test file with just a cube using the same material setup as my character file. It exhibits the exact same behavior.", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Crash when selecting line art\nOperating system: Linux mint 21. Blender installed using flatpak.\nGraphics card: See attached system_information.txt\n\nBroken: version: 3.5.1\n\nBlender Crashes.\n```\nbacktrace\n\nPython backtrace\nFile \"/app/blender/3.5/scripts/startup/bl_ui/space_view3d.py\", line 704 in draw\nFile \"/app/blender/3.5/scripts/modules/bpy_types.py\", line 903 in draw_ls\n```\n\n```Py\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\nbpy.ops.outliner.item_activate(deselect_all=True) # Operator\n```\nWith attached blend file, in the outliner, select cameras, line-art then try to change the color of the background.\n\n", "Cycles GPU rendering is broken on Apple M1/macOS Ventura\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.3.0 Release Candidate\nWorked: 3.2.2\n\nCycles GPU rendering is broken, CPU rendering works as expected.\n\nCycles - CPU:\n\n\nCycles - GPU Compute:\n\n\n1. Create any scene\n2. Switch Cycles to GPU Compute\n[simple_test.blend](simple_test.blend)\n", "Quick Smoke crash guide February 3, 2023\nOperating system: macOS-13.2-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 3.5.0 Alpha\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\nBake ALL button within Sample 128 from Frame 1 to 220 cause CRASH GUIDE\n\n[image.png](image.png)\n[image.png](image.png)\n[Blender-2023-02-03-113746.ips](Blender-2023-02-03-113746.ips)\nTest File: [3.5.zip](3.5.zip)\n```\nCall Stack: Main thread\n__psynch_cvwait\n_pthread_cond_wait\ntake_gil\nPyEval_RestoreThread\nPyGILState_Ensure\npy_timer_execute\nBLI_timer_execute\nwm_event_do_notifiers\nWM_main\nmain\nstart```", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "Regression: Crashes when uses preview or final render modes\nOperating system: Mac Os Monterey 12.6.1\nGraphics card: AMD Radeon R9 M380 2 GB\n\nBroken: blender 3.6.2\nWorked: Blender 3.4.1\n\nBlender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.\n\nSimply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.\n\n" ]

[ "Crash on exit with Metal backend\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 3.6.0 Beta\nWorked: Perhaps 3.5\n\n\nBlender 3.6 Beta and 4.0 Alpha very often crash on exit. When built with ASAN the following hint is reported:\n\n```\n=================================================================\n==33707==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x0001692a0fb0 at pc 0x0001262961f4 bp 0x00016d44a7b0 sp 0x00016d44a7a8\nREAD of size 8 at 0x0001692a0fb0 thread T0\n #0 0x1262961f0 in blender::gpu::MTLBuffer::~MTLBuffer() mtl_memory.mm:589\n #1 0x12627c438 in blender::gpu::MTLBuffer::~MTLBuffer() mtl_memory.mm:588\n #2 0x12627ba48 in blender::gpu::MTLBufferPool::free() mtl_memory.mm:58\n #3 0x12627b6a4 in blender::gpu::MTLBufferPool::~MTLBufferPool() mtl_memory.mm:50\n #4 0x12627c3dc in blender::gpu::MTLBufferPool::~MTLBufferPool() mtl_memory.mm:49\n #5 0x1261d43c8 in blender::gpu::MTLContext::global_memory_manager_release_ref() mtl_context.hh:907\n #6 0x1261d1490 in blender::gpu::MTLContext::~MTLContext() mtl_context.mm:352\n #7 0x1261bba58 in blender::gpu::MTLContext::~MTLContext() mtl_context.mm:263\n #8 0x1261bbaac in blender::gpu::MTLContext::~MTLContext() mtl_context.mm:263\n #9 0x125cb671c in GPU_context_discard gpu_context.cc:121\n #10 0x109096920 in DRW_opengl_context_destroy draw_manager.c:3238\n #11 0x1076d6ee8 in WM_exit_ex wm_init_exit.cc:673\n #12 0x1076d6008 in WM_exit wm_init_exit.cc:716\n #13 0x1076d5eac in wm_exit_handler(bContext*, wmEvent const*, void*) wm_init_exit.cc:453\n #14 0x107646640 in wm_handler_ui_call(bContext*, wmEventHandler_UI*, wmEvent const*, bool) wm_event_system.cc:817\n #15 0x10763ff20 in wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) wm_event_system.cc:3313\n #16 0x107634ad4 in wm_handlers_do(bContext*, wmEvent*, ListBase*) wm_event_system.cc:3430\n #17 0x107630884 in wm_event_do_handlers wm_event_system.cc:4057\n #18 0x1075c41e0 in WM_main wm.c:632\n #19 0x102b03c70 in main creator.c:584\n #20 0x19fc73f24 (<unknown module>)\n```\n\nIs hard to reproduce reliably with a simple file, but is ver easy to do with more complex files.\n\n\n* Download Mr. Elephant scene from demo-files/\n* Open the file\n* Hit F12\n* CMD-Q and exit.\n\n" ]

[ "Blender crashes in edit mode in wireframe view\nOperating system: Linux Mint 21.1\nGraphics card: geforce gtx 1060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc, type: release\nWorked: 3.5.1\n\nOn the attached file, selecting the bear head and going into edit mode, then switching to wireframe, or switching to edit mode while in wireframe mode, blender crashes and exit.\n\nSelect the bear head, switch to edit mode in wireframe. It crashes. It doesn't happen with a default cube in an empty file. The bear has geometry node hairs attached to it on the fur layer, but the geometry nodes are disabled. It also has an armature.\n\nThe problem also happens on windows10 on the same computer.", "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "Region Overlap does not work on VSE editors\nOperating system:\t\tWindows 7\nGPU:\t\t\t\tRadeon Vega 64\nGPU Software Version:\t20.4.2 (2020.0515.1537.28108)\nCPU:\t\t\t\tIntel Core i7-5960X\n\n**Blender Version(s)**\n*(listed are versions tested)*\n\nWorking:\t\t\t\t`2.79 (sub 00), branch: master, commit date: 2018-03-22 14:10, hash: f4dc9f9d68b, type: Release, build date: 2018-03-22, 09:59 AM`\nBroken:\t\t\t\t` 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release, build date: 2019-07-29, 09:44 AM`\nBroken:\t\t\t\t` 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: 26bd5ebd42e3, type: Release, build date: 2019-11-20, 16:33:00`\nBroken:\t\t\t\t` 2.82 (sub 07), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f, type: Release, build date: 2020-02-13, 01:56:46`\nBroken:\t\t\t\t` 2.83.3 LTS, branch: master, commit date: 2020-07-22 06:01, hash: 353e5bd7493e, type: Release, build date: 2020-07-22, 04:04:56`\nBroken:\t\t\t\t` blender-2.90.0-4f59e4bddcb0-windows64` (BF Build Bot)\nBroken:\t\t\t\t` blender-2.91.0-21fec9513969-windows64` (BF Build Bot)\n\n\n|  |  |\n| -- | -- |\n\n\n[No Overlap.blend](No_Overlap.blend)", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Multiresolution - Crash when Linear Subdivision level is above 1\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.91.0\nWorked: Never? (2.90 and 2.92 dailies seem to crash on this one as well)\nWhen using multiresolution modifier on this part of my model and using linear subdivision level above 1, Blender crashes.\nThis does not happen with other subdivision methods, as shown in video.\nI've also tried to make this mesh manifold, but Blender crashed either way.\n\n\n1. Open attached Blend file\n2. Add multiresolution modifier to a mesh\n3. Press on \"linear\" button twice\n\n[Crash_SampleFile.blend](Crash_SampleFile.blend)\n\n[MultiresCrash0001-2375.mp4](MultiresCrash0001-2375.mp4)\n\n", "Title: CTRL-Z from edit into sculpt mode causes crash if mesh has shape-keys \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.82 (sub 7)\n\nBlender crashes when you CTRL-Z back to sculpt mode when the mesh has shape-keys. This bug happens in 2.83.0 and up, only in the Windows builds. Tested in Linux Mint 19.3 and had no crash there.\n\nAdd basis shape-key on any mesh -> change to sculpt mode -> Change mode to edit -> Undo back -> This causes a crash when it undoes back to sculpt mode.\n", "VSE: Overlap during handle transform fails\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nOverlap during handle transform fails:\n{[F11318256](overlap_fail.gif), size=full}\n\nEx.\n- Import a bunch of images.\n- Select the strip. \n- Separate the images(y)\n- Select all strips.\n- Select the right handle.\n- Hit G to transform.\n- Make the strips overlap in both Overwrite and Extend.\nThe result it that it is shuffling, where it was expected to Overwrite or Extend.\n\n**Slideshow**\nAn example of where the Extend in the same channel would be useful is when making slideshows, where the steps from above and Extend in the end should allow users to batch extend all strips in one go. Combined with this patch: [D10207](D10207) slideshows would be much easier to do. \n\n", "Adding new hook while in Edit mode breaks when trying to undo/redo the operator\nWin7 (32bit)\n\nBroken: 2.78a\n\n\n- Add Path from Curve menu, add new Armature\n- Assign Bone to control point as Hook\n- Blank Hook modifier appears along with real one\n\nScreencast: [screencast0001-0250.mp4](screencast0001-0250.mp4)\n", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "MeshDeformModifier Crashing\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.6.0 Alpha\nWorked: -\n\nAfter binding, with the Dynamic attribute driver value set to 1 in driver editor, it crashed.\n\n1. Add a driver to use_dynamic_bind.\n2. Click Bind\n3. Set the driver value to 1\n\n\n\n\n", "Blender crash in bmesh.to_mesh() while using it to modify weights\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70\n\nBroken: version: 2.82 (sub 1)\nWorked: (optional)\n\nCrash in bmesh.to_mesh() if using it to modify weights in weightpainting while playing animation\n\n*Remove any lights or cameras, keep just one cube in the scene (for the simple script to work).\n*Subdivide it 5 times and apply the modifier.\n*Add the script below to the script editor and run it\n*Go to weight paint mode for the cube\n*Run the animation and try to paint. If you just click the left mouse button it will paint a dot and the script will work, but if you hold and drag, Blender crashes.\n\n\n```\nimport bpy, bmesh\n\n\ndef add_handler():\n # remove existing handlers\n old_handlers = []\n for h in bpy.app.handlers.frame_change_post:\n if \"paint_test\" in str(h):\n old_handlers.append(h)\n for h in old_handlers: bpy.app.handlers.frame_change_post.remove(h)\n # add new handler\n bpy.app.handlers.frame_change_post.append(paint_test)\n\ndef paint_test(scene):\n for ob in scene.objects:\n me = ob.data\n \n print(str(scene.frame_current) + \": Creating Bmesh\")\n bm = bmesh.new()\n bm.from_mesh(me)\n \n group_index = ob.vertex_groups.active_index\n dvert_lay = bm.verts.layers.deform.active\n \n for vert in bm.verts:\n dvert = vert[dvert_lay]\n try: dvert[group_index] -= 0.1\n except: pass \n \n print(str(scene.frame_current) + \": Writing Bmesh\")\n bm.to_mesh(me)\n bm.free()\n \nadd_handler()\n```", "Subdiv hangs blender\n**System Information** DESKTOP-HR30UII\nOperating system:Windows 11 Home Single Language\nGraphics card:2GB NVIDIA GRAPHICS DRIVER\n\n\nBroken: Blender Version 3.5\nWorked: ?\n\nBLENDER 3.5 KEEPS NOT RESPONDING WHILE I USE MODIFIERS \n\nON BLENDER ADD MESH AND ADD MODIFIERS TO SUBDIVISION SURFACE THEN CHANGING THE VALUE OF LEVELS VIEWPORT VALUE ABOVE 4 .THEN ONWARDS BLENDER COMPLETELY STOPS WORKING AND I NEED TO RESTART IT AGAIN\n\n", "Blender crashing when rendering with eevee, not with cycles however.\nOperating system: Linux-5.15.82-1-lts-x86_64-with-glibc2.36 64 Bits\nGraphics card: AMD Radeon RX Vega (vega10, LLVM 14.0.6, DRM 3.42, 5.15.82-1-lts) AMD 4.6 (Core Profile) Mesa 23.0.0-devel (git-e20564cfdb)\n\nBroken: version: 3.3.2\nWorked: None, I've tried 3.3-LTS, 3.4 (both the default version provided through steam and manually selecting 3.4 LTS) and the daily-alpha build (with the daily-alpha build I reset settings all to default as well) All of these versions are the ones provided through Steam.\n\nWhen rendering in eevee some of my meshes completely bug out as if only part of them are rendering (I've looked at my normals and they're all fine) and after that my entire PC crashes, forcing a power cycle. The viewport display, when in rendered mode, looks fine in eevee but after rendering and before my PC crashes the viewport also messes up with my meshes looking bizarre. This issue does not occur in cycles when using CPU or GPU compute and other blender files work fine in eevee / cycles both in the viewport and when rendering. I also tried applying all modifiers despite needing a displacement on my torches to animate them but no luck. My blend file also becomes corrupt sometimes after the crash.\n\nSimply just hitting the render button with my current .blend file when in eevee. Sometimes the render goes through with broken meshes (which then I can close the render window and switch to eevee in my viewport display but my meshes will be all messed up and then my PC will crash, sometimes it crashes before the render output. \n\n\n[Dungeon Course.blend](Dungeon_Course.blend)\n\n[Dungeon Course.blend1](Dungeon_Course.blend1)\n\n[3.4 config.7z](3.4_config.7z)", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n", "GPencil: Blender crash when file open\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.0 Beta\n\nAs soon as I open attached file Blender crashes. Attached also crash log file.\n\n- Open attached file\n- Change radius (say 0.6)\n- Save file\n- reopen it (Crash)\n[#102930.blend](T102930.blend)" ]

[ "VSE Adjustment crashes on blank frame\nMac OSX 10.11.13\nMacBook Pro (Retina, 13-inch, Late 2013)\nIntel Iris 1536 MB\n\nBroken: (2.77)\nWorked: (optional)\n\nIn VSE, Crash when there is an Adjustment Strip and nothing below it\n\nPut an adjustment layer in a blank VSE, give it an adjustment value (like multiply 1.2) and go to a frame where there is nothing beneath it.[vseAdjustmentBug.blend](vseAdjustmentBug.blend)" ]

[ "Crash on toggle bone layer\nOperating system: OpenSUSE Linux, kernel 5.10.7\nGraphics card: intel \n\nBroken: blender-2.92.0-a5637756491c-linux64\n\nBlender crashes when I'm trying to enable bone layer visibility.\n\n1) Open example file: \n[rig-bug3.blend](rig-bug3.blend)\n2) Click on the *second* rig bone layer: \n\nResult: blender crashes with backtrace:\n\n```\n# Blender 2.92.0, Commit date: 2021-02-05 15:23, Hash a5637756491c\nbpy.ops.outliner.item_activate(extend=False, deselect_all=True) # Operator\nbpy.ops.outliner.item_rename() # Operator\nbpy.ops.outliner.orphans_purge(num_deleted=40) # Operator\nDeleted 40 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=10) # Operator\nDeleted 10 data-block(s) # Info\nbpy.ops.outliner.orphans_purge(num_deleted=1) # Operator\nDeleted 1 data-block(s) # Info\nNo orphaned data-blocks to purge # Info\nSaved \"rig-bug3.blend\" # Info\nbpy.context.space_data.context = 'DATA' # Property\nSaved \"rig-bug3.blend\" # Info\n\n# backtrace\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_system_backtrace+0x20) [0x865fd90]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb3a2a]\n/lib64/libc.so.6(+0x3d6c0) [0x7ff5377926c0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_displist_vertbuf_create_pos_and_nor+0x5e) [0x13d443e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_curve_batch_cache_create_requested+0x4ea) [0x13d24ea]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x85bf76b]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(BLI_ghash_free+0x4e) [0x85c00ee]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0x13840e7]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(DRW_draw_render_loop_ex+0x1ac) [0x138649c]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(view3d_main_region_draw+0x8f) [0x1c0442f]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(ED_region_do_draw+0x7e1) [0x17ab221]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(wm_draw_update+0x52e) [0x123c70e]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(WM_main+0x30) [0x123a5a0]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender(main+0x31e) [0xdeb30e]\n/lib64/libc.so.6(__libc_start_main+0xea) [0x7ff53777ce0a]\n/home/z/soft/blender-2.92.0-a5637756491c-linux64/blender() [0xeb03c3]\n\n```", "blender crash itself while importing a dae (collide) file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nBroken: version: 2.82 and all versions in between then and now\nWorked: n/a\n\nHi, I'm using blender version 3.3 on a windows 10 downloaded on steam.\n\nwhen i try to import dae files, blender crashes itself and shuts down\n(this only happens with some dae files, not all and the ones who crash are not to big ).\n\nI tried to search with powershell to find the problem and I got this:\n\nError: EXCEPTION_ACCESS_VIOLATION\n[bgr_darryls_ship_ground.dae](bgr_darryls_ship_ground.dae)\n\n```\nThe gh->hashfp function pointer is NULL (hasn't been initialized yet)\n\nblender.exe!ghash_keyhash(const GHash * gh, const void * key) Line 133\tC\nblender.exe!ghash_lookup_entry(const GHash * gh, const void * key) Line 411\tC\nblender.exe!BLI_ghash_lookup(const GHash * gh, const void * key) Line 736\tC\nblender.exe!BKE_armature_find_bone_name(bArmature * arm, const unsigned char * name) Line 601\tC\nblender.exe!ArmatureImporter::create_armature_bones(Main * bmain, std::vector<Object *,std::allocator<Object *>> & arm_objs) Line 478\tC++\nblender.exe!ArmatureImporter::make_armatures(bContext * C, std::vector<Object *,std::allocator<Object *>> & objects_to_scale) Line 826\tC++\nblender.exe!DocumentImporter::finish() Line 228\tC++\n[External Code]\t\nblender.exe!DocumentImporter::import() Line 127\tC++\n```\n", "crash when changing viewport shading to wireframe mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14760 Core Profile Context 21.2.3 27.20.14535.3005\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-04-23 20:25, hash: 17fca62fff9b, type: Release\nBroken: 2.81\nWorked: 2.80\n\n\nif you have a high poly mesh and try change the shading mode to wireframe. depending on the model it constantly crashes.\n\n\nI noticed this trying to make a retopo of a character. I tried to check what was causing de crash by deleting each object and testing the wireframe. \n\nI deleted everything but the main body mesh, without any uv map, vertex color or any other thing that could make it heavier, and also I tried reseting factory settings.\n\nI would send the file but its 200mb, the main mesh has about 4million vertices.\n\n\nthe crash doesn't happen when changing to eevee or solid view, it only happens when changing to wireframe.\n\nImportant note: if you DON'T move the camera after opening the file before changing to wireframe it doesn't crash even if you go to solid and wireframe back and forth as shown in the video bellow \n[2021-05-01 14-18-16.mp4](2021-05-01_14-18-16.mp4)\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[untitled.blend](untitled.blend)\n- open the file above\n- rotate it about 180degrees\n- activate wireframe", "Blender crashes as soon as an image texture is plugged in the material BSDF node\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 1080 Ti\nSee attached log for more detail\n\nBroken: 3.5.1, but also 4.0.0 Alpha, did not try intermediate versions\nWorked: ??? The earliest available build, 2.93.18, also causes the same crash\n\nThe second any kind of image texture is plugged in a material, Blender crashes without any warning. Occurs when creating a new image texture, when plugging an existing file, or even when trying to plug a UV grid for unwraping purposes\n\n**Similar tickets**\n#76193\n#76377\n\n1. Start Blender.\n2. Create new default file.\n3. Select the default cube.\n4. Switch to Shading workspace.\n5. Add Image Texture node.\n6. Create new image or select an existing one.\n7. Plug Color output to the Base Color input of the Principled BSDF node.\n8. Watch Blender shut down.", "Blender Crash MacOS Arm M1 - Wireframe - Memory issue\nOperating system: macOS-12.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Pro Apple 4.1 Metal - 76.3\n\nBroken: version: 3.2.0 Alpha\nBroken: version: 3.1.2\nWorked: Any version using linux/windows\nWorked: version: 3.1.2 on Intel base Mac\n\nBlender crashes with a viewport in wireframe mode or tries to allocate ~100 GB memory when .\n\nBase: default blend file.\n\n1. Go to \"Geometry Node\" tab\n2. Create new node setup\n3. Add Mesh line node\n4. Set count to something big like 256^3 (this was my test case)\n5. Switch the viewport to wireframe\n6. Crash\n\nNote: Slower increase can lead to huge memory consumption by blender:\n\n\nExample node setup:\n\n\nSwitch to wireframe:\n\n\n", "Rigify crash in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315\n\nBroken: version: 3.5.0\n\nWhen I orbit the view in edit mode, the program crashes after a few seconds. Especially around the hands and face.\nIn version 3.1.2 it does not happen to me, it does happen in 3.3.0 and 3.5.\nTried to clean and reinstall, update drivers, save file in 3.1.2 and open in new versions, but the bug persists.\n\nSorry for bothering you, I hope you have a good day.-\n\n\ncreate human metarig, go to edit mode, orbit the view. Orbiting around hands seems to crash faster.\n\n", "Render crash\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon RX 560X ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.1.220810\n+ AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx\n\nBroken: version: 3.3.0 Beta\nWorked: 3.2.2\n\nBlender every time crash when switch to render mode in viewport.\nRender set to Cycles with GPU Compute.\nVega 8 selected as device in preferences.\nIf I select RX 560X in preferences, GPU Compute is greyed in Render preferences (also interesting why).\n\nAny project with simple cube crashed.[test11.crash.txt](test11.crash.txt)\n", "Error with paint curves and drawing with mouse buttons\n[system-info.txt](system-info.txt)\n\nBroken: blender-2.80.0-git.cc600de6695a-windows64 (and probably above)\n\nWhen using paint curves, they don't draw upon clicking the right mouse button if specified as the button to select with in the preferences. But they do if you set the mouse button to select with to be the left one. So if you have selected the LMB in the preferences then you can draw the paint curve (I don't mean creating the curve) with the LMB, but if you have chosen it to be the RMB then it doesn't work when pressing the RMB, neither does the LMB. (Also, the UI button for drawing the curve in the stroke panel does not work. But you can draw it when you type draw curve in the search panel)\n \nGo to the *Sculpting* screen layout and create a paint curve on an object (if it helps, I used the the normal *Draw* brush). Open the *Stroke* panel in the *Properties Editor* and set the *Stroke Method* to *Curve*. If you have chosen the left mouse button in the *Keymap* section in the *Blender Preferences* under *Select With:* , then everything works fine. You can draw the paint curve on the object by doing a left click after creating it by doing multiple Ctrl-RMB clicks. But if you now set the mouse button with which you want to select to *Right*, then you can create the paint curve with Ctrl-LMB clicks, but when you try to sculpt/draw the paint curve with either the left mouse button or the right mouse button, none of them work. (And again, if you try to draw the paint curve with the *Draw Curve* UI button in the *Stroke* panel, it will also do nothing but turn blue because you clicked on it...)", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Crash undoing in certain scenario (disabling Global Undo)\nOperating system: Linux-5.10.12-200.fc33.x86_64-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.82a\n\nCrash undoing in certain scenario (disabling Global Undo)\n\nFrom the default startup file (order of operations is important here):\n- move the cube (could be any objectmode operator) {key G Z 3}\n- disable `Global Undo` in Preferences {key F4} > `Preferences` > `System` > uncheck `Global Undo`\n- add an armature {key Shift A} > `Armature`\n- go to pose mode\n- select bone\n- move bone\n- Undo {key Ctrl Z}\n - > crash\n\n```\n1 BKE_scene_object_base_flag_sync_from_base scene.c 2914 0x35b41a9 \n2 BKE_scene_set_background scene.c 2125 0x35b2957 \n3 setup_app_data blendfile.c 386 0x4b63950 \n4 setup_app_blend_file_data blendfile.c 416 0x4b639e4 \n5 BKE_blendfile_read_from_memfile blendfile.c 524 0x4b63e38 \n6 BKE_memfile_undo_decode blender_undo.c 88 0x4b62cc0 \n7 memfile_undosys_step_decode memfile_undo.c 193 0x486eb47 \n8 undosys_step_decode undo_system.c 214 0x4bb97ec \n9 BKE_undosys_step_load_data_ex undo_system.c 809 0x4bbb2df \n10 BKE_undosys_step_undo_with_data_ex undo_system.c 870 0x4bbb4a4 \n11 BKE_undosys_step_undo_with_data undo_system.c 880 0x4bbb4d3 \n12 BKE_undosys_step_undo undo_system.c 889 0x4bbb511 \n13 ed_undo_step_direction ed_undo.c 278 0x486c907 \n14 ed_undo_exec ed_undo.c 489 0x486d214 \n15 wm_operator_invoke wm_event_system.c 1332 0x3a17b06 \n16 wm_handler_operator_call wm_event_system.c 2161 0x3a198e3 \n17 wm_handlers_do_keymap_with_keymap_handler wm_event_system.c 2486 0x3a1a617 \n18 wm_handlers_do_intern wm_event_system.c 2782 0x3a1b591 \n19 wm_handlers_do wm_event_system.c 2914 0x3a1bafc \n20 wm_event_do_handlers wm_event_system.c 3445 0x3a1d2a3 \n```\n```\n \n```\n\n\n", "Application templates crashes if the startup.blend of the application template contains scene named \"Asset\"\nOperating system: Windows-10-10.0.22621-SP0'\nGraphics card: NVIDIA GeForce RTX 2070 Super with Max-Q Design/PCIe/SSE2\n\nBroken: 3.5.1 2023-04-24 18:00 e1ccd9d4a1d3\nWorked: Never\n\nApplication templates that contain certain pattern in startup.blend lead to Blender to crash.\nApparently occurs when the scene is created with the name \"Asset\" and used as a application template.\n\n- Download attached [MCE.zip](attachment) file\n- Install the attached application template file (`Blender` menu > `Install Application Template...`).\n- Load it (choose the new \"MCE\" option in `File` > `New`).\n\nBlender crashes.\n\nAttached also the `blender.crash.txt` and another template.\n\n[MCE.zip](attachment)", "Annotation tool: wrong undo order and different in different modes\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: 2.93.2\nBroken: 3.0.0 Alpha, `c1f5ac7cfe`, 2021-07-25 18:36\nBroken: 2.83.17\nWorked: never\n\n\n| Object mode | works correct, as expected. Each undo action undoes 1 stroke |\n| -- | -- |\n| Weight paint | works properly |\n| Vertex paint | works properly most of the time, sometimes as Texture paint |\n| Texture paint | do not undoes each stroke but after number of {key Ctrl+Z} (n=strokes) undoes all strokes simultaneously or disables em at n=strokes+1 and undo previous action (mode switch in my case) |\n| Edit mode | same as Texture paint |\n| Sculpt mode | Undoes strokes one by one, but on the last stroke it do not react to {key Ctrl+Z} once, and then on the secon disables stroke and previous action (mode change) |\n\n**Steps to Reproduce**\n- Open default scene\n- Switch to Edit or texture paint mode\n- Draw 4 strokes with annotation tool\n- Undo 4 times (nothing happens to any stroke)\n- Undo again: Clears all strokes\n[2021-08-15_15-46-27.mp4](2021-08-15_15-46-27.mp4)\n\n", "Blender Crashing When Painting Stroke into a \"Moving Animated Character\" (heap-use-after-free)\nBroken: 4.0 alpha\nBroken: version: 2.79 - 2.82 (sub 7)\nWorked: Never\n\nI have this experiment of making LIVE talking head, via OSC. And I noticed that if I tried painting a stroke on a talking moving animated head, it will crash. Even with timeline not running.\n\nI got a video (Might need iPhone X with MOM addon to test this....) :\njhHdG6ZXFDU\n\n- Open attached file\n- Run animation\n- Paint over the animated object\n[paint_animated_shapekey_bug.blend](paint_animated_shapekey_bug.blend)\n\n\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```" ]

[ "Crash when alt + LMB click in weight paint mode\nWin10 RX460\n\nBlender 2.80 alpha2 32dca36afb1\n\nCrash when alt + LMB click in weight paint mode\n\n1. Enter weight paint mode\n2. Click LMB with alt" ]

[ "Blender 3.0.0 breaks compatibility of rigs with the previous version\nOperating system: Windows 11 Pro 21H2\nGraphics card: Nvidia RTX 3070\n\nBroken: 3.0.0\nWorked: 2.93.6\nBlender 3.0.0 breaks compatibility of rigs with the previous version.\n\n1. Open Agent 327 shot 10_03_B-agent_dodges animation file (10_03_B.anim.blend)\n2. Observe that the rigs are completely broken\n\n\n", "Blender 3.6.3 SegFault Crash at startup on MacOS Ventura 13.5.2\nOperating system: MacOS Ventura 13.5.2 (22G91)\nGraphics card: Intel Iris Plus Graphics 650 1536 Mo\n\nBroken: 3.6.3 (3.6.3 2023-09-21)\nWorked: None tried on this machine\n\nCrash on startup with `Segmentation fault: 11`\n\nEither:\n- Double-click on Blender application icon\nOr:\n- command line : `/Applications/Blender.app/Contents/MacOS/Blender` with or without option `--gpu-backend`\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x109d2903d (anonymous namespace)::Local::Local() + 29\n1 Blender \t 0x109d28fe9 memory_usage_init + 25\n2 Blender \t 0x109d26f09 MEM_init_memleak_detection + 9\n3 Blender \t 0x101e098c3 main + 227\n4 dyld \t 0x7ff815a5241f start + 1903\n```", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Blender crash when selecting and moving vertex using API\nOperating system: Linux Mint 20 Ulyana\nGraphics card: NVIDIA GeForce RTX 2060 Super\n\nBroken: 2.91.2, 5be9ef417703, master, 2021-01-19\n\n\nBlender crashes when opening a new instance pasting the below script in a new document in the \"Scripting\" editor and clicking play:\n\n```\n\nimport bpy\n\ncontext = bpy.context\n\n# Assume default cube exists and select it\nobj = bpy.data.objects[\"Cube\"]\nobj.select_set(state=True)\ncontext.view_layer.objects.active = obj\n\n# Select a vertex and move it\nobj = bpy.context.active_object\nobj.data.vertices[0].select = True\nbpy.ops.object.mode_set(mode = 'EDIT')\nbpy.ops.transform.translate('INVOKE_DEFAULT',\n constraint_axis=(True, True, False),\n orient_type='GLOBAL',\n release_confirm=True)\nbpy.ops.object.mode_set(mode='OBJECT')\n```\n", "Crash on forcing laptop to sleep when rendering animation\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\nCpu AMD Ryzen 7 4800h\n\nBroken: version: 3.3.1\nWorked: Maybe never? (able to reproduce in 2.83)\n\nblender crash when I wake up my laptop , I lost my unsaved file\n\n- Open .blend file\n- Start render animation\n- Force laptop to sleep {nav Start -> Power -> Sleep}\n[test1.blend](test1.blend)\n[test1.crash.txt](test1.crash.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n", "Crash to desktop when trying to bake (Blender 3.3.6)\nOperating system: Windows 11 (64-bit)\nGraphics card: NVIDIA RTX A2000\n\nBroken: (3.3.5, 3.3.6, blender-3.3.6-stable+v33.948f8298b982-windows.amd64-release)\nWorking (2.91.2)\n\nWhen trying to bake scene produced in script, Blender crashed.\n\nOpen attached blend file and press Bake.", "Blender crashes after GPU spike (Specially when we have a character with Rigify)\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: 3.4.1\nWorked: 3.3\n\nEvery time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve.\n\n- Open a blender file\n- Import a character using rigfy with Linked Library\n- Library override\n- Turn Eeve on\n- Start working\n- Eventually, blender will crash.\n\nI noticed that if I don't import a character with rigfy, it doesn't have the GPU spike\n[Christmas.crash.txt](Christmas.crash.txt)\n[KalyAndAkrasiel 3.5.crash.txt](KalyAndAkrasiel_3.5.crash.txt)", "Some meshes causing crash on file opening since Blender 3.4\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.4.0\nWorked: 3.3.2\n\nOpening some files in Blender 3.4 was causing a crash. The source was narrowed down to a mesh that might be corrupt in some way, and upon entering Edit Mode crashes 3.3 too, however 3.2 did not crash on opening the file, thus at least allowing to delete such meshes.\n\n[Amphitheater-cedar3.blend](Amphitheater-cedar3.blend)\nOpen the file -> Crash", "Blender crashes when using temp_override on 'UV' area with transform.translate, transform.resize\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.3.5\nBroken: version: 3.4.1\nBroken: version: 3.5.0\nWorked: none\n\nWhen executing `transform.resize` or `transform.translate` with `context.temp_override(area=uv_area)` Blender crashes. This happens when the area.ui_type is UV, with VIEW_3D is works fine.\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF72DEF3C80\nModule : blender.exe\nThread : 000009dc\n```\nthe complete crash file is attached\n\n1. create a new Text and paste the below code into the text (the attached file issue.blend can also be used)\n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nwith context.temp_override(area=area):\n bpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n bpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n2. run this text, Blender will now crash\n\n**Note**: not using `temp_override()` and executing these operators in the current context with the ui_type set to UV works fine. Like this: \n```py\nimport bpy \ncontext = bpy.context\narea = context.area\narea.ui_type = \"UV\"\nbpy.ops.transform.resize(value=(0.5, 0.5, 0.5), orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\nbpy.ops.transform.translate(value=(0.25, -0.25, 0), orient_axis_ortho='X', orient_type='GLOBAL', orient_matrix=((1, 0, 0), (0, 1, 0), (0, 0, 1)), orient_matrix_type='GLOBAL', mirror=False, use_proportional_edit=False, proportional_edit_falloff='SMOOTH', proportional_size=1, use_proportional_connected=False, use_proportional_projected=False, snap=False, snap_elements={'INCREMENT'}, use_snap_project=False, snap_target='CLOSEST', use_snap_self=True, use_snap_edit=True, use_snap_nonedit=True, use_snap_selectable=False)\n```\n\n", "Mantaflow: charge force field crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen I try to add the charge force field and play the simulation the blender 3.0.0 Alpha crashes\n\nMake a simple water simulation and add the charge force field\n**Crash seems to happen only in release builds**\n\n[#92110.blend](T92110.blend)", "Wintab rarely gets into a bad state and prevents Blender startup\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.40\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nFor a few months now, I have been getting a fairly rare, but reoccurring issue (maybe once a week on average) where Wintab gets into some erroneous state and prevents Blender from starting if the Tablet API setting of the Input preferences is set to `Wintab` or `Automatic`.\nWhen Wintab gets into this erroneous state and Blender is already open, Blender will crash if I attempt to open the User Preferences. I'm not sure what else might cause a crash when Blender is already open.\n\nBy adding extra logging to a custom build of Blender, I've determined that the crash when starting Blender occurs when calling the `open` (`WTOpenA`) function: GHOST_Wintab.cc#L85\n\nMy drawing tablet's software also reports an exception in `WTOpen`, the value of which appears to equal 0xC0000005 which I think indicates a `STATUS_ACCESS_VIOLATION` according to 596a1078-e883-4972-9bbc-49e60bebca55.\n\n\nIn the drawing tablet's software, this exception only occurs if I actually connect the tablet to my PC, whereas Blender crashes even when the tablet is not connected.\n\nCurrently, if I don't actually need my tablet, I'm working around the issue by starting Blender headless, changing the Tablet API setting to Windows Ink, and then starting Blender normally.\n\nI have already tried updating the drivers for my tablet to the newest version and it made no difference.\n\nIf I start Blender with `--debug-wintab`, all that's printed is:\n```\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release> .\\blender.exe --debug-wintab\nRead prefs: \"C:\\Users\\Thomas\\AppData\\Roaming\\Blender Foundation\\Blender\\4.0\\config\\userpref.blend\"\nLoading Wintab for window 00000000000910C4\nPS D:\\Downloads\\temp\\blender-4.0.0-alpha+main.dd9a92785acc-windows.amd64-release>\n```\n\nEvery version of Blender I've tried between 2.79 and 4.0.0a crashes unless I have the Tablet API set to `Windows Ink`.\n\nI don't know the specifics of how Wintab is handled, but could it be possible to either catch the exception in `WTOpen` and allow Blender to continue loading, or to check for a connected tablet before attempting to call `WTOpen`, similar to what my tablet's software appears to be doing?\n\nUnfortunately, Wintab getting into this erroneous state where it crashes in `WTOpen` occurs too rarely for me to figure out how to reproduce it and I'm not even sure if it's Blender that is causing it to get into this state in the first place.\n\n", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Blender randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\n", "Crash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming)\nOperating system: Win 10\nGraphics card: Nvidia Quadro M5000 \n\nBroken: 3.4.1\nWorked: 3.4.1\n\nCrash upon renaming collection or clicking on Blenderkit after creating said collection (without renaming). \n\n- Download file through the link from Google Drive attached (I leave the file as it is since I don't know what caused the problem)\n- Click in the collection \"Möblierung\",\n- create some new collection in it,\n- rename the new collection (with double click)\n- hit enter - crash\n\nOr create the collection, don't rename it and then click something in the interface (Blenderkit \"eye\" symbol in my case).\n\nReload didn't do anything, just kept crashing.\n\nLoaded a recent autosave, seems to work. Already hat to kill startup file and all settings yesterday, got permanent exception access violation crashes upon file load, after enabling some addon (TrueAssets) it worked.\n\nLink to the blend: view?usp=sharing\n\n", "Access violation in `vk_icdNegotiateLoaderICDInterfaceVersion` when putting computer to sleep.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.3 Release Candidate\nWorked: (3.6.2)\n\naccess violation when putting computer to sleep. crash log is created immediately after clicking sleep.\n\n\n1. launch blender.\n2. open a file\n3. save it\n4. put the computer to sleep\n\nEdited steps because it just happened when blender was launched normally. Wasn't saved this time, and was a different blend file." ]

[ "Blender 2.93 TLS and 3.0 crashes on basic operations\n{[F12798709](blender_unsuported_graphics_driver.png)}Operating system: Windows 10 x64 Home\nGraphics card: NVIDIA GeForce GTX 960M\n\nBroken: TLS 2.93, 3.0\nWorked: none\n\nThis Bugreport is **related to #94748**\nSince Version 3.0 crashes I installed TLS 2.93\nThis version also crashes. I dont load any file just make some simple navigation operations whith the default cube (move, scale, rotate) and click some menues (without rendering).\nI could not find a file blender.crash.txt on the whole system.\nWhen I restart Blender I get the well know error about an unsupported driver (attached).\nThereseems to be a leftover after the crash which gets cleared on a reoot.\n**After the reboot I can start Blender again without the error message attached.**\nI use the newest NVIDIA driver but dont know if the GPU is really used.\n**=> Can I supply any additional information?**\n\nJust start Blender and navigate around with the default cube." ]

[ "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "Dae parsing issue\nOperating system:Windows 10\nGraphics card: NVidia gforce GTX660\n\n 2.79\n\n\nIt is a common error, when trying to upload an object to Second-life or Opensim, to be unable to upload a model,created in Blender, due to a \"DAE parsing issue\"\nThis object is one that is effected.\n\n[lowpol.blend](lowpol.blend)\nExport as .DAE file and upload to Opensim or Second-life", "CUDA problem Error: Invalid value in cuMemcpy2DUnaligned_v2(&param)\ndoes anybody know what this error mean (blender 3.5, 3.6, 4.0 win 11):\n\n*Error:Report:\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\nInvalid value in cuMemcpy2DUnaligned_v2(&param) (C:\\Users\\blender git blender-v350 blender.git\\intern\\cycles\\device\\cuda\\device_impl.cpp:823)\n\n\n\nWe tried two rtx 4070ti video cards and this error came up when we were about to render. If I disable one of the two, the render runs fine, but if I enable both, the render freezes. I see that it starts using both, but it still gives an error.\n\nThanks\n\n", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "Hitting 'Escape' while editing a shortcut enters that key on Windows, while on linux it cancels edition\nWindows 7 64bits, nvidia gt540m CUDA 2GB, Intel i7 2GHz, 8GB ram\n\nBroken: 2.75 c6b042b\n\n\nWhen i do a search of a shortcut, and then if i want to assign a new value and then cancel, the tab disappear.\n\nBlender User Preferences > Input > Search by key-binding \"Ctrl Tab\" > Show key map and property of any tab > Clic on \"type of event\" to change the value > Press Esc to cancel > the tab disappear.\n", "Crash playing animation with rigid body\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.83.1\n\nAfter opening a blend file (ver BLENDER-v280RENDH). The frame starts at 25 upon opening it. I changed the frame to 0. I pressed space to play then the application closes.\n\n[Whiskers Away.blend](Whiskers_Away.blend) \n- Open file\n- Rewind to frame 1 {key Shift Left}\n- Seek to frame 0 {key Left}\n- Play animation\n\nCrash doesn't happen every time. Redo all steps in such case. There is about 30% probability to reproduce successfully.", "Crash at the end of preview generation for a deleted datablock\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: -\n\nBlender crashes if you trigger the generation of a preview for a data block and then delete the data block itself. Obviously, the preview data is generated, but since the datablock itself no longer exists, I get an `EXCEPTION_ACCESS_VIOLATION` and a crash.\n\n\nRun simple script in attached *.blend file.\n\n", "Splash Screen: \"Updated Preferences\" Infobox\nFor Blender 4.0 there will be various default keymap updates (#105298) that users should be aware of when loading their 3.6 preferences.\nThis task will become necessary once those patches are merged.\n\nThe idea is to add a popup to make users aware and point them towards resources to inform themselves. This will avoid frustration and many invalid bug reports.\n\n### Mockups\n\nThe addition of an info icon to the operator button that loads the previous preferences (As an indication that this will open a popup with more info).\n\n\n\nA possible layout for the main popup.\nThis info might be very important for some users, so the popup can only be closed with an explicit button press.\n\nThis also includes a an operator button \"Read more...\" that links to the relevant release notes page without closing the popup itself. An added border would make this more recognisable as a button.\n\n\n\nThis popup could then be used for future releases and other important changes (only if absolutely needed).\n\n", "Blender Instantly Crashes When Rendering Cycles Or Clicking Wrong Setting\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nCPU: 12th Gen Intel(R) Core(TM) i7-12700KF, 3600 Mhz, 12 Core(s), 20 Logical Processor(s)\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.9.1.230821\n\nBroken: version: 3.6.2\n\nWhenever Blender attempts to render in cycles mode it exits immediately. It doesn't try for a few seconds, there's no loading, just click and instantly the process dies. This happens whether Preferences>System>Cycles Render Devices is set to \"None\", \"HIP\" with my GPU selected, or \"HIP\" with my CPU selected. Regardless of the cycles render device setting when I turn on viewport shading it works as it defaults to Eevee. However, if I try to change it to cycles, the moment I click cycles Blender crashes.\n\nThis same instant crash happens when I try to click OptiX or CUDA in Preferences>System>Cycles Render Devices instead on None or HIP.\n\n\n- Start Blender with a default project\n- Press Z then 8 to go into rendering mode\n- On the sidebar click render properties\n- Click the dropdown to change render engine\n- Click Cycles\n- Should see it crash instantly\n\nTo see the settings crash\n- Start Blender with a default project\n- Navigate to Edit>Preferences>System>Cycles Render Devices\n- Click between None, HIP, and OneAPI without issue\n- Click CUDA or OptiX and see the instant crash\n\n", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Blender 2.91 alpha - Debug menu, instant crash\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.55\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90.1\n\nShader compilation is causing an error when the debug menu is invoked on a blank scene or working scene.\n\nOpen the .blend attached file, press F3>search: Debug. Type 22 (eevee GPU speed benchmarking verbose),\nBlender will crash immediately. The same is true on a blank new scene in the general application template.\n\nFile to test: \n44cb6eb461af31ad1209dedb738d76c0.blend\n\n", "Use draw manager for clip editor drawing\nCould be stalled to 2.93 as there isn't an real issue here as far as we are aware of. The compositor issues are more tangable.", "stack_overflow exception while rendering with viewport render on\nOperating system: win10\nGraphics card: 2070super\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: 2.83.4, 2.91 6fe609d4c3\n\n\nwhen pressing f12 in render mode, blender crashes,\nwhen pressing render in solid mode, blender doesnt crash\n\n[blender_debug_output.txt](blender_debug_output.txt)\n```\nError : EXCEPTION_STACK_OVERFLOW\nAddress : 0x00007FFF42963FDB\nModule : C:\\Windows\\system32\\DriverStore\\FileRepository\\nv_dispsi.inf_amd64_6af46268c19e4980\\nvcuda64.dll\n```\n[2.blend](2.blend) \n1. switch to render mode\n2. press f12 & watch task manager.\n3. blender will close", "project turning purple automatically after closing and opening later+zoom in/out buttons not working properly.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.79\n\nBroken: version: 3.6.2\n\n\n\n", "For ID blocks, move + and x buttons into popover\nWith our ID blocks in the top right of the window, the little + and x icons make the Blender UI overly busy and complex. There's also the problem that, at least on Windows and Linux, the close button is in the top right corner of the display, creating this clumsy configuration of two X's. \n\n{[F5673488](Screenshot_2018-11-22_at_01.50.52.png), size=full}\n\nWe could change these ID blocks to work as popovers instead, creating a much simpler top level interface. When opened, we can display the controls to add, remove or rename items inside the popover, similar to what we already do for the presets:\n\n\n\nThis would result in a cleaner top level UI, and avoid the double X on some OS's:\n\n{[F6622971](Screenshot_2019-02-16_at_01.19.50.png), size=full}" ]

[ "Blender gives error message after closing user preferences \nWindows 8.0\nIntel HD 4600\n\nBroken: Master\n\nBlender gives the following error message in CMD after closing user preferences\"\n`<!> event has invalid window`\n\nOpen user preferences then close" ]

[ "Inactive Rigid Bodies still get affected by Force Fields\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40\n\nBroken: version: 3.3.0 Alpha\nWorked: None\n\nForce Fields still affect inactive ('Dynamic' off, 'Animated' on) Rigid Bodies, making them move after becoming active, even if the Force Field's strength is at 0 then.\n\nI discovered this issue when animating a Chess match where the fractured pieces get pushed away by a Force Field after getting taken down, and the next fractured pieces explode when becoming active, due to the previous Force Field (each piece has it's own Force Field).\n\n1. Download attachment\n2. Press play\n\n[Force bug on inactive Rigid bodies.blend](Force_bug_on_inactive_Rigid_bodies.blend)", "Impossible to move with G key an object scale to 0 and parent to an empty\nOperating system: Windows 7\nGraphics card: GTX 780\n\nBroken: 3.5.1\nWorked: \n\nWhen an object is parented to an empty, and this object is scale to 0, you cannot move it anymore with the G key. But you can move it in the transform menu location.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open blend.\n2. Try to move object with G key.\n3. It is possible with Transfom menu.\n\nThanks a lot !\ndono", "Wireframe opacity doesn't work if object is \"in front\" and viewport shading is set to material preview or rendered.\nBroken: 3.0\nWorked: \n\nWireframe opacity slider doesn't work if the object is \"in front\" and \"texture space\" is checked and viewport shading is set to material preview or rendered.\n\nSelect Cube\nObject properties-> viewport display -> in front ON\nObject properties-> viewport display -> texture space ON\nIn the viewport overlay panel, drag the wireframe opacity to lower the value.\nchange the viewport shading to preview or rendered, wire will have full opacity.", "Texture stencil \"Reset Transform\" doesn't work properly\n**System information**\nLinux Mint 17.3 (x86_64)\nLinux Mint 18 (x86_64)\nWindows 8.1 64bit\n\nNvidia Geforce GT640\nNvidia Geforce 820M\n\nBroken: 2.78, 2.77a\n\nIn texture paint mode (wether in 3D or 2D), the \"Reset Transform\" under \"Texture\" doesn't work once you clicked on the \"Reset Transform\" under \"Texture Mask\".\n\n\n\n - Open this .blend file [stencil Reset transform bug.blend](stencil_Reset_transform_bug.blend)\n\n - Click on the upper \"Reset transform\"\n\n - it works.\n\n - revert file\n\n - click on the lower reset transform, then on the upper one\n\n - it doesn't work.", "Make channel selection consistent with outliiner\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3050 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03\n\nBroken: version: 4.0.0 Alpha\n\nChannel selection are either cleared or not detected when selecting with Shift-ctrl-LMB\n\n- open attached file\n- In outliner `ctrl-click` on two objects to select them\n- then `shift-ctrl-click` on third object (selects third object and doesn't clear previous selection)\n- Now perform same with animation-channels\n\n", "Workbench: Random object color disables transparency in solid view\nOperating system: Windows 10 64bit\nGraphics card: Nvidia RTX 2080ti\n\nBroken: 2.83.1 official\n\n\n\n\nWhen setting the color of the material in the viewport to be semitransparent (Alpha value = 0.1) it works if the color of the viewport objects is set to \"Material\" it works, while if the color is set to \"Random\" the object is not semitransparent anymore.\n\nBlend file to test:\n[bug.blend](bug.blend)", "Blender 2.7x keymap: Add reroute shortcut (shift right mouse) doesn't work\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.91\n\nCaused by 58e554a55c\n\nShortcut for add reroute doesn't work in node editor.\n\nTry add reroute between two connected nodes using shortcut (shift + RMB during cross line).\n\n", "Camera to View and zoom do not work with orthographic cameras\nIf you switch to ortographic camera (point 1), and try to zoom in with the camera viewport active, the camera behaves as \"view lock>camera to view\" unchecked.\nThe correct behavior is that you can get near the object without changing the camera \"unlock view > camera view\" (point 3). Even though it's checked, it's not working as intended (check point 2 in the picture)\n\n\n- Open attached .blend file\n- Try zoom in, dolly in...\n[ortho_bug.blend](ortho_bug.blend)\n\n", "Properties Editor Popover\nWith properties search and outliner to properties tab switching we need a place in the properties editor for various settings. These options may include:\n* Outliner Tab Switch. There isn't an automatic solution that works well enough, so an explicit toggle is needed. [Auto, Enabled, Disabled]. Auto will keep the current behavior of only switching tabs on shared borders\n* Property search: Full tooltip text search would be useful, but could make performance suffer so a toggle would be useful\n* Tab hiding. Some workspaces don't need to display certain tabs and they can be hidden by default", "Annotation tool: wrong undo order and different in different modes\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: 2.93.2\nBroken: 3.0.0 Alpha, `c1f5ac7cfe`, 2021-07-25 18:36\nBroken: 2.83.17\nWorked: never\n\n\n| Object mode | works correct, as expected. Each undo action undoes 1 stroke |\n| -- | -- |\n| Weight paint | works properly |\n| Vertex paint | works properly most of the time, sometimes as Texture paint |\n| Texture paint | do not undoes each stroke but after number of {key Ctrl+Z} (n=strokes) undoes all strokes simultaneously or disables em at n=strokes+1 and undo previous action (mode switch in my case) |\n| Edit mode | same as Texture paint |\n| Sculpt mode | Undoes strokes one by one, but on the last stroke it do not react to {key Ctrl+Z} once, and then on the secon disables stroke and previous action (mode change) |\n\n**Steps to Reproduce**\n- Open default scene\n- Switch to Edit or texture paint mode\n- Draw 4 strokes with annotation tool\n- Undo 4 times (nothing happens to any stroke)\n- Undo again: Clears all strokes\n[2021-08-15_15-46-27.mp4](2021-08-15_15-46-27.mp4)\n\n", "Armature Object's \"Display As\" does nothing\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nWorked: version: 2.79 release.\n\nWhen I add an armature and change the Viewport Display Mode, nothing happens.\n\n\nOpen the blender;\nDelete the default objects;\nAdd an Armature, single bone;\nIn the Properties Panel, Object Properties, Viewport Display:\nChange 'Display As' to anything, it doesn't work.\n\n\n\n", "Highlighting active area (design task)\nThis design tasks was created in response to [D5047: UI: Dim Text Editor Caret and Selections When Inactive](D5047). \n\n----\n\nCurrently the active area isn't always as obvious as it could be, while the header changes color, little else changes.\n\nSome possible solutions:\n\n- Increase the header contrast.\n\n *Some headers are transparent, so adjusting menu background or similar might be needed instead.*\n- Highlight the border around the area.\n\n- Change the background color of the area.\n\n *In some cases this wont work well, for text-editor, Python-console or outliner it could work, for image or 3D view, we can't always do this.*\n\n- Change the color of the content (highlight gizmos, cursor, change selection color... etc),\n\n```\nD5047 does this for the text editor. \n```\n\n *Relies on there being a selection to see the change, may cause flicker effect since Blender users sloppy focus.*", "UV Unwrapping: Disconnect between unwrapped geometry and displayed geometry with shapekeys\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: (presumably) never\n[uv_unwrap_shapekeys-2022-02-07_12.29.52.mp4](uv_unwrap_shapekeys-2022-02-07_12.29.52.mp4)\nUV unwrapping uses active shapekey as if it was fully applied, even though it isn't active in the viewport.\n\nI don't think you can call this a bug, but unwrapping another geometry than the one you see should not be intended behaviour. It's a big point of confusion and potential source for errors. So I'm creating a report nonetheless.\n\n- Create shapekey on plane\n- Deform shapekey\n- Turn on `Shape Key Edit Mode`\n- UV unwrap geometry while deformed shapekey is active\n\nFile:\n[uv_unwrap_shapekeys.blend](uv_unwrap_shapekeys.blend)\n", "Object Info node not update if delete object from viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.93.0 Alpha\n\nIf you delete an object selected in the Object Info node, the object remains selected in the node\n\n\n\nDelete object from viewport selected in the Object Info node. Object Info node not update socket\n\n[Proximity_displaces2.blend](Proximity_displaces2.blend)\n\nNote that if you delete it from the outliner things work. The issue is when the object is deleted from the viewport.\n\n**Original file**\nThis file doesn't help because the object was already deleted from it:\n[Proximity_displaces.blend](Proximity_displaces.blend)\n\n\n\n\n", "NLA: Active Strip State lost when dragging Strip between tracks\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Quadro RTX 3000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: Never Worked\n\nClicking on a strip and dragging or G dragging the Strip on the timeline on the same Track and then hitting TAB to enter tweak mode is working, but if I do the same thing but drag it to another TRACK then hit TAB I get an error\n\nOpen my example Blend file and select the \"Click and Drag Me to the Drag Strip Here track\" STRIP and drag it to \"Click and Drag Me to the Drag Strip Here track\" then hit the TAB key to enter tweak mode, you should see an error as shown in the image. \n\"No active strip(s) to enter tweak mode on\n\"\n\n\n\n" ]

[ "Switching object with alt+click do not fade inactive objects\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nExpected: same fading as with direct entering to sculpt/edit or as with newer switch operator.\n\n[2021-03-09_16-33-47.mp4](2021-03-09_16-33-47.mp4)" ]

[ "Crash when change material on render with python\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.8+, 2.9 - 2.93.0 Alpha\n\nHey :)\nI’m trying to change material on a few objects during \"frame change\" with python.\nIn a viewport everything works fine but during Animation Rendering(cycles or eevee) it crashes immediately or a few frames later.\nMy system can’t handle more than 500 cubes.\n\n\n- Open \"change_mat.blend\"\n- Run script \"change_mat\" from Text Editor\n- Change Frame in Time-Line (0,1,2) // All cubes in the scene/viewport change their active material (Red, Green, Blue)\n- Press \"Render Animation\" => Crash // If it does not crash then duplicate more cubes\n\n[change_mat.blend](change_mat.blend)\n[change_mat.crash.txt](change_mat.crash.txt)\n\nMany Thanks!\n", "lost 90% of my progress\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\ni was 90% through my build and had forgetten to save although i havent made saving every five minutes my priority anyways i was almost done when it freezes then crashes and all of mt work is now gone this has already happened once but i didnt lose anything so i therefore didnt report it\n\n", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Freeze when using Object.ray_cast in a driver script\nOperating system: Linux-5.10.15-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.15-1-MANJARO, LLVM 11.0.1) AMD 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.91.2, 8dc95f61f3\nWorked: Unknown, fails on at least as old as 2.83.10.\n\nRunning a driver that includes a call to Object.ray_cast will freeze the interface entirely. Still exits normally when sent a SIGTERM. It does not create a crash.txt. Blender crashes with a segmentation fault in version 2.83.10 (hash: `b439a155442b`), and does create a crash.txt (see attached). Blender version 2.93.0 Alpha (hash: `7a608f88a713`) also freezes in the same way as 2.91.2. Using the ray_cast function in a non-driver script appears to function as expected.\n\nIn the attached blend file, run the text block `TurretRayCasting.py`, to put the script into the driver namespace. Next, click \"update dependencies\" in the driver panel. The application should freeze entirely. If `return target.ray_cast(turretTargetSpace, direction)- [x]` is commented out and replaced with `return True`, the application does not freeze.\n\n[driver_freeze2.blend](driver_freeze2.blend)\n\n[driver_freeze2.crash.txt](driver_freeze2.crash.txt)\n\n[system-info-2.91.2.txt](system-info-2.91.2.txt)", "Blender 2.71 (rc2) crashes when a UV sphere is added\nMac OS X 10.10 (beta) / AMD Radeon HD 6750M 512 MB\n\nBroken: 2.71 (release candidate 2)\nWorked: -\n\nBlender 2.71 (rc2) crashes when a UV Sphere is added to a existent project in Edit Mode.\n\nUsing the attached file, select the figure (stickman), go to Edit Mode and add a UV Sphere. After executing these steps, Blender stops responding and it's necessary to force quit and reopen. \n\nIt seems that's something to do with the modifiers (in the attached file, I'm using Mirror, Skin and Sub-surf). One or more of them are causing the crash when the UV Sphere is added. If I create a new project with no modifiers, I'm able to add UV Sphere. \n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "Fluid/Smoke modifier has an \"Apply\" button, which is misleading/dangerous (only meaningful for mesh-baked liquid domains)\n(All systems)\n\n- 2.81a and earlier (pre-mantaflow)\n- and 2.82 Alpha (2020-01-05) 5c66739b782e (mantaflow)\n\n**Short description of the error**\nAll objects involved in a fluid (gas or liquid) simulation, including domains, effectors, etc, have a modifier in the modifier stack.\n\nHowever, in all cases except one, the \"Apply\" button in this modifier is (as far as I can tell) just a synonym for \"remove the modifier and the physics settings (destructively!)\". It only actually \"applies\" something when we're dealing with mesh-baked liquid domains.\n\nSuch \"Apply\" button may be misleading and dangerous if a user were to, for instance, try to \"freeze\" a frame of a smoke simulation, which will just result in them losing all cache.", "LineArt; Crash after press play in a scene with LineArt modifier\nOperating system: Linux-5.4.0-105-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.144\n\nBroken: version: 3.2.0 Alpha\n\nNo idea what crashes blender. Just press play and wait some seconds.\n\nI would love to help solving this issue, so when someone could remind me where the crashreport usually lands in Linux, i could share that as well.\n[Narrator.blend](Narrator.blend)\n\n", "Keyed Particle Duration Crash\nOperating system: Windows 7 64\nGraphics card: nVidia GeForce GTX 970\n\nv.2.80.60\nDate: 2019-05-10 22:21\nHash: de9d846353bd\n\nBlender will sometimes crash when a keyed physics type particle system references more than one particle system. This usually occurs when attempting to change the duration setting of the second particle system.\n\nIn the provided file, change the duration setting in the particle system settings. Blender will crash.\n\n[Keyed Particle Duration Crash.blend](Keyed_Particle_Duration_Crash.blend)", "Render crash when using Python API to modify object Attribute data in frame_change_pre handler\nOperating system: Windows 10 Home\nGraphics card: GTX 1070 8GB\n\nBroken: Blender 2.93.0 84da05a8b806 (2021-06-02 11:21)\nWorked: n/a\n\n\nThis issue was discovered during development of an addon that generates procedural meshes in a `frame_change_pre` handler. When adding attributes to these meshes in the `frame_change_pre` handler, Blender can crash during render on random frames.\n\nThe `Render → Lock Interface` option is enabled as per the note in the [handlers documentation ](bpy.app.handlers.html#note-on-altering-data).\n\nI have created a simplified script that reproduces this crash during render, typically within a minute of starting the render. This script randomly generates triangles and attribute values in a frame change handler:\n\n```lines=5\nimport bpy, random\n\n\ndef frame_change_pre(scene):\n n_triangles = 10000 # number of triangles to generate\n n_attributes = 10 # number of attribute 'layers' to generate\n \n tsize = 0.1\n vertices = []\n triangles = []\n for i in range(n_triangles):\n xshift, yshift, zshift = random.uniform(-3, 3), random.uniform(-3, 3), random.uniform(-3, 3)\n vertices.append((-tsize + xshift, -tsize + yshift, zshift))\n vertices.append((tsize + xshift, -tsize + yshift, zshift))\n vertices.append((0 + xshift, tsize + yshift, zshift))\n triangles.append((3 * i, 3 * i + 1, 3 * i + 2))\n\n object = bpy.data.objects[\"Cube\"]\n object.data.clear_geometry()\n object.data.from_pydata(vertices, [], triangles)\n \n for i in range(n_attributes):\n attribute_name = str(i)\n try:\n object.data.attributes.remove(object.data.attributes.get(attribute_name))\n except:\n pass\n \n attribute = object.data.attributes.new(attribute_name, \"FLOAT\", \"POINT\")\n for value in attribute.data:\n value.value = random.uniform(0, 1)\n \n \nbpy.app.handlers.frame_change_pre.append(frame_change_pre)\n```\n\nIncreasing the number of triangles and/or number of attribute layers seems to increase the frequency of crashes. The crashes do not seem to occur when rendering from the command line.\n\nThis is the error reported after the crash:\n\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7736C6490\nModule : blender.exe\nThread : 00000814\n```\n\nAttached is the crash log: [attribute_crash_example.crash.txt](attribute_crash_example.crash.txt)\n\n\nAttached is a .blend file including the script that reproduces this issue.\n\n1. Open the .blend file\n2. Press 'Run Script'\n3. Begin rendering the animation (Blender > Render > Render Animation)\n\n[attribute_crash_example.blend](attribute_crash_example.blend)\n\n-----\nSeems easier to reproduce on a debug build since it hits an assert (although i'm not sure who is at fault there, could be the script, could be blender, @HooglyBoogly will likely know since he worked in this area recently) \n\n1) Make a debug build\n2) Load up the .blend above\n3) Hit the Play button on the Python script\n4) Rather than render, just his play on the timeline\n5) Boom!\n\n```lines=10\nBLI_assert failed: K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361, BKE_mesh_vertex_normals_ensure(), at 'CustomData_has_layer(&mesh->vdata, CD_NORMAL) || mesh->totvert == 0'\n\nStack trace:\nblender.exe :0x00007FF783355EA0 bli_windows_system_backtrace_stack_thread K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:233\nblender.exe :0x00007FF783354F30 BLI_windows_system_backtrace_stack K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:320\nblender.exe :0x00007FF783354900 BLI_system_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:386\nblender.exe :0x00007FF783359730 _BLI_assert_print_backtrace K:\\BlenderGit\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:50\nblender.exe :0x00007FF777848300 BKE_mesh_vertex_normals_ensure K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:361\nblender.exe :0x00007FF7778467E0 BKE_mesh_calc_normals K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\mesh_normals.cc:475\nblender.exe :0x00007FF77951DC80 ED_mesh_update K:\\BlenderGit\\blender\\source\\blender\\editors\\mesh\\mesh_data.c:1106\nblender.exe :0x00007FF77885B520 Mesh_update_call K:\\BlenderGit\\2022_full_with_tests\\source\\blender\\makesrna\\intern\\rna_mesh_gen.c:7350\nblender.exe :0x00007FF778528720 RNA_function_call K:\\BlenderGit\\blender\\source\\blender\\makesrna\\intern\\rna_access.c:7336\nblender.exe :0x00007FF778A024F0 pyrna_func_call K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_rna.c:6304\npython310_d.dll :0x00007FFA32E09B40 _PyObject_MakeTpCall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:215\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:112\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4232\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E0EAC0 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:114\npython310_d.dll :0x00007FFA32E0ED10 method_vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\classobject.c:53\npython310_d.dll :0x00007FFA330F0690 _PyObject_VectorcallTstate E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Include\\cpython\\abstract.h:115\npython310_d.dll :0x00007FFA330F0C90 call_function E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5870\npython310_d.dll :0x00007FFA330E37B0 _PyEval_EvalFrameDefault E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:4183\npython310_d.dll :0x00007FFA330F0350 _PyEval_Vector E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Python\\ceval.c:5072\npython310_d.dll :0x00007FFA32E08510 _PyFunction_Vectorcall E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:342\npython310_d.dll :0x00007FFA32E07FD0 PyVectorcall_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:255\npython310_d.dll :0x00007FFA32E086F0 _PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:290\npython310_d.dll :0x00007FFA32E07680 PyObject_Call E:\\db23\\build\\S\\VS1564D\\build\\python\\src\\external_python\\Objects\\call.c:318\nblender.exe :0x00007FF778A12F20 bpy_app_generic_callback K:\\BlenderGit\\blender\\source\\blender\\python\\intern\\bpy_app_handlers.c:354\nblender.exe :0x00007FF776ECF220 BKE_callback_exec K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:51\nblender.exe :0x00007FF776ECF400 BKE_callback_exec_id K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\callbacks.c:67\nblender.exe :0x00007FF7776D5C60 BKE_scene_graph_update_for_newframe_ex K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2648\nblender.exe :0x00007FF7776D5C10 BKE_scene_graph_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\blenkernel\\intern\\scene.c:2712\nblender.exe :0x00007FF778A46A10 ED_update_for_newframe K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_edit.c:1729\nblender.exe :0x00007FF778A70B30 screen_animation_step_invoke K:\\BlenderGit\\blender\\source\\blender\\editors\\screen\\screen_ops.c:4754\nblender.exe :0x00007FF777D74A30 wm_operator_invoke K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:1339\nblender.exe :0x00007FF777D6FE10 wm_handler_operator_call K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2340\nblender.exe :0x00007FF777D72F10 wm_handlers_do_keymap_with_keymap_handler K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:2693\nblender.exe :0x00007FF777D720D0 wm_handlers_do_intern K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3020\nblender.exe :0x00007FF777D70B70 wm_handlers_do K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3161\nblender.exe :0x00007FF777D6A440 wm_event_do_handlers K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c:3775\nblender.exe :0x00007FF777D3EB60 WM_main K:\\BlenderGit\\blender\\source\\blender\\windowmanager\\intern\\wm.c:642\nblender.exe :0x00007FF776EB2C60 main K:\\BlenderGit\\blender\\source\\creator\\creator.c:564\nblender.exe :0x00007FF7837A1B00 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF7837A18B0 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF7837A1890 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF7837A1BC0 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFAE8F27020 BaseThreadInitThunk\nntdll.dll :0x00007FFAE9062630 RtlUserThreadStart\n\n```\n\n", "Random crashes with NVidia + GPU Subdivision (sometimes when activating X-Ray or Wireframe overlay)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\n| Graphics card: | Driver : | User:\n| --- | --- | ---\n| NVIDIA GeForce RTX 3090/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @GabrielMoro\n| NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 512.15 | @STYXtheMUTT\n| NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 | 4.5.0 NVIDIA 516.94 | @Jojolix\n|NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2|NVIDIA 516.59|@MassimilianoPuliero\n|NVIDIA GeForce RTX 3090|NVIDIA 516.94|@The5\n\nBroken: version: 3.2.2\n\nOn some seemingly random occasions, Blender crashes with the following stack:\n```lines=10\nStack trace:\nblender.exe :0x00007FF77C1458B0 BKE_subdiv_free\nblender.exe :0x00007FF77C147880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF77BFFC3D0 <lambda_c000e58b9a8caf72c54e0e02a46effdb>::operator()\ntbb.dll :0x00007FFDBAF64FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF77BFFC6F0 BKE_mesh_wrapper_ensure_subdivision\nblender.exe :0x00007FF77CB38FA0 raycast_obj_fn\nblender.exe :0x00007FF77CB375E0 iter_snap_objects\nblender.exe :0x00007FF77CB3E530 transform_snap_context_project_view3d_mixed_impl\nblender.exe :0x00007FF77CB3F0E0 ED_transform_snap_object_project_view3d\nblender.exe :0x00007FF77CB5E7C0 applyFaceProject\nblender.exe :0x00007FF77CB5EE00 applySnappingIndividual\nblender.exe :0x00007FF77CB72F70 recalcData_objects\nblender.exe :0x00007FF77CB81010 applyTranslation\nblender.exe :0x00007FF77CB46BE0 transformApply\nblender.exe :0x00007FF77CB41920 transform_modal\nblender.exe :0x00007FF77C229D30 wm_macro_modal\nblender.exe :0x00007FF77C20F9E0 wm_handler_operator_call\nblender.exe :0x00007FF77C210BD0 wm_handlers_do_intern\nblender.exe :0x00007FF77C210000 wm_handlers_do\nblender.exe :0x00007FF77C216590 wm_event_do_handlers\nblender.exe :0x00007FF77C1FC380 WM_main\nblender.exe :0x00007FF77B2F12A0 main\nblender.exe :0x00007FF7814128B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDC7B67020 BaseThreadInitThunk\nntdll.dll :0x00007FFDC85A2680 RtlUserThreadStart\n```\n```lines=10\nStack trace:\nblender.exe :0x00007FF7A50C5B10 BKE_subdiv_update_from_mesh\nblender.exe :0x00007FF7A50C7880 BKE_subsurf_modifier_subdiv_descriptor_ensure\nblender.exe :0x00007FF7A52A1110 draw_subdiv_create_requested_buffers\nblender.exe :0x00007FF7A52A2080 DRW_create_subdivision\nblender.exe :0x00007FF7A52D1870 DRW_mesh_batch_cache_create_requested\nblender.exe :0x00007FF7A52C6000 drw_batch_cache_generate_requested\nblender.exe :0x00007FF7A529F1A0 drw_engines_cache_populate\nblender.exe :0x00007FF7A529B8C0 DRW_draw_render_loop_ex\nblender.exe :0x00007FF7A529C9B0 DRW_draw_view\nblender.exe :0x00007FF7A5D3FA00 view3d_main_region_draw\nblender.exe :0x00007FF7A5551070 ED_region_do_draw\nblender.exe :0x00007FF7A51A3700 wm_draw_window_offscreen\nblender.exe :0x00007FF7A51A3560 wm_draw_window\nblender.exe :0x00007FF7A51A2FB0 wm_draw_update\nblender.exe :0x00007FF7A517C380 WM_main\nblender.exe :0x00007FF7A42712A0 main\nblender.exe :0x00007FF7AA3928B0 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFD1C4A54D0 BaseThreadInitThunk\nntdll.dll :0x00007FFD1D524830 RtlUserThreadStart\n```\n\nOccasions observed:\n- try to snap objects on faces (the object that shall be snapped to is usually a complex mesh with modifiers like subdivisions, mirror, solidify, bevel and booleans)\n- toggle the shading mode between shaded and wireframe or between X-Ray and Wireframe Overlay.\n[intro.crash.txt](intro.crash.txt)\n\n\n- open attached file\n- disable and enable X-Ray multiple times\nIt happens specially when working fast.\n\n[BLENDER_Youre_Alive_v67.blend](BLENDER_Youre_Alive_v67.blend)\n\n", "GP Fill tool crashes with maximum Precision (macOS, Metal)\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: OpenGL\n\nThe Fill tool leads to crashes when Precision is set to maximum. (macOS, Metal)\n\n- new 2D Animation\n- draw a Circle\n- select Fill tool\n- set Precision to max (8)\n- try to fill\n\n<details>\n <summary>Thread 0 Crashed:: Dispatch queue: com.apple.main-thread ...</summary>\n\n0 libsystem_kernel.dylib \t 0x7ff80c84200e __pthread_kill + 10\n1 libsystem_pthread.dylib \t 0x7ff80c8781ff pthread_kill + 263\n2 libsystem_c.dylib \t 0x7ff80c7c3dbe __abort + 139\n3 libsystem_c.dylib \t 0x7ff80c7c3d33 abort + 138\n4 libsystem_c.dylib \t 0x7ff80c7c30cb __assert_rtn + 314\n5 Metal \t 0x7ff8152fd8a4 MTLReportFailure.cold.1 + 43\n6 Metal \t 0x7ff8152e7c05 MTLReportFailure + 529\n7 Metal \t 0x7ff8152e0378 _MTLMessageContextEnd + 1278\n8 Metal \t 0x7ff815231bdf -[MTLTextureDescriptorInternal validateWithDevice:] + 3296\n9 AMDMTLBronzeDriver \t 0x7ffa28ecc4f5 -[BronzeMtlTexture initInternalWithDevice:descriptor:] + 59\n10 Blender \t 0x112db8230 blender::gpu::MTLTexture::ensure_baked() + 1280\n11 Blender \t 0x112db832f blender::gpu::MTLTexture::get_metal_handle_base() + 15\n12 Blender \t 0x112d8997f blender::gpu::MTLFrameBuffer::bake_render_pass_descriptor(bool) + 879\n13 Blender \t 0x112d7c8c0 blender::gpu::MTLCommandBufferManager::ensure_begin_render_command_encoder(blender::gpu::MTLFrameBuffer*, bool, bool*) + 112\n14 Blender \t 0x112d806b5 blender::gpu::MTLContext::ensure_begin_render_pass() + 325\n15 Blender \t 0x112bdddd7 GPU_clear_color + 71\n16 Blender \t 0x10dd4f9e8 gpencil_fill_modal + 4456\n17 Blender \t 0x10d26677d wm_handler_operator_call(bContext*, ListBase*, wmEventHandler*, wmEvent*, PointerRNA*, char const*) + 1389\n18 Blender \t 0x10d265551 wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1841\n19 Blender \t 0x10d2647e0 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n20 Blender \t 0x10d263b7a wm_event_do_handlers + 2554\n21 Blender \t 0x10d259950 WM_main + 32\n22 Blender \t 0x10ca4a59e main + 878\n23 dyld \t 0x12095152e start + 462\n</details>\n\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "RigidBody explodes\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 2.93.2 Release Candidate\n\nWhen adding RigidBody, the simulation \"explodes\".\nI noticed that it only happens when the objects are near the center of the scene.\nIf we move the objects in the +Y direction, the problem disappear\n\nIn the video example I show that the rigidbody is working correctly by adding an icosphere and coliding it to the wall\n\nAdd rigidbody near the center of the scene\n\n[ZzbBGXn6sP.mp4](ZzbBGXn6sP.mp4)\n[rigidbody_problem_example.blend](rigidbody_problem_example.blend)\n\n", "Mantaflow: Crash when setting a Guide Fluid Effector\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0\n\nAfter setting a mesh as a \"Guide\" fluid effector, checking the \"Guides\" box in the fluid domain settings crashes Blender. \n\n- Open attached file,\n- go to the fluid domain settings\n- check the \"Guides\" box. \n[Fluid_Guide_Crash_01.blend](Fluid_Guide_Crash_01.blend)\n\n" ]

[ "Crash applying explode modifier\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX1060\n\nBroken: 2.80 beta, 2019-01-14, hash : 84c06e996a7a\n\n\nHello !\n\nI have noted that Blender crashes everytime I apply the modifier \"explode\". Moreover, this modifier doesn't seem to work without a particles system (but maybe it's normal with the 2.8 version?). \n\nThank you a lot for your work.\n\nGuillaume.", "Blender 2.8 crashes after applying explode modifier on objects.\nSystem Information\nAsus Laptop N550JK. Intel® Core™ i7-4700HQ\nOperating system: Fedora 28, Kernel ->4.19.4-200.fc28.x86_64\nGnome: Version 3.28.2\nOS Type: 64-bit\nGraphics card: GeForce GTX 850M/PCIe/SSE2, (add. info. It has Optimus)\nBlender Version\nBroken:\nblender 2.8, c59370bf643f\nSteps to recreate it:\n1- Select a primitive object and set an Explode modifier for it. (bpy.ops.object.modifier_add(type=\"Explode\")\n2- Apply this modifier by clicking on the Apply button.\nand then Blender window closes without harming the operating systems performance or stability.\nI tried the same operation on Blender 2.79 and it worked with no problem.", "bug on modifier \nOperating system: Windows-10-10.0.18351 64 Bits\nGraphics card: NVS 4200M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.58\n\n\nBroken: version: 2.80 (sub 48)\nWorked: (optional)\n\n\n\n\nBlender abruptly switch off when applied explode\nmodifier on mesh.\n\n" ]

[ "Some modifiers do not consider freshly added vertex group as empty\nOperating system: Win 10\nGraphics card: 1050 ti\n\nBroken: 3.2.0 Alpha\n\nEmpty vertex group was added to mesh in object mode without weight assigning and modifiers in stack are using this vgroup.\nSomehow some modifiers follow restriction and others don't. But if you assign zero weight for this vgroup in edit mode, then all modifiers are limited in execution as expected.\n\nFor example, open file and enable viewport rendering for every modifier in stack. \n[empty_vgroup.blend](empty_vgroup.blend)\n\nList of modifiers with this behavior:\nCast\nCurve\nDecimate\nLattice\nSmooth\nSmooth Corrective\nSmooth Laplacian\nWeld\nWave\n\n\n- Open new General template\n- Add monkey\n- Create new vertex group, but don't assign any vertices or weight\n- Add Smooth modifier\n\nIt should not deform mesh, because of empty vertex group, but it does", "How to handle difference in sinf/cosf for M1\nAs discovered in 104513 , it appears that the single-precision floating point trig functions are producing slightly different results on apple silicon CPUs (M1, M2) compared with x86_64 CPUs, for certain inputs.\ne.g.\n```\n sinf(0.8960554599761962890625) = 0.780868828296661376953125 <- output on x86_64\n sinf(0.8960554599761962890625) = 0.78086888790130615234375 <- output on Apple M1 and M2\n```\n\nThis is a design task to help understand this problem, track solutions and mitigations.\n\nSee for example, 0eba9e41bff97659bdb5e51ba814d3e5dd150b43\n\n", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "Hook modifier after Vertex Weight Mix modifier pulls incorrect vertices\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: \n3.5.0 Alpha\n3.4.0\n3.2.0\n2.93.8\n2.83.20\n(all version of blender, so far as I tried)\n\nWorked: None\n\nHook modifier after Vertex Weight Mix modifier pulls incorrect vertices.[HookAfterVWM.blend](HookAfterVWM.blend)\nIn other words, Vertex Weight Mix modifier breaks vertex index for Hook modifier.\n\n- Add a plane mesh and subdivide\n- Select some of vertices and \"Hook to new object\"\n- (At this time, an empty and a hook pull vertices correctly)\n- Add empty vertex group \"Group\" to plane\n- Add a VertexWeightMix modifier *before* the Hook modifier and set \"Group\" to Vertex Group A\n- The hook pulls incorrect vertices\n\n", "Weight gradient tool auto normalizes over locked groups\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.36 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Alpha\n\nWhen gradient painting over a group, the auto normalization affects other groups that are locked.\n\n[Weight Gradient Normalize.blend](attachment)\n1. Notice the weighing of the **Bone 1** vertex group.\n\n2. Select the **Bone 2** vertex group.\n3. Drag over the model to gradient paint.\n\n4. Select **Bone 1** again.\n**Bone 1** has been auto normalized even when it's locked\n", "Metal: Assert is triggered when drawing a Batch with an attribute format different from the type used in the Shader\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: [couldn't check yet]\n\nI'm not sure how serious the problem is.\nEven with the assert, the drawing seems to work.\nBelow is a small code that demonstrates the problem:\n\n```python\nimport bpy\nimport gpu\nfrom gpu.types import (\n GPUBatch,\n GPUIndexBuf,\n GPUVertBuf,\n GPUVertFormat,\n)\n\ndef draw():\n x1=0\n y1=0\n x2=bpy.context.region.width\n y2=bpy.context.region.height\n\n # The size of each color in `vertex_colors` needs to be 4 and\n # the size of each vector in `vertices` needs to be 3\n # otherwise a assert will be triggered the Metal backend.\n vertex_colors = ((1.0, 0.0, 0.0, 1.0), (1.0, 1.0, 1.0, 1.0))\n vertices = ((x1, y1), (x2, y2))\n\n shader = gpu.shader.from_builtin('POLYLINE_SMOOTH_COLOR')\n shader.uniform_float(\"viewportSize\", gpu.state.viewport_get()[2:])\n shader.uniform_float(\"lineWidth\", 5)\n\n vbo_format = GPUVertFormat()\n vbo_format.attr_add(id='color', comp_type='F32', len=len(vertex_colors[0]), fetch_mode='FLOAT')\n vbo_format.attr_add(id='pos', comp_type='F32', len=len(vertices[0]), fetch_mode='FLOAT')\n\n vbo = GPUVertBuf(vbo_format, len(vertices))\n vbo.attr_fill('color', vertex_colors)\n vbo.attr_fill('pos', vertices)\n\n batch = GPUBatch(type='LINE_STRIP', buf=vbo)\n batch.draw(shader)\n del batch\n\n\nbpy.types.SpaceView3D.draw_handler_add(draw, (), 'WINDOW', 'POST_PIXEL')\n\n```\n\nNote that the dimension of the vertices is 2D.\nIf converted to 3D (by adding a z value), the assert is no longer triggered.\n\n- Open attached .blend file.\n- Run the script in the text editor\n- Update the 3D view (by zooming for example)\n\n[gpu_metal_assert__bug.blend](attachment)\n\n", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n", "Hair Curves: Posed hair curves get stuck onto a wrong pose upon entering and exiting Sculpt, Vertex Paint or Weight Paint mode on the surface object\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060 Super\n\nBroken: 3.6.1\nWorked: n/a\n\nOn posed hair when using the 'deform curves on surface' node, if you enter and exit Sculpt, Vertex Paint or Weight Paint mode on the surface object, the posed hair will get stuck on a wrong pose, see attached images for comparison. You don't have to edit anything for the bug to occur. \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Open the file and select the \"Surface\" object\n2. Enter and exit Sculpt, Vertex Paint or Weight Paint mode\n3. The hair curves object should now have deformed onto a wrong pose and can't be fixed until you reload the file\n\nThis bug still appears in the final render and can only be fixed by reloading the save file.\n\n", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n", "Discrepancy between CPU and GPU rendering/material behaviour\nOperating system: macOS 13\nGraphics card: AMD W6800X Duo MPX module\n\nBroken: 3.3.1 (latest full release)\n\nI bought some assets which render with weird artefacts with the GPU, but work fine with CPU.\n\nThe assets are made by Bproduction (Florian Benedetto) on Blender Market. They are trees and vegetation models, which can be used individually or with Scatter 5.3. Simply put: they render properly with the CPU (Mac Pro, 24-core Intel), but render with horrible artefacts using the dual GPU. This doesn't happen with any other assets or materials I have.\n\nThe images below show the issue. I believe it's something to do with the material setup, but in any case it should render properly under both systems. Maybe it's an issue with macOS drivers?\n\n\n\n", "Hair particle length vertex group effect is non linear\nOperating system: MacOS Big Sur 11.2.3\nGraphics card: AMD Radeon Pro 5500M 8 GB\n\nBroken: 3.0 alpha, 4b06420e6504, master, 2021-09-13\nWorked: Unknown\n\nHair particle length scales non linearly with its length vertex group. Put another way, hair length is usually not quite equal to vertex weight * max hair length, which I assume is unintended. This causes problems when exact hair length is needed.\n\nThe screenshot below demonstrates the issue. \n\nIn this example, planes are instanced along the X axis from 0 to 1, using Geometry Nodes. The X position of each face is assigned to the vertex group controlling hair length. A hair particle system is added and set to spawn 1 particle per face.\nAs seen in the screenshot, the actual height of the hair is slightly wavy and doesn't form a straight line.\n\nHere's a video showing the same issue, this time spawning particles on a single face with interpolated vertex weights:\n[Hair Length Vertex Group Non Linear Bug.mov](Hair_Length_Vertex_Group_Non_Linear_Bug.mov)\n\n1. Delete the default cube\n2. Add a plane\n3. Add a vertex group to the plane\n4. In edit mode, assign a weight of 0.1 to all vertices.\n4. Add a hair particle system\n5. Set the hair length to 1m\n6. Assign the vertex group to control hair length\n7. In side-on orthographic view, observe that the hair length is slightly less than 0.1m.\n\n[Hair Length Vertex Group Bug.blend](Hair_Length_Vertex_Group_Bug.blend)", "Bevel disappears when vertex group value is less than 0.5\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.1.0 Alpha\n\nBevel modifier disappears when vertex group value is less than 0.5.\n\n\n - Open file and start decreasing weight value of active vertex in N-panel -> see how bevel is shrinking relatively to the weight\n - Go under 0.5 value -> bevel stops working abruptly\n - Invert vgroup influence inside modifier options\n - Go from 0.5 to 0.0 value -> bevel functioning again\n\n[bevel_vgroup.blend](bevel_vgroup.blend)\n\n", "Add error message feedback on constraints, similar to what already exists for modifiers.\nCurrently de-activated constraints only show their status through a small red icon. It would be better for users to also show an error message explaining what is the issue, similar to what modifiers already do.\n\nSee e.g. the invalid settings for the IK constraint of the first bone in this file from #100128: [lib.blend](lib.blend)", "Vertex weight not carried through bevel modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4080 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nVertex weight not carried through bevel modifier in some cases\n\n\n[105012.blend](attachment)\n- open blend\n- apply visual geometry on the `good` object\n\n- apply visual geometry on the `bad` object\n\n\n\n\nOK, some more testing (which solves the issue at least on the example I posted [also if there is a second bevel modifier with custom profile on there] -- as well as to some degree for the original file as well [which is posted below]):\n\n- open the file\n- go into editmode on the `bad` object\n- select all **edges** (edge select mode)\n- `Mesh` > `Sort Elements` > e.g. `Cursor Distance`\n- voila!\n\n-----\n\n\n\n**Original report**\n\nWhen wishing to create a bevel with the modifier on a specific vertex group aftern another Bevel modifier, the vertex group does not carry over.\n\n\n* Create a geometry\n* Mark some edges to bevel with bevel weight set to 1\n* Add an edge loop in to a vertex group\n* Add a bevel modifier and use Weight\n* Add 2nd bevel modifier and use vertex group. The area where the first Bevel modifier has been executed does not become incorporated into the vertex group\n\n\n\n\n\n\n\n\n", "Missing call to BMesh.update_edit_mesh causes crash in edit-mode\nRunning the following script in the default startup file crashes.\n\nUn-commenting the last line resolves the crash.\n\nThe issues is caused by triangulated loops referenced from `BMEditMesh.looptris` being freed.\n\nReporting this issue for reference, since it's a simpler test case compared to #70711, which has the same root cause.\n\n```\nimport bpy, bmesh\nbpy.ops.mesh.primitive_cube_add()\nob = bpy.context.active_object \nbpy.ops.object.mode_set(mode='EDIT')\nme = ob.data\nbm = bmesh.from_edit_mesh(me) \nbmesh.ops.subdivide_edges(bm,edges=bm.edges,use_grid_fill=True,cuts=1)\n# bmesh.update_edit_mesh(me, True)\n```" ]

[ "Vertex weights not editable or displaying properly in edit mode\nOperating system: Windows 10\nGraphics card: NVIDIA GForce GTX 1080\n\nBroken: 3.6.2\nWorked: 3.6.1\n\nVertex weights no longer display properly, or are editable in Edit mode.\nIn the \"Vertex Weights\" section of the \"Item\" tab of the N panel, the vertex weights of different groups all display the same value, regardless of the value that was set. When attempting to edit the values, the value entry doesn't work, except for the last group in the list, which changes all values.\n\nSelect the default cube. \nAdd some vertex groups in the Properties>Object Data panel.\nEnter edit mode and select a vertex.\nAssign it to several of the vertex groups.\nAttempt to adjust the vertex weight values in the N panel.\n\n", "Regression: Vertex Weights Panel is Broken\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 3.6.1\n\nThe Vertex Weights Panel appears to be broken in 3.6.2\n\n1. In the attached .blend file, select a vertex in Edit Mode\n2. In Object Data Properties, go to the Vertex Groups Panel and set a weight with the Weight slider \n3. Use the 'Assign' to execute the bpy.ops.object.vertex_group_assign() operator, assigning a weight to the selected vertices\n4. In the Item > Vertex Weights panel, if there are multiple Vertex Groups, the same weight will be displayed for all the vertex groups.\n5. Either open the Spreadsheet Editor to see the correct weights or run the below script in the Text Editor to print them in the System Console. You will see that the Item > Vertex Weights panel is incorrect.\n\n```Py\nimport bpy\n\ncontext = bpy.context\nactive_obj = context.active_object\nprevious_mode = context.object.mode\nbpy.ops.object.mode_set(mode=\"OBJECT\")\n\nif active_obj.type == 'MESH':\n vertices = active_obj.data.vertices\n\n for vi,vert in enumerate(vertices):\n if vert.select:\n print(\"#\"*20,vi,\"#\"*20)\n weights = [g.weight for g in vert.groups]\n for i,w in enumerate(weights):\n print(i,w)\n total_weight = sum(weights)\n print(\"total_weight\",total_weight)\n\nbpy.ops.object.mode_set(mode=previous_mode)\n```\n\n", "Each Vertex Shows The Same Weight For Each Bone\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: AMD JUNIPER (DRM 2.50.0 / 5.15.0-79-generic, LLVM 12.0.0) X.Org 3.3 (Core Profile) Mesa 21.2.6\n\nBroken: version: 3.6.2\n\nSee attached pic.\nIf I click on any vertex, every bone weight for that vertex is the same.\nI can't change any of the weights.\nI opened a file in both Blender 3.6.1 and 3.6.2 at the same time, and the weights are correct in 3.6.1.\n\nAs far as I know, if you save the file in Blender 3.6.2 (with wrong weights displayed), the correct weights will still be displayed if you open the same file in 3.6.1.\n\nThis has *not* been fixed in 3.6.3 release candidate.\n\n\n\nUse Blender 3.6.2 to open any file that has different weights assigned to a vertex.\n\n", "3.6.2 doesnt display correctly normalized weights in edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: 4.0\n\n\nIn edit mode weight display options blender always show the same value for all bones .The normal behavior is always show normalized values for bones and other values for non bones weights. \n\n\nmake an armature and assign to a mesh .Paint some weights with auto normalize enabled . Enter edit mode ,Select a vertex and check his values .All values are the same witch its not true \n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Regression: Edit mode weights panel shows incorrect values\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.36 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.2, caused by cd74ba6413\n\nEdit mode weights panel incorrectly shows the last weight in all the entries.\n\n\n[EditModeWeights.blend](attachment)\n\nThe groups are named according to the weight value they hold.\nYou can also clearly see by the color that the active group holds a value of 1 in all vertices.\nHowever the weights panel shows 0.25 for all groups\n\n\n\n", "Vertex weight table in edit mode completely useless in 3.6.2\nOperating system: Windows 10\nGraphics card: GTX 1070\n\nBroken: 3.6.2\nWorked: 3.6.1\n\nThe vertex weight panel in 3.6.2 is totally wrong, thesame blendfile opened in 3.6.1 is showing the correct weights.\nLook at the pictures\n\nI cannot include the blendfile, too large and complex.\n\n", "Vertex Weights Panel displays weight values wrongly.\nOperating system: Win11\nGraphics card: RTX 2060\n\nBroken: (blender 3.6.2, blender 3.6.3 release candidate)\nWorked: (blender 3.6.0, blender 4.0 alpha)\n\nin mesh edit mode, select a single vertex to show \"Vertex Weights\" Panel, vertex weight value does not display correctly, they are always the same as bottom vertex group.\n\n1. with the default cube in edit mode, select some vertices and add to vertex group\n2. repeat 1 to add more vertex groups\n3. use above setup or the attached \"vertex weights\" blend file. in edit mode, select a single vertex. in 3d viewport - item, the \"Vertex Weights\" panel shows up.\n4. all vertex groups value always equal to bottom vertex group value. this wrongly represents their actual weight values as shown in the attached gif.\n\n", "vertex weight panel only shows the max weight\nOperating system: windows 10 pro 22H2\nGraphics card: nvidia gtx 1060 driver 528.49\n\nBroken: 3.6.2\nWorked: 3.6.1\n\nThe vertex weights panel doesn't work anymore, worked fine in 3.6.1 so this is a regression. The weights are assigned fine and correctly visualized in weight paint mode, but the vertex weigths panel only shows the max weight.\n\nsteps:\n1. create some vertex groups for the default cube\n2. for each group assign different weights to a vertex\n3. check the vertex weight panel, it only shows the max weight\n\n", "Vertex weights incorrectly display as all the same\nOperating system: Ubuntu MATE 22.04.3 LTS\nGraphics card: Intel i3 10th Gen\n\nBroken: 3.6.2, also 4.0.0 Aug 22 commit d45f47a809dd\nWorked: 3.3.11 Aug 21 commit 7311c9d51e1e\nI'd check more versions but the site is only giving them at 200 kb/sec and it's taking 20 minutes to download each one.\n\nVertex weights are shown inaccurately in the transform menu. The same weight value is shown for all vertex groups, even when the actual weights are different.\n\n1. Start with the attached file, OR\n 1a. Start with the default cube, add an armature, add a second bone to the armature, parent the mesh to the armature with automatic weights\n 1b. Enter edit mode, select a vertex influenced by at least 2 bones, and press N to open the transform info.\n2. Look at vertex weights shown. Observe the same value is shown for all weights.\n3. Type in a different value for the bottom weight. Observe the value shown for the top weight changes to match it.\n4. Type in a different value for the top weight. Observe there is no visible effect and the same value is still shown as before.\n5 (optional). Pose the bones. Go back and adjust the weights again, noting that the actual position matches what you typed in and not the value shown.\n\n" ]

[ "Support for snapping to Lattice objects\nOperating system: Darwin-17.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.27.6 378.10.10.10.20.109\n\nBroken: version: 2.82 (sub 0)\nWorked: (optional)\n\nIt is not possible to snap any type of vertex (mesh, curve or lattice vertex) to a lattice vertex.\n\nsee video\n\n[latice_verts_not snapping.blend](latice_verts_not_snapping.blend)\n\n[lattice_verts_not_snapping.mp4](lattice_verts_not_snapping.mp4)\n\n", "Modifier re-evaluation makes editing dimensions unreliable\nCurrently editing dimensions uses the bounding box that's recalculated while dragging.\n\nThis can cause a feed-back loop as the objects scale is used by some modifiers which calculate a new bounding based on the scale which is then used in dimensions.\n\nIn the case of armature modifier - any zero scaled axis makes causes the mesh to scale into a single point, making any further changes to the dimensions not have any effect.\n\n----\n\nOriginal report:\n\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Blender 2.79\n\n\nIf object is rigged scrolling its dimension value toward zero causes object to disappear, even if right mouse button has been clicked in order to cancel a scaling. So blender accepts a scale of zero even if left mouse button hasn't been released yet, Is it an expected behavior in Blender 2.8?\n\n\n\n\n - Select the cube.\n - Scroll any of its dimensions value toward zero without releasing the left mouse button\n - Cancel scrolling by right mouse button click.\n\n\n\n[Bug_report.blend](Bug_report.blend)\n\n", "Boolean Modifier is evaluated if an object linked to the cutter object is link-duplicated\nOperating system: Linux-5.4.0-58-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.38\n\nBroken: version: 2.91.0\n\n\nSuppose ObjectA has a boolean modifier, the target object of which is CutterA. CutterA shares the same mesh datablock as CutterB. If CutterB is link-duplicated (Alt-D), ObjectA 's boolean modifier is re-evaluated. In large technical scenes with many linked cutters this means Blender frequently stalls, re-evaluating *every boolean in the scene every time you duplicate a cutter.*\n\nExpected behaviour: boolean modifier should only be evaluated if the cutter object datablocks *change*, and adding a user to a datablock should not count as a change.\n\n", "Bushing under the Displace modifier will change the primitive mesh\nOperating system: Windows-10-10.0.21343-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.0 Alpha\nWorked: (the newest version of Blender that worked as expected)\n\n\nUnder the replacement modifier, sculpting the object will add the effects of the replacement modifier to the brush\n\nstep1:add modifier into the object as a Displace modifier\nstep2:In the Sculpt Mode, Bushing under the Displace modifier will change the primitive mesh\n\n[Peek 2021-03-30 18-59.webm](Peek_2021-03-30_18-59.webm)\n\n[Bushing under the Displace modifier will be change premitive mesh .blend](Bushing_under_the_Displace_modifier_will_be_change_premitive_mesh_.blend)", "Snap Increment with \"Absolute Grid Snap\" not working correctly in XY plane\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.Q3.230719\n\nBroken: version: 3.6.2\n\nDescription of error\nWhen moving an object by using Increment Snapping with \"Absolute Grid Snap\" enabled and constraining the plane the object no longer moves with the mouse cursor. It is best demonstrated in the video I have captured.\n\nTo repeat follow these steps:\n1. Make a new default blender scene with an object to move.\n2. Enable Snapping, set to Increment.\n3. Select the object and then \"G\" to move it.\n4. Constrain movement to XY plane and move the object around the 3D space.\n5. Next cancel the transform and Enable in the Snapping Setting, \"Absolute Grid Snap\".\n6. Press \"G\" to move the object once again and contrain its movement to the same plane as before and move the object around.\n7. The object will no longer follow the cursors movement.\n\nAdditionally, this is a recent bug as of this version as tested both 3.4.1 and 3.5 version of blender and they both work as expected, with no Discrepancy.\n", "Boolean modifier assigns wrong material\nOperating system: win10\nGraphics card: 1050 ti\n\nBroken: 3.4 alpha\nWorked: 3.3.2\n\nMaterial transferred during boolean operation is not the one assigned to target geometry.\n\n[boolean_material_update_problem.blend](boolean_material_update_problem.blend)\nOpen attached file or:\n\n - Create some boolean difference situation with modifier\n - Add two materials to target, assign first to geometry and put it on second slot -> modifier owner slice has wrong material\n\n\n", "Geometry Nodes Object Group input does not remove dependencies\n[system-info.txt](system-info.txt)\n\nBroken:version: 3.4.0 Alpha, branch: master, commit date: 2022-10-04 22:45, hash: f9a10e7ed039, type: release\n...been already around for a while\n\nIt seems that Blender does not correctly remove the dependency from the formerly connected object from the Geometry Nodes Object Group input.\nEven when deleting all the default values.\n\n- Append the object `Cube` from the attached .blend file\nit will also append Suzanne even though all former links in the setup have been removed.\nThe only thing that helps to get rid of the dependency is to delete the input and recreate it together with all the links. \n[dependency_bug.blend](dependency_bug.blend)\n...and do not get me wrong i really like Suzanne! But if she appears all the time even when she is not invited it gets a bit annoying.\n", "Geometry node don't expose materials to the solidify modifier\nOperating system: Windows 10\nGraphics card: Nvidia RTX 2060\n\nBroken: blender-3.1.0-beta+v31.93cc89247010\nWorked: 3.0.1\n\n\nWhen using a geometry node to generate a mesh, and then applying a solidify modifier to it, the materials are not properly exposed and not or wrongly assigned to the final mesh\n\n- create a plane\n- go in edit mode and delete all the mesh data\n- back in object mode, add geometry node modifier\n- add a Cylinder mesh primitive, and set its fill type to None\n- add a Join Geometry node and plug the Group Input Geometry socket and the Cylinder node Mesh socket into the Join node\n- plug the join node into the output\n- add 3 materials to the object and set different colors\n- add a solidify modifier and set material for offset and rim to indices 1 and 2\n\nThe resulting tube doesn't show any of the materials.\n\n- go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays the last material of the list on some parts, but this is still not it.\n\n- Instead of creating a cylinder in the geometry node tree, plug a Mesh circle primitive\nThen add a screw modifier to extrude it, after the geometry node modifier and before the solidify modifier\nSet its angle to 0° and Screw value to 1\n\nNow the resulting tube is only displaying the first material\n\n- Go in edit mode and add at least one vertex to the mesh\n\nNow the resulting tube displays all the materials properly.\n\nNote : it is not obvious, but it is mandatory to join the original geometry into the end result to get the materials correctly propagated to the output.\nMaybe this could be more clearly explained or simplified somehow.\n\nSample file here reproducing all cases mentionned above :\n[solidify_material_bug.zip](solidify_material_bug.zip)", "Broken Twist on meshes deformed with Particle Instance Modifier with Along Path\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.90.1\n\nThe twist of a mesh deformed with the Particle Instance Modifier with the Along Path option seems broken, more noticeable with steep curvature in hairs. I compare it to the Curve Deform modifier as an example of proper deformation. Now, you may say it's an unfair comparison given that curves have an explicit twist that you can modify, unlike hairs. But even without controlling the initial twist of the hair, it's broken in a couple of ways.\n\nFirst, it deforms the mesh unevenly, with some vertices twisting more than others, even in a case where vertices are completely equidistant around the origin and both origins are aligned, like the cube in this image. The selected face and the edgeloop here should be squares but aren't, unlike in the curve deform modifier \nSecond, when changing the length with the Position Slider, the whole thing seems to change twist at once. Instead of having a consistent twist on each point of the path [Particle Instance Mod bug2.mp4](Particle_Instance_Mod_bug2.mp4)\nAs a side note, when using Along Path, finding how to orient your mesh to the hair is unintuitive, always using the global Y axis as the length axis in which I added subdivisions but then twisting weirdly when changing the Axis option in the modifier, I settled for Z in this example.\n\n\nAttached is the same file used in the video, you can open it and move the Position slider in the Particle Instance Modifier, the scale of the Curve Deform modifier example is driven by it so you can see both changing in real time.\n\n[ParticleInstanceTwistBug.blend](ParticleInstanceTwistBug.blend)\n\nWhy do I think this is happening? Well, if you select the object with the particle system, go to the particle properties, and change the length of the hair under the Render>Timing>End subpanel, you can see the problem is the same, basically the twist changes with length. Maybe the modifier should do something different and get the twist from the whole length particle and then scale the mesh instance before deforming or something like that, idk\n\n", "Enhance ways of accessing active modifier for poll functions of operators\nCurrently, poll function of operators can only get the modifier they are supposed to work on from the context. This is often missing (when called from shortcuts e.g., also with drag-n-drop of modifier panels...).\n\nThis is a sever problem for liboverrides, as some modifiers should then be edited (the locally added ones), and others not.\n\nI can see two ways to solve that: \n \n- Add current 'active' modifier to context (not sure how, or even if, this is always possible).\n- Work around the issue by adding some kind of second 'polling' helper function to be used from invoke/exec functions (since when not found in context, those use event to get the modifier to work on, but events are not passed to poll functions).\n", "Generic way for modifiers to check user-edited flags\nThe simulation modifiers need to take care of invalidating cache when user edits are performed on the modifier itself, or its dependencies.\n\nFor the point cache (rigid body simulation, for example) this is done as a dedicated dependency graph node, which is hooked to the rest of the graph via a relation which has `RELATION_FLAG_FLUSH_USER_EDIT_ONLY` flag. The benefit of such approach is that a generic callback function can be used (without capturing any internal state of the graph). The downside is the more complex routing of relations.\n\nThe simulation nodes took a bit different approach: the nodes modifier has a special lambda callback which checks the node and dependency graph state:\n```Cpp\nmodifier_node->evaluate = [](...) {\n if (modifier_node->flag & DEPSOP_FLAG_USER_MODIFIED) {\n ...\n }\n}\n```\n\nSuch approach allows to access the modification state without extra nodes and relations, but it is not very generic: ideally the modifier-specific logic will be left to the modifier's \"apply\" callback.\n\nFortunately, there is a simple modification to the current nodes modifier callback we can do!\n\nGeneral idea: have a generic modifier node callback (for all node types) which will copy the user-modified flag from the modifier dependency graph node to the modifier data. The modifier's \"apply\" callback then can make decision based on this flag.\n\nPseudo-code of this proposal goes as following:\n```Cpp\nmodifier_node->evaluate = [modifier_index = ...](::Depsgraph * /*depsgraph*/, ...) {\n ModifierData *md_eval = object_eval->modifiers[modifier_index];\n if (modifier_node->flag & DEPSOP_FLAG_USER_MODIFIED) {\n md_eval-> flag |= MODIFIER_USER_MODIFIED;\n } else {\n md_eval-> flag &= ~MODIFIER_USER_MODIFIED;\n }\n}\n```\n\nUse the modifier index since it can be captured at the graph construction time, and will stay available even if the original objects are destroyed (the long-term goal is to allow the depsgraph be fully independent from the original scene after its Copy-On-Write was run). It is a bit annoying to do an index-based lookup in the list, but it is unlikely to show up in a profiler.\n\nThe geometry node modifier can immediately use this new flag. In a longer term the rigid body will do the same or be migrated to the new simulation framework :)\n\n", "Mirror Modifier On Cage Selection Papercut \nBroken: 2.93.4\nWorked: Maybe never.\n\nWhen in edit mode, using the \"On Cage\" option for the mirror modifier results in some unintuitive behavior when selecting vertices created by the bisect feature. The vertices created by the by the bisection are mapped to the original mesh data in a way that appears to be based on blenders internal representation of the mesh and not based on something observable to the user.\nThe behavior when selecting should feel consistent to the user. To fix this, I suggest that the vertices created by the bisection should always map to the vertices on the original mesh that are on the removed side of the bisection plane. This way users would be able to tweak the centerline of the mirrored mesh in while using \"On Cage.\" As it is currently implemented, there are vertices that affect the mesh that cannot be accessed through normal click selection unless \"On Cage\" is off.\n\n**Example**\n\n\nSelect the +X or -X face of the default cube and scale it by 0.5.\nAdd the mirror modifier and select bisect for the X axis so that the object is mirrored and bisected about the X axis.\nTurn on \"On cage\" for the mirror modifier then enter edit mode for the object.\nWhen selecting the vertices on plane X=0, you should notice that two of the vertices correspond to visible mirrored vertices and two correspond to vertices removed by the modifier. \n\nSimple scene showing the behavior. \n[MirrorSelectOnCagePapercut.blend](MirrorSelectOnCagePapercut.blend)\n", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Apply modifiers on objects with shapekeys (with some exceptions)\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nCurrently it is not possible to apply modifiers to an object that has shapekeys, even though it would be technically possible for most modifiers. I suggest making it possible to apply modifiers to objects with shapekeys with some exceptions.\n\n\n\nFor example:\n\nThe subdivision and wire modifier does not modify the objects topology as the shape change. This modifier could be applied while still keeping the shape keys.\n\n---\n\nScreen capture example of how to apply modifiers and keep shapekeys.\n[apply modifiers with shape keys.mp4](apply_modifiers_with_shape_keys.mp4)\n\n---\n\nModifiers that can't be applied in a simple way when the object has shapekeys.\n\n- Boolean\n- Build\n- Decimate\n- Geometry nodes (in some cases. Easiest to just exclude this modifier)\n- Mirror (**IF USING BISECT**)\n- Remesh\n- Skin\n- Volume to mesh\n- Weld\n- Explode\n- Fluid\n- Ocean\n- Particle instance (Since source particle system density mapping can be applied in world space)\n- Particle system \n\n\n\nWhen the user tries to apply any of these modifiers when the object has shape keys, the error message should be:\n***Modifier that changes topology based on shape cannot be applied to a mesh with shape keys***\n\nNote:\nWhen applying a modifer of type \"Modify\" (for example \"Data transfer\"), the current shape should be used when applying the modifier (i.e. the resulting shape of all combination and values of the objects shape keys)\n\n\n", "data transfer breaks if more than one remesh is above it in the stack.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nSometimes the `DataTransfer` modifier doesn't work for no apparent reason.\nIn the attached file, putting a `Boolean` modifier after the `Remesh` makes `DataTransfer` work again.\nThis isn't anything to do with differing topology between the hidden and unhidden monkey, otherwise it wouldn't work with only one remesh modifier in the stack.\n\n- Open the file bellow\n- with the monkey selected, turn off the boolean modifier in the stack. \nThe uvs which are being transferred from the hidden monkey will disappear (making the monkey all black).\n[simplified data transfer.blend](simplified_data_transfer.blend)\n\n---\nOriginal file:\n\nOne remesh modifier works fine:\n\n\n\ntwo remesh modifiers break the data transfer:\n\n\n[terminator.blend](terminator.blend)\n" ]

[ "No snapping for objects referenced in modifiers (even if disabled)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\nWorked: probably never; hopefully it's just an oversight. Even 2.79b is broken\n\nI've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's \"origin\" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object.\n\n[snap-issue.blend](snap-issue.blend)\n\n- Open the attached .blend file OR follow next instructions to setup\n - Start with default scene and add an Empty to the scene\n - Add a Simple Deform modifier to the Cube\n - Set the Simple Deform's \"origin\" object to the Empty, the mode to \"Bend\" and the \"Angle\" to 0deg (to prevent any deformation)\n - Set the scene snapping mode to vertex\n\n- Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug)\n\n- Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug)\n\n- Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file)\n\n- Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube\n\n" ]

[ "Persistent Base of Layer brush resets when selecting another object\nOperating system: gentoo ~amd64\nGraphics card: 1060\n\nBroken: all\nWorked: none\n\nPersistent Base resets in local mode\n1 select default cube\n2 subdivide it (Edit mode > W> Subdivide to 100 > Object mode)\n3 go to sculpt mode\n4 select layer brush\n5 select \"Persistent\" chbox\n6 Push Set Persistent Base\n7 Draw\n8 Draw with CTRL (it now worked like undo brush)\nNow all good works, and i can change anu brush - super useful\nbut\n9a select any other object/collection\n9b go to other mode ant went tot sculpt mode\n9c go to local mode (hotkey /) and went back\n10 Draw with CTRL (now it don't work right - it draw without Persistent Base)\n\nPlease see my screencast\n[2020-05-26 09-58-50.mp4](2020-05-26_09-58-50.mp4)\nIn global mode all works perfect\nIn local mode Persistent Base was gone\nThank you for great opensource sculpt tool!\n\nUpdate\n[2020-05-26 10-09-57.mp4](2020-05-26_10-09-57.mp4)\nBug happend If object has been selected agane too", "Eyedropper for props does not work in dialog boxes\nBlender 2.81, 71f2229b0d82\nfor example, in Texture Paint Context Menu\nI wanted to implement something using Operator and context.window_manager.invoke_props_dialog()\nThis is not a bug, but why not do it at the dialog level.\n", "Dynamic Paint sub-steps doesn't work with particles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.0 Alpha\n\nWhen using a particle system as a dynamic paint brush, the sub-steps setting of the canvas doesn't work. The sub-steps appear to work as intended with all other brush types. Whether the painting is done with vertex or texture maps doesn't seem to have an impact on the bug.\n\n* Open attached .blend\n* Bake the dynamic paint cache with a sub-steps value > 0\n* The result shows no sub-steps\n[Bug2.blend](Bug2.blend)\n", "Enable pen tilt support by default\nThis task keeps track of the tested devices in order to enable pen tilt support by default.\nThe reason this feature was committed as experimental was because it is not clear what devices and OS configurations are supported and what devices we are planning to support. \nRight now the feature can be enabled in alpha builds as a experimental feature and used in some sculpt tools (draw sharp, scrape, clay strips...). \n\n\nWorking:\n- Wacom Cintiq Pro 16 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Ubuntu 20.04\n- Wacom Cintiq Pro 24 - Manjaro 19 GNOME \n- Wacom Intuos Pro M - Ubuntu 20.04\n- Wacom Intuos Pro M - Pop OS 20.04\n- Wacom Intuos Pro M - Windows 11\n\n- XP-Pen Artist 13.3 Pro - Windows 10\n- XP-Pen Artist 15.6 Pro - Windows 10\n\n\n\nNot working:\n- Wacom Mobilestudio Pro 16 - Windows 10 (y tilt axis is inverted)\n- Huion Kamvas 13 - Windows 10 (y tilt axis is inverted)\n", "GP brush pin for fill only, makes both stroke and fill\nHi \nI want to have fill and stroke in different color but if I pin, I get both color same.\nSo that I cannot make custom brush, or I have to change it vertex mode every time.\nCan you please check?\n\n[image](attachment)\n\n", "Snapping collision object to particle emitter not working\nOperating system: Linux-5.9.3-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.9.3-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.2.1\n\nBroken: 2.79 - version: 2.92.0 Alpha\nWorked: -\n\nIt is impossible to snap an object with Collision to an object with a Particle System (not event the snapping circle showing up), but it works the other way round (SnapTo set to everything but Increment). This seems to have been around for a long time, but I can't find any report regarding the issue.\n\nAdd a particle system to the default cube (P)\nAdd another primitive, activate collision in the physics settings (C)\nTry snapping C to P, it won't work\nBut snapping P to C works and collision objects can be snapped to each other. C to P only works if you remove the collision or the particle system.\n\n", "Scroll drag stuck after specific MMB click\nBlender 2.80rc1, 2.83 (sub 2)\n\nHere is the video\n[2019-02-26_06-35-31.mp4](2019-02-26_06-35-31.mp4)\n\n - Open Blender\n - In `Preferences -> Interface -> Menus` enable `Open on Mouse Over`\n - Close preference windows and go to any paint/sculpt mode\n - Display the sidebar and go to the Tool tab\n - Move mouse pointor over brush`s big icon and before it reacts with highlight (brush-search window appear) press and hold MMB\n - Then LMB to discard.\nNow scroll sticks. It releases after Esc or MMB. But at first I was forced to restart blender, because pointer stuck there.\n", "The SHIFT key, mapped on my graphic tablet is not working in Blender 2.80\nOperating system: Windows 10\nGraphics card: NVidia GeForce GTX 1070\n\nBroken: 2.80 25-12-2018\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nI own a Huion NEW 1060 PLUS 8192 graphics tablet. One of my keys is mapped as SHIFT, but Blender doesn't recognize it at all. As one of the pen keys is mapped as the Middle Mouse Button.\nAnother key on the tablet is mapped as CTRL, another as ALT etc. and they all work with the MMB on the pen, but the SHIFT key is not recognizable to Blender. I can zoom, I can rotate, I can change views but i cannot pan nor select multiple objects. Basically, everything that is connected to the SHIFT key is dead.\nBlender recognizes the keyboard SHIFT key, as well as a mapped SHIFT shortcut on the mouse, but not on the tablet.\nAll around the OS and in Rhino, Photoshop, Illustrator, the Shift key from my tablet is working perfectly, but inside Blender no.\n\nOh, and this is the first time I'm trying 2.8. \nEverything works fine in 2.79.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Grease Pencil Bezier points can't be deleted immediately after moving\nOperating system: Linux Mint 64-bit\nGraphics card: NVDIDA GTX 1080 ti\n\n2.93.5 (also broken in 3.0 alpha)\n\nDelete (X) does not work on Grease Pencil edit curve points if the previous operation was to transform them.\n\n - Enable curve editing in Edit Mode on a Grease Pencil object (attached)\n - Select and transform any bezier point (G, R, S)\n # Use Delete (X) on the selected point\nIt won't delete!\n[GPbug.blend](GPbug.blend)", "Multires Displacement Smear brush + Dyntopo Error\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.92.0\n\n[When you want to use the multires displacement smear brush with dynamic topology, blender closes.]\n\n\n1. Open Blender\n2. Enter sculpted mode\n3. Select the Multires Displacement Smear brush\n4. Activate Dynamic Topology dyntopo\n5. Pass the brush through the Bucket\n6. Blender closes\n\n[untitled.blend](untitled.blend)\n\n", "CMD terminal stays open after opening blender\nOperating system: Windows-10-10.0.25247-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\n\nI'm not sure why it';s happening but it's not happening for 3.3 version\n\n\n\n", "Simple ball shooting animation not working as before\nOperating system: win7\nGraphics card: gtx970m\n\nBroken: 2.80, 2.81a, 2.82a, 2.83-1239cab11ff9\nWorked: 2.79b\n\nI've tried to create a simple shooting ball and while the effect was ok with blender 2.79b it won't work the same\nway on the specified \"broken\" versions. I'm not sure if the way to make these type of animations has changed of\nif this it's really an existing bug. \n\nDemo: [Blender 2.79b vs 2.82](2020-04-09_16-14-38.mp4)\n\n\nYou'll find the .blend file ready to display the issue below.\n\n[test1.blend](test1.blend)", "Line stroke method not working with Scene spacing\nOperating system: Linux-5.4.0-121-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.151\n\nBroken: version: 3.2.1\n\nLine stroke method not working with Scene spacing\n\nOpen blender, then open a new sculpt file, select any brush change the stroke method to line and chose scene spacing distance. \nIt only works when started and ended inside the object, but when coming from outside the object or end up outside the object it doesn't work, sometimes it gives an initial effect when it comes in contact with the object but only one sample.\nI the video you can see how it works with view spacing and then how behaves with scene spacing.\n\n[vokoscreen-2022-07-12_14-43-22.mp4](vokoscreen-2022-07-12_14-43-22.mp4)\n\n", "Stroke overlay when erasing\nOperating system: Win 10\nGraphics card: NVIDIA GeForce GTX 1070 Ti\n\nBroken: (example: 2.80, 66684bdff30f, master, 2019-07-05)\n\n\nThe new alpha overlap stops working, when you erase somethin of that stroke.\n\n \nOpen a new project create a blank stroke object draw something try to erase it", "Surface tension is not working\nOperating system:Windows-10-10.0.19041-SP0 64Bits\nGraphics card:NVIDIA GeForce RTX 2080/PCIe/SSE2\n\nBroken:3.1.0 Alpha, branch: K-Cycles, commit date: 2022-01-16 15:45, hash: 164a13275cf8\nWorked: \n\nIn mantaflow fluid simulation, change the value of 'surface tension' does not work at all, My cpu is Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz, i tried different version of blender, it didn't work either\n[surface1.blend](surface1.blend)" ]

[ "Pressure sensitivity stops working after I open \"Edit -> Preferences\" window (Veikk a15 tablet)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007\n\nBroken: version: 2.82 (sub 7)\n\nI am using a Veikk a15 tablet. Pressure sensitive stops working after I open the \"Edit -> Preferences\" window. Now I work with version 2.82a, but I found the same problem in 2.79 - 2.83a versions. I tried changing the \"Preferences -> Input -> Tablet API\" settings, but that didn't help.\n\nI open the program in sculpting mode or general and pressure sensitivity works well.\n\nIf I open the \"Edit -> Preferences\" window, then the pressure sensitivity stops working until I restart the program. \n\nAlso, pressure sensitivity stops working after opening the save window (ctrl + s).\n\n\n\n" ]

[ "VSE: Ensure all operators in the Strip menu are working on the selected and not only on active strip (+unselected) \nAs it is confusing and inconsistent to have functions in the Strip menu which only works on properties of the active strip even if it is unselected, this design list is for ensuring all functions in the strip menu to work on selection. \n\n- - [x] Swap Strip: #91191 Fix: [D12441](D12441)\n- - [x] Effect menu. Fix: [D12451](D12451)\n- - [x] Movie(Set Render Size + Deinterlace) and Image(Set Render Size + Separate Images) menu entries should be moved into the source sidebar with +alt for selection. Fix: [D12464](D12464)\n- - [ ] Add Modifier in the menu needs to work on selection and is missing +alt for selected, when executed in the sidebar.\n- - [ ] Inputs menu: Swap data should go into the swap menu and the rest into Strip Source sidebar with +alt for selected. Bug report: #91350\n- - [ ] Toggle Meta and UnMeta should go into the strip sidebar, as they are only working on the active strip. Old patch: #74130\n(A checked checkbox means a fix has been submitted, but not necessarily been committed)\n\n", "updates to the Purge operator in the Outliner\nThe Purge unused IDs operator has been updated recently (2718ea80d2), it can now recursively delete all unused IDs, including indirectly unused ones, and also only affect linked or local data.\n\nThis is fully exposed in the `File -> Clean Up` menu, but the Outliner `Orphaned` view still only have one button with default (old) behavior.\n\nOptions are:\n- Keep things as they are.\n- Keep a single button, but change its behavior to `recursive purge`.\n- Change it to a menu with same options as in `File` cleanup menu.\n- Others?\n\n", "Unable to get object to stay hidden while new mesh tool is active.\nWindows 10, 1060\n\nBroken: 2.80 master (also reproduced in a month-old daily build, so not new behavior).\n\nIf you have an active tool like Add Cylinder going, and you hide another object using the eye icon in the outliner, then as soon as you touch the cylinder parameters, the hidden object becomes unhidden.\n\n1) From the default scene, Add a Cylinder to the scene and expand the tool properties in the lower left of the 3dview.\n2) Because the cylinder is hidden inside the cube, we can't easily see the effect of changing the tool parameters, so go to the outliner and click the eyeball icon associated with the cube to hide it in the viewport.\n3) Change any parameter in the cylinder tool properties pop-up in the 3dview. The cube reappears and the eyeball indicates it is no longer hidden.\n\nBasically any changes made to the Outliner visibility icons gets reverted as soon as you change any active tool property, (at least for the Cylinder tool). This at least unexpected behavior.", "Recursive Purge Orphans datablocks on file save\nFully deleting datablocks from a blend file doesn't happen as easily as most users might expect, since \"delete\" is often used in the UI when \"un-link\" is what is actually meant. This can cause a lot of confusion and uncertainty during production. Proper deletion of datablocks requires that they are first un-linked, then they can be purged via File->Clean Up->Recursive Unused Datablocks. This works beautifully, and I would like to propose adding an option to have this operation executed after existing deletion operators. For example, after deleting a collection of objects, it would then also delete everything that was used only by those objects, such as their mesh and shape key datablocks, materials, actions, textures, etc.\n\nMy previous proposal was to have an option to execute Recursive Purge only on file save, which seemed to make sense to everyone I talked to at the time. (@dr.sybren @mont29 @JulianEisel @SimonThommes ) \nI still think that solution would be a step forward, but the new proposal above would achieve the same goals in an even more foolproof way. \n\n### Use case\nCurrently, this can very easily happen:\n- Animator duplicates an overridden character. All its objects get a .001 suffix.\n- Animator deletes that copy, saves their file, and later re-opens it. Only one \"layer\" of unused objects has been cleaned, so there can still be orphan object datablocks lying around unseen.\n- Animator duplicates the character again. Now the number suffix of their objects are all over the place. Some of them have .001 and others have .002.\n\nAs they continue working and duplicating characters, the old, unused objects slowly get deleted, and the name suffixes really get all over the place. It's not nice to get your objects names all mixed up like this, as things get really confusing when trying to troubleshoot problems in a production file, since everywhere where one object references another, the mismatching suffixes give the troubleshooter anxiety and uncertainty. The only way to avoid this currently is to tell the entire production team to always run a recursive Purge after deleting anything, which is very error-prone. \n\n\n### Potential issues\n\n- ~~The current recursive purge purges Text datablocks, which is bad because they don't have the possibility of a \"Fake User\", so they should be excluded (or better yet, be included in the \"fake user\" system, and get a fake user by default). ~~ (Fixed by [D10983](D10983))\n- Actions don't have fake user enabled by default. The long standing issue of Action datablocks \"disappearing\" on users and making them lose hours of work if they forget to click Fake User would be exacerbated by this change. This could be trivially fixed by giving Actions a fake user on creation, and forcing users to clean up their unused Actions themselves.", "Resizing the Blender Window causes the interface to disappear\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 3.6.0\nBroken: 3.6.1, 4.0.0 (Metal)\nWorked: OpenGL\n\nWhen resizing the Blender window the whole UI goes blank.\n\n\n- edit the layout by removing the 3D view\n- resize the Blender window\n\nSee `resizing-window-interface-disappear.mov`.\n\n***\n\n**Original report**\n\nNo on any one project, and doesn't always happen immediately.\n\nLiterally resizing the window nothing else. I do have magnet installed for windows management, that wasn't being used in this instance.\n\nI have a multi monitor setup, 3440x1440, 2560x1440 and the MacBook's internal display active.\nOnce in this happens the UI has only reappeared once so far and requires Blender to be closed and relaunched.\n\nI had OBS open at the time, I don't have to be recording for the incident to happen.\n", "Geometry Nodes: Only re-evaluated log do update available attributes in drop-down menu\nBroken: version: 4.0.0 Alpha\n\nThis is a fairly insignificant UI bug. If the GeoNodes modifier is disabled, the list of available attributes to select in one of the inputs is not updated. For example, when a vertex group is renamed, that won't be reflected in the list, until the modifier is enabled again. Can result in a bit of confusion.\n\n1. Open attached file.\n2. Notice the GeoNode modifier is disabled.\n3. Rename the vertex group.\n4. Try assigning the renamed vertex group as the modifier's Factor input; You can't, because it won't appear in the list.\n5. Enabling the modifier updates the list again, and then all is well.\n\n", "Removing a quick favorite leaves sub-levels of enum menus open\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 3.6.2\n\nRemoving a property while the list is expanding keeps it expanded.\n\n\n1. Add to quick favorite a property with an enumeration.\n2. Call it and open it.\n3. Remove a property from quick favorites.\n\n", "Dissolve Edges should not dissolve vertices that are not previously selected\nOperating system: Win 11\n\n\nBroken: 1a44120d7175\nWorked: N/A\n\nUpdated description:\n\nThe \"Dissolve Vertices\" option from \"Dissolve Edges\" operator should not dissolve vertices that are not previously selected.\n\nThe vertex in red circle should not be dissolved in any way, no matter whether \"Dissolve vertices\" option is on or off. And this only happens when the vertex in red circle and the adjacent selected one being 3-way connected.\n\n\n\nReproduce:\n\n1. Open `109765.blend`.\n2. x > Dissolve Edges.\n3. Try enabling and disabling \"Dissolve Vertices\" option in the operator arguments panel, either way it's incorrect.\n\nExpected behaviour:\n\n\"Dissolve Vertices\" option should never dissolve the vertex circled in red.\n\n-------\n\nOriginal description:\n\nIt seems like Blender removes non connected vertices during edge dissolve. See the video and the image\n\n| | |\n|--|--|\n|  | <video src=\"attachment\" title=\"blender_mqFBR66QUe.mp4\" controls></video> |\n\n\n1. Load `bug_05072023_2041_45` file.\n2. delete the selected edges using \"X->Dissolve Edges\".\n\n", "Scaling in edit mode with individual origins and snapping activated is broken\nWin7 x64\n\nBroken: 2.76\n\nFollowing #39161. Scaling in edit mode works well with \"median\" as pivot point but with \"individual origins\" it breaks.\n\n\nIn attached file:\nScale and choose a vertex with \"ctrl\" pressed, cube seems to disappear.\nTo compare, press \"G\" and choose a vertex for snap, the cube's center is moved as a cube (also individual origins could make all selected verts move to that position making a point instead of a cube?) to that vertex.\nScale with \"median\" as pivot, it works\n[bug scale individual origins.blend](bug_scale_individual_origins.blend)\n\nSo maybe to make it consistent, make \"individual origins behave like median.\n", "AutoMerge Keyframes only deletes unselected keyframes (scaling muliple selected to zero or snapping to the playhead fails)\n\n\nLinux Ubuntu & GeForce GTX 580\n\n\nBroken: master\n\nWith \"AutoMerge Keyframes\" toggled on it simply doesn't do that, whether you're scaling keyframes or moving them around.\n\n[auto_merge.blend](auto_merge.blend)\n\nMake an armature, go to pose mode and set keyframes on the bone. Scroll forward a few frames, move the bone around (and rotate) and key it again. Do this a couple of time so you have some keys to work with.\n\nIf you select all the keys in the dopesheet editor and scale them down so some of them land on the same frame, blender doesn't automerge them. The keys seem to still exist on the same frame, as you can see in the graph editor. Even if you select all the keys and move them by one frame (which should trigger the automerge) it still doesn't merge the keyframes.\n", "GP: Time offset and Armature modifier causes glitches\nOperating system:WINDOWS10\nGraphics card:GTX1060\n\nBroken: 2.93LTS\n\n\n[#89433.blend](T89433.blend)\n\n- Open file\n- Move selected bone to left until it hits constraint, and then a bit randomly\n\nGP object will keep rotating in one direction and can be reset only by changing frame.\nSame happens when scrubbing in negative frame range.\n", "Crash (memory use after free) on freeing RigidBody world\nReproducible with current master, probably there since forever.\n\n# Steps\nWith an ASAN build:\n\n- Open `rigid.anim.blend`\n- Close Blender\n\n[rigid.anim.blend](rigid.anim.blend) \n\n(Case found while working on #86379 (When using \"Append\" rigid body objects + empty constraint, none of its constraints work.))\n", "Move Tool Todo\n## Move\n * - [ ] {icon circle color=green} Currently, distances are not well communicated while dragging, only the axis. We can make it much clearer how far you've moved your item, like so:\n\nHere, the distance moved is brighter than the rest of the axis line.\n * - [x] {icon circle color=yellow} The Redo panel for moving items should be simplified. The Constraint Axis controls should be hidden, and the Move X, Y, Z controls should always work. The current UI here is annoying to use and takes up lots of space.\n\n * - [x] {icon circle color=yellow} The tool has 3 names: 'Grab' (in the toolbar), 'Move' (inside the Redo panel), and 'Translate' (Redo panel title). It should have one name. 'Move' is the most universally understood word, that everyone will understand. The other two are ambiguous and unclear. ", "Transform & Drag Action \nWhen switching the transform tools in the toolbar, there are times when you would still like to be able to box select while gizmos are active.\n\nWe can solve this by adding a Drag Action tool option to all the transform tools:\n\n\n\nWhen set to Box Select, you can still drag in the viewport to select, while using the gizmo to move, rotate or scale.\n\nDetails:\n - This option should ideally be shared between all tools with gizmos, I think. If you set one tool to work this way, you likely want them all to\n - This works best if we add back the Transform tool\n\n", "Multires Unsubdivide Deletes Hidden Geometry\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.6.0 Beta\nWorked: ??? also a bug in 3.5\n\n**Description**\nIf you use the unsubdivide tool on the multires modifier while geometry is hidden in edit mode, the geometry that was hidden gets 'deleted' (or more like dissolved) from the mesh. It's easy to work around, but it definitely isn't the expected behavior.\n\nSelect the default cube and enter edit mode, subdivide it several times, hide part of the mesh, back to object mode and add a multires modifier, click unsubdivide, the hidden geometry is dissolved.\n\n" ]

[ "It is not possible to remove edit mode ruler\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nIt is not possible to remove rulers (Measure tool) created it edit mode. Once they are created in edit mode, they are in the scene for good\n\n1. In a new .blend file, select default cube and enter edit mode\n2. Using a Measure tool, create a new ruler\n3. Delete it using X key (Or delete, depending on keymap)\n4. Exit edit mode\n5. Enter the edit mode again\n\nResult: Deleted ruler reappears upon re-entering the edit mode.\n\nExpected: Deleted ruler stays deleted.\n", "Measure deleted are back after enter/exit edit mode\nOperating system: Mint 19\nGraphics card: NVidia 860M\n\nBroken: March 2nd of 2.80\n\nMeasure deleted are back after enter/exit edit mode\n\n* On default scene : \n* Select Measure tool\n* Add a measure\n* Clic on X to delete the measure\n* Tab to enter edit mode on cube\n* Tab to exit edit mode on cube\n* Measure previously delete is back" ]

[ "Using subdiv modifier affects normal baking performace of all objects in scene\nOperating system: Windows 10\nGraphics card: GTX 1080Ti\n\nBroken: version: 2.83 (sub 10)\nWorked: Never (2.8+)\n\n[#60428.blend](T60428.blend)\n- Open file\n- Press bake, watch memory usage\n# Remove subsurf modifier on `door_frame_low.001` object and repeat step 2\n\nBaking is much quicker and doesn't require too much RAM\n", "Sculpt mode: hide masked do not work when modifier enabled, but hidden part works with modifier.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\n\nAs title said. Hiding works with modifier but not work simultaneously as «hide masked»\nFor example, edit mode work well with mirror and hiding, hiding by faceset works well too...\n\n**Steps to Reproduce**\n- Open .blend file\n- Paint with mask brush\n- {nav Sculpt > Hide Masked} \n\nTest File:\n[#92372.blend](T92372.blend)\n[2021-10-20_18-49-00.mp4](2021-10-20_18-49-00.mp4)\n", "Curves: Edit mode transform pivot on individual origins does not work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.1.230210\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso 3.5 beta.\n\nIn curves edit mode, transform pivot on individual origins does not work.\n\nPivot on active element also does not work, but it seems curves edit doesn't have the concept of active element at all, so not sure if this is a limitation right now.\n\n[CurvesEditTransformPivot.mp4](attachment)\n\n", "Unsubdivide support for non-grid topology\nOperating system:mac os mojave 10.14.5\nGraphics card:intel iris 550\n\nBroken: d62a749fcf48\nWorked: never\n\nUnsubdive either from the edge menu or under the decimate modifier not giving expected result with many production models. This never worked well so I figured I put in a report since I haven't seen an active one.\n\nAttached blend file, unsibdivide fails more often than not, producing triangles with unsubividealbe geometry. Works in other packages though, so it's not a problem with the geo.\n\n\n[unsubdivide.blend](unsubdivide.blend)", "UDIM tiled images with generated contents dont render in Cycles\nOperating system: Windows 10 pro 64 bit, AMD Ryzen 5 3400 G with radeon vega graphics, 16 gb ram\nGraphics card: nvidia GTX 1650 super\n\nBroken: 2.91.0, 0f45cab862b8, master, 2020-11-25 \n\n\n\nworking on the new udim mode I was proving my uvs with a uv grid and when i went to try to get a render i note that when you change to cycles in the render engine the texture is lost and dont appears in the render but in eevee it works fine. the error only happen when you try to use cycles.\n\n*Open the file\n*Go to render preview mode\n*Change to cycles in the render engine section", "Inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken:\n3.2.0 Alpha 2022-05-01 a5644f9a28ea\n3.1.2 2022-03-31 cc66d1020c3b\n3.0.1 2022-01-25 dc2d18018171\n2.93.9 2022-04-19 31712ce77a6a\n2.83.19 (can't find build details)\n\nWorked: -\n\nThere's an inconsistent behavior of the Subdivide Edge Ring and Subdivide actions on meshes with shape keys.\n\nWith Subdivide Edge Ring, no matter what kind of interpolation and profile factor you use, the one applied to all other shape keys will use \"Linear\" and \"0\" respectively.\n\nWith Subdivide, if you use it on the Basis shape key, all other shape keys will inherit half of the transform of the \"smoothness\" setting, and they will be transformed in some undefined manner by the \"fractal\" setting as well. If you use it on non-Basis shape key, in addition to the described behavior with remaining shape keys, the Basis shape key will always use the default settings (smoothness and fractal = 0).\n\n**Exact steps for others to reproduce the error / sort-of-transcript of the video**\nwatch?v=s9dPcdHOlpo\nIf you use the Subdivide Edge Ring, leave the default settings, and go through the shape keys, you can see that the positions of vertices are slightly off between the current/modified shapekey and others.\nHowever, that changes when you change interpolation to \"Linear\" - then they start being the same.\nWhen you go through various options it seems that the only thing applied properly across all shape keys is the number of cuts.\nAll shape keys other-than-the-active-one seem to always be using the \"Linear\" interpolation, and profile factor = \"0\"\nFrom my tests it doesn't matter which shape key you use this action on - it will always have the same effect between the current shape key and all other.\n\nNow, there's something even weirder goin on with the regular Subdivide.\nIf we Subdivide the mesh with default settings, it will look the same in all shape keys - that's great.\nHowever, if we change something, then the mesh across shapekeys will look different.\nAs a general rule, if we Subdivide a shapekey like Key 2, then the Basis will look like it was Subdivided with the default settings instead of the chosen ones (besides the number of cuts), but all other shape keys will also be modified, just in a different way than the active shapekey.\nFor example, if we change the smoothness of our Subdivide, then other shapekeys will look just \"less modified\". If we check the coordinates of the vertices, then we can see that in Key 1 they are transformed exactly half-way to their position in Key 2.\nHowever, if we use the Fractal setting, then the results are different: The Basis is still default-Subdivided, but the vertices of Key 1 are not just halfway there to the positions of Key 1 - they're completely different.\nOn a final note, with regular Subdivide, if, instead of Subdividing Key 2 you did that to the Basis, then both Key 1 and 2 would look like Key 1 in my example. There would be no shape key that stays with default Subdivide settings.", "Crashing while viewing animation in Cycles\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 83\n\nBroken: version: 3.4.0\n\nWill crash seconds after playing animation in viewport when Cycles is selected and in render view. Both CPU and GPU crash. Does not crash when removing the Subdivision Surface Modifier so polycount may be a factor? This is a brand new Apple M1 Max computer from BestBuy with nothing else installed. Also tried initializing a render to video file and crashed as well. (Note: This is an error strictly with Apple M1 computers as I have tested it on an Apple intel MacBook Pro and it works just fine.) Thank you and happy holidays!\n\n1. Load file. It is a mesh plane with default cloth and subdivision modifiers acting on a wind force.\n2. Make sure Cycles is selected as Render Engine.\n3. Select Viewport Shading to Rendered (to view cycles render)\n4. Push play. Will crash or freeze seconds after play.\n\n[Cloth_Cycles_Crash.blend](Cloth_Cycles_Crash.blend)\n\n[Blender 3.4 Crash Report 12.13.22.rtf](Blender_3.4_Crash_Report_12.13.22.rtf)\n[Blender 3.5 Crash Report 12.14.22.rtf](Blender_3.5_Crash_Report_12.14.22.rtf)", "Xray doesn't work in wireframe shading for objects set to display as wire.\nBroken: 3.0\nWorked: \n\nXray doens't work in wireframe shading mode for objects set to display as wire.\n\n- Open .blend file\n- Change the viewport shading to wireframe.\n- Set one of the cubes to \"Display As : Wire\" in object properties->viewport display.\n- change X-ray value from `Viewport Shading` popover\n- compare the two, only one has xray effect.\n\nTest File:\n[#94802.blend](T94802.blend)", "GPU Subdivision not optimized in Weight Paint mode\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.4.0 Alpha\n\nI'm not sure if it's unimplemented/unplanned or just overlooked, so I'm here to report in case.\nWhen you have a mesh using an Armature modifier and Subdivision modifier, the Subdivision will affect performance while posing the armature but enabling GPU Subdivision will noticeably improve performance during posing and animation. \n\nHowever, if you select the armature and the mesh and go into weight paint mode, allowing you to pose the rig, the GPU Subdivision will not boost performance with the Subdivision modifier. Weight Paint Pose is slower regardless as to the Subdivision modifier, just GPU Subdivision seems to be disabled here. \n\n- Open attached .blend file\n- Make sure `GPU Subdivision` is enabled in Preferences\n- in Weight Paint Mode, pose the rig (move any bone)\n- Go to object mode, select the rig and go to Pose mode\n- Compare performance when posing the rig\n\n[#101485.blend](T101485.blend)\n", "Outliner: Sorting not working for some types in Scene display mode\nBroken: Current master\nWorked: Never\n\n\nSorting elements in the outliner only works for objects. Scenes, collections, and other types are not sorted.\n\n<img src=\"https://projects.blender.orgattachment\">", "Armature combined with subdivision incorrect normals\nOperating system: Windows 10 Pro\nGraphics card: GeForce 1050ti\n\nBroken: 2.82 (broken in a different way), 2.83.14, 2.92, 2.93 beta, 3.0 alpha\nWorked: 2.79b (important is working in 2.81)\nWhen using an armature modifier and subdivision modifier on the same mesh you get the wrong normals. If the armature is applied to the mesh then the subdivision normals are correct. The problem with the armature and subdivision together only applies if the armature is posed.\n\nThis broke between good ba1e9ae4733a and bad da6929488a64, probably 9516921c05\n\nI think that a bug has come into 2.82 a fix has been applied but it has broken it differently. So between 2.81 and 2.82 something broke, then a fix was put in that is still broken but in a different way. So 2.81 is the good version.\n\nCreate a mesh and create an armature on the mesh. Add a subdivision modifier. Make sure the armature has a pose. Show the normals.\nThe consequences will mean that the surfaces are wrong and the subsurface and general render will just look wrong.\nGood:\n\nBad:\n\n\n[blender2_79b.blend](blender2_79b.blend)\n\n[blender2_92.blend](blender2_92.blend)", "Subsurface scatering does not indirectly affect diffuse.\nHello,\nI've noticed an oddity: materials with SSS are considered totally opaque, but only for the diffuse aspect, but remain visible for glossy surfaces ;\n\n\n\n\nIt looks like a limitation, but it doesn't seem to be listed anywhere :\n\n-0df9b2c715\n-sss.html\n\nMaterials, such as ivory, jade, marble, rubber or skin, will produce variable results.\n\nIf this is a limitation, it's strange that it's only on the diffuse component and not the glossy one.\n\nSo it looks like a bug.\n\nThanks for reading, and sorry about my bad English.\n\n\nOperating system: Windows 11\nGraphics card: nvidia 2080ti\n\nBroken: 3.6\nWorked: none ?\n\n\nLoad SssPasstrought.blend , render\n\n", "Cycles adaptive subdivision tasks\nAdaptive subdivision and displacement needs some work still to be considered stable and fully supported. This task is to keep track of what needs to be done.\n\nSubdivision:\n* #49159: Normal maps do not work, no tangents are computed.\n* #49585, also #86684: Adaptive subdivision setting linking issue (Make adaptive subdivision a proper modifier setting so it is copied correctly)\n* #49431: Missing smooth (face-varying) UV subdivision.\n* #73395: Pointiness not working with subdivision\n* #73403: Missing vertex colors\n* Motion blur not working ([test file ](open?id=12qOQg-5YSj4rTwwwFU3VFQJBE7-pPRNp), report #83639)\n* Support for instances, two strategies both worth trying:\n**Object space dicing option so users can manually set it for all instances** Bin instances according to distance from camera, so we have about log(N)\n* Grid primitive to reduce memory usage\n* Optimizations, reduce memory allocations, .. (#73564 (Adaptive subdivision modifier takes to much memory ))\n* In Blender 2.8, Blender subdivides the mesh itself which leads to too much memory usage.\n* #78055: panorama dicing works poorly compared to matching perspective camera\n* #92893 (\"Persistent Data\" stops \"Adaptive Subdivision Surface\" from working properly.)\n* #97364 (Adaptive subdivision breaks attributes passed from geometry nodes to shader editor)\n\nDisplacement:\n* Fast BVH refit updates when tweaking displacement shader\n* Better results for bump from vector displacement.\n* Vector displacement tangents compatible with other software.", "Dynamic Paint sub-steps doesn't work with particles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.0 Alpha\n\nWhen using a particle system as a dynamic paint brush, the sub-steps setting of the canvas doesn't work. The sub-steps appear to work as intended with all other brush types. Whether the painting is done with vertex or texture maps doesn't seem to have an impact on the bug.\n\n* Open attached .blend\n* Bake the dynamic paint cache with a sub-steps value > 0\n* The result shows no sub-steps\n[Bug2.blend](Bug2.blend)\n", "Cycles Ray Visibility trick for motion blur on objects with animated render-ability is no longer working\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.11\n\n\nBroken: version: 2.80 (sub 74)\nWorked: 2.79b, date: 2018-03-22 14:10, hash: `f4dc9f9d68b`\n\n\nCycles motion blur artifacting is a known issue with objects that become renderable while the shutter is open.\nA workaround is to transfer the Restrict Render animation to all the Cycles Ray Visibility options at the object level.\nThis solution worked for us in production on Next Gen using 2.78, but appears to no longer work in 2.80.\n\nThe attached file contains 4 planes linked to an animated camera. The 2 on the right are just static. The one on the upper left has animated Restrict Render to reveal the plane on frame 6. The plane on the lower left has Cycles Ray Visibility revealing it on frame 6.\nSince all planes are linked to the camera and have no transformation animation, none of them should show any motion blur at all.\n\nOpen the attached file in 2.79b and render frame 6 to see that the top left plane appears blurred (it shouldn't) and the lower left plane appears correct.\nOpen the attached file in 2.80 and render frame 6 to see that both left side planes are now showing the blur artifact.[rnd.motion_blur_bug.v0003.blend](rnd.motion_blur_bug.v0003.blend)\n\n" ]

[ "Subdivision surface \nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.80\n\nBroken: version: 3.1.0 Beta\n and all versions after\nWorked: 3.1.0 Alfa\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\n\nsubdivision surface doesn't work in cycles viewport render view, and final render.\nunless it has another modifier after it, even if it isn't actually doing anything as long as it's on[the other modifier]. and Adaptive subdivision doesn't have this issue\n[SubivisionSurface_Bug.blend](SubivisionSurface_Bug.blend)", "OGL Subdiv doesn't show in cycles viewport\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.1.0 Beta\nWorked: 3.0\n\nWhen OGL Subdiv is enabled and viewport mode is set to Cycles, it shows the non subdivided version\nNotice the outline overlay is subdivided while the geo is not\n\n[OGLSubdiv.blend](OGLSubdiv.blend)\nSwitch viewport to Rendered mode", "GPU subdivision data cannot be transferred to Cycles\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0 Alpha\nWorked: Hash 79012c678499\n\nWhen the new GPU subdivision is enabled, Blender finds itself unable to have the data transferred to Cycles for rendering (in both viewport and F12 rendering). Actions on objects that disable the new evaluator (by way of creating a dummy modifier or by enabling the experimental adaptive subdivision), will allow the object to render as intended.\n\nAdd a subdivision surface modifier to the default cube (with GPU evaluation enabled) and switch to the Cycles rendered view, then try the F12 rendering. I do not think a .blend file for debugging is needed.\n\n", "GPU Subdivision surface modifier does not apply to Cycles renders \nOperating system: Linux-5.15.0-2-amd64-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.94\n\nBroken: version: 3.1.0 Alpha\nWorked: Prior to eed45d2a23\n\nWhen the GPU option is enabled for the subdivision surface modifier, it results in the subdivision surface modifier having no effect on the Cycles render.\n\n[2022-02-01 10-51-53.mp4](2022-02-01_10-51-53.mp4)\n\n1. Open preferences (From the top of Blender select `Edit -> Preferences`)\n2. In the Preferences window navigate to the `Viewport` tab.\n3. Under the `Subdivision` section in the Viewport tab, ensure `GPU Subdivision` is enabled.\n4. Select a mesh object in the scene and give it a `Subdivision Surface` modifier.\n5. Change the render engine to Cycles and render the scene with either viewport rendering or final rendering and notice that the Subdivision Surface modifier doesn't appear to be effecting the geometry of the object.\n6. Disabling `GPU Subdivision` in preferences fixes this issue.", "Cycles GPU Subdivision: bmw27 scene render artifacts in Blender 3.2.0/Master\nOperating system: Linux-5.13.0-28-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.2.0 Alpha\n\nEnable GPU Subdivision from user pref. Open and render bmw27 sample scene. \n\nMy result:\n\n\nThe problem occurs in CPU and GPU render.\n" ]

[ "`user_remap` fails silently when object is in edit mode\nBlender 3.6\n\nWay to reproduce:\n1) Create new empty blender project\n2) Select cube\n3) Enter edit mode\n4) Run the code below\n\nResults - mesh wasn't replaced and no errors occured. Expected - to either mesh to change or get some warning/error.\n\n```python\nimport bmesh\nimport bpy\n\nobj = bpy.context.active_object\n\ndata = bpy.data.meshes.new('test')\nbm = bmesh.new()\nbmesh.ops.create_monkey(bm)\nbm.to_mesh(data)\nbm.free()\n\nobj.data.user_remap(data)\nassert obj.data == data\n```\n\n", "Error \"Gizmos hidden in this view\" when trying to delete with measure tool and gizmos disabled\nOperating system: Windows 10 64 bit\n\nBroken: 2.83 release, 2.90 ec776f18ff70\nWorked: blender-2.82a-windows64\n\nIf the \"Measure\" tool is selected AND gizmos are turned off (\"Show Gizmo\", in the top right next to \"Overlays\"), trying to delete with the X Shortcut will result in the error \"Gizmos hidden in this view\".\nIf either\n* another tool is selected, or\n* gizmos are enabled\ndeleting works as expected.\n\n[delete_without_gizmo.blend](delete_without_gizmo.blend)\nOpen the file.\nHit the X key.\n\n", "Blender development todo list -- Scripting\n| Notes: |\n| -- |\n| - This is a direct dump of Scripting (without cherrypicking the [still] valid items)\n| - Changed the broken python documentation links |\n\n\n**Unstable or poorly tested**\n- [ ] BMesh operators currently use int's for enums that have undocumented values. blender/blender-addons#34914\n\nFixes that still need doing.\n**Internal API Problems**\n- [ ] Class registration needs to be reworked. as well as some internal bugs fixed.\n- [ ] RNA api has a bug where 'raw_type' defaults to INT but is not set for MFace verts in makesrna.\n- [ ] ID data returned from functions is not included unless the type is an ID itself.Returning a mesh will work but not a meshes face for eg. See bpy_rna.c - /- [ ] XXX this is missing the ID part! []/\n- [ ] Dynamic enums currently refer to invalid memory when accessed from python, we need a way for python to hold the memory until its done with the dynamic enum.\n\n**Low Priority Py API**\n- [ ] Re-Registering classes leaks memory, would be good to resolve this. (see comments in bpy_rna.c)\n- [ ] 'Safe Mode' - where writes to invalid memory are detected.\n- [ ] Implement import hooks rather than replacing import/reload pep-0302/\n\n### Python/RNA API Design TODO\n- [ ] Add a way to cancel running scripts from the user interface, with no console this becomes very problematic (Esc --> KeyboardInterrupt for example).\n- [ ] Currently there is no way to write packed images from blend files, support for this should be added to exporters. eg: image.pack_write(\"somepath.png\")\n- [ ] Addressing operators/panels/menus, should we translate all names fromSOME_MT_menu --> some.menu, ONE_PT_panel --> one.panel ? would mean the UI code could reference them by this more pythonic syntax.\n- [ ] need to decide how 2.4x api's will fit in with new apis. PyNodes, PyConstraints.\n- [ ] convenience function to get selected verts/edges/faces to prevent expensive iteration over meshes. Something like: me.verts.selected\n- [ ] Design a method to allow custom UIs to filter properties/options. Useful for Blender GE too (example: which constraints are supported (#26804). Complex matter for which rna needs to be extended?\n- [ ] Zero bytes are not supported in RNA byte string types, see blender/blender-addons#32581\n- [ ] Better python API and undo stack integration, see #38386\n\n**Inconsistencies**\n- [ ] bpy.ops.mode_set(...) has different mode-names than bpy.context.mode. E.g. TEXTURE_PAINT vs PAINT_TEXTURE''CoDEmanX:'' Getting mode from bpy.context.mode for mode_set() is inappropriate, use '''bpy.context.object.mode''' instead!\n- [ ] bpy.ops.object.move_to_layer() takes a boolean array of 20 elements (like in Blender GUI), but most functions require 32 elements. bpy.ops.object.add() for example.\n- [ ] bone.matrix returns a matrix, but requires a list when assigning to it. This also goes for some of the other matrix attributes of bone, editbone and posebone. [appears to be resolved as of 2.67?]\n- [ ] the term 'size' is used incorrectly in some cases, where it should be 'scale' instead. Review and correct: search.html?q=size&check_keywords=yes&area=default\n- [ ] keyframe_insert(), options for insert or replacing existing keyframes, threshold for detecting doubles see: bpy.types.bpy_struct.html#bpy.types.bpy_struct.keyframe_insert\n- [ ] The ID data block path returned by RNA_path_full_ID_py (rna_access.c) for node trees only works for node groups, which are stored as true ID data blocks in bpy.data.node_groups. For material/compo/texture nodes which are part of Material/Scene/Texture respectively the function can not determine the correct path. Best solution would be to get rid of nested ID data blocks altogether blender/blender-addons#35720\n\n### Python RNA access\n- [ ] Remove mesh vertices / edges / polygons (without bmesh module)\n- [ ] Shorthand for active vertex / active edge (bmesh module)\n- [ ] Active vertex / edge index for meshes (like Mesh.polygons.active)\n- [ ] Remove Shape Key\n- [ ] Remove Curve Points\n- [ ] Particle edit mode\n- [ ] Start/stop the physics sim\n- [ ] Sculpt mask custom data\n- [ ] Add / remove rigid body + constraints + world\n- [ ] Add / remove transform orientation\n- [ ] Add / remove Text curve object Textboxes\n- [ ] Add / remove Particle Systems\n- [ ] Sequencer, ability to load and images blender/blender-addons#40663\n- [ ] Pixels and resolution are not available with multilayer EXR or Render Result images #53768\n\n### Python Console\n- [ ] Append to (and remove from?) SpaceConsole .history and .scrollback\n- [ ] input() is not supported #40592\n\n### General todo items\n- [ ] Operator redo (toolbar) could also change the last InfoWindow print of the python operator equivalent.\n- [ ] mathutil.geometry.intersect_point_quad_2d works inpredictable for non-concave or quads with singularity edges #30831\n- [ ] modules/rna_xml.py: BoolVectorProperty and CollectionProperty issue blender/blender-addons#32882\n- [ ] Drivers should be able to access '''self''' for bones and objects.\n- [ ] Add the ability to report() without an operator, internally use CTX_wm_reports(C), See: operator-report-outside-operators\n", "Shader not working on Mac blender 3.5 - works in Windows\nOperating system: macOS-13.3-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0\n\nI have been trying to install the Weight Paint Tools paid addon weight_paint_tools?layout=profile&recommended_by=library\n\nThis worked fine for years, up till 3.5, now it crashes upon activation. The developer has attempted to update it for metal, but it still wont work. He's sent me a simplified script that he says should work without errors.. but still errors out. See attached blend file.\n\nRun the script\n\n\nRun the script\n\n", "Node Tools not exposed in the Preferences > Keymap\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon (TM) R9 380 Series ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.35.02 27.20.1034.6\n\nBroken: version: 3.3.1\n\n**Short description of problem**\nFor the Node Editor keymap, there are hidden Node Tool keymaps that exist within Blender (they are only visible via search filter) that override the keymaps that are exposed, and can't be customized properly.\n\n\n\nThis report stems from this bug report:\nT102422 ", "Importing a keymap with a default name makes a non deletable copy\nBroken: version: 3.2.1\n\nAfter importing a keymap configuration with the name \"Blender\" it created a copy of the default setting that is impossible to remove from the UI at least.\n\n\n\n\n\nImport a keymap setting with a default name\n\n\n**Fix**\nDelete keymap configuration from the user folder directly \n\n> \\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\scripts\\presets\\keyconfig\n\n\n", "Metal: Assert is triggered when drawing a Batch with an attribute format different from the type used in the Shader\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: [couldn't check yet]\n\nI'm not sure how serious the problem is.\nEven with the assert, the drawing seems to work.\nBelow is a small code that demonstrates the problem:\n\n```python\nimport bpy\nimport gpu\nfrom gpu.types import (\n GPUBatch,\n GPUIndexBuf,\n GPUVertBuf,\n GPUVertFormat,\n)\n\ndef draw():\n x1=0\n y1=0\n x2=bpy.context.region.width\n y2=bpy.context.region.height\n\n # The size of each color in `vertex_colors` needs to be 4 and\n # the size of each vector in `vertices` needs to be 3\n # otherwise a assert will be triggered the Metal backend.\n vertex_colors = ((1.0, 0.0, 0.0, 1.0), (1.0, 1.0, 1.0, 1.0))\n vertices = ((x1, y1), (x2, y2))\n\n shader = gpu.shader.from_builtin('POLYLINE_SMOOTH_COLOR')\n shader.uniform_float(\"viewportSize\", gpu.state.viewport_get()[2:])\n shader.uniform_float(\"lineWidth\", 5)\n\n vbo_format = GPUVertFormat()\n vbo_format.attr_add(id='color', comp_type='F32', len=len(vertex_colors[0]), fetch_mode='FLOAT')\n vbo_format.attr_add(id='pos', comp_type='F32', len=len(vertices[0]), fetch_mode='FLOAT')\n\n vbo = GPUVertBuf(vbo_format, len(vertices))\n vbo.attr_fill('color', vertex_colors)\n vbo.attr_fill('pos', vertices)\n\n batch = GPUBatch(type='LINE_STRIP', buf=vbo)\n batch.draw(shader)\n del batch\n\n\nbpy.types.SpaceView3D.draw_handler_add(draw, (), 'WINDOW', 'POST_PIXEL')\n\n```\n\nNote that the dimension of the vertices is 2D.\nIf converted to 3D (by adding a z value), the assert is no longer triggered.\n\n- Open attached .blend file.\n- Run the script in the text editor\n- Update the 3D view (by zooming for example)\n\n[gpu_metal_assert__bug.blend](attachment)\n\n", "Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than [\"path/to/blender.exe\"]\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.5.1\n\nBlender crashes when calling `ArgumentParser.parse_args()` if `sys.argv` is anything other than `[\"path/to/blender.exe\"]`\nI discovered this bug while trying to run a script using the `exec()` function. Any script that uses argparse makes blender crash.\n\nYou can run this code\n```Py\nimport argparse\nimport sys\nimport bpy\n\nsys.argv = [bpy.app.binary_path]\nsys.argv.append(\"--some_arg\") # Comment this line and everything works fine\n\nparser = argparse.ArgumentParser()\nargs = parser.parse_args()\n```\n\n", "Unable to export/import EXR files after doing `import bpy` and when using the multiprocessing in Python (Blender freezes)\nI am trying to render depth maps and surface Normals using Cycles and store the results in OpenEXR format using nodes. I set up the nodes as follow using Blender's Python API:\n\n\n```\n#blenderClass.py\nimport importlib\n\nclass Blender(object):\n def __init__(self):\n self.bpy = importlib.import_module(\"bpy\")\n self.scene = self.bpy.context.scene\n self.scene.render.use_sequencer = False\n self.scene.display_settings.display_device = 'sRGB'\n\tself.scene.view_settings.view_transform = 'Raw'\n\tself.scene.sequencer_colorspace_settings.name = 'Raw'\n self.scene.render.engine = 'CYCLES'\n self.scene.use_nodes = True\n\tself.setupRenderNodes()\n\n def setupRenderNodes(self):\n\t\t\n\tfor node in self.scene.node_tree.nodes:\n\t\tself.scene.node_tree.nodes.remove(node)\n\trenderNode = self.scene.node_tree.nodes.new('CompositorNodeRLayers')\n\n\t# Depth map\n\tself.depthOutputNode = self.scene.node_tree.nodes.new('CompositorNodeOutputFile')\n\tself.depthOutputNode.format.file_format = 'OPEN_EXR'\n\tself.depthOutputNode.format.color_depth = '32'\n\tself.depthOutputNode.format.color_mode = 'RGB'\n\tself.depthOutputNode.format.exr_codec = 'ZIP'\n\tself.depthOutputNode.base_path = 'somePath/'\n\tself.depthOutputNode.file_slots[0].path = 'fileNameDepth#'\n\n\t# Link\n\tself.scene.node_tree.links.new(renderNode.outputs[2], self.depthOutputNode.inputs[0])\n\n def render(self, objPath):\n self.bpy.ops.import_scene.obj(filepath=objPath)\n self.bpy.ops.render.render(write_still=True)\n```\n\n```\n#main.py\nfrom multiprocessing import Process\nimport blenderClass import Blender\nblender = Blender()\n\nobjPaths = ['obj1.obj', 'obj2.obj', 'obj3.obj', 'obj4.obj']\n\nprocList = []\nfor path in objPaths:\n proc = Process(target=blender.render, kwargs={'objPath': path})\n procList.append(proc)\n proc.start()\n\nfor job in procList:\n job.join()\n```\n\nThe problem is when I do bpy.ops.render.render(write_still=True) Blender freezes and the results are not saved on disk. However, if I change OPEN_EXR_MULTILAYER and OPEN_EXR to PNG and change the color_depth to '16' everything works and I get the rendering results on disk. Note that I do not change any of my rendering engine settings like tile size, resolution etc. Does anyone know why Blender freezes and the rendering results are not on disk when using OpenEXR?\n\nThe strange thing is everything works normally when running Blender with GUI and setup the nodes and rendering engine the same way. It would be also useful if someone can try this and let me know if things work fine on their side.\n\nI'm not sure if this has something to do with the problem that I'm facing but I have compiled Blender manually and import it as a module in the Python installed on my machine. Here are the CMake settings I used to compile Blender 2.79b from source:\n\n\n```\ncmake blender \\\n -DCMAKE_INSTALL_PREFIX=/usr/lib/python3/dist-packages \\\n -DWITH_INSTALL_PORTABLE=OFF \\\n -DWITH_PYTHON_INSTALL=OFF \\\n -DWITH_PYTHON_MODULE=ON \\\n -DPYTHON_SITE_PACKAGES=/usr/lib/python3/dist-packages \\\n -DPYTHON_VERSION=3.5 \\\n -DWITH_OPENAL=ON \\\n -DWITH_CODEC_AVI=ON \\\n -DWITH_MOD_OCEANSIM=ON \\\n -DWITH_CODEC_FFMPEG=ON \\\n -DWITH_SYSTEM_GLEW=ON \\\n -DWITH_FFTW3=ON \\\n -DWITH_OPENCOLORIO=ON \\\n -DWITH_GAMEENGINE=OFF \\\n -DWITH_PLAYER=OFF\n```\n\nUpdate: I experience the same behavior with Blender 2.78 and 2.79, compiled with the same exact settings above.\n", "Regression: Importing of collada model with instances became a LOT slower since 2.80 (practically freezing)\nOperating system: windows 10\nGraphics card: geforce gtx 1070\n\nBroken: blender 3.4.1\nWorked: 2.80\n\nImporting of collada model makes Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\n- import attached collada file\n- Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\nLink to model file:\n\nCruisn-Exotica-arcade-game-Dual\n\n[doubleexotica.zip](doubleexotica.zip)", "Microsoft store: Blender cannot be used in terminal\nWindows 11\n\nBroken: 3.4\nWorked: 3.3\n\n**Short Description**\nEver since blender 3.4 released, I have been unable to use blender in the command line. Running just the command \"blender\" gives error 0xc0000022 and whenever I try to run any actual command like \"blender -b untitled.blend -a\" nothing happens. I have never had any issues like this in versions prior to 3.4. I am running the Microsoft store version.\n\nIssue only happens with blender from Microsoft store\n\n**Steps to Reproduce**\n * Assuming that blender is already in your system path, which it should be by default,\n * open a terminal in absolutely any folder;\n * run absolutely any blender command;\n * for example, run \"blender -E help\"\n\n- - -\n!!For now, workaround is to type \"blender-launcher\" instead of \"blender\" to launch blender from command line (but that won't accept any arguments)!!", "Add-On: Material Utilities - Icon Id error\nOperating system: Linux-6.3.5-arch1-1-x86_64-with-glibc2.37 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.5.1\nWorked: never?\n\nIn certain situations the Material Utils menu will not list a newly created material.\n\n\n1. New scene.\n2. Assign material (with Material Utils menu) *not* having materials properties panel open.\n3. In shading editor, object : Drag and drop texture, hook up to color.\n4. Material Utils fails to list newly created material.\n5. Error message in console:\n```\nTraceback (most recent call last):\n File \"/usr/share/blender/3.5/scripts/addons/materials_utils/menus.py\", line 58, in draw\n icon_value = material.preview.icon_id)\n ^^^^^^^^^^^^^^^^^^^^^^^^\nAttributeError: 'NoneType' object has no attribute 'icon_id'\nTraceback (most recent call last):\n File \"/usr/share/blender/3.5/scripts/addons/materials_utils/menus.py\", line 58, in draw\n icon_value = material.preview.icon_id)\n ^^^^^^^^^^^^^^^^^^^^^^^^\nAttributeError: 'NoneType' object has no attribute 'icon_id'\n```\n\nNote: Changing the line to:\n`icon_value = layout.icon(material))`\nfixes the issue for me. fwiw.", "Eyedropper picker Afected by retopology overlay\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: \n\nBroken: version: 4.0.0 Alpha\n\n\nUsing the Eyedropper Data-Block wouldn't pick visible objects if edit mode and retopology overlay are active\n\n1. Enter edit mode with the default cube.\n2. Activate retopology overlay\n3. Enter in the view tab in the n-panel\n4. Use the Eyedropper Data-Block and you won't be able to pick the object, only if you are at the origin of the object.\n\n", "OBJ: support importing loose points (point clouds) when mesh data is also present\nOBJ importer ignores pointclouds written by OBJ exporter in case if exported objects contain edges or faces.\n\nOBJ export of a Blender objects contain faces, loose edges and loose vertices (as pointclouds). Pointcloud/Loose vertices in OBJ format are written as vertices that are listed but unused in mesh data which is specific for OBJ file format, but makes OBJ importers ignore them which leads to imported data incompleteness.\n", "Crash choice asset library\nOperating system: Win 10\nGraphics card: RX460 2gb\n\nBroken: (3.2)\nWorked: (3.0)\n\n[Tests.zip](Tests.zip)\n\n- Extract archive and add `...\\Tests\\Test Asset\\` path to asset libraries\n- Open Asset library blend file\n- Open New file\n- Change any editor to Asset Browser\n# List contents of `Test Asset` library\n\nIt should crash.\nSometimes, omitting step 2 would prevent crash, but no assets would be shown.\nAlso omitting `tests` folder somehow prevented the crash, \n\nCrash log:\n[P3143: (An Untitled Masterwork)](P3143.txt)\n```\n# Blender 3.4.0, Commit date: 2022-08-14 18:40, Hash 659b63751d63\nbpy.context.space_data.params.asset_library_ref = 'Test Asset' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : UNKNOWN EXCEPTION\nException Address : 0x00007FFF3F66D759\nException Module : KERNELBASE.dll\nException Flags : 0x00000001\nException Parameters : 0x4\n\tParameters- [x] : 0x0000000019930520\n\tParameters- [x] : 0x000000FB7C5FD460\n\tParameters- [x] : 0x00007FF678278398\n\tParameters- [x] : 0x00007FF66CA80000\n\n\nStack trace:\nKERNELBASE.dll :0x00007FFF3F66D6F0 RaiseException\nVCRUNTIME140.dll :0x00007FFF283E63F0 CxxThrowException\nblender.exe :0x00007FF672BC42D0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC36C0 nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_string<char,std::char_traits<char\nblender.exe :0x00007FF672BC82B0 blender::io::serialize::JsonFormatter::serialize\nblender.exe :0x00007FF66E27B970 blender::ed::asset::index::AssetIndexFile::write_contents\nblender.exe :0x00007FF66E277D40 blender::ed::asset::index::update_index\nblender.exe :0x00007FF66E653B90 filelist_readjob_list_lib\nblender.exe :0x00007FF66E654370 filelist_readjob_recursive_dir_add_items\nblender.exe :0x00007FF66E653710 filelist_readjob_asset_library\nblender.exe :0x00007FF66DB341A0 do_job_thread\nblender.exe :0x00007FF672E5A810 _ptw32_threadStart\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThreads:\nThread : 00000448\nntdll.dll :0x00007FFF41D2C620 ZwDelayExecution\nblender.exe :0x00007FF672B3A220 BLI_thread_is_main\n\n\nThread : 000069ac\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003130\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069cc\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000054bc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000026c0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008788\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000aa4c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000608c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009c7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008d78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029c4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009918\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000162c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001478\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000040b4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000036d0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003468\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007444\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005208\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000059e4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a018\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000085a8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b1ac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000921c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005544\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad94\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067e0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000401c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b360\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008b38\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005884\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003334\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008c60\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a2e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nnvoglv64.dll :0x00007FFE819D057C Symbols not available\n\n\nThread : 00009be0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFF3F690C30 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003f9c\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007978\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ace0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ada4\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFF3012457B Symbols not available\n\n\nThread : 00009dbc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005f9c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009dac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000405c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000834c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000099e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00006284\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005ec8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a8fc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003240\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00000a10\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000082dc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000196c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004374\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007dec\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004294\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000559c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a90\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004cc8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000055f8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069a4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005c40\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001a80\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004308\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000081c8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b0d4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004bc0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009d28\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008010\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF66CA80000 3.4.0.0 blender.exe C:\\Users\\John\\Desktop\\blender-3.4.0-alpha+master.659b63751d63-windows.amd64-release\\blender.pdb \n0x00007FFF41C90000 10.0.19041.662 ntdll.dll \n0x00007FFF40620000 10.0.19041.662 KERNEL32.DLL \n0x00007FFF3F640000 10.0.19041.662 KERNELBASE.dll \n0x00007FFF40C70000 10.0.19041.546 WS2_32.dll \n0x00007FFF41310000 10.0.19041.662 RPCRT4.dll \n0x00007FFF41170000 10.0.19041.685 USER32.dll \n0x00007FFF1D640000 tbb.dll \n0x00007FFF3FCC0000 10.0.19041.662 win32u.dll \n0x00007FFF41940000 10.0.19041.685 GDI32.dll \n0x00007FFF1D600000 tbbmalloc.dll \n0x00007FFF3FAB0000 10.0.19041.685 gdi32full.dll \n0x00007FFF3FA10000 10.0.19041.546 msvcp_win.dll \n0x00007FFF3F910000 10.0.19041.546 ucrtbase.dll \n0x00007FFF417D0000 10.0.19041.610 ADVAPI32.dll \n0x00007FFF406E0000 7.0.19041.546 msvcrt.dll \n0x00007FFF41980000 10.0.19041.662 sechost.dll \n0x00007FFF3FED0000 10.0.19041.662 SHELL32.dll \n0x00007FFF283E0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFF3AE70000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFF40F00000 10.0.19041.546 SHLWAPI.dll \n0x00007FFEC90D0000 14.29.30139.0 MSVCP140.dll \n0x00007FFF3FC70000 10.0.19041.546 CFGMGR32.dll \n0x00007FFF36DA0000 10.0.19041.488 dbghelp.dll \n0x00007FFF3FBC0000 10.0.19041.662 bcrypt.dll \n0x00007FFF40CE0000 10.0.19041.546 ole32.dll \n0x00007FFF41470000 10.0.19041.662 combase.dll \n0x00007FFEC8180000 10.0.19041.546 OPENGL32.dll \n0x00007FFF41440000 10.0.19041.546 PSAPI.DLL \n0x00007FFF41A20000 10.0.19041.662 shcore.dll \n0x00007FFF3FEA0000 10.0.19041.546 IMM32.dll \n0x00007FFEB74B0000 9.0.0.0 openvdb.dll \n0x00007FFEC5BE0000 59.16.100.0 avformat-59.dll \n0x00007FFEB4FB0000 59.18.100.0 avcodec-59.dll \n0x00007FFF1D5D0000 59.4.100.0 avdevice-59.dll \n0x00007FFF40FC0000 10.0.19041.546 OLEAUT32.dll \n0x00007FFEC9030000 6.4.100.0 swscale-6.dll \n0x00007FFEC5A00000 57.17.100.0 avutil-57.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFEC5190000 1.21.1.0 OpenAL32.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFEC29E0000 2.0.20.0 SDL2.dll \n0x00007FFF39630000 libgmpxx.dll \n0x00007FFEC0D70000 3.10.2150.1013 python310.dll \n0x00007FFF40780000 10.0.19041.546 SETUPAPI.dll \n0x00007FFF300E0000 tbbmalloc_proxy.dll \n0x00007FFF31280000 6.10.19041.488 COMCTL32.dll \n0x00007FFF1C490000 10.0.19041.1 AVIFIL32.dll \n0x00007FFF39120000 10.0.19041.546 VERSION.dll \n0x00007FFF3D210000 10.0.19041.546 dwmapi.dll \n0x00007FFF1C460000 10.0.19041.546 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFF27EE0000 10.0.19041.546 Secur32.dll \n0x00007FFECB6B0000 4.3.100.0 swresample-4.dll \n0x00007FFECBF00000 10.0.19041.1 AVICAP32.dll \n0x00007FFF2EBF0000 10.0.19041.546 WINMM.dll \n0x00007FFF20660000 10.0.19041.1 MSACM32.dll \n0x00007FFECB5D0000 10.0.19041.1 MSVFW32.dll \n0x00007FFF24F20000 10.0.19041.1 winmmbase.dll \n0x00007FFF3F280000 10.0.19041.662 SSPICLI.DLL \n0x00007FFF3D240000 10.0.19041.546 kernel.appcore.dll \n0x00007FFF3D520000 10.0.19041.662 windows.storage.dll \n0x00007FFF3EE40000 10.0.19041.662 Wldp.dll \n0x00007FFF3CE80000 10.0.19041.610 uxtheme.dll \n0x0000022043090000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFF3F300000 10.0.19041.546 profapi.dll \n0x00007FFF41880000 2001.12.10941.16384 clbcatq.dll \n0x00007FFF38BE0000 10.0.19041.546 MMDevApi.dll \n0x00007FFF3F180000 10.0.19041.546 DEVOBJ.dll \n0x00007FFF38EF0000 10.0.19041.662 AUDIOSES.DLL \n0x00007FFF3E980000 10.0.19041.546 powrprof.dll \n0x00007FFF3E840000 UMPDC.dll \n0x00007FFF41AD0000 10.0.19041.662 MSCTF.dll \n0x00007FFF39850000 10.0.19041.662 AppXDeploymentClient.dll \n0x00007FFE80E80000 31.0.15.1640 nvoglv64.dll \n0x00007FFF3AE30000 10.0.19041.546 \n```\n\n\n - The conditions have been changed, but the error is still present. -----------------------------------------------------------" ]

[ "Import Error FBX OBJ X3D\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro RTX 4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 1)\nWorked: (tested) version: 2.82 (sub 6)\n\nBlender will not import three (3) file types: fbx, obj, x3d. They will return an error. \nTests include one (1) file from Autodesk Fusion (fbx and obj), and one (1) file created in blender (default cube), exported from blender to various file types.\nWorked: (tested) dae, abc, ply, stl, glb\nError Given: \nFBX:\n\"\nTraceback (most recent call last):\n```\nFile \"/media/toast/HighGround/Programs/Blender 2_8/blender-2.83-5325bc3fb629-linux-glibc217-x86_64/2.83/scripts/addons/io_scene_fbx/__init__.py\", line 217, in execute\n if import_fbx.load(self, context, filepath=path, **keywords) == {'FINISHED'}:\n```\nTypeError: load() got an unexpected keyword argument 'hide_props_region'\n\nlocation: <unknown location>:-1\n\"\n\nOBJ:\n\"\nTraceback (most recent call last):\n```\nFile \"/media/toast/HighGround/Programs/Blender 2_8/blender-2.83-5325bc3fb629-linux-glibc217-x86_64/2.83/scripts/addons/io_scene_obj/__init__.py\", line 146, in execute\n return import_obj.load(context, **keywords)\n```\nTypeError: load() got an unexpected keyword argument 'hide_props_region'\n\nlocation: <unknown location>:-1\n\"\n\nX3D:\n\"\nTraceback (most recent call last):\n```\nFile \"/media/toast/HighGround/Programs/Blender 2_8/blender-2.83-5325bc3fb629-linux-glibc217-x86_64/2.83/scripts/addons/io_scene_x3d/__init__.py\", line 79, in execute\n return import_x3d.load(context, **keywords)\n```\nTypeError: load() got an unexpected keyword argument 'hide_props_region'\n\nlocation: <unknown location>:-1\n\"\n\nUsing a blank default file, create a mesh cube. File/Export/(fbx, obj, or x3d). Then, File/Import/(fbx, obj, x3d). Receive error.\n\n**Notes**\nThanks for all the great work you people do!\n\n\n", "Import (OBJ, FBX) fails\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.83 (sub 1)\nWorked: about week ago.\n\n\nTrying to Import FBX or OBJ object causes following error message:\n\n------------------------------------------\n\n```\nFile \"C:\\Users\\user\\VirtualBox VMs\\Windows\\Build\\Release\\2.83\\scripts\\addons\\io_scene_obj\\__init__.py\", line 146, in execute\nreturn import_obj.load(context, **keywords)\nTypeError: load() got an unexpected keyword argument 'hide_props_region'\n```\n\n```\nlocation: <unknown location>:-1\n```\n\n-------------------------------------------\n\n\n1. Open Blender\n2. Import obj or fbx (For example. export the default cube and import that)\n3. Error and fails to import.\n\n" ]

[ "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "Motion blur artifacts on complex object animation (reproducable)\nOperating system: win10\nGraphics card: 2070super\n\nBroken: (example: 2.83.4, 2.92.0alpha)\n\n\n**motion blur gives strange artifacts in some frames.**\n\n[bug_motion_blur.blend](bug_motion_blur.blend)\n\n\nIn the attached file, this happens on frames 9 and 20. Bug reproducable", "Asset Browser: Material preview with black background when Cycles is disabled\nBroken: version: 3.0.0, 3.4.0\nWorked: Never\n\nWhen a scene was saved with Cycles but I disable the Cycles add-on the material previews get a black background.\n\n* Disable Cycles add-on.\n* Click on any (e.g., the Yellow) material asset and update its preview.\n[black_preview.blend](black_preview.blend)\n", "Some Cycles nodes are active when muted (RGB To BW, Math, vector Math, Separate RGB)\nWin10 64bit\n\nBroken: 2.79\n\nRGB To BW node is active when muted\n\nOpen file and render\n[RGB_BW.blend](RGB_BW.blend)\n\n", "ColoRamp value change from 0.501 to higher value results in slowdown and shading error\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nColoRamp value change from 0.501 to 0.502 as input to density results in slowdown and shading error for Principled Volume Shader.\n\nOpen attached .blend\nChange viewport to Rendered\nChange ColoRamp from 0.501 to a higher value\nRender speed is dramatically reduced and Volume Shader is incorrectly much brighter\n\n[ColorRamp bug.blend](ColorRamp_bug.blend)\n", "EEVEE: User preference settings (anisotropy, texture size limit) affect rendering\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n[Viweport texture limit size affects eevee rendering.]\n\nWhen I change the \"texture limit size\" setting it also limits the size of the texture in the render.\nAs the setting is in the \"viewport\" tab I believe it should only affect the viewport, not the rendering.\n\n", "Cycles: Cycles Alpha Representation is incorrect on some PNG files when loaded from disk compared to packed in the file\nOperating system: macOS-13.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple `M1` Pro Apple 4.1 Metal - 83\n\nBroken versions: \n3.3\n3.4\n3.5.0 Alpha\nWorked: 3.2\n\nA certain mix node setup that I found in the Spring demo file results in extremely bright outputs. I could only reproduce the issue in Blender 3.3 and higher. The issue isn't there in Blender 3.2 or lower. I could also only reproduce this issue in Cycles.\n\n\n\n1. Download the attached .zip file, extract it, and open it. It's an extremely simplified version of the `Spring` demo file from the Blender foundation.\n2. Enter Cycles rendered viewport. Notice how the hand is really bright. This is caused by the output of the `mix node` found in the material `MAT_spring.hands` on the hands.\n3. Test the EEVEE rendered viewport. Notice the issue isn't there. Test Blender 3.2 or older and notice the issue isn't there.\n\n[Spring Bright Hand Issue.zip](Spring_Bright_Hand_Issue.zip)\n\nExtra note: If the image texture that's causing the issue is packed into the .blend file, and the file is re-opened, then the issue goes away.", "Eevee Incorrect rendering of the volume\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.4.0 Alpha\n\n\n\n[bug_volume_eevee.blend](bug_volume_eevee.blend)\n", "Adaptive Sampling Noise Threshold strange behaviour on Ambient Occlusion bake\nOperating system: Windows 10\nGraphics card: RTX 2080\n\nBroken: 3.6\nWorked: 2.9 (No noisy regions, but I'm not sure if the threshold is even working)\n\nStrange noise regions appear on baked ambient occlusion map. They are not related to geometry, and not related to illumination, since even the light AO regions appear noisy. Disabling adaptive sampling or changing the threshold to extremely small values removes the issue. Values for the noise threshold look inadequate in these regions. Setting it to 0.01 gives around 27 out of possible 256 light difference between adjacent pixels in HSL color. In regions with reduced noise, the level looks similar to what it should be, you can see both on the image below. The noise disappears when threshold is turned off, so it's not related to maximum samples count. Same issue does not appear on baking direct or indirect light and the noise level seems adequate. It's not related to denoiser, since it's not working in baked maps (unfortunately).\n\nIt's hard to imagine synthetic scene in which the situation will repeat itself. In the attached scene, you just need to click the bake button and see the results. Try changing the Noise Threshold values or disabling it. You can change AO map texture size to make baking happen faster.\n\n", "HDRI Preview Spheres appear in surface reflections\n\n\nBroken: version: 2.82 (sub 7)\nMaster\n\nWhen using material shading and overlays in the viewport, the gizmo at the bottom-left corner (sphere displaying the environment map used for preview) is reflected by shiny surfaces in the 3D world, despite technically being a part of the UI. Using the icon to show / hide overlays affects this, the reflection also disappears when overlays are hidden.\n\nShould work in any setup, if there are issues replicating this let me know and I'll extract the relevant part from my project's blend file. Just add a plane, lower its material roughness so it's shiny, move the view upward so the overlays appear under it, and you should see the strange reflection.\n\n\n\n[HDRI_reflected_in_viewport.blend](HDRI_reflected_in_viewport.blend)", "Stucci noise texture ignores all color settings\nOperating system: Windows 10 Pro N (unlicensed so far :( )\nGraphics card: AMD 6800 XT\n\nBroken: 3.0.0\nWorked:\n\nWhen using Stucci noise as texture for density of particles, the colors properties of the texture do not apply. F.x. setting contrast to 0.1 or 1.0 makes no difference.\n\n\n\n\n\nMake a plane. Add particles. Add texture to particles. Use Stucci noise. Set as density for particles. Try to change contrast.\n[GrassyMeadow.blend](GrassyMeadow.blend)", "Cycles: Volumes in the world shader behave strangle with some textures\n**System Information:**\nOperating system: Linux-5.14.0-1-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01\n\nBroken: version: 3.0.0 Alpha, and every version between master at 2.81 (That is how far I tested).\nWorked: Unsure\n\n**Short description of error:**\nWhen using certain procedural textures in the volume output of the world shader in Cycles, you get unexpected results.\n\n**Exact steps for others to reproduce the error:**\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. In the `World Shader`add a `Magic Texture` node and connect one of the outputs to the `Volume` socket on the `World Output` node.\n5. You will noticed that in the viewport you can see the `Magic Texture` is projecting light onto objects in the scene, but you can't see the `Magic Texture` directly.\n6. Place a `Color Ramp` node between the `Magic Texture` and the `World Output` nodes. Now you can see the `Magic Texture` in the viewport.\n\nAnother test:\n1. Create a scene in Cycles.\n2. Change to the rendered viewport.\n3. Open a shader editor and change to the `World` shader and delete the `Background` node.\n4. Add a `Noise Texture` node and connect an output to the `Volume` socket on the `World Output` node.\n5. Notice that you can see the impact the `Noise Texture` is having on the scene, but you can't see the `Noise Texture`\n6. Place a `Color Ramp` between the `Noise Texture` and the `World Output` nodes. You still can't see the `Nosie Texture` in the scene.\n7. Place a `Volume Scatter` node in the `World Shader`, connecting the output to the `Volume` socket on the `World Output` node and connect the output of the `Color Ramp` node to the `Density` input of the `Volume Scatter` node. You can now see the noise texture in the volume if you have a light in your scene.\n8. Select the left most handle (the handle that is black) in the `Color Ramp` node and drag it closer to the position `0.5`. You will see the results you expect until you reach the position `0.5` where the volume will seem to disappear from your scene. Yet when you look at objects in the scene, the light reaching them is still affected by a volume shader you can't see.\n\nHere's a video demonstrating this:\n[Volumetrics not visibile in viewport in certain sitautions.mp4](Volumetrics_not_visibile_in_viewport_in_certain_sitautions.mp4)", "Baking Procedural Wave Textures\nOperating system: Win10\nGraphics card: Nvid 2080ti / 3090 \n\n3.4 (and others)\n\nCannot bake these textures correctly. \n\nCreate an object. \nAdd a wave texture, set it to uv, and scale it to show many even lines. \nAdd a color ramp to tighten those lines, setting it to constant. \nPlug this into the bump/normal to make raised lines. \nNow bake this. \n\nThe lines will be a broken mess most of the time. I have tried almost every trick I can find/think of, and nothing makes this better. \n\nI am not sure it's a bug, but it is certainly a problem.\n\n", "Avoid graphical glitches during threaded preview generation\nWhen previews are generated using an OpenGL engine, there can be a number of glitches until the preview is done. That's because some data is accessed/modified that is not thread safe. E.g. `object_preview_render()` modifies `U.pixelsize`. I think other glitches are caused by overriding the active theme in `ED_view3d_draw_offscreen()` - although when I avoided this some time ago for similar work on threaded offscreen drawing for VR, this didn't solve the color flickering.\nThe active theme should probably use thread local storage.\n\nBesides that, the preview generation should be thread safe with OpenGL:\n* It uses the draw-manager's own context, which is mutex protected.\n* The non-thread-safe immediate mode API is not used inside the draw-manager.\n* The draw-manager already has workarounds for GPU driver issues with threaded drawing.\n\nA note: We could also speed up Eevee preview generation significantly by using viewport render quality, not final render quality. The `_imbuf` offscreen rendering functions don't expose the `is_image_render` option for that, which they probably should.", "Selected object color is weird in wireframe mode if the object color isn't single.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 3.0.0 Alpha\n\nOutline overlay seems to be drawn under wireframe.\n\n[#91619.blend](T91619.blend)\n\nImmediately visible in provided file." ]

[ "Voronoi texture incorrectly displayed in the viewport Cycles\nWindows10 x64, intel hd graphics 2000\n\nBroken: 2.78rc1 0e5089c - 2.78 a267710\n\nProcedural texture Voronoi (coloring Cells and Intensity) incorrectly displayed on an object in the viewport shading mode Cycles material.\n\nIntensity:  \nCells: \n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\n 1. Use a default blender scene.\n 2. Toggle to render Cycles, viewport shading - Material.\n 3. Select the cube. On the materials settings tab click on the button \"use nodes\".\n 4. Under the surface dropdown in material parametres in node socket Color choose Voronoi Texture.\n 5. Then change the coloring with Intensity on Cells.\n\n[Voronoi texture incorrectly displayed in Cycles viewport.blend](Voronoi_texture_incorrectly_displayed_in_Cycles_viewport.blend)", "Musgrave texture incorrectly displayed in the viewport Cycles\nWindows10 x64, intel hd graphics 2000\n\nBroken: 2.78rc1 0e5089c - 2.78 a267710\n\nProcedural texture Musgrave (coloring fBM, Hetero Terrain, Hybrid Multifractal, Ridged Multifractal, Multifractal) incorrectly displayed on an object in the viewport shading mode Cycles material\n\n\n\n\n\n\n\n\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n\n 1. Use a default blender scene.\n 2. Toggle to render Cycles, viewport shading - Material\n 3. Select the cube. On the materials settings tab click on the button \"use nodes\"\n 4. Under the surface dropdown in material parametres in node socket Color choose Voronoi Texture\n 5. Then change the coloring with fBM on Hetero Terrain. Then Hybrid Multifractal. Then Ridged Multifractal. Then Multifractal.\n\n[Musgrave texture incorrectly displayed in Cycles viewport.blend](Musgrave_texture_incorrectly_displayed_in_Cycles_viewport.blend)" ]

[ "UV unwrap: pinning faces in an island causes other islands to have the wrong scale and fill the whole map\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\n\nBroken: version: 2.80 (sub 75)\nWorked: 2.79\n\n\nWhen unwrapping, if you pin some faces in an island, then the other islands will not be in the same scale anymore, they will fill the whole map instead of remaining in the same scale.\n\n- before unwrapping any object, add some seams around a few faces so that this area will have its own small island in the UV map\n- unwrap the object. You should now have a main island, and a small island in the UV map\n- pin a few faces of the main island in the UV map\n- unwrap the object again. Now the small island will fill the whole map or be way too large, instead of remaining in the correct scale.\n\nI tried in Blender 2.81, and the problem is still there.\n\n**Steps to reproduce**\n\n* Open file\n* In UV editor, pin selected vertex\n* select all vertices and unwrap\n\nIsland will fill the whole map", "Automatic Weights not working if part of mesh has negative scale\nOperating system: Windows 10 Pro\nGraphics card: NVIDIA GTX 960\n\nBroken: 3.1.0\nWorked: Never (2.8+)\n\n\nWhen part of a character mesh is given a negative scale in Edit mode, parenting to an armature with Automatic Weights no longer seems to work correctly. Applying scales does not help either as the scaling is done in Edit mode.\n\nI realise there are other ways to mirror part of a mesh rather than negative scale, however myself and one of my students have now both lost hours to this issue before I finally found out what seemed to be causing it.\n\n**How to recreate the bug**\n1. Open the file \"Block Man Example.blend\".\n2. Select the Cube mesh.\n3. Go into Edit mode.\n4. Select an entire arm or leg (I used Select Linked).\n5. Set the scale to -1 on the x-axis. (S, X,-1).\n6. Return to Object mode.\n7. Select the Cube mesh, then holding shift, select the Armature as well.\n8. Press Ctrl+P to parent, choosing With Automatic Weights.\n9. Select the Armature and go into pose mode.\n10. Try rotating the bones around the arm or leg which had been scaled.\n11. You see the mesh does not follow the bone as you would expect.\n\nFile: [Block Man Example.blend](Block_Man_Example.blend)", "Transform pivot gizmo not scaled properly when drawn\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 2.93.0\n\nThe transform pivot gizmo doesn't use the settings for gizmo size, and can become minuscule.\n\n- Create a cube.\n- Enter \"edit\" mode.\n- Select all & scale 20x\n- Zoom out so the cube fits the screen.\n- Go to \"object\" mode.\n- Press Ctrl + \".\" (period) to switch context and show the transform pivot axes.\nSince the object matrix is still diag(1,1,1), the pivot gizmo will not be scaled up, and will be drawn too small.\n\n{[F10172633](Move_vs_transform_pivot_gizmos.png), size=full}\n\nDetails:\nBefore the \"transform pivot\" is drawn, it is only transformed using the object matrix.\n\noverlay_extra.c:\n```\nDRW_buffer_add_entry(cb->origin_xform, color_xform, ob->obmat);\n\n```\nThis means that for a mesh that is big in \"object local coordinates\", but the object matrix is\nstill ortho-normal, the gizmo will not be up-scaled to a proper size in \"screen space\".\n\nIn other places in the code, preferences -> Viewport -> Display -> Gizmo Size is used.\n\nFor example in transform_gizmo_3d.c:\n```\nvoid drawDial3d(const TransInfo *t)\n ...\n float scale = UI_DPI_FAC * U.gizmo_size;\n \n```\nSeems like a good idea to let the transform pivot axes be controlled by the U.gizmo_size as well\nto make their sizes constant in screen space.\n\n(PS This is not just me. I've been encouraged by other artists in my community to report this.)\n", "Stitch by matching target edge length\nAdditional option to existing operator **stitch** that scales one uv island to match the other uv island by matching the edge lengths of the target uv island\n\n**Starting point**\n\nA couple of edges selected before running “stitch operator”\n\n\n\n\n**Undesired result**\n\n\n\nThe uv island that is being stitched to the bigger uv island is still very small\n\n\n\n**Desired result**\n\nThe loose UV island has the same texel density as the UV island that it stitches to \n\nSuggested approach:\n- Store\n - Original pinning\n - Original seams\n- Run “seams from islands”\n- Clear seams on selected edges\n- Pin all but the UV island that will stitched to bigger uv islande\n- Unwrap\n- Restore \n - Original pinning\n - Original seams\n\n", "Bevel modifier UV problem with corners\nBroken: 2.79. 2.8*\n\n**Description**\nImportantly for games with Weighted Normals and Bevels workflow it would be very desirable for Corners of UV to scale and connect correctly so there are minimal distortions and UV disconnections. \n\n\nThis is how it opens in max post export:\n\n\nPlease also note that in 2.8 Bevel modifier completely distorts UVs in \"Vertex average\"(and possibly other) Normal Modes. Works as in 2.79 without any normal mode.\n\n\nPrepared debug scene (as requested by Howard): \n\n[debug_bevel_uv.blend](debug_bevel_uv.blend)\nAlso available here: debug_bevel_uv.blend\n\nThank you!\n", "Dithering is not applied for Texture Baking\nDebian amd64, Radeon HD with fglrx\n\n\nBroken: current GIT, also many previous versions were affected in case of BI Baking\n\n\nDithering is not applied for Texture Baking, resulting in banding artefacts.\nCycles Baking and BI Baking are affected.\n\nAlso when saving a 32 bit float image as 8 bit PNG, no dithering is applied (despite Dithering was set to 1.0, and \"Save as Render\" was activated).\n\nA .blend file is attached. Click on \"Bake\" and wait a few seconds. After baking is finished you should see the banding artefacts in the dark-gray regions.\n\nThanks\n", "Adjust modifier values when using \"Apply scale\"\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nWhen using \"Apply scale\", the modifier values are not adjusted if the object scale is not [1,1,1]. I would like to suggest that the operator \"Apply scale\" iterates through all modifiers of the selected objects and adjusts all values related to scale\n\nFor example\nBevel modifier - Amount\nDisplace - Strength\nData transfer - max distance, ray radius\nUV project - Scale X, Scale Y, \netc\n\n---\n\nCurrent behaviour\n{[F9849514](image.png), height = 700}\n\n---\n\nDesired behaviour\n{[F9849529](image.png), height = 700}\n\n---\n\nsuggested Operator mockup\n\n{[F9852183](image.png), height = 300}", "Clicking on a pie menu item doesn't work when holding the pie menu key.\nOperating system: Windows 10\n\nBroken: 2.79, 2.92\n\nClicking on a pie menu item doesn't work when holding the pie menu key. This is a problem because sometimes the pie menu key release isn't detected by blender and then the it locks the UI.\n\n1. On the 3D Viewport hold Z for the shading pie menu.\n2. While still holding Z try clicking on the pie menu items. Doesn't work.\n3. While still holding Z, left click on Windows's Taskbar then release z.\nAfter that, clicking on the pie menu items doesn't work even though the user isn't holding the pie menu key anymore, blender still considers that the key is held. Then Blender gets locked to the user unless he knows to press esc or right click. The solution is making the pie menu clickable even when the pie menu key is held.", "UV Stitch and Minimize Stretch do not support the trackpad\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\n\nWe can use the mouse wheel while executing \"UV Stitch\" and \"Minimize Stretch\" operators to adjust the Limit and Blend values. However, this feature is not available for trackpad users.\n\nA possible solution can be seen here:\nD8812\n\n", "Automatic UV seam creation tool\nAutomatic seam creation tool, that balances various goals:\n* Keep angular and area distortion below a given threshold\n* Minimize total length of seams and number of islands\n* Prefer seams along sharp edges / features in the model\n* Prefer seams to be straight instead of jagged\n* Make seams symmetric when there is symmetry in the model\n* Prefer islands for naturally distinct parts of a model (arms, legs, ..)\n* Avoid too complex concave islands shapes that are difficult to pack\n\nResources:\n* [xatlas](xatlas)\n* [UVAtlas](UVAtlas)\n* [D-Charts: Quasi-Developable Mesh Segmentation](dcharts_eg.pdf)\n* .. various more papers can be found, also in the field of mesh segmentation\n\nSplit out from #68889.", "Insufficient transform precision?\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.1\n\nIn rigs, and to a lesser degree in geometry itself, there is percievable jiggle in moving objects that are further from world origin.\n\nWe are working on an animation feature film, which has lots of open nature scenes. That assumes moderately large object dimensions and distances (1-10 kilometers) in relation to life sized character close-ups. In shots that are not located in the center of the coordinate system there is a visible jiggle in bone locations and resulting geometry. Same jiggle can be seen in plain geometry objects that are further from origin, however in characters it becomes a problem already at a 100m from the world origin, probably due to many layers of transform/parent/constraint relationships multiplying the error.\n\nInsufficient floathing point precision? #90125 might be of same nature but in rotation.\nEdit: just to be clear this is about precision of transforms and calculated final world coordinates. Never encountered problems with precision of the stored geometry data.\n\n[var.blend](var.blend)\nPress play. Vertex motion gets quantized.\n", "UV: Add \"Common-Origin\" to Average Island Scale\nCurrently, Average Island Scale rescales islands so that they have a similar scale.\n\nHowever the origin of the transform is chosen to be the center of each island individually.\n\nIt would be nice if the origin of the transform could be shared between all the islands, so that subsets of islands which have a common scale would then keep their relative positioning after scaling.\n\n", "Modifiers header misalignment on change Resolution Scale [pixel perfect thing]\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.5161\n\nBroken: version: 2.92.0; blender-2.90.0-d7c4e9649320\nWorked: don't know\n\nModifiers/Constraints header buttons misalignment on different (especially smaller) Resolution Scale value\n\nSimple as that. Tried set Resolution Scale down on a notebook, and saw the modifier name input \"jump\" out of the modifier box.\nSo checked that any value bellow 1, varnishes the \"top margin\" of it. The same on constraints, bones included.\nThan i suppose it has something to do with the dragging feature.\n\nOpen Blender.\nAdd any modifier/constraint an object.\nGo to Preferences -> Interface -> Display -> Resolution scale, and click the input's left arrow.\nSe the bug on the modifier header\n\n\n\n", "Rotation/Move support for Transform Cage\nThe idea is have a Transform Cage to move, rotate and scale in the 3D viewport (similar to the gizmo that exists for 2D UV editing).\nThis is will be realy useful for Grease Pencil and 2D animation workflow and is common in other 2D animation programs.\n\nPlease, check this video for more info:\n[Tramsform Cage2.mp4](Tramsform_Cage2.mp4)\n\n\nDaniel\n\n----\n\n\n****is this just the current scale cage with rotation handles added?***\nYes, basically. It would be nice if you grab an edge of the cage you have a skew transform (see the video)\n\n[2020-02-13 01-53-56.mp4](2020-02-13_01-53-56.mp4)\n\n***Would the pivot point be used only for rotation or scale as well?***Yes, for all tranformations***Would it be possible not to use this pivot point, and use the 3D cursor instead?***It´s is possible but I think that is more convenient and easy for the user***How this is accessed (As a sub-tool of transform? like scale cage?)***\nYes, as a sub-tool of transform\n\n", "Color space seems wrong while painting in image editor.\nIn the image editor add a new image and with default settings just do a red line paint over a green line paint.\nDark zone appear in the falloff between red and green. it should not be there and should stay clear, not dark. \nI don't know why, but it looks like a color space issue. \n\ndark falloff not ok in blender:\n\n\nclear falloff ok in gimp:\n\n\nblender 2.8\nWindows 7 \n\n\n" ]

[ "UV Constrain to bounds not constraining when scaling UV's\nSystem: MacOS 10.12\n\nBlender Version: 2.78a\n\nUV's are able to be scaled beyond bounds in 'constrain to bounds mode' when pivot point is set to 2D cursor, and positioned on an edge.\nThis issue can also be reproduced on the x axis as well, it seems to be dependent on where the 2D cursor is placed within the UV workspace.\n\n - Open: [UV_Constrain_to_bounds_bug.blend](UV_Constrain_to_bounds_bug.blend)\n - Go to UV editor\n # Try to scale to the y axis\n\n\n\n" ]

[ "Bake's Ray Distance only considers one side of the face\nOperating system: Linux-4.13.10-041310-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.67\n\n\nBroken: version: 2.80 (sub 74)\n\n\n[video demo ](watch?v=9CduQ7AFsVk)\nWhen trying to bake a normal mapped plane, or full geometry to another object, the bake will 'go through to the other side'\n\nUnless a solidify mod is added to the active.\n\n\nThis is because 'Ray Distance' affects only one side of the face.\n\n\n* open attached blend file\n* notice the solidify mod on the object we want to bake to\n* bake either or both of the two smaller objects to the cube (it should work fine)\n* turn off the solidify mod, and bake again and bake (the results should appear on the opposite side)\n\n[baking_requires_solidify.blend](baking_requires_solidify.blend)\n\n", "Crash when baking quick smoke fire simulation\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nQuick Smoke within FIRE (Bake Data) button\n\n\nfrom 32 change to 256 see picture \n\nSee End: from 256 to 1000 (frames) \n\n(Bake ALL) on Type: ALL\n\n\n[Blender-2022-08-15-103438.ips](Blender-2022-08-15-103438.ips)\n[Blender crash guide on Mac appear.txt](Blender_crash_guide_on_Mac_appear.txt)\n\n[Quick Smoke within FIRE.blend](Quick_Smoke_within_FIRE.blend)\n\n\n", "Dependency cycle detected even when the constraint is inactive\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.3.0\nWorked: Never\n\nBlender complains on inactive (disabled) dependency cycles each time when I bake animation.\nUnfortunately it affects the baking process (the keys are baked with the delay in one frame). \nI know it might not be considered as the bug, but it is a problem:\n For instance: I'd use empties to fix feet sliding the ground during the complex character root motion movements. \n To make it work first I constraint empties to feets, bake the animation, delete the constraints, then clean up the empties animation so they keep stable toward the surface and finaly constraint the feets to the empties to bake fixed animation. \n Defenetly I would not want to create and delete the constraints over and over again: it is much easier to turn them on and off during the work. Same goes with objects that can guide a character or be guided by one during the same scene. We might just want to choose when the object is constrained to the character and when the character should be constrained to the object. \n \n So when the constraint is disabled it should not be considered as the dependency cycles. (It should not be considered in general)\n1. Create some bone and an empty\n2. Add a Copy Transforms constraint to the bone. Choose the empty as the target.\n3. Add a Copy Transforms constraint to the empty. Choose the bone as the target and **disable the constraint to break the loop.**\n4. Animate empty and try to bake this animation to the bone in a pose mode.\nOnce you press Bake Action (with Visual Keying On) you'll have a warning: Dependency cycle detected like if you have both constraints enabled. \nThe animation will be baked with the delay in one frame.\n\n", "Simulation Nodes: bake UI in simulation node\n_No response_\n\n", "Performance test and notes regarding multires\nDaniel Bystedt and Dalai Felinto had a catch up meeting 11:th of May. During that meeting we talked a bit about sculpting. Dalai asked me to create this task and to add a test file and some more info which is detailed below.\n\n**Computer and Blender specs**\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nversion: 2.92.0\n\n\n**Blend file**\n[orc_head_5_subd_v001.blend](orc_head_5_subd_v001.blend)\n\n**Switching symmetry on/off**\nSwitching symmetry on/off is something a user does quite often in order to not make human faces (for example) look totally mirrored when sculpting. It’s a bit surprising that it is so slow when the vertex count is high. \n\n@PabloDobarro explained via chat: *The lag from turning on/off symmetry is because of a BVH rebuild. Symmetry is a property of meshes, so each time a property of the mesh changes, it considers it as a change in geometry and rebuilds the BVH again. It should be possible to do a more proper tagging of these changes to avoid this, which will fix this multires and any other future system we can make.*\n\n|Vertex count| Time to switch symmetry on/off\n| -- | -- |\n|10 million| 3 s 7ms|\n\n**Subdivide performance**\nSubdividing when vertex count will be above 1-3 million is usually rather slow. The user only have to subdivide the model once when sculpting a model so it’s not a frequent thing that you do. If it could be made faster it would be a nice improvement though\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|subdiv 2.6 million > 10 million| 16 s 5 ms|\n\n**Switching sculpt levels performance**\nSwitching sculpt subdivision levels is something the user does quite often, so if it is fast it would be great. The performance is not terrible though.\n\n|Vertex count| Time subdivide with multires|\n| -- | -- |\n|2.6 million > 10 million| 1 s 8 ms|\n\n\n**Performance investigation starting point**\n- Run a profiler to see if we do not have obvious bottlenecks and see that all threads are occupied\n- Measure exact memory footprint of OpenSubdiv topology. If it is not terribly big, can cache those on different levels while being in the sculpt mode\n- Look into sparse patch tables. This seems to be a solution to a specific of OpenSubdiv which is related on a single-threaded nature of topology construction\n- Run quick and dirty check whether using GPU evaluation brings 10x speedup (quick and dirty is because doing proper integration is not trivial and you don't want to do it if the speedup is not that great)\n- Check whether all tools are properly multi-threaded\n- Make ID_RECALC_PARAMETERS to work for non-geometry properties of meshes (to mitigate the symmetry lag)", "animating texture space on largish curve object causes slow down\nOperating system: MacOS 10.14.6\nGraphics card: Radeon Pro Vega 48 8GB\n\nBroken: 2.82 alpha 2019-12-16\nWorked: (optional)\n\nI imported a largish SVG (300 KB). I joined the curves into one object and then placed a keyframe in the texture space. Blender will then slow down to unworkable. It depends on the size of the curve object, larger means slower.\n\n I can't animate textures that way. So now I am using another object for texture coordinates which works and doesn't slow down at all but I would rather use the texture space.\n\n[#72501 example.blend](T72501_example.blend)\n\n*Developer note: see thread for profiling info and bottleneck*", "Subdivision Surface Performance Degrades Markedly With Non-Quad Meshes\nOperating system: Windows 7 Pro X64\nGraphics card: Nvidia Geforce GTX 980 Ti\n\n\nBroken: Date: 2019-01-21\n```\n Hash: dd3f5186260e\n Branch: Blender 2.7 (although it's supposed to be a 2.80 Beta)\n```\n\n[OpenSubDiv_PerformanceBug.zip](OpenSubDiv_PerformanceBug.zip)\n\nSubdivision surfaces are fast and responsive in Edit mode *with all-quad meshes*, but very slow (~ 10x slower) with meshes comprised of triangles and quads.\n\n\nOpen the attached blend file and select **Cube.001**\n\nGo into Edit mode. Turn on Proportional Editing. Grab a point and move it - observe how responsive the viewport is with the all-quad mesh.\n\nGo back to Object Mode. Select **Cube**. Go back into Edit Mode. Grab a point and move it (with proportional editing still turned on) Observe how slow it is.\n\n", "Cycles takes very long to cancel a render\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.2.0\nWorked: 2.93\n\nEver since Cycles was upgraded to Cycles X whenever I render a scene with a high Max sample count and cancel the render mid-render it always takes very long (up to a few minutes) until the render actually stops.\nThe time it takes to until the render stops seems to be proportional to both scene complexity and Max sample count.\nAt the start of rendering the samples first go up at small increments and later go up at greater increments. The greater the increments between sample count updates the longer it takes to stop the render.\nChecking Task manager shows that after hitting `cancel render` it does keep using the GPU, therefore keep rendering, until it finally stops.\nDuring the time between hitting `cancel render` and Cycles actually stopping the render the entirety of Blender becomes completely unresponsive.\n\nThis is only a problem when actually rendering the scene. Viewport render doesn't seem have this issue.\n\nTest file:\n[untitled.blend](untitled.blend)\n\nHit render and wait a little until the rate samples go up slows down. The hit `cancel render`.\n\nThank you and have a great day!", "Working on a mesh that has a high multires subdivision causes blender to build Up memory even on lower levels.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\nRAM: 16GB\nCPU: AMD Ryzen 7 3800\n\nBroken: version: 3.6.0\n\nWhen editing a mesh that has been subdivided a few times will cause blender to increasingly start to consume more and more memory aggressively even if the modifier is turned off.\n\nSubdivide the mesh a few times using the multiresolution modifier, noted on 5-up levels on a mesh with originally 9 272 faces. then either switch the modifier Viewport Level to either 1 or disable It entirelly, start editing the mesh in edit mode the memory consumption stats will start to skyrocket with no signs of going back down until blender starts slowing down the computer and/or crashes entirely. (Got to about 32 GBs some times about where the computer would stop handling It anymore) I haven't tried doing it in workbench I think so I'd suggest trying to do It in Eevee mode too.\n", "PBVH task scheduler performance issues\nThis is a task to investigate a possible issue in the PBVH task scheduler. \n\n**Issues**\n - Some users report bad performance in sculpt mode, while others can work without problems on really high poly meshes with similar hardware.\n\n - On my main computer, brush strokes with TBB disabled feel more responsive regardless the mesh vertex count. When TBB is enabled, strokes usually stop generating new samples in the middle of the stroke or take a fraction of a second to start. I know this is happening to some other users. \n\n - Simple operations that need to loop over all vertices on high poly meshes are extremely slow for no specific reason. (doing x = 1.0f - x on a 25M elements array often takes up to 5 seconds). When the operation is more complex (like updating the normals or updating the nodes on the GPU), this can take minutes to finish. \n\nWe are not getting the reports of people that may be affected by this issue because most of them assume that Blender sculpt mode performance is just bad by default, so I can't tell if this is a problem with a specific configuration of hardware/software or a general problem in how the scheduler works. It would be nice to have more data from this test (and sculpt mode performance in general) on different hardware/software configurations to have a better understanding of how we can improve it. \n\n**How to test:**\n\n - Apply this patch: [P1202](P1202.txt)\n - Add a cube, subdivide N number of times and apply\n - Enter Sculpt Mode\n - Run \"Invert Mask\" (press A + drag left)\n\n\n**My results**\n\nOperating system: Linux-5.4.2-1-MANJARO-x86_64-with-glibc2.29 64 Bits\nCPU: Intel i7 6700K @ 4.00GHz x 8\nRAM: 32GB\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nSubdivide default cube N number of times:\n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|---------|\n| 11 | 25165826 | 7596 | 2.474073 | 0.571511 | 432.90% |\n| 10 | 6291458 | 1920 | 0.307948 | 0.159395 | 193.20% |\n| 9 | 1572866 | 464 | 0.111459 | 0.096845 | 115.09% |\n| 8 | 393216 | 112 | 0.002289 | 0.007297 | 31.37% |\n\n\nSubdivide default cube 6 times, use multires to N level.\n\n| Level | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|-------|----------|------------|------------------|-------------------|---------|\n| 6 | 26763264 | 3696 | 1.076635 | 0.322183 | 334.17% |\n| 5 | 7102464 | 912 | 0.074586 | 0.113303 | 65.83% |\n| 4 | 1990656 | 232 | 0.012938 | 0.048273 | 26.80% |\n| 3 | 614400 | 56 | 0.004059 | 0.012778 | 31.77% |\n\n\nAs you can see, a simple loop over all vertices in the mesh is way faster on my setup with TBB disabled.\n\nIf I change the ##LEAF_LIMIT## in ##pbvh.c## to 100000 (x10) in order to increase the amount of work each node has and reduce the number of total nodes: \n\n| N Subdivisions | Vertices | PBVH Nodes | TBB ON (seconds) | TBB OFF (seconds) | DIFF |\n|--------------|----------|------------|------------------|-------------------|--------|\n| 11 | 25165826 | 760 | 0.106868 | 0.210985 | 50.65% |\n| 10 | 6291458 | 184 | 0.029088 | 0.105376 | 27.60% |\n| 9 | 1572866 | 56 | 0.007168 | 0.029653 | 24.17% |\n| 8 | 393216 | 8 | 0.002261 | 0.006321 | 35.77% |\n\nIf we compare the two results with TBB on:\n\n| Vertices | 1000 LEAF_LIMIT (default) | 10000 LEAF_LIMIT (new) | Perf. gain |\n|----------|-----------------|------------------|------------|\n| 25165826 | 2.474073 | 0.106868 | 2315.07% |\n| 6291458 | 0.307948 | 0.029088 | 1058.68% |\n| 1572866 | 0.111459 | 0.007168 | 1554.95% |\n| 393216 | 0.002289 | 0.002261 | 101.24% |\n\nIt seems like if we avoid starting TBB with a large number of nodes the performance improvement is huge. Increasing the leaf limit makes these kinds of operations up to 23 times faster, but that would be like disabling multithreading for small brush strokes.\n\n- Is there a way to fix this in the scheduler?\n- Can we do something like sending small chunks of nodes to TBB instead of starting the loop with 7000 nodes at the same time?\n- Can we find a better optimal leaf limit to get a better workload per core suitable for modern processors by comparing the results on different hardware? Dyntopo leaf limit is in 100 elements, which I think it does not make much sense. ", "2.9.1 Close without error message\nOperating system: Windows 10, 10gb ram, ssd\nGraphics card: Nvidia GTX 650 1gb vram\n\nBroken: (2.83 LTE and 2.90 current available version)\nWorked: (2.82)\n\nWhen rendering with GPU AND CPU, the app crashes, works perfectly fine on CPU only. On GPU only too but slower than older versions.\n\n\n```\nblender.exe :0x00007FF7A5B76440 ccl::kernel_cpu_sse41_filter_finalize\nblender.exe :0x00007FF7A57A9220 ccl::CPUDevice::denoising_solve\nblender.exe :0x00007FF7A57DA470 ccl::DenoisingTask::reconstruct\nblender.exe :0x00007FF7A57D8ED0 ccl::DenoisingTask::run_denoising\nblender.exe :0x00007FF7A57A7240 ccl::CPUDevice::denoise_nlm\nblender.exe :0x00007FF7A57AB590 ccl::CPUDevice::thread_render\nblender.exe :0x00007FF7A57ABA30 ccl::CPUDevice::thread_run\nblender.exe :0x00007FF7A57A60B0 ?_Do_call@?$_Func_impl_no_alloc@V<lambda_d884e08a7877f415f05ce8ffda8f97b4>@@X$$V@std@@EEAAXXZ\nblender.exe :0x00007FF7A7D5F520 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5F037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFBF5EF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFBF5EFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFBF5F019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFC08611FA0 o_exp\nKERNEL32.DLL :0x00007FFC0B647960 BaseThreadInitThunk\nntdll.dll :0x00007FFC0B7AA250 RtlUserThreadStart\n```\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Crush while baking a cloth simulation\nOperating system: macOS-13.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\n\nI was performing the baking of a cloth simulation. During the initial and subsequent baking attempts, everything worked fine. However, when I tried to re-bake the simulation after moving the cursor in the timeline, the program crashes. I tries to bake that cloth in previous versions. It didn't work as well\n\nTo trigger the crash, you simply need to move the cursor in the timeline and then initiate the baking process.\n\nUnfortunately, i cannot add the file (size is 200mb and i can't make it smaller ), so than i added the crash txt file and a link to the file on google drive\nview?usp=sharing\nThank you!\n\n", "Use after free: Baking Rigid Body physics causes instant crash\nOperating system: macOS 10.15.7\nGraphics card: AMD Radeon Pro 5500M 4 GB / Intel UHD Graphics 630 1536 MB\n\nBroken: 2.92.0, branch: master, commit date: 2021-02-24 16:25, 2.93.0 Beta, branch: master, commit date: 2021-04-28 22:25, \nbroken: f7b22fc3d27113715e8726c69ab3264e1d487439\nWorked: \n\nBaking the Rigid Body world physics causes Blender to crash either instantly, or after baking less than 100 frames (it varies). Interestingly, a friend with the PC version of 2.92 says the project works fine, no crashes whatsoever.\n\nOpen the project. Make sure Allow Negative Frames is on under Preferences/Animation. Go to the Rigid Body World and hit bake.\n\n[physics test b.blend](physics_test_b.blend)\nAsan report: [T88113_asan_report.txt](T88113_asan_report.txt)", "Solidify Node\nWe will drop support for Simple mode since the difference is hard to tell and performance-wise better to optimize the Complex mode than maintaining both.\n\nFill and Only options are a bit confusing in the modifier since fill refers to the fill of the rim and has to be checked on to make Rim Only work.\nInstead, I suggest making Fill refer to the part that is not the rim and Rim refer to the rim and make them independent from each other and both true by default.\n\nThe modifier has options for a vertex group as a factor for the thickness and two vertex groups to store the fill and rim geometry.\nvertex groups will be replaced by two attribute string fields for the factor and to tag the rim geometry\n\n", "Regression: Importing of collada model with instances became a LOT slower since 2.80 (practically freezing)\nOperating system: windows 10\nGraphics card: geforce gtx 1070\n\nBroken: blender 3.4.1\nWorked: 2.80\n\nImporting of collada model makes Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\n- import attached collada file\n- Blender not respond anymore with high CPU usage in windows task manager (and never finishes no matter how long you wait)\n\nLink to model file:\n\nCruisn-Exotica-arcade-game-Dual\n\n[doubleexotica.zip](doubleexotica.zip)" ]

[ "Very high memory usage for Cycles baking compared to ordinary renders\nI've been playing around with Cycles baking and running into a few limitations here and there. I've put together a pretty simple scene with an HDR image light, some reasonably simple bricks, a mortar mesh, and a bake target. I haven't tried the other passes, but both Combined and AO seem to have very high memory usage given what is being baked. Blender shoots up to 2.87 GB of memory usage on this fairly simple scene, while it uses about 133 MB (about the same as normal) when I just render. I did all my tests with the CPU only. If Dalai could run a debugger, try baking the scene for himself, and see if he can reproduce the rather preposterous memory usage, I would really appreciate it. I also tried baking with instanced meshes and it didn't seem to make a difference for memory usage.\n\nTo get all the relevant meshes into the scene for baking, just toggle layers 2 and 3 to reveal the source meshes.\n\nDownload the .blend [here.](30421)\n\nUsing BF's official 2.71 build on Windows 7 64-bit. Processor is AMD FX-8320, GPU is a GTX 780 with 3 GB of VRAM. I have 8 GB of ordinary RAM." ]

[ "Move origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.1\nBroken: version: 3.2.0\nWorked: (newest version of Blender that worked as expected) - don't know any working version from 2.8\n\nMove origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\nLooks like limitation maybe around Transform Options and lack of implementations or bug that blocking move origin.\nWhen using addon Cad Tranform (slcad_transform_0.91.0.zip) and Turn on Transform Options Origins then can move origin (but problems with magnet snap).. soo looks like bug in blender grab area.\nAnyway it's problem when looking correct position for my object and work with collections, only addon can solve problems.\n\n1. Turn on Transform Options Origins - try move origin for Collection2, eg. for corner\n2. Turn off Transform Options Origins, select Object Set Origin and Origin to Center or other option\n\n\n\n\n[Origin_bug.blend](Origin_bug.blend)\n", "Motion Paths not updating when working on the graph editor\nOperating system: Windows 10\nGraphics card: 1050 TI\n\nBroken: 3.5\nWorked: Supposedly never worked due to the way the code is set up.\n\n\nMoving the F-curve for key-framed object will not update motion paths.\n\n\n- Do some location key frames on the default cube.\n- Calculate the cube's motion path in the object properties tab.\n- Move the f-curve key frames on the default cube, motion path does not update.\n - Move the object directly, only the motion path of the current frame is updated.\n\n", "Sculpt: Grid overlay for Grab active point do not work.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nThis seems to be issue only with Nvidia GPUs on windows.\n\nBroken: version: 3.0.0 Alpha\n\n\nGrid overlay for Grab active point do not work.\n[2021-07-18_18-56-46.mp4](2021-07-18_18-56-46.mp4)\n\n\n**Steps to reproduce**\n[#89942.blend](T89942.blend)\n\n- Open file\n- Check if wireframe overlay is drawn under cursor\n\nWhat fixes this is to have any transform gizmo visible while using brush, then it works until Blender is restarted.\n\n\nFrom #92703:\n\n> This was proposed on the blenderartists thread, I have no idea if it works or if it could broke the preview on the AMD cards\n>  \n> If you know how to compile you can fix it by erasing ! from the line 1157 : if (!depth_test) {\n> to read like so: if (depth_test) {\n\n\n", "No projection onto empty object types\n(This is was coming from a discussion with @ideasman42 )\n\nThere are Tools and Operators that will take empties into account, even though this is very counter-intuitive in most workflows.\nOne example of this is the 3D Cursor being projected onto image empties. In the workflow of creating characters and props it's common to import images as references, especially turntable drawings.\nIn Blender 2.8 These these need to be imported as empties and set up to be visible in the background from different angles.\n\n\nIt is very anoying to try to place the 3D Cursor to add new objects and have it projected onto one of the empties. The empties are reference. They should not be taken into account for the tools (Except for snapping to an empty origin).\n\nAnother example is when drawing a curve and using the surface depth method for drawing. This way it will draw the curve onto surfaces instead of around the 3D Cursor.\nIf there's an empty in the way, it will take the wires & surfaces of the empty also into account, which really has no use.\n\nThis needs to be further discussed if this functionality should be completely changed or made optional if there are any workflows that benefit from this.", "Limit Scale does not Limit Scale on the Minimum Value\nOperating system and graphics card\nOS X 10.8.5\nGraphics AMD Radeon HD 6490M 256 MB\n\n\nBroken: Blender 2.69\n\nThe Limit Scale constraint fails with a minimum value of 0.0. The user is able to bypass the minimum and scale all the way \"down\" to the negative maximum value. It is easiest to bypass the minimum value at 0.0. It is also possible at values close to zero such as 0.2 or 0.4, but the user must move the mouse rather quickly to jump over the minimum value into the negative side.\n\nThis is reproducible with the default blend or with the attached.\n[limit_scale_bug.blend](limit_scale_bug.blend)\n", "Parent mode for Location Transform Orientation \nThis has come up several times, and is something we need a lot in animation:\n\nWhat is it?\nBasically a way to display the Location XYZ orientation based on the parent of the selected object/bone/control.\n\nWhen any objector control is parented to an other it's location transforms depends on the parent, so if i rotate the parent in any weird angle, the locations of the child (the one i want to move) depend on that object, making any of the transform orientation options make no sense when you want to use a specific axis unless you do it from the graph editor or from the transform values.\n\n[transform orientations.webm](transform_orientations.webm)\n\nPropolsed solution:\n\nAdding a new transform orientation (for location only) that is called parent, where it will always look at the parent transforms of the seelected object to orient the transform gizmos, when there is no parent, the \"parent\" is the world so it'd show the orientations based on that.\nThat'll make it fast, easy and really a great improvement in the animation workflows.\n", "Set parent (keep transform without inverse) has no effect on scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.0 Alpha\n\n\nSet parent (keep transform without inverse) has no effect on scale. End result is different if use Set parent (without inverse)\n\n[parent_scale.mp4](parent_scale.mp4)\n", "Changing rotation axis in operator panel has no effect\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 3.1.0 Alpha\n\nAfter confirming a rotation operator with a click, attempting to change the axis in the popup panel has no result.\n\n\nAdd any object. Press R to rotate it, and choose any specific axis. After you click to confirm, attempt to change the axis of rotation in the operator panel. \n", "Orbit around selection not working with modifers in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\n\nWhen \"orbit around selection\" is turned on in the preferences the viewport usually rotates around the selected object - for example a selected vertex.\nIf the objects geometry is influenced by a modifier, though, the viewport does not rotate around the modifieds position of the vertex but still around the original position of the vertex. This can be very limiting, esspecially when using heavily deformed meshes which is often the case when using lattices.\n\n1. Preferences -> Navigation -> check \"Orbit Around Selection\"\n2. create Cube\n3. put simple Deform Modifier on Object\n4. In the modifier next to the Camera and Viewport Display icons press the \"Edit Mode\" icon and the \"On Cage\" icons. (see image)\n5. Select a single vertex of the Cube and rotate the viewport\n6. The viewport does not rotate around the vertex.\n\n\n\n\n", "Camera Movement along an axis issue\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12001.7006\n\nBroken: version: 2.81 (sub 3)\nWorked: (optional)\n\n**Description of error**\nWhile moving my camera along the y-axis, I noticed this bug. I have made a video and uploaded it to youtube, to demonstrate it. Here is the link to it: get9_hMZXDQ\n\nBasically when I move my camera along the y axis .. beyond 300m mark, it suddenly jumps to -10000000m or something.. and the screen goes blank. Also, I have not tested it along the X axis or Z axis so far. \n\n\n\n", "X axis isn't showing in camera view like Z axis \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.2.1\n\nX axis isn't showing in camera view like Z axis when we activate it from viewport overlays:[2022-07-06 22-43-44.mp4](2022-07-06_22-43-44.mp4)\n\n", "Architecture Texture Coordinates in Cycles\nHello dear Cycles team and developers :)\n\nI've been working in an archiviz project and stumbled upon a short come of Cycles: we don't have a straightforward way of setting world-based-dimensioned textures . This is a must for architecture, and I can give a few real-world use cases if requested.\n\nAs a Blender user I came up with a node system that can handle this. You can check my approach here: ?p=1198. Basically what this does it to take the Object texture coordinate and transform it based on the face normal (so we have an unstretched mapping for X, Y and Z).\n\nAs a Blender/Cycles developer I think we can do even better, and have this feature into master once we agree on the design and approach for the implementation.\n\nI wonder why this never came up before as an issue. As a side note, if you read the Expose 3D Blender migration post on BlenderNation () you will find that they consider the \"Lack of architectural UV mapping\" as the number one \"flaw\" of Cycles rendering.\n\nMy initial suggestion would be to have a Node where you could control (via socket input) the offset, scale and rotation of the texture. At first I would like to keep it simple and have offset to be a Vector(2), Scale to be a Vector(2), and Rotation to be a Float. In other words, I wouldn't bother with having per-axis nitty-gritty control. Also, the object size should NOT affect the texture size (unlike my original approach, or even the one from the \"Sure UVW mapping” addon used by the Expose 3D team). I'm not sure if this last bit is possible though.\n\nAny thoughts?", "Rotation/Move support for Transform Cage\nThe idea is have a Transform Cage to move, rotate and scale in the 3D viewport (similar to the gizmo that exists for 2D UV editing).\nThis is will be realy useful for Grease Pencil and 2D animation workflow and is common in other 2D animation programs.\n\nPlease, check this video for more info:\n[Tramsform Cage2.mp4](Tramsform_Cage2.mp4)\n\n\nDaniel\n\n----\n\n\n****is this just the current scale cage with rotation handles added?***\nYes, basically. It would be nice if you grab an edge of the cage you have a skew transform (see the video)\n\n[2020-02-13 01-53-56.mp4](2020-02-13_01-53-56.mp4)\n\n***Would the pivot point be used only for rotation or scale as well?***Yes, for all tranformations***Would it be possible not to use this pivot point, and use the 3D cursor instead?***It´s is possible but I think that is more convenient and easy for the user***How this is accessed (As a sub-tool of transform? like scale cage?)***\nYes, as a sub-tool of transform\n\n", "Draw Face Sets smoothing and Relax Face Sets don't respect locked axes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (Actually Windows 11, but I'll leave the auto-generated specs here as well).\nGraphics card: NVIDIA GeForce RTX 3090 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 4.0.0 Alpha\nWorked: Assumably never.\n\nThe Tool ➔ Symmetry ➔ Lock X/Y/Z options don't work when:\n● you use Shift in the Draw Face Sets brush to smooth Face Set borders;\n● you use Mesh Filter ➔ Relax Face Sets.\n\nThis is a handicap when you want to smooth borders and don't want the Face Set border vertices to move in a locked axis direction.\n\n1. Start Blender.\n2. Subdivide the default cube by pressing Control + 4.\n3. Press Control + A ➔ Visual Geometry To Mesh.\n4. Go to the Sculpting workspace, and activate the Draw Face Sets tool.\n5. Draw a Face Set area.\n6. Lock an axis in Tool ➔ Symmetry ➔ Lock X/Y/Z.\n7. Smooth the Face Set's border with Shift. The locked axis isn't respected.\n8. Press Undo.\n8. Activate Mesh Filter ➔ Relax Face Sets, then click and drag across the mesh. The locked axis is again not respected.\n\n", "Incorrect gizmo orientation \nOperating system: MacOS Monterey v12.3.1\nGraphics card: AMD Radeon Pro 5300M 4 GB Intel UHD Graphics 630 1536 MB\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked: ?\n\nWhen changing orientation of gizmo, previous (incorrect) orientation is used with select tool.\n\n1. New General project\n2. Rotate object/cube so local orientation is different to global (say, rotate 45 degrees on x-axis).\n3. In Gizmo dropdown, under Object Gizmos section:\n - Activate 'Move' checkbox\n - Select Local orientation\n4. Activate Select tool on the toolbar - the gizmo will appear using Local orientation (expected)\n5. Select Move tool on toolbar\n4. Change gizmo orientation to Global\n11. Click Select tool on toolbar\n\nObserve the gizmo orientation is Local, while it should be Global" ]

[ "Object constraint copy rotation Bug\nOperating system: Windows 10 - version: 1809 - build: 17763.316\nGraphics card: GeForce 1050ti/PCIe/driver 441.20\n\nBroken: version: 2.82; version: 2.83 Alpha, February 28, 00:32:47 - 28fca2c588fd\nWorked: 2.81a\n\nWhen we want to \"Copy rotation\" by Add object constraint for making animation rotation by local axis via adding \"empty\" object as target - is it not working.\n\n[#74281.blend](T74281.blend)\n\n- Open file\n- Rotate empty around Z axis\n\nCube should be rotated around local Z axis" ]

[ "Blender full crash during smoke+noise baking \"EXCEPTION_ACCESS_VIOLATION\"\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\nCPU: Ryzen 5900X\n[system-info.txt](system-info.txt)\n\nBroken: 2.92\n\nEvery single time I try to bake a high res particle system, in this case, fire at 256 + default noise settings, it never gets to complete the render and the blender crashes completely (including the console running in the background) at around frame 60 / 150.\nPausing and resuming baking sometimes works but most of the time it instantly crashes on the resume.\n\nEdit:\nI currently have 32 GB RAM and they are not really under much use during the bake.\nI tried with an RTX 3070 and Ryzen 5800x and the same issue.\n\nCrash file:\n\n\n```lines=30\n# Blender 2.92.0, Commit date: 2021-02-24 16:25, Hash 02948a2cab44\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF76E01AD1A\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0x000001C8281373F8\n\n\nStack trace:\nblender.exe :0x00007FF76E01A850 adaptive_domain_adjust\nblender.exe :0x00007FF76E021580 update_flowsfluids\nblender.exe :0x00007FF76E01F380 manta_step\nblender.exe :0x00007FF76E018CD0 BKE_fluid_modifier_processDomain\nblender.exe :0x00007FF76E018530 BKE_fluid_modifier_do\nblender.exe :0x00007FF76E2CC220 modifyMesh\nblender.exe :0x00007FF76E0C4DF0 mesh_calc_modifiers\nblender.exe :0x00007FF76E0C4AF0 mesh_build_data\nblender.exe :0x00007FF76E0C7170 makeDerivedMesh\nblender.exe :0x00007FF76E0A65F0 BKE_object_handle_data_update\nblender.exe :0x00007FF76E0A6320 BKE_object_eval_uber_data\nblender.exe :0x00007FF771D6AFA0 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph * __ptr64,Main * __p\nblender.exe :0x00007FF771D69380 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF771D69330 blender::deg::`anonymous namespace'::deg_task_run_func\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF771DEE500 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAAF51D0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFDEAAFA490 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00002380\nntdll.dll :0x00007FFDEFFED280 NtDelayExecution\nKERNELBASE.dll :0x00007FFDEDB18FE0 SleepEx\nblender.exe :0x00007FF76E122380 wm_window_process_events\nblender.exe :0x00007FF76E1184D0 WM_main\nblender.exe :0x00007FF76DE09C70 main\nblender.exe :0x00007FF772313468 __scrt_common_main_seh\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000024a0\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000549c\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006094\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003a78\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000722c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000058fc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004090\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005f20\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000029a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000047b8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005718\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ba0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002ae4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006820\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001738\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c44\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004984\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c48\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000389c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002d68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002f90\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00007248\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005010\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000027d8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002668\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000571c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000017f0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nblender.exe :0x00007FF7719101D0 IlmThread_2_4::Semaphore::wait\nblender.exe :0x00007FF77190F9A0 IlmThread_2_4::ThreadPool::numThreads\nblender.exe :0x00007FF771910650 std::_LaunchPad<std::unique_ptr<std::tuple<void (__cdecl IlmThread_2_4::Thread::*)(void) __ptr64,Il\nblender.exe :0x00007FF770B059C0 std::_Pad::_Call_func\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000060a4\nntdll.dll :0x00007FFDEFFF05F0 ZwWaitForAlertByThreadId\nntdll.dll :0x00007FFDEFFB3EF0 RtlSleepConditionVariableSRW\nKERNELBASE.dll :0x00007FFDEDB3C8A0 SleepConditionVariableSRW\nMSVCP140.dll :0x00007FFDD2CEBA70 _crtSetThreadpoolWait\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nMSVCP140.dll :0x00007FFDD2CC2650 std::_Winerror_message\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006c64\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FF5670 alcGetInteger64vSOFT\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001d08\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nOpenAL32.dll :0x00007FFDC8FE0080 alGetError\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003ea4\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFDEE0BA1E0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003cb8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000dd8\nntdll.dll :0x00007FFDEFFF0650 NtWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFDEFFA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071bc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nnvoglv64.dll :0x00007FFD2046D50D Symbols not available\n\n\nThread : 000058f8\nntdll.dll :0x00007FFDEFFED750 NtWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFDEDB1C480 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFDEDB1C460 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20719620 DrvPresentBuffers\nnvoglv64.dll :0x00007FFD20B35890 vk_icdNegotiateLoaderICDInterfaceVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000037dc\nwin32u.dll :0x00007FFDEDDDA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFDEF8A06F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFD206E0280 DrvValidateVersion\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002bcc\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000031b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001778\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003c94\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003e70\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000059b4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000070a4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00003fd4\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005b68\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00005508\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00002c88\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000587c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000065ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000055ec\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00006998\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00001c30\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00004bd0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 00000ee0\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000049c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000041a8\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 0000721c\nntdll.dll :0x00007FFDEFFECC80 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFDEDAF15D0 WaitForSingleObjectEx\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFDEAB019C0 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nThread : 000077f0\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFDEAB037A0 tbb::recursive_mutex::scoped_lock::internal_try_acquire\nblender.exe :0x00007FF76E319F80 tbb::internal::task_group_base::wait\nblender.exe :0x00007FF771D68EC0 blender::deg::deg_evaluate_on_refresh\nblender.exe :0x00007FF76DF8E3C0 BKE_scene_graph_update_for_newframe\nblender.exe :0x00007FF76E7B6A90 fluid_bake_startjob\nblender.exe :0x00007FF76E13D7D0 do_job_thread\nblender.exe :0x00007FF77234F320 _ptw32_threadStart\nucrtbase.dll :0x00007FFDEDE21B20 configthreadlocale\nKERNEL32.DLL :0x00007FFDEE7A7020 BaseThreadInitThunk\nntdll.dll :0x00007FFDEFFA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF76DCE0000 2.9.2.0 blender.exe C:\\Program Files (x86)\\Steam\\steamapps\\common\\Blender\\blender.pdb \n0x00007FFDEFF50000 10.0.19041.844 ntdll.dll \n0x00007FFDEE790000 10.0.19041.804 KERNEL32.DLL \n0x00007FFDEDAD0000 10.0.19041.906 KERNELBASE.dll \n0x00007FFDEF880000 10.0.19041.906 USER32.dll \n0x00007FFDEDDD0000 10.0.19041.906 win32u.dll \n0x00007FFDEF500000 10.0.19041.746 GDI32.dll \n0x00007FFDED770000 10.0.19041.746 gdi32full.dll \n0x00007FFDED880000 10.0.19041.789 msvcp_win.dll \n0x00007FFDEAAF0000 2019.9.0.0 tbb.dll \n0x00007FFDEDE00000 10.0.19041.789 ucrtbase.dll \n0x00007FFDEEDB0000 10.0.19041.906 SHELL32.dll \n0x00007FFDED920000 10.0.19041.546 CFGMGR32.dll \n0x00007FFDEEA40000 10.0.19041.546 WS2_32.dll \n0x00007FFDEE5E0000 10.0.19041.746 RPCRT4.dll \n0x00007FFDCFCF0000 7.0.0.0 openvdb.dll \n0x00007FFDCF740000 10.0.19041.844 OPENGL32.dll \n0x00007FFDEEC60000 10.0.19041.610 ADVAPI32.dll \n0x00007FFDEED10000 7.0.19041.546 msvcrt.dll \n0x00007FFDEEAB0000 10.0.19041.906 sechost.dll \n0x00007FFDEDFF0000 10.0.19041.906 combase.dll \n0x00007FFDEE850000 10.0.19041.746 ole32.dll \n0x00007FFDEEA30000 10.0.19041.546 PSAPI.DLL \n0x00007FFDEEB50000 10.0.19041.746 SHLWAPI.dll \n0x00007FFDCF870000 3.7.7150.1013 python37.dll \n0x00007FFDEDFB0000 10.0.19041.546 IMM32.dll \n0x00007FFD22410000 58.54.100.0 avcodec-58.dll \n0x00007FFDCD5C0000 58.29.100.0 avformat-58.dll \n0x00007FFDEAB40000 58.8.100.0 avdevice-58.dll \n0x00007FFDEE510000 10.0.19041.804 OLEAUT32.dll \n0x00007FFDD40F0000 5.5.100.0 swscale-5.dll \n0x00007FFDCF610000 56.31.100.0 avutil-56.dll \n0x00007FFDEDDA0000 10.0.19041.662 bcrypt.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFDC8FD0000 1.20.1.0 OpenAL32.dll \n0x00007FFDCE1D0000 2.0.12.0 SDL2.dll \n0x00007FFDEAAE0000 2019.9.0.0 tbbmalloc_proxy.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFDEFAA0000 10.0.19041.844 SETUPAPI.dll \n0x00007FFDD2CB0000 14.26.28720.3 MSVCP140.dll \n0x00007FFDEAAC0000 14.26.28720.3 VCRUNTIME140.dll \n0x00007FFDEAAB0000 14.26.28720.3 VCRUNTIME140_1.dll \n0x00007FFDE1F70000 6.10.19041.844 COMCTL32.dll \n0x00007FFDE7F50000 10.0.19041.1 AVIFIL32.dll \n0x00007FFDE6B50000 10.0.19041.546 VERSION.dll \n0x00007FFDD8550000 10.0.19041.844 GLU32.dll \n0x00007FFDEBD30000 10.0.19041.867 dbghelp.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFDD30A0000 3.5.100.0 swresample-3.dll \n0x00007FFDCDB10000 10.0.19041.546 Secur32.dll \n0x00007FFDD82B0000 10.0.19041.1 AVICAP32.dll \n0x00007FFDE28A0000 10.0.19041.546 WINMM.dll \n0x00007FFDD2C70000 2019.9.0.0 tbbmalloc.dll \n0x00007FFD5AD10000 10.0.19041.1 MSACM32.dll \n0x00007FFDD3070000 10.0.19041.1 MSVFW32.dll \n0x00007FFDDECB0000 10.0.19041.1 winmmbase.dll \n0x00007FFDED580000 10.0.19041.906 SSPICLI.DLL \n0x00007FFDEE980000 10.0.19041.746 shcore.dll \n0x00007FFDEBF80000 10.0.19041.546 kernel.appcore.dll \n0x00007FFDEB590000 10.0.19041.906 windows.storage.dll \n0x00007FFDED100000 10.0.19041.662 Wldp.dll \n0x00007FFDEADF0000 10.0.19041.746 uxtheme.dll \n0x00007FFDED6F0000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFDED5D0000 10.0.19041.844 profapi.dll \n0x00007FFDEEBB0000 2001.12.10941.16384 clbcatq.dll \n0x00007FFDE6250000 10.0.19041.789 MMDevApi.dll \n0x00007FFDED440000 10.0.19041.546 DEVOBJ.dll \n0x00007FFDE6400000 10.0.19041.906 AUDIOSES.DLL \n0x00007FFDECC30000 10.0.19041.546 powrprof.dll \n0x00007FFDECAF0000 UMPDC.dll \n0x00007FFDEAF10000 10.0.19041.546 resourcepolicyclient.dll \n0x00007FFDEF6D0000 10.0.19041.906 MSCTF.dll \n0x00007FFDC2F40000 10.0.19041.746 dataexchange.dll \n0x00007FFDE8030000 10.0.19041.746 d3d11.dll \n0x00007FFDE8EB0000 10.0.19041.906 dcomp.dll \n0x00007FFDEBFD0000 10.0.19041.746 dxgi.dll \n0x00007FFDE6B60000 10.0.19041.746 twinapi.appcore.dll \n0x00007FFDE7A20000 10.0.19041.906 AppXDeploymentClient.dll \n0x00007FFD1FA70000 27.21.14.6192 nvoglv64.dll \n0x00007FFDEA2D0000 10.0.19041.546 WTSAPI32.dll \n0x00007FFDED280000 10.0.19041.546 msasn1.dll \n0x00007FFDE6AA0000 10.0.19041.906 cryptnet.dll \n0x00007FFDED970000 10.0.19041.844 CRYPT32.dll \n0x00007FFDED040000 10.0.19041.546 cryptbase.dll \n0x00007FFDED690000 10.0.19041.804 WINTRUST.dll \n0x00007FFDEC4F0000 10.0.19041.546 ntmarta.dll \n0x00007FFDE5470000 10.0.19041.546 dxcore.dll \n0x00007FFDEB000000 10.0.19041.746 dwmapi.dll \n0x00007FFDEC490000 10.0.19041.546 WINSTA.dll \n0x00007FFDCB3B0000 10.0.19041.906 textinputframework.dll \n0x00007FFDE9960000 10.0.19041.746 CoreMessaging.dll \n0x00007FFDE9420000 10.0.19041.546 CoreUIComponents.dll \n0x00007FFDE9CA0000 10.0.19041.906 wintypes.dll \n0x00007FFDC2C70000 10.0.19041.844 explorerframe.dll \n0x00007FFDEA590000 7.0.19041.867 propsys.dll \n0x00007FFDED050000 10.0.19041.546 CRYPTSP.dll \n0x00007FFDEC7A0000 10.0.19041.546 rsaenh.dll \n0x00007FFDE53A0000 3.7.7150.1013 python3.dll \n0x00007FFDD40D0000 3.7.7150.1013 _bz2.pyd \n0x00007FFDD04E0000 3.7.7150.1013 _lzma.pyd \n0x00007FFDD04C0000 3.7.7150.1013 _socket.pyd \n0x00007FFDDFD70000 3.7.7150.1013 select.pyd \n \n# Python backtrace\n\n```\nSimply bake the file attached, I can't do it and I tried with multiple brand new .blend simple mantaflow setups.\n[Cinematic Fire Simulation.blend](Cinematic_Fire_Simulation.blend)", "Randomize Transform + Affect Only Origins, not working\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0 Alpha\n\nRandomize Transform not working as expected with Affect Only = origin. Whole object is transformed rather than just origin.\n\nin the 3d view port go Options > Affect Only and tick Origins\nselect default cube\nTransform the cube using Object>Transform>Randomize Transform\n\nCube moves/rotates/scales when I'd expect only the origin to be affected\n\n", "Mantaflow: Smoke simulation is affected by point force field in a wrong way \nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.0.0\n[particles with point force.blend](particles_with_point_force.blend)\n\n\n\n\n\n[smoke with point force.blend](smoke_with_point_force.blend)\nI have seen the issue first with version 2.8x but it is on all later versions including 3.0.\n\nI found that a point force field affects a smoke simulation in the wrong ways while it affects particles in the correct way.\n\nIn my example I use a mesh uv-sphere as emitter for a smoke simulation. I use mainly default settings in the flow emitter and smoke domain but I disabled gravity for this scene.\nA point force field is set in the middle of the sphere emitter so I would expect that the smoke became and holds a spherical shape that’s growing only in size over the time.\n\nBut the result that I see is a kind of 3d cross ( a cross on all 3 axes ). To me it seems that some vector math is not done correctly .\n\nAs force fields affect smoke and particles I did the same setup with a particle system instead of smoke domain. The uv-sphere is now the emitter . Gravity is also disabled as well as all kinds of start velocity.\nThe particles are emitted only in the first three frames.\n Then particles are affected from the point force field is set in the middle of the sphere emitter. As expected the particles always keeps the shape of a sphere as it should be.\n\nI will add blend files and screenshots to illustrate the issue.\n\n", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain moves problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\n\nIf Noise is ON then:\nsometimes Adaptive Domain position jumps between two consecutive frames and smoke jumps too.\n\nAdaptive Domain jumps problem\n(even if Domain is static - must be much larger)\n\nsometimes Adaptive Domain position jumps between two consecutive frames and smoke jumps too which is noticeable for the viewer and not acceptable.\n\nSee \"Adaptive Domain jump - Noise ON OFF.png\"… the camp fire simulation according to the book \"Learn Blender Simulations the Right Way\".\n\nIf Noise OFF, OK! Seems Noise OFF is solution to these problems but then smoke does not look good. Or Adaptive Domain OFF but then render time is soaring.\n\nBlend files without simulation data (too big) in \"AD boundary jumps\" directory shows the problem, in my simulation data most remarkable jump was between frames 353 and 354.\n\nuploaded files \"AD moves problems.7z\"\n\n\n- Open file QuickSmoke4.blend\n- Bake data + noise\n- Check next frame (353 -> 354)\n\nDomain will move.\n", "Adaptive Domain creates lines in smoke\nOperating system: Win 10\nGraphics card: Dual RTX Titans\n\nBroken: Blender 2.82\n\nWith adaptive domain enabled, noticeable horizontal (and sometimes vertical) lines appear in the smoke\n[weird lines.mp4](weird_lines.mp4)\n\nSimple blend file: \n\n - Create a large box and set it as a gas domain.\n - Create a small object as the Flow (both 'smoke' and 'fire' reproduce it)\n - Put the flow object near the bottom of the domain\n - Enable Adaptive Domain\n - Bake\n - You should see lines like this: \n # Turn off adaptive. Not only will the smoke move faster creating a totally different looking simulation (which is problem in itself) but the lines will be gone: \n\nIt's most noticeable when the domain is large, and the adaptive box is only a small portion of it.\n\nIncreasing the adaptive margin to 24 helps somewhat, but it's still there. Any higher and it defeats the purpose of adaptive - baking takes as long as just turning it off.\n\nSample blend:\n[adaptive bug2.blend](adaptive_bug2.blend)", "Volume voxels visible in compositing (Cycles)\nOperating system: Windows 10\nGraphics card: GeForce GTX 950 OC\n\nBlender 2.80 cc73d59ad580\n\nFirst of all :\nNot sure if this is a bug or if Im just not getting it.\n\nEverything is done in Cycles\n\nIm subtacting the DiffInd passes in compositing and I get the volxel shape of my smoke sim.\n\nHere a screenshot of my Nodesetup (note the backdrop)\n\n\nI do this to extract the Indirect lighting of for example fire or something else while excluding the sun and stuff.\n\n\nThis is the image (the white cuby thing to the right of the smoke)\n\n\n\n\nAdd a basic smoke simm with high resolution and a ground and wall.\nAdd a sun light\nAdd a new view layer\nExclude the smoke domain from the 2nd layer\nEnable the DiffInd pass for both layeres\n\nIn compositing :\nSubtract the DiffInd passes from each other.\n\n\nThis is an example scene:\n[debug.blend](debug.blend)\n\nIt seems like there is a problem how \"null\" surfaces get handeled.\nIf I set a layer to indirect only the indirect light only appear outside the voxels (where they are intersecting the geometry).\n", "Audio in VSE starts in wrong location when rendered with negative frames\nOperating system: win 10 \nGraphics card: GTX960\n\n2.80\n\nWith negative frames, audio starts on the first negative frame not where it is placed in the VSE when it is rendered out. (same issue in 2.79B)[test-0048-0045.mp4](test-0048-0045.mp4)\nBased on the default startup or an attached .blend file (as simple as possible).\n[VSE starts audio in wrong frame.blend](VSE_starts_audio_in_wrong_frame.blend)", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n", "Crash when rendering (Apple M2)\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 3.6.2\n\n[Rendering with GPU (metal) works fine without fire simulation, with fire simulation the render crashes, while rendering in the viewport is no problem.]\n\n\n", "Cycles smoke is not exported to render without baking\nOperating system: win 10\nGraphics card: geforce 1080 ti\n\nBroken: blender-2.80-4488056f3d9-win64\\\nWorked: (optional)\n\nSmoke is visible in viewport but not in render.\n\n\n- Select default cube.\n- Run quicksmoke\n- Select the domain and in the simulation cache settings choose `Replay`(step added to be reproducible in mantaflow)\n- Run play so you get some smoke.\n- Press f12 (or switch to cycles and press f12).\n- Renders cube but no smoke.\n\nManually setting it up gives the same result.", "Transforms: Relative Mirror with negative rotation can act like a dependency cycle\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: Unknown, possibly never?\n\nWith \"X-Axis Mirror\" and \"Relative Mirror\" pose options enabled, when both left and right sides of a bone are selected, they have a negative X rotation, and you try to translate them, they turn into a happy little helicopter and float away:\n[x_mirror_helicopter-2022-02-01_15.16.21.mp4](x_mirror_helicopter-2022-02-01_15.16.21.mp4)\n\n- File: [pose_mirror_madness.blend](pose_mirror_madness.blend)\n- Try translating the two selected bones using either G hotkey or the transform gizmo. It should break.\n- **If you only select one bone**, it works.\n- If Relative Mirror is off, it works.\n- If the X rotation of the bones is not negative, it works.\n\nVery specific bug...! The behaviour reminds me of when there is a dependency cycle in a rig, so I assume when both left and right sides are selected, they are trying to write into each other's transforms at the same time, resulting in madness.", "Smoke does not leave through open domain boundary\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.1\nunknown\n\nSmoke does not leave through open domain boundary\n\n\n\n1. start blender\n2. add fluid domain to default cube\n3. add border collision to bottom\n4. Change cache type to Modular\n5. Change gas bouyancy density to 0 and Heat to 0\n6. Add 0.5m mesh plane\n7. add fluid->inflow to mesh plane\n8. set inflow initial temperature to 0\n9. enable initial velocity to mesh plane\n10. set initial z-velocity to -1m/s\n11. bake fluid domain\n12. See how smoke is crawling up along side walls despite that border collision is not enable for these walls. I see this as a bug.\n\n[#81442.blend](T81442.blend)\n \n", "Dynamic Paint doesn't update to original values on start frame\nOperating system: win10 64\n\nBroken: 2.81\n\nAdd *Dynamic Paint (Canvas)* to any mesh and try to set 0 as a start frame of simulation.\n\n1. Open file and see how Displace modifer doesn't affect mesh\n2. Run animation -> bake current cache\n3. First problem: see how weight is empty at the mesh origin (Displace modifier works except begining of animation)\n4. Second problem: return to frame 0 -> weight doesn't updated to original values (Displace modifier still active on vertex group)\n\n[dyn_paint.blend](dyn_paint.blend)", "Smoke Domain Showing Erratically and Incorrectly\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\nWorked: I think 3.5.1 was working correctly. I tested on 3.3 and had similar problems.\n\nSmoke domains are showing in the viewport rendered view and separately in renders.\n\n\nTest file link: t-Xqh0QbgWyU\n\nSmoke domains with effects set to occur later in the file are showing as textured erratically throughout the timeline. Attached are 3 images from a render showing the problem and 2 images taken from the submitted test file. The 2 images come from the same frame - one is a screen capture of the viewport and the other is a render.\n\nTo replicate simply move through the timeline and the smoke domain will show its texture off and on until the situational, and then will continue to behave erratically.\n\n- I tried re-baking using \"Uni Cache\" instead of OpenVDB, but still with the same problem.\n\n\n\n", "Error collada import about negative numbers (source file does not have negative numbers for materials)\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: ATI Radeon HD 5770 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.42.15\n\nBroken: version: 2.83 (sub 17)\n\nTrying to import a DAE file causes sometimes errors in the console. The issue is that if there are errors in the materials it should step over these. I get this error about negative numbers in for an IOR value, but I do not see these in the file? Another point is that the import states \"Import : ok\" but nothing happens? WHen I check the DAE value, I don't see any negative numbers for any material and thus I don't understand the error given.\n\nAnother \"issue\" is, way is collada addon build in now? This used be an addon. I cant find it anywhere and looks like its compiled inside blender now,\n\n```\n+----------------------------------\n+-- Collada Import parameters------\n| input file : /Users/macpro1/Downloads/CCvision Car wrapping artwork/VW-Tcross/vw_655.dae\n| -- |\n| use units : no\n| autoconnect : no\n+-- Armature Import parameters ----\n| find bone chains: no\n| -- |\n| min chain len : 0\n| fix orientation : no\n| keep bind info : yes\n| import Image: /Users/macpro1/Downloads/CCvision Car wrapping artwork/VW-Tcross/paint_frame.jpg\n| import Image: /Users/macpro1/Downloads/CCvision Car wrapping artwork/VW-Tcross/paint_frame.jpg\n| import Image: /Users/macpro1/Downloads/CCvision Car wrapping artwork/VW-Tcross/tire.jpg\nSax FWL (Warning): Texture with sid \"Map #3-image\" not found in effect with id \"paint_frame-fx\".\nIOR of negative value is not allowed for materials (using Blender default value instead)IOR of negative value is not allowed for materials (using Blender default value instead)+----------------------------------\n| Collada Import : OK\n| -- |\n+----------------------------------\n```\n\n01 unzip linked file below\n02 Import file but using File > Import > Collada\n03 See console for errors, nothing is imported when errors occur (not ideal)\n\ntcross\n" ]

[ "Smoke cache with negative start frame doesn't read cache properly\nArchlinux x86_64\n\nBroken: Tested from buildbot 9355446\n\nSmoke simulation doesn't work as expected when using a negative cache start frame.\n\n\n1. Open [smoke_cache_negative_start.blend](smoke_cache_negative_start.blend)\n2. Bake smoke simulation\n3. Play animation; smoke does not animate, yet all the cache files appear to be generated for every frame.\n\n\n" ]

[ "'Show Instancer' option for Viewport hides the mesh in edit mode\nOperating system: Linux-5.7.8-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Alpha\nWorked: Never\n\nWhen using either Face or Vertex duplication on meshes, turning off `Show Instancer` in the Instancing settings (Object Properties) hides the parent object.\nThe problem is when you enter edit mode. Both the instancer and the instances are invisible.\nOne solution could be to unhide the instancer.\n\n - Open attached file\n - Uncheck 'Show Instancer' for Viewport\n # In the 3D View, press tab or otherwise enter editmode\n\nYou now are editing an invisible mesh - since we can select and edit the mesh, it would be much, much friendlier to allow editing, as the user probably expects this, by showing the mesh just in edit mode - it could be wireframe only or semitransparent, to indicate that it's hidden in object mode.\n\n(This may be considered an enhancement or a bug - at the very least it feels like a lack of polish in the interface, but it would be extremely befuddling to some users should they find themselves in this state.)\n[instancer_bug.blend](instancer_bug.blend)\n\n", "Outliner: Sorting not working for some types in Scene display mode\nBroken: Current master\nWorked: Never\n\n\nSorting elements in the outliner only works for objects. Scenes, collections, and other types are not sorted.\n\n<img src=\"https://projects.blender.orgattachment\">", "Object.display_type \"Solid\" behaves the same as \"Textured\"\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.8.1 26.20.13001.29010\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.79b\n\nIn a viewport set to \"Textured\" mode (either on Cycles or Eevee), setting Object.display_type = \"SOLID\" still shows a textured object.\nOn Blender 2.79 this property was called \"Maximum Draw Type\" and was behaving as expected.\n\n1.-Set the viewport to Textured mode.\n2.-Select a textured object and set its property \"Display As\" to Solid.\nIt will stil be shown as Textured so theres no difference between the two modes (Solid, Textured)\n\nBlender 2.81\n\n\nBlender 2.79b\n\n\nExample blend.\nThe viewport is set to \"Textured\", the monkey set to \"Solid\" but is shown as Textured.\n[solid_object_display_type.blend](solid_object_display_type.blend)\n", "Prompt when entering sculpt mode on non-uniform scaling\n### Motivation\n\nIn the sculpting workflow it is a common step to always apply the scaling of an object so that the tools, brushes and operations work as expected.\nThis is adding extra steps for the user for something that could be automated or fixed. It also confuses most beginners who need to learn this the hard way.\n\n### Proposal\n\nAdd a prompt when entering sculpt mode on an object that has non-unform scaling. This popup will behave similarly to enabling dyntopo while having object data that could be destroyed by using that option:\n\n\nThis popup will ask the user \" Warning!\"\n\"You are entering sculpt mode on an object with non-uniform scaling values. We recommend to apply the scaling of the object before proceeding.\"\n\nIt will then offer 2 options: \"Apply Scale\" which is highlighted and will be used when pressing enter, and \"Don't Apply\" which enters sculpt mode regardless without applying the scale.\n\nIf the scaling is applied the normals should also be recalculated if the scale was negative. This will save the user some trouble of going into edit mode and doing this manually.\n\n### Issues\nCertain bugs would lead to progress being destroyed such as #74361.\nThese need to be resolved first.\n\nAlso ff the user wants to keep the scale intact it will also prompt them every time they enter sculpt mode. Potentially this is not ideal but still better than not having the prompt.", "Instanced wire objects are hidden in solid mode instead wire appearance\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\n\nIf I instance wireframe (only edges) object with GN, I don`t see instances in Solid mode (except 1st).\nWireframe mode is okay.\n\n[GN Stack wire.blend](GN_Stack_wire.blend)\n[2021-03-19_12-47-47.mp4](2021-03-19_12-47-47.mp4)\n\n**Edit:** also can be reproduced without geometry nodes:\n[2021-04-28 13-23-38.mp4](2021-04-28_13-23-38.mp4)\n\n- Open attached file\n- Switch between Solid and Wireframe View\n[missing_wires.blend](missing_wires.blend)", "Hair: changing children related settings in objectmode dont show when switching to particle editmode\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.83.7\nWorked: 2.79\n\nWhen I change additional options like Clumping, children not updates and their update stuck for edit mode for any try except 1st. \nDemonstration and details:\n[2020-10-15_01-46-01.mp4](2020-10-15_01-46-01.mp4)\n\n#69000 (Hair: changing children related settings not updating in particle editmode) is very much related", "GPU Subdivision: Wrong objects statistics information\nWindows 10\ni7-4790\n16 GB RAM\nRTX 2070\n\nBlender v3.4.1 (Steam)\n\nWrong objects statistics information in object mode when GPU Subdivision is enabled\n\n- Open `Rat.blend` file\n- Enable GPU subdivision\n- Rotate/move the bone\n- Switch to object mode (notice the viewport statistics)\n\n\n\n", "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "Unnecessary Proportional editing in Sculpt Mode.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 and 2.82 (sub 1)\nWorked: (optional)\n\nthis is probably not a bug but more of a design since Sculpt mode now has regular transform tools.\n\nI accidentally found out that if you enable Proportional editing then going to Sculpt mode the Transform tools will show Proportional editing & it's hotkeys in the Status bar.\n\n * Enable Proportional editing in Object mode.\n * Enter Sculpt mode.\n * Use any tool of the Transform tools.\n", "Sculpt mode: brush strength jump, when brush switches between two parts of mesh\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 3.0.0 Alpha\n\nWhen brush jumps from one mesh to another its strenght increases for a moment.\nHere is demo and file for tests:\n\n\n[2021-05-13_21-10-24.mp4](2021-05-13_21-10-24.mp4)\n\n[jump.blend](jump.blend)", "Color attributes in sculpt mode not showing in instance objects\nOperating system: Linux-5.15.0-47-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00\n\nBroken: version: 3.4.0 Alpha\n\nWhen sculpting an object its instance reflect the changes after the stroke, but not with color attributes, you have to go out of sculpt mode to see the color attributes.\n\n1. Open a new sculpt file.\n2. Make and instance in object mode with Alt D\n3. Enter sculpt mode of the original object.\n4. Paint some color attributes\n5. Sculpt with clay brush to see the expected behavior.\n\n[Grabación de pantalla desde 17-09-22 16:08:53.webm](Grabación_de_pantalla_desde_17-09-22_16_08_53.webm)\n\n\nOne funny thing is that if you give the original object a mirror modifier, the changes to the instance are in real-time, not after the stroke, both for sculpt and for paint. But not when you sculpt or paint in the one without the modifier.\n\n\n[Grabación de pantalla desde 17-09-22 16:22:16.webm](Grabación_de_pantalla_desde_17-09-22_16_22_16.webm)\n\n", "Sculpting/Painting on invisible objects\nOperating system: Linux-6.5.2-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.54, 6.5.2-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-b492f73f87)\n\nBroken: version: 4.0.0 Alpha\nWorked: ---\n\nThis is an inconsistency that I noticed when toggling between collections of objects while working on an asset. It's most likely not a regression.\n\nIn edit mode it's impossible to operate on the selection if the object is currently hidden. This is very helpful to prevent mistakes and as feedback that you might be editing the wrong object atm.\n\nWhile in sculpt mode or any of the painting modes this is not the case. If the object is currently hidden while in sculpt or weight paint mode, it is possible to use the brushes on the geometry.\n\nIdeally any operation should be prevented if the object is hidden.\n\n1. Enter edit mode.\n2. Select everything.\n3. Hide the object or collection in the outliner.\n4. Try to move or otherwise edit the selected geometry.\n5. Show the object again (No edits should have happened).\n6. Enter sculpt mode and hid the object/collection again.\n7. Use a brush on the hidden object.\n8. Show the object/collection (See the edits that have been done).\n\n", "Copying in edit-mode copies the entire object, not the selection\nthere is an issue occurs when a part of (mesh) is copyed in the edit mode \nwhat happens when copying one part of a (mesh) and pasting it\nyou suppose to get this part only pasted ,but instead you get the whole (mesh) pasted\n\nfor examble if you have a cube model with a single face selected in the edit mode \nif you copyed then pasted it the result is the whole cube modele is pasted rather than the single face \n \n \n\n", "Wrong undo/redo sequence with direct transform change (via Item/transform panel or addon)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: version: 2.93.1\n\n\nUndo operation is not working properly with `Copy attributes addon`.\n[refer the video to understand the situation better]\n\n\n**Exact steps to Reproduce the error**\n\n[2021-07-28_13-59-32.mp4](2021-07-28_13-59-32.mp4)\n\n**To reproduce**\n- 0. Make sphere, go to sculpt mode.\n- 1. Draw «1» on sphere\n- 2. Change location via item panel\n- 3. Draw «3» on the sphere\n- 4. Undo actions with {key Ctrl+Z}: undo order is broken\n\n---\n\n**Exact steps to Reproduce the error (Addon Case)**\n\n- Open .blend file\n- Enable Copy attributes addon\n- Select both mesh objects\n- Do {key Ctrl C} -> `Copy Locations`\n- Switch to edit mode\n- Perform some changes to the mesh\n- Switch to object mode\n- Perform undo operation.\n\n[Notice that the undo operation ignores all the steps from edit mode and directly switches the mesh to the initial position]\n\n\n[2021-07-27_13-33-38.mp4](2021-07-27_13-33-38.mp4)\n\nTest File:\n[#90234.blend](T90234.blend)", "When Object is not selectable it can still be switched to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0\nWorked: dont know\n\nWhen a object is disabled for selection in the outliner and the object is then selected in the outliner its possible to enter any of the interaction modes. \nI would assume if a object is not selectable this should not be happening. \nNote: it only happens with single object selections. \nMaybe this is by design, it just felt like a strange thing and i thought i report it just in case.\n\n1. Create a object\n2. disable the object selection in the outliner \n\n3. Choose your interaction mode \n\n4. The mode changes to the one you selected \n\n" ]

[ "mesh is not updated when select different object in sculpt mode\nOperating system: Linux Mint 18.3 Cinnamon 64-bit\nGraphics card: Nvidia Geforce 760\n\nBroken:d59c4c9d61a\n\n**mesh is not updated when select different object in sculpt mode**\n\nfrom factory settings\nduplicate the default cube and place near to the original one\nswitch to sculpt mode\nuncheck the \"Lock Object Modes\" in the edit menu\nperform some sculpt\nalt + left click to select the other cube\nthe cube you just sculpted shows the shape it had before sculpting", "Sculpted changes dissapear visually when selecting a second object\nwin10 64, nvidia 1060\n\nBroken: blender-2.80.0-git.606223f6a61-windows64\n\nWhen you disable \"Lock object mode\" in the Edit menu, and sculpt on one ojbect, if you select a second object, the sculpted changes will \"disappear\" from the first. The changes are still there, you just have to select the first object and you can see them, but selecting back and forth between the two objects will make the changes appear and disappear. And in order for this to not happen, you have to get out of Sculpt mode, but it will happen once you sculpt again.\nUsing the attached blendfile, make sure \"Lock object mode\" is disabled in the Edit menu. The red monkey is already selected and in sculpt mode. Sculpt visible changes on the red monkey, select the white monkey (right click select presumably) and see the changes dissapear, select the red monkey again and see the changes come back.\n\nAnimated gif:\n\n\n[bug3.blend](bug3.blend)", "Dyntopo Sculpt on 3 Objects with Lock Object Modes Off\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon R7 450 ATI Technologies Inc. 4.5.13507 Core Profile Context 23.20.15032.11\n\n\n2019-04-23 12:31 Hash 5a144c797a3b Blender 2.80 Beta buildbot\n\n\nTurning off Lock Object Modes so that I can sculpt in dyntopo on 3 separate mesh objects, and selecting each and switching to Sculpt mode I found that the object doesn't hold the updated sculpt info for view once you select the next one, it returns to the previous state until you select it again. I also found that saving the file will cause it then to show that last sculpted position and tesselation count, but once sculpted it will also switch again once deselected until save again.\n\nSteps: duplicate the default cube, once or twice and then turn off Lock Object Modes, select each in turn and swap to sculpt mode and set to dyntopo. Select the first, sculpt, select the second and watch the first snap back to the starting shape. Sculpt the second, select the first and then watch the second revert temporarily while deselected. Save the file after some sculpting and then see the saved shape will be where they revert to. Attaching a simple example.\n\nI used this method of sculpting on several objects in 2.79b a lot, makes it easier to work with complicated subjects. Thanks for looking!\n\n[three_cubes_sculpted.blend](three_cubes_sculpted.blend)\n\n", "switching objects in sculpt mode - not showing previous objects sculpting work\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\n\nBroken: version: 2.80 (sub 53)\nWorked: (optional)\n\n\nselecting different objects in sculpt mode problem\nsee video below as it's easy to explain by showing you :)\n\nopen?id=1Wqcyxv5WpfeZKlC2CMt3ljdKlblVGCcf\n\n\n", "Sculpt Mode Doesn't Update When Selecting Other Objects Without Leaving Sculpt Mode\n\nOperating system: Windows 10\nGraphics card: Gforce GTX 1050 Ti\nBut I am a teacher and I am using Blender 2.8 in my classes at the university I work. This bug happens in different hardware configurations.\n\n\nBlender 2.80\nDate: 2019-03-04 11:00\nHash: 2644ef8f49b\n(Tested today, but this has been happening for a while)\n\n\nWhen you have more the one geometry in the scene, enter the Sculpt Mode of one of them, sculpt something, and select any other geometry with Alt+Clic (\"Lock Object Modes\" Must be disabled in the Edit Menu), the modifications made in the sculpted object doesn't display. For them to be displayed you have to select the object and leave sculpt mode. This is very bad for those who like to sculpt with multiple objects at the same time to merge them in the end (with pro booleans or other tool like that).\n\n\n1 - Creat at least two geometries.\n2 - Enter the Sculpt Mode of one of them.\n3 - Sculpt Something;\n4 - Disable the \"Lock Object Modes\" option in the Edit Menu.\n5 - Select any other geometry without leaving the sculpt mode (With Alt + Click)\n6 - You will see that the modifications made in the first object will not be visible. The object will have the original appearance. \n\nBased on the default startup." ]

[ "Hiding a nested collection doesn't immediately update its parent instances in the scene\nBroken: 483ae407d9d1 (blender2.8 HEAD)\nWorked: ?\n\nHiding a nested collection doesn't immediately update its parent instances in the scene.\n\n\n[outliner-deg.blend](outliner-deg.blend)\n\nHide the `Torus` collection (via the screen icon), this should hide this collection objects in the `B - I Instanced a torus` collection, however it doesn't unless you save and re-open or force depsgraph update in other ways.\n\n\n\nIf you toggle the `A - I have a torus` collection off, this one affects the instanced visibility immediately.\n\n*Note 1: The file only has Empties because I was looking at the depsgraph image and it was giving me a simpler depsgraph this way.*", "Crash: Custom Panel UI Toggle while Undoing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83 (sub 4)\nBroken: 2.82\nBroken: 2.81\n\n\nRead Access Violation when toggling custom UI button and repeatedly undoing. Crash unlikely to happen first time but will happen eventually. In the video, I toggle a few times, then hold Undo while toggling. (Video shows exact steps)\n\nSometimes it can take a bit of time before the crash happens. It might happen faster if you reload the file then repeat the toggling process.\n\n\nOpen attached .blend File\nRun Script\nGo to 3DView -> N -> Panel \"Crash\"\nToggle the button a few times\nHold Undo while continuing to toggle the button. \nCrash occurs eventually.\n\n\n[crash_simpler_vid.mp4](crash_simpler_vid.mp4)\n\n[crash_simpler1.blend](crash_simpler1.blend)\n\nBelow is a pic of where the exception is thrown (Blender version for source pic attached)\n\n\n\n\nThank you for your time and hard work.\n\n\n\n\n", "Improve UX for interaction of modifier stack and node editor\nWhen a non-nodes modifier is selected as active modifier there is no indication or way to change that in the geometry nodes editor and it's very confusing for the user, especially when the properties editor is not displaying the modifiers panel.\n\nThis is related to #84927\nA potential solution has been proposed there as well (move towards interface similar to shader editor and material slots).", "Lasso Select Broken if Select key is changed from Default Left to Right\nOperating system: Windows 10 (Home)\nGraphics card: Nvidia 1070 \n\n**Blender Version** \nBroken: 2.90.0 (Steam)\nWorked: Not sure, Has been like this since before 2.79b\n\nWhen the default select mode is changed from Left to Right Mouse button Lasso Select no longer works with Tweak + RMB Any. \n\nSplash Screen Change on initial set up or Select button or Edit - Preferences - KeyMap - Select With Mouse Button\n\nAffected: any View Mode that has the Lasso option. (Edit mode, Object Mode, Grease Pencil, etc)\n\n\nSee attached MP4.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nStart Blender and use Start up Cube. [BlendBug_2.mp4](BlendBug_2.mp4)\n\nTemporary fix if the Select key is changed from Left to Right Mouse Button is to walk through the KeyBindings and set anything that uses Lasso to Tweak Right and anything that was using Tweak Left to Tweak Right where Lasso is was changed. ", "Add Ico Sphere in edit mode adds misshaped ico sphere if object has shape keys\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nWorked: (Probably never, I tried a few older versions including Blender 2.79)\n\nWhen an ico sphere is added to an object in edit mode, if it has at least the \"Basis\" shape key the ceated ico sphere is mishaped.\n\n- create a new blender file\n- select the default cube\n- DON'T DELETE IT!\n- add one shape key to get the \"Basis\" shape key\n- go to edit mode\n- Add (Shift A) ▸ Mesh ▸ Ico Sphere\n- in the Add Ico Sphere menu, increase subdivisions to see the mishaped parts better\n\nSee attached video. Without shape keys the ico sphere is flawlsess but with shape keys is misshaped.\n\n", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Apply modifiers on objects with shapekeys (with some exceptions)\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nCurrently it is not possible to apply modifiers to an object that has shapekeys, even though it would be technically possible for most modifiers. I suggest making it possible to apply modifiers to objects with shapekeys with some exceptions.\n\n\n\nFor example:\n\nThe subdivision and wire modifier does not modify the objects topology as the shape change. This modifier could be applied while still keeping the shape keys.\n\n---\n\nScreen capture example of how to apply modifiers and keep shapekeys.\n[apply modifiers with shape keys.mp4](apply_modifiers_with_shape_keys.mp4)\n\n---\n\nModifiers that can't be applied in a simple way when the object has shapekeys.\n\n- Boolean\n- Build\n- Decimate\n- Geometry nodes (in some cases. Easiest to just exclude this modifier)\n- Mirror (**IF USING BISECT**)\n- Remesh\n- Skin\n- Volume to mesh\n- Weld\n- Explode\n- Fluid\n- Ocean\n- Particle instance (Since source particle system density mapping can be applied in world space)\n- Particle system \n\n\n\nWhen the user tries to apply any of these modifiers when the object has shape keys, the error message should be:\n***Modifier that changes topology based on shape cannot be applied to a mesh with shape keys***\n\nNote:\nWhen applying a modifer of type \"Modify\" (for example \"Data transfer\"), the current shape should be used when applying the modifier (i.e. the resulting shape of all combination and values of the objects shape keys)\n\n\n", "Modifier re-evaluation makes editing dimensions unreliable\nCurrently editing dimensions uses the bounding box that's recalculated while dragging.\n\nThis can cause a feed-back loop as the objects scale is used by some modifiers which calculate a new bounding based on the scale which is then used in dimensions.\n\nIn the case of armature modifier - any zero scaled axis makes causes the mesh to scale into a single point, making any further changes to the dimensions not have any effect.\n\n----\n\nOriginal report:\n\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Blender 2.79\n\n\nIf object is rigged scrolling its dimension value toward zero causes object to disappear, even if right mouse button has been clicked in order to cancel a scaling. So blender accepts a scale of zero even if left mouse button hasn't been released yet, Is it an expected behavior in Blender 2.8?\n\n\n\n\n - Select the cube.\n - Scroll any of its dimensions value toward zero without releasing the left mouse button\n - Cancel scrolling by right mouse button click.\n\n\n\n[Bug_report.blend](Bug_report.blend)\n\n", "Blender crashes when using an EnumProperty to set Space\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nIn this script, I'm using `context.area.type` with a property to change the Space type. It caused Blender to crash.\n\n1. Running this script from the Text Editor (below)\n2. Switch to Graph Editor or Dope Sheet\n3. Click new property buttons on right of Header\n\n```\nimport bpy\nfrom bpy.types import PropertyGroup\nfrom bpy.props import EnumProperty\n\ndef set_space(self,value):\n context = bpy.context\n\n for area in context.screen.areas:\n if area != context.area:\n break\n\n override = {'region': area.regions[0]}\n\n if value == 0:\n context.area.type = \"GRAPH_EDITOR\"\n elif value == 1:\n context.area.type = \"DOPESHEET_EDITOR\"\n\nclass SWITCH_PG_switcher_props(PropertyGroup):\n space: EnumProperty(\n name=\"Space Target\",\n description=\"Switch to space\",\n items=(\n ('GRAPH_EDITOR', \"\", \"Graph Editor\", \"GRAPH\", 0),\n ('DOPESHEET_EDITOR', \"\", \"Dopesheet Editor\", \"ACTION\", 1),\n ),\n default='GRAPH_EDITOR',\n set = set_space\n )\n\ndef draw_enum(self, context):\n layout = self.layout\n scene = context.scene\n layout.prop(scene.switcher, \"space\", icon_only=True, expand=True)\n\ndef register():\n bpy.utils.register_class(SWITCH_PG_switcher_props)\n bpy.types.Scene.switcher = bpy.props.PointerProperty(type=SWITCH_PG_switcher_props)\n bpy.types.DOPESHEET_HT_header.append(draw_enum)\n bpy.types.GRAPH_HT_header.append(draw_enum)\n\ndef unregister():\n del bpy.types.Scene.switcher\n bpy.types.DOPESHEET_HT_header.remove(draw_enum)\n bpy.types.GRAPH_HT_header.remove(draw_enum)\n bpy.utils.unregister_class(SWITCH_PG_switcher_props)\n\nif __name__ == \"__main__\":\n register()\n```\n\nSetting the `context.area.type` in Python seems to cause others' scripts to crash:\n[Performing a Translate Operation after switching the context area crashes Blender ](1164763)\n", "Able to paint/select \"through\" disabled UI items.\nBroken: 2.80, 2.81...\n\nWith region overlap, if a UI element is diabled, clicks are passed through it, which can result in paint strokes.\n\n\n1. Load the default scene and enter Texture Paint mode on the cube.\n2. Add a paint slot and make a stroke.\n3. In the UV/Image editor, select the painted image, open the sidebar and switch to Image tab. The UI items should be disabled there now.\n4. Make sure that sidebar overlaps the image.\n5. Click on sidebar background.\n6. Click on any of the disabled items.\n\nIn (5), nothing happens. In (6), the click passes through and leaves a paint stroke on the image.\n\n", "bpy.ops.paint.image_paint with a texture requires initialization with manual paint stroke otherwise color not quite right\nWin 10 5820K GTX 970\n\n2.79b and latest daily build\n\nbpy.ops.paint.image_paint with slightly wrong colors when painting on object with texture on brush before a manual paint stroke applied\n\n1. Load attached file\n2. Run script\n3. With mouse over the cube - press space and type Simple Modal Operator to activate modal paint operator\n4. move mouse about to paint. \n5. left click to stop modal paint operator\n6. now paint on the cube normally by holding mouse button down\n7. you will see this is a slightly different color \n8. press space and type Simple Modal Operator to activate modal paint operator again\n9. move mouse around\n10. you should now see modal operator painting correctly\n\nThis seems to happen each time I change the texture on the brush to a new one (with obviously different colors on it)\n\nImage is attached showing this.\n\nPossibly something not being initialized properly?\n\nThanks you in advance for any work on this.\n\n[modal_paint.blend](modal_paint.blend)\n\n\n", "New shapekey features potentially destroy mesh shape on old files on tab-tab\nFedora GNU/Linux 64 bit v 21/ intel cpu / nvidia gpu \n\nBroken: Current Master\nWorked: 2.73\n\nSome shapekey enhancements seem to cause a problem on some old meshes, destroying basis shape just by tabbing in and out of edit mode\nselecting the mesh and pressing 'tab tab' creates the error. Not that even though there appears to be an active shapekey, the buttons for pinning etc. are not visible.\nIf one first selects a shapekey and *then* tab tabs, the bug goes away. however, this can cause loss of work/destroyed meshes if the user does not notice in time.\n1- download the attached [gilgatest.blend](gilgatest.blend)\n2- open the file, the mesh should be selected\n3- note the appearance of the shapkey panel: even though basis appears active, the pin button and associated area does not display\n4- without clicking anywhere else, press tab-tab in the 3d view (enter and exit editmode)\n5- note that the appearance of the mesh changes - if you save this it is not revertable\n6- don't save\n7- reopen the original file\n8- this time, click once on the Basis Shape\n9- observe that the relative checkbox, pin, and display in edit mode buttons all appear.\n10- press tab tab in the 3d view\n11- observe that the mesh shape does not change\n\n\nFinal notes:\nIn my opinion this is quite severe if/when it hits, as the user (in this case me) might not notice and end up doing a bunch of work in a file, saving and committing it. In my case, since I have SVN I can revert and redo that work. Other people may not be so lucky.\n\n", "\"Shape Key Edit Mode\" toggle for correct mesh deformations\nWhen using the toggle \"Shape Key Edit Mode\" it gives me a representation of all shapekeys mixed together but it's only a visual preview. \n\n\n\nIt doesn't affect the result of rotating or scaling the mesh since you still only work on the shapekey that is selected instead of the mixed representation that is shown. \nAnd since it's all just based on vertex location the results can be pretty odd, especially when using the 3D cursor as a pivot point. \n\n[2019-07-15 11-23-25.mp4](2019-07-15_11-23-25.mp4)\n\nSince working with multiple shapekeys is a great way to work non-destructively it would be a big improvement if the mixed shapekey representation would also be used for any deformations made.\nThis could be by default or as an additional toggle.", "UI: Excessive cut-off while searching in keymap preferences\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001\n\nBroken: version: 3.1.0 Alpha\nBroken: version: 2.50alpha1 (searchbox for input first appeared)\nWorked: never\n\nWhen searching in keymap text name of a category will be cut too much.\nIt does not happen with add-ons or properties editor search.\n\n1. Open Keymap in preferences.\n2. Resize window. Notice that category name will be cut off only when it really doesn't have any spare space.\n3. Start searching for anything, for example `grease pencil`.\n4. Resize window. Now category name will be cut off way too easily, having spare space several times largen than it's full text.\n[Excessive cutoff2022-01-19 12-55-36.mp4](Excessive_cutoff2022-01-19_12-55-36.mp4)", "Remove BKE_layer_collection_resync_forbid and BKE_layer_collection_resync_allow\nThese can be removed after each area has been checked and optimized to use the new structure (synced_ensure)\n\nRecently ceb0e7fcea was done and added a use for resync_forbid. This makes this ticket perhaps irrelevant?" ]

[ "Changing keys in Transform Modal Map collapses menu\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14800 Core Profile Context 22.3.1 30.0.15002.1004\n\nBroken: version: 3.2.0\nWorked: Perhaps never worked\n\nIn the keymap editor if you try to change hotkeys in Transform Modal Map, menus that you just expanded will collapse back to default state as shown in video.\n\nOpen Blender → Go to Preferences → Keymap → 3D View → 3D View (Global) → Move → Transform Modal Map.\nThen change any hotkey (example X to A).\nAfter that expanded menu will collapse.\n\n[0aX7cATEU9.mp4](0aX7cATEU9.mp4)\n" ]

[ "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "Python API: Mesh editing: Editing uvs after normals with a previously assigned variable doesn't work\nBroken: 3.5.1\nWorked: 3.4.1\n\nCaused by 6c774feba2\n\nHolding on a variable referencing the uv layer data for later uv editing, doesn't work when normals are edited in between\n\nRun the attached python script in Blender 3.5.1\nThis creates three objects, all should have all their loop uvs as 0,0:\n\n- no_set_normals (should have default normals, sideways)\n- with_set_normals_and_reaccess_uv (should have upwards +z normals)\n- with_set_normals_but_no_reaccess_uv (should have upwards +z normals)\n\nGo in edit mode on each generated object, look at the normals and uvs\nThe results are only correct for no_set_normals and with_set_normals_and_reaccess_uv\nFor with_set_normals_but_no_reaccess_uv, neither the uvs nor normals are correct. Both appear to be defaults\n\nIn Blender 3.4.1 this works as expected, i.e. with_set_normals_and_reaccess_uv and with_set_normals_but_no_reaccess_uv are identical\n\nAttached are also screenshots in 3.5.1 of the normals and uvs of each object\nAnd a screenshot in 3.4.1 showing the expected results\n\n**Guess at what's happening**\nOn more complicated cases (actual meshes with hundreds of triangles), the normals are messed up (seemingly random instead of defaults) and Blender is prone to crashing. This leads me to believe holding on the uv layer data after normal editing accesses freed memory or something like that?\n\n", "Update Tweak Tool behaviour on Right Click Select\nThis has been a long running known issue for the Active Tools when using right click select.\n\n## Issue\nOn RCS, the Tweak Tool in the toolbar is placing the 3D Cursor instead of tweaking elements.\nThis duplicates the behaviour of the Cursor Tool (right next to it in the toolbar).\n\nThe reason for this seemed to be that right click & drag is already using the tweak action.\nIf the Tweak Tool would tweak with left & right click then there is no way of setting the 3D cursor anymore.\n\nBut the Tweak Tool doesn't require the 3D cursor. And this workaround is breaking the tweak tools purpose.\n\n## Solution\n\nThe Tweak Tool needs to tweak with left click & drag.\nThis can be it's own keymap item in the preferences under the Tweak Tool.\nRight click & drag can still use the default tweak action in the preferences.\n\nThe benefits are:\n- The Tweak Tool can be used without a drag threshold with left click & drag, if the option \"Alt Cursor Access\" enabled in the preferences\n- There is a functional distinction between the Tweak Tool and the Cursor Tool.", "UV Editor Snap Active to Vertex is Not Working\nOperating system: Linux-5.19.0-38-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.0\n\nI can not snap active to vertex, no matter what I try it acts like it is in median mode.\n\n\n\n\nIn the startup file snapping is enabled. In the uv editor try to move the selected vertex to snap to another vertex. Or try to snap a face instead, same issue. Sync mode on/off doesn't change the behavior.\n\n", "snap to face broken with mirror modifier\nOperating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits\n(same behavior on Windows 8.1)\n\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\nBroken: version: 2.81 (sub 11)\nAlso broken in 2.80 stable\n\n* open demonstration blend file with no config dir\n* note that snap-to-face (target:closest, affect:move) is already enabled\n* select small cuboidal in lower left\n* G, then X, to move along X, and attempt to snap to broad side of nearby horizontal cuboidal\n* see that the object flashes erratically, alternately assuming its original position, and alternately assuming an incorrectly snapped position\n* if instead the cuboidal we are trying to move is moved a bit first, without snapping, and then we again try to snap to the face, it doesn't flicker any more, but it still snaps incorrectly (and actually still does flicker on the overlapping face but doesn't jump around in position)\n* if the mirror modifier on the cuboidal we are trying to move is disabled, it snaps correctly\n\nStarting position: \n\nIncorrect snap result: \n\nCorrectly snapped result: \n\nDemo blend file: [snapbug.blend](snapbug.blend)", "Offset Edge Tool Menu Rescaling Makes It Impossible To Use\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.3 26.20.13025.1004\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nName: Edit Mesh Tools (0, 3, 6)\nAuthor: Meta-Androcto\n\nThe tool menu ad the bottom left of the viewport pops between sizes making it impossible to use\n\nselect edges, use the offset edge with extrude option.\nopen the tool menu in bottom left of 3D viewport, then switch between Angle or Depth option a few times.\nNow hovering over either the Depth or Angle button will trigger it and rescale the menu. This moves the other button up making it impossible to select.[edit menu pops up and down.mp4](edit_menu_pops_up_and_down.mp4)\n\n\n", "Rebind default 'Set 3D Cursor' hotkey to Shift+Alt+Middle doesn't work\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.47\n\nBroken: version: 2.93.0, 3.4\nWorked: it was working with 2.92\n\nRebinding the default Shift+Right press hotkey to Shift+Alt+Middle press hotkey doesn't work. It moves the 3D cursor but I can't drag it everywhere I want like the default behavior.\n\n- Find the default shorcut by typing cursor to the search bar\n- Under 3Dview there is Set 3D Cursor (view3d.cursor3d)\n- Change the default to Shift+Alt+Middle\n- It doesn't work as expected\nioGcz_mV78k", "Select Circle doesn't apply changes to radius while running back to active tool\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 5)\nWorked: (optional)\n\nIf i change radius with LMB+MScroll, it resets to initial after LMB release\n[2020-03-02_21-20-49.mp4](2020-03-02_21-20-49.mp4)\nIf it is by design, I can`t find hotkeys to change circle radius permanently.\nI am trying to replace C-selection with this tool in my pipeline because it allow to rotate around object.\nFor me mass selection looks like this: take big brush, select big mass, change brush to smaller one, correct selection, zoom in and manually select/deselect certain faces/points. So I don`t see the point to have temporary radius for 1 stroke.\n\nI asked few skillfull guys. They still use C-selection, because it keep it`s radius.", "No (selection) tool in Image editor mask mode (Left-click and drag selection doesn't work)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nLeft-click and drag selection doesn't work in Image editor -> Viewer Node -> Mask mode\n\nCreate a mask in the Image Editor and try to select it with left-click and drag selection\n\n\n", "Interface. Sculpt mode, checkbox title not react to click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 375.70\n\nBroken: since 2.83.9, checked with version: 2.93.0\n3.0 alpha broken too\n{[F10178598](изображение.png) size=full} — here\n\n\n[2021-06-18_00-08-00.mp4](2021-06-18_00-08-00.mp4)\n", "3D View Selection Occlusion (Select Through) \nCreating this design task as there are unresolved issues with [D6322: Mesh: Select through](D6322) which are more design issues.\n\nThis is a place holder, some topics to address:\n\n- Where this option is stored, accessed?\n- Which selection tools/operators should use this?\n- Which modes this should be supported in (edit, pose, grease pencil... etc)\n- How to display this option when in wire-frame display (when the user will always select-through)\n- How to access this from both active-tools & key-bindings?\n- How to make it obvious selecting-trough is enabled *(draw style, cursor - this might help avoid confusion)*.\n- Should this be supported in object mode too?(the reverse since objects already select-through), IIRC we discussed having this option for box select too.\n\n\n### Related Topics\n\nNote that there are topics being raised which relate to select-through, but might be best treated as separate topics since we could change behavior here with or without select-through.\n\n- Current behavior of X-ray.\n- Current usability toggling X-ray (Z-drag or Alt-Z).\n- Selecting faces by their centers.\n- Lasso select using object centers #64281 (Option to lasso-select using geometry instead of object centers.).\n", "Backface culling is not working for mask in edit mode\n2.80 (sub 45), 893fa598319e, 2019-02-24 22:02\n\nAnd wireframe too heavy.\n\n\n\nIdk if it is bug or intended, but it will be nice, if it will work like on the 2nd or 3rd picture: much more readable.\nAnd when x-ray is on, wireframe on the background will be faded too, accordingly slider-setting.\n\n\n\n\n", "Mesh flickers in edit mode if shapekey added\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.0.0 and later\nWorked: 2.93\n\nThat mesh I put in .blend file is from my old project (started in 2.79). For some reason normals on that mesh go crazy if I try to edit it in Face selection mode. I found that this particular mesh can't have shapekeys and auto smooth enabled at the same time.\n\n1. Add Basis shapekey to the mesh\n2. Enter Edit Mode\n3. Select Face Selection Mode\n4. Move any face\n\n[bugFlicker.blend](bugFlicker.blend)\n[bandicam 2022-12-03 01-21-18-089.mp4](bandicam_2022-12-03_01-21-18-089.mp4)", "Inset operator modal handling misses option to toggle \"Offset Even\" via shortcut\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nNoticed problems when using Inset Faces tool in Edit Mode. If I'm using the select tool and I press **I** to activate the tool Inset Faces tool its menu doesn't display anywhere so I can't choose Even for example. If I click on the tool icon then it works, even if I then use **I** to activate the tool. This makes it so I can't use shortcut keys anymore. I suspect this is happening with other tools as well. Another thing worth noting is that the status bar says the Call Menu is triggered by the right mouse button but it actually just closes the tool.\n\n\n\n\n\n\nGo into edit mode with the default cube. Select a face. Hit I to activate the inset faces tool. Notice that the options for the tool aren't available.\n\n", "Bevel profile incorrect when using arc for inner miter\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.07\n\nBroken: version: 3.3.0 Alpha\n\nThe Bevel operation and modifier has an incorrect profile when the inner miter is set to arc and the profile value is either very high or low.\nthis happens in both edge bevel and vertex bevel mode.\n\n|Inner miter sharp (Ok):\n|---\n|\n\n|Inner miter arc:| \n|---|---\n||\n|Shape 0.93|Shape 0.5\nIn this case the Bevel kind of overshoots.\n\nProbably related to #95916 (Pinching effect when using bevel and bevel modifier).\n\n- Open attached .blend file\n[Test.blend](Test.blend)\n\nThank you and have a great day!\n\n---\nUPDATE:\nIn some cases it can also happen with Inner Miter Sharp (#105064)\n" ]

[ "Regression: Extrude tool settings reverted after tool switching\nOperating system: Linux Mint 20.2 Cinnamon\nGraphics card: GeForce GTX 750 Ti\n\nBroken: 3.0.0, master\nWorked: 2.93.6\nCaused by 082ddc9379\n\nThe \"XYZ\" option under Extrude Tool always gets reset to \"Normal\" after changing the tools\n\n1. Switch to Extrude Tool\n2. Change \"Normal\" mode to \"XYZ\"\n3. Switch to any other tool\n4. Switch back to Extrude Tool\n5. The mode is back to \"Normal\"\nExpected result (2.93.6 works this way): The mode should stay on \"XYZ\"[bug-2021-12-06_10.30.38.mp4](bug-2021-12-06_10.30.38.mp4)", "Extrude Tool Regression: Gizmo setting reverted after tool switching\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0 Alpha\nWorked: Blender 2.93\n\nOne of the tool settings of the Extrude Tool is by default on \"Normal\". If changed to \"XYZ\" and then switching between a different tool, it will revert back to Normal.\n\n- Go into edit mode\n- Make the Extrude Tool in the toolbar active\n- Switch the tool setting to XYZ\n- Make another tool active and \n- Then switch back to the extrude tool" ]

[ "Blander crash without ray shadows Nvidia GTX 950M CUDA\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nWhen turn off ray shadow visiblity render becomes slow and the blender crashes.\n[2019-10-28_03-53-23.mp4](2019-10-28_03-53-23.mp4)\n\n------------\nI tested again on GTX 750 Ti and 2.92.0 Alpha. If I turn shadows off first, then switch to rendered view, it gives bad render:\n\nIt disappears when you do something. Typical when there's something wrong in Cycles. I need to restart Blender to be able to render again.\nWhen I turn rendered view first, then turn shadows off, it sometimes crashes.\nThis is all Cuda. Optix renders nothing at all. I presume Optix doesn't do volumes yet.\nAlso noticed that deleting sun lamp and leaving only area lamps fixed the issue.\n\n**Steps to reproduce**\n[облака в стекле.blend](облака_в_стекле.blend)\n- Open file\n- Disable shadow ray invisibility on object\n- Switch to rendered shading\n", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "VSE: Cycles displayed as Rendered in Scene strip makes Blender hang - and other Scene strip bugs\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nThe Render modes of Scene Strips are either missing or broken:\n- When Cycles is set as render and Rendered set as display, it'll make Blender hang.\n- Wireframe and Rendered doesn't work with any Render. \n- The only thing working is Eevee with either solid or Material Preview. \n- Workbench and Cycles settings seems to just use the Eevee render, since these are producing the same results in Solid and Material Preview.\n\n{[F10177251](scenestrip.gif),size=full}\n\nTest file:\nCycles is set up as render in the 3D Footage scene. In the Master Edit scene, switch display mode to Rendered. Blender will hang.\nTry the various other display modes and renders(by changing the render in the 3D Footage scene), to see wireframe and rendered doesn't work with any render. \n[multicam_3d_c.blend](multicam_3d_c.blend)\n\n\n", "Switching object with alt+click do not fade inactive objects\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nExpected: same fading as with direct entering to sculpt/edit or as with newer switch operator.\n\n[2021-03-09_16-33-47.mp4](2021-03-09_16-33-47.mp4)", "Set Active UV - new node\n\n\n---\n\nSee also: #98851 (Active UV - new node)", "Dither affects 'File Output' image even when \"save as render\" is disabled \nThe dither option in the Post Processing tab affects images saved through the file output node in the compositioner even when \"save as render\" is disabled, when disabled it should not touch the output image, when \"save as render\" is enabled it makes sense to dither.\n\n\nnoise in output file\n\n\n- Open attached file\n- Optionally change the Dither in {nav Output Properties > Post Processing}\n- hit render\nIt will generate an image in the directory pointed to by the node `File Output`.\nNote that Dither also affects this image.\nMaybe the fileoutput node needs his own dither value, it really is bad when generating raw pixel data.\n\n[gradient.blend](gradient.blend)", "Checking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.80, 2.83.8, 2.92.0 Alpha c271600101, \nWorked: 2.79b\n[T82260_2.79_Sample.blend](T82260_2.79_Sample.blend)\n\nChecking the Vector Blur pass checkbox causes the most recently emitted particles to not be rendered. This issue is visible when using a fast moving emitter.\nRendering on the GPU or CPU doesn't seem to make a difference, the issue still occurs.\n\n - Open the attached .blend\n\n[T82260_2.92.0_Alpha_Sample.blend](T82260_2.92.0_Alpha_Sample.blend)\n - F12 to render.\n - Click on the Vector Blur pass checkbox.\n - F12 to render.\n - Compare the 2 render results.\nVector Pass unchecked\n\n\nVector Pass checked.\n\n\n[Desktop 2020.10.30 - 21.14.11.01.mp4](Desktop_2020.10.30_-_21.14.11.01.mp4)\n\n\n\n\n", "Geometry Nodes: Simulation and Repeat nodes is work though they are muted\nBroken: version: 4.0.0 Alpha\nWorked: Never.\n\n\n\n1. Geometry Nodes tree:\n a. Add Simulations nodes.\n b. Mute both.\n2. Play animation.\n\n", "Alpha channel of Textures can't be deactivated in UV Editor\nOperating system: Windows10\nGraphics card:Geforce GTX 970M\n\nBroken: 2.91.0\nWorked: 2.83.0\n\nWhen you load an Image/Texture with an alpha channel in the UV editor, you can't turn the alpha channel off anymore, the image will stay black.\nIt worked in older Versions from 2.80 up to 2.83, there you only have to click on **Color** in **Display Channel** options.\n\nOnly areas that aren't black in the Alphachannel will be visible, in my examples I work with textures that need an all black Alpha channel.\n\njust load any Texture with Alpha channel in UV editor viewport\n\n\n\nHere an Screenshot from Blender 2.83.0 where it worked\n\n\n\n\nand here an screenshot of Blender 2.91.0, the same Texture is used, I also tried different settings under Image, but nothing works\n\n\n", "project turning purple automatically after closing and opening later+zoom in/out buttons not working properly.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce MX330/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.79\n\nBroken: version: 3.6.2\n\n\n\n", "Blender 2.80 Canceling of visibility actions during opened panel with object default parameters.\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560\n\n2.80 beta, 1df6a98b176f, blender2.8, 2019-03-05\n\n**Error description**\nLooks like a small flaw. Panel with default parameters(radius, etc..) of standard objects if objects just created - will be canceling your actions with outliner panel (visibility actions) if you dont close it and continue changing parametrs after that\nDemo: 0876b975cd74ce4d9400b6556e5cbe14.mp4\n\n**Steps to reproduce**\n\n- Open new general template\n- Add mesh - circle\n- Hide cube in outliner\n- In Adjust Last Operation panel change radius\n\nCube is no longer hidden", "Node link drag search in shader editor doesn't filter by render engine compatibility\nOperating system: macOS-11.6.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-16.5.7\n\nBroken: version: 3.2.0 Alpha\nWorked: I don't think ever. The feature was introduced in 3.1: 11be151d58\n\nOther than the default node search menu ( {nav Add > Search...} ) the link drag search doesn't filter out nodes that are not compatible with the current render engine.\n\n[node-link-drag-search-bug.mp4](node-link-drag-search-bug.mp4)\n\nAs shown in the video:\n- open the default blend scene with factory settings\n- switch to the shader editor\n- add a *Value* or *RGB* node\n- drag from the node's output and release the link on the canvas to activate the link drag search\n- look for the \"Toon BSDF\"\nResult: inputs from the node appear in the search despite the node not being supported by Eevee.\n\nHere's the simple setup from the video.\n[node-drag-link-search-bug.blend](node-drag-link-search-bug.blend)\n\n", "Themes→3dViewport→Active vertex color do nothing\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.5.0\n\nThis one influence nothing. Should it be deleted?\n\n\n[2023-04-13_07-48-03.mp4](attachment)\n\n\np.s. Dull colors and other issues about wireframe [described here](426) and I am sad, that it looks abandoned and ignored…\n\n", "shadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1 Release Candidate\n\nshadow catcher data missing from diffuse passes when transparency is disabled, and shadow catcher object is masking environment when transparency is enabled (can't recombine moving scene envronment). This makes it impossible to rebuild the image unless the shadow catcher pass is used, which is not suitable when using vector motion blur.\n\nOpen below blend file (choose to load ui)\ngo to scene 'no transparency'\nin the compositor press f12 to render a frame\ncompare the combined image and the rebuilt image\n\ngo to the second scene 'transparency'\nin the compositor hit f12 to render again\nthis time the environment is masked out by the shadow catcher, making it impossible to use the rendered environment (which is necessary if the camera is animated)\n\nrequired behaviour - \n\nshadows appear in diffuse passes when transparency is disabled, so the rebuilt image matches the viewport.\n\nshadow catcher object doesn't mask out the environment pass when transparency is enabled (so the environment can be added back to the image when the camera is moving (backplate cant be used here))\n\n\n\nThe only possible solution currently is to always render with transparency enabled, and then render your scene a second time with only the environment visible, which causes issues when rendering via scripts.\n\n", "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty." ]

[ "Some Cycles nodes are active when muted (RGB To BW, Math, vector Math, Separate RGB)\nWin10 64bit\n\nBroken: 2.79\n\nRGB To BW node is active when muted\n\nOpen file and render\n[RGB_BW.blend](RGB_BW.blend)\n\n", "Vector Math node does not mute properly in Cycles\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.91.0 Alpha\nWorked: Unknown, broken in 2.83.4 at the very least.\n\nSome modes of the Vector Math node do not mute properly in Cycles. Specifically, the Dot Product, Distance, and Length modes are the ones affected. These modes all output greyscale values with the grey handle rather than vectors with the blue one. When muted, The red pass-through line indicates that the node should output the first input vector untouched, but instead it outputs a greyscale value. It appears to be the same greyscale pattern regardless of which mode was used. It does appear to be working properly in EEVEE. The problem is present in CPU, CUDA, and Optix modes, both in the viewport and in actual renders. It is present in 2.83.4 which is the oldest version I currently have access to.\n\nUse the Vector Math node on the Dot Product, Distance, or Length mode. Compare it unmuted, muted, and disconnected. \nI've attaching a simple demo file, along with a image showing everything needed to reproduce the problem.\n\nI only used the Dot Product mode in the examples, but it also works with the Distance and Length modes.\n\n[Vector node bug - isolated.blend](Vector_node_bug_-_isolated.blend)\n" ]

[ "Hair Dynamics: cannot generate a valid particle cache\nOperating system: 4.20.12-gentoo Linux\nGraphics card: Radeon(TM) Pro WX9100 (VEGA10, DRM 3.27.0, 4.20.12-gentoo, LLVM 6.0.1)\n\nBroken: 2.80 (sub 48) commit hash: bf9904ec8018 Build: 2019-03-13 01:14:16 Linux Release branch: blender2.7\n\nWorked: (optional) 2.79b commit hash and date unknown; compiled from Gentoo repository\n\nFails to make a valid particle cache when rendering a dynamic hair system via Cntl + F12. Hair particle motion appears compromised after the first frame. see video clip **dyn_on.mkv**.\n\n**Require**\nA .blend file with a mesh object that has a hair particle system defined on it. Hair dynamics is turned on in the particle system properties panel. The file should have been previously saved without a cache. Blend file **dyn_on.blend** provided for this requirement. \n\n1. Open **dyn_on.blend**\n2. Cntl + F12 to render animation (implicitly build in-memory cache)\n3. Observe:\n```\n a. Cache indicator on timeline shows only 1 or 2 valid initial frames; remaining 248 - 249 frames are invalid.\n b. Hair particles exhibit only limited rotational dynamics. They do not follow the surface of the sphere (i.e., they appear \"unanchored\"), nor do they seem affected by gravity. See **dyn_on.mkv** video clip.\n c. After the last frame has been rendered, click on the rewind control in the timeline. The cache section in the Particles properties reports the state of the cache: \"1 frames in memory (216 KB), not exact since frame 0\"\n```\n\n**Workaround**\n1. Bake particle dynamics first or\n2. Run the animation through in the 3D viewport to create an in-memory or on disk cache before rendering.\n\nRendering with an in-memory, on-disk, or with baked dynamics appears to generate an unaffected animation. See **dyn_on_cache.mkv** video clip.\n\n**Notes:**\n1. Examples rendered in Cycles, but EEVEE and Workbench rendering does not change behavior.\n2. Hair particles rendered with a collection of simple mesh geometry in the examples, but rendering with single mesh objects or rendering hair paths does not change behavior.\n3. Running in single thread mode (-t 1 on command line) does not change behavior.\n4. Rendering via CPU or GPU does not change behavior.\n5. Problem seems specific to hair particle systems. Emitter particle systems without pre-computed caches can be rendered with Cntl + F12; the cache seems fully valid in the time line, dynamics of falling emitter particles do not seem unusual and the cache section in the Particles properties reports that there are 250 valid frames in memory at the conclusion of the animation.\n\n**Related:**\n#62439 describes a failure in particle updates which seems very similar in appearance exhibited by particles in video clip **dyn_on.mkv.**\n\n[dyn_on_cache.mkv](dyn_on_cache.mkv) - dyn_on_cache.mkv\n[dyn_on.mkv](dyn_on.mkv) - dyn_on.mkv\n[dyn_on.blend](dyn_on.blend) - dyn_on.blend\n", "Cycles rendering world origin extremely slow when using hair particle system with density maps (no, really!)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.1\nTested in 2.93.1, 2.90 on CPU and Nvidia GPU.\n\nCycles is rendering the world origin extremely slowly, even if there is nothing at all in view.\nSeems to be caused by Hair particle system using a texture influencing density.\n\nWatch this video for me walking through the bug:\nwatch?v=3DdTrC-qN2M\n\n[particle_render_slow.blend](particle_render_slow.blend)\nRender image\n\n", "Particle Edit Breaks After Selecting a Mesh with Cloth Physics\nOperating system: macOS 10.13.6\nGraphics card: NVIDIA GeForce GT 650M 1024 MB\n\nBroken: at least 2.82 up to 2.92 experimental (I suspect it never worked since 2.80)\nWorked: 2.79\n\nParticle edit behaves like object edit mode, but the UI shows \"Particle Edit\" being active.\n- There is no circle typical for the comb tool around the mouse cursor.\n- No additional key points to select or black hair strands are rendered.\n- Instead of e.g. combing you will move the object around once you drag with the mouse.\nBasically everything except for the UI stays in \"Object Mode\".\n\nEffect On (broken):\n\n\nEffect Off (works as expected):\n\n\nBased on the default startup:\n1. Go to \"Particle Properties\"\n2. Add a particle system\n3. Set its type to \"Hair\"\n4. Add a second particle system\n5. Set its type to \"Hair\" too\n6. Add a new mesh e.g. \"Plane\"\n7. Go to \"Physics Properties\"\n8. Add \"Cloth\" physics\n9. Select the original \"Cube\" again\n10. Switch mode to \"Particle Edit\"\n\nWays to reverse the effect (make \"Particle Edit\" work properly again):\n- Either: Make a new file and append both objects of the old file\n- Or: Delete one of the particle systems on the \"Cube\" and undo the operation\n\nEven after reversing it you can restore the effect by selecting the \"Plane\" once.\nAt least two particle systems are required for the effect.\n\nThe effect can even be saved and stays the same after loading from the file again.\nThus I was able to create two files one with the effect and one without.\nThe file without the effect is a little bigger in size.\n\n[EffectOn.blend](EffectOn.blend)\n\n[EffectOff.blend](EffectOff.blend)\n\nIt took me a whole day to find the cause and boil it down so far.\nHope it helps and that it can be fixed with the provided info.", "Viewport Render crashes on macOS 12.3\nOperating system: macOS-12.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Beta\n\n\nUpdated MacOS to 12.3 (Beta) and going to Viewport Render will cause a full Mac freeze then crash. A hard reboot is the only resolution.\n\nNot sure if this is caused from the latest version of MacOS (12.3 Beta) or if it's the latest version of Blender (3.1Beta). \nI haven't tried with the latest Blender 3.1 Beta build with Monterey 12.2 Beta as this would require me to wipe the computer and reload all apps and files in the OS downgrade process.\n\nOpen default scene and toggle the Viewport Render button.\n\n", "Instanced wire objects are hidden in solid mode instead wire appearance\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\n\nIf I instance wireframe (only edges) object with GN, I don`t see instances in Solid mode (except 1st).\nWireframe mode is okay.\n\n[GN Stack wire.blend](GN_Stack_wire.blend)\n[2021-03-19_12-47-47.mp4](2021-03-19_12-47-47.mp4)\n\n**Edit:** also can be reproduced without geometry nodes:\n[2021-04-28 13-23-38.mp4](2021-04-28_13-23-38.mp4)\n\n- Open attached file\n- Switch between Solid and Wireframe View\n[missing_wires.blend](missing_wires.blend)", "Hair particle system duplicates objects on some faces and don't fill the rest\nOperating system: Ubuntu 19.04\nGraphics card: AMD Radeon RX580\n\nBroken: (2.81 release compiled from source)\nWorked: (optional)\n\nEven with even distribution enabled, 1 particle per face and a low count of particles to spawn, the particle system put two particles on the same face but with different sizes.\n\n1) Create a cylinder with 32 vertices.\n2) Create a small (scale 0.05) cylinder to use as a reder for particle.\n3) Delete the top and bottom faces of the small cylinder so it becomes like an empty tube.\n4) Enable particle system hair on first cylinder and, choose 30 as number, 1 per face source and disable random order, select as render object the small cylinder, the scale 1.0 and choose to randomize the scale a few (0.5 is ok).\n5) Play with the number of particles and the seed and more than sometimes you will notice two or more small cylinders rendered on the same place overlaping (specially on the top and bottom faces).\n\nWhat I expect:\nIf you count the number of faces of the cylinder (added with default parameters) it will have near 30. If I choose \"even distribution\" of particles and \"1 for each face\" without random, what I expect is that all the faces of the cylinder have at least 1 particle, no more, no less.\nIf there are 30 faces and if I limit the number of particles to exactly 30, there must be exactly one particle for each face.\nWhat happens actualy is that there are 4 particles lying around on the top and bottom faces and I don't know why. And there are no particles on some other faces. And sometimes two spawns on the same place on the bottom or top face of the cylinder.\n\nWith complex meshes it makes a mess, specially if I need to paint the weight to affect density. In that case there are more particles on some places and there are no particles on places with a high value of weight. \n", "Textures not displayed in sculpt mode due to missing UVs (PBVH rendering, Multires)\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\n\nBroken: version: 2.80 (sub 55)\nWorked: 2.79b\n\n\nModel with Multiresolution modifier doesn't display texture in Sculpt Mode.\nRender engine doesn't matter.\n\n \n\n\nObserved in display modes:\n1. Solid (Lighting: Studio / Color: Texture)\n2. LookDev\n3. Rendered (in Cycles mesh is invisible)\n\n- Open [test.blend](test.blend)\n- Enable \"Display modifier in viewport.\"\n\nOR\n\n- Switch to LookDev mode\n- Apply multiresolution modifier to a mesh with texture\n- Add single subdivision (`Sculpt Base Mesh` OFF)\n", "Hair particles rendered as an object do not follow parent object when the parent object is falling under gravity as a rigid body when animating\nOperating system: Microsoft Windows 10 Home, Version 10.0.18362 Build 18362\nGraphics card: GeForce GTX 1080\n\nversion: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4caf4, type: Release\nbuild date: 2020-03-12, 15:41:08\nplatform: Windows\n\nI have an issue where i have a cube mesh, I create hair particles, and set the hair to render as an object, say a cylinder. I then enable rigid body physics for the cube. I also have a passive plane below the cube. When I run an animation, the cube falls as if under gravity and stops at the plane, but the cylinder particles remain in their original position?\n\nIf I add soft body physics to the cube and order the soft body physics before the particle settings, then the cylinders fall, but lag behind the cube. The cube falls through the plane below, but the cylinders are stopped by the plane?\n\nWith soft body added (to top of stack). Particles do fall but have a lower acceleration rate, and the cube no longer detects the floor and passes through the plane?!\n\nThanks!!\n\nSee attached blend file [StackExchangeParticleProblem-001.blend](StackExchangeParticleProblem-001.blend)", "SpaceView3D.draw_handler_add with PRE_VIEW draw type does not result in visible draws\nOperating system: MacOS 11.6.3, Ubuntu 18.04 LTS (issue exists in both)\nGraphics card: Intel UHD 630, Nvidia Quadro RTX 400 (issue exists in both)\n\nBroken: 2.93 LTS, latest master (b626edd751d64b269da12ef8e774ced2836c3c9e)\nBroken: 2.83.0\nWorked: 2.82\n\nBroke between good 189e96ba68 and bad d95e9c7cf8\n\n1. Startup Blender\n2. Go to scripting tab and create a new script\n3. Copy \"Triangle with custom shader\" code from: gpu.html\n4. Change draw_type param in draw_handler_add from\n```\n'POST_VIEW'\n```\nto\n\n```\n'PRE_VIEW'\n```\n5. Run script.\n\nExpected behavior:\nThe drawn triangle is visible.\n\nActual behavior:\nThe drawn triangle is not visible.\n", "Regression: Rendering hair instances size in animation bug with animated emitter object scale\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.2\nBroken: 2.93\nWorked: 2.92\n\nRegression from 50782df425.\n\nIncorrect rendered instanced object scale if rendering hair animation with animated object.\n\n1 Create Cube and object for instancing\n2 Set cube scale animation for some frame range\n3 Apply patricle system to cube (hair / rendered instances as object or collection)\n4 Try to render single frame and render animation, compare difference\n\n[hair_render.mp4](hair_render.mp4)\n[test_hair.blend](test_hair.blend)\n\nWill set to high prio to raise awareness this is a regression, but this can probably be lowered again since also involves the EOL particle system.\nNote: if you really need to render this, consider using Cycles (where this still works when the `Persistent Data` option is OFF.", "Particle Edit mode for non hair particles - Not working\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\nWorked: can not find one\n\n\nCan not edit a baked particle simulation's particle paths in Particle Edit mode\n\n\n- Delete all object from the original scene\n- Create a plane\n- Add a particle system. For the sake of testing with 20 particles,\n- Bake the simulation (not in disk)\n- Switch to Particle Edit mode\n- Select Point select mode\n\n- > There is no particle path in the view-port to be edited.[path not showing in particule edit .blend](path_not_showing_in_particule_edit_.blend)\n", "Clay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop) \nOperating system:\n\nDevice name\tDESKTOP-V97J8T0\nProcessor\t12th Gen Intel(R) Core(TM) i7-12700F 2.10 GHz\nInstalled RAM\t32.0 GB (31.8 GB usable)\nSystem type\t64-bit operating system, x64-based processor\nPen and touch\tPen support\n\nGraphics card:\n\n3070 RTX\n\nBroken: 3.3.1\nWorked: 3.2.2 \n\n\nClay Strip brush sensitivity BUG/Problem that appears only in Blender (works fine in ZBrush and Photoshop). it works fine in blender when i push Wacom Intous tablet on max with pen\n\nVideo Link: 1J_NZ0-1Qqg", "cycles stalls with hair particles in viewport\nOperating system: Windows 10 home version 21H1 OSBUILD 19043.1415\nGraphics card: no card\n\nBroken: 3.0.0\nWorked: prior to 3.0.0\n\n\n[CUBE HAIR packed.blend](CUBE_HAIR_packed.blend)\n\ncycles stalls in viewport with hair particles, final render does not work\n\n\n1. Change the render engine to Cycles\n2. Create the material shown below (The parameter surrounded in red have been modified on the Principled BSDF)\n\n3. Give the material created above to a mesh object.\n4. On that same mesh object, add a hair particle system.\n5. Enter the rendered viewport. And take note of the slow rendertimes.\n6. \"Restart\" the render by doing something like **one** of these steps:\n - Move, scale, or rotate an object\n - Click on a material in the 'Material Properties' tab of the `Properties editor`\n - Adjust a material property in the world material or the object material\n - And probably others\n7. Notice the viewport render is now much faster.\n\n> Original Steps to reproduce\n> click display render preview in viewport, observe cycles stalling, then click on 'material' in layout panel, now observe cycles picking up and running at fast pace, then try final render, observe that it does not proceed", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up.", "Regression: Vertex colors are now broken in hair strands\nOperating system: Gentoo Linux kernel 5.18.0-gentoo\nGraphics card: RX 480\n\nBroken: 3.2.0, 3.3.0\nWorked: 3.1.0\n\nCaused by b9799dfb8a\n\n\nVertex colors are strange and patchy when moving from 3.1.0 to 3.2.0 or later: \n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Make something with vertex colours and a hair system which utilises them in Blender 3.1.0. In my instance I used geometry nodes to generate them; this may differ when making them manually as one of my other projects which does it manually does not seem to exhibit this issue. \n2. Open file in Blender 3.2.0. \n\nI created the following .blend file to demonstrate the issue: [Color_test_3s.blend](Color_test_3s.blend)" ]

[ "Hair Particles don't show in Viewport on macOS 10.13.6\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD 6970M OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.2.0\nWorked: Blender 3.0.0\n\nWhen you create a Particles System and select Hair, the hair particles don't show in Viewport on macOS 10.13.6, only it is showed a single hair, independently of the total number of particles but if you change to Particle Edit Mode the particles are showed.\n\nThe issue appears in Object Mode > Solid Shade,\n\nRest of Modes > X-Ray, Wireframe, Material Preview and Redered (Eevee & Cycles) work fine.\n\n\n1. Open the default startup file.\n2. Select the Cube and create a Particle System.\n3. Change the Particle System to Hair.\n4. A single hair is showed in viewport in Object Mode (and viewport shading: solid), if you change to Particle Edit Mode the hair particles are showed.\n\n\n\n" ]

[ "viewport problem\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23\n\nBroken: version: 4.0.0 Alpha\n\nwhen I move inside the viewport, some objects become hidden.\n\n", "Viewport not updated after changing material properties\nWindows 10\nGraphics card:\nGTX 1660TI\n\n\nBroken: version: 3.2.0 Beta\nWorked 3.0\n\nHello. If you create an object, for example, a sphere, assign it a material with a base color, for example, red or something else, then copy the material, create another object, create a material for it, and then paste the material on the new object, the material that was copied will be inserted, but if after that you start changing it it will not change on the object until it is reselected.\nWhy don't its settings change immediately after changing them in the settings? Is this a bug or is it supposed to be like this?\n\nI copied the material from the sphere to the cylinder, it was added to it, after that I replaced the base color on it with green but it does not change on the cylinder.\n\n**Steps to reproduce**\n[#98458.blend](T98458.blend)\n\n- Open file\n- Copy material from selected (green) cube\n- Paste material to other cube\n- Change Base Color in pasted material\n\nColor is not updated in viewport.", "Texture on active object is not visible in solid view with sculpt mode activated\nOperating system: Windows 10, Ubuntu 16.04\nGraphics card: GeForce GTX 760\n\nBroken: 2.80\n\nTexture is not visible in solid view with sculpt mode activated\n\nCreate a texture, apply it to an object, like start cube, make sure you're in solid view mode with textured color active, you'll see the texture in object mode. After switching to sculpt mode, object becomes gray.\nIf you change view mode to LookDev or Material, everything is fine.\n\n**Extra info**\nIf you go back to Solid view and add a Shape Key, texture is visible again, but mask brush doesn't work. The problem with mask brush and shape keys is already mentioned #67303\nI made a video about those problems Mk2w41C87AI", "Hair particles won't follow instaced position under 2 level nested collections.\nOperating system: Linux-5.11.0-7620-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 2.93.3\n\nHappens when you have an object with hair as instanced collection (A) inside another collection (B). Then, when you instance (B) the hair particle from (A) will not follow the relative position correctly.\n\n\n- Open .blend file\n- Select \"Cube\"\n- Object -> Quick Effects -> Quick Fur\n- {key Shift A} -> Collection Instance -> Collection\n- Move the instanced collection little away\n- {key M} -> New Collection -> Ok\n- {key Shift A} -> Collection Instance -> Collection 2\n- Move the instanced Collection 2 little away\n- You will notice the hair particle with a wrong position in relation to the original emitter Cube.\n\n1 min video here:\n[bugOrFeature.mp4](bugOrFeature.mp4)\n\nblend 2.93 here:\n[#91008.blend](T91008.blend)\n\n---\n\nNote that the concept works under 2.7 using Instaced Groups:\n\nblend 2.7 here:\n[ConceptWorks_b27.blend](ConceptWorks_b27.blend)\n", "Particle bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nHair particles in particle edit mode cannot add new particles if emit is set to vertices. When you try to change emit to faces - all previously created particles disappear.\n\n\n[test.blend](test.blend)\n", "NaN in object matrix of instanced objects\nRyzen 7 3800x\n31.9 GB Ram\nOperating system: Windows 10\nGraphics card: Nvidia 2060 6GB Ram\n\nI tested the same scene out on my other box and the problem happened. Both machines are running RTX 2060s. One is a Intel box and the other AMD.\n\n**Blender Version** 2.81 and 2.82a\nWorked: Nothing has worked\n\n**Error**\nYouTube link to render glitches: e1ScHjBANLk\n\nWhenever I start a render, around frame 58 the sun shadows just disappear.\nIf I close the scene and open it back up and render the frame where the shadows disappear, it will render fine. But after about 50 or so frames the shadows disappear again. \nIt works fine in viewport. \n\n**note**\nI deleted the volume light box with just a 1000 floating sprite boxes for the dust inside the garage. After that, the issue went away all together. I then added the volume box back and the problem happened again. It must have something to do with volume lighting. The grass outside is over 12k clones using a particle hair so it has something to do with volume lighting and particles inside a object. \n\n**Files**\n[Blender_Bug.zip](Blender_Bug.zip)\nIt was 12 GB, removed extra elements and brought it down to this.\nAround frame 60 if you render the animation 1-300 the shadow will disappear. Escape the render… The viewport will continue to display the shadow. But after the shadow disappears during the render, and without closing and reopening Blender, whenever you render that frame, the shadow “sun light” is absent. \n\n\n\n\n", "Hair particles: 'Use modifier Stack' option removes all hair if particles have been added or removed in particle editmode\nOperating system: Linux-3.10.0-957.10.1.el7.x86_64-x86_64-with-centos-7.6.1810-Core 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 4)\n\nUse modifier stack checkbox deletes all the hair particles if they were created with the add hair brush and combed (not necessary), even if there are no modifiers before the particle system. This also happens if particles have been deleted (X) in particle editmode.\nAnd there is no way to get those hairs back. It can really destroy all your work on grooming.\nBy the way, that check box becomes inactive in 2.79 after grooming, but it's active for some reason.\n\nCreate a hair particle system.\nGo into particle edit mode.\nDelete all the hairs (by the way, you won't be able to do that until you comb it, may be a second bug).\nAdd some hairs via add hair brush (you can add hair without deleting on the previous step, the bug will occur anyway).\nGo back to object mode.\nCheck the use modifier stack checkbox.\nAll the hairs disappear!\n\nThe attached file has all that done except the very last step.\n\n[hair_use_modifier_stack_bug.blend](hair_use_modifier_stack_bug.blend)", "Hair Dynamics: cannot generate a valid particle cache\nOperating system: 4.20.12-gentoo Linux\nGraphics card: Radeon(TM) Pro WX9100 (VEGA10, DRM 3.27.0, 4.20.12-gentoo, LLVM 6.0.1)\n\nBroken: 2.80 (sub 48) commit hash: bf9904ec8018 Build: 2019-03-13 01:14:16 Linux Release branch: blender2.7\n\nWorked: (optional) 2.79b commit hash and date unknown; compiled from Gentoo repository\n\nFails to make a valid particle cache when rendering a dynamic hair system via Cntl + F12. Hair particle motion appears compromised after the first frame. see video clip **dyn_on.mkv**.\n\n**Require**\nA .blend file with a mesh object that has a hair particle system defined on it. Hair dynamics is turned on in the particle system properties panel. The file should have been previously saved without a cache. Blend file **dyn_on.blend** provided for this requirement. \n\n1. Open **dyn_on.blend**\n2. Cntl + F12 to render animation (implicitly build in-memory cache)\n3. Observe:\n```\n a. Cache indicator on timeline shows only 1 or 2 valid initial frames; remaining 248 - 249 frames are invalid.\n b. Hair particles exhibit only limited rotational dynamics. They do not follow the surface of the sphere (i.e., they appear \"unanchored\"), nor do they seem affected by gravity. See **dyn_on.mkv** video clip.\n c. After the last frame has been rendered, click on the rewind control in the timeline. The cache section in the Particles properties reports the state of the cache: \"1 frames in memory (216 KB), not exact since frame 0\"\n```\n\n**Workaround**\n1. Bake particle dynamics first or\n2. Run the animation through in the 3D viewport to create an in-memory or on disk cache before rendering.\n\nRendering with an in-memory, on-disk, or with baked dynamics appears to generate an unaffected animation. See **dyn_on_cache.mkv** video clip.\n\n**Notes:**\n1. Examples rendered in Cycles, but EEVEE and Workbench rendering does not change behavior.\n2. Hair particles rendered with a collection of simple mesh geometry in the examples, but rendering with single mesh objects or rendering hair paths does not change behavior.\n3. Running in single thread mode (-t 1 on command line) does not change behavior.\n4. Rendering via CPU or GPU does not change behavior.\n5. Problem seems specific to hair particle systems. Emitter particle systems without pre-computed caches can be rendered with Cntl + F12; the cache seems fully valid in the time line, dynamics of falling emitter particles do not seem unusual and the cache section in the Particles properties reports that there are 250 valid frames in memory at the conclusion of the animation.\n\n**Related:**\n#62439 describes a failure in particle updates which seems very similar in appearance exhibited by particles in video clip **dyn_on.mkv.**\n\n[dyn_on_cache.mkv](dyn_on_cache.mkv) - dyn_on_cache.mkv\n[dyn_on.mkv](dyn_on.mkv) - dyn_on.mkv\n[dyn_on.blend](dyn_on.blend) - dyn_on.blend\n", "Cycles rendering artifacts with fluid particles + Vector pass (missing particles)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nSections of fluid particles are missing when rendering in cycles.\nThe issue occurs when you enable the vector render pass.\nThere are no issues when rendering in the viewport, only during the final render.\nThe parts that are missing changes every frame.\nIt also happened on the same computer with a different graphics card (RTX 2060). \n\nViewport render\n\ncycles render\n\nrendered only the particles\n\n\n- Open attached file\n- Bake fluid simulation data and particles\n- In {nav View Layer Properties > Passes > Data} enable `Vector`\n- Render scene\n\n[FluidSplash2.blend](FluidSplash2.blend)\n\n", "MacOS, Metal: Banding artefacts in viewport when using curves in color management\nOperating system: macOS-13.2.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro Vega 64 1.2\nScreen: iMac 27 inch Retina 30bit\n\nBroken: version: 3.5.0\nWorked: same version with openGL viewport API\n\nIn the \"wanderer\" demo file you get white lines in the bright parts of the scene. They are visible in rendered view as well as in the final render (but only inside blender). \nWhen \"Use Curves\" in \"Color Management\" is turned off, they dissapear. \nWhen switching back to openGL api everything looks ok.\n\nOpen the demo file wanderer wanderer.blend\n\n", "Hair particles: cannot delete hair particles in particle edit mode until you comb it\nOperating system: Linux-3.10.0-957.10.1.el7.x86_64-x86_64-with-centos-7.6.1810-Core 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.81 (sub 4)\nWorked: 2.79\n\nYou cannot delete all (hit a) hair particles until you comb them. Even more, if you select one hair or several and hit delete, they disappear, but if you then select all the rest and hit delete, all the particles deleted come back.\n\n\n- Open this blend file: [#69487-hair-delete-279.blend](T69487-hair-delete-279.blend)\n- Press {key X} and choose Particles\n\nIn current Blender (2.82 alpha @ 756b9acaf5) hairs get deselected but are not deleted. In 2.79b the hairs are deleted.\n\n**Original steps to reproduce:**\n\nCreate a new hair particle system\nGo into particle edit mode\nSelect all, hit X delete particles -> nothing happens\nDeselect all\nSelect a couple, hit X -> the selected hairs will disappear\nSelect all, hit X -> all the hairs come back visible again\n\nThere's a hair particle system newly created in the attached file.\n[hair_particles_delete_bug.blend](hair_particles_delete_bug.blend)", "overlays extras option being ignored\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Beta\nWorked: (unsure, definitely 2.8 possibly 3.0)\n\nbounding box representation of particle instanced geometry (hair) where the object being instanced is set to bounding box is not being hidden from the viewport when the 'extras' option is checked. \n\n\n", "Hair with negative clumping floats above emitter\nOperating system: Linux\nGraphics card: RTX2060\n\nBroken: 2.93.0 beta\nWorked: ?\n\nParticle_System Hair with a negative Clumping value \"floats\" above the emitting surface. Positive Clumping values remain anchored on emitter.\n\nsee attached .blend file. Further details in text-block \"notes\".[test028_grassNegClump.blend](test028_grassNegClump.blend)\n\n[system-info.txt](system-info.txt)\n\n", "Mask invisible on object with modifiers when entering sculpt mode\nOperating system: Linux-5.4.0-81-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: unkown\n\nWhen selecting a previously unselected object with a modifier and a sculpt mask, the mask is invisible at first when entering sculpt mode.\nPainting the mask reveals it.\n\n- Create an object with a modifier (e.g. mirror or array) and paint a sculpt mask on it. Or use the file attached.\n- Outside the sculpt mode first make sure the object is unselected, then select it and enter sculpt mode.\n- The object appears with no mask visible, still you can not sculpt the masked parts.\n- Painting the mask reveals it.\n\n[mask.blend](mask.blend)\n\n[mask.mp4](mask.mp4)", "Viewport and final render differs in lighting/materials\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.40\n\nBroken: version: 3.6.0\n\nSimple scene, only one sun light and HDRI lighting. Shows different result in viewport render and final render.\n\nJust compare viewport and final render and see the difference in specular highlight of the sun on the main (green) material.\nAlso, I don't know if this is important, I use Agx color transform in Blender, not Filmic or Standard.\n\n" ]

[ "It doesn't show Particle Hair in solid mode from a file ver3.0\n**System Information**MacOS Montrey\nOperating system:MacOS Monterey 12.0\nGraphics card:Radeon Pro 560 4GB\n\nBroken: 3.2 and 3.1 stable\nWorked:3.0 stable\n\nBlender 3.2 and 3.1 doesn't show Particle Hair in solid mode from a file ver3.0.\nBut it shows in wireframe and render mode.\n" ]

[ "Workbench: Cull before batch creation during viewport animation rendering\n\n## Current Situation\n\nWhen drawing an object (eg sending draw calls to the GPU) the object boundary sphere is tested against the active view). When the test fails the object isn't send to the GPU. Before this happens the GPUBatches were already generated.\n\nWhen doing animation playback this could lead to the situation that the GPU Batches are calculated, but not used.\n\n## Target Situation\n\nWhen using the Overlay engine/Workbench engine we could test the objects to the default view (e.g viewport). When this fails we could skip this object at all. This feature would be disabled when the shadows are turned on and only enabled when doing an image/animation render.\n\nA consistent framerate is more important to animators then having some frames faster.\n", "Menu Hotkey do not work in Batch Rename Dialogue\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.1\n\nIn the Batch Rename Dialogue there the \"Type\" drop down. In this drop down pressing the underlined characters does not work like in other drop downs and menus.\n\n\n1. Select one or multiple objects\n2. Hit Ctrl + F2 for \"Batch Rename\"\n3. The \"Type\" drop down is set to \"Find/Replace\" by default\n4. Click the \"Type\" Drop Down to open it\n5. press \"S\" \n6. Nothing happens even though the drop down should now be set to \"Set name\" as indicated by the underlined \"S\".\n", "Transfer Mode Operator Do To's\nNOTE: This task should be split up into multiple tasks soon.\n\nThis task is concerned about loose ends for a full working implementation of the \"Transfer Mode\" operator.\n\n---\n\n- [ ] Add the operator to a menu in every mode\n\nRight now this would always be the first menu to the right of \"View\" and \"Select\". \nLike \"Paint\", \"Weights\", \"Grease Pencil\", \"Draw\", etc. Some modes would need a new menu added for this.\n\n- [ ] Add the flash overlay for grease pencil objects\n\nArmature and curve objects are also missing the overlay but there it's less needed since other overlays are already a good indicator.\n\n- [ ] Support the operator between all object types\n\nIt is possible to use the operator on between object types (Meshes, Lattices, Curves, ect) but it doesn't work for GP edit mode, sculpt mode, vertex paint and weight paint modes.\n\n- [ ] (Armature) Edit Mode: The operators still won't run in this mode.\n- [ ] (Metaball) Edit Mode: Doesn't run.\n\n- [ ] (Optional) Also select parented aramtures when using the oeprator in weight paint modes.\n\nWhen using this operator it deselects any other objects, rendering this operator useless for weight paint mode. \n\n- [ ] (Optional) Discuss clarity of the operator name and tooltip. Potentually rename to \"Switch Object\"", "\"Updating Objects Flags\" Stalling Blender\n{[F10130762](22_Nautilus_through_City_-_Cycles___Eevee.zip)}Operating system: Linux-5.8.0-53-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBroken: version: 2.92.0\nWorked: Not working down to 2.83 LTS\n\nThis file will not render the Scene named \"Cycles\" with the Cycles render engine. \n\n\n1. Open attached blend file. Note everything except camera and lights are turned off.\n\n2. Using command line, attempt to render a single frame (say 130).\n\n3. Result = Everything initialises but the render stalls on \"Updating Objects Flags\".\n\n4. Open the file in UI\n\n5. Render image renders a blank image (expected).\n\n6. Turn on Buildings and Landscape, 9 collections from the top, and Nautilus and Submarine Search Lights at the bottom. \n\n7. Render a single frame, or the cycles render layer in the compositor.\n\n8. Result = A single image may render in cycles (followed by the second scene in Eevee that composites).\n\n9. Render animation\n\n10. Result = Blender hangs on \"updating objects flags\" and it does not render, and it is not possible to cancel the render.\n\nIt may be possible to get back rendering by saving the file as a new file. But as soon as rendering an animation as attempted, \"updating objects flags\" hangs Blender either in command line or in UI mode.\n\nNotes: \n\n1. I have tried the same file on multiple machines and multiple Operating Systems with the same result.\n\n2. Quite a number of files have similar kinds of problems. Most commonly, the files will not render in UI mode. Usually though, rendering in command line works. In this case it does not.\n\n3. I have tried every permutation of trouble-shooting I can think of. I have added meshes back in one by one, re-baking ocean modifer, particles, everything. Trying recently, I had to re-bake the particles after which rendering stopped working in any configuration. The particle systems have been baked to a disk cache.\n\n4. Reconstructing from a new blend file is pointless - new blend files are fine and I do not know what is happening to bring about the bug.\n\n5. It may be necessary to re-send the file in its state when it cannot render. Please let me know if anymore information is required.", "Exact Boolean with Incorrect Result - multiprecision/float round trips not exact\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.91.0 Beta dca36a8ec922\n\nAnother case, where the exact boolean does not work as expected. (Sorry @howardt, I had to break it. I have to admit, that I have not run into this problem in a real scene.)\nAgain, this manifests after applying the same difference operation several times.\n\n[boolean_rotated_box3.blend](boolean_rotated_box3.blend)\nLook at the scene.\nThe first run of the modifier works as expected, the second creates overlapping faces, the third removes most of the mesh.\nThis \"bug\" is very erratic, and if the transform of the objects is slightly changed, it does not occur.\n\nThis is what I see:\n\n\nThe expected behavior is that the second and third modifier do nothing.", "Cannot to make single user in object properties (if object is used by multiple collections)\nOperating system:\nGraphics card:\n\nBroken:\n\n\nI made a linked copy of an object (not object data!) in another collection by dragging the object from one window of the outliner to another.\nNow in object properties showing amount users equals 2:\n\n\n\nif you click on button \"make a single copy\" then nothing will happen. I am not sure but seems this UI inconsistency\n\n\nOpen the file and try to make single user to click in object property window:\n\n[make-single-copy.blend](make-single-copy.blend)", "UV: Add \"Common-Origin\" to Average Island Scale\nCurrently, Average Island Scale rescales islands so that they have a similar scale.\n\nHowever the origin of the transform is chosen to be the center of each island individually.\n\nIt would be nice if the origin of the transform could be shared between all the islands, so that subsets of islands which have a common scale would then keep their relative positioning after scaling.\n\n", "Boolean Modifier not working \nOperating system: Windows \nGraphics card: Nvidia Geforce GTX 770\n\nBroken: 2.93.4\nWorked: 2.90\n\nIf one tries to apply the boolean modifier \"Difference\" it does nothing. In previous version it functions.\n\n1. Download the Blender File from above \n2. There a 3 objects in the collections. The objects are in the positive xy-quardant. (Sorry that they are not centered)\n3. If one tries to apply the modifier on the Frame object there is no error message but the frame object doesnt get modified.\n\nGreetings Philip \n\nTest File:\n[#71360.blend](T71360.blend)", "Multi-Object-Mode: Operators that need refactor on their logic\nSome operators are working for multiple-object editing however are still not fully benefiting from it.\nThe most common case is that the operator works but only if all the objects have the same transformation matrix.\n\n* **~~MESH_OT_select_similar~~** (SIMEDGE_FACE_ANGLE, SIMFACE_AREA, SIMFACE_PERIMETER). 0c1934f3c2\n\n* **MESH_OT_knife_project** and **MESH_OT_knife_tool**.\nNeed to convert the code from screen space to world space. More details on [D3637](D3637).\n\n* **UV_OT_weld** (UV_STRAIGHTEN, UV_STRAIGHTEN_X, UV_STRAIGHTEN_Y).\nThe current logic to determine the first and last selected vertex is not very compatible with multi-object. We should be able to select vertices from different objects, and use their position to determine the line extremes.\n\n* **LATTICE_OT_flip**\nThe axis need to be in world space, not local space.\n\n* **~~CURVE_OT_select_similar~~** (SIMCURHAND_DIRECTION). ab77f5b5fe\nNeed to calculate direction taking scale into consideration.", "Python API: Mesh editing: Editing uvs after normals with a previously assigned variable doesn't work\nBroken: 3.5.1\nWorked: 3.4.1\n\nCaused by 6c774feba2\n\nHolding on a variable referencing the uv layer data for later uv editing, doesn't work when normals are edited in between\n\nRun the attached python script in Blender 3.5.1\nThis creates three objects, all should have all their loop uvs as 0,0:\n\n- no_set_normals (should have default normals, sideways)\n- with_set_normals_and_reaccess_uv (should have upwards +z normals)\n- with_set_normals_but_no_reaccess_uv (should have upwards +z normals)\n\nGo in edit mode on each generated object, look at the normals and uvs\nThe results are only correct for no_set_normals and with_set_normals_and_reaccess_uv\nFor with_set_normals_but_no_reaccess_uv, neither the uvs nor normals are correct. Both appear to be defaults\n\nIn Blender 3.4.1 this works as expected, i.e. with_set_normals_and_reaccess_uv and with_set_normals_but_no_reaccess_uv are identical\n\nAttached are also screenshots in 3.5.1 of the normals and uvs of each object\nAnd a screenshot in 3.4.1 showing the expected results\n\n**Guess at what's happening**\nOn more complicated cases (actual meshes with hundreds of triangles), the normals are messed up (seemingly random instead of defaults) and Blender is prone to crashing. This leads me to believe holding on the uv layer data after normal editing accesses freed memory or something like that?\n\n", "Skin modifier does not work on meshes created from scratch during evaluation (primitives, etc.)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.0.0 Alpha\nWorked: NA\n\nSkin Modifier does not work with Geometry Nodes Mesh Primitives, see attached blend file.\n\nOpen attached file, note that Skin Modifier has no effect.\n\n[GN_skin_modif_bug.blend](GN_skin_modif_bug.blend)\n", "Subdivision Surface modifier performance issues\nOperating system: Xubuntu 18.04\nGraphics card: Nvidia Titan X (Pascal)\n\nBroken: 2.80 26d5a3625ed\nWorked: Before the new \"Quality\" setting was introduced in the Subdivision Surface modifier\n\nThe Subdivision surface modifier has slowed down significantly, especially noticable with multiple Subdivision Surface modifiers on the same object.\nCreating the same setup in the builds before the new setting is as fast as 2.79.\n\n- Create Monkey object\n- Add Subdivision Surface modifier\n- Add Wireframe Modifier\n- Add second Subdivision Surface modifer\n[slow-subsurf.blend](slow-subsurf.blend)", "No Vector Displacement On Instances\nWindows 10 x64\n\n2.79.4\n\nVector displacement doesnt work with instances, It mirrors the displacement on the first object, Im sure this is working as intended but there are many cases where you need to displace actual instances as well.\n\nHaving a checkbox somewhere to enable instance displacement would be amazing\n\n\n\n\n\n[instances.blend](instances.blend)\n", "UV: Mesh won't Unwrap at all\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nWhat is happening is that when i unwrap my mesh nothing happen, even if i isolated one face and tried to unwrap it wont work, also even faces you extruded from the faulty face won't unwrap, but adding a new plane from the add menu inside the same mesh unwraps normally, even if i connected the plane to the faulty face.\n\n1. Create a plane.\n2. Give one edge a Mean Bevel Weight from the side bar.\n3. Give the plane a Bevel Modifier and the Limit Method set to Weight (visually nothing will change since its just a plane but the error will still reproduce).\n4. Apply the Modifier and Unwrap the plane. (normally the plane comes unwrapped by default, try changing the UVs out of bounds or scale them down just so you can notice the change ).\n\nThanks you blender developers.", "Add Driver : Clicking the pickers (object / input variable) dont work\nBroken:2.80, 4c31bed6b46, blender2.8, 2018-11-30\n\nClicking the object picker in the `Add Driver` should enter object picking mode, but does nothing.\n\n\nBased on the default startup :\n- Select the **Cube**\n- Right click on **Location/X** and **Add a Driver**\n- Into **Object field**, click on the **picker**\n\n\n> In #58341#702152, @angavrilov wrote:\n> This happens because `ui_context_rna_button_active` within operators and poll functions invoked for the popover UI elements can't find the actual UI control in the popover, and instead returns the property UI control through the context menu of which the popover was invoked. It seems there is a big issue with context and region management in some popovers, and may require a fix in the UI core rather than a specific operator.\n> \n> Edit: Note that this issue is different from the picker attached to the Add Input Variable - that one is simply not (re-)implemented yet to work with the new way Add Driver works.\n\n\nEven though `Object` picker vs `Input Variable` picker are slightly different issues, will keep them together here since from a user perspective this is so tightly related." ]

[ "[UV] [Multi-Edit] Display>Stretch>Area doesn't work\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 57)\nWorked: (optional)\n\n\nThere is a bug with Area stretch type in UV window. It doesn't show correct values (colors). Also it doesn't respect size of one object UV Islands according to another objects sizes. \n\n[When you merge all object into one it all works! It doesn't work with multi edit.]\n\n1.Create cube\n2.Duplicate this cube, put it aside\n3.Open first cube UV window\n4.Move UV a bit that it doesn't overlap with other cube UV\n5.Now select 2 cubes and open UV window, Go to Display>Stretch(tik)>Area\n6. Cubes UVs should be blue, now try resize one of them\n\nThey remain blue and they should changing colors based on size of the object and overall unwrap. \nThis bug is since forever in 2.80 and probably there's more realated to it.\n\nCheers!\n" ]

[ "Collection linking + library override doesn't allow to transform object inside\nBroken: version: 3.6.0\n\n\nLinking this collection and then creating a Library Override on it doesn't allow to move the \"Gear\" object inside such collection.\n\n- Download [Test.blend](attachment)\n- Open Blender and link the collection \"Collection\" from Test.blend\n- In the Outliner right click on the imported collection and do Library Override > Make > Selected and Content\n\n", "blender crash itself while importing a dae (collide) file\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nBroken: version: 2.82 and all versions in between then and now\nWorked: n/a\n\nHi, I'm using blender version 3.3 on a windows 10 downloaded on steam.\n\nwhen i try to import dae files, blender crashes itself and shuts down\n(this only happens with some dae files, not all and the ones who crash are not to big ).\n\nI tried to search with powershell to find the problem and I got this:\n\nError: EXCEPTION_ACCESS_VIOLATION\n[bgr_darryls_ship_ground.dae](bgr_darryls_ship_ground.dae)\n\n```\nThe gh->hashfp function pointer is NULL (hasn't been initialized yet)\n\nblender.exe!ghash_keyhash(const GHash * gh, const void * key) Line 133\tC\nblender.exe!ghash_lookup_entry(const GHash * gh, const void * key) Line 411\tC\nblender.exe!BLI_ghash_lookup(const GHash * gh, const void * key) Line 736\tC\nblender.exe!BKE_armature_find_bone_name(bArmature * arm, const unsigned char * name) Line 601\tC\nblender.exe!ArmatureImporter::create_armature_bones(Main * bmain, std::vector<Object *,std::allocator<Object *>> & arm_objs) Line 478\tC++\nblender.exe!ArmatureImporter::make_armatures(bContext * C, std::vector<Object *,std::allocator<Object *>> & objects_to_scale) Line 826\tC++\nblender.exe!DocumentImporter::finish() Line 228\tC++\n[External Code]\t\nblender.exe!DocumentImporter::import() Line 127\tC++\n```\n", "Outliner: Linking object hierachies to a collection is buggy\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 2.93.2 Release Candidate\nWorked: Unknown\nLinking objects with parent child relationship has inconsistent display behaviour in outliner\n\nThis bugreport is about linking an object in the outliner to an additional collection. \n\nA linked object can have children. Normally they are displayed in a greyed out state until they are also linked to the same collection as the parent. But there is a bug or at least an inconsistent behaviour if these childs are displayed in a greyed out state or not at all.\n\n\nThe following script adds 3 cubes ,creates a collection and links the cubes to it. \nI deleted everything from the Scene Collection and did run the script. \n\nThis will work: \n\nBut just one more child-level in the tree and it starts to behave inconsistent as can be seen in the outliner shown in the screenshot of some reruns of the same script on a totally empty scene. \n\n\n\n\n\n\n\n\n\n```\n\nimport bpy\n\n# create some cubes\nbpy.ops.mesh.primitive_cube_add(location=(0,0,0))\ncube0= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(5,0,0))\ncube1= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube2= bpy.context.active_object\nbpy.ops.mesh.primitive_cube_add(location=(10,0,0))\ncube3= bpy.context.active_object\n\n#create a new coll\ncollection = bpy.data.collections.new(\"Test\")\nbpy.context.scene.collection.children.link(collection)\n\n# establish parent child relationships\n\ncube1.parent = cube0\ncube2.parent = cube1\ncube3.parent = cube2\n\n# link root cube to new coll\ncollection.objects.link(cube0)\n\n\n```\n\n\n", "Crash when modifing materials after using BMesh in Depsgraph-Pre event\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49\n\n\nBroken: version: 3.0.0\nBroken: version: 3.0.1 Release Candidate\nBroken: version: 3.1.0 Alpha\n\nI wrote a script with a function that copies a mesh via BMesh to another object and then changes it's materials. When I want to export the scene as an alembic, Blender crashes when the function gets called via the Depsgraph_Pre event. Depsgraph_Post and Frame_changed_Pre & Post all work fine.\n\n\n- Open the attached Depsgraph_Pre_Crash.blend file in Blender\n- Run the script\n- (Optional) Scroll on the timeline between frames 1 & 2 to check that the script works\n- Set the active frame on the timeline to 1\n- Export as alembic with default settings\n- Blender crashes\n[Depsgraph_Pre_Crash.blend](Depsgraph_Pre_Crash.blend)\n\n[Depsgraph_Pre_Crash.crash.txt](Depsgraph_Pre_Crash.crash.txt)\n\nHere is the callback registered in `depsgraph_update_pre`:\n```lines=10,lang=python\ndef updateFrame(scene): \n```\n emptyObject = bpy.data.objects[\"EmptyObj\"]\n firstOBJ = bpy.data.objects[\"Frame1\"]\n secondOBJ = bpy.data.objects[\"Frame2\"]\n```\n\n```\n if(scene.frame_current == 1):\n bmNew = bmesh.new()\n bmNew.from_mesh(firstOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n```\n\n #Doing anything with the materials crashes blender on alembic export\n```\n emptyObject.data.materials.clear()\n```\n\n```\n if(scene.frame_current == 2):\n bmNew = bmesh.new()\n bmNew.from_mesh(secondOBJ.data) \n bmNew.to_mesh(emptyObject.data)\n bmNew.free()\n \n emptyObject.data.materials.clear()\n```\n", "EXCEPTION_ACCESS_VIOLATION when changing shaders\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0\n\nThis also seems to crash 2.93 and 3.0. \n\nEXCEPTION_ACCESS_VIOLATION causes crash when some shaders are applied.\n\nOpen the file. In the shader editor, set the material of the cube to rim_gradient. Shift-click on the specified shader node in the picture to turn it into the material output. Observe crash.\n\n\n[crash.blend](crash.blend)\n\n\n", "Unlinked/deleted objects reappear, when deleted at startup in a python script (i.e. ./blender --python delete.py)\nDebian 7.4 64bit, also occurs on OSX\n\nBroken: 2.63, 2.69.0\n\n\nUnder certain conditions objects which have been unlinked from a scene do reappear.\n\n\n\n\n - Start blender with `./blender --python delete.py` (see below for the script) (blender just shows an empty scene)\n - Once the GUI is loaded, do: **Add -> Mesh -> Plane**\n # Immediately afterwards hit **F6** and adjust one Property of the newly added object (e.g. the radius)\n\nResult: the objects from the start scene (camera, lamp, cube) reappear.\n\n**Doesn't occur when...**\n - ... A second Mesh is inserted before hitting **F6** to change its properties\n - ... The script is executed in the Blender Editor (and not at startup with option `--python`)\n\n\n**Python script `delete.py`**\n\t\n\n\n\n```\n import bpy\n \n```\n - IMPORTANT: run as: ./blender --python delete.py\n - once blender started, here is what I did in Blender GUI:\n - - add a new mesh (Add -> Mesh -> Plane)\n - - Hit F6 immediately afterwards and modify radius\n # Result: Blender start scene (cube, light & camera) is visible again\n```\n \n```\n # the described bahaviour and result is the same for deleteScene1() - deleteScene3()\n```\n \n def deleteScene1():\n bpy.ops.object.select_all(action='SELECT')\n bpy.ops.object.delete()\n \n def deleteScene2():\n bpy.ops.object.select_by_type(type='MESH')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='LAMP')\n bpy.ops.object.delete()\n bpy.ops.object.select_by_type(type='CAMERA')\n bpy.ops.object.delete()\n \n def deleteScene3():\n scn = bpy.context.scene\n for obj in scn.objects:\n scn.objects.unlink(obj)\n \n```\n - deleteScene1()\n - deleteScene2()\n```\n deleteScene3()\n\n```\n\n\n\n", "Crash on purging orphans\nOperating system: Windows 8.1, Windows 10\nGraphics card: GTX 770, RTX 2060\n\nBroken: 3.3 LTS, 3.5\nWorked: unsure\n\nWhen browsing through material search list fast enough (with textures loaded or not [purple as shown in video]) and then deleting the object + purging orphans, blender crashes.\n\n- Open uploaded file\n- Scroll through materials from dropdown\n- Switch to object mode and delete object\n- In outliner, execute Purge operation from `Orphan Data` display mode\n[#103820.blend](T103820.blend)\n[sample.blend](sample.blend)\n[3.3.lts.mp4](3.3.lts.mp4)", "Old blend file corrupts to crash blender, I guess\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.14761 Core Profile Context 20.11.2 27.20.14540.4003\n\nBroken: version: 3.0.0\n\nCrashes here and there. RN I witness crush form select/deselect. help plz ;c\n\nI do, tho, have installed two PROBABLY outdated addons BUT in new file crash doesn't seem to happen.\n\nThe problem is - Idk exact steps, but overall it takes to select/deselect all/smth at all few times\n\nSteps\n- Open the provided .blend below\n- Enter edit mode on the main SN4K3Mesh\n- Select-All, De-Select-All (Repeat)\n\n[#94213-asan.txt](T94213-asan.txt)\n\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF715993808\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n```\n# Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\nbpy.ops.mesh.select_all(action='SELECT') # Operator\nbpy.ops.mesh.select_all(action='DESELECT') # Operator\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF71599380C\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000000\n\tParameters[1] : 0xFFFFFFFFFFFFFFFF\n```\n\n[SN4K3.blend](SN4K3.blend)\n\n[SN4K3.crash.txt](SN4K3.crash.txt)", "bpy.ops.constraint.apply crashes when owner='BONE' and in object mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nWorked: unknown\n\nThe bpy.ops.constraint.apply operator crashes blender when targeting a bone constraint while in object mode. The attached blender file reliably causes the crash. It also seems to crash in pose mode at times, but I've so far been unable to recreate this in a small example file. See also [#97640](T97640) where a crash relating to the operator being used on objects has seemingly been fixed between 3.1.2 and 3.2\n\nto recreate simply open the blender file and run the script.\n[apply_bone_constraint_crash.blend](apply_bone_constraint_crash.blend)\n[apply_bone_constraint_crash.crash.txt](apply_bone_constraint_crash.crash.txt)\n\n", "Geometry Node boolean input socket broken when recursive linked file is reloaded in the Outliner\nOperating system: Windows 10 19044.1645\nGraphics card: GeForce RTX 3070\n\nBroken: 3.6.1, 8bda729ef4dc, branch: blender-v3.6-release, 2023-07-17\nWorked: none\n\nGeometry Node with boolean group input socket will show error \"Property type does not match input socket (socket name)\" and the input socket will not get evaluated if the recursively linked source file is reloaded in the Outliner 'Blender File' view mode.\n\nBrief description of the file linking structure\n\"01_source_GN-bool-Input.blend\" is the blend file that contains the source geometry node.\n\n\"02_GN_linked_level1.blend\" linked the \"01_source_GN-bool-Input.blend\" geometry node and using it on a local object.\n\n\"03_GN_linked_level2.blend\" linked \"02_GN_linked_level1.blend\" \"GN Cube\" object.\n\nTested with Integer input socket, works as expected in the above file linking condition.\n\n1. Open the attached blend file \"03_GN_linked_level2.blend\"\n2. In the Outliner 'Blender File' view mode (on the middle right of the UI from file), right click on the file \"//02_GN_linked_level1.blend\" and click \"Reload\"\n3. Noticed that the boolean input 'Switch' checkbox is now showing error \"Property type does not match input socket \"(Switch)\"\"\n\n", "GPencil: Blender crash when file open\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.4.0 Beta\n\nAs soon as I open attached file Blender crashes. Attached also crash log file.\n\n- Open attached file\n- Change radius (say 0.6)\n- Save file\n- reopen it (Crash)\n[#102930.blend](T102930.blend)", "Allow changing the active modifier on linked objects\nUnzip the files from [active-modifier-linked.zip](active-modifier-linked.zip)\n\nOpen `linked.blend` and try to change the active modifer. You can't because it is linked.\n\nIn order to allow users to inspect their nodetrees (and eventually see the evaluated result of the modifier) I suggest we treat this as UI data and allow users to change that even for linked objects.\n\nWe do something similar already for the modifier \"Realtime - Display in viewport\" option.\n", "Instancing a collection with an object that has been Disabled in Viewport fails to correctly link in disabled objects breaking \"Make Instances Real\" operator\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0\n\nInstancing a collection into a scene fails to properly link in objects that have been disabled in viewport (henceforth disabled object) using either the \"Disable in Viewport\" icon in the outliner or by setting obj.disable_viewport = True in a script or console. This bug doesn't appear when you hide an object using the H key or obj.hide_set(True)\n\nThis means that if you instance a collection and then \"Make Instances Real\" that the disabled objects will not be transformed with the parent object even if they have been parented to it in the original file and Keep Hierarchy is checked. \n\nThis is a problem because if you have used the disabled object as the operand in e.g. a boolean modifier then as soon as you make a collection real your collection breaks. This is doubly a problem since the default behaviour in the new asset browser is to instance collections into the scene rather than appending them. This bug also affects instancing a collection in the same scene as well as instancing in a collection from an external file. \n\nStart from default file. \nAdd a second cube.\nTransform second cube and place on corner of default cube.\nMake second cube a child of default cube.\nAdd a boolean difference modifier to default cube.\nSet second cube as Object in boolean modifier\nDisable second cube in viewport in the outliner\nInstance collection into scene by dragging and dropping collection from outliner somewhere which isn't the origin.\nEverything appears as it should.\nSelect instanced collection\nSelect Object > Apply > Make Instances Real\nWhile the none disabled cube has been made real the second cube hasn't and if we look in the modifier you can see that the boolean object is still set to the original second cube.\n\nIf instead of disabling the second cube we instead hide it and then instance the collection into the scene the second cube is linked in (although it's also unhidden which is annoying). If we the make this collection real everything works as it should (i.e. the second cube used as a boolean is also made real)\n[link bug.blend](link_bug.blend)", "Switching collections does not work in Local mode.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 580/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 5)\nWorked: 2.81\n\nIn Local mode, switching collections with hotkeys (1, 2, 3 ...) does not work.\n\nWhen I select several objects from different collections, and go into local mode, switching collections through hot keys (1, 2, 3, etc.) stops working.\n\n", "Objects with physics referred to by PointerProperty throw find_node_operation: Failed for (RIGIDBODY_REBUILD, '') when rendering\nOperating system: Ubuntu 20.04, Windows 10\nGraphics card: GeForce GTX 2080, GeForce GTX 1080\n\nBroken: 3.1.2\nWorked: Unknown\n\n\nWhen you have a PointerProperty, and that property refers to an object that has a rigid body, the following is output to the console when rendering:\n\n```\nfind_node_operation: Failed for (RIGIDBODY_REBUILD, '')\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Could not find op_from (OperationKey(type: TRANSFORM, component name: '', operation code: RIGIDBODY_REBUILD))\nadd_relation(Rigid Body Rebuild -> Point Cache Reset) - Failed, but op_to (ComponentKey(OBBox, POINT_CACHE)) was ok \n```\n\nThis doesn't seem to have any other adverse effects, as rendering still succeeds with the object in the correct simulated position, but these types of messages fill up the console extremely quickly.\n\nOpen the following blend file, and render a frame. For some reason this requires the file to be opened via the UI.\n[repro2.blend](repro2.blend)\nAlternatively, unzip the following and run with `blender -b --python repro.py`.\n[repro.zip](repro.zip)\n" ]

[ "Crash after Instancing to Scene after making linked Collection local\nOperating system: Linux-5.8.0-59-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 520 (SKL GT2) Intel 4.6 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.1\nWorked: none known\n\nBlender crashes after instancing a collection to the scene after making it local from being linked.\n\n- Link a Collection into a blend file or open the attached linking.blend which has a collection linked from external.blend\n- Use the operator \"ID Data\" > \"Make Local\" on the linked collection.\n- Instance the collection to the active Scene.\n- Try to do something in the 3D Viewport.\n- Blender crashes\n\n[linking.blend](linking.blend)\n[external.blend](external.blend)\n[linking.crash.txt](linking.crash.txt)\n\n\nAlso, see the attached video:\n[linking-crash-2021-07-12_21.17.08.mp4](linking-crash-2021-07-12_21.17.08.mp4)\n\n" ]

[ "sharp_edge attribute doesn't work for GN-created geometry in 4.0\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13\n\nBroken: version: 4.0.0 Alpha\n\nBlender 4.0 is expected to finally expose normal smoothing capabilities to geometry nodes, and while the sharp_face attribute seems to somewhat work on the geometry generated inside GN, instead of inherited from the parent object, sharp_edge attribute just won't work on GN-created geometry no matter what.\n\n\n1. Open the attached file: [sharpbug.blend](attachment)\n2. Move the B value of Great Than node\nResult: sharp_edge attribute modifications don't have any effect on the mesh shading.\nExpected: sharp_edge attribute modifications affect the mesh shading.\n\n", "Frame Selected does not respect Geometry Nodes viewer geometry\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.11.2.221130\n\nBroken: version: 3.5.0 Alpha\nWorked: n/a\n\nNot sure if this is a bug to report or feature request but a minor inconvenience with the Viewer node.\n\nWhen Geometry Nodes Viewer node is active, Frame Selected works on the (invisible) output geometry instead of the Viewer geometry. Since the Viewer geometry is actually selectable, I think it makes sense that Frame Selected to respect it.\n\n[FrameSelectedViewerNode.mp4](attachment)\n\n", "Vertex Painting with data type \"Color\": Painting pure Red or Green creating non Zero in Blue Channel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.63\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nIn Geometry Nodes, I've tried scattering objects with vertex painting (data type \"Color\") using pure red (1,0,0), green (0,1,0) and blue (0,0,1). With a math node set to \"Greater than\", the different color channels are tested whether their values are bigger than 0. However, I discovered that I needed actually a \"Threshold\" value slightly bigger than 0 (I used 0.0001, just below the \"Spreadsheet's\" precision) because my objects for the blue painted areas got also displayed in red and green areas with a \"Threshold\" value of exactly 0 for testing the blue color channel. The red and green channels could be tested with a threshold of exactly 0. \n\nWith vertex painting using the data type \"Byte\", I could also set the blue channel's testing threshold to exactly 0.\n\n**Steps to Reproduce**\n- Open attached file\n- Set Threshold value exact to 0 for blue color channel\n[Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend](Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend)\n\n", "Geometry Nodes Volume Features Implementation\n**Status:** *In planning phase*\n\n---\n\n## Team\n**Commissioner:** @HooglyBoogly\n**Project leader:** `?`\n**Project members:** @erik85 \n\n## Description\n**Big picture:** *Address the large opportunities for procedural volumes while fitting into geometry nodes design, especially using existing openVDB tools*\n\n**Use cases**:\n* Procedural modeling\n* Fluid simulation\n* Motion graphics\n* ...\n\n**Design:**\n* Volume grids are like attributes conceptually\n* SDF Volumes are openVDB level sets and can be accessed directly with new nodes\n* Volumes have one built-in grid, \"density\", which is an SDF grid\n* Volumes can be adjusted and created with fields\n\n**Engineer plan:**\n* Besides field evaluation, openVDB tools will be used for most functionality\n* Initially fields will just be used to reference grids directly\n* Field evaluation will be very basic, just flattening out all data in the context's voxel topology\n\n\n## Work plan\n### Milestone 1 - Very basic SDF volume nodes\n*Expose SDF volumes as a basic data type, provide a few fundamental nodes for future development*\n\n- [x] SDF Sphere input node (creates a sphere with openVDB function, puts it in \"distance\" grid\n- [x] Add \"Mesh to SDF Volume\" and \"Points to SDF Volume\" nodes\n- [x] Add a SDF volume \"filter\" node using the openVDB level set tools functions (no mask input yet). Just acts on \"distance\" grid\n\n### Milestone 2 - Basic support for fields as references to grids\n*Allow referring to grids with the named attribute node, but not any modification*\n- [x] The named attribute node (`AttributeFieldInput`) should work for volumes too, referencing grids by name\n- [x] Add a \"Sample Volume\" node that gives the value of a grid at a location, with an `AttributeFieldInput` input. Any other field can be rejected for now. It just looks up the grid by name\n- [x] Add the \"Signed Distance\" node which is a field input node for the \"distance\" attribute\n\n### Milestone 3 - Grids as anonymous attributes\n*Creation of and references to grids without a name, to allow referencing them with node links*\n- [ ] Add the ability to store grids with an anonymous attribute ID rather than a name\n- [ ] Add \"SDF to Fog Volume\" and \"SDF to Mask Volume\" nodes that create anonymous grids\n- [ ] Support anonymous grids in \"Sample Volume\" node\n- [ ] Add basic support to \"Store Named Attribute\" node. For now it can only give a name to an anonymous grid\n- [ ] Change Volume Cube node to output an anonymous grid, use \"Store Named Attribute\" for versioning\n- [ ] Add field inputs to \"Volume to Mesh\" and \"Distribute Points in Volume\" nodes. Like above, only supports `AttributeFieldInput` for now.\n\n### Milestone 4 - Evaluating fields on grids\n*Support basic volume advection*\n- [ ] Add a `VolumeGridFieldContext` that can provide the position field at each voxel (by index for now, so voxels probably have to be flattened)\n- [ ] Add an \"Advect Volume\" node with an \"Offset\" field input.\n- [ ] Give the grid field context the ability to sample other volumes (special VArray output for attribute field input)\n- [ ] Add the ability to create grids matching the exact topology of existing grids with capture attribute node and store named attribute node\n\n### Milestone 5 - Changing grid values with fields\n- [ ] Allow function nodes on arrays of flattened voxel values provided by the field inputs from milestone 4\n\n### Milestone 6 - More advanced volume nodes\n*More advanced use cases building on the fundamentals above*\n- [ ] \"Fracture SDF Volume Node\" corresponding to fracture level set openVDB tool\n- [ ] Volume Boolean node including CSG operations (this could come earlier, but the design isn't totally clear yet)\n- [ ] More...?\n\n\n---\n\n### Relevant links\n* #91668 (How to deal with multiple volume grids in a geometry)\n* [D12100: Geometry Nodes: Level Set Nodes (WIP)](D12100)", "Support warnings for field input nodes\nField input nodes evaluate in a context, but currently they give no warning if they do not support\na particular context. The initial goal is to add a warning like \"Input node does not support geometry type: Mesh\" on the spline parameter node in the following situation:\n\n{[F12738459](image.png) size=full}\n\n### Implementation\nA potential implementation isn't clear.\nIt seems there needs to be a way to keep track of which node (`bNode`, `NodeRef`, `DNode`, etc.) the field input node came from.\nThen the field evaluation system should have a way to collect errors and return them to the caller. Or maybe the caller can pass a\n\"logger\" class to the field evaluation system. That generalization could allow more specific breakdowns of node timing in the future.", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT960\n\nBroken: 3.5.0 (2023/01/11)\n\nData Transfer does not work on geometry generated by Geometry Nodes\n\nError is set up in the attached file:\n\n[Color Transfer Test.blend](Color_Transfer_Test.blend)\n\nDoesnt work in `Material` or `Rendered` viewport mode either.\n\n[Color Transfer Test 2.blend](Color_Transfer_Test_2.blend)\n\nI don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.\n\n[GeometryNodesColorBug.blend](GeometryNodesColorBug.blend)", "Maximum number of attributes that can be used with eevee shading needs to be documented\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.6.0 Beta\nWorked: This is the only version I have used\n\nThere are more than 20 parameters or attributes in my geometry nodes setup, and when I try to use those attributes in shader editor it doesn't update its values. Sometimes it updates when there is a viewer node connected.\n\nIts a big node tree and a lot of materials, so that's it.\n\n", "Support Attribute Search In Material Nodes\nThe \"Attribute\" node in shader node trees could support attribute search based on the context data. The search code would be generally the same, but the data would be accessed directly from the evaluated geometry set of the active object. \n\nTherefore attribute search should not be used when the node tree is pinned, or alternatively it could depend on the pinned object context of the node editor, if that is available.\n\nNote that fewer attributes are available for EEVEE. There will have to be a special case there until more attribute access is implemented there.\n\nSome starting points / references:\n`node_geometry_attribute_search.cc`\n85421c4fab\nc0b2c75c44\n[D10623: Geometry Nodes: Add domain and data type to attribute search](D10623)", "Geometry Nodes: writing attributes (from procedurally created geometry) to vertex groups not working\nOperating system: macOS Monterey 12.4\nGraphics card: RX 6800 XT\n\nBroken: 3.1 & newer\nWorked: 3.0.1\n\n\nIn Blender 3.0.1, it was possible to write attributes from procedurally created geometry (created by geometry nodes) to vertex groups, as long as the \"Group Input\" node was joined with the procedural geometry. However, no version newer than 3.0.1 seems to have this capability. From what I understand, this may have been done intentionally in anticipation of attributes replacing vertex groups entirely... but it seems odd to kill this feature before that transition is complete, so I'm reporting this as a bug.\n\n\nOpen the attached .blend file in Blender 3.0.1:\n[geonodes_attrib_to_vgroup.blend](geonodes_attrib_to_vgroup.blend)\nThis file contains a geonodes setup where half of a procedurally generated grid is extruded using a solidify modifier. The \"geonodes\" object should look exactly the same as the \"Expected Result\" object. \n\nNext, open the file in Blender 3.3 (or 3.1, or 3.2) and notice how the \"Expected Result\" object no longer matches the \"geonodes\" object.\n", "Geometry Nodes: 3D Viewport Overlay Statistics don't respect Viewer Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.4.0 Alpha\n\n\nThe geometry output by the preview node is not taken into account by the overlay scene statistics:\n[2022-09-30 11-35-43.mp4](2022-09-30_11-35-43.mp4)\n", "Annotations shouldn't be shared among different Geometry Nodes\nOperating system: ubuntu 20.04\nGraphics card: cpu\n\nBroken: 2.93.0\n\nWhen you ad an annotation to a geometry node, by default the same annotations can be seen in all the other geometry nodes layout.\nThis is unexpected, since each geometry node layout should have its own annotations.\n\nAdd a geometry node modifier.\nWrite something with the annotate tool.\nDuplicate that geometry node modifier, erase the old nodes, the annotations, and you'll find out that you erased the annotation also from the first geometry node layout.\n", "Output UVs from mesh primitive nodes with anonymous attributes\nInstead of creating a named `uv_map` attribute on the geometry, they should be anonymous attribute field outputs. This brings up a few complications.\n- Currently we have no 2D vector socket. We probably want to avoid adding this for 3.0, so a 3D vector can be used for now. Automatic conversions will make versioning simple when we add a 2D vector socket, hopefully for 3.1.\n- The BMesh mesh primitive icosphere creates an `MLoopUV` attribute, this should be converted into a 3D vector anonymous attribute.\n\nThe output should be called \"UV Map\"", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "GPU Subdivision: Geometry Nodes: Realize Instances node does not use the GPU version of the curve object\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: Current master.\nWorked: Never.\n\nCollection Info node does not use the GPU version of the curve-objects from collection.\n\n1. Create curve.\n2. Make curve extruded.\n3. Added subdivision modifier.\n4. Create another collection.\n5. New object in another collection.\n6. Added geometry nodes:\n a. `Collection Info` -> `Realize Instances` -> `Group Output`.\n b. Set first group in `Collection Info` node." ]

[ "Geometry Nodes: Writing an attribute of type 'color' directly to the position attribute has no effect.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel Iris OpenGL Engine Intel Inc. 4.1 INTEL-12.10.16\n\nBroken: version: 2.93.0 Alpha\n\nWriting to the position attribute doesn't work when using an attribute of type 'color'.\nThis means: Directly writing the output of the Attribute Sample Texture node to the position attribute or mixing colors with the Attribute Mix node with the result set to \"position\" has no effect.\nBoth cases work for the rotation and scale attributes.\nExplicitly converting the color attribute to a vector attribute first using a Vector Math Node works as expected.\n\n[position-attribute-bug.mp4](position-attribute-bug.mp4)\n\n\nFrom startup file:\n- Add a Geometry Nodes modifier to the default cube\n- Add an Attribute Sample Texture node, plug it in between input and output node. Add a new Texture and set the result to \"position\".\n- The position of the vertices will be unaffected.\n\nFrom the .blend-file in the video:\n- open the file and plug in different Attribute Sample Texture nodes into the Point Distribute node. The one with the Result set to \"position\" will have no effect.\n[sample-texture-position-bug.blend](sample-texture-position-bug.blend)\n\n", "Use implicit conversion when writing to built-in attributes\nNormally the type of a node's output attribute will change based on the operation. \nFor example, the attribute color ramp node will always upgrade the type of the output to \"Color\". \nHowever, the type of built-in attributes cannot change, so the writing fails.\n\nThere are two options to solve this:\n1. Change every node that writes an attribute to support writing with all types\n2. Use implicit conversion when writing to a built-in attribute\n\nThe second option should be implemented for this task, which will likely involve changing `OutputAttributePtr`. \nThe first option can be implemented for some nodes later if the implicit conversion ends up being a performance bottleneck." ]

[ "Curves: Edit mode transform pivot on individual origins does not work\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.2.1.230210\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nAlso 3.5 beta.\n\nIn curves edit mode, transform pivot on individual origins does not work.\n\nPivot on active element also does not work, but it seems curves edit doesn't have the concept of active element at all, so not sure if this is a limitation right now.\n\n[CurvesEditTransformPivot.mp4](attachment)\n\n", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT960\n\nBroken: 3.5.0 (2023/01/11)\n\nData Transfer does not work on geometry generated by Geometry Nodes\n\nError is set up in the attached file:\n\n[Color Transfer Test.blend](Color_Transfer_Test.blend)\n\nDoesnt work in `Material` or `Rendered` viewport mode either.\n\n[Color Transfer Test 2.blend](Color_Transfer_Test_2.blend)\n\nI don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.\n\n[GeometryNodesColorBug.blend](GeometryNodesColorBug.blend)", "UV Unwrapping: Disconnect between unwrapped geometry and displayed geometry with shapekeys\nOperating system: Linux-5.15.11-76051511-generic-x86_64-with-glibc2.34 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 3.2.0 Alpha\nWorked: (presumably) never\n[uv_unwrap_shapekeys-2022-02-07_12.29.52.mp4](uv_unwrap_shapekeys-2022-02-07_12.29.52.mp4)\nUV unwrapping uses active shapekey as if it was fully applied, even though it isn't active in the viewport.\n\nI don't think you can call this a bug, but unwrapping another geometry than the one you see should not be intended behaviour. It's a big point of confusion and potential source for errors. So I'm creating a report nonetheless.\n\n- Create shapekey on plane\n- Deform shapekey\n- Turn on `Shape Key Edit Mode`\n- UV unwrap geometry while deformed shapekey is active\n\nFile:\n[uv_unwrap_shapekeys.blend](uv_unwrap_shapekeys.blend)\n", "Sculpt Mode: Edit Voxel Size hotkey conflict\nOperating system: Win 10\n\nBroken: blender-2.90-51ac411ce80c-windows64\n\nThe \"Edit Voxel Size\" and the \"Repeat Last\" functions are using the same hotkey (Shift+R), and as a result, the \"Repeat Last\" command is not working in sculpt mode.\n", "Delete geometry node performance regression writing to multiple vertex groups in 3.1\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0\nWorked: 3.0.1 and older\n\nCaused by f5e5a0987a\n\nUsing a combination of Delete Geometry node along side the Armature modifier makes the node run slower and slower the more vertex groups armature is using. The difference is an immense drop from 144fps back to 8fps using the same .blend file in 3.0.1 and 3.1\n\n[Delete Geometry + Armature 3.0.1.blend](Delete_Geometry___Armature_3.0.1.blend)\n\n[Delete Geometry + Armature 3.1.blend](Delete_Geometry___Armature_3.1.blend)\n\n**.blend file overview**\n\n\nI would argue that this bug is a high priority issue and makes a lot of the character animation workflows impossible to use in 3.1 .\nDelete Geometry Node has been a replacement for the Mask Modifier ever since Geometry Nodes was introduced, it is a crucial part of a lot workflows. \n\n\n\n**More information if needed :**\n\n- Order of the modifiers does not matter\n- Vertex groups on the mesh have to be used by the armature for it to take an affect, however the vertex group used to delete the geometry is not being used by the Armature\n- The issue seems to be that the Node is now checking every single vertex group instead of the single attribute given to it\n- The more vertex groups used by the armature the worse the performance\n\n\n\n", "Subdivision modifier does not interpolate zero weights.\nOperating system: Linux\nGraphics card: Intel UHD\n\nBroken: 2.90.1\nWorked: ???\n\n\nThe subdivision modifier usually interpolates both value and membership across subdivided vertices.\n\nThis allows it to be used in non-destructive, modifier-based workflows that operate on or using vertex groups.\n\nIt does not do this, however, when vertex weights are equal to zero. The original vertices retain their (zero-weighted) vertex group membership, while new vertices in between them have no vertex group membership.\n\nAn example of why this is problematic is screenshotted below, with the file attached:\n\n\n\nEach Subdivision'd sphere has a bumpy texture applied using a Displace modifier after a textured VertexWeightMix modifier.\n\nThe rightmost sphere has its vertices weighted to 0.01, and interpolates and behaves correctly.\n\nThe leftmost sphere has its vertices weighted to 0.00. It intuitively (and, numerically/extrapolatively) should be indistinguishable to the 0.01 sphere. Because its weights aren't correctly interpolated, it instead ends up with a bunch of spikes at each of its original vertices.\n\nThe middle sphere has vertices weighted in a gradient from 0.00 to 0.50. It serves as an example of a feasible real-world application which would be broken by this kind of behaviour. Perhaps the original vertex weights act as a sort of base heightmap for a terrain model, and the changes made by the Subdivision and textured VertexWeightMix modifiers add an extra layer of detail. In this case, the clear and useful behaviour would be for behaviour to be continuous in the transition from 0.01 to 0.00. Instead, there is a sharp cutoff at 0.00, and inconsistent and discontinuous behaviour after that.\n[ZeroWeightSubdiv.blend](ZeroWeightSubdiv.blend)\n\nApply a subdivision modifier to a mesh with zero vertex weights, then check the vertex group membership of its vertices afterwards.\n\nOr download and open the attached `.blend` file.", "Sculpting with shape keys very slow\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.2.1\n\nAdding shapekey to the model slows down the sculpting process a lot\n\n[2022-07-29-13-53-25.mp4](2022-07-29-13-53-25.mp4)\n\n", "Undoing the removal of a vertex group in edit mode changes other vertex groups and doesnt bring the removed vertex group back\nOperating system: Linux-5.4.13-201.fc31.x86_64-x86_64-with-fedora-31-Thirty_One 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: (optional)\n\n\nUndoing a vertex group changes the rest. The video should show the issue. There's 3 vertex groups, A = A, B = B and C = C. If you delete A, B = B and C = C. If you delete A and then undo it, B = A and C = B.\n\nTy9U5rj_6Sw\n\n[#63434.blend](T63434.blend)\n- Open File\n- you should be in editmode\n- remove the `zero_weight` vertex group\n- Undo {key Ctrl Z}\n- `zero_weight` vertex group is not back\n- `half_weight` vertex group now has zero weights\n- `full_weight` vertex group now has half weights\n\n\n", "Child Of vertex group fails when controled by Particle System\nWin10 64bit\n\nBroken: 2.79\n\nChild Of constraint fails on rotation from PS\n\nOpen file, play animation on every layer\n\nFirst layer: *Empty* with *Child Of* constraint is controled by Plane's transform animation -> works OK\nSecond layer: *Empties* with *Child Of* are controled by Plane's *Particle System* (via *Explode*) -> Location is maintained, but **rotation is non-synchronized**\nThird layer (example of how previous case is expected to work): Empties parented to *3 vertices* are controled by same PS - OK\n[Child_Of_test.blend](Child_Of_test.blend)\n", "Mesh edit, Shift+V vertex slide adjustment produces unexpected result\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.92.0\n\nInstead adjustment movement with slider i have broken shape:\n[2021-04-30_15-00-38.mp4](2021-04-30_15-00-38.mp4)\n\n", "Curves with curve modifiers are not translated to mesh correctly and can't be used as a target for constraints and modifiers predictably\nOperating system: W10\nGraphics card: GTX 1080TI\n\nBroken: 2.80-d966c2f0c2ad-win64\nWorked: 2.79 master build\n\nIf you ctrl+a and press \"visual geometry to mesh\" on a curve that has a curve modifier, the resulting mesh you're getting is as if you didn't have that curve modifier at all. This was not the behaviour in 2.79b. Also, if you assign any constraints or assign this curve as a modifier for objects, you'll have it deformed as if the deforming curve doesn't have the curve modifier.\n\nCtrl+a on the bezier curve in this sample file\n[sample.blend](sample.blend)", "Nonfunctional \"Vertex Weight Proximity\" Modifier's Influence Mask Inversion\nOperating system: Linux-5.4.0-66-lowlatency-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 680/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nLast Broken: version: 2.93.0 Alpha\nFirst Broken: version: 2.90.0\nWorked: version: 2.83.13\n\nButton for inversion of Influence Mask (modifiers[\"VertexWeightProximity\"].invert_mask_vertex_group) in \"Vertex Weight Proximity\" Modifier doesn't work.\n\n\n* Open the attached .blend file.\n* Click Invert button of \"Mask Vertex Group\" in \"Vertex Weight Proximity\" modifier (Influence section).\n* Mask is not inverted on the model & Face button of Geometry proximity mode gets wrongly highlighted. (Its highlighting seems to be linked with the Invert button.)\n\n* Another thing I observed is that any change of Geometry Proximity mode (ie. Vertex / Edge / Face) clears both Falloff inversion and Mask Vertex Group inversion if they are switched on. Which was the case in Blender versions 2.83.x too.\n\n[Vertex Weight Proximity Bug.blend](Vertex_Weight_Proximity_Bug.blend)\n\nP.S.: This issue might be connected with the issue:\nT83863\n\nThanks and have a good day!\n", "Themes→3dViewport→Active vertex color do nothing\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.5.0\n\nThis one influence nothing. Should it be deleted?\n\n\n[2023-04-13_07-48-03.mp4](attachment)\n\n\np.s. Dull colors and other issues about wireframe [described here](426) and I am sad, that it looks abandoned and ignored…\n\n", "Removal of an attribute with same name as Vertex Group removes the Vertex Group instead of the Attribute\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.4.0 (Also 3.5 Alpha hash: `50c7eb14f455`)\nWorked: Never, 3.3 both the attribute and vertex group are removed\n\nWhen removing an attribute that has the same name as an existing vertex group using either the UI button or the Python API the vertex group is removed instead of the attribute\n\n1. Open Blender\n2. Add an attribute named 'Group' to the default cube\n3. Add a vertex group (automatically name 'Group')\n4. Remove the attribute named 'Group' using either the - button or the following API command `C.object.data.attributes.remove(C.object.data.attributes['Group'])`\n5. The vertex group is removed instead of the attribute\n\nIn 3.3 LTS both the attribute and vertex group are removed when trying to remove the attribute.\n\n[removal_of_attributes_vg_bug.webm](removal_of_attributes_vg_bug.webm)" ]

[ "ShapeKey does not \"see\" modified Vertex Group (e.g. proximity modifier, dynamic paint)\nOperating system: Linux-5.11.0-25-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.57.02\n\nBroken: version: 3.0.0 Alpha\nWorked: I don't know...\n\nI'm not sure if it's a bug...\nThe \"vertex group\" option inside shape keys is not using the \"modified\" result of the vertex group modifier for example proximity. Not even using the result of geometry nodes modified vertex group.\n\nJust open the prepared blend file and you will see methods:\n- Painted = Just randomly painted the vertex group and use it to \"limit\" the \"cast\"(cast modifier applied as shape) shape key.\n- Proximity modifier = A modified vertex group (all weights set to 1.0) via proximity modifier and I'm trying to feed the \"vertex group\" shape key dropdown menu but it seems to use the original vertex group and not the modified one (I'm not sure if it's a bug or if it misses the option to choose between original or modified vertex group).\n- Geometry Nodes = A proximity attribute mixed with the vertex group to get the same effect as proximity modifier and overwriting the vertex group and I'm trying to feed the \"vertex group\" shape key dropdown menu but it seems to use the original vertex group and not the modified one.\n\n[ShapeKey_VertexGroup.blend](ShapeKey_VertexGroup.blend)", "Dynamicly changed weight paint does not affect Shape Keys\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.2\n\nIf you have weight paint that is being set dynamically - for example by using dynamic paint and a shape key that uses vertex group same as the one being modified, there is no change in the shape even if weight was changed.\n\nReproduction steps:\n1. Create sphere\n2. Create Basis and Key 1 shape keys and set value to 1\n3. Enter edit mode and modify the shape key (for example resize the sphere), then exit edit mode\n4. Add Vertex group\n5. Set the new group in the Vertex Group in the shape key\n6. Add dynamic paint, canvas, Surface Type : Weight, Output: Vertex Group : Group\n7. Add second sphere\n8. On second sphere add Dynamic Paint : Brush, surface: Volume + Proximity\n9. Create animation where one ball is 2 ball lengths apart and gets as close as to touch the other ball\n\nResult: In weight paint mode observe that weight changes, but the shape is not affected.\nBonus round: Paint the weight paint manually and observe object changing\n\nI have tested it on Blender 3.1 and Blender 3.0, both have this problem\n\n", "Driving shape keys with vertex groups generated from modifiers (like vertex weight proximity) does not work.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.1.2\n\n[Im trying to affect the pre-existing shape key through a vertex group generated by modifiers like:\n1- vertex weight proximity modifier\n2- data transfer modifier]\n\n[Everything is set up in the file with different examples of cases that work and those that don't]\n\n" ]

[ "Timeline scrubbing is laggy when Preview tab is open in Material Properties\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.0\nWorked: N/A\n\n\n\nHaving the little preview tab open in Material Properties when scrubbing the timeline causes heavy lag, noticeable even on the default cube file. \n\nThe material can be a mesh material or a grease pencil material, but the result is the same.\n\nVideo example: watch?v=1Fw6Y-XzMyE\n\n", "Blender 3.2.1 - Particles - Particles generate differently on Linux vs Windows\nOperating system: Linux-5.4.0-122-generic-x86_64-with-glibc2.31 64 Bits - Windows 10 x64\nGraphics card: NVIDIA GeForce GTX 1080 - NVIDIA RTX 3080\n\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: a2d59b2dac\nWorked: 2.7.9\n\nParticles render differently between windows and linux.\nLinux:\n\n\nWindows and MacOS:\n\n\n\n[particleTest_v001.blend](particleTest_v001.blend)\n\n1. Open attached blend file on a Linux machine\n2. press f12\n3. save image to network drive\n4. open attached blend file on a windows machine\n5. press f12\n6. open the image from the network drive in another window\n7. press alt tab to flick between them and see that the particles generate differently.\n\n", "VSE UI: Change Path/Files is over exposed \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nChange Path/Files is exposed in four places. \n{[F10401818](image.png),size=full}\nAs this function is only working(afaik) on the active strip(why Files in plural?), it should only be exposed in the strip sidebar. See: #91306 If the function is basically the same as changing the path to the source file then the folder button next to the path should be enough. \nAlso, having it as a secret pop-up menu, shortcut key \"C\", is inconsistent with anything in Blender and this should be removed. \n\n\n", "Filesystem accidental creations of directories\nOperating system: Windows 10 Pro (64-bit), version 1809, OS build 17763.615\nOperating system: Ubuntu 18.04.2 LTS 64-bit\nGraphics card: Nvidia GTX 650\n\nWindows Build version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: \nWindows Build version: 2.81 (sub 1), branch: master, commit date: 2019-08-05 13:33, hash: 8f1a55831c89, type: Release\nUbuntu Build version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: Release\n\nThe window pop-up asking for confirmation of a filesystem change, e.g creating a directory, seeks cursor and a click gets immediately accepted as a confirm.\n\nFile -> Open\nClick the \"file path\" area (\"C:\\Users\\%USERNAME%\\\" or similar)\nType \"C:\\Users\\%USERNAME%\\something_random\" and click in the file browser.\nResult: Created a directory called something_random.\n\nBased on the default startup nothing other than Blender needed.", "File browser should show a note about full disk access upon encountering an inaccessible folder\nOperating system: macOS-11.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: version: 3.0.0\nWorked: (2.93)\n\nKnown Issue: File browser cannot navigate in files in newest version of Box Drive (cloud based storage) ~/Library/CloudStorage/Box-Box or Apple Mail in `~/Library/Mail`\n\nUpdate Box Drive to version 2.24.11, open Blender, Add/Attach Image/Reference, attempt to navigate in Blender File Browser, Blender cannot see/locate Box Drive to add reference image.\n[c3VqYUVoNTv]\n\nOR\n\nTry to navigate to ~/Library/Mail in blender file browser.\n\nCurrent fix is to give Blender Full Disk Access in System Preferences: 12.0\n\nIf this type of read permission denial can be detected, we could show a warning about allowing full disk access or directing them to docs on how to do it.\n", "Asset Browser refreshes unnecessarily and halts Blender when doing so\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\n\nThe Asset Browser refreshes its thumbnails often, without need for it, and stalls Blender when doing so.\n\nThe video demonstrates that only some actions cause this and that this only happens when the Asset Browser is visible + it shows that the UI can be completely unresponsive for seconds.\n\nThis happens any time the asset browser is open and certain actions such as deleting any object is being performed.\nLarger Asset libraries and slower hard drives compound the issue.\n[2022-08-30_17-22-14.mp4](2022-08-30_17-22-14.mp4)", " BLI_mmap not thread-safe on Linux/macOS (unfreed memory generating thumbnails)\nRecently I noticed generating blend file thumbnails sometimes leaks memory, this is caused by 0f2ae614a1, which uses a linked list for `error_handler_data.open_mmaps`, threads are used to open blend file thumbnails which add/remove items without any locking.\n\nTesting should be straightforward.\n\n- Remove thumbnail cache, (e.g. `rm -rf ~/.cache/thumbnails`)\n- Open a directory containing many blend files.\n- Wait for the thumbnails to load.\n- Close blender.\n\nOn exit ASAN reports this error (below).\n\nChecking `BLI_mmap` it looks like all list access would need to locking, including handling errors.\n\n----\n\n```\nDirect leak of 32 byte(s) in 1 object(s) allocated from:\n - 0 0x7f7ed1d97459 in __interceptor_calloc /build/gcc/src/gcc/libsanitizer/asan/asan_malloc_linux.cpp:154\n - 1 0x55cd8a26f9ac in MEM_lockfree_callocN /src/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:236\n - 2 0x55cd8a00563a in BLI_genericNodeN /src/blender/source/blender/blenlib/intern/listbase.c:932\n - 3 0x55cd89eded19 in sigbus_handler_add /src/blender/source/blender/blenlib/intern/BLI_mmap.c:136\n - 4 0x55cd89edef8c in BLI_mmap_open /src/blender/source/blender/blenlib/intern/BLI_mmap.c:188\n - 5 0x55cd89fa181d in BLI_filereader_new_mmap /src/blender/source/blender/blenlib/intern/filereader_memory.c:130\n - 6 0x55cd83c2f97d in blo_filedata_from_file_descriptor /src/blender/source/blender/blenloader/intern/readfile.c:1223\n - 7 0x55cd83c2fec8 in blo_filedata_from_file_open /src/blender/source/blender/blenloader/intern/readfile.c:1270\n - 8 0x55cd83c30137 in blo_filedata_from_file_minimal /src/blender/source/blender/blenloader/intern/readfile.c:1293\n - 9 0x55cd83c31e31 in BLO_thumbnail_from_file /src/blender/source/blender/blenloader/intern/readfile.c:1513\n - 10 0x55cd84e68067 in imb_thumb_load_from_blendfile /src/blender/source/blender/imbuf/intern/thumbs_blend.c:72\n - 11 0x55cd84e6810b in IMB_thumb_load_blend /src/blender/source/blender/imbuf/intern/thumbs_blend.c:86\n - 12 0x55cd84e6540c in thumb_create_ex /src/blender/source/blender/imbuf/intern/thumbs.c:390\n - 13 0x55cd84e6676c in thumb_create_or_fail /src/blender/source/blender/imbuf/intern/thumbs.c:495\n - 14 0x55cd84e677e9 in IMB_thumb_manage /src/blender/source/blender/imbuf/intern/thumbs.c:656\n - 15 0x55cd893c5c44 in filelist_cache_preview_runf /src/blender/source/blender/editors/space_file/filelist.c:1472\n - 16 0x55cd8a24591e in Task::operator()() const /src/blender/source/blender/blenlib/intern/task_pool.cc:178\n - 17 0x55cd8a24a288 in tbb::internal::function_task<Task>::execute() /usr/include/tbb/task.h:1059\n #18 0x55cd83a89424 in tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) (/src/cmake_debug/bin/blender+0x12db9424)\n```\n", "UI: Image/UV Editor\nThe UI of the Image and UV Editor can be improved.\n\n* Move smooth edges option to user pref\n* Move overlays to an overlay popover\n\n\n\n\n* Move display settings to a popover\n* Change the Pixel Coordinates toggle into an enum to choose between Pixels or Normalized\n\n\n* Slightly re-arrange the header:\n\n* Move th UV Vertex panel away from the Image Sidebar category and into Item, and include Coordinates option here too:\n\n", "VSE's selection not centred to images\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.5058\n\nBroken: version: 3.1.0 Alpha\nWorked: Never\n\nWhen zooming in enough to a selected image's corner, it can be seen that the selection box (white rectangle) reaches outside the image itself. It also happens with a scaled down \"color\" strip.\n\n- Open a \"Video Editing\" workspace and add a \"Color\" strip\n- Scale it down and zoom to a corner\n- To better notice the issue, play with the resolution of the Preview (in Properties)\n\n\nNotes & thoughts:\n- The selection box (white box) is unresponsive to \"aspect ratio\" changes (in Properties)\n- The drifting of the image is somewhat annoying, and sticking the selection box to the image wouldn't fix this.\nSince I don't know how pixel alignment works in the preview, I'm not sure about this, but it may work to instead drift the canvas, leaving the image put like the selection box currently does. So sticking the image TO the selection box.", "Clicking on Driven decorator should open the Edit Driver popup\nIt would be nice if single-click on the driver icon would open the edit driver popover and double-clicking open driver editor. \n\nIn the keyframe icons by double clicking you could open in floating window the curve editor would be good, or ctrl + left click.\n\n\n\n", "Can't display .blend thumbnail in the Windows explorer\nwindows 7 64 bit\n\nBroken: blender 2.75a c27589e\n\nCan't display .blend thumbnail in the Windows explorer!\n\nboth v2.75 and 2.75a all can't display .blend thumbnail in the windows explorer! I have install and uninstall again and again ,it's still don't display thumbnail. \n", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "If 'Open Folders on Single Click' is enabled, double-clicking performs 3 clicks\nOperating system: Windows-11 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\n\nWhen option `Open Folders on Single Click` in Preferences>Keymap>File Browser is enabled, double-clicking on a folder will open it and then perform additional double-click on a file that ends up under the mouse cursor. So in total it acts as a single-click + double-click. This is very bad, because this way it's very easy to overwrite a wrong file when saving.\n\n\n- Open the file browser in blender\n- Find a folder that shows a file under a mouse cursor when you open it\n- Double-click on such folder\n\n", "Make saving of `quit.blend` on exit optional\n### Description & Scope of Problem\n\nEvery time Blender quits, when it has something on the undo stack, it will write the current \"undo file\" to `${TEMPDIR}/quit.blend` ([manual](open_save.html#last-session)).\n\nSaving `quit.blend` can take a while when the file is large. While the file is being written, Blender's UI is gray and unresponsive.\n\nThe problem is not pressing, as usually it takes considerably longer to load the files in the first place. I've asked some artists at the Blender Studio and they didn't really consider the delay when quitting Blender a practical issue. Still, it gets somewhat in the way of quickly testing things with various production blend files, so it could be seen as an issue for developers more than for artists.\n\n### Possible Solutions & Impact\n\n**Simplest solution:**\n\nAs a solution we could introduce a user preference \"Save Recovery File\" that is enabled by default. Disabling this option would:\n- Avoid writing `quit.blend`.\n- Remove the \"File ‣ Recover ‣ Last Session\" menu item.\n- Remove the \"Recover Last Session\" button from the splash screen.\n\n**Alternative solution:**\n\nThe \"Recover Last Session\" operator does not poll the filesystem from its poll function. This means that the operator is available even when the file `${TEMPDIR}/quit.blend` does not exist. Changing this, such that the operator is disabled when `quit.blend` does not exists, means that the above solution would not have to remove the recovery operators when \"Save Recovery File\" is disabled. The operators would auto-detect whether a recovery file is available at all.\n\nThe upside of this solution is that it makes the \"Recover Last Session\" operator appear more reliable, as it refuses to work when it knows it cannot do its job. This would be an improvement regardless of the \"Save Recovery File\" status.\n\nThe downside is that an old `quit.blend` might be lingering around after \"Save Recovery File\" has been disabled. This means that it could appear as if you could still recover, but it would load an older file. This could be avoided by removing `quit.blend` when disabling \"Save Recovery File\", but I'm not a big fan of Blender explicitly removing files that are meant to recover from human error.\n\n### Discussion Topics\n\nThis task is meant to discuss the following:\n\n- Do we want to make it possible to quit without writing `quit.blend` at all?\n- If so, which of the solutions is preferred? Or is there another way to deal with this that's even better?\n- Do we want this as a general option, or something that's enabled only when \"Developer Extras\" are enabled?\n", "Rendered object in displayed as a transparent png\nOperating system: Windows-10-10.0.19043\nGraphics card: Radeon AMD Radeon HD 8500M (4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001)\n\nWorked: (3.2.0)\n\nidk if it is even a bug but when i render my object, it shows the object as a transparent png. how do i fix it?\n\n[donut.blend](donut.blend)" ]

[ "Blend file thumbnail shows the file browser\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nWhen using the full screen file browser preference and saving a blend file, the thumbnail shows the file browser\n\n\n\nSet file browser to Maximized Area\n\nSave a file\nCheck the thumbnail\n\n" ]

[ "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n", "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n", "Objects with \"In Front\" don't appear when overlays are reenabled until viewport update\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.73.01\n\nBut works on:\nOperating system: Linux-5.10.0-6-amd64-x86_64-with-glibc2.31 64 Bits (Debian testing)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (WHL GT2) Intel 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.91.2\n\nMight be the same as #102199 (Regression: Armatures [in front] overlay doesn't update properly (toggling overlay ON and OFF)) (which was bisected down to 0f95f51361)\n\nWhen an object (specific ones) is set to be displayed in front of everything else, it will not come back immediately when reenabling the overlays. This happens only in solid shading mode as far as I can tell.\n\nThe objects affected by this are first off all objects which have some kind of lines, so camera, lights, the wireframes of meshes, outlines of reference images, empties, ...\nThen there is also the armature which is special in the way that it is rendered solid, but it also vanishes just like the lines.\n\n1. Add an armature\n2. set it to In Front in Armature > Viewport Display\n3. toggle the viewport overlays on and off (that button next to x-ray)\n4. if your rendering was set to solid shading, the armature should be gone now\n5. rotate the view, the armature will reappear\n6. you can do the same with the default camera and light and on the cube if wireframes are enabled (globally or locally on the cube) \n\n", "File Browser resort and select at the same time\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nWhen opening any file browser and you click between the first listed file or folder and then area to change the order by name you change the order and select the file/folder right after that even though you clicked only once.\n\n1. Go to any file browser, for example File > Save\n2. Navigate to any directory where at least 1 file or folder is listed\n3. Move the cursor to the point between the listed file/folder and the area above to change the listing order and click\n4. You will with only one click, change the listing order and after that select the first listed item\n\n[2022-02-11 10-15-59.mp4](2022-02-11_10-15-59.mp4) ", "Basic File Browser UI/UX reiteration\n**This topic requires better focus to be discussed.** Some aspects of the proposal (\"Setting\" status) can be looked at separately, while the rest of the proposal needs better communication and broader consensus to move forward. Keeping the original text for a later iteration.\n\n> Original text:\n> After investigating the updated File Browser functionality in Blender 2.8, a few changes should be introduced:\n> ~~- [ ] [D12667](D12667): Restore single-click navigation of folders (selection is possible with right-click) in the Blender keymap. The industry compatible keymap can keep double click.~~\n> ~~- [ ] [D12668](D12668): Move file name field under file path field (as in 2.7)~~\n> - [ ] Save the status of the \"Settings\" region across sessions\n> ~~- [ ] Re-introduce parent folder `..` navigation. Allows for fast file browsing (no need to switch context between files list and navigation menus)~~\n> The goal of these changes is to allow for faster and more focused interaction with files. Artists often browse through hundreds of files and folders everyday and having a more compact and responsive interface helps.", "File browser: filename not updated immediately after rename\nOperating system: Linux-5.15.21-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.15.21-1-MANJARO, LLVM 13.0.0) AMD 4.5 (Core Profile) Mesa 21.3.5\n\nBroken: version: 3.0.1, 3.2.0 Alpha\nWorked: -\n\nOpening renamed files does not work if you click \"Open\" in the file browser immediately after renaming.\n\nLet's assume there is a file A.blend\nOpen Blender's file browser, right-click A.blend and rename it to B.blend.\nPress Enter to confirm your changes, then click \"Open\"\nBlender now tries to open a file with the old name A.blend and can't find it anymore, so it shows an error message:\n\"Report: Error\nCannot read file '/yourpath/A.blend': No such file or directory\"\n\nThe renamed file will open:\n- if instead of clicking \"Open\" the renamed file is double-clicked.\n- after selecting a different file and then selecting the renamed file again (now \"Open\" works).\n- after clicking refresh/changing to a different directory and back.\n\nChanging display mode or clicking in the search field before clicking \"Open\" does not help.\n", "Asset Browser preview generation not updating untill hovering over Preview menu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\n\nWhen trying to generate an asset preview using `Render Active Object` the preview **won't display** until hovering over the `Preview` menu.\n\nOpen `Blender` -> Open `Asset Browser` -> Mark any **object** as asset -> Open `Asset Details` -> In the `Preview` Menu you will find `Render Active Object Button`\n\n[2022-12-08 21-59-59.mp4](2022-12-08_21-59-59.mp4)", "Scene strips don't include passes\nOperating system: Linux-5.8.11-1-MANJARO-x86_64-with-glibc2.32 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.11-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.8\n\nBroken: from 2.79 to version: 2.92.0 Alpha\nWorked: -\n\nThe render passes of another scene (as scene strip) are ignored in the master scene.\nThis will most probably be categorized as limitation. Since it is a severe one, it should at least be documented here:\nPagename: `video_editing/sequencer/strips/scene`\n\nName current scene \"A\", create new scene, in the sequencer add scene strip for \"A\", hit F12\nThe content of scene \"A\" will be rendered, but the Z channel (enabled by default / other channels if activated) of scene \"A\" will not be rendered, the Select Pass dropdown is not there and the layers are not saved to multilayerEXR.\n\n", "Crash choice asset library\nOperating system: Win 10\nGraphics card: RX460 2gb\n\nBroken: (3.2)\nWorked: (3.0)\n\n[Tests.zip](Tests.zip)\n\n- Extract archive and add `...\\Tests\\Test Asset\\` path to asset libraries\n- Open Asset library blend file\n- Open New file\n- Change any editor to Asset Browser\n# List contents of `Test Asset` library\n\nIt should crash.\nSometimes, omitting step 2 would prevent crash, but no assets would be shown.\nAlso omitting `tests` folder somehow prevented the crash, \n\nCrash log:\n[P3143: (An Untitled Masterwork)](P3143.txt)\n```\n# Blender 3.4.0, Commit date: 2022-08-14 18:40, Hash 659b63751d63\nbpy.context.space_data.params.asset_library_ref = 'Test Asset' # Property\n\n# backtrace\nException Record:\n\nExceptionCode : UNKNOWN EXCEPTION\nException Address : 0x00007FFF3F66D759\nException Module : KERNELBASE.dll\nException Flags : 0x00000001\nException Parameters : 0x4\n\tParameters- [x] : 0x0000000019930520\n\tParameters- [x] : 0x000000FB7C5FD460\n\tParameters- [x] : 0x00007FF678278398\n\tParameters- [x] : 0x00007FF66CA80000\n\n\nStack trace:\nKERNELBASE.dll :0x00007FFF3F66D6F0 RaiseException\nVCRUNTIME140.dll :0x00007FFF283E63F0 CxxThrowException\nblender.exe :0x00007FF672BC42D0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC39A0 nlohmann::detail::serializer<nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_stri\nblender.exe :0x00007FF672BC36C0 nlohmann::basic_json<nlohmann::ordered_map,std::vector,std::basic_string<char,std::char_traits<char\nblender.exe :0x00007FF672BC82B0 blender::io::serialize::JsonFormatter::serialize\nblender.exe :0x00007FF66E27B970 blender::ed::asset::index::AssetIndexFile::write_contents\nblender.exe :0x00007FF66E277D40 blender::ed::asset::index::update_index\nblender.exe :0x00007FF66E653B90 filelist_readjob_list_lib\nblender.exe :0x00007FF66E654370 filelist_readjob_recursive_dir_add_items\nblender.exe :0x00007FF66E653710 filelist_readjob_asset_library\nblender.exe :0x00007FF66DB341A0 do_job_thread\nblender.exe :0x00007FF672E5A810 _ptw32_threadStart\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThreads:\nThread : 00000448\nntdll.dll :0x00007FFF41D2C620 ZwDelayExecution\nblender.exe :0x00007FF672B3A220 BLI_thread_is_main\n\n\nThread : 000069ac\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003130\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069cc\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000054bc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000026c0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008788\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000aa4c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000608c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009c7c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008d78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029c4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009918\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000162c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001478\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a78\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000040b4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000036d0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003468\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007444\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005208\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000059e4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a018\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000085a8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b1ac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000921c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005544\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ad94\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000067e0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000401c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b360\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008b38\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005884\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003334\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nblender.exe :0x00007FF673904E60 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF673904670 IlmThread_3_1::ThreadPool::numThreads\nblender.exe :0x00007FF66CDB3A50 std::thread::_Invoke<std::tuple<void (__cdecl usdBlender__pxrReserved__::HdRenderThread::*)(void) _\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008c60\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a2e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nnvoglv64.dll :0x00007FFE819D057C Symbols not available\n\n\nThread : 00009be0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFF3F690C30 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nnvoglv64.dll :0x00007FFE81C6EF90 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003f9c\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFE81C3A540 DrvValidateVersion\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007978\nntdll.dll :0x00007FFF41D2F9F0 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFF41CA0E20 LdrAccessResource\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ace0\nntdll.dll :0x00007FFF41D2CAF0 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFF3F690C50 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\ncombase.dll :0x00007FFF41539AA0 RoGetServerActivatableClasses\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000ada4\nwin32u.dll :0x00007FFF3FCCA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFF411906F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFF3012457B Symbols not available\n\n\nThread : 00009dbc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005f9c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009dac\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000405c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000834c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000099e8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00006284\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005ec8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000a8fc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00003240\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00000a10\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000082dc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000196c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004374\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00007dec\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004294\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000559c\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009a90\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004cc8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000029cc\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000055f8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000069a4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00005c40\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00001a80\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004308\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000081c8\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 000071a0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 0000b0d4\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00004bc0\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00009d28\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nThread : 00008010\nntdll.dll :0x00007FFF41D2C020 ZwWaitForSingleObject\nKERNELBASE.dll :0x00007FFF3F65A2C0 WaitForSingleObjectEx\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFF1D64D800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFF3F931430 configthreadlocale\nKERNEL32.DLL :0x00007FFF40637020 BaseThreadInitThunk\nntdll.dll :0x00007FFF41CDD0B0 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF66CA80000 3.4.0.0 blender.exe C:\\Users\\John\\Desktop\\blender-3.4.0-alpha+master.659b63751d63-windows.amd64-release\\blender.pdb \n0x00007FFF41C90000 10.0.19041.662 ntdll.dll \n0x00007FFF40620000 10.0.19041.662 KERNEL32.DLL \n0x00007FFF3F640000 10.0.19041.662 KERNELBASE.dll \n0x00007FFF40C70000 10.0.19041.546 WS2_32.dll \n0x00007FFF41310000 10.0.19041.662 RPCRT4.dll \n0x00007FFF41170000 10.0.19041.685 USER32.dll \n0x00007FFF1D640000 tbb.dll \n0x00007FFF3FCC0000 10.0.19041.662 win32u.dll \n0x00007FFF41940000 10.0.19041.685 GDI32.dll \n0x00007FFF1D600000 tbbmalloc.dll \n0x00007FFF3FAB0000 10.0.19041.685 gdi32full.dll \n0x00007FFF3FA10000 10.0.19041.546 msvcp_win.dll \n0x00007FFF3F910000 10.0.19041.546 ucrtbase.dll \n0x00007FFF417D0000 10.0.19041.610 ADVAPI32.dll \n0x00007FFF406E0000 7.0.19041.546 msvcrt.dll \n0x00007FFF41980000 10.0.19041.662 sechost.dll \n0x00007FFF3FED0000 10.0.19041.662 SHELL32.dll \n0x00007FFF283E0000 14.29.30139.0 VCRUNTIME140.dll \n0x00007FFF3AE70000 14.29.30139.0 VCRUNTIME140_1.dll \n0x00007FFF40F00000 10.0.19041.546 SHLWAPI.dll \n0x00007FFEC90D0000 14.29.30139.0 MSVCP140.dll \n0x00007FFF3FC70000 10.0.19041.546 CFGMGR32.dll \n0x00007FFF36DA0000 10.0.19041.488 dbghelp.dll \n0x00007FFF3FBC0000 10.0.19041.662 bcrypt.dll \n0x00007FFF40CE0000 10.0.19041.546 ole32.dll \n0x00007FFF41470000 10.0.19041.662 combase.dll \n0x00007FFEC8180000 10.0.19041.546 OPENGL32.dll \n0x00007FFF41440000 10.0.19041.546 PSAPI.DLL \n0x00007FFF41A20000 10.0.19041.662 shcore.dll \n0x00007FFF3FEA0000 10.0.19041.546 IMM32.dll \n0x00007FFEB74B0000 9.0.0.0 openvdb.dll \n0x00007FFEC5BE0000 59.16.100.0 avformat-59.dll \n0x00007FFEB4FB0000 59.18.100.0 avcodec-59.dll \n0x00007FFF1D5D0000 59.4.100.0 avdevice-59.dll \n0x00007FFF40FC0000 10.0.19041.546 OLEAUT32.dll \n0x00007FFEC9030000 6.4.100.0 swscale-6.dll \n0x00007FFEC5A00000 57.17.100.0 avutil-57.dll \n0x0000000070440000 1.0.28.0 libsndfile-1.dll \n0x00007FFEC5190000 1.21.1.0 OpenAL32.dll \n0x000000006ACC0000 libgmp-10.dll \n0x00007FFEC29E0000 2.0.20.0 SDL2.dll \n0x00007FFF39630000 libgmpxx.dll \n0x00007FFEC0D70000 3.10.2150.1013 python310.dll \n0x00007FFF40780000 10.0.19041.546 SETUPAPI.dll \n0x00007FFF300E0000 tbbmalloc_proxy.dll \n0x00007FFF31280000 6.10.19041.488 COMCTL32.dll \n0x00007FFF1C490000 10.0.19041.1 AVIFIL32.dll \n0x00007FFF39120000 10.0.19041.546 VERSION.dll \n0x00007FFF3D210000 10.0.19041.546 dwmapi.dll \n0x00007FFF1C460000 10.0.19041.546 GLU32.dll \n0x0000000070680000 libfftw3-3.dll \n0x00007FFF27EE0000 10.0.19041.546 Secur32.dll \n0x00007FFECB6B0000 4.3.100.0 swresample-4.dll \n0x00007FFECBF00000 10.0.19041.1 AVICAP32.dll \n0x00007FFF2EBF0000 10.0.19041.546 WINMM.dll \n0x00007FFF20660000 10.0.19041.1 MSACM32.dll \n0x00007FFECB5D0000 10.0.19041.1 MSVFW32.dll \n0x00007FFF24F20000 10.0.19041.1 winmmbase.dll \n0x00007FFF3F280000 10.0.19041.662 SSPICLI.DLL \n0x00007FFF3D240000 10.0.19041.546 kernel.appcore.dll \n0x00007FFF3D520000 10.0.19041.662 windows.storage.dll \n0x00007FFF3EE40000 10.0.19041.662 Wldp.dll \n0x00007FFF3CE80000 10.0.19041.610 uxtheme.dll \n0x0000022043090000 10.0.19041.662 bcryptPrimitives.dll \n0x00007FFF3F300000 10.0.19041.546 profapi.dll \n0x00007FFF41880000 2001.12.10941.16384 clbcatq.dll \n0x00007FFF38BE0000 10.0.19041.546 MMDevApi.dll \n0x00007FFF3F180000 10.0.19041.546 DEVOBJ.dll \n0x00007FFF38EF0000 10.0.19041.662 AUDIOSES.DLL \n0x00007FFF3E980000 10.0.19041.546 powrprof.dll \n0x00007FFF3E840000 UMPDC.dll \n0x00007FFF41AD0000 10.0.19041.662 MSCTF.dll \n0x00007FFF39850000 10.0.19041.662 AppXDeploymentClient.dll \n0x00007FFE80E80000 31.0.15.1640 nvoglv64.dll \n0x00007FFF3AE30000 10.0.19041.546 \n```\n\n\n - The conditions have been changed, but the error is still present. -----------------------------------------------------------", "Grid doesnt show\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Masks overlay not visible with Mirror Modifier\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.5.0 Alpha\nWorked: Unclear. Tested all the way back until 3.1\n\nThe mask overlay is regularly disappearing when using modifiers. The most reliable to reproduce this issue is the Mirror modifier.\n\n- Add an object with a mirror modifier\n- Duplicate the object\n- Enter sculpt mode on one of the objects and create a mask\n- Exit sculpt mode, select the other object, then the primary object again and enter sculpt mode (The mask is no longer visible)\n- Use the shortcut `Alt Q` to switch to another object and switch back (The mask should now be visible)\n- Or disable the modifier and the mask should appear.", "Design issue: Icon next to overridden property does not perform the function it strongly suggests\n3.0.0\n\nWhen a propertry is overridden, the \"animate property\" button next to it is replaced by this \"reset\" icon:\n\nThese really seem to suggest that clicking them will remove the override. Instead it just adds a keyframe as usual. This seems misleading.\n\n - Override a property of some library override asset\n - Click the button to the right of that property\n\n", "Importing multilayer EXRs into compositor with animated view layers creates unexpected results.\nOperating system: Linux-4.4.0-161-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nAll passes connected to my main View layer disappear when what was a View layer with an animated \"Use for rendering\" attribute, appears. \n\nBasically I in my original scene I created a \"main\" view layer, with several passes attached, and a \"secondary\" view layer, also with several passes attached. This \"secondary\" layer had its \"use for rendering\" attribute so that it would appear on frame 41 of 210.\n\nThe render went fine and opening these files in Nuke, with a layercontactsheet node attached, I see the \"main\" layer, with all its associated passes, and after frame 41, I see the additional \"secondary\" layer and all it's passes as well.\n\nHowever, with a new scene in Blender the following happens;\nIn the compositor, add an image input and select the multilayer EXRs.\nAttach a viewer to the main image output and select the \"main\" layer on the image node.\nAll the passes sockets are visible on the image node, until I scrub to frame 41, where the \"main\" layer enumerator changes to the \"secondary\" one and all sockets are visible still for all passes. But, if I change back to the \"main\" layer, I see it, but with only an image and alpha socket. All additional pass sockets have disappeared.\n\nWithout speculating, it feels like Blender, is having a trouble when an additional layer with passes suddenly appears in a sequence.\n\n[#69898.zip](T69898.zip)", "Image Editor: Viewing a value buffer could use incorrect channel selector\nThis is a long outstanding issue in the image editor that should be fixed.\nWhen rendering a value based AOV and switching in the render result to the AOV would render incorrect as the wrong channel selector is selected (Still Color + Alpha).\n\nThis is also visible when reading single channel images or OpenEXR files.\n\n**Solution**\nAdd an option to view `Value` option to the channel selector and change RNA get/set/itemf + add support of this to the image engine.", "Support Scenes Overrides\nCurrently Scenes liboverrides are not really working, changes to its master collection will be lost, resync of scene itself is not possible when the override is the active scene, etc.\n\nSee e.g. #89963 (crash when library override is applied to an object)" ]

[ "Asset Browser doesn't show assets when drop-down set to \"All\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.5 stable version!\nWorked: This feature is new as of 3.5 and I'm seeing the behavior in both. \n\nAssets from other files are not visible when asset browser preference is set to \"All\" (when assets are part of catalogs)\n\n- Extract uploaded file\n - Open general blend file\n- Set it as asset library path\n- Open asset browser and set preference to \"All' [notice every asset is visible (i.e. engine parts and sculpted sphere)\n- Now open `open-file.blend`\n- In asset browser, set preference to \"All\" (notice engine assets are missing)\nIf switched to \"user library\" then engine assets are visible\n" ]

[ "Low hair children and viewport display numbers cause hair to be excluded from parts of the mesh \n**System Information:**\nOperating system: Windows 10 and Linux (both show issues)\nGraphics card: RTX 2060 SUPER (452.06 Windows) (450.66 Linux)\n\n**Blender Version:**\nBroken: 2.79, 2.80, 2.81, 2.82, 2.83, 2.90, 2.91.0 Alpha\nWorked: Not sure\n\n**Short description of error:**\nWhen an object with a hair particle system has the `Viewport display` percentage set to a low amount and the `Hair Children viewport display` option set low, hair is excluded from parts of the mesh. Here's a video demonstrating the issue:\n[0029-1590.mp4](0029-1590.mp4)\n\n**Exact steps for others to reproduce the error:**\n1. Obtain a object with a high number of faces (I used a cude subdivided 5 times)\n2. Give the object hair particle system and increase the hair count to something like 10,000 or 100,000 to make the effect more apparent.\n3. In the hair particle settings scroll down to the `Viewport display` section and change the `Amount` slider to a low percentage (E.G. 2% or 5%)\n4. Notice how there are hairs distrobuted across the entire mesh.\n5. In the `Children` tab of the hair particle settings tab, enable one of the options `Simple` or `Interpolated`.\n6. Notice how the hair is now only distrobuted over part of the object rather than the entire object. As you increase the `Viewport display - > Amount` value and/or the `Viewport display number` for the children, this issue goes away.\n\nHere's a .blend file show casing the issue: [#81117 - Hair excluded from parts of a mesh.blend](T81117_-_Hair_excluded_from_parts_of_a_mesh.blend)", "\"Set normal from faces\" operator does not work in a sensible way, needs decision on what is expected behavior here.\nReading current code of that operator, it's not making much sense…\n\n - It computes some averaged vertex normals out of select faces' normals only (without even complying to our generic, weighted computation for that).\n - It then does two different loops (over selected verts of edges of faces first, then over loops of verts), to set some custom normals to those weirdly averaged vertex normals computed at step 1.\n\nI think what it is supposed to/trying to do here is actually the following:\n\n # For each clnor fan (i.e. set of contiguous faces around a given vertex, delimited by sharp edges, that share the same custom normal), properly compute the averaged normal from **selected** faces, and set it.\n\nThis will give predictable results, when a single face is selected for each custom normal it will just set to that face's normal, same in case all edges are sharp… And the 'keep sharp edges' option is not needed anymore, I do not see the reason for that one anyway, if you do not want a sharp edge, just do not tag it as such. ;)\n\n-----------------\nOriginal Report\n-----------------\n\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\n[I can not use set normals from faces when selecting a specific face. When I split normals/make em sharp I expect that I can control specific face normal without it interfering with the other normals, this is at least how you do it in all other 3d packages]\n\n[Split/ make all edges sharp, select all vertexes, go to mesh/normal/rotate to make all normals crazy. Now try to set the normals from one of the faces.[Normals.blend](Normals.blend) ]\n\n", "Geometry Nodes: Modifier input properties don't cause update for screen statistic\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nModifier input properties of geometry node don't cause update for screen statistic.\n\n1. Create object with geometry nodes.\n2. Add any Mesh Primitive node in modifier node tree.\nPut mesh primitive on group output. Updating the detail of a primitive affects the statistics of the scene.\n3. Put group input dummy socket in detail of a primitive node to create connection.\nChanging the details through the modifier settings is not reflected in the statistics.\n", "Add error message feedback on constraints, similar to what already exists for modifiers.\nCurrently de-activated constraints only show their status through a small red icon. It would be better for users to also show an error message explaining what is the issue, similar to what modifiers already do.\n\nSee e.g. the invalid settings for the IK constraint of the first bone in this file from #100128: [lib.blend](lib.blend)", "Particle system baking messes particle dietime (that in turn messes up particle textures)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.5.0\n\nIf texture with color ramp is used for animating particle size through lifetime, in ~10 last frames of simulation all particles PERMANENTLY getting smaller until totally disappear lol, and it occurs only if using BAKE.\nthis is not animation, this is 100% bug, looks like particle size animation is applied to WHOLE particle system respectively/relatively to all scene timeline, and is overriding every single particle age at the end of timeline.\n\nFile uploaded.\nParticle systems in blender are SOOOO broken, the way how it works is so facepalmable, particularly \"bake\" and \"textures\".\nlooks like in my case they met lol\n", "Adjust modifier values when using \"Apply scale\"\nThis feature request was discussed with Campbell Barton during meeting 2021-02-23\n\nWhen using \"Apply scale\", the modifier values are not adjusted if the object scale is not [1,1,1]. I would like to suggest that the operator \"Apply scale\" iterates through all modifiers of the selected objects and adjusts all values related to scale\n\nFor example\nBevel modifier - Amount\nDisplace - Strength\nData transfer - max distance, ray radius\nUV project - Scale X, Scale Y, \netc\n\n---\n\nCurrent behaviour\n{[F9849514](image.png), height = 700}\n\n---\n\nDesired behaviour\n{[F9849529](image.png), height = 700}\n\n---\n\nsuggested Operator mockup\n\n{[F9852183](image.png), height = 300}", "Dynamic vertex groups (Dynamic Paint, Weight Proximity modifier, Geometry Nodes, ...) do not update density of particles in viewport display\nOperating system: windows 10\nGraphics card: Quadro M620\n\nBroken: 2.90\nWorked: Never\n\nI want to use my dynamic vertex group to generate particles on a plane.\nIt just works when I change parameters during the playback but it's not realtime when I hit play.\n\n- Open attached file\n- Play animation\n- Change any property of the particle during the playback\n[dynamic_paint_test.blend](dynamic_paint_test.blend)", "Setting/editing keyframes on multiple characters in pose mode doesn't work for Whole Character and Whole Character(selected Bones Only) options.\nOperating system: Windows 10 Home Edition\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0 Master Build\nWorked: never\n\nSetting/editing keyframes on multiple characters in pose mode at the same time only affects the Active Character's Keys on certain insert key options.\nIdeally the insert key options work consistently for all selected characters bones.\n\n - Add two character skeletons to a new scene (Shift+a > Armature > single bone)\n - Select the first bone then Shift+Select the second one.\n - Switch to pose mode\n - hit \"a\" to select all. You should have both bones highlighted\n # hit \"i\" to insert a keyframe.\n - # if you choose Whole Character or Whole character \"Selected bones only\" it will only set a key on the bones for the Active Character.\n - # if you choose any other option it sets keys on both characters.\n\n\n\n\n\n\n**Additional comments:**\nIdeally Whole character would key all characters currently in pose mode.\nand Whole Character (Select bones only) would Key any currently selected bones regardless of which character they belong to.\n\nThe current functionality is confusing, if it is intended, the label should read \"Active Character\" and \"Active Character(selected Bones only)\"\n\nHowever when a user chooses to have multiple characters in pose mode it is because they are trying to pose and key them at the same time without having to switch back and forth with every adjustment. So having the ability to key multiple whole characters, or a random selection of bones belonging to multiple characters would be useful.\n\nThat said keying rotation/translation/scale&custom properties gets me what I need so this is not a blocker but it is something that could be improved for clarity as it will frustrate many animators unaware of this inconsistent behavior for the last two options.\nI was relying on \"Whole character\" and \"whole character (Selected bones only)\" to essentially key everything until I had to do multiple characters and I got confused for a while why my animations were looking janky until a dug into it.", "'Reset to Default Value' sets any property on a node to 0\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.82 (sub 7)\nWorked: Never\n\nIn shader editor gamma default is 1 when I do the hover over setting and press backspace to reset the default it goes to 0.0\nSame with hue/saturation/value.. and probably more.\nThe one with hue is pretty annoying as it has specific default settings .\nSame deal with groups - I set the defaults, it doesn't default .. goes to 0\n\n- in any node editor hover over any setting and press backspace to reset to default value.\nIt defaults to 0 instead of 1 or whatever it's default was in shader editor..\n\n", "Colorpicker: Hue is not saved if Saturation is on 0\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.0.0 Alpha\n\nThis is an interesting papercut I noticed a lot. When you start changing the hue of a color but the saturation is on 0, it won't remember that hue if you close and reopen the color picker.\nThis can be annoying at times, especially when using the Square (SV + H) color picker layout.\nMy guess is that this is because the values that are actually stored for the color are the RGB values and not the HSV values.\nSo if a color is (0.5, 0.5, 0.5) and you change the hue, it is meaningless.\nBut perhaps this can still be improved since other painting applications are actually saving the HSV values and artists would expect Blender to remember what Hue is chosen even if the color is essentially grey.\n\nThis can be easily shown by changing the hue on a color with 0 saturation. The 2 hue sliders are of course not actually changing the color but they are also disconnected and not remembered.\nBut once there is a bit of saturation this is fixed.\n\n[2021-05-13 18-50-05.mp4](2021-05-13_18-50-05.mp4)", "Bug: Extrude faces along normals + \"Individual origins\" pivot point\nOperating system: Windows 10 64-bit\nGraphics card: NVIDIA Geforce GTX 960M\n\nBroken: 2.80 957b4547aeeb 2019-01-28 22:11\nWorked: Set the piviot point option to anything else, such as bounding box center, 3D cursor, etc.\n\nWith pivot point set to **individual origins**, the tool **Extrude faces along normals** don't work properly. It just acts like the **extrude** tool.\n\nVery simple. open the startup file with a cube, set the pivot point to **individual origins** and use **extrude faces along normals**(Alt+E) inside the edit mode.", "Kill Particles does not make them really dead\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 2.93.6\nWorked: -\n\nIf you give a mesh a physics property of collision and check the \"Kill Particles\" Checkbox, they are not becoming dead, they just stop moving. If you add a Particle Instance to another object and only show dead, the dead objects show correctly in viewport but not in render (eevee/cycles).\n\nI created a plane, put it about 10m higher and turned it 180° on x axis. Then i added a particle system to that plane with default settings. I added another plane and scaled it up a few times and applied all transforms. I then added a collision physics property with \"Kill Particles\" enabled to that plan. Now i added an Icosphere, scaled it down, applied all transforms and added the Particle Instance modifier. As Object i chose the first created plane and only left show dead active. After baking the Particle system, you see in viewport the Icosphere as soon as the particles hit the Plane with the collison physics property. But if you then want to render the image they are gone.\n\nWith the attached .blend file you just have to click bake in the particle system properties of the ParticleEmitter object and you should see the dead ParticleInstance object at Frame 40. But if you render the image then they are gone.[ParticlesNotDead.blend](ParticlesNotDead.blend)", "Texture paint Backface culling option does not work if symmetry is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.1\nWorked: never since implemented in e2d60d180ed8 afaict\n\nWhile in the texture paint mode, the backface culling option of the brush is sometimes ignored, allowing painting onto backfaces. It only seems to affect certain objects. I could not discern why. See the attached blend file.\n\n1. Open attached blend file.\n2. Paint on the backfaces of the mesh; observe bug.\n3. Select cube\n4. Paint on the backfaces of the cube; observe no bug.\n\n", "Smooth shading usabilty\nWhen adding a mesh primitive in Blender, it is by default flat-shaded without subdivision surfaces. This means that after adding a new object with a smooth surface (like a sphere or monkey mesh), the user almost always has to change some settings.\n\nWe could change the default mesh settings to avoid that. However there are two distinct use cases which require different settings.\n\n* Meshes with autosmooth and/or custom normals. This could be either a low poly model for games, or a high poly model imported from CAD software.\n* Subdivision surfaces with creases to define sharp areas of the model. Custom normals are lost in the subdivision process, and autosmooth can't be combined with GPU acceleration.\n\nOnce subdivision surface settings become part of the mesh (#68891 (Subdivision surface settings part of the Mesh)), we could handle these as more distinct cases in the user interface and implementation.\n* If a mesh is a subdivision surface, no autosmooth or custom normals would be available.\n* Subdivision surface mesh primitives could be in a separate submenu of the Add menu, with all faces smooth shaded by default.\n* Mesh primitives could have smooth shaded faces and autosmooth enabled by default when it makes sense.\n\nEnabling autosmooth by default will negatively impact performance, particularly in edit mode. It's not obvious this is something we want to do. Further optimizations in this area are possible, but there will always be a cost.", "Objects referenced in the `UVProject` modifier property are not snapped\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.90 (sub 0)\n\nWhen i select an object as projector transform in the UVProject modifier it doesn't snap to the object I added the modifier to.\n\n- add cube\n- add an empty\n- add uvproject modifier to the cube\n- set the empty as projector transform\n- enable snaping to surface\nor\n- open attached file\nWhen moving the empty it does not snap to the cube\n[bug.blend](bug.blend)" ]

[ "Face count decimate modifier not work\ni5 16gb ram\nrenderer:\t'GeForce GTX 970/PCIe/SSE2'\nvendor:\t\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 416.16'\n\nversion: 2.80 (sub 30), branch: blender2.8, commit date: 2018-11-07 23:10, hash: a421cfa8d31, type: Release\nbuild date: 07/11/2018, 17:03\nplatform: Windows\n\nthe Face count of decimate modifier not work\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Handle Type selector in the Graph Editor's sidebar sets different types than selected\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.40\n\nBroken: version: 3.3.0\nWorked: Don't know if it ever worked before or when.\n\nWhen choosing the type of handle for a keyframe in the Graph Editor's sidebar, the options don't work as expected. Selecting \"Vector\" sets the handle to \"Free\", and selecting \"Automatic\" or \"Auto Clamped\" sets it to \"Aligned\".\n\nNot sure if this is expected behavior, but choosing an option to get a different one be set felt weird. Most of all, I couldn't set it as Vector from there, so I had to press V in the Graph Editor and do it from there. Interestingly, then it appears as \"Vector\" in the sidebar as well.\n\nI'm attaching a screenshot of the menu I refer to, and a .blend prepared to reproduce the issue (any file with an animation would do).\n\n\n\n1. Create an animation (already present in the attached .blend file)\n2. Open a Graph Editor\n3. Select a keyframe\n4. Open the Graph Editor's sidebar\n5. Try to change the handle type options in the F-Curve tab of the sidebar\n\n[Handles Issue.blend](Handles_Issue.blend)\n\n", "Texture Node Editor defaults to empty value\nOperating system: Linux-4.19.33_1-x86_64-with-glibc2.9 64 Bits\nGraphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\n\nBroken: version: 2.80 (sub 54)\nWorked: (optional)\n\n\nWhen switching to the texture node editor, it defaults to an empty texture type.\nAdditionally, the \"World\" texture type is missing the texture selection list at the top, so no texture can be manipulated or created.\n\n- Switch window to Texture Node Editor > No Type is selected\n- Switch to \"World\" Texture type, texture selection and creation is missing in the header\n", "Blender Mantaflow gas fire and smoke simulation - Adaptive Domain problem!\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\nTHE SAME BEHAVIOUR FOR Blender versions 3.3.1 and 3.4.1.\n\nAdaptive Domain from time to time shrinks as intended, but those shrinks are sometimes visible.\n\n\n- Open [file](https://projects.blender.orgattachment)\n- Bake 180 frames\n- Check frames 173 - 178\n\nDomain shrinks while space is occupied by smoke with substantial density", "Object.display_type \"Solid\" behaves the same as \"Textured\"\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.8.1 26.20.13001.29010\n\nBroken: version: 2.81 (sub 12)\nWorked: 2.79b\n\nIn a viewport set to \"Textured\" mode (either on Cycles or Eevee), setting Object.display_type = \"SOLID\" still shows a textured object.\nOn Blender 2.79 this property was called \"Maximum Draw Type\" and was behaving as expected.\n\n1.-Set the viewport to Textured mode.\n2.-Select a textured object and set its property \"Display As\" to Solid.\nIt will stil be shown as Textured so theres no difference between the two modes (Solid, Textured)\n\nBlender 2.81\n\n\nBlender 2.79b\n\n\nExample blend.\nThe viewport is set to \"Textured\", the monkey set to \"Solid\" but is shown as Textured.\n[solid_object_display_type.blend](solid_object_display_type.blend)\n", "Cycles Render: Volume (Before Baked Simulation Starts) still trying to be rendered\nOperating system:windows 11\nGraphics card:nvidia geforce rtx 2060\n\nBroken: 3.4.1\n\nThe cycles render tries to use the volume cache to render if the frame is less than the start of the simulation. See video example.\n\n1. Default cube: Add Quick Smoke.\n2. Cache settings:\n a. Type: All.\n3. Start frame: 50, end: 100.\n4. Bake.\n5. Start render on 30~ frames.\nExpected: Simulation chunks will appear in different parts of the domain.", "Cache-folder name makes fluid simulation not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 20.1.3 26.20.15015.1007\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nCache-folder name makes fluid simulation not working. My blend file (with fluid cache data) was in a folder named badeværelse and the fluid sim didn't work. Changed the folders name to badevaerelse and it worked.\n\nMake folder called \"æ\" (possibly \"ø\" and \"å\" too)\nMake a blend file inside it and try to bake liquid sim and use the folder as cache directory for the fluid physics\nSee how no particles appear when you press bake\n\n", "Mantaflow simulation stops and crashes at the end of the bake (or when closing blender): The CG solver diverged, residual norm > 1e30, stopping.\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nCrash baking fluid simulation.\n\n\nOpen the file and bake all its frames (or only frame 181 to 183).\n\n[beach.blend](beach.blend)\n\n```\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 169, in bake_fluid_data_5\n File \"<string>\", line 164, in bake_fluid_process_data_5\n File \"<string>\", line 136, in liquid_adaptive_step_5\n File \"<string>\", line 221, in liquid_step_5\nRuntimeError: GridCg::iterate: The CG solver diverged, residual norm > 1e30, stopping.\nError raised in extern/mantaflow/preprocessed/conjugategrad.cpp:562\n(...)\nterminate called after throwing an instance of 'Manta::Error'\n what(): can't clean grid cache, some grids are still in use\nError raised in extern/mantaflow/preprocessed/fluidsolver.cpp:33\nAborted (core dumped)\n```\n\nComplete output: [P2568](P2568.txt)", "Particle Angular velocity doesn't work\nOperating system: Darwin-19.3.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.5.5\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nRotation > Angular velocity section of particle system settings doesn't rotate particles over time.\n\n\n[#81671.blend](T81671.blend)\n* open attached .blend\n* play animation\n", "Creating Lattice object with script with {\"REGISTER\", \"UNDO\"} if parameters was changed in Undo window and mesh was in Edit mode - undo last changes to the mesh or last action\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 2.93.1\n\n{\"REGISTER\", \"UNDO\"} also undo last action if parameters was changed in \"Adjust last action\" pannel and mesh was in Edit mode.\n\n[Register_Undo_Issue.mp4](Register_Undo_Issue.mp4)\n\n[REGISTER_UNDO_in_EDIT_Mode.blend](REGISTER_UNDO_in_EDIT_Mode.blend)\n\n", "Dynamic vertex groups (Dynamic Paint, Weight Proximity modifier, Geometry Nodes, ...) do not update density of particles in viewport display\nOperating system: windows 10\nGraphics card: Quadro M620\n\nBroken: 2.90\nWorked: Never\n\nI want to use my dynamic vertex group to generate particles on a plane.\nIt just works when I change parameters during the playback but it's not realtime when I hit play.\n\n- Open attached file\n- Play animation\n- Change any property of the particle during the playback\n[dynamic_paint_test.blend](dynamic_paint_test.blend)", "Consider using more explicit names instead of the generic 'Size' value for Empties.\nWhen creating an Empty, the pop-up window specifies the `Radius` for the Empty, presumably because the shape chosen could be a sphere, arrows, or any number of different types.\n\nHowever, when viewed in the Object Data Properties, the radius is displayed as a more generic `Size` value.\n\n\n\nThis leads to confusion, especially when comparing an Empty to a Cube. In the example below, the visual scale of these two items is identical, yet looking at their `Size` tells a different story.\n\n\n\nFor context, this came up as a point of confusion for a use case where I'm using non-scaled empties as a 'holder' for position/rotation/scale while applying a set of custom properties to be exported as .glb and used in threejs.\n\nMy suggestion would be to continue the use of `Radius` as the label in the Object Data Properties, instead of `Size` since that's what is actually meant by the value.\n\n", "Mantaflow replay length change doesn't take into account effectors.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83 (sub 15)\n\nWhen you run a mantaflow simulation with replay, then increase the length of the simulation, collision effectors fail\n\nOpen file, Shift + right arrow to go to initial frame and make folder. play to bake till frame 20. (it'll be quick)\nPause, change frame end for baking to something bigger: 50. \nShift + right arrow to go to first frame. Play. After 20th frame, see effector being ignored & fluid rushing in.\n[#76075.blend](T76075.blend)", "Child Of vertex group fails when controled by Particle System\nWin10 64bit\n\nBroken: 2.79\n\nChild Of constraint fails on rotation from PS\n\nOpen file, play animation on every layer\n\nFirst layer: *Empty* with *Child Of* constraint is controled by Plane's transform animation -> works OK\nSecond layer: *Empties* with *Child Of* are controled by Plane's *Particle System* (via *Explode*) -> Location is maintained, but **rotation is non-synchronized**\nThird layer (example of how previous case is expected to work): Empties parented to *3 vertices* are controled by same PS - OK\n[Child_Of_test.blend](Child_Of_test.blend)\n", "Force field + hair dynamics not working in (linked) instanced collections\nOperating system: Windows 10 64 bit\nGraphics card: GeForce GTX 1070\n\nBroken: 2.80 3d8cbb534f82 (2019-01-25)\nWorked: 2.79b release\n\nA surface force field does not affect hair dynamics when it is part of a collection that is linked into another file.\n\nSteps to reproduce:\n1. Create a hair particle system, with hairs along x axis. \n2. Enable hair dynamics on hair\n3. Create a surface force field underneath it.\n4. Press play button to verify hair is affected by force field.\n5. Save file\n6. Link the collection from the first file into another file. (I have 'Instance Collections' turned on)\n7. Press play. hair will fall and not be affected by the force field.\n\nExample blend file attached.\n[hair_force_test.blend](hair_force_test.blend)\n", "Vertex Painting with data type \"Color\": Painting pure Red or Green creating non Zero in Blue Channel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.63\n\nBroken: version: 3.5.0 Alpha\n\n**Short description of error** \nIn Geometry Nodes, I've tried scattering objects with vertex painting (data type \"Color\") using pure red (1,0,0), green (0,1,0) and blue (0,0,1). With a math node set to \"Greater than\", the different color channels are tested whether their values are bigger than 0. However, I discovered that I needed actually a \"Threshold\" value slightly bigger than 0 (I used 0.0001, just below the \"Spreadsheet's\" precision) because my objects for the blue painted areas got also displayed in red and green areas with a \"Threshold\" value of exactly 0 for testing the blue color channel. The red and green channels could be tested with a threshold of exactly 0. \n\nWith vertex painting using the data type \"Byte\", I could also set the blue channel's testing threshold to exactly 0.\n\n**Steps to Reproduce**\n- Open attached file\n- Set Threshold value exact to 0 for blue color channel\n[Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend](Geometry-Nodes_Instancing_with_Vertex-Colors_1Jan2023_7.blend)\n\n" ]

[ "The checkbox for flip fluids is \"fakely\" enabled when the domain is manually created\nBroken: version: 2.82 (sub 6)\nWorked: Never\n\nCreating a fluid simulation, the `Liquid` checkbox visually seems to be enabled. But you must click on it to really enable it.\n\n- Open Blender; save the startup file\n- Default cube: Physics > Fluid > Type: Flow; Flow Type: Liquid\n- Add cube, scale up. Physics > Fluid > Type: Domain; Domain Type: Liquid\n- Hit \"Bake Data\".\n- Looking under Particles (or Modifiers), there won't be any particle system, which I believe is expected.\n- Click the `Liquid` checkbox in the domain.\n- There are the particles." ]

[ "Keyed Particle Physics Incorrectly Rendered Under Eevee and Cycles, but Correctly Rendered in Viewport Render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha\nWorked: Never (2.80+)\n\nCreate two objects. Attach a normal particle system to the first one. Attach a keyed particle system to the second one, with the two relations \"first object\" then \"second object\". Therefore, particles should move from the first object to the second object. If the starting velocities are non-trivial and the keyed particles are generated over three or more frames (e.g., start time 10, end time at least 12) then the particles of the keyed system are correctly rendered in the viewport (rendered mode) but appear in different positions when actually rendering (pressing F12).\n\nI first discovered this with a more complicated example, and the same behaviour occurred under both 2.90 and 2.83 (normal releases). Googling did not turn up anything relevant. (Motion blur is off.)\n\nI have been able to recreate it with a simple .blend file attached. Included are two screenshots at frame 20, one of the viewport, one of the rendered image. While the difference is just one particle here (a red particle is over the left square in the viewport but off the square in the rendered image), vastly different behaviour can be achieved by increasing the difference between start and end times. \n\nIn the more complicated example, not included here, a particle would appear at the top of the screen and move towards its final destination. When rendered though, it would appear in the correct place on that frame but then immediately jump to a very different location on the next frame.\n\nNote: This bug might depend on the first object's particles having a short lifetime - the original motivation is having one object explode then morph into another object. The rendered animation looked very different (and incorrect) from the viewport animation.\n\n[system-info.txt](system-info.txt)\n\n\n\n\n\n\n[Debug 2.blend](Debug_2.blend)\n1) Open it.\n2) Set viewport to Rendered mode.\n3) Move playhead to frame 20.\n4) Observe the locations of the 4 red particles near Plane.001. (They form a loose \"T\" shape and none are touching Plane.001.)\n5) Press F12.\n6) Observe the locations of the 4 red particles near Plane.001 are very different. (Two are touching Plane.001 and the other two are in line ready to arrive at Plane.001.)\n\n", "Add Ico Sphere in edit mode adds misshaped ico sphere if object has shape keys\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\nWorked: (Probably never, I tried a few older versions including Blender 2.79)\n\nWhen an ico sphere is added to an object in edit mode, if it has at least the \"Basis\" shape key the ceated ico sphere is mishaped.\n\n- create a new blender file\n- select the default cube\n- DON'T DELETE IT!\n- add one shape key to get the \"Basis\" shape key\n- go to edit mode\n- Add (Shift A) ▸ Mesh ▸ Ico Sphere\n- in the Add Ico Sphere menu, increase subdivisions to see the mishaped parts better\n\nSee attached video. Without shape keys the ico sphere is flawlsess but with shape keys is misshaped.\n\n", "bake hair dynamics issues\nOperating system: wind 10\nGraphics card: gtx 1070\n\nBroken: blender-2.80-79f67acccb36-win64\nWorked: idk\n\nunable to bake hair dynamics. i click the button but nothing happens. in particle edit mode particle hair still looks as if it was not simulated.\n\n", "Regression: Guiding in manta is broken\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.29\n\nBroken: version: 3.5.0\nWorked: It was working in 3.2.1\n\nIt looks like this was caused by 05952aa94d33eeb504fa63618ba35c2bcc8bd19b\n(there is a bit of uncertainty to this though since with that commit, I dont get mentioned error in the console, bake is broken nonetheless with that commit)\n\nIf you us a smoke domain to guid a liquid you get no result because there is an error in the console that shows that two variables are undefined.\n\n```\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 250, in bake_guiding_166\n File \"<string>\", line 235, in bake_guiding_process_166\nNameError: name 'x_guidevel_s166' is not defined\nTraceback (most recent call last):\n File \"<string>\", line 1, in <module>\n File \"<string>\", line 169, in bake_fluid_data_166\n File \"<string>\", line 164, in bake_fluid_process_data_166\n File \"<string>\", line 80, in liquid_adaptive_step_166\n File \"<string>\", line 334, in fluid_pre_step_166\nNameError: name 'weightGuide_s166' is not defined\n```\n\n1. Open the file.\n2. Configure the cache folders in both domains.\n3. Bake the smoke domain.\n4. Bake the liquid domain (you will see the error in the console and no liquid in the scene).", "crash when i try to make instances real for nodes\nhi , in attached files all info about the crash , its when i try to make instances real for nodes modifier addon scifi pro + flex\nso can i fix it ?\n\n", "Fluid simulation result not visible after reloading file\nOperating system: MacOs\nGraphics card: Intel Iris Plus Graphics 640\n\nBroken: 2.91\nWorked: -\n\nHello. After I opened project, that I closed before, the fluid simulation didn't exist. It is very easy, to know the issue. Thanks for attention.\n- New file\n- Quick liquid effect on default cube\n- Save file\n- Close Blender\n- Open the same file again\n- The domain is just a smooth shaded cube until you play the file long enough for it to loop back to the first frame.", "use after free Fluid sim seg fault\nIn Debian testing, and Debian stable.\n\nbroken: blender 3.0.0 f7b22fc3d27113715e8726c69ab3264e1d487439\nbroken: Blender 2.93.0, Commit date: 2021-05-10 22:16, Hash ce62d650945f \nbroken: blender 2.92\n\nSegfaults on bake of modular fluid sim.\nReproducible each time I run blender on it.\n(Building a debug build now. the crash text isn't so useful yet).\n\n1. Load .blend (attached)\n2. Bake fluid\n3. Segfault\n\n[flu.blend](flu.blend)\nAsan report on f7b22fc3d27113715e8726c69ab3264e1d487439 [T88475_asan_use_after_free.txt](T88475_asan_use_after_free.txt)\nTwo crash reports on blender 2.92: \n[Blender_2021-05-22-145034_MACBOOKAIR.crash](Blender_2021-05-22-145034_MACBOOKAIR.crash)\nSimilar to #88113#1157996: [Blender_2021-05-22-193554_MACBOOKAIR.crash](Blender_2021-05-22-193554_MACBOOKAIR.crash)", "Particle Systems keep reacting to a Force Field even though the Force Field's already been deleted\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R5 M335 ATI Technologies Inc. 4.5.13497 Core Profile Context 23.20.768.12\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nParticle Systems keep reacting to a Force Field even though the Force Field's already been deleted. It's not that big a deal, but it may confuse or frustrate new users.\n\n - Select the default Cube. In the Particles tab, add a new particle system. Hit Play in the timeline to start the particle simulation.\n - While the simulation is still playing, add a Force Field, such as Wind. Rotate it 90 degrees around the y-axis. In the Physics tab, increase the Strength, perhaps to 20. The particles are now being blown away.\n # Delete the Force Field when the playhead is at about frame 40 or so. The particles keep being blown away from the start to that frame 40 or so, even though there's no longer a Force Field, even if you've tried replaying the simulation in the Timeline. The only way to return them back to before is to alter some settings, for example hiding the Cube in the Outliner then showing it again, or change the particle count, or baking the simulation, which are all awkward and confusing.\n[particleforcefield.blend](particleforcefield.blend)", "Particle system texture added via API not working ['blend_type' when created using the interface is MULTIPLY, whereas when created through API, its value is MIX]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83 (sub 17)\n\nHi,\n\nI have been trying to write a script that automatically adds a clouds texture to control the density of hair particles/instances. I have been able to successfully add a texture to the active particle system of the selected object with the Density checkbox under Influence activated -- all done through API. However, there is no effect on the density of the particles.\n\nI am clueless of why this is happening. Is this a bug?\n\nI have attached a blend file (with an internal script) for reproducing the bug.\n\n - Open the attached blend file.\n - Allow execution of scripts (in case not allowed)\n - Select the plane (already has a particle system) and search for 'Particle Density Texture' and execute the script.\n\nThe texture will get added successfully to the particle system's texture slots with the density option on, but will have no effect on the particle distribution whatsoever. The script also has an UNDO panel. You could try changing values there or in the properties panel as well, but will have no effect.\n\nAm I doing something wrong? Or is this a bug or a known issue or any API limitation?\n[particle_density_texture.blend](particle_density_texture.blend)\n\n", "Occasional render glitches when using simulation zones on an object without a material.\nThis bug has an easy workaround, mostly posting this so anyone running into the same issue knows the solution.\n\nOperating system: Linux-5.15.0-79-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.30.02\n\nBroken: version: 3.6.2\nWorked: N/A, 3.6 is the first version with simulation nodes.\n\nIn Eevee, rendering an object with a simple simulation zone applied in geometry nodes and no material assigned to the object results in some rendered frames being blank or displaying odd glitches.\n\nThe workaround is to simply assign a material to the object.\n\nCheck out the attached .blend file for reproduction.\n\n", "Distribution: Jittered And Random ignore flag \"Use Modifier Stack\" PS\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.5.0 Alpha\nWorked: never\n\njitter and random ignores modifier stack\n\n\n- Open default scene\n- In particle system change distribution to grid (modifiers stack appears to be included)\n- Change type to jitter/Random\n[GNParticle.blend](GNParticle.blend)\n", "Cannot paginate shape key list\nSteps to reproduce:\n* add any mesh (e.g. a cube)\n* in Object Data Properties > Shape Keys click '+' twenty times\n* clicking above or below the scroll bar does not paginate the list\n\nBroken: 3.5 alpha, 50c7eb14f455, master, 2022-12-19\n", "Particles reset their position when using time stretching\nMinimal reproduction steps:\n- Add a particle system to the default cube and make it renderable.\n- Set the old time stretching setting to 20 and leave the new at 100.\n- Play the animation until frame 90 and render.\n- Find that the particles are sticking on the object as opposed to their correct position in the viewport.\n- Render again. They now have their correct position.\n- Play another 5 frames.\n- Render again, they are now sticking to the object again.\n\n[timeStretchingBadRender.blend](timeStretchingBadRender.blend)\n\n**Original Report**\n\nHello,\n\ni am using blender-3.1.0-linux-x64 and working on particles with time stretching but the viewport display is correct.\n\nattached is the blend file. [experiment with text.blend](experiment_with_text.blend) \n\nproblem seen in cpu/gpu/cycles/evee.\n\nregards,\nYaju", "Flip the Render\nI proposed this idea to Campbell via email and he said it sounded reasonable enough to add here...\n\nThe idea: In the image editor, when the Rendered Result is displayed, pressing F will flip the render horizontally. This is a common action that many digital painters use in Photoshop to refresh their eyes and see new flaws in their work.\n\nSome notes:\n - It will should only work in the Rendered Result, not on regular images\n - All tools that normally work in Rendered Result, should work here as well. (rendered border, sampling image color, painting)\n - Only Flip X. I've tried Flipping Y before, but I haven't found it to be that helpful in the artistic process. Could be added later though if people want it?\n - Should apply the Flip state to all Slots. Eg. If flipped in Slot 1, when you change to slot 2 it will also be flipped. If you turn Flip off in Slot 2, it will also be off in Slot 1 and all slots.\n - To remove the potential confusion for users who flipped it by accidentally pressing F but don't know the hotkey, a new button should display in the toolbar. Here: ", "Some mesh operations (e.g. smooth, randomize) are not using mirror modifier mirror object transform correctly for clipping\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 950M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.1 Release Candidate\n\nWhen using mirror modify with clipping, Smooth Vertices ignore clipping and smoothing all, and this is no options\n\n\nTools to check:\n`Transform` > `Randomize`: does not clip (even without mirror object usage)\n`Transform` > `Warp`: does not clip (even without mirror object usage)\n`MESH_OT_vertices_smooth`\n\nnote: all of the above are not part of the transform system (randomize is even written in python), so it might be a bit cumbersome to implement" ]

[ "[Mantaflow] Setting \"Domain Type: Liquid\" doesn't apply all the \"liquid\" presets (flip particles and wireframe display)\nOperating system: Ubuntu 16.04\nGraphics card: nvidia quadro p2000 mobile\n\nBroken: 2.82 alpha, fa5e28ab08c7, 2019-12-26\n\nUpdated description (see discussion below):\n\nSetting a Fluid domain to \"Domain Type: Liquid\" seems to check the `- [x] Liquid` checkbox but \n- it doesn't create the \"FLIP Particles\" particle system\n- it doesn't set display level to \"Wireframe\"\n\nWorkaround: manually click on `- [x] Liquid`. It will stay selected (proving that it wasn't really selected before) and makes the updates needed.\n\n- Open Blender; save the startup file\n- Default cube: Physics > Fluid > Type: Domain; Domain Type: Liquid\n- Observe that `- [x] Liquid` is checked\n- Observe that, under Particles, there is no \"FLIP Particles\" system\n- Observe that checking `- [x] Liquid` manually triggers the creation of a particle system\n\n\n---- \n\nOutdated description:\n\n**Short description of error** \nI can't find any way to display the FLIP particles to debug/preview a FLIP (mantaflow) liquid simulation. \n\nI don't have any \"show FLIP\" option in the domain settings.\n\nHowever, using \"Quick liquid\" to set up the simulation correctly creates a particle system (called \"FLIP Particles\")\n\n- Open Blender; save the startup file\n- Default cube: Physics > Fluid > Type: Flow; Flow Type: Liquid\n- Add cube, scale up. Physics > Fluid > Type: Domain; Domain Type: Liquid\n- Hit \"Bake Data\".\n- Looking under Particles (or Modifiers), there won't be any particle system, which I believe is expected.\n\n(Alternatively: doing\n- Default Cube > Quick Effects > Quick Liquid\ncreates a particle system, not explicitly linked to any data block, called \"FLIP particles\")" ]

[ "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Outliner selection not working correctly after undoing object deletion\nOperating system: Linux-5.17.15-1-MANJARO-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD VERDE (LLVM 13.0.1, DRM 2.50, 5.17.15-1-MANJARO) AMD 4.5 (Core Profile) Mesa 22.1.2\n\nBroken: 2.91.2, 3.2.0, version: 3.3.0 Alpha\nWorked: prior to b077de086e\n\nAn object that is linked in another collection can usually be removed from just that collection by using unlink, while using delete removes it from both collections. But if you delete the object and undo, unlink does delete the object in both collections. \nRenaming the cube or creating a new object \"breaks\" the cubes apart so they can be selected/unlinked individually again.\n\nIn the default scene,\n- create a new collection\n- in the outliner, ctrl-drag the default cube object to that collection to link it\n- delete the cube\n- undo\n- in the outliner, it is now impossible to select the cube in the new collection separately and using unlink will delete both cubes", "Nodes: Group input subtype \"Angle\" max values are in radians, but the default implies degrees.\nOperating system: Linux-5.4.0-148-generic-x86_64-with-glibc2.31 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 3.6.0 Alpha\n\nThe subtype \"angle\" in the socket editor provides a default value in °, and a min and a max value, which seem related to the default setting in degrees, so the user assumes the slider in the modifier frontend UI to stop at the set values. Which it doesn't. Set max to say 1, and the slider will stop at 57,3° (180/pi), not at 1°.\n\n\n", "Alt modifier key to disable node auto-connection\nWe often get requests to make the behavior of auto-connection when placing nodes optional. This is because it can be tricky to place a node without connecting to overlapping links, among other reasons.\n\nA simple solution discussed in earlier [sub-module meetings ](22309) was is using the `alt` key to disable the auto connection.\n\n", "Importing a keymap with a default name makes a non deletable copy\nBroken: version: 3.2.1\n\nAfter importing a keymap configuration with the name \"Blender\" it created a copy of the default setting that is impossible to remove from the UI at least.\n\n\n\n\n\nImport a keymap setting with a default name\n\n\n**Fix**\nDelete keymap configuration from the user folder directly \n\n> \\AppData\\Roaming\\Blender Foundation\\Blender\\3.1\\scripts\\presets\\keyconfig\n\n\n", "Console warning \"ToolSettings\"/ \"snap_node_element\"\nOperating system: Windows 10\nGraphics card: Geforce GTX 970\n\nBroken:\n2.80, 8c8979067490, blender2.7, 2019-01-31\n\nI was importing a file from an older blender version and I noticed this error in the console:\n\nIt appears when you hover over the node editor and when toggling edit mode.\n\nThe reason I think it's not an issue which appears because of the different blender version is that I recently released an addon for managing nodes with layers and a few people noticed similar errors when editing a mesh with KitOps or similar addons and then trying to change the nodes.\nI also don't think it's an issue with my addon as I didn't change the file (included) with the addon and I tried it with a clean blender version as well.\n\n[warning_message.blend](warning_message.blend)\n- Open the file\n- Open blender console to see error messages\n- Hover over node editor with the cursor\n- > Warning message should appear", "crash when rendering with optics\nOperating system: windows\nGraphics card: 3060\n\n**Error**\n\n```\n# Blender 3.4.1, Commit date: 2022-12-19 17:00, Hash 55485cb379f7\n\n# backtrace\nException Record:\n\nExceptionCode : EXCEPTION_ACCESS_VIOLATION\nException Address : 0x00007FF7B98A5710\nException Module : blender.exe\nException Flags : 0x00000000\nException Parameters : 0x2\n\tParameters[0] : 0x0000000000000001\n\tParameters[1] : 0x0000000000000000\n\n\nStack trace:\nblender.exe :0x00007FF7B98A56F0 blender::default_construct_n<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_\nblender.exe :0x00007FF7B98B6730 blender::Array<blender::SimpleMapSlot<std::pair<int,int>,blender::meshintersect::ITT_value>,1,blend\nblender.exe :0x00007FF7B98B5770 blender::Map<std::pair<int,int>,blender::meshintersect::ITT_value,0,blender::PythonProbingStrategy<\nblender.exe :0x00007FF7B98B7570 blender::meshintersect::trimesh_nary_intersect\nblender.exe :0x00007FF7B98BE4D0 blender::meshintersect::boolean_trimesh\nblender.exe :0x00007FF7B98BE240 blender::meshintersect::boolean_mesh\nblender.exe :0x00007FF7B94D43D0 blender::meshintersect::direct_mesh_boolean\nblender.exe :0x00007FF7B3ACF380 exact_boolean_mesh\nblender.exe :0x00007FF7B3ACE760 modifyMesh\nblender.exe :0x00007FF7B37C78F0 modifier_modify_mesh_and_geometry_set\nblender.exe :0x00007FF7B37C6190 mesh_calc_modifiers\nblender.exe :0x00007FF7B37C5F80 mesh_build_data\nblender.exe :0x00007FF7B37C8560 makeDerivedMesh\nblender.exe :0x00007FF7B3759B30 BKE_object_handle_data_update\nblender.exe :0x00007FF7B3759990 BKE_object_eval_uber_data\nblender.exe :0x00007FF7B39AA920 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF7B39AA6C0 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7B92A2780 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475AF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FFA475A4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FFA475AA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FFA475AD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FFA60E41B20 configthreadlocale\nKERNEL32.DLL :0x00007FFA61A27600 BaseThreadInitThunk\nntdll.dll :0x00007FFA63722680 RtlUserThreadStart\n\n\nThreads:\nThread : 00004b34\nntdll.dll :0x00007FFA6376D6D0 NtDelayExecution\nblender.exe :0x00007FF7B9267160 BLI_thread_is_main\n```\n\nuse a lot of boolean modifiers(4-6) and high subdivision modifier level(3) and set it to display the changes only on the render and use optix\n\n", "Custom Node Trees: Selected node tree is lost when editor is switched to other node editors\n1. Run the official Custom Nodes Python template\n2. Switch to the newly registered Custom Node Tree editor\n3. Create a node tree\n4. Switch to another node editor (Shader Editor for example)\n5. Switch back to the custom node tree editor\n6. The selected node tree was switched back to None", "`outliner.object_operation (select hierarchy)` does not change active object when directly called through a key event\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.5.1\n\n\"outliner.object_operation\" has an inconsistent behaviour when assigned to a key:\nwhen I go to the outliner and I select a hierarchy with the \"right-click menu\" > \"select hierarchy\" I just click on the object that has a hierarchy that I want to select.\n\nIf I assign this \"outliner.object_operation\" \"select hierarchy\" to a key for example \"right click\" + \"alt\" when I click on the same object by pressing \"alt\" sometimes it will not perform the correct selection.\n\nI recorded a video to explain better the problem, sorry for my voice I'm a bit sick :( \n7E_2Zra_3CY\n\n\n- Assign \"outliner.object_operation\" \"select hierarchy\" to \"right click\" + \"alt\" .\n- Alt+right click on the hierarchy.\n- \"select hierarchy\" does work, but it selects the hierarchy of the active object instead from the object under the mouse pointer.\n - Expected: \"select hierarchy\" if performed with a mouse click, should select the object under the mouse pointer and select the hierarchy.\n", "Custom RenderEngine: Shader Editor issues\nOperating system: Arch Linux\nGraphics card: GTX Titan\n\nBroken: git version, 2.81.8 (f2400c1bb5e2)\n\n\nBehaviour with respect to keeping Cycles/Evee shader nodes around seems to be inconsistent with the documentation, as the shader editor is either not available or shows an incomplete list of shader nodes.\n\n\nOn bpy.types.RenderEngine.html the property `bl_use_shading_nodes_custom` is described as\n\n> Don't expose Cycles and Eevee shading nodes in the node editor user interface, so own nodes can be used instead\n\n\nUsing the attached RenderEngine test class, which is based on the code in the above doc page:\n\n1. Start `blender -P blender_render_engine.test.py`\n2. Switch to `Custom` renderer\n\nI see the following depending on `bl_use_shading_nodes_custom`:\n\n- When `bl_use_shading_nodes_custom` is `False` (i.e. keep Cycles/Eevee nodes\n```\naround) the Shader editor's add node menu (`Shift+A`) under `Shader` only \nhas a `Principled Volume` entry, other Cycles nodes are gone. But when creating a new material in\nthe editor the initial graph is `Principled BSDF -> Material Output`, i.e.\nusing the principled BSDF node that cannot be created from the menu.\n```\n\n- When `bl_use_shading_nodes_custom` is `True` the Shader editor is \n```\nno longer available. Is this new behaviour, where a custom RE\nneeds to provide its own editor page, instead of adding to the existing shader editor?\n\n```\nThere's also a corner case when having the Shader editor visible (for example when Cycles is active) and then switching to a render engine that has `bl_use_shading_nodes_custom=True`: the icon for the editor will become blank, but the Shader editor remains visible. In the console I warnings in this case:\n\n`WARN (bpy.rna): ../source/blender/python/intern/bpy_rna.c:1451 pyrna_enum_to_py: current value '3' matches no enum in 'SpaceNodeEditor', '(null)', 'tree_type'`\n\n [blender_render_engine.test.py](blender_render_engine.test.py)\n", "Segfault in CustomData_blend_read\nOperating system: Debian Linux, Stable\nGraphics card: GTX970\n\nBroken: 3.6.0 Alpha, branch: main (modified), commit date: 2023-04-05 18:55, hash: 92c9c1d4003e, type: Release\nWorked: Unsure. Old blend I loaded and worked on for a while. Errors on open now.\n\nSegfault on load.\n\n1. Load blend, or open blender and load blend\n\n(No idea what the gvfs error is.)\n```\nFailed to open dir (No such file or directory): /run/user/6001/gvfs/\n[New Thread 0x7fffe3ae9700 (LWP 2310937)]\n...\n[New Thread 0x7fffdb9fe700 (LWP 2310945)]\nRead blend: \"/tmp/segfault.blend\"\n\nThread 1 \"blender\" received signal SIGSEGV, Segmentation fault.\n0x0000000001009af9 in CustomData_blend_read (reader=0x7fffffffd498, data=0x7fffd9c471f0, \n count=5002)\n at /opt/src/blender-git/blender/source/blender/blenkernel/intern/customdata.cc:5194\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n(gdb) l\n5189\n5190 int i = 0;\n5191 while (i < data->totlayer) {\n5192 CustomDataLayer *layer = &data->layers[i];\n5193\n5194 if (layer->flag & CD_FLAG_EXTERNAL) {\n5195 layer->flag &= ~CD_FLAG_IN_MEMORY;\n5196 }\n5197\n5198 layer->flag &= ~CD_FLAG_NOFREE;\n(gdb)\n```\n\n", "Blender just crashes for no reason, and the crash report is empty. (Segmentation fault)\nOperating system: Arch Linux x86_64\nGraphics card: AMD Radeon RX 6900 XT\n\nBroken: (example: 3.6.2, ffe93138751e, master, 2023-08-31, as found on the splash screen)\nWorked: (No idea when this error started happening.)\n\nBlender does not start up. When I start it via the command line, I get this error:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\n`/tmp/blender.crash.txt`:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nTrying to open Blender.\n\n", "Linked data-block has \"pointer\" property still active\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Probably never\n\n\n\n[torus.zip](torus.zip)\n\nOpen torus.blend. It has a linked collection containing the selected object `Torus`.\n\nAs you can see in the image, the \"Object\" rna properties (parent, and the array modifier one) are both active:\n\n{[F13627034](image.png), size=full}\n\nIn fact you can even click on the property to change it (the popup show up, but clicking on it at least doesn't change it):\n\n{[F13627039](image.png), size=full}", "Geometry Nodes Inputs `is_animatable` Property Incorrectly Returns False\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0 Alpha\n\nGeometry Nodes inputs' context menus ([WM_MT_button_context ](bpy.types.Menu.html#extending-the-button-context-menu)) incorrectly show the inputs' `is_animatable` property as `False` when the property does accept keyframes (see screenshot, attached).\n\n\n - Open the attached .blend file (attached, below)\n - Run the script in the Text Editor\n - Right-click the Input property of the Cube's Geometry Nodes Modifier\n - Open the System Console to see the `is_animatable` property of `context.button_prop` is `False`\n[is_animatable.blend](is_animatable.blend)", "Rigid Body Animation segmentation fault after canceled move of passive rigid body\nOperating system:\n\"Ubuntu 20.04.5 LTS\" XFCE window manager\n32 GB RAM\n\nGraphics card:\nNVidia GTX1080 (Zotac Mini) -- Driver Version: 390.157\n\nBroken: 3.4.1\nWorked: 3.5\n\nForcing change to rigid body physics simulation by grabbing passive rigid body object (conveyor belt ) and then canceling results in segmentation fault on play of animation.\n\n - Open attached Blend file\n - In 3D viewport, select belt mesh\n - **NEW MISSED STEP** Play Animation without touching anything (note crazy physics)\n - g, drag, escape the \"Belt\" object to force physics cache to update.\n # Play animation. Segmentation fault should occur.\n\n[convetor.belt09.blend](convetor.belt09.blend)" ]

[ "Error during connection custom sockets to group input / output nodes\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 630 Intel 4.5.0 - Build 25.20.100.6471\n\nBroken: version: 2.93.0\n\n\nMy guess is that this is relevant to connecting custom (Sverchok) sockets because connecting standard color socket does not caus the error in a console.\n\n```Code marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-v293\\blender.git\\source\\blender\\blenkernel\\intern\\node.cc:441 in write_node_socket_default_value.```\n\nCan't help but report with such the invitation))\n\n1. Download sverchok add-on\n2. Add a node group\n3. Connect any node to group input / output nodes\n\n[2021-06-03 16-45-28.mp4](2021-06-03_16-45-28.mp4)\n" ]

[ "Compiling shaders for Eevee locks up the viewport until the process is complete (MacOS)\nOperating system: macOS-11.2.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.0.7\n\nBroken: version: 2.93.0 Beta\nWorked: I don't believe this has ever been good on the Mac platform\n\nWhen working in a heavy scene (the spring or barbershop demo, for example), the UI will \"beach ball\" or lock up while blender calculates Eevee shaders. On a pc, these calculations don't appear to lock up the interface the way it does on Mac. The expected behavior would be that the UI remains responsive at all times.\n\nOpen the Spring or Barbershop demos. Switch the viewport to full Eevee interactive rendering. The UI will lock up while Blender calculates the shaders. Once this process is complete, the viewport will return to normal behavior.\n\n", "Weight paint mode and vertex paint mode share the same brushes\nBroken: b8bb2bb960ac\n\nPretty much what the title says. When you adjust the settings of the Draw brush in the vertex paint mode the same changes apply to the weight paint mode. These are 2 separate modes with their own use cases and settings. They should not share their brushes.", "GPU Subdivision: Slow operations with Shape Keys\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3, 3.2\n\nWith the GPU subdivision turned on, many operations with shape keys (locking, changing the active shape key) are quite slow, but the reason for the delay is the GPU subdivision itself, because when it is turned off, the speed of operation is several times higher\n\nselect the body itself, and perform various operations with the shape keys (for example, changing the active one). Compare the speed with the GPU subdivision turned off and on\n[kira_lite.blend](kira_lite.blend)\n[2022-10-09 22-50-29.mp4](2022-10-09_22-50-29.mp4)", "Grease pencil strokes are incorrectly blended with geometry in draw mode (depending on 'Fade Inactive Geometry' setting)\nOperating system: Win 10\nGraphics card: ATI Radeon 5700\n\nBroken: (example: 2.92b, 213f8*, master, 2021-01-28, as found on the splash screen)\n\n\nnote: this is due to `Fade Inactive Geometry` being ON\n\nWhen drawing grease pencil strokes with a black material the rendering style changes when...\n\n - ...switching between draw-mode and edit mode, or\n - ... toggling the overlay button in draw mode (even will all overlay options disabled).\n\n\nThis leads to noticeable rendering artifacts while drawing. Please consider the following screenshots:\n\noverlays on:\n\n\noverlay off:\n\n\nSome assumptions:\n- I assume that the blend modes are not correctly set and thus interfere with the MSAA.\n- The white artifacts are especially pronounced for thin strokes of all opacities. Increasing the thickness factor slightly decreases the problem.\n\nLoad the following blender file\n[stroke-test.blend](stroke-test.blend)\n\nStep by step:\n1. Start blender\n2. Create Cube\n3. Create Grease Pencil\n4. Add new material for grease pencil and change to black\n5. Draw strokes (with different opacities)\n6. Switch between Draw and Object mode or toggle Overlay-Toggle\n", "Slow EEVEE timeline scrubbing when using Scene World material\nOperating system: Arch Linux\nGraphics card: Intel UHD 620 (`iris` with `INTEL_DEBUG=reemit`)\n\nBroken: `0781c22ceedc`, `2.90`\nWorked: \n\n\nScrubbing through the timeline on an empty scene is slow when viewing through EEVEE and Scene World enabled, even though the node graph for it is a simple Background Shader node.\n\nThis also happens when *nothing* is connected to World's material output.\n\n[slow_scrub.mp4](slow_scrub.mp4)\n\nYou can see in the first part of the video, when using LookDev and have Scene World disabled, the scrubbing is relatively fluid and very close to the cursor. After enabling Scene World you can see that the scrubbing is lagging behind the cursor.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Create a new scene\n2. Delete everything (not really necessary)\n3. Try scrubbing the timeline without Scene World in LookDev\n4. Try scrubbing the timeline *with* Scene World in LookDev\n5. Notice that the latter is less responsive\n\n**Note**\n\nI have only experienced this on this GPU (probably due to its low-performance), however I still feel this is a weird bug.", "C and V keys pressed while drawing a Grease Pencil stroke unchangeable in keymaps\nOperating system: Windows 10\nGraphics card: RTX 3070\n\nBroken: 3.0.0\nWorked: n/a\n\nWhile in the middle of drawing a stroke, pressing C and V keys toggle guides on and off. \n\nThe C and V keys can be bound to something else in preferences, but whatever you bind them to, pressing them while in the middle of drawing a stroke still turns the Guides on and off. I can find no listing for these shortcuts in the Keymaps section.", "Sculpt: Evaluate multiple paint steps at the same time.\nCurrently a paint step is evaluated one by one. Redoing multiple checks and calculations. In case those checks and calculations are similar we could improve performance by evaluating multiple paint steps in the painting kernel.\n\nWhen sculpting this isn't possible as geometry is changing, but when only effecting colors or attributes this could improve performance.\n\nChecks/calculations that would return the same result:\n* Clipping tests: In order to do this we should split clipping tests from brush tests.\n* Most texture evaluation\n\nWould especially improve texture painting performance as most effort at this moment was done to reduce the calls to these tests.\n\nA possible approach would be to collect the steps in a list, still evaluate them one by one. But brushes that can benefit would store the needed data in a list containing dynamic data per step.\nWhen the paint frame finishes the brush will be triggered to do the actual evaluation.\n", "Color space seems wrong while painting in image editor.\nIn the image editor add a new image and with default settings just do a red line paint over a green line paint.\nDark zone appear in the falloff between red and green. it should not be there and should stay clear, not dark. \nI don't know why, but it looks like a color space issue. \n\ndark falloff not ok in blender:\n\n\nclear falloff ok in gimp:\n\n\nblender 2.8\nWindows 7 \n\n\n", "Polishing the Painting Experience\nThere are a few tasks that would enhance the texture painting pipeline that could be prioritized before advanced features like layered textures is even considered.\n\n## Existing Painting System\n\n### Small Tasks (e.g., bug fixing)\n- [ ] Graphics Tablet Lag when in Texture Paint mode in Blender 3.0 #93796\n- [ ] Undo bugs\n - [ ] Undo eliminates brush texture #88592\n - [ ] Texture paint undo can changes texture slot #62520\n - [ ] Texture Paint mode tools swap when exiting maximized area #98014\n- [ ] Color space support for texture painting #95797\n- [ ] Sync Image Sequence options (Frames, Start Frame, Offset, Cyclic, Auto Refresh) #109769\n- [ ] Texture paint: Bleedind around thin cuts do not fill texture #106066\n- [ ] Add support for \"Channels\" to the Images & Color Attributes #108404\n- [ ] 8/16 bit textures have different strength behavior (premultiplied problems) #101436\n- [ ] UDIM bugs [need report]\n- [ ] 3D mirroring in Image Editor\n- [ ] Other bugs (by Daniel Bystedt) [need report]\n\n### Bigger Tasks (e.g., re-designs) - need design\n- [ ] Image syncing between Editors via active image canvas #103636\n- [ ] Multi-object painting\n- [ ] Multi-object uv editing\n- [ ] Support \"viewport\" face sets in Image Editor\n- [ ] Square brush\n\n## 3D Brush\n\nRelated to #96225\n\n### 3D brush vital\n- [ ] Color sampling\n- [ ] Erase blend mode\n- [ ] Affect only visible (Show/Hide)\n- [ ] Affect Alpha option\n- [ ] Masking\n- [ ] (2D) Fill operation\n\n### 3D brush additional\n- [ ] Feature parity\n - [ ] Blur & Smear brushes\n - [ ] Clone brush\n - [ ] Sync masks and edit mode selection\n - [ ] Paint modified geometry instead of base mesh\n - [ ] Missing brush settings\n - [ ] Stencil masking\n- [ ] Image editor syncing\n- [ ] Dedicated paint mode\n- [ ] Performance\n\n", "Vertex Paint ➔ Paint menu ➔ Smooth Vertex Colors could be improved\nOperating system: Windows 10 Pro 64-bit\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nTested: Blender 2.81 Alpha, September 18, 14:29:45 - b962aca8003d\nWorked: never\n\nVertex Paint ➔ Paint menu ➔ Smooth Vertex Colors tool does not smooth other than direct loop neighbors.\n\n1. Divide the default cube a few times (apply if subdivision is done with modifier).\n2. Enter Vertex Paint mode.\n3. Paint an area with black.\n4. Apply Paint menu ➔ Smooth Vertex Colors.\n5. The vertex paint is not smoothed other than direct loop neighbors.\n\n\nHere is some clarification as the descriptions above are not very clear (I work with vertex colors very regularly and still came out confused by reading this post).\n\n- The Smooth Vertex Colors command will have visible results *if* it is run on vertex colors that have been applied per-face (by first selecting the desired faces in Edit mode, and then filling them with colors in Vertex color mode with the face filter enabled). Think of these as \"harsh\" vertex colors. When such vcols exist, then the smooth operation will indeed smooth out the vcol data so that the harsh separation between painted faces will be smoothed out, blending it with the surrounding faces.\n- But if the command is run on vcol data that has been painted on using the paint brush or on vcol generated by the \"dirty vertex colors\" command then nothing will happen as the vcols will already be point-based.\n\nTherefore there is no bug here, just some very confusing naming of the command and a lack of clarity when the command is run but nothing happens. For any user working with painted-on vertex colors, it will indeed seem like nothing is happening at all since one would expect some sort of global smoothing to be applied.\n\nPart of the confusion is also coming from the fact that this command sits just below \"Dirty Vertex Colors\" in the menu, which generates smooth, per-vertex vcol data. Meaning that for a user exploring vcol mode by trying one feature after the next, \"smooth vertex colors\" will almost always feel like it is doing nothing at all (unless the user first applied some vcol using face masking, which is extremely unlikely).\n\nIf anything the tooltip and/or the menu entry could be changed for clarity :\n\n- The menu item name could be renamed from \"Smooth vertex colors\" to \"Smooth harsh per-face vertex colors\"\n- The tooltip could be changed from \"Smooth colors across vertices\" to \"Smooth colors across vertices. Only operates on harsh, per-face vertex colors\".\n\nAnd then of course it would be great to have a new feature altogether to blur vcols globally, similarly to what the blur brush does.", "Realtime compositor: Texture node output textures with artifacts\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.6.0 Alpha\nWorked: n/a\n\nTexture node support was introduced in 151a53110c\n\nIn realtime compositor, Texture node outputs textures with artifacts.\n\n\n\nIt happens with most procedural textures I tested. This does not happen when a custom image is used, or when Blend texture is connected from the Value output (instead of the Color output) of the node. (With other textures it happens with both outputs.)\n\nThis does not happen when running Blender with a single thread (`blender -t 1`)\n\nFile for quick test: [TextureNodeTest.blend](attachment)\n\n", "GP brush pin for fill only, makes both stroke and fill\nHi \nI want to have fill and stroke in different color but if I pin, I get both color same.\nSo that I cannot make custom brush, or I have to change it vertex mode every time.\nCan you please check?\n\n[image](attachment)\n\n", "Paint Mode: Erasing\nNOTE: This task is currently to document the requirements for erasing workflows for painting. This should be the basis for discussions on the implementation.\n\n# Goal\n\nFor an intuitive painting workflow it's necessary to have an eraser accessible at all times.\nThis has been a shortcoming in Blender for painting, since the erasing of alpha channels has only been available as a blending mode for brushes.\nThis is very hard to access via the UI and shortcuts.\n\n# Recommendations\n\nThe ideal solution is to have a very simple brush tool in the toolbar. Aside from the typical texture, stroke, falloff and cursor settings, it can only erase alpha.\n\nThis tool can then have the shortcut `E` assigned by default to make it very accessible.\n\n## Pure Emissive Colors\n\nThe motivation behind not offering a blending mode to \"Add Alpha\" in the Erase Tool is because this has been notoriously difficult to do like the user would expect.\nSee #86868 & #83342.\n\nWhen painting float or pre-multiplied images, the alpha is treated differently. Any color with an alpha 0 would have the RGB colors displayed as pure emissive colors and still visible.\nThe only way to erase the colors completely is to also erase the RGB channels to 0.\n\nAs a result the design for the brush should emphasise this: **The Erase brush is a destructive tool!**\nIf you erase the alpha directly via painting tools you should expect to likely lose the full RGBA color information.\nThe alpha 0 areas can be painted over with a new color afterwards. \n\nFor non destructive erasing of alpha values it is recommended to use a separate image as a mask. This can be done right now via nodes.\nThis non-destructive approach might not be very accessible right now but that can be addressed separately (Especially with the [layered textures design]())\n\n## Erasing Selections\n\nWe need to discuss how we want to handle other erasing operations like via Gesture Tools (Box/Lasso/Line Erase), or for example the Color Filter for gradual erasing. These generally affect the unmasked/selected areas.\nThere are different ways to enable this workflow.\n\n**Erase Operator**\n\nThe simplest way would be to add an operator to the menus and mapped to a shortcut (Like `Delete`) to erase the colors on any selected areas.\nThe user would in that case use the existing Gesture Tools and brushes to mask/select areas to define the areas to be deleted.\nThis approach would follow the Select -> Operate paradigm of Blender closest.\n\n**Erase Tools**\n\nThe existing Color Filter tool could receive an additional Filter Type to 'Erase'. This would allow gradual erasing in the case where it is needed.\nAdding Gesture Tools specifically or erasing is also possible but might just bloat the Toolbar.\n\n## Erase Mode\n\nAn alternative approach is to make the \"Erase Alpha\" blending mode in the regular painting tools more accessible.\nIn other painting application such as Krita every tools and brush has an \"Erase Mode\" button that can be easily toggled with a shortcut and applies globally to all tools and brushes.\nWe could implement this design as an alternative to the Erase Tools/Brush for users that prefer this workflow.\n\nIn that case the Erase Alpha blending mode would be a button in the header that can be toggled directly, instead of being part of the blending modes popup.\nA shortcut could also be assigned.\nThis toggle should be available for for all brushes and tools that affect colors. ", "Sculpt Paint: Accumulative Painting/Sculpting\nNOTE: This design is still under discussion and is incomplete.\n\nThe recent addition of painting tools in sculpt mode also added an alternative design for accumulative painting.\nBecause of this there are now two different ways of handling accumulative strength.\nThis needs to be polished and properly integrated into the UI and painting workflow.\n\n# Strength and Accumulate\n\nSo far brushes always had an \"Accumulate\" setting for removing the maximum strength cap. Brushes would then keep adding their effect as long as the stroke continues.\nOtherwise they would either accumulate up to a hard-coded upper strength cap (sculpt mode) or up to the set strength (painting modes).\n\nThe issues with this implementation are:\n- It is easy to accidentally clip the colors while painting (There is no upper cap with accumulate)\n- The setting is hidden in \"Advanced\" brush settings even though it is regularly used, and even preferred for painting.\n\n# Flow\n\nThe new painting brush in sculpt mode instead uses a \"Flow\" slider, which defines how strong each step of the stroke is. \nThe stroke will then keep accumulating more slowly towards the set Strength.\n\nThere are a few issues with this implementation:\n- The Flow setting is less accessible, even though it can sometimes to be the preferred way of changing the stroke intensity.\n- The relationship between Strength and Flow becomes very confusing, especially when comparing sculpting & painting brushes or when enabling pressure sensitivity settings\n\n# Proposal\n\nHow to make the settings and behaviours more predictable and accessible needs to be further discussed.", "Mirror painting error\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "Texture Painting is slow / lags with large brush size\nOperating system: Windows 10\nGraphics card: GeForce 1080\n\nBroken: 2.80 690478027bd7\n\nWorked: (optional)\n2.79b with Window Draw Method set to Overlap Flip\n\n\nTexture painting in the 3D viewport is laggy in 2.8, especially with a medium to large brush size. The smaller the brush size, the better the performance. Painting in the UV viewport has no lag. \n\nIn 2.79, changing the Window Draw Method to Overlap Flip fixed this problem. I have been unable to find the Window Draw Method settings in the 2.8 prefs.\n\nYou can test this on the attached object. Just create a new image and try painting on it in the 3D viewport. With a GeForce 1080 on Windows 10 with 32GB of RAM and a 3.6GHZ Xenon processor, I get extremely laggy performance.\n\n[branch.blend](branch.blend)", "brush lag in texture painting\nOperating system: Windows 10\nGraphics card: GTX 1080Ti\n\nBroken:\n2.80 0f5b53ba4dc\n\nWhen painting textures in 3D viewport brush lags very much, so that it is not even possible to draw a circle. In Texture editor it works fine. \n\nThe same issue with any mesh. Does not matter how many polygons. increased brush spacing also does not help. [Painting_Lag.mp4](Painting_Lag.mp4) \nAttaching short video with this issue.", "Stroke lag in texture paint with Geforce GTX 1080 ti\nOperating system: Windows 64 bits\nGraphics card: GTX 1080 ti\n\nBroken:\n2.79 and 2.8\n\n**\nWhen painting in texture paint I´m having lag that gives me straight lines instead soft curves.\nThis is happening to me and a friend, and both have a 1080 ti.\nI tested the same problem in a pc with a Geforce 820m and in other pc with a RTX 2080 and worked perfectly, so appareantly the problem is only with the 1080 ti **\n\n**\n- Select the default cube and select the texture paint workspace\n- Create a new Image and select this image in the texture slots (single image mode)\n- With the brush draw some curves in the cube and you will notice **" ]

[ "texture in solid mode not updated\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2, 2.93\nWorked: probably never\n\nif the shader editor is located in another workspace, in which there is no viewport in solid mode, then the texture on the object will not be updated\n\n- Open .blend file\n- In both layout an shading workspace: make sure skin texture is selected\n- switch to shading workspace and select blue texture\n- Now switch back to layout workspace (notice `blue` texture is selected in node space but viewport is not updated)\n\n[#99598.blend](T99598.blend)\n\n---\noriginal file and video provided by the reporter\n[jupiter.blend](jupiter.blend)\nVideo [F13283900](2022-07-11_00-19-08.mp4)", "Viewport Shading 'Attribute' Option Broken for Instanced Geometry\nOperating system: Windows 10\nGraphics card: Nvidia GTX 2080\n\nBroken: 3.5\nWorked: 3.4, 3.4.1\n\nWhen instancing a mesh to another meshes vertices, the Solid Viewport Color Option 'Attribute' is no longer displaying the vertex color data.\n\nCreate A Sphere, and using \"Vertex Paint Mode\" Paint a color onto the sphere.\nUsing geometry nodes set up the following, Group Input (Geometry) -> Mesh to points - > Instance on points -> Realize Instances -> Output (Geometry)\nSet a simple sphere as the object to be instanced.\nSet Shading mode to 'Solid'.\nToggle 'Attribute'\n\n", "Can't display .blend thumbnail in the Windows explorer\nwindows 7 64 bit\n\nBroken: blender 2.75a c27589e\n\nCan't display .blend thumbnail in the Windows explorer!\n\nboth v2.75 and 2.75a all can't display .blend thumbnail in the windows explorer! I have install and uninstall again and again ,it's still don't display thumbnail. \n", "Subsurface scatering does not indirectly affect diffuse.\nHello,\nI've noticed an oddity: materials with SSS are considered totally opaque, but only for the diffuse aspect, but remain visible for glossy surfaces ;\n\n\n\n\nIt looks like a limitation, but it doesn't seem to be listed anywhere :\n\n-0df9b2c715\n-sss.html\n\nMaterials, such as ivory, jade, marble, rubber or skin, will produce variable results.\n\nIf this is a limitation, it's strange that it's only on the diffuse component and not the glossy one.\n\nSo it looks like a bug.\n\nThanks for reading, and sorry about my bad English.\n\n\nOperating system: Windows 11\nGraphics card: nvidia 2080ti\n\nBroken: 3.6\nWorked: none ?\n\n\nLoad SssPasstrought.blend , render\n\n", "Xray doesn't work in wireframe shading for objects set to display as wire.\nBroken: 3.0\nWorked: \n\nXray doens't work in wireframe shading mode for objects set to display as wire.\n\n- Open .blend file\n- Change the viewport shading to wireframe.\n- Set one of the cubes to \"Display As : Wire\" in object properties->viewport display.\n- change X-ray value from `Viewport Shading` popover\n- compare the two, only one has xray effect.\n\nTest File:\n[#94802.blend](T94802.blend)", "Unable to accurately sample colors in Vertex Paint mode\nOperating system: Linux-5.10.11-arch1-1-x86_64-with-arch 64 Bits\nGraphics card: GeForce GTX 660M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.92.0\nBroken version: 2.83.1\nWorked: 2.79b\n\nSampling colors in Vertex Paint mode is unreliable even in flat shading or when utilizing an emission shader and standard color management (although this reports the correct color some of the time) in both Cycles and Eevee.\n\n1. With the default cube selected, enter Vertex Paint mode.\n2. Switch the viewport shading to Solid, the lighting to Flat, and the color to Vertex.\n3. Change the brush color to #000003.\n4. Go to the Paint menu and select Set Vertex Colors (or press Shift+K)\n5. Sample the color on the cube by either using the eyedropper from a color picker, or pressing S with the mouse hovering over the cube (doesn't matter if Sample Merged is checked or not)\n6. Check the brush color and see that it has changed to some other color (#010103 on my machine)\n", "Sculpt Mode: Improve Expand performance\nWith [D16434: Sculpt Mode: Invert Expand behavior for masking consistency](D16434) it will be a stronger focus to highlight the Expand operators as a core feature in sculpt mode to create masks & face sets.\n\nThe issue is that the operator tends to be too slow to initialize on high res meshes.\nThis is especially the case for the geodesic expanding method.\n\nWe need to address these performance issues.\nOne usggestion was to incrementally calculate the distances while the operator is running.", "Inconsistent naming for modes in the undo history menu\nBroken: 3.4 alpha\n\nIn the undo history panel, the \"Object mode\" entry is registered with the name of previous modes. Switch from sculpt mode to Object mode will create an undo step with \"Sculpt Mode\" name\n\nAs for the other modes entries, they have no naming standard. Some entries have \"Toggle\" written before, some have \"Toggle\" after, some don't have \"Toggle\". Also they all have \"Mode\" written except for texture paint. \nThe entries are as follows:\n\n\"Texture Paint Toggle\"\n\"Weight Paint Mode\"\n\"Vertex Paint Mode\"\n\"Toggle Edit Mode\"\n\"Sculpt Mode\"\n\nBased on the default startup;\nChange modes; \nCheck \"Edit -> Undo History\" menu.\n", "Painting on pixel-textures do not allow to paint some faces\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: \n- 2.92.0\n- 2.91.0\n- 2.90.1\n\n\nI can paint one face but can`t do it with another, and third one transfer color to wrong place of texture.\n[2020-12-21_11-51-55.mp4](2020-12-21_11-51-55.mp4)\n\nHere the file\n[1pxTexturePaint.blend](1pxTexturePaint.blend)\n", "Armature Object's \"Display As\" does nothing\nOperating system: Linux-5.3.0-26-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.82 (sub 6)\nWorked: version: 2.79 release.\n\nWhen I add an armature and change the Viewport Display Mode, nothing happens.\n\n\nOpen the blender;\nDelete the default objects;\nAdd an Armature, single bone;\nIn the Properties Panel, Object Properties, Viewport Display:\nChange 'Display As' to anything, it doesn't work.\n\n\n\n", "Sculpt brush with texture breaks sculpt tiling\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.14757 Core Profile Context 20.11.2 27.20.14501.18003\n\nBroken: version: 2.93.0 Alpha\n\nIf the sculpt brush has a texture enabled with mapping set to *Area Plane*, then tiled strokes break up and do not match properly at the seams.\nIn this example the original stroke is on the right.\n\n\n1 Add texture to a brush\n2 Set mapping to area plane\n3 Enable tiling in the Symmetry drop-down menu\n4 Try sculpting at the seams\n\nOr use the file\n[tiling_bug.blend](tiling_bug.blend)\n\n", "Sculpt Mode TODO tasks\nThis task keeps a list of approved tasks related to Sculpt Mode that can be considered as TODOs or missing functionality in the current design.\n\n**Gesture tools**\n\n - Make Hide Box tool use the new sculpt API and gesture operator\n - Face Set Line Gesture\n - Color Fill Gestures\n - Line Trim Gesture\n - Normal Orientation for trimming tools\n - Poly line gestures\n - Mask Gradient Gesture tools\n - Lasso, Line and Poly line hide tools\n\n\n\n**Sculpt Vertex Colors**\n\n - Sculpt vertex colors gradient Tool\n - Combined Color Coords Undo step\n - Pick Sculpt Vertex Color from other object with the sample color operator\n\n\n**Transform tool**\n\n - Transform Tools TODO: #80392\n\n\n\n**Brush tools**\n\n - Expose minimum size and size pressure smoothness for all brushes\n - Implement area normal/center stabilizer \n - Make Grab active vertex grab from original coordinates instead of PBVH deformed coordinates\n - Pinch perpendicular mode for crease\n\n\n\n**Viewport**\n\n - Update matcaps to include a separate specular pass\n - Render Face Sets as contour lines\n\n\n\n**Elastic Deform**\n\n - Pinch elastic deform mode\n - Multi scale twist-scale-pinch for elastic deform\n\n\n\n**Filter tools**\n\n - Support textures in mesh filter\n - Unify filter strength with brush strength \n\n\n\n**Cloth Sculpting**\n\n - Expose solver properties as Sculpt properties (iterations, delta...)\n - Make use collisions options global\n - Implement SDF collisions\n - Implement collisions plasticity\n - Elastic Deform cloth brush\n - Support cloth deformation target with dynamic area in all brushes\n - Support cloth deformation target for the transform tool\n\n\n\n**Boundary brush**\n\n - Split the internal and boundary falloff into two different falloff\n - Let boundary falloff offset be smaller than 1\n\n\n\n**Sculpt Mode options**\n\n - Store radial and tiling symmetry in meshes\n - Enable \"Delay Viewport Updates\" by default\n - Add a separate property to meshes to store if they should use flat/smooth shading in sculpt mode, without modifying their normals\n\n\n\n**Multires**\n\n - Multires Delete Lower\n - Multires refit/rebase\n - Key map changes to support switching up/down subdivisions\n - Hide remeshers and Dyntopo when multires is active\n - Preview the current/total number of subdivisions in the viewport\n - Optimize Unsubdivide dissolve operation when creating the base mesh\n\n\n", "Texture paint Backface culling option does not work if symmetry is enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.6.1\nWorked: never since implemented in e2d60d180ed8 afaict\n\nWhile in the texture paint mode, the backface culling option of the brush is sometimes ignored, allowing painting onto backfaces. It only seems to affect certain objects. I could not discern why. See the attached blend file.\n\n1. Open attached blend file.\n2. Paint on the backfaces of the mesh; observe bug.\n3. Select cube\n4. Paint on the backfaces of the cube; observe no bug.\n\n", "Switching to a mode that has a tool set which is not available for that object causes error [e.g Select Box tool is available if paint mask is enabled, if it is disabled it causes error]\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0\n\n[when i try open vertex paint or weight paint , brush and color bar not coming to viewport]\n\n[after basic modeling something i apply all modifer and try to create uv but i cant do properly. So after unsuccessful attempt i tried to paint weight paint but color and other bar not coming to screen. But if i create new blend file and append it. Also work and i can create but after some paint also broke vertex paint file and mine locak vertex paint parts gone. btw i also cant open in new file as link...\n\n[try_007_gun.blend](try_007_gun.blend)\n\n\n", "Undo in Sculpt Mode\n\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.90.1\n\nWhen I apply undo in sculpt mode it applies to my previous settings as well (symmetry activation, some of brush settings and any settings in sculpt mode). \nThis is so annoying moment please help with it?\n\n" ]

[ "Texture on active object is not visible in solid view with sculpt mode activated\nOperating system: Windows 10, Ubuntu 16.04\nGraphics card: GeForce GTX 760\n\nBroken: 2.80\n\nTexture is not visible in solid view with sculpt mode activated\n\nCreate a texture, apply it to an object, like start cube, make sure you're in solid view mode with textured color active, you'll see the texture in object mode. After switching to sculpt mode, object becomes gray.\nIf you change view mode to LookDev or Material, everything is fine.\n\n**Extra info**\nIf you go back to Solid view and add a Shape Key, texture is visible again, but mask brush doesn't work. The problem with mask brush and shape keys is already mentioned #67303\nI made a video about those problems Mk2w41C87AI" ]

[ "Solidify creating points at incorrect angles using complex option with flat option\nOperating system: Linux-5.4.0-84-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.0.3\n\n\nBroken: version: 3.0.0 Alpha\nAlso happens in 2.93.4\n\nSolidify creating points at incorrect angles using complex option with flat option\n\n\n\n\n\n\n\n\n\n\n\n\n\nAnimation showing the issue\n\n\n\nHere's a test Blend file\n[solidfy_issue.blend](solidfy_issue.blend)\n", "Rigid body Bounciness parameter not functioning\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.20\n\nBroken: 2.92 and version: 3.0.0 Alpha\nWorked: 2.83.13\n\nIn recent Blender versions the bounciness parameter of rigid bodies does nothing.\n\nOpen attached file, press space to start animation.\nOlder versions: ball bounces\nRecent versions: ball falls and immediately comes to an halt when it hits the surface of the cube.\n\n[Bounciness bug.blend](Bounciness_bug.blend)", "Radius in place of Size at Empty viewport menu\nI{[F6596506](RIGHT.JPG)}\n\n am new to blender and not know where to post this but plz check it.It seem wrong to me\nthanks", "Loop Cuts and Inset Faces cutting Meshes\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 750 TI\n\nBroken: 3.2\n\nTrying to add regular edge loops with Control + R, or even trying inset a face, they are cutting my mesh, or merging the ends. (I shared this on reddit, and it was suggested I create bug for it. \n\nAll I did was delete the bottom face of the mesh since I would not need it, but somehow I created invalid geometry and when I add an edge loop near the end it merges. If I try to inset the faces, it gives me weird end geometry.\n\n(This is what was noted from someone on Reddit: Update: just checked the file and here are my findings:\n\n```\n Adding a loop, be it length ways, long ways, or any other way seems to works just fine with the CTRL-R shortcut\n```\n\n```\n The loop cut tool also works just fine.. except if you try and loop cut around the XY plane instead of the XZ plane (drawing a line around the thinnest faces) at which point the mesh seems to collapse to zero height\n```\n\n```\n Insetting faces also works fine, be it via the tool or pressing I... but if you then try and extrude the inset suddenly the model collapses\n```\n\nOther things of note: the face orientation is inside out for this mesh (turning on Face Orientation in the Overlays menu (two overlapping circles in the header) shows them as red) and the object-level scale hasn't been applied. Fixing both of these doesn't correct any of the above issues -- although it IS normally advised since it prevents a few shading and modelling issues -- but it does, for some reason, change how the errors manifest, like the model collapsing in a slightly different way or the CTRL-R shortcut suddenly causing the same issues the tool version of loop cut and slide has.\n\nConclusion: you've somehow managed to turn this mesh into some form of invalid geometry that Blender can't seem to handle properly. You may wish to report it as a bug, including this file as a demonstration.\n\n- Open .blend file\n- enter edit mode and select face mode\n- press numpad 3 for YZ plane view\n- Add loopcut on visible face side (it'll merge the edges)\n\n---\n- repeat first 2 steps from above\n- press numpad1 for XZ plane view\n# select visible face -> extrude + scale (will merge edges). Works with inset tool\n\nTest File:\n[Issues Build2.blend](Issues_Build2.blend)", "Sculpt, Mask extract with certain mesh produces broken mesh (hidden geometry)\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nMesh made as «mask extract» from sculpt, then I fill and triangulated top.\nIt looks like mesh contains non-selectable geometry, that prevents to make proper operation Origin to geometry.\nTry to do it. Origin will stay at the same place.\n\nAfter exporting obj and importing back bug gone. After remesh too.\nIt is the second time, I`ve encountered such issue.\nMay be related to #82209 (Blender hanging with «separate selection» in particular model/file (svg imported).)\n\n[mesh.blend](mesh.blend)\n\n[2021-03-24_11-40-49.mp4](2021-03-24_11-40-49.mp4)\n\n\n\n", "Solidify (Complex, Constraints) - very rare glitch\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.5.1\nWorked: 3.1.2\n\nbehavior changed in c2e8e68b6517b91eb14270707d7182c1727861c4\n\nSolidify modifier creates a weird glitch at a specific vertex.\n\nI have a model with about 40000 verticies that I wanted to solidify. Everything works fine, except the surroundings of a single vertex. The topology does not seem any particular there. The model is made out of triangles, but the glitch also appears if I convert it to quads. I copied the vertex and the surrounding faces to a sperarate blender file and recorded how the glitch appears depending on moving one of the verticies:\n\n(the glitch looks exactly the same when the vertex is part of the larger object)\n\nSolidify Modifier Settings:\nMode: Complex\nThickness Mode: Constraints\n(other settings does not affect the glitch)\n\n", "Blender freezes when moving the cube repeatedly on 3.6 and 3.5\nOperating system: Ubuntu 23.04\nGraphics card: Intel UHD 620\n\nBroken: 3.6.2 2023-08-16\nWorked: None\n\n\nWhen opening Blender(first or other times) and choosing general then moving the cube in multiple directions, Blender freezes\n\n\n- Open Blender\n- Choose general\n- Move the example cube with the move tool in multiple directions\n\n", "Unsubdivide support for non-grid topology\nOperating system:mac os mojave 10.14.5\nGraphics card:intel iris 550\n\nBroken: d62a749fcf48\nWorked: never\n\nUnsubdive either from the edge menu or under the decimate modifier not giving expected result with many production models. This never worked well so I figured I put in a report since I haven't seen an active one.\n\nAttached blend file, unsibdivide fails more often than not, producing triangles with unsubividealbe geometry. Works in other packages though, so it's not a problem with the geo.\n\n\n[unsubdivide.blend](unsubdivide.blend)", "No snapping for objects referenced in modifiers (even if disabled)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\nWorked: probably never; hopefully it's just an oversight. Even 2.79b is broken\n\nI've experienced this a handful of times but finally sat down to investigate from the user perspective here today (sorry, haven't looked at the code). But apparently the object you use as Simple Deform's \"origin\" will not be snap-able to the object that has Simple Deform on it. It doesn't matter if the modifier is enabled or disabled or if the settings actually produces no deformation, it always breaks snapping for the origin object.\n\n[snap-issue.blend](snap-issue.blend)\n\n- Open the attached .blend file OR follow next instructions to setup\n - Start with default scene and add an Empty to the scene\n - Add a Simple Deform modifier to the Cube\n - Set the Simple Deform's \"origin\" object to the Empty, the mode to \"Bend\" and the \"Angle\" to 0deg (to prevent any deformation)\n - Set the scene snapping mode to vertex\n\n- Grab the Empty and attempt to snap it to verts of the Cube -- it cannot snap (bug)\n\n- Disable the modifier and repeat the snap attempt -- it still cannot snap to the Cube (bug)\n\n- Create a new object and attempt to snap the empty to that new object -- it succeeds (the Sphere in the attached .blend file)\n\n- Delete the modifier and repeat the snap -- finally, it is able to snap to the Cube\n\n", "Crash when importing / working with big or multiple VDB's in Shaded or Rendered 3dView (GPU & CPU)\nOperating system: macOS-13.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 5700 XT 1.2\n\nBroken: version: 3.6.0 Alpha\n\n\nBlender crashes when using big VDB files or scattered VDB's.(clouds)\nIn the viewport, when scattering VDB files, it is only possible in wireframe view mode.\n- When switching to only GPU shaded or rendered mode blender crashes.\n- When switching to only CPU you are able to use wirframe and rendered 3dview as well as rendering the image.\nBut not shaded view!\n\nMacOS 13.3.1 CPU --> 64GB \nAMD Radeon Pro 5700XT GPU --> 16GB\n\nSingle VDB files up to 450MB are OK. \nBigger cloud VDB used = 2.8GB crashes right after or while importing.\nThe scattered clouds are smaller in filesize, but more of them used.\n\nWhen opening the files, it's then only possible in wireframe mode.\n\n3DViewport used without realtime compositor !\n\nSince this is to big to upload here, the VDB file is here for free to test: clouds/\n\nOpen latest MacOS Blender version, switch to wireframe mode and CPU.\nImport the VDB from the link above.\nNow try shaded & rendered 3dview with CPU and then GPU. \n\n\nCRASHLOG:\n```\nRead prefs: \"/Users/NURB/Library/Application Support/Blender/3.6/config/userpref.blend\"\nDevice with name AMD Radeon Pro 5700 XT supports metal minimum requirements\nMETAL API - DETECTED GPU: AMD Radeon Pro 5700 XT\nregister\n\nWARN (bpy.rna): source/blender/python/intern/bpy_rna.c:1342 pyrna_enum_to_py: current value '17' matches no enum in 'View3DShading', '(null)', 'studio_light'\nWARN (bpy.rna): source/blender/python/intern/bpy_rna.c:1342 pyrna_enum_to_py: current value '17' matches no enum in 'View3DShading', '(null)', 'studio_light'\n\n[MTLTextureDescriptorInternal validateWithDevice:]:1344: failed assertion `Texture Descriptor Validation\nMTLTextureDescriptor has depth (2088) greater than the maximum allowed size of 2048.'\n\n[1] 42841 abort /Users/NURB/blender-git/build_darwin/bin/Blender.app/Contents/MacOS/Blender\n```\n", "The display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) R7 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.11.1 27.20.12033.2007\n\nBroken: 2.93 as well as version: 3.0.0 Beta\nWorked: Haven't tested before 2.93.\n\nThe display will be damaged when the node editor in Fullscreen Area mode (ctrl alt spacebar).\n\n* Switch workspace to Geometry Nodes\n* Add a new Geometry Nodes modifier/datablock\n* Ctrl+Alt+Space to go fullscreen (not Ctrl + Space)\n* Select or move a node\n\nFile:\n[bug.blend](bug.blend)\n\nGIF：\n", "Regression: Crash on Start Up\nOperating system: Mac OS 12.6.9\nGraphics card: AMD FirePro D500 3 GB\n\nBroken: blender-3.6.3-stable+v36.d3e6b08276ba-darwin.x86_64-release.dmg\nWorked: blender-3.6.3-candidate+v36.71b55b491e9c-darwin.x86_64-release.dmg\n\nApp crashes at start up.\n\nClick on App icon, app attempt to start, crash. I restarted my computer with same results. Not opening app from a .blend file. Tried opening default app with same result.\n\n", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Blender crashes with certain geometries (e.g. tweaked Jiggly Pudding simulation demo file)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 4.0.0 Alpha\nWorked: Unsure\n\nWith certain geometries, Blender will freeze then crash. I have included a demonstration in the video attached below:\n<video src=\"attachment\" title=\"Jiggly Pudding Crash.mp4\" controls></video>\n\n1. Download the Jiggly Pudding demo from demo-files/\n2. Follow the steps outlined in the video attached above. The steps in the video are as follows:\n a. Open the Jiggly Pudding file.\n b. Select the Pudding and open a geometry node editor.\n c. Inside the Simulation zone there is a node with the title \"Scale\". Change the Scale from 0.85 to 10 or something higher.\n d. Open a 3D viewport (if you haven't already) and press play in the time line.\n e. Blender will freeze and crash.\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?" ]

[ "Solidify with fill 'only rim' results in wrong face loop cycle for certain topology \nWindows 8.1, NVIDIA GeForce GTX 645\n\nBroken: 2.73a\n\nWhen I use *Rip* on plane with *Solidify* and *Bever* modifiers applied, Blender crashes.\n\nCreate plane and subdivide once. Add *Bevel* and *Solidify* modifiers (Solidify on top). Check *Only Rim* from Solidify modifier. Select middle verticle and rip (V). Use Rip again and Blender will crash.\n\nJust open attachment *rip_crash.blend* and press V.[rip_crash.blend](rip_crash.blend)\n" ]

[ "The arrows for expanding N/T panel are now drawn when using cycles and render border exists in the viewport\nOperating system: Linux-5.15.0-78-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro K5100M/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 390.157\n\nBroken: version: 4.0.0 Alpha\nWorked: never...? 3.3.9~4.0 all broken like this\n\n\nThe arrows for expanding N/T panel are now drawn when using cycles and render border exists in the viewport.\n\nIt's only drawn once and then disappears. Moving the viewport will show it again for 1 redraw and then it disappears again.\n\nNot _that_ much of a problem, but if you are just using mouse/pen to find it during render preview it's kinda inconvenient.\n\n\n- Switch to cycles\n- Set a render border with `ctrl-b`\n- `Z -> Render Preview`, the arrow flickers for 1 redraw and then disappears.\n\n", "Inconsistent behavior of knife tool\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon(TM) 535 ATI Technologies Inc. 4.5.13540 Core Profile Context 25.20.14002.1\n\nBroken: version: 2.93.0 Alpha, branch: `master` , commit date: `2021-03-24`, hash: `26b45448abf`\n\n\nAfter confirming the cut ( hit `space` ) , sometimes one or more drawn knife edges disappear ( problem seen with edges . verts does not disappear )\n\n - Select default cube ( any mesh ) \n - Move to edit mode \n - Select knife tool \n - draw cuts with knife tool . Issue is more predictable when initial and final verts of a cut are closer and end vertices near the center of face\n```\n ( not necessary though ) \n```\nVideo :\n( Unpredicted behavior is visible from 13th sec )\n\n [Blender 2021-03-25 14-52-57.mp4](Blender_2021-03-25_14-52-57.mp4)\n\n", "Particles on Faces/Volumes with grid does not respect zero gravity\nSystem Information\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GTX 1650\n\nBlender Version\nBroken: 3.0.0 Release candidate, 2.93.4\nWorked: Not sure\n\nParticles on Faces/Volumes with grid does not respect zero gravity\n\n1. Open a default scene and remove the default cube\n2. Add a plane\n3. Add a particle system and change the emission to Faces or Volumes and Distribution to Grid\n4. Change the Gravity to 0 in Field Weights\n\nExpected result: The particles generated needs to move up\nObtained result: The particles generated sticks to the plane\n\n", "GN: Delete Geometry node hides edges in some cases\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.2.0 Alpha\n\nHard to describe this one more abstract..\n\nI start with a mesh line primitive (0,0,0) (0,1,0) and extrude it **n** times along **x** to get a grid.\nNow I try to delete all points with a distance from the **y** axis greater than **d** \nWhenever **d** lies between the first and the last extrusion, the edges of the starting primitive are not displayed.\nIt shows up in the spreadsheet however and reappears if I apply the modifier and tab into edit mode and back \n\n[2022-02-05 19-27-50.mp4](2022-02-05_19-27-50.mp4)\n[del_geo_node.blend](del_geo_node.blend)\n\n", "object display as wire , invisible when overlay is turned off \nwin 10\nintel i5\namd radeon \n\nblender 2.8 \n6b39dc7672eb\n\n\nNot sure if it's abug or intended behaviour \n\nWhen an object is set to wireframe ( object properties , viewport display ) , when overlays is turned off , the object is not shown ", "Wireframe not visible with X-ray in weight paint mode.\nOperating system: Win10\nGraphics card: GTX 1070\n\nBroken: 3.0.0\nWorked: 2.93.6\n\nWireframe on other side of mesh can't be seen through faces when x-ray is enabled.\n\n[#94704.blend](T94704.blend)", "weird viewport visual glitch\nOperating system: Windows 11 64 bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti Gaming X Trio\n\nBroken: version: 3.3.1\nWorked: cant bother sorry\n\nits like the position of the viewport has an offset relative to the orientation of the camera, and the viewport has a set size and cant change.\n\nfirst go to the layout workspace and have an animation playing (must have an animation playing for the bug to happen), then create a new viewport by sliding it like im doing in the video. then change the viewport into rendering mode like im doing in the video and when you resize the viewport, it has a set size and cant be changed and the position of all parts have an offset according to the position and orientation of the camera.\n\n", "Wireframe opacity slider does not work.\nOperating system: Windows 10\nGraphics card: gtx1060\n\nBroken: 3.1\nWorked: \n\nWireframe opacity slider does not work if smooth wires is turned off.\n\nopen preferences>viewport\ndisable smooth wire overlay\nsave preference\nset viewport to wireframe shading\nin the overlay panel in viewport drag the wireframe opacity slider, the wire color will fade to black, the opacity won't change.", "Hiding Armature in Outliner while in Pose Mode, leaves viewport without ability to select or exit the Pose Mode.\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.39\n\nBroken: version: 3.0.0\n\nWhen Armature is hidden via Outliner in Pose Mode, the selection, active object, and the Mode remains on that armature, not allowing to select anything anymore. Same happens with Meshes and Edit Mode, but one is still able to exit the Edit Mode. I assume it's likely that one either shouldn't be able to hide the object one is in Edit/Pose mode with, or the Mode probably should be exited upon hiding it's object. Or, at least, switching the Mode off shouldn't be disabled if the object is considered still active/selected.\n\n[armature.blend](armature.blend)\n - Select Bone,\n - Press Disable in Viewports for Armature object in Outliner,\n - > Can't select other objects in viewport now, or exit the pose mode.", "Particle systems on a moving emitter with particle settings start/end outside the animation frame range showing up in wrong place intermittently\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.0.1\nWorked: xx\n\n[Desktop 2022.02.10 - 14.44.35.08.mp4](Desktop_2022.02.10_-_14.44.35.08.mp4)\n\nRepro steps with particle_bug.blend (attached)\n[particle_bug.blend](particle_bug.blend)\n1. Press play, observe:\n - on the initial frame of the animation, a cubic volume of particles spawn at the initial position of the cube\n - when the animation loops, the trail of particles disappears\n**This is the behavior I believe is a bug.**\n\n2. Change the animation start frame from 40 to 0, and let the animation play through at least one full loop.\n3. Change the animation start frame back to 40, and observe:\n - on the start frame of the animation, no cube of particles appears at the initial position of the cube\n - when the animation loops, the trail persists with each particle seeming to remain in its existing location.\n**This is the behavior I believe is intended when using duplicate particle systems with non-overlapping timespans to create the illusion of looping particles.**\n\n4. In the particle properties tab on the right, select the 'during' particle system (instead of the currently selected 'pre' particle system), and observe:\n - the behavior from step 1 immediately resumes: the particle trail disappears and the cube of particles appears at the initial position of the cube on the first frame of the animation.\n**This is the easiest way that the bug can be reproduced predictably.**", "UDIM grid changes and enhancements\nThe UDIM tile grid behaves oddly/inconsistently in many circumstances for both configuration and display. This design tasks will hopefully a) enumerate the most egregious issues b) provide a place for artist feedback on the proposals c) document the ultimate decision for each item below.\n\nComplete\n- [x] The UV tile grid no longer disappears as soon as an image is loaded into the UV editor space (4fb7217043)\n- [x] [D11862](D11862): Provide a way to disable the grid entirely and respond to the Overlay toggles. Move current UI into Overlay panel as well. \n\nFuture design / discussion required\n- [ ] Should the tile grid only have manual/static dimensions or should it automatically adjust if the user moves a UV point outside the current dimensions of the grid?\n- [ ] Should the tile grid also be shown in the Paint/Mask/Viewer modes in addition to UV edit?\n- [ ] Should anything different be done about the grid when displaying non-square images?\n\nFeedback thread: 20136\n\nThis task will be used for general organization. Most feedback should be provided on the DevTalk thread above.", "Blender locks into Pose Mode if rig-object or the rig's collection is hidden\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.0.0\nWorked: 2.9 \n\nBlender locks into Pose Mode if rig-object or the rig's collection is hidden\n\nOpen Blender, add a rig.\nGo to pose mode, hide the rig object (toggle its viewport render or deactivate the collection the rig is in).\nBlender now stays in Pose-Mode unable to leave it without restoring rig visibility.\n\nIn 2.9 Blender automatically exits Pose mode in this scenario. (Desired behavior)\n", "Random rectangles 'missing' when rendering with optix + motion blur\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03\n\nBroken: version: 3.5.0\n\nEdit: I downloaded 3.5.1 and It still occurs there\n\nWhen I render a scene that uses motion blur with optix, there are randomly rectangles/sections where it skips straight to the background. Its random and only exists in some frames, and does not appear when using cuda. The object it appears on (or near) has motion blur disabled.\n\nIts very random and I'm not sure how to reproduce it in a simpler scene. I've had it happen in several different complex scenes and its always been an issue when ever theres an object that has motion blur disabled\n\nOptix with Motion Blur\n\n\nOptix without Motion Blur\n\n\nCuda with Motion Blur\n\n\n", "Resizing the Blender Window causes the interface to disappear\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nOperating system: macOS-12.6.3-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 455 1.2\n\nBroken: version: 3.6.0\nBroken: 3.6.1, 4.0.0 (Metal)\nWorked: OpenGL\n\nWhen resizing the Blender window the whole UI goes blank.\n\n\n- edit the layout by removing the 3D view\n- resize the Blender window\n\nSee `resizing-window-interface-disappear.mov`.\n\n***\n\n**Original report**\n\nNo on any one project, and doesn't always happen immediately.\n\nLiterally resizing the window nothing else. I do have magnet installed for windows management, that wasn't being used in this instance.\n\nI have a multi monitor setup, 3440x1440, 2560x1440 and the MacBook's internal display active.\nOnce in this happens the UI has only reappeared once so far and requires Blender to be closed and relaunched.\n\nI had OBS open at the time, I don't have to be recording for the incident to happen.\n", "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n" ]

[ "Orthographic Viewpoints Hidden Grid\nOperating system: Windows 7 Ultimate 64 bit\nGraphics card: EVGA GeForce GTX 780 SC ACX\n\nBroken: 2.80, 0b6dbbc306b0, 2019-02-10 00:16 to 790cb7799dcf, 2019-02-19 00:38\nWorked: Recent 2.80 builds around 8c8979067490, 2019-01-31 01:07\n\nIn previous builds, I could disable the grid and all three axes in the overlays menu in order to hide them in the user orthographic view. The grid would still appear in the top, left, right, etc. orthographic viewpoints when I click the interactive gizmo axes or use the rotate view navigation shortcut with axis snapping. In recent builds, the grid is now hidden in these viewpoints and the only way to make them visible is by enabling the grid or at least one axis in the overlays menu.\n\nI've tried File > Restore factory settings, but the bug persists in both builds I've mentioned. Unsure if this is a bug or a feature removal/update. Attached is my startup.blend file after restoring factory settings. I'm certain this worked in 8c8979067490, 2019-01-31 01:07 and before, but it doesn't work now even in that old build. Perhaps an update to the userpref.blend file by a recent build caused it to stop working? [startup.blend](startup.blend)\n\nIn the overlays menu > guides, disable the grid and all three axes. The grid is hidden in the user orthographic view and also (undesirably) in every orthographic viewpoint." ]

[ "adding drivers in the compositor always results in a dependency cycle which often causes blender to hang when reopening the saved .blend file.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.90.0 Alpha\n\nadding drivers in the compositor always results in a dependency cycle which causes blender to hang when reopening the saved .blend file.\n\n\nJust to clarify, the append issue I mention in the video only happens if you copy and paste 3d objects from a file with the dependancy cycle problem into a new file, save the new file, and then try and append that new file into another new file, in this instance it also results in a missing data block if trying to re-open the file you copied into.\n\n[compositor dependancy cycle on all drivers.blend](compositor_dependancy_cycle_on_all_drivers.blend)\n\n[2020-06-02 17-50-21.mp4](2020-06-02_17-50-21.mp4)\n\n", "Python variables becomes invalid when batch creating attribute layers\nOperating system: Gentoo Linux\nGraphics card: AMD WX 9100\n\nBroken: 3.2 and master\nWorked: I'm guessing this has been broken since attribute layers were introduced\n\nWhen creating new attributes layers via python, the returned attribute object will stop work after multiple layers are added.\nIt seems like the attribute layers might be reallocated and moved while the python pointers doesn't get updated when this happens.\n\nIn a python script, create multiple attributes for a mesh in a row and save the return value.\nNotice that if you add too many the previously returned variables will stop working.\n\nSteps to reproduce with the attached file:\n1. Click run script\n2. Notice that at2 through at5 is of length zero\n3. If you remove any one of the `new` calls the returned variables are valid.\n[attribute_error.blend](attribute_error.blend)", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Exclude 'Render Result' and 'Viewer' image types in the dropdown in certain contexts [Shader Editor, Compositor, UV Editor...]\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\ncompositor's image node doesn't output render result.\n\nopen attached file, go to compositor, hit render, click on split viewer, nothing appears in compositor backdrop.\n\n[comp image node bug.blend](comp_image_node_bug.blend)\n\nPS, shouldnt this node have the ability to select which render result slot and layers to ouptut? Not sure how to comp two render results together that are in different slots otherwise (without saving each slot out as multilayer exr)\n\n****\n\nAlso using an Viewer image type in a shader nodetree is known not to work for the same reasons (using data that is not available yet or running into recursion), see #76352\n\nSo proposed solution would be to exclude the Render Result and Viewer image types in the dropdown in certain contexts [Shader Editor, Compositor...]\n", "compositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: (4.0 alpha from a few weeks ago not sure of version as deleted now)\n\nCompositor blur node set to fast gaussian produces black output when fed a colour output from an EXR image.\n\n1. Open a new blend file.\n2. Go to the compositor.\n3. Drag in the image file attached below.\n4. Connect the resulting image node's 0_Image output to a viewer node and turn on the backdrop.\n5. Image will be shown.\n6. Now place a blur node between the image node and the viewer node.\n7. Set the x and y values of the blur node to 1 and the size to 1.\n8. Image will blur.\n9. Now change the blur mode to fast gaussian.\n10. Image will go completely black.\n\n[test-image](https://projects.blender.orgattachment)", "Movie clip playback FPS is reduced in 3DView.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.59\n\nBroken: version: 2.83 (sub 9)\nWorked: ～2.79\n\nWhen a movie clip is read into a background image and displayed on a 3D view, the FPS decreases in a sequence of 2K or more.Even in full HD, FPS decreases a little.\nThere is no problem if you play only with the movie clip editor.\nRegardless of file format or file size, resolution seems to be involved.\nThere was no problem if the resolution was dropped to 2k or less.\nEven if the sequence is full HD, the FPS will drop slightly. There is no problem if it is less than Full HD.\n\nBelow is a comparison with 2.79 under the same conditions.\n\n2.83\n[Blender 2020-03-18 21-57-40.mp4](Blender_2020-03-18_21-57-40.mp4)\n\n2.79\n[Blender 2020-03-18 21-56-03.mp4](Blender_2020-03-18_21-56-03.mp4)\n\n\n[#74814.blend](T74814.blend)\n\n\n- Open file\n- Play animation (and make sure it is not able to play at 1200FPS)\n# In properties editor, toggle Show Background Image\n\nFPS rate will drop significantly", "Asset Browser - Append (Reuse Data) without instancing collections doesn't add more objects\nOperating system: Windows 10 Home 64bit (10.0, Build 19044)\nGraphics card: Nvidia RTX 3080\n\n\nBroken: 3.2.0\n\nWhen dragging a collection item from the Asset Browser with \"Append (Reuse Data)\" and \"Instance Off\" it doesn't add the collection again, it moves one object and leaves the rest where they were.\n[Asset Browser Reuse data issue.mp4](Asset_Browser_Reuse_data_issue.mp4)\n\n1. Create a collection asset with at least two items inside\n2. Save that collection to your library (save file inside the correct folder)\n3. Open a new scene\n4. Drag your new collection asset into your scene with Append (Reuse Data) active\n5. In the tool window (not sure about its name) lower left turn off \"Instance\"\n6. Drag out another of the same collection asset\n7. It should now have moved one of the two items", "Exporting render pass as exr ignores pass selection\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: since 2.80\nWorked: 2.79\n\n\nExporting a pass (any other than combined) as single-layer exr from the render window always just saves the combined pass instead of the selected pass.\nIt works as expected while using other format options (jpg, tif, ...).\nThis behaviour started with 2.80. Blender 2.79 worked fine.\n\n[save_exr_pass_bug.blend](save_exr_pass_bug.blend)\nSimplified example with a cube.\n- press render (F12)\n- in the render window switch from Combined pass to DiffCol pass\n- save as exr saves the combined pass instead of the selected one\n- saving as jpg works as expected\n\n", "Render Result not applying the compositor if the region is cropped\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0\n\nWhen you render just a small region (to save time) and make the composite in full size (fullHD), it isn't taken into account in the final result. \nHaving the resulting file (in this case full size - fullHD) without the compositing taken into account, makes no sense.\n\nThis really limits the use of both *render region* and *Compositor*\n\nWorkaround is *File Output* node but that doesnt support video output.\n\n\nThanks and regards\n\n\n\n- Open attached file\n- render it and compare the compositor preview with the render result output\n\n[Test.blend](Test.blend)\n\n", "File Output node outputs incorrect dimensions in some cases\nOperating system: Linux 64-bit\n\n2.92\n\nWhen connected to certain composite node trees, the File Output node will output images with incorrect and unexpected dimensions. This appears to have something to do with the blur node, but I suspect the issue might occur with other nodes that alter the image buffer dimensions.\n\n[composite bug.blend](composite_bug.blend)\n\n - Open and inspect attached file\n - Adjust output file paths to whatever is convenient\n - Render a frame\n - Review the outputted image\n\n", "Files don't appear in File Browser while Asset Browser loads assets\nOperating system: Linux-5.8.0-59-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.14735 Core Profile Context 21.10\n\nBroken: version: 3.0.0 Alpha\n\nLinux: When opening a file or import a file while the Asset Browser loads assets, the files do not shown up in the File Browser. Only after all assets were loaded. This happens with at least the 4 lasts builds.\n\n\nOpen an Asset Browser with an asset library that takes a moment to load, open >File > Open , then the directory contents do not appear in the File Browser\n", "Object Info node random output doesn't work properly\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13399 Core Profile Context 0\n\nBroken: version: 3.6.2\nWorked:\n\n**Short description of error and steps for others to reproduce the error**\nI have a scene with many collection instances of a collection containing a car and its wheels. The car has a material on it with its base color being controlled by an object info node's random output:\n[![enter image description here][1]][1]\n\nEverything looks good as long as I am in material preview with the overlays turned off:\n[![enter image description here][2]][2]\n\nBut with the overlays turned on(or sometimes the other way around) or if rendered using the EEVEE render engine, all the cars will have the same color.\n[![enter image description here][3]][3]\n\nHere is the .blend file:\n4whyzTYK#LYLMOGpAT3VvUi4j73Jg63W2p8sG_HRQ8L3E_A107z0\n\n [1]: Api9y.png\n [2]: XZ0Gz.png\n [3]: OeeZJ.jpg\n\n", "Sequencer doesn't reflect source range in strip display correctly\nWindows 7\n\nBroken: 2.78 Release\n\nWhen the length of a render source is modified, the display in the strip display doesn't show it. The info 'Original frame range' is correct though.\n\n1. From the default scene, create a 'link object data' copy (although i guess the type doesn't matter)\n2. Go back to scene 'Scene' and set the end frame to 100\n3. Go to scene 'Scene.001', open sequence editor and add scene 'Scene'. It will now show a strip of 100 frames length.\n4. Go back to scene 'Scene' and change the end frame to 50\n5. Go back to scene 'Scene.001' \nThe Sequence Editor will still show a green bar 100 frames long, although the info in the properties panel tells the correct info: Original frame range 1-50 (50).\nMore importantly, you can drag the right grabber of the strip to the right and it will still paint 100 frames green and the rest grey/transparent, although the 100 frames don't have any meaning no more - it was just the length it was created with. You can also unlink the strip from the original scene and relink it again, it will still paint 100 frames green/valid.\n\nMaybe this is a bug, an oversight, maybe even intentional, I don't know. \nI don't think a .blend file is necessary in this case, but I will upload one, if desired. \n", "Sequencer: transforming strips with overwrite enabled sometimes shuffles\nThe overwrite option sometimes shuffles the strips.\n\nWith `838b6ec48af6fb767089784193d8525c5f5faf13` (current master), and the attached file, the following error can be observed.\n\n- `G` key.\n- Type in `654`.\n- Press Enter to confirm.\n\n... if this doesn't shuffle the strips (so one strip is placed above the others), press Ctrl-Z and repeat the steps above.\n\n[sequencer_overwrite_sometimes_shuffles.blend](sequencer_overwrite_sometimes_shuffles.blend)\n\n", "Splitting strips will change image output\nOperating system: Windows 8\nGraphics card: 550Ti\n\nBlender Version\nBroken: 2.93.0 Beta\nWorked: Not sure\n\nSplitting strips with \"hard\" method will change image output.\n\nAdd movie or image sequence to VSE\nSplit strip by pressing Shift + K\n\nImage will change\n\n" ]

[ "2.93 file output node broken with more than 4 inputs\nOperating system: win10\nGraphics card: 2070 super\n\n2.93 4/6\n\nCaused by 6524ceb8cf\nnote #87292 might be a duplicate but has slightly different symptoms.\n\nfile output node doesnt write to folder\n\n\n[file_output_node_bug.zip](file_output_node_bug.zip)\n\nStep to produce :\n- extract zip file\n- `ctrl + f12` to render animation\n- it will render `.png` to `output_3d` folder and render `.exr` to `output_comp/test/`\n- add an Input to the `File Output` node (connected or unconnected does not make a difference)\n- it will render `.png` to `output_3d` folder but won't render `.exr` to `output_comp/test/`\n\n---\nOriginal steps:\n1, go to compositor\n2. create file path\n3. render\n4. no file in the path\n---" ]

[ "Geometry Node Crash\nOperating system: macOS-11.6-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon HD - FirePro D500 1.2\n\nBroken: version: 3.6.2\n\nGeometry Node crash when I try to add a node to the default Cube.\n| Node Setup: | Crash Log: |\n| --- | --- |\n|||\n\n- open blender\n- open the geometry node workspace\n- With the default cube selected, add a new Geo Node setup\n- add a node using the menu or Shift A\n\nBlender crashes.\n\nIf I delete the cube, add a plane, and add the geo node to the plane, blender does not crash.\n\n", "FADE INNACTIVE GEOMETRY MODE doesn't work properly with COLLECTION INSTANCES\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\nBroken: version: 2.91.0 Alpha\n\nI really like this mode, but it feels likeit not completely done. It's not work with collection instances at all.\nHere is was my expectations and what it looks like currently: \n\nAnd even instances from other scenes ignore this mode too. Will be cool if it(instances) will work in stream ideology of this mode\n\n\nOpen this file [FADE INNACTIVE GEOMETRY DOESN'T WORK PROPERLY WITH INSTANCES.blend](FADE_INNACTIVE_GEOMETRY_DOESN_T_WORK_PROPERLY_WITH_INSTANCES.blend) and select (one by one) buttom figures (cone/torus/cube) and after selecting each one - press Tab.\nYou will see that instances ignores this mode\n\n", "Seemingly no way to remap \"use tool\" button?\nBroken: 2.80+\nWorked: 2.79\n\nSee 599\n\nThere doesn't seem to be a way to remap or disable the button which activates the tools selected by the buttons found in the T panel. Sometimes this button conflicts with the 2.7x keymap. For example, in the node editor, left tweak *always* applies the selected tool (box select by default), which prevents all the 2.7x Left Tweak shortcuts from working\n\n\n[27_28_keymap.blend](27_28_keymap.blend)\n\n1. Open the file with --factory-startup\n2. Go to the keymap section in the preferences\n3. Select the 27X preset\n4. Try to use the Shift+Left Tweak shortcut to add a reroute node\n5. Box select will be invoked instead", "Data Transfer doesn't work in some situations (geometry nodes modifier preceeding the Data Transfer modifier)\nOperating system: Windows 10\nGraphics card: Nvidia GeForce GT960\n\nBroken: 3.5.0 (2023/01/11)\n\nData Transfer does not work on geometry generated by Geometry Nodes\n\nError is set up in the attached file:\n\n[Color Transfer Test.blend](Color_Transfer_Test.blend)\n\nDoesnt work in `Material` or `Rendered` viewport mode either.\n\n[Color Transfer Test 2.blend](Color_Transfer_Test_2.blend)\n\nI don't know if it's related (it feels like it is) but even setting color inside a geometry node (on geo node created meshes) doesn't work in Material or Rendered viewport modes.\n\n[GeometryNodesColorBug.blend](GeometryNodesColorBug.blend)", "Geometry Node: Sculpt mode doesn't cause update due to editing\n## SIMPLE REPORT:\n\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha\nWorked: Never\n\n\nObjects with geometry nodes do not update if dependent on the object that is currently being sculpted.\n\n[2023-01-14 13-13-37.mp4](2023-01-14_13-13-37.mp4)\n\n\n1. Duplicete default cube.\n2. Add Geometry Node tree on copy, add `Object Info`, choose other one cube, connect geometry to group output.\n3. Select other one cube, go to sculpt mode, do anything.\nCube with geometry node does not according to sculpted one\n\n## USER REPORT:\n\nOperating system: Windows 10 Pro\nGraphics card: Geforece RTX 2080\n\nBroken: 3.4.1 Stable\nWorked: not sure\n\n\nGeometry nodes network is not updating when in sculpt mode. It's updating fine when in edit mode.\n\nI have nodes basically adding differences in point positions from one mesh to another -\n\n\n\n\n[sculpt_mode_update.blend](sculpt_mode_update.blend)\n\n\n\n\n\n- Create an object(=A) and add a geometry nodes modifier\n\n- Duplicate the object(=B), and use it's object info in the first objects geometry node\n\n- Connect object B geometry, position and ID into a sample index node, sampling a vector on a point\n\n- Subtract the vector coming from the sample index from object A's position\n\n- Connect the result to the offset\n\n- Try moving verts on object B in edit mode and see object A updating\n\n- Try moving verts on object B in sculpt mode. Object A is only updating when switching from sculpt mode back to object mode.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Breaking nodes API changes for 4.0\n- [x] Remove `Node.width_hidden`\n- [ ] Complete \"Spline\" to \"Curve\"/\"Curves\" rename in geometry nodes\n- [ ] Stop storing node locations relative to their parents\n- [ ] Use a separate type for internal links (in RNA too) (see [D16960](D16960))\n- [ ] Use a separate type for node group interface inputs and outputs and node sockets\n- [ ] Use dynamically allocated `char *` array to store string socket default values", "Delete geometry node performance regression writing to multiple vertex groups in 3.1\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.1.0\nWorked: 3.0.1 and older\n\nCaused by f5e5a0987a\n\nUsing a combination of Delete Geometry node along side the Armature modifier makes the node run slower and slower the more vertex groups armature is using. The difference is an immense drop from 144fps back to 8fps using the same .blend file in 3.0.1 and 3.1\n\n[Delete Geometry + Armature 3.0.1.blend](Delete_Geometry___Armature_3.0.1.blend)\n\n[Delete Geometry + Armature 3.1.blend](Delete_Geometry___Armature_3.1.blend)\n\n**.blend file overview**\n\n\nI would argue that this bug is a high priority issue and makes a lot of the character animation workflows impossible to use in 3.1 .\nDelete Geometry Node has been a replacement for the Mask Modifier ever since Geometry Nodes was introduced, it is a crucial part of a lot workflows. \n\n\n\n**More information if needed :**\n\n- Order of the modifiers does not matter\n- Vertex groups on the mesh have to be used by the armature for it to take an affect, however the vertex group used to delete the geometry is not being used by the Armature\n- The issue seems to be that the Node is now checking every single vertex group instead of the single attribute given to it\n- The more vertex groups used by the armature the worse the performance\n\n\n\n", "Multiple Edge Loop Selection doesn't always work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0\nWorked: 3.3\n\nMultiple Edge Loop Selection (Shift+Alt+Select) will sometimes stop working until Shift is released and depressed again. Problem started in Blender 3.4 and did not exist in Blender 3.3 (tested).\n\n\n- Create a cylinder primitive.\n- Enter Edit Mode.\n- Attempt to Edge Loop Select multiple edges by holding Shift+Alt and clicking on them. Occasionally, this function will simply stop working after the first few selects -- no more edge loops can be selected -- until Shift is released and depressed again.\n\nThis problem does not occur for general multi selection (when only Shift is held).\n\n", "Weight Paint Vertex Selection Display issue\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: never really, more on that below\n\nWhen in weight paint mode with\n* vertex selection enabled\n* show wire enabled\n\nedges will not be drawn within the selection\n\n\n**The odd part**\nClicking in an empty space will get the wires to show again, but keep the vertices selected. \nThat's a behaviour that has changed from 3.1.2 to 3.2.2\nPreviously it deselected the vertices but didn't draw the edges\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n* Open the attached blender file\n* you can see that edges are not drawn between selected vertices\n* click in an empty space (important to click, not click drag)\n* vertices stay selected but wires are drawn\n\n", "Annotations shouldn't be shared among different Geometry Nodes\nOperating system: ubuntu 20.04\nGraphics card: cpu\n\nBroken: 2.93.0\n\nWhen you ad an annotation to a geometry node, by default the same annotations can be seen in all the other geometry nodes layout.\nThis is unexpected, since each geometry node layout should have its own annotations.\n\nAdd a geometry node modifier.\nWrite something with the annotate tool.\nDuplicate that geometry node modifier, erase the old nodes, the annotations, and you'll find out that you erased the annotation also from the first geometry node layout.\n", "Applying geometry nodes modifier create an empty material slot for no reason\nOperating system: W10\n\n3.4.1\n\nApplying geometry nodes modifier create an extra empty material slot for no reason.\n\n| Geometry node tree | Applyed mesh |\n| -- | -- |\n|  |  |\n\n1. Create an object\n2. Add a GN modifier\n3. Create some geometry inside GN and assign a material to it (or don't)\n4. Apply the modifier, you'll get an empty material slot on the object.\n\n", "Follow Active Quads affects on non-selected islands, when selected several objects\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.4\n\nWhen using Follow Active Quads, it is expected that it affects only the island(s) whose faces are highlighted. However, this works when one object is being edited, when editing several objects, the operator affects random islands of other objects\n\n[2023-01-18 05-07-25.mp4](2023-01-18_05-07-25.mp4)\n[untitled.blend](untitled.blend)\n1. execute Follow Active Quads first with one selected cylinder, and then several. The cylinders can be taken from the file above in order to shorten the time", "Node editor: Allow editing geometry node tree without context\nLike the \"Material/World\" toggle in the shader editor, add an option to allow choosing any node group regardless of the context.\n\n", "Copy and Pasted framed nodes jitter around when grab and drag\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0\nWorked: N/A\n\n\nWhen copy pasting framed nodes with Ctrl + C then Ctrl + V, then G to move by mouse, many nodes appeared to be jittering for unknown reasons.\n\nThis behaviour doesn't exist when G to move existing framed nodes or when duplicating via Ctrl + D.\n\n(the video compared the behaviour \"ctrl + c / ctrl + v / g to drag\" with \"ctrl + d drag\")\n\n[blender_1n2MKEk5wo.mp4](blender_1n2MKEk5wo.mp4)\n\nThis is important because I have a reasonable doubt that copy pasting framed nodes from 1 node graph to another will sometimes erroneously create invalid socket link due to this jitter. This larger problem is very difficult to reproduce, BUT here is a case where I believe such behaviour result in a \"2 link in 1 socket\" invalid setup (when grab them over other frame nodes).\n\n\n\n- Download the blend,\n- Use Select Box to select the Frame and all nodes inside,\n- use {key Ctrl C} then {key Ctrl V} to duplicate framed nodes in GN view,\n- {key G} to move nodes to see the then swimming.\nTry varying the Zoom if the problem is not noticed.\n\nNOTE: The problem is more noticeable by setting the `Noodle Curving` in Theme to 0\n\n[frame-group-jitter.blend](frame-group-jitter.blend)\n", "UV Editor Snap Active to Vertex is Not Working\nOperating system: Linux-5.19.0-38-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.0\n\nI can not snap active to vertex, no matter what I try it acts like it is in median mode.\n\n\n\n\nIn the startup file snapping is enabled. In the uv editor try to move the selected vertex to snap to another vertex. Or try to snap a face instead, same issue. Sync mode on/off doesn't change the behavior.\n\n" ]

[ "New reroute node generated with cut are not active\nOperating system: macOS-12.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.3\n\nBroken: version: 3.3.0 Alpha\n\nAdding label for reroute doesn't work immediately after adding them through shortcut\n\n- Open default scene\n- add GN tree\n- Add reroute in existing noddle with {key Shift RMB}\n\nIf i add a reroute by ctrl-right mouse hole -> F2, i cannot rename my reroute\n\n[reroute naming works partially.mov](reroute_naming_works_partially.mov)\n" ]

[ "Timeline scrubbing is laggy when Preview tab is open in Material Properties\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.0\nWorked: N/A\n\n\n\nHaving the little preview tab open in Material Properties when scrubbing the timeline causes heavy lag, noticeable even on the default cube file. \n\nThe material can be a mesh material or a grease pencil material, but the result is the same.\n\nVideo example: watch?v=1Fw6Y-XzMyE\n\n", "Crash/Bugs with material's Surface dropdown + undo\nOperating system: Linux-4.15.0-45-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 4)\nAlso confirmed to crash in 2.80.\nWorked: 2.79b does not crash (works as expected)\n\nWhen changing the surface/volume in material properties (the list view of the shader nodetree) and undo, opening the dropdown directly afterwards again can crash Blender.\n\n- Download repro blend file (it's just a Cube with a Principled BSDF) [shaderlistRepro.blend](shaderlistRepro.blend)\n- In Properties Editor, click on Surface (Principled BSDF) and select any option in the dropdown\n- Move your mouse over the Surface dropdown and keep it there!\n- Press CTRL+Z to undo\n- Click on the Surface (Principled BSDF) dropdown again (your mouse may not leave the dropdown box)\n- Blender crashes\n\nThe same happens when done with the Volume dropdown instead.\n\n[2020-02-24 15-09-16.mp4](2020-02-24_15-09-16.mp4)\n\n**Possibly related issue**\nIn another file, doing the exact same steps as above has some other effects:\n- Either it spawns this popup (clicking any of these options crashes Blender) \n- Or it spawns a blank popup \nThis is the reproduction file which caused this: [shaderlistRepro2.blend](shaderlistRepro2.blend)\n\nWhich effect happens is really inconsistent and I am not sure how to reproduce one or the other.", "Crash while baking the Line Art modifier\nOperating system: Windows 11\nGraphics card: RTX 2070\n\nBroken: 7c2dc5183d03\n\n\n\nI get regular crashes when baking Line Art modifier in relatively complicated geometries. \n\nI can't provide my project file. I am hoping that the crash log will give insight into this bug.\n\n", "Selecting vertices and centering the model crashes Blender\nOperating system: Windows 10\nGraphics card: RTX 2070 \n\nBroken: 03015a9b222e\n\n\nSelecting some vertices and trying to center the selection crashes blender. See the crash log\n\n[crash.txt](crash.txt)\n\nOpen the attached .blend\nSelect the object\nGo into edit mode\nSelect all vertices\nCenter (press Numpad .)\n\n\n\n\n\n[_13122021_2147_15.blend](_13122021_2147_15.blend)", "Blender development todo list -- Render\nNOTE: this is a direct dump of Render (without cherrypicking the valid items)\n\n### Render & UI\n\n- [ ] While rendering, manipulating images (like reload, resizing generated) can still crash Blender. Better image \"owner\" locking is required for 2.5 (#28477)\n- [ ] While rendering, several UI changes can cause crashes (#24758)\n- [ ] Rendering can't really use normal scene data if ui is interactive without causing all kinds of trouble, for examples and related issues see the item above this one.. and the reports (#26535)\n- [ ] Renaming scene leads to missing rendered result in image editor and compositor (see (#30222))\n- [ ] Rendering with File Output nodes could produce unwanted output images, see (#38605)\n- [ ] Shaded draw mode (using render code for vertex colors) is most certainly not coming back\n- [ ] Color Management can be communicated better, like when sampling colors in Image Window it confuses (could indicate such). Color Management also wasn't added backward compatible, disabling it gives dark results.\n- [ ] Compositor \"file out\" node doesn't work for FSA, and as color management troubles too.\n- [ ] FSA render uses temp files with names preventing other Blender instances to render too. (#28314)\n- [ ] Texture nodes have been implemented by recursively (backwards) calling parent nodes, this gives issues for viewers, previews and threads in general.We will try to keep it stable, but the functionality for this is going to replaced with a better shader system in 2.6. (compositor and material nodes call nodes forward, sorted on dependency. Each node is only called once this way).\n- [ ] Render display in Image window, for a window previously showing UV editor, doesn't restore correctly. (#26828). Code for this is too much spread around and fuzzy, needs full revision.\n- [ ] Object transform is not possible during rendering #37019\n- [ ] Don't render and warn when a driver or pre-render script can't be executed, a texture is missing, physics are not baked. Needed e.g. when renderfarms have scripts blocked.\n\n### Node Textures\n- [ ] Grouping texture nodes affects on data range #45696\n\n### Baking\n- [ ] add option to smooth vertex colors as a post process after baking #35066.\n- [ ] Baking to a low-res textures might miss pixels which lies on the UV island boundary #37681\n- [ ] Vertex baking might cause AO artifacts #44178\n- [ ] Support dupligroups #43553\n- [ ] Modifier produces non deterministic effects #42015\n- [ ] Update Blender side baking to support different topologies needed for adaptive subdivision #49405", "Crash with animated displacement modifier in Texture paint mode while playing\nAMD Ryzen 5 2600, 16GB ram\nWindows 7 64bit\nNvidia GTX 1060 6gb (driver version 416.34)\n\n2.79b\n\nI intend to paint a heightmap interactively. So i keyframed a displacement modifier (2 frames) on a subdivided plane and assigned a texture.\nPlaying the timeline should now refresh the modifier every frame. \nPainting in the UV-editor this way works fine, but switching to texture paint mode and painting on the mesh directly crashes blender after about 0.5seconds.\n[HeightmapPaint.blend](HeightmapPaint.blend)\nI attached an example file.\nHit play and in the uv editor paint on the noise texture. This works okay.\nNow switch to Texture painting in the 3d viewport. The moment a stroke is applied to the mesh it should crash (it does consistently for me). ", "Blender 3.3 crashes on importing external .exr file on compositor\nOperating system: Windows 11 x64\nGraphics card: gtx 650 ti\nprocessor ryzen 9 5900X\n\nBroken: tried 3.3 LTS (september 7, 2022 release) and also 3.2.1, but had this failure before in previous builds.\n\n**Short description**\nBlender immediately crashes after importing a multilayer .exr (generated in Houdini's Karma renderer) to the compositor. Example files attached\n\nOpen new blender scene, switch to compositor tab and check \"use nodes\". Then the error happens after either dragging and dropping the images or using the image node for import.\n\nThe crash seems to occur only when importing images with AOVs packed in, I attached one example that works perfectly but only has the color layer. I know this is a niche workflow but I'm out of options for compositing until I can upgrade my graphics card, sorry if this isn't really worth looking into.\n\n\n\n", "VSE (Video Sequence Editor) scene strips have very slow playback in both Material preview and Rendered mode.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Alpha\n\nAdding the 3d scenes to the VSE and turning Material Preview or Rendered mode are making the playback very slow.\n\n1. With the default scene opened create a second scene.\n2. Switch to the Video sequencer.\n3. Add a first scene to the timeline.\n4. Switch \"Scene strip display\" to Material preview or Rendered.\n\nThank you.", "Regression: Crashes when uses preview or final render modes\nOperating system: Mac Os Monterey 12.6.1\nGraphics card: AMD Radeon R9 M380 2 GB\n\nBroken: blender 3.6.2\nWorked: Blender 3.4.1\n\nBlender 3.6.2 crashes on MacOS when you change between preview or final render modes. I Think is a problem related with the Realtime Viewport compositing. I think it is not enabled at all on MacOS but maybe developers did not do it correctly and some render features are requesting missing elements.\n\nSimply make 3 or 4 render previews and then press F12 to obtain a final render (or viceversa). Blender Crashes immediately.\n\n", "Blender 3.4 Random Crashing Since GPU Replacement\nOperating System: Windows-10-10.0.19044-SP0\nGPU: NVIDIA GeForce RTX 3060/PCIe/SSE2 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.0, branch: blender-v3.4-release\n\n**Short Description**\nI have replaced my RX580 with an RTX3060 earlier and ever since that replacement, I have been having constant crashes whenever I attempt to use Blender, do note that I've been in edit/object mode during these crashes as I'm working on a subd model, I have tried a handful of fixes such as upping TDR values but it didn't seem to fix the issue.\n\nRyzen 5 2600, RTX3060, 16gb RAM, no temperature exceeds 60 degrees Celsius and nothing is active besides Blender 3.4 along with addons I have installed.\n\nHere are the logs I get when I run Blender via the gpu debug cmd: \n\nEdit: I did try disabling UV Packmaster as per the error logs, but that didn't stop the crashing.\n\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n[gunflipped.crash.txt](gunflipped.crash.txt)", "Crash when rending animation w/simple physics sim\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0\nWorked: Spinning beach ball in 3.1 Alpha\n\nWhen selecting \"Render Animation\", the Rendering window starts to draw, and then the app crashes.\n\n\nFile attached. Just load and Select Render Animation.[simple-physics-crash.blend](simple-physics-crash.blend)\n\n", "not possible to make multiple fabrics with different properties collide\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.1.0\nWorked: n\n\n1. By default, it is not possible to make multiple fabrics collide\n2. Use \"jion\" to combine multiple fabrics to generate collision, but it will lose different cloth properties at per object.\n3. Adding collision modifier while using fabric modifier will lead to very unexpected results.\n\nI have created a simple example to reproduce this problem.\n\n - > open the file\n [test_some_cloth.blend](test_some_cloth.blend)\n- > paly animation.\n\n", "Extremely frequent crashing when using the compositor. Especially when using the glare node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.99\n\nBroken: version: 3.6.2\nWorked: I believe it was far more stable before the realtime compositor implementation. (Blender 3.3-ish)\n\nBlender crashes extremely frequently when using the compositor on my system, especially when the glare node is being used at all. Does not seem related to vram or system specs, and looking through logs has not come up with any errors - it just closes.\n\nAdjust compositor glare node values with the viewer enabled. It seems to crash within a minute of doing so, usually sooner.\n\n", "Cycles X material preview using 100% of cpu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.0\n\nUsing cycles X, opening the material preview causes my computer to lag and drop in FPS\n\nCreate a new material and open the material preview with cycles x\n\nFor a new scene with default cube and default material, preview render completes in about 5 seconds.\nWith Beckmann glass it's ~10 seconds.\nWith Multiscatter GGX Glass, ~35 seconds.\n\n(Size of preview render: 134x150px)\n", "Shader not working on Mac blender 3.5 - works in Windows\nOperating system: macOS-13.3-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.5.0\n\nI have been trying to install the Weight Paint Tools paid addon weight_paint_tools?layout=profile&recommended_by=library\n\nThis worked fine for years, up till 3.5, now it crashes upon activation. The developer has attempted to update it for metal, but it still wont work. He's sent me a simplified script that he says should work without errors.. but still errors out. See attached blend file.\n\nRun the script\n\n\nRun the script\n\n" ]

[ "Blender crashes when dragging Material-Assets into the 3D Viewport\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.0 Alpha\nWorked: version: 3.0.0 Alpha\nCaused by e8027ec2a0\n\n\nBlender will crash instantly, as soon as I drag the material asset from the asset browser over the boundry of the 3D viewport. \nThe crash happens exactly when the dragged material icon preview reaches the border to the 3d viewport, but not other editors / panels. If i drag it over other editors, blender doesn't crash.\n\n\n- Open the asset browser on the left side of the 3d viewport;\n- Grab a material-asset from the asset browser and try to drag it to the right into the 3d viewport;\n- Blender will crash instantly wenn crossing the dividing line between the two panels.\n\n\n\n\n\n\n\n[Material Asset dragging crash - Marcel Freyer.blend](Material_Asset_dragging_crash_-_Marcel_Freyer.blend)" ]

[ "Nodes to convert between cartesian/spherical coordinates\nThere should be nodes to convert between spherical and cartesian coordinates in a standardized way.\n\nThis point came up when discussing [D12746](D12746) .\n\nThey are multiple design aspects to be figured out:\n- Node layout\n- Naming and Scope\n- Units\n- Value Ranges", "Geometry Nodes: 3D Viewport Overlay Statistics don't respect Viewer Node\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.11\n\nBroken: version: 3.4.0 Alpha\n\n\nThe geometry output by the preview node is not taken into account by the overlay scene statistics:\n[2022-09-30 11-35-43.mp4](2022-09-30_11-35-43.mp4)\n", "Node Operators: Add Selection input node\n_No response_\n\n", "Mesh: Subdivide op flushes selection too eagerly\nBroken: 2.92 master\nWorked: N/A\n\n\nThe Subdivide operator selects geometry that it shouldn't. Consider this example:\n\n\n\nIt looks as if the op flushes selection a bit too much. Note that the 'Expected' selection is valid selection in edge mode, as the edge rings around the rims are **not** selected. Those edges should neither participate in the op, nor be selected as the result of it, if vertex selection mode is not enabled.\n\nA better example:\n\n\n\n...here in face mode, a lone edge is getting selected by the op.\n\n\n1. On the default cube, in face mode select top and bottom faces, inset and bridge them.\n2. In edge mode select vertical edge rings.\n3. Subdivide.\n\nAlternatively, load this simplified example file:\n\n[subdivide_selection_issue.blend](subdivide_selection_issue.blend)\n\n...and Subdivide. Resulting selection of the middle face is unwarranted.", "Geometry Nodes: Viewer overlay disappears when enabling In Front\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nWhen enabling \"In Front\" in the Viewport Display options of an object, which currently has a geometry nodes viewer overlay, that overlay disappears.\n\n| Viewer object: `In Front`: OFF | Viewer object: `In Front`: ON |\n| -- | -- |\n|  |  |\n\n1. Open the attached file in 3.4 or newer versions.\n2. Make sure the viewer node is enabled in the geometry nodes of `Plane.001`.\n3. Under Viewport Display, toggle `In Front` for `Plane.001`.\n\n[bug_report.blend](bug_report.blend)\n", "Buffering of nodeGroups is not working correctly\nOperating system: Fedora 31 (5.3.16-300.fc31.x86_64)\nGraphics card: Intel Corporation UHD Graphics 620 (rev 07)\nNVIDIA Corporation GP108M [GeForce MX150] (rev a1)\n\nBroken: 2.81\nWorked: (optional)\n\nIn compositing mode, when connecting output of a Value node to Y input of Translate node, every thing works as expected.\nBut when putting the Value node to a group and enables the `Buffer Groups`, connecting the output of group (which is output of Value node inside it) to Y input of Translate node does not works as expected!\n\n\nOpen:\n[problem.blend](problem.blend)\n* F12 to update.\n* Note that the `Buffer Groups` option is enabled (SideBar).\n* Note that by disabling this option and updating the tree, node group will work again.", "Output UVs from mesh primitive nodes with anonymous attributes\nInstead of creating a named `uv_map` attribute on the geometry, they should be anonymous attribute field outputs. This brings up a few complications.\n- Currently we have no 2D vector socket. We probably want to avoid adding this for 3.0, so a 3D vector can be used for now. Automatic conversions will make versioning simple when we add a 2D vector socket, hopefully for 3.1.\n- The BMesh mesh primitive icosphere creates an `MLoopUV` attribute, this should be converted into a 3D vector anonymous attribute.\n\nThe output should be called \"UV Map\"", "Fields UI: Differentiate between dynamic attribute fields and anonymous attributes\nThere should be way to clearly tell the relation of a field to geometry in the nodetree.\n\n**Definitions**\n\n**Dynamic Attributes**\nThere input fields of attributes/derived data that can be evaluated on any geometry and change dynamically to changes that are made on that geometry. (E.g. Position, Normal, Index, etc.)\nThis type of field gets especially confusing when it is generated with an operation that includes a secondary geometry, which it relies on implicitly. (E.g. Raycast, Attribute Transfer)\n\n**Anonymous Attributes**\nOn the other hand there are attribute fields that depend on/are associated with a certain geometry and don't *change* throughout the node-tree, but are only propagated/interpolated. (E.g. Captured Attributes, Group Inputs)\nTheir evaluation only makes sense in the context of that associated geometry that they exist on.\n\n**The Issue**\nTheir difference in behaviour as to when in the node-tree the values are reevaluated can be crucial to understand what a node-tree is doing and can very easily cause problems and confusion.\nThis is why it should be easy to read in the UI what geometry a fields is associated with when making any fields connection, or when investigating the node-tree.\n\nThere are 3 different categories of fields that can result from this:\n- Fully dynamic: All referenced attributes are dynamic/derived data. They are not simply propagated through the node-tree but rather calculated whenever the field is evaluated in a geometry operation. This means that they change depending on the context of when they are evaluated.\n- Fully anonymous: All referenced attributes are anonymous. They are clearly associated with a geometry that they were created on and only make sense in the context of that geometry and any geometry that inherits this data.\n- Mixed: Some referenced attributes are dynamic and some are anonymous. The restricting factor for socket connection here is given by what geometry the anonymous fields are associated with. On the other hand the dynamic aspect of changing data is also something to keep track of.\n\n**Initial Proposal**\nThere are multiple possible ways to go about visualizing this. My idea is to create the least additional visual concepts necessary and show the information as it is needed.\n\n**Geometry Association**\nI think the most straight-forward to visualize the dependency of anonymous attributes with their associated geometry is to highlight compatible geometry while drawing a connection from an output socket carrying a field that depends on.\nThat can be done by highlighting all geometry connections starting from the first geometry socket that includes the anonymous attribute that was created last and branching off downstream. (E.g. thickening the noodle and adding glow)\nOn top of that input sockets could also be highlighted/greyed out depending on their compatibility.\n\nSocket selection would also help here, so that this wouldn't only happen as a connection is drawn but also for a selected socket.\n\n**Dynamic Reference**\nBy default, this would also already mark fully dynamic fields by not having any geometry highlighted visual. I do still think though that there should be an additional hint whenever a field carries a dynamic reference. For both fully dynamic and mixed fields. \nI think this could be done by altering the socket of all fields with dynamic references to have an additional outline with an offset.\n\n**Remarks**\n\n- When no input geometry is connected on a node, also don't grey out inputs\n- Node groups pose an issue in that what field is associated with what geometry needs to be marked. This could be derived implicitly/set by the user/following a convention.\n\n--- \nThere are many other ways this could be done, but as I am working with geometry nodes I am noticing more and more the need for this, so I wanted to make an initial push.\nFurther discussion and feedback, especially also from the UI team are welcome and requested.", "Selecting (or connecting) nodes in Compositor is malfunctioning when when monitors have different dpi\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 5)\n\nSelecting nodes in Compositor is glitching when when monitors have different dpi. This happens when Compositor is opened on both monitors.\n\n - In Windows 10 set custom scale on the second monitor in Display Settings > Scale and Layout, for example to 175%, so that each monitor has different scale.\n - Put one Blender window on each monitor (same Blender session).\n - Open Compositor in both windows. Enable nodes.\n - In the window with scale equal to 100% try clicking on the Composite node couple times. Selection will switch to the other node.\n[custom_dpi_compositor_bug.blend](custom_dpi_compositor_bug.blend)\n[custom_dpi_compositor_bug_02.03.2020.mp4](custom_dpi_compositor_bug_02.03.2020.mp4)", "Geometry Nodes socket is not showing relevant value info for current modifier\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.3.0 beta\n\nUsing many modifiers with the same GN node tree (multiple users) has some issue with data updating.\nIf you bring cursor over socket to see its value, then it shows only data from first GN modifier, no matter what modifier is selected at the moment. Seems to be only interface problem, as internally processed data is correct.\n\nIn attached file bring cursor over orange socket (Object type) and it will show same object for both modifiers, when in fact they are different.\n[socket_info_issue.blend](socket_info_issue.blend)", "Geometry Nodes: Rendered glitch with Image Texture and Scene Time\nOperating system: Linux-5.15.0-76-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.0\nWorked: Never\n\n**Short description**\nGeometry nodes that use single images or image sequences are rendered inconsistently but usually look normal in the viewport.\nHigh-res images seem to be more unstable.\nHaving a connected/unconnected scene time node in the geo node group while using an image sequence with any number of frames also makes the rendered image/animation more unstable.\n\n|Expected render|Occasional render glitch|\n|--------------------------|--------------------------------------|\n|| |\n\n\n**Reproduction steps**\nThis is the most unstable setup:\n\n1. Create new project\n2. in the image editor window add a new image with resolution of around 1080x1080 pixels and set the source an image sequence \n3. add geometry nodes modifier to the default cube\n4. follow this node setup; in the image texture node use the created image sequence \n5. Render animation\n6. some of the rendered images will be glitched\n\nI've also tested this approach with face extrusion or instance selection instead of deleting faces. The resulting renders were also glitched. \n\nInside of this zip file is a blender project with a similar setup along with some sample images:\n[geo node groups that use images are rendered inconsistently.zip](attachment)\n\nThis reddit post seems to be describing a similar issue:\ngeometry_nodes_rendering_glitch_info_in_comments/\n\nThe workaround with disabling geo nodes modifier in the viewport mentioned there seems to be working in a simple setup. In the above project from the .zip file it is less effective.\n\n", "Mismatch between nodetrees when creating a link does not throw error\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.6.0 Beta\nWorked: Tested as far back as 3.3.4 and no error was thrown\n\nWhen creating a node-link an error is not thrown if the node trees of `links`, `input socket`, and `output socket` are not all the same node tree or even the same type! It makes troubleshooting code sometimes difficult when no errors are thrown but with unexpected results.\n\nPaste the following into the text editor in Blender and Run it:\n\n```py\nimport bpy\n\nD = bpy.data\n\nnt1 = D.node_groups.new(\"NT1\", \"GeometryNodeTree\")\nnt2 = D.node_groups.new(\"NT2\", \"ShaderNodeTree\")\nnt3 = D.node_groups.new(\"NT3\", \"CompositorNodeTree\")\n\nnd1 = nt1.nodes.new(\"NodeReroute\")\nnd2 = nt2.nodes.new(\"NodeReroute\")\n\nnt3.links.new(nd1.outputs[0], nd2.inputs[0])\n```\n\n", "Nodes: Socket and title click detection is broken for multiple monitors\nOperating system: Windows 11 Home, Version 22H2, OS Build 22621.1265, 64-bit\nGraphics card: NVIDIA GeForce RTX 3060 Ti, NVIDIA GeForce RTX 2070 SUPER\n\nBroken: Blender 3.4.1, Blender 3.5.0 Beta (2cd7e70c18a8), Blender 3.6.0 Alpha (ef60b13c1f29)\n\n\nThe click detection for node sockets and titles does not work when using main windows in two separate monitors.\n\nThis issue is similar to 96255 , but I'm facing this issue even with UI scale = 1.0.\n\n\n1. Create a geometry node tree. Node socket/title click detection works properly.\n2. Create a new Main Window. Click detection still works.\n3. Move a main window to another screen. Click detection fails. Clicking and dragging sockets/titles triggers box selection. \n\n(See attached video)\n\nMain monitor: Dell U2720Q\nSecondary monitor: LG DualUp 28MQ780\n\n", "Geometry Nodes related memory leak and exception access violation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.5.1\nWorked: \n\nBlender freezes, memory usage spikes and eventually you get exception access violation crash.\n\nOpen attached file and enable Layer 3. Blender will freeze, memory usage will spike and eventually lead to exception access violation crash. Crash log is generated.\n\n[gnodes bug1.blend](attachment)\n\nTo stop crashing disconnect Twig Object from Object Info node. I think this started happening after I deleted the \"fir_twig\" object, but there was still a hidden reference in the Object info. However, I was not able to replicate this in a new file and the crash stops happening if I delete / modify some of the node groups, even in unrelated ways. I am pushing Blender to the limits and this is a heavily reduced file.\n\n", "Regression: Multi sockets on muted nodes display wrong internal noodle\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.29\n\nBroken: version: 3.5.0 Release Candidate\nAlso broken in 3.4\nWorked: 3.3.1\n\nWhen a node with a multi socket (e.g. Join Geometry or Mesh Boolean) is muted, the visual internal noodle goes from the last (bottom) input instead of the first (top) input, even though it is the top input that is actually passed through.\n| 3.3 | 3.5 |\n| -- | -- |\n|  |  |\n\n- Open attached .blend file or\n - Create a geometry node group\n - Connect two or more different inputs into a Join Geometry node\n- Mute the Join node\n\nObserve the discrepancy between the visualized noodle and the actual result in the viewport\n\n" ]

[ "Geometry nodes: Inverted socket do not output correct part of geometry\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.1.0 Alpha\nCaused by 3e92b4ed24\n\n**Short Description**\nInverted socket do not output correct part of geometry\nCheck the file and inverted part. It returns full mesh instead part of it.\n\n**Steps to Reproduce**\n- Open .blend file\n- Connect `Inverted` socket to Group output\n[Separate.blend](Separate.blend)\n\n[2022-01-07_08-24-52.mp4](2022-01-07_08-24-52.mp4)\n\n" ]

[ "Compositor: Viewport issues when Passepartout is off\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nComposition Mask is \"rendered\" wrongly in the viewport when the camera `Passepartout` is off.\nNote that the Compositor is set to Camera.\n\n\n* Open this file: [zoomed_out.blend](attachment)\n* Notice that the passepartout is disabled in this camera, but the viewport compositor is set to Camera.\n\nCurrent buggy result:\n\n\nThe mask only matches when the camera has `Passepartout` on:\n\n\n\nRelated: #111344\n\n", "VSE: Invisible and reversed transitions\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 2.93.0\n\nInvisible transitions(duration=0):\n\n\nReversed transitions, because of inputs are assigned in selection order:\n\n\nAbandoned attempt to solve both things:\nD10207\n\n\n", "CMD terminal stays open after opening blender\nOperating system: Windows-10-10.0.25247-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.5.0 Alpha\n\nI'm not sure why it';s happening but it's not happening for 3.3 version\n\n\n\n", "Audio Scrubbing bug\nOperating system: Windows 10 64-bit\nGraphics card: RTX 2070 Super\n\nBroken: (2.90, 2.91, 2.92 Alpha, 3.0)\n\nEnabling \"Audio Scrubbing\" with \"AV-sync, Frame Dropping, and No Sync\" causes an issue with animations in the 3D Viewport and Timeline \n(AV-sync issue)\n1. Open a default Blender file.\n2. Create basic animation with any mesh, just something to show keyframe movement. Frames 1 - 250 should be enough for this procedure.\n3. In the timeline window, click \"Playback\" and switch \"Audio\" to \"AV-sync\" and enable \"Scrubbing\". A sound file is **not** needed for this step.\n4. Hit spacebar. The timeline cursor and animation should move as intended.\n5. Hit spacebar again to stop the timeline cursor and animation.\n6. Now the tricky part! Move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and the timeline cursor will not move. Yet, the \"FPS counter\" in the top left corner and the \"Anim Player\" icon will stay visible as if the animation is playing.\n7. Press spacebar to stop the \"ghost\" animation.\n\n(Frame Dropping and No Sync issue)\n1. Using the same file from above, add a sound clip in the \"Video Sequence\" editor.\n2. In the timeline window, click \"Playback\" and switch \"Audio\" to either \"Frame Dropping\" or \"No Sync\" and enable \"Scrubbing\". A sound file **is** needed for this step.\n3. Hit spacebar. The timeline cursor, animation, and sound should play as intended.\n4. Hit spacebar again to stop the timeline cursor and animation.\n5. Same as before, move the timeline cursor in any direction on the timeline, then **instantly** hit spacebar again. It may take a few tries but when it does work, the animation and timeline cursor will move but the sound will not play.\n6. Hit spacebar to stop the animation.\n\nWith both examples above, issues only popped up when \"Scrubbing\" was enabled. Disabling it did not produce the same results.\n\n\n", "Operator: Play Rendered Animation no frame_preview_start for images\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.83 (sub 11)\n\nTopbar >> Render >> View Animation \n`bpy.ops.render.play_rendered_anim()`\n\nWhen using the View Animation operator it runs as intended with videos, however if you're using images as your render output, and using a preview range,\nthe operator will output from the Render Frame Start, rather than the Preview Frame Start. \n\nSo, unless your preview range included the first scene frame, the player will fail to start. \n\n\n**Steps to Reproduce**\nStep 1:\nEnable Preview Range in the timeline (click clock next to the Start/End numbers)\nChange the Start Frame (this is currently the Preview Start, not the Render/Scene Start)\n\n```\n Step 2: Option 1:\n in python window (or text editor) run:\n print(bpy.context.scene.render.frame_path(preview=False)) # Outputs Render Range\n print(bpy.context.scene.render.frame_path(preview=True)) # Outputs Preview Range\n```\n\n```\n Step 2: Option 2:\n Render the animation (3D Viewport Header >> View >> Viewport Render Animation)\n Topbar >> Render >> View Animation \n```\n\n\nRepeat Step 2, twice. \nOnce with your Render Output format set to any video format (AVI / FFMpeg)\nOnce with your Render Output format set to any image format (PNG / BMP / JPEG / etc)\n\n\n**Details**\n`\\2.83\\scripts\\startup\\bl_operators\\screen_play_rendered_anim.py` `line #117`\n`file = rd.frame_path(frame=scene.frame_start, preview=scene.use_preview_range)`\n\nThe function `bpy.context.scene.render.frame_path()` isn't doing anything with the `preview` variable, when the output is an image, so it just always return `scene.frame_start`\n\n`\\blender\\makesrna\\intern\\rna_scene_api.c` >> ` void RNA_api_scene_render` >> `static void rna_SceneRender_get_frame_path`\n\nThis function does one check for movies and different one for images. \nif it's image, it doesn't use the `preview` bool variable, and just use the scene's frame\n\n", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", " LineArt: (Collection) Issue for Cameras in Orthographic View\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.1\nChecked in Blender version 3.4.0 Apha, commit date: 2022-10-08 02:26 - same issue\n\nFor orthographic Camera without any shifts - Line art modifier (for a Collection) showing lines for objects behind other objects - which otherwise should not be visible. And some lines are not visible which should be.\nHappens with contours option in the Line Art modifier. Slight rotation on z axis solves the issue.\n\nNoticed issue with some specific frames on my complete blend file.\n\nOpen attached blend file and go to front orthographic view.\n\n[BugReport01.blend](BugReport01.blend)\n\n", "EEVEE is ghosting with viewport denoising enabled.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nHere's a viewport render:\n[EEVEE ghosting0001-0090.mp4](EEVEE_ghosting0001-0090.mp4)\n\nHere's what it looks like during playback if viewport denoising is enabled:\n[2021-10-23 17-07-44.mp4](2021-10-23_17-07-44.mp4)", "Physics: The default value for Format Volumes is nothing...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\n\nThe default value for Format Volumes is nothing...\nBlender will stop working if you try to let the Animation play. EDIT: Can no longer reproduce with Blender 3.0\n\nDo a Backspace (to reset to default) on \"Format Volume\"\n![2021-09-09 09_15_29-Blender_ [C__Users_raimund.klink_Downloads_adaptive bug2.blend].png](2021-09-09_09_15_29-Blender___C__Users_raimund.klink_Downloads_adaptive_bug2.blend_.png)\n[happy_little_bug.blend](happy_little_bug.blend)\n\n", "Movie Strip not showing in video editing preview only sound is working\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\n\nI was dragging and dropping my usual .mp4 file to my video editing project, the sounds are working but the video isn't showing. I tried the same .mp4 file in VFX project and it worked there. I \n\n{[F8632488](Thank_you_bencrulis.png)}then tried to import the same video file using the add - movie strip but I got an error. Then I renamed the file containing the following characters: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 18-19-35. And it worked. Bare in mind I have 15 other movie strips carrying the same characters but different numbers. I am using an external drive. I drag and dropped the file (like I normally do) and the preview doesn't show. I copied the file to my computer and still the preview did not show. If I have a video with these characters, then the preview doesn't show: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 03-56-05 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 03-20-53 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 02-33-57 C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 02-27-21. **HOWEVER,** if I have the following characters, the video preview in the video editing shows and works just fine: Call of Duty®_ Modern Warfare® 2020-04-26 21-00-17 Call of Duty®_ Modern Warfare® 2020-04-26 21-16-20 Call of Duty®_ Modern Warfare® 2020-04-26 22-10-30 and so on with previous dates. By renaming the rest of my new .mp4 files, all of them work correctly in the video editing sequencer. \n\nOpen Blender\nSelect the blend.file that you are working on\ndrag and drop a .mp4 video to the sequencer with the following characters of the file name: C​a​l​l​ ​o​f​ ​D​u​t​y​®​_​ ​M​o​d​e​r​n​ ​W​a​r​f​a​r​e​®​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​ 2020-06-15 18-19-35\nClick play\n\n[COD Pro Kills Part 1.blend](COD_Pro_Kills_Part_1.blend)\n\n", "Blender Wont run.\nOperating system: Windows\nGraphics card: AMD Radeon HD 8570\n\nBroken: 2.92\nWorked: Nothing has worked. But blender worked before I did this. \n\nWhen I open blender it closes immediately.\nAnd I get this \n\nwatch?v=3rugIsYwl7s).\nSo Out internet was down, And I wanted to get blender On my other pc account, So I went to the main account And Thinking that the installer required internet, I took the system files, and copied them to a thumb drive and pasted them Into the other account when I did that this first started happening, so when The internet came back On. I just got rid of the files I pasted in and then Installed it. With the same result as last time. But this time the bug/glitch was on all accounts. and I tried uninstalling and reinstalling it from the apps and features and from the control panel. I also installed the app from the windows app store with no luck. If you guys know how to fix this issue then please email me at [email protected]\n Ps, My CPU wasn't hot.\n- - -\nAble to run blender from `blender_debug_gpu_glitchworkaround.cmd` batch file", "Blender 2.91.0 Alpha - Blender cannot export proper image when containing smooth gradient of Alpha\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.38\n\nBroken: version: 2.91.0 Alpha\n\nISSUE is appearing when you try to save-as and export an RGBA image as .PNG etc, out of Blender result looks completely different by color, different brightness, etc. (3), not only in Photoshop but also in Windows Viewer.\n\n1. Open the attached blend file\n2. Press render\n3. Save-as RGBA ... .PNG file format, etc. save on your local device\n4. Open the outputted image in any program or viewer and compare again vs blend file to see the difference \n\n5. By the way .EXR format looks correct, but not the PNG. Once I render the.EXR needs to convert all the sequences to.PNGs once again \n\n[ISSUE-RENDERING.blend](ISSUE-RENDERING.blend)\n\n\n", "GPencil: Airbrush draw tool with solid stroke has transparency artifacts\nOperating system: Win 11, GTX 3080, Wacom Tablet\n\n\n\nBroken: 2cd7e70c18a8\nWorked: ~~3.3.0~~\n\nThe airbrush tool has artifacts around the stroke during drawing. Also what is drawn during stroke has nothing to do with the final result visually. Please see the video for the issue.\n\n\n\n- New scene -> 2d Animation\n- Select Airbrush tool from the tool pane\n- Switch to `solid stroke` material from header\n- Draw\n\n[image](attachment)\n[blender_lOlSgoorkK.mp4](attachment)\n", "Volume render bug in view layer indirect only.\nOperating system: windows 10\nGraphics card: RTX 2080 supper\nCPU: AMD ryzen7 2700\n\nBroken: 2.92.0\nWorked: no\n\nOutliner \"Indirect Only\" option does not work well with volumes, as inner shadows are ignored.\n\n\nSurface material with indirect only can work.\n\n- Open attached file\n- Display Render Preview in any of the viewports\n(Make sure the \"Indirect Only\" option in the outliner is enabled).\n[renderlayer bug.blend](renderlayer_bug.blend)", "Missing Letter V and Black Screen\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.0\n\nWhenever I open Blender, the viewport is black and the letter v is not displayed in any of the menus. Here is a link to a screenshot: VZui9.png \n\nIt simply appears like this on startup.\n\n" ]

[ "VSE do not hear audio when playing in edit mode\nOperating system: Linux-5.14.14-1-default-x86_64-with-glibc2.34 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74\n\nBroken: version: 3.1.0 Alpha\n\nI added added a separate audio clip to my video in the VSE, when I play, the audio is silent.\n\nI went back to the previous version and the audio comes out out.\n\n- {nav File > New > Video Editing}\n- {nav Add > Sound}\n- Play" ]

[ "data transfer breaks if more than one remesh is above it in the stack.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.0.0 Alpha\n\nSometimes the `DataTransfer` modifier doesn't work for no apparent reason.\nIn the attached file, putting a `Boolean` modifier after the `Remesh` makes `DataTransfer` work again.\nThis isn't anything to do with differing topology between the hidden and unhidden monkey, otherwise it wouldn't work with only one remesh modifier in the stack.\n\n- Open the file bellow\n- with the monkey selected, turn off the boolean modifier in the stack. \nThe uvs which are being transferred from the hidden monkey will disappear (making the monkey all black).\n[simplified data transfer.blend](simplified_data_transfer.blend)\n\n---\nOriginal file:\n\nOne remesh modifier works fine:\n\n\n\ntwo remesh modifiers break the data transfer:\n\n\n[terminator.blend](terminator.blend)\n", "Rigid body bugs\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.21\n\nBroken: version: 2.93.1\n\nSimulation somehow broken for small (less than 1 cm) or light (less then 100 grams) objects. In first example below object stay still between bouncing and small shivering. And that is just one example. Another examples are – reaching speed of light instantly (one frame), partial simulation when one object (or some objects) acts like it suppose to, but others act completely inadequate, two or three similar parts in one simulation (example 2). I tried different options but nothing helped. \"Substeps per frame\" and \"Solver iterations\" seems not working because there are no actual changes with different values or simulation just goes nuts.\n\n[r_body-bug.blend](r_body-bug.blend)\n[r_body-bug2.blend](r_body-bug2.blend)\n", "particle system locations not as expected\nOperating system: macOS-11.4-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.5.14\n\nBroken: version: 3.0.0 Alpha\n\nif i parent an animated cube vertex to a vertex with a particle system and rotate that cube, it works fine. \nIf i copy that vertex with the particle system to another position - the locations get a bit weird.\n\n- tab -> edit mode\n- select vertex\n- Shift-D -> double vertex\n- Mesh -> Separate -> selection\n- rename that to vertex (not important, just for me)\n- add a default particle system to vertex\n- select vertex, ctrl select cube -> edit mode -> ctrl-p\n- select vertex -> origin to geometry -> run\n- works fine\n- select cube, insert keyframe scale/rot/loc\n- go to frame 100\n- location.z: 8 rotation.z: 360*8 -> keyframe both\n- run, works fine, all locations as expected\n\n- select the vertex\n\n- shift-d X -2\n\nrun -> weird location \"disorders\"\n\n\n[particle_bug.blend](particle_bug.blend)\n\n---\nor\n\n- open .blend file\n- select Vertex from outliner\n- {key Shift D} and place the duplicate Vertex anywhere\n- Play animation\n\n[#90494.blend](T90494.blend)\n\n---\nVideo:\n[particle_bug.mov](particle_bug.mov)", "Auto keyframing causes Duplicate Linked object to change location \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.1.0\nWorked: Never (2.8+)\n\n- Open new general animation template,\n- Turn on auto keyframing\n- Add a mesh object\n- Alt+D create few Duplicate Linked objects,\n# Change frame\n\nDuplicate Linked objects will change location.\n", "Needs two clicks with Ctrl or Shift key to deselect an item from a list of selected items\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0\n\nNeeds two clicks with Ctrl or Shift key to deselect an item from a list of selected items.\n\n\n* Open the project file “OutlinerSelectItemWithCtrl.blend” in attachment as a starting point.\n\nThe same problem happens in different views with different details.\n\nOutliner:\n* Select the entire collection of objects from the collection “Item List”. You can click the “Cone” object, hold the Shift key and then click the “Torus” object to select the entire list.\n* Then hold the Ctrl key and click the Cylinder object to deselect.\n* The item’s color get a lighter color, but it is still not excluded from the whole selection.\n* Clicking a second time on the object really deselects the object.\n* If clicking the first item of the selection (which is the Cone is this example), it is deselected properly.\n\n3D View:\nThe Shift key is used to select/deselect objects individually. It is pretty much the same issue. It requires two clicks on the same object to really deselect the object, whatever the order of the object in the selection. However, if one object has already been selected before deselecting everything, then the same object gets selected with an additional highlight from the new selection (dragging the mouse cursor in the viewport).\n\nShading view:\nPretty similar to the 3D view.\nIf I deselect all the nodes (Alt + A for example) and I drag the mouse cursor to select all nodes, the last selected node is highlighted in white. If I click the node highlighted in white while holding the Shift key, the node is deselected. However, if I do the same thing for the other nodes, it selects the node with a white highlight and I have to click a second time on the same node to really deselect it. The behavior of the last selected item is also present in the 3D View, but not for the Outliner.\n\nThe Compositing view has the same problem and I suspect that the Geometry Node view has the same too (I haven’t tested the last one).\n\nIn general, it requires two clicks to deselect an object with the normal behavior.\n\nThe first click behaves as an “add to selection” click unless the object already had a selection before completely creating a new selection.\n\nIn all cases, there is an issue with deselecting (or excluding) and single object from a selection of objects in different views. As a reference how it should behave correctly, the Windows Explorer in Windows is able to deselect a single item on the first time it is clicked.\n\n[OutlinerSelectItemWithCtrl.blend](OutlinerSelectItemWithCtrl.blend)\n\n[Deselect_Issue.mp4](Deselect_Issue.mp4)", "The Tool Selector Window close one time every two times, when opened too closed to the bottom border of the screen\nOperating system: Windows 10\nGraphics card: GTX 1080\n\nBroken: 2.80\nWorked: (optional)\n\nThe Tool Window, open and close immediately, choosing the tool under the mouse cursor, if the tool window is opened too close from the bottom of the screen.\n\n1) In Edit > Preferences > Keymap, set the \"Space Bar action\" to \"Tools\"\n2) On the 3D viewport, place your mouse cursor in the top area of the viewport\n3) press the spacebar, the tool menu open without any problem, and you can choose a tool with a shortcut key (for example press B to choose the Box selection)\n4) You can repeat that several times in a row without any problems.\n5) Now move your mouse cursor much more closer to the bottom border of the screen, so that you know that the tool window will have to be shifted upward to be displayed correctly.\n6) Press the spacebar a first time. This is ok, you can select your tool\n7) Now press the spacebar a second time. This time, the tool window open and intermediately closed, and the tool selected is the one that is under your mouse cursor.\n8) Press the spacebar again: the tool window open normally\n9) Press the spacebar again: the bug reappear\n10) Now on, every one time over two, the bug appear.\n\n**Expected behavior**\nThe Tool Window should open and stay opened consistently, no matter where the mouse cursor is placed on the screen, when the spacebar is pressed.", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "Macro operators [e.g. Loop cut and slide]: \"adjust last operation\" fails completely [when called from the menu -- F9 is fine]\nBroken: 2.8x\nWorked: 2.79b\n\nThis might fall into the same boat as anything related to #45964, although it does seem to be \"new\" in 2.8x.\nAfter performing a loop cut and slide operator, you can adjust the properties in the operator panel (albeit with caveats from #45964). However, if you instead open the Adjust Last Operation panel, it will list a different operator name (Loop Cut, not Loop Cut and Slide), and while you can change properties there, those changes have no effect, even though they are reflected by the operator panel.\nThis didn't use to happen in 2.79b, though IIUC the \"Adjust...\" panel is different in 2.8x from the \"Redo Last\" of the 2.7x era.\n\n1. Load the default scene.\n2. Go into edit mode on the cube.\n3. Add a loop cut, e.g. via the shortcut or using the active tool\n4. Expand the operator panel in the bottom left and adjust properties. Note how those adjustments do have an effect on the result.\n5. Go Edit -> Adjust Last Operation\n6. Note the different operator name in that newly opened panel (Loop Cut vs. Loop Cut and Slide).\n6. Try adjusting any properties in the newly opened panel. Note how the operator panel in the bottom left picks up these changes, but at the same time they have no effect on the operation.\n\n[Demo video ](eAlL08M8AZA)", "full scene copy does not duplicate obdata of objects in Edit mode\nOperating system:\nGraphics card:\n\nBroken: 3.3 LTS and 3.3.1 LTS\n\n\nif you make a full screen copy of a 2D blend file with some objects in edit mode, the objects in edit mode are linked to the original scene i.e.not independent.\n\nCreate a new 2D project and add a blank grease pencil object\nSelect draw mode and add a stroke say a square\nSelect edit mode and select the stroke for point editing\nCreate a full copy of the scene still in edit mode\nMove a point on the selected stroke in the new scene and observe that the same point moves on the original scene. This means the two scenes are linked.\nCarry out the same steps but before creating the new full copy change the mode to object mode.\nagain move one of the points of the stroke in the second scene and note that the object in the original scene does not change i.e. a full copy.\n\nSame is true at least for meshes and curves, so presumably all obdata.\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "Adjust last operation fails to align new objects\nOperating system: Linux-5.11.0-31-generic-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 620 (KBL GT2) Intel 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: version: 3.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked: Unknown\n\nWhen trying to add new objects, changing the alignment via Adust Last Operation does not work.\n\n- Enter Camera View\n- Add Object\n- Deselect Object\n- Open Adjust Last Operation (Edit --> Adjust Last Operation)\n# Change `Align` to `View`\n\n", "Move origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.1\nBroken: version: 3.2.0\nWorked: (newest version of Blender that worked as expected) - don't know any working version from 2.8\n\nMove origin from Transform Options not working for collection correctly - not moving, but moving if Object Set Origin is changed\nLooks like limitation maybe around Transform Options and lack of implementations or bug that blocking move origin.\nWhen using addon Cad Tranform (slcad_transform_0.91.0.zip) and Turn on Transform Options Origins then can move origin (but problems with magnet snap).. soo looks like bug in blender grab area.\nAnyway it's problem when looking correct position for my object and work with collections, only addon can solve problems.\n\n1. Turn on Transform Options Origins - try move origin for Collection2, eg. for corner\n2. Turn off Transform Options Origins, select Object Set Origin and Origin to Center or other option\n\n\n\n\n[Origin_bug.blend](Origin_bug.blend)\n", "Multiple Edge Loop Selection doesn't always work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0\nWorked: 3.3\n\nMultiple Edge Loop Selection (Shift+Alt+Select) will sometimes stop working until Shift is released and depressed again. Problem started in Blender 3.4 and did not exist in Blender 3.3 (tested).\n\n\n- Create a cylinder primitive.\n- Enter Edit Mode.\n- Attempt to Edge Loop Select multiple edges by holding Shift+Alt and clicking on them. Occasionally, this function will simply stop working after the first few selects -- no more edge loops can be selected -- until Shift is released and depressed again.\n\nThis problem does not occur for general multi selection (when only Shift is held).\n\n", "Redo panel does not work for the 3d cursor\nUbuntu 18.04\n\nBroken: 7d38654\n\nRedo panel for moving the 3d cursor does not work as expected.\n\nStart moving the 3d cursor and then change the value in the redo panel.\n\n\n\nMy guess is that this happens because the 3d cursor is not effected by the normal undo.", "Multires: Duplicating objects sets the viewport level to sculpt level\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 3.1.0 Alpha\n\nWhen sculpting on an object with a multiresolution modifier there are 3 sliders to define the level of subdivision.\nWhen duplicating the object right now, it will set the viewport level to the same value as the sculpt level.\n\n- Add a multires modifier\n- Subdidive the object\n- Set the viewport level to soemthing other than the viewport value\n- Duplicate the object\n\n" ]

[ "Blender 2.8. REPEAT LAST action doesn't work properly for editing mode [FOR EXTRUSION]\nwin 10 - 64 bit\nNVIDIA GeForce GTX 560 [last driver version]\n\n\nBroken: 2.80, dbfbd6b9043d, 2019-03-16\nWorked: 2.79b, f4dc9f9d68b, 2018-03-22 \n\n\nLooks like **REPEAT LAST** action doesn't work properly for editing mode. In particular for extrude operation. When you repeat last extion for extrude - it will allways moves towerd first one extrusion oriented movemant and never toward 'normals'. Even if you will choose any others combinations of transform orientation and pivot point Here is I captured video: #!sXYlAIzY!OXinB6ZXQ1FSktu0UkLnnOSDKf_5efb6Pt0EEjAM68Q\n\nOpen default file. Put a cube. Turn on edit mode. Select any side and extrude it. Then press SHiFT+R[or open Edit>Repeat last/ or Edit>Repeat History and choose last action] - and repeat action - all looks good. Then take any other side of the cube and press SHIFT+R and you will see that extrusion will oriented toward first one extrusion movement. Even if you will choose any other of transform orientation, you will never get correct result. It's works fine in old version of Blender.\n\n", "Extrude and duplicate object bug\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.83 (sub 4)\nWorked: for dupticate object working normal in 2.82 but not for extrude in edit mode\n\n1. in 21.2.2020 build if pressing E for extrude region and then shift R for repeat, the extrusion always happens in opposite direction than intended.\nsame with duplicate object linked or not.\n2. in official 2.82 build if pressing E for extrude region and then Shift R for repeat then repeat happens in X direction no matter in what direction was extrusion in first place\n\nif i extrude and press adjust last operation then i see the numbers not correct in which direction i moved the extrusion\n", "repeated extrusion is buggy \nOperating system: Win 10 64bit\nGraphics card: Geforce 940M\n\nBroken:\n2.80, 4dd0a90f4213 win64, blender2.8, 2018-12-16\n\nextruding a face and then redoing the action with shift+r gives unwanted result when extrusion axis isn't locked\n\nselect default cube, go to edit mode select face, press e to extrude and z,z to free axis\nrepeating the action with shift r will move the new faces in a weird way\n" ]

[ "Editing an object that is referenced in a disabled modifier (of another object) forces the other modifiers on the same stack to update\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\nWhen there are two Boolean modifiers, and the second one is disabled, editing its shape still recalculates the Boolean operation if the first one is enabled.\nEven when both modifiers are disabled, editing their shapes is slower than editing the same shape that is not targeted by a Boolean modifier.\n\nAs an example:\n\n[2020-01-17_18-02-50.mp4](2020-01-17_18-02-50.mp4)\n\n\n- Open [#73199-testboolean.blend](T73199-testboolean.blend) (or add two cubes, make a dense mesh, add Boolean modifiers to the dense mesh each targeting a cube).\n- Switch off a single Boolean modifier.\n- Edit the mesh that is targeted by that Boolean modifier. This is slow.\n- Switch off the other Boolean modifier.\n- Edit the same mesh as above. This is now much faster.\n- Add a third cube and edit it. This is still faster than in the previous step.\n\n", "Vertex/Edge Slide stuttering with modifier.\nOperating system: Windows 11\nGraphics card: RTX 3070\nCPU: Ryzen 5900x\n\nBroken: 2.83 and all other.\nWorked: 2.79b\n\nVertex/Edge Slide freezes a lot with subdiv modifier in a relatively simple object.\n\n| With `Use Limit Surface` | Without `Use Limit Surface` |\n| -- | -- |\n| https://projects.blender.orgattachment | https://projects.blender.orgattachment |\n\n1. Import attached fbx.\n2. Add subdivision modifier set to 1 subdivision.\n3. Select the loop in the middle.\n4. Edge slide.\n\n", "Disable selection operators in sculpt mode\nA small task to improve keymap changes from #105298\n\nSelect operators can be used in sculpt mode, even though they have no effect:\n\n- `view3d.select_circle`\n- `view3d.select_box`\n- `view3d.select_lass`\n\nEspecially due to recent keymap cleanups, the circle select operator can be called with the shortcut `C`. These operators need to be disabled while in that mode to prevent this.\n\n", "Sculpt Mode: Improve Expand performance\nWith [D16434: Sculpt Mode: Invert Expand behavior for masking consistency](D16434) it will be a stronger focus to highlight the Expand operators as a core feature in sculpt mode to create masks & face sets.\n\nThe issue is that the operator tends to be too slow to initialize on high res meshes.\nThis is especially the case for the geodesic expanding method.\n\nWe need to address these performance issues.\nOne usggestion was to incrementally calculate the distances while the operator is running.", "3D Cursor & Origin overlays should be grayed out if hidden by current mode/tool\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar.\n\nThe 3D Cursor and Origins are not displayed in painting modes as well as sculpt mode. \nThe overlay popover does not give feedback on this though.\n\n\nThe overlays should be grayed out in the modes and tools where it is hidden. \nIdeally there should be exceptions to this rule, like while the 3D Cursor is transformed (already implemented) and when the current Tool is using it (Annotation Tools).", "Modifiers don't work on particle instances of a hidden object\nOperating system: Linux Mint 20.3 Cinnamon kernel 5.13.0-35\nGraphics card: 3400G\n\nBroken: 2.83\nWorking: apparently never\n\nRelated to #96367 (Crash when trying to snap to instances on an object)\nTo replicate bug, the instantiated Object (the one with a `Modifier`) has to meet the following conditions:\n* Must have a modifier (obviously)\n* Must be instantiated through a particle system. (instantiated through Geom Nodes is OK and through Dupli Verts/Faces hides the `Object` as well)\n* Must be hidden inside a collection with the `Excluded from View Layer` option enabled\n\nAnd the instantiating Object (the one with `Particle System`) has to meet the following conditions:\n* Must be referenced by a `Camera` in the \"`Focus on Object`\" field\n* In the outliner, the `Camera` object must be placed in a `Collection` before the instantiating Object\n\n|||\n| -- | -- |\n|Camera placed before |Camera placed after\n\n # Open the attached file\nUnhide collection or switch `Camera` and `Plane with particle system` collections order (via Drag and Drop) get around the problem.\n[Camera 'Focus on Object' - particle system issue.blend](Camera__Focus_on_Object__-_particle_system_issue.blend)", "PyAPI: template_modifiers doesn't work in the viewport\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\nWorked: -\n\nThis was working outside the context of the Properties Editor prior to 9b099c8612 -- when it was still template_modifier(md).\n\nDisplaying the dafault modifier layout doesn't work in the viewport (in the sidebar or in a popup). template_modifiers() gives errors:\nPanel type 'MOD_PT_Array' not found.\nPanel type 'MOD_PT_Bevel' not found.\nPanel type 'MOD_PT_SimpleDeform' not found.\n... \n(interface_panel.c, line 292)\n\nBased on the attached file:\n1. Run the script in the text editor to create a panel in the sidebar called \"Modifiers\"\n2. Verify that the modifiers don't show up and there are errors in the console\n3. Click the \"Modifier Popup\" button\n4. Same thing should happen with the popup\n\n[template_modifiers_bug.blend](template_modifiers_bug.blend)\n", "sculpt mode: invert visible hides all faces with Multires modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.0 Beta\n\n`Invert visible face sets` hides all faces with Multires modifier.\nOperator is expected to only hide visible faces (and unhides hidden faces)\n\n- Open .blend file\n- Use box hide brush to hide vertices\n- {nav Face sets > Invert Visible Face Sets}\n\nTest File:\n[#95419.blend](T95419.blend)", "Advancing Displace and Solidify modifiers to handle overlaps\nI briefly discussed this with C. Barton. I often I solidify and displace surfaces in the processes I work on -- recently for 3d printing custom assistance devices including molds for casting rubber, customized computer peripherals, etc. Whether or not they use clear-cut geometric forms, or are of organic nature, they often succumb to the issue of intersections with displace/solidify. I've wanted to work out some details on processes which would enhance these modifiers, but need some help. I'd attempt to implement it so it would be inactive normally, and use thresholds when enabled, so as not to slow down the normal modifier functionality, and a require a minimum processing when the features are used.\n\nThe main issue I'm having is that the modifiers do not presently have access to information on adjacent vertices, and my first approach to an algorithm would examine, with some function fn(vertex_normal, displacement_amount), if there would be a crossing (e.g. if faces would intersect). Then the simplest method would angle the normals away from each other. However, this does all require the ability to examine adjacency, and I'm relatively inexperienced in blender internals, having only contributed minor bits to sculpting tools and physics code. Your guidance would be appreciated.\n\n", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "MultiRes+Solidify while trying to use Sculpt Mode cause Blender to crash\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 (sub 12)\nWorked: (optional)\n\nI tried deactivating one modifier while keeping the other one active to see if Blender would crash, but this was not the case. Only when I used both simultaneously did the program reliably crash every time, regardless of brush.\n\nAdd the modifiers that are active in the video and follow along. \n[Desktop 2019.09.23 - 00.49.39.02.mp4](Desktop_2019.09.23_-_00.49.39.02.mp4)\n", "Sculpt with Perspective mode. Changing brush size is impossible with closups\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\n\nAs title says. This behavior prevents to use {key F} as size modifier on closeups.\n\n[2021-03-20_10-32-46.mp4](2021-03-20_10-32-46.mp4)\n\n[brushsize.blend](brushsize.blend)", "Modifier re-evaluation makes editing dimensions unreliable\nCurrently editing dimensions uses the bounding box that's recalculated while dragging.\n\nThis can cause a feed-back loop as the objects scale is used by some modifiers which calculate a new bounding based on the scale which is then used in dimensions.\n\nIn the case of armature modifier - any zero scaled axis makes causes the mesh to scale into a single point, making any further changes to the dimensions not have any effect.\n\n----\n\nOriginal report:\n\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GT 620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\n\nBroken: version: 2.80 (sub 74)\nWorked: Blender 2.79\n\n\nIf object is rigged scrolling its dimension value toward zero causes object to disappear, even if right mouse button has been clicked in order to cancel a scaling. So blender accepts a scale of zero even if left mouse button hasn't been released yet, Is it an expected behavior in Blender 2.8?\n\n\n\n\n - Select the cube.\n - Scroll any of its dimensions value toward zero without releasing the left mouse button\n - Cancel scrolling by right mouse button click.\n\n\n\n[Bug_report.blend](Bug_report.blend)\n\n", "Sculpt Paint: Accumulative Painting/Sculpting\nNOTE: This design is still under discussion and is incomplete.\n\nThe recent addition of painting tools in sculpt mode also added an alternative design for accumulative painting.\nBecause of this there are now two different ways of handling accumulative strength.\nThis needs to be polished and properly integrated into the UI and painting workflow.\n\n# Strength and Accumulate\n\nSo far brushes always had an \"Accumulate\" setting for removing the maximum strength cap. Brushes would then keep adding their effect as long as the stroke continues.\nOtherwise they would either accumulate up to a hard-coded upper strength cap (sculpt mode) or up to the set strength (painting modes).\n\nThe issues with this implementation are:\n- It is easy to accidentally clip the colors while painting (There is no upper cap with accumulate)\n- The setting is hidden in \"Advanced\" brush settings even though it is regularly used, and even preferred for painting.\n\n# Flow\n\nThe new painting brush in sculpt mode instead uses a \"Flow\" slider, which defines how strong each step of the stroke is. \nThe stroke will then keep accumulating more slowly towards the set Strength.\n\nThere are a few issues with this implementation:\n- The Flow setting is less accessible, even though it can sometimes to be the preferred way of changing the stroke intensity.\n- The relationship between Strength and Flow becomes very confusing, especially when comparing sculpting & painting brushes or when enabling pressure sensitivity settings\n\n# Proposal\n\nHow to make the settings and behaviours more predictable and accessible needs to be further discussed.", "Unify Interpolation In Vertex Paint And Sculpt Mode\nVertex paint squares colors when it interpolates, while the paint tools in sculpt mode do not. This should really be made consistent across both modes. \n\n\n" ]

[ "Mirror Modifier does not work in sculpt mode.\nOperating system: widows 10\nGraphics card: geforce gtx\n\nBroken: 2.80, master, 2019-4-26,\n\n\nMirror modifies work in object mode and edit mot just fine. However they do not work in sculpt mode.\n\nPrevious version of blender allowed for mirror modifiers to work in sculpt mode. You need to bring this functionality back \n\nThe mirrored mesh is currently invisible in sculpt mode\n\nproof that mirror modifiers have worked in sculpt mode in the past\n\n[proof ](s3pnLyTwbJk?t=192)\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nad a mesh\n\nsubdivide the mesh\n\ndelete half the mesh\n\nmirror the remaining half with a mirror modifier\n\nenter sculpt mode\n\nthe mirrored mesh had vanished!!!!!", "Sculpt: mirror and other modifiers not visible in workbench sculpt mode\nOperating system: WIndows 7\nGraphics card: GTX 1050\n\nBroken: ee0d8426ab6d\n\nModifier visibility inconsistent across solid and rendered modes while in sculpt mode.\n\n* download .blend\n* go to sculpt mode (modifiers doesn't work)\n* go to rendered mode (works)\n\n[modfier bug.blend](modfier_bug.blend)" ]

[ "Display issue in model corner when loop cutting\nBroken: 2.79, 2.81\nWorked: -\n\nWhen creating and edge loop around de outside faces it creates in one of the cornes an extrange artifact\n\nCreate an edge loop across the outside faces of the model.\n\nBlender file:\n[loop cut.blend](loop_cut.blend)\n\nArtifact:\n\n", "Mulitres: Grab brush + 'Grab Active Vertex' option seems not intuitive or broken 3.2\nOperating system: Windows-11-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.2.0\nWorked: (In 3.1 sort of?)\n\nI am not sure if its a bug but here we go:\nWhen you add a mulitres modifier to an object and try to sculpt on it with the grab brush it works.\nIf you enable Grab active vertex in the Brush settings it looks broken to me. Even in 3.1 the vertex are displaced from the original and impossible to grab. \n\n1. Start blender\n2. Add a sphere\n3. Add a multires on lvl 1 or 2\n4. Using the grab brush in sculpt mode works until you enable the grab active vertex option.\n\nThe blend file has the setup just try in sculpt mode the grab brush and the options.\n\n\nOn a side note the bug report said win 10 but i run win 11. It seems not to recognized my system.[GrabActiveVertexBUG.blend](GrabActiveVertexBUG.blend)", "Regression - depth buffer drawing go bonkers when selecting object on second collection\nOperating system: Linux-5.8.18-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0\nWorked: 2.90\n\nAfter drawing simple 3d lines with python script - depth buffer is drawn incorrectly when deselecting object that is placed on **second collection**. \nScript itself is very generic - from blender gpu docs examples. It worked ok in all previous blender versions.\n\n[Linde_draw_depth_bug.mp4](Linde_draw_depth_bug.mp4)\n\n- run script - it will draw 2 lines in 3d view for 8 seconds\n- if you select/deselect box which is placed on second layer/collection you will see those lines are drawn incorrectly on object deselect.\n\n[3d_view_lines_bug.blend](3d_view_lines_bug.blend)\n\n\n\n", "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "Crash on sculpt mask brush when Multiresolution modifier is copied from another object\nOperating system: Windows 11\nGraphics card: GTX 1060\n\nBroken: 3.3.0 / 3.2.0 / 2.93.10\nWorked: (First time trying multires hasn't worked on any of the versions I've tested on)\n\n\nCrash on sculpt mask brush when Multiresolution modifier is copied from another object.\n\n\nReplicate problem 1:\n\n - Add a Cube (#1)\n - Add Multiresolution modifier to Cube (#1)\n - Subdivide 4 times\n - Add a Cube (#2)\n - Copy Cube (#1)'s modifier onto Cube (#2) through the use of Link/Transfer Data > Copy Modifier\n - Select Cube (#2) and enter sculpt mode\n - Select Mask Brush\n - Use Mask Brush (Should crash blender)", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "Multi-object-Mode: EditMode transform properties\nEdit-mode buttons currently only show median values for the active edit-object.\n\nThe Mean Crease value of the N panel doesn't work for multiple objects:\nHere i have 2 objects selected\n\nIn Edit Mode changing the Mean Crease value does change its effect only on the selected object:\n", "Transform Tools influence on Hidden Face Sets with Multires Modifier\nOperating system: Linux-5.3.0-62-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nThere seem to be multiple strange effects that the Transfrom Tools (Move, Rotate, Scale, Transform) have on an object with Multires in Sculpt Mode.\nWhen hiding face sets the boundaries are still being effected but are lagging behind.\nIf the operation is cancelled (Esc) the boundary edges will move half of the way anyway.\nIf the operation is accepted it will unhide all face sets.\n\n[2020-07-27 14-06-58.mp4](2020-07-27_14-06-58.mp4)\n\n- In the default cube, add the Multires modifier\n- Subdivided the mesh a few times.\n- In sculpt mode, draw a Face Set for one of the faces.\n- Hide the rest\n- Enable the Transform tool and move the object.\n", "Outliner: Object selected/deselected when clicking with RMB on it's object data [`Sync Selection` option causes this]\nBroken: version: 3.0.0\nBroken: version: 2.91.2\nBroken (differently): 2.90.1, 2.83\nWorked: 2.82\n\nWhen clicking with RMB on *some* object data in outliner (can confirm for materials), parent object is selected/deselected (both in outliner and in 3D viewport). That can lead to undesired actions. For example, when click RMB on material object data from a cube and choosing `Delete` you'll get one of the following:\n- Delete only material object data if parent object is not selected\n- Delete cube object itself **and** material object data if parent object is selected\nMesh/ligh/camera object data also have this \"parent object selection/deselection\" behavior but for this object data it's not so apparent in terms of functionality since in both cases mesh/light/camera object data is deleted and object can't exist without those so it's deleted too.\nModifiers and constraints are handled consistent with context menu - deleting only modifier - although it's something to be discussed since it shows that parent object is selected.\nFor shortcut behavior there is already #94062.\n\nIn 2.90.1 core issue is same but behave slightly different - it'll not always change selection/deselection, can provide details if requested.\n\nFor materials:\n1. Open attached file. You'll see two objects with same mesh object data.\n2. Repeatedly click with RMB on material object mata in outliner to see parent object selected/deselected.\n3. Choose `Delete` from context menu when parent object is selected - one of the objects is deleted and one material that was clicked on (you can see it on other objest mesh object data since they share it).\n4. Undo\n5. Choose `Delete` from context menu when parent object is not selected - only one material is deleted.\n\nFor showcasing mesh/light/camera data behavior:\n1. Open attached file.\n2. RMB on `Sphere` mesh object data to a point where parent object is either selected or deselected.\n3. Choose `Delete` from context menu - in both cases all objects are deleted.\n[RMB outliner selection bug.blend](RMB_outliner_selection_bug.blend)", "EEVEE-Next: Refactor renderpass storage\nCurrently render-passes are allocated in multiple texture buffers.\nThey take a lot of binding points and currently prevent the deferred pipeline to output diffuse color correctly.\n\nThe plan is to combine all render-passes into the same array texture and use an associated UBO containing offset to the layer of each pass type.\n\nThis would very similar to the AOV support.\n\nAnother direct benefit of this would be that the GBuffer encoding could be simplified.\n\n", "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "Scene update bug\nSystem Information\nwindows7 64\nASUS ATI Radeon HD6870\n\nBlender Version\nBroken: (All)\nWorked: (None)\n\n\n\n\n\n\n\n\nopen this file, select plane and try to select for this plane any mesh - all this meshes don't have users, but was saved, try to select material - materials was saved, but don't have users, \nwe can revert, close and open again many times - materails and meshes will be saved.\ntry to add gruop instance - we will have all this groups is empty.", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "Material slots menu: copy material and copy to selected work different\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Alpha\n\nCopy and paste material actually work as copy of all data from one material to another.\nCopy to selected do not work as copy, it acts like material linking/referencing\n\n**Steps to Reproduce**\n- Open attached file\n- Switch to material preview\n- In material properties tab open `material specials` popup\n- Click Copy materials to Selected\n[#85419.blend](T85419.blend)\n[2021-02-06_07-55-48.mp4](2021-02-06_07-55-48.mp4)" ]

[ "Display failures on an object with more than one material\nOperating system: Linux-5.0.0-36-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 220/PCIe/SSE2 NVIDIA Corporation 3.3.0 NVIDIA 340.107\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n[When trying to use a second material or more on an object, the faces where it is applied become transparent or in some cases they are distorted as black rectangles that stretch to the origin (this second occurs above all with more complex models than a cube). This bug is noticed in edit mode or object, obviously if in viewport shading the option of material color or texture is used. In the other color modes of the Viewport Shading as Object, Vertex, Single or Random, the meshes of the object are displayed without the errors mentioned above. It happens in Blender 2.81 as well as in Blender 2.82, but in Blender 2.80 there is no such error.]\n\n[\n 1) Create a material and apply it to the cube by default.\n 2) Create a second material and apply it to one of the faces of the cube, that face will be transparent.\n 3) Create a third material and apply it to another face of the cube, it is also transparent\n{[F8170373](Bug_Material.blend)}]\n\n" ]

[ "Joining meshes (having equally named attributes on different domains) leads to name collisions for attributes (leading to e.g. errors on gltf export)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95\n\nBroken: version: 3.6.0 Alpha\n\n\nIf I have two attributes with same name, and try to export it as glb, exporter produces huge page of inner errors,\nsay that there is name collision, but do not say what object cause the issue.\nExpected: short message, more readable, says «object _objName_ have name collision in attributes. Attribute_name appears more than once, can`t export»\n\nIn case when you have hundreds of objects with dozens of attributes it is hard to find where the issue is and fix it. And such long page of errors only confuses user.\n\n\n- on one mesh object, create a color attribute on the `Vertex` domain (doesnt matter if `Color` or `Byte Color`) called `Color`\n- on another mesh object, create a color attribute on the `Face corner` domain (doesnt matter if `Color` or `Byte Color`) called `Color` as well\n- join the two mesh objects\n- leads to name collisions (two `Color` attributes on the same mesh)\n- leads to errors on e.g gltf export\n\nThis is also true for other attributes (does not have to be color attributes really)\n\n**Original report**\n\nOpen file [atrcollision issue.blend](attachment), try to export as gltf/glb, check error log.\n\n", "Principled BSDF Anisotropy black faces\nWin10, 1080Ti\n\nBroken: 2.79\n\nIt seems that using anisotropy produces black odd artifacts under certain mesh circumstances. I don't think this happens often as it seems the actual mesh caused it, possibly by being a little bit too symmetrical? \n\nI suppose often it goes unnoticed so I thought it might be good for someone to investigate upon if there isn't some inconsistency.\n\nRotating the object by the tiniest bit helps (probably helps by something being non 0 ^__^).\n\nMoving random vertices randomly produces different results that are often completely correct or at least 50% correct. Good to try that in Rendered mode.\n\nScreenshot: \n\nBlend: [Anisotropy_Bug.blend](Anisotropy_Bug.blend)", "wireframe object shows face orientation when other close to it\nOperating system: Linux-5.14.17-hardened1-1-hardened-x86_64-with-glibc2.33 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics 630 (CFL GT2) Intel 4.6 (Core Profile) Mesa 21.2.5\n\nBroken: version: 3.0.0 Beta\n\n\n\n\nadd 2 cubes side by side\nchange display to `wire` for a cube\nopen `face orientation` in `viewport overlays`\nwireframe cube will show face orientation unexpected\n[bug.blend](bug.blend)\n", "Scripting: undo after mesh.separate causes crash\nOperating system: Linux\n\nLatest tested: blender-3.5.0-beta+v35.f23e3c7f04f3-linux.x86_64-release\nEarliest tested: blender-3.1.2-linux-x64\n\nTrying to undo `bpy.ops.mesh.separate(type='MATERIAL')` in a script crashes Blender.\n\n1. Create a cube and two materials. Go to edit mode and assign some faces to both materials. Go back to object mode.\n\n \n\n2. Open the Text Editor and run this script\n\n ```py\n import bpy\n bpy.ops.ed.undo_push( message = \"temp\" )\n bpy.ops.mesh.separate( type = 'MATERIAL' )\n bpy.ops.ed.undo()\n ```\n\n3. Crash (segmentation fault).\n\nSomewhat mysteriously if I save just before running the script, close Blender, then reopen the .blend and then run the script, I get non-determinstic results (sometimes the undo does nothing, sometimes the white part is gone). The only consistent way I found to get a crash was to create the cube from scratch every time. So no .blend is attached to this issue.\n\n", "Z-fight with invisible face in edit mode\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nWorked: \n\nI have 2 cubes. Bigger one is set viewport display as wire. Both share the same XZ plane. In Object mode shading is fine, but if I enter in Edit mode with smaller cube artifacts are appear.\n\n[ladder_01.blend](ladder_01.blend) \n\n", "Mix/Add nodes breaks Eevee AO render pass if one socket is unfilled.\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.92.0, 2.93.0, 3.0 0efb627bbd\n\nIn Eevee, any material which contains an add shader node will be broken in the AO pass, if second socket is *invalid*, leaving the material either entirely black or white.\nThis is annoying if you're creating entirely black materials by leaving a socket empty.\n\n- Add a mesh, give it a material.\n- Put either an an add shader node or a mix node into the material somewhere, but only fill one of the input sockets\n- Enable AO with Eevee, and look at the AO render pass in render view. In 2.92, the object will be completely black, in 2.93 it will completely white.\n\n----------------\n- Render the scene with the file given.\n- For the second case, render by swapping the socket inputs of the \"Add Shader\" node.\n[T88779_mine.blend](T88779_mine.blend)\n\n\n\n\n\nAdditional example images.\n(2.93)\n[F10155389](image.png)\n[F10155391](image.png)\n\n(2.92)\n[F10155385](image.png)", "Select similar face regions doesn't work across objects in multi-object edit mode\nOperating system: Windows 10\nGraphics card: GTX 1070\n\nBroken:\n3.0.0 alpha, 3.1.0 alpha\n\nSimilar face regions don't get selected across objects in multi-object edit mode.\n\n\nBased on the attached .blend file.\n\nI made a scene with a cube and bevelled its edges. I then copied the cube, selected both objects, entered edit mode and selected 3 faces of the active cube object where bevelled edges meet.\nThen I went to Select Similar > Face Regions and Blender selected 7 analogous face regions, but only on the active cube, not on the other object.\nIn comparison, if I add materials to these objects and try selecting faces by similar materials, both objects' faces will be selected. Any other trait among \"Select Similar\" will select faces across multiple objects.\n\n\n\n[similar face regions don't get selected across objects in multi-object edit.blend](similar_face_regions_don_t_get_selected_across_objects_in_multi-object_edit.blend)", " Render Face Sets and Mask as contour lines\nFace Sets were added to control the visibility of all paint modes and currently, they are rendered as colors (which is the easiest way to debug them and work with them from sculpt mode). This won't work for vertex paint and texture paint (and any other mode that works with color), so a different rendering needs to be implemented that does not affect the color of the surface as an option these painting modes. \n\nIf possible, this should be implemented for the current sculpt mask (add an option to render it as a contour line, similar to the lasso selection) as the same mask implementation and rendering will also be used for vertex paint.", "Bake artifacts with multimaterial in object\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nThen i try bake Ambient Occlusion in object with 2 or more assigned materials, Ambient Occlusiun bakes grey or black squares\n\n\n- Open attached file and bake ambient occlusion.\n[Bake_Test.blend](Bake_Test.blend)\n\n", "Color picker samples merged (display output) colors on a certain object regardless of \"Sample Merged\" setting\nOperating system: Windows 10 v1909\nGraphics card: NVIDIA GeForce GTX 1660 super\n\nThe bug occured on the latest Steam release of Blender (2.90.1). I also tried to open the project file with the said bug in 2.83 LTS steam beta branch but it happened there too.\n\nWhen trying to texture paint a certain project it ignores the \"Sample Merged\" setting and always picks the display output color, while other objects don't share this problem. \nIt happens regardless of the material or texture I'm editing, it seems to be tied to a single object. For example, If I create a cube and assign the material which the bugged object uses color picking works fine with it, and if I assign any other material to the bugged object it still samples display output color regardless of the settings.\n\nI'm sadly not sure how to reproduce it. Though I appended the bugged object to a fresh file: [color_picker_thing.blend](color_picker_thing.blend)\nIt's system info:\n[system-info.txt](system-info.txt)\nI separated it so you wouldn't have to dig through the mess that is my main project file :D. It retained it's weird inabillity to pick colors though.\n\nI couldn't find a solution to this when I tried to google for it, so my only assumption left here is it being a bug. I'm sorry in advance if something I said isn't clear. If needed, I can provide a whole project or try and provide more specific information if what I wrote here isn't enough as soon as possible.\nCheers!", "different generation of graphic card won't utilise together.\nOperating system: Windows 10\nGraphics card: Radeon R9 295X2 (secondary chip) + Radeon RX560 4GB\nAMD Ryzen 1700X\nMSI X370 Gaming Pro Carbon\n3 * 8GB DDR4-2400\n\nBroken: 2.82.7 to 2.83.3 <--- where x is from 0 to current stable version\nWorked: 2.8, 2.83.4 (partly worked, may end up sudden wattman reset)\n\nRadeon Version: 20.7.2\n\nafter the 3rd step, the render did not show anything, switching back to material viewport, the whole program was frozen. not sure if that is graphic card problem, but that way i could not even render anything. on 2.82.7, this also happened and the render kernels failed to work.\n\n\n1. open up a file of as shown\n2. set the preferences that would use OpenCL to render with R9 295X2 (and RX560)\n3. preview in Cycles\n4. unable to load the preview, switch back to material viewport.\n\n[zeta school 1.blend](zeta_school_1.blend)", "File->Open Recent behaves different from Edit Override Library on Linked Object Materials\nOperating system: Windows 10\nGraphics card: AMD Radeon & NVidia 1060Ti\n\nBroken: 3.6.2\nWorked: Unknown\n\nWhen using File->Open Recent to change blend files, the overridden materials on a linked object are getting broken/changed. When using Edit Override Library on the linked object, the materials remain consistent.\nI am seeing a behaviour difference that breaks the material order when using File->Open Recent versus Edit Override Library. When using File->Open Recent it is changing the order of the materials destructively. This is related to linked objects and overriding their materials.\n\nDefault startup, 2 files needed.\nWhen using File->Open Recent the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. File->Open Recent->(File from step 1)\n12. File->Open Recent->(File from step 10)\n13. Notice that Material 1 and Material 3 are now the same materials\n\nWhen using Edit Override Library the steps are:\n\n1. Create an object that will be linked. In this case, default cube\n2. Color it with 3 materials (Red, Blue, Green)\n3. Create a new blend file\n4. Link in the cube from step 1\n5. Make it a library override (Object->Library Overrides->Make)\n6. We are going to change material 3\n7. Select Material 3 change to Object Data\n8. Select the default material\n9. Change the color\n10. Save the file\n11. Item->Edit Linked Library\n12. Item->Return to Original\n13. Notice that the Materials are in the order and color from step 7, no change\n\nThis requires several files as the initial set up gets broken. Easiest to follow the steps.\nFiles are included, they are:\n\nLinkedObjectMaterials.blend -> This is the file with the object that will be linked into the other files\nOverrideTest.blend -> File has a link to LinkedObjectMaterials.blend and it has a changed material that was set up and tested using EditOverride Method and the materials are OK\nFileOpenRecent.blent -> File has a link to LinkedObjectMaterials.blend and the 3rd material was changed and now both the first and third materials are the same.\n\nAsk if any clarifications are needed. It took me a while to narrow it down to this case.\n\n", "Geometry Nodes: Curve primitives issues with object material\nBroken: version: 3.2.0 Beta, 3.3.0 Alpha\nWorked: n/a\n\nMaterials assign to the object don't work in some cases for curve primitives created in the geometry nodes tree.\n\nOpen file, you will see that the star doesn't get the red object material.\n\n[curve_object_material.blend](curve_object_material.blend)\n\nUnhiding any of the hidden nodes (Grid or Set Material) will make the object material show up.", "Hair with material using a non-existing attribute looks different between Eevee and Cycles\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.00.20.220516\n\nBroken: version: 3.4.0 Alpha\nWorked: -\n\nHair can be affected by materials that use attributes such as mesh.\nThe color of the mesh at the root position of the strand usually defines the color.\nBut that's not the case in Eevee if an attribute doesn't exist.\n\n\nThe actual color can be kind of undefined, but there should be a convention between the renders.\n\n- Open attached .blend file\n- Compare Cycles and Eevee\n[hair_material_with_non-existing_attribute__bug.blend](hair_material_with_non-existing_attribute__bug.blend)\n\n", "Rigid body bugs\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.21\n\nBroken: version: 2.93.1\n\nSimulation somehow broken for small (less than 1 cm) or light (less then 100 grams) objects. In first example below object stay still between bouncing and small shivering. And that is just one example. Another examples are – reaching speed of light instantly (one frame), partial simulation when one object (or some objects) acts like it suppose to, but others act completely inadequate, two or three similar parts in one simulation (example 2). I tried different options but nothing helped. \"Substeps per frame\" and \"Solver iterations\" seems not working because there are no actual changes with different values or simulation just goes nuts.\n\n[r_body-bug.blend](r_body-bug.blend)\n[r_body-bug2.blend](r_body-bug2.blend)\n" ]

[ "Multi-materials\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Quadro FX 4800/PCIe/SSE2 NVIDIA Corporation 3.3.0\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nDrawing error with multi-material object. Faces dissapear or showing artefacts with 2 or more material slots applyed to same object\n\nSelect the face on the objetc and apply the second material slot\n\n\n\n[materials.blend](materials.blend)\n" ]

[ "Memory Leak: Render Animation Sequence\n**System Information** Mac Studio Max, 64 GB Ram\nOperating system: Mac OS Ventura 13.3.1\nGraphics card: Metal 32 core GPU\n\nBroken: 3.5.1.\nWorked: N/A\n\nWhen attempting to render out 100 frame sequence to Tiffs... after 25 to 30 renders @2K using Cycles GPU only (Metal) the Ram usage is through the roof and Blender crashes. It appears that it doesn't flush the RAM between each render... by frame 25 Blender is using all the system RAM and has a swap file of over 100GB. The scene contains a single simple character sculpt with 4 fur curve nodes applied. Average render time when applied to single frame at .1 sampling is about 25 seconds.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Crash when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "Crash when shading\nModel: HP Probook x360 435 G7 (independently upgraded SSD and RAM)\nOperating system: Windows 11 Pro 22H2 22621.1555\nGraphics card: AMD Radeon Graphics (Built-in graphics of AMD Ryzen 5 4500U with Radeon Graphics)\n\nBroken: 3.5.1 and 3.3.1 were tested, both had this issue.\nWorked: 3.1.2 – At the time of issue creation, there are no newer versions that have worked, including the latest build of 3.6.0 Alpha.\n\nBlender freezes for a second or so, and then crashes.\n\nI don't know if it *is* reproducable, but I have tested multiple conditions under which it crashes. These conditions are accompanied with the crash logs of that test. The problem does not seem to be (V)RAM usage, as the usage remains constant from before Blender is opened to long after.\n- Press F12 to Render Image: Crash [Log](itihmb)\n- Select Default Cube, Click on Shading workspace: Crash [Log](nxyeck)\n- Select Default Cube, Go to Materials tab: Crash [Log](ixgrhp)\n- Change Viewport Shading mode to Material Preview: Crash [Log](diwmma)\n- Change Viewport Shading mode to Render Preview: Crash [Log](ztajes)\n- DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: Crash [Log](gcaded)\n- Change Render Engine to Cycles, Press F12 to Render Image: **No** crash\n- Change Render Engine to Cycles, Click on Shading workspace: Crash [Log](chmkgj)\n- Change Render Engine to Cycles, Go to Materials tab: **No** crash\n- Change Render Engine to Cycles, Change Viewport Shading mode to Material Preview: Crash [Log](fhfyfo)\n- Change Render Engine to Cycles, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Cycles, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\n- Change Render Engine to Workbench, Press F12 to Render Image: **No** crash\n- Change Render Engine to Workbench, Click on Shading workspace: **No** crash\n- Change Render Engine to Workbench, Go to Materials tab: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Material Preview: **No** crash\n- Change Render Engine to Workbench, Change Viewport Shading mode to Render Preview: **No** crash\n- Change Render Engine to Workbench, DEL to delete Default Cube, SHIFT+A M P to create a Plane, Go into Materials Tab, Create Material: **No** crash\nThank you for your help.\n\n", "Crash when moving to Shading workspace\nOperating system: Darwin-16.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.17.5 355.10.05.45f01\n\n|Broken:|version: 2.83.0, commit date: 2020-06-03,|hash: `211b6c29f7`\n| -- | -- | -- |\n||version: 2.90, commit date: June 08,|hash: `9f7d84b656`\n|Worked:|version: 2.82|-\n\nWhen I open Blender, without changing anything in the default scene, if I move to the 'Shading' workspace my system freezes for a few seconds and crashes (it closes).\n\n- Default startup scene\n- click on 'Shading' workspace from the top bar\n", "Shader compilation is crash\nOperating system: Linux-6.3.0-1-MANJARO-x86_64-with-glibc2.37 64 Bits, X11 UI\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 23.0.3\n\nBroken: version: 3.5.1, 3.6.0\nWorked: 2.93.17, 3.3.6\n\n\nI am creating a shader and I need to use a lot of color mix node:\n| Version | Result |\n| -- | -- |\n| 2.93.17 |  |\n| 3.3.6 |  |\n| 3.5 |  |\n\n\nLaunch attached blend in different the Blender versions", "Cycles HIP device crash on rendering on latest AMD Adrenaline Driver\nOperating system: Windows 11 Pro for Workstation\nGraphics card: AMD Radeon RX 6750XT (Driver: AMD Adrenaline 23.7.1, 23.7.2 23.8.1 23.9.1)\n\nBroken: 3.6.1 LTS (On latest driver)\nWorked: 3.6.1 LTS (On old driver: AMD Adrenaline 23.5.2)\n\nAfter synchronizing objects, Blender crash\nBut render the default cube scene Blender works well even using 23.7.1 driver\n\nBased on the default startup or an attached .blend file (as simple as possible).\nScene is from Blender official demo file: \nbarbershop_interior/\nCrash log file: \n\n", "Crash when playing animation in rendered view (cycles)\nOperating system: macOS-12.0.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Max Apple 4.1 Metal - 76.1\n\nBroken: version: 3.0.0, 3.5\nWorked: unknown\n\nPlaying animations in cycles rendered view frequently crash blender. With the attached file I consistently get a crash within 1-2 minutes of starting the animation.\n\nThe crashes do not occur when running the intel version through rosetta. They occur much faster/more often when using the CPU than when using the GPU.\n\nOpen attached file\nSwitch to rendered view (Crashes with and without Metal preference)\nPress spacebar to play\n\n[Boat boating.blend](Boat_boating.blend)\n[Animation crash.txt](Animation_crash.txt)\n```\nThread 17 Crashed:\n0 Blender \t 0x10319354c tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 340\n1 Blender \t 0x103193644 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 588\n2 Blender \t 0x103192c60 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 184\n3 Blender \t 0x103183300 tbb::internal::arena::process(tbb::internal::generic_scheduler&) + 252\n4 Blender \t 0x10318c3b8 tbb::internal::market::process(rml::job&) + 40\n5 Blender \t 0x10318d6b0 tbb::internal::rml::private_worker::run() + 288\n6 Blender \t 0x10318d584 tbb::internal::rml::private_worker::thread_routine(void*) + 12\n7 libsystem_pthread.dylib \t 0x1b39cd4ec _pthread_start + 148\n8 libsystem_pthread.dylib \t 0x1b39c82d0 thread_start + 8```", "Crash with mantaflow\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nBaking simulation causes crash\n\n[splash.blend](splash.blend)\n\nOpen file and bake liquid\n", "Pack UV's crashes blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "Crash going to material preview or rendered shading mode Blender 2.83.0\nMacBook Pro 15 inch Early 2013\n2.7 GHz Intel Core i&\n16 GB 1600 Mhz DDR3\n|Operating system:|MacOS 10.12.5 - @Tramfabriek\n| -- | -- |\n||Mac OS X 10.12.6 (16G2136) - @johan-eds\n|| macOS 10.12.6 - @UmbertoOldani\n\n|Graphics card:|NVIDIA GeForce GT 650M 1024 MB + Intel HD Graphics 4000 1536 MB - @Tramfabriek\n| -- | -- |\n||NVIDIA GeForce GTX 775M, PCIe, 2048 MB - @johan-eds\n|| NVIDIA GeForce GTX 680MX 2048 MB - @UmbertoOldani\n\nBisected to find the bad commit: 804e90b42d\n\nCrash when clicking on Viewport Shading >Material Preview or >Rendered\nThis did happen already in the 2.83 betas, but none of the 2.82 and earlier version had this problem on this computer running this same OS at least since Blender 2.79.\n\n**System crash report 1** (crash in `UI_draw_roundbox_aa` -> `GPU_batch_draw `. Probably the material render icon):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff909add42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff90a9b457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff909134bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff9091342f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff88cdbfbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff76297390 0x7fff7607a000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff88cdd524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff76385867 0x7fff7607a000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff763554fd 0x7fff7607a000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff76282a2b 0x7fff7607a000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff7626ee9a 0x7fff7607a000 + 2051738\n11 com.apple.GeForceGLDriver \t0x00007fff76289654 0x7fff7607a000 + 2160212\n12 com.apple.GeForceGLDriver \t0x00007fff7626af97 0x7fff7607a000 + 2035607\n13 com.apple.GeForceGLDriver \t0x00007fff763851ad gldUpdateDispatch + 1041\n14 GLEngine \t0x00007fff7ff1d32a gleDoDrawDispatchCoreGL3 + 520\n15 GLEngine \t0x00007fff7fecebd9 gleDrawArraysOrElements_Entries_Body + 128\n16 GLEngine \t0x00007fff7fecaab4 glDrawArraysInstanced_GL3Exec + 220\n17 org.blenderfoundation.blender \t0x0000000109614f2c GPU_batch_draw_advanced + 428\n18 org.blenderfoundation.blender \t0x0000000109614d6c GPU_batch_draw + 124\n19 org.blenderfoundation.blender \t0x0000000105218c51 UI_draw_roundbox_aa + 353\n20 org.blenderfoundation.blender \t0x0000000104f3d96c ED_region_do_draw + 1372\n21 org.blenderfoundation.blender \t0x0000000104b6d49c wm_draw_update + 2092\n22 org.blenderfoundation.blender \t0x0000000104b6b010 WM_main + 48\n23 org.blenderfoundation.blender \t0x0000000104827762 main + 962\n24 libdyld.dylib \t0x00007fff9087f235 start + 1\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5b521f78 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5b521fa0 rsp: 0x00007fff5b521f78\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x000000011ab85cf8 r13: 0x0000000000000000 r14: 0x00007fff998033c0 r15: 0x000000011ab85000\n rip: 0x00007fff909add42 rfl: 0x0000000000000206 cr2: 0x00007fff960d0b58\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n\n**System crash report 2** (crash in `blf_batch_draw ` -> `GPU_batch_draw `):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff8b1dfd42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cd457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff8b1454bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff8b14542f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff83587fbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff71040390 0x7fff70e23000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff83589524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff7112e867 0x7fff70e23000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff710fe4fd 0x7fff70e23000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff7102ba2b 0x7fff70e23000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff71017f8e 0x7fff70e23000 + 2051982\n11 com.apple.GeForceGLDriver \t0x00007fff7100b6bc 0x7fff70e23000 + 2000572\n12 com.apple.GeForceGLDriver \t0x00007fff7100bec2 0x7fff70e23000 + 2002626\n13 com.apple.GeForceGLDriver \t0x00007fff7101113f 0x7fff70e23000 + 2023743\n14 com.apple.GeForceGLDriver \t0x00007fff7143f25e 0x7fff70e23000 + 6406750\n15 com.apple.GeForceGLDriver \t0x00007fff7143f4e6 0x7fff70e23000 + 6407398\n16 com.apple.GeForceGLDriver \t0x00007fff7143f5d7 0x7fff70e23000 + 6407639\n17 com.apple.GeForceGLDriver \t0x00007fff71013d3d 0x7fff70e23000 + 2035005\n18 com.apple.GeForceGLDriver \t0x00007fff7112e1ad gldUpdateDispatch + 1041\n19 GLEngine \t0x000000011925232a gleDoDrawDispatchCoreGL3 + 520\n20 GLEngine \t0x0000000119203bd9 gleDrawArraysOrElements_Entries_Body + 128\n21 GLEngine \t0x00000001191ffab4 glDrawArraysInstanced_GL3Exec + 220\n22 org.blenderfoundation.blender \t0x000000010b288f2c GPU_batch_draw_advanced + 428\n23 org.blenderfoundation.blender \t0x000000010b288d6c GPU_batch_draw + 124\n24 org.blenderfoundation.blender \t0x000000010b283d82 blf_batch_draw + 418\n25 org.blenderfoundation.blender \t0x000000010b282359 BLF_batch_draw_end + 9\n26 org.blenderfoundation.blender \t0x0000000106fc2163 view3d_draw_region_info + 8515\n27 org.blenderfoundation.blender \t0x0000000106936dbd DRW_draw_callbacks_post_scene + 445\n28 org.blenderfoundation.blender \t0x00000001069376cd DRW_draw_render_loop_ex + 1757\n29 org.blenderfoundation.blender \t0x0000000106fc2668 view3d_main_region_draw + 136\n30 org.blenderfoundation.blender \t0x0000000106bb157e ED_region_do_draw + 366\n31 org.blenderfoundation.blender \t0x00000001067e149c wm_draw_update + 2092\n32 org.blenderfoundation.blender \t0x00000001067df010 WM_main + 48\n33 org.blenderfoundation.blender \t0x000000010649b762 main + 962\n34 libdyld.dylib \t0x00007fff8b0b1235 start + 1\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff598ab4b8 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff598ab4e0 rsp: 0x00007fff598ab4b8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x0000000120bebcf8 r13: 0x0000000000000000 r14: 0x00007fff93fe13c0 r15: 0x0000000120beb000\n rip: 0x00007fff8b1dfd42 rfl: 0x0000000000000206 cr2: 0x00007fff8b1c727d\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n1. Open Blender\n2. Click to remove start up information panel\n3. Click on Viewport Shading >Material Preview or >Rendered\n\nResult:\nCrash", "Blender 2.91 crashes when enabling Archipack addon\nOperating system: Linux-5.8.0-23-generic-x86_64-with-debian-bullseye-sid 64 Bits\nUbuntu 20.10 Groovy Gorilla (development branch)\nGraphics card: Mesa Intel(R) UHD Graphics 620 (KBL GT2) Intel 4.6 (Core Profile) Mesa 20.2.0\n\nBroken: version: 2.91.0 Alpha\n\nBlender crashes after enabling Archipack addon. Terminal says 'Aborted (core dumped).' Also, Blender doesn't record a crash.txt (that I can find). \n\nStart Blender>Edit>Preferences>Addons>Enable Archipack addon.\n\n[CoreDump.mp4](CoreDump.mp4)\n", "Crashing/unexpected results while rendering custom Node-defined volumetric materials\nOperating system: Linux-5.6.0-2-amd64-x86_64-with-glibc2.29 64 Bits\nGraphics card: AMD Radeon (TM) RX 470 Graphics (POLARIS10, DRM 3.36.0, 5.6.0-2-amd64, LLVM 10.0.0) X.Org 4.6 (Core Profile) Mesa 20.0.7\n\nBroken: version: 2.91.0 Alpha\nWorked: Never\n\nWhen rendering the attached .blend file, Blender frequently crashes or at the very least fails to render properly. It seems to be something to do with the materials I've defined for Evee to use.\n\n\n[#79682.blend](T79682.blend)\n- Open file\n- Render animation", "Crash when rendering animations (GPU Subdivision ON, OFF is fine)\nSystem Information\nOperating system: WIndows 11 22H2\nGraphics card: Nvidia GeForce RTX 4080\n\nBlender Version\nBroken: 3.4.1, 3.5, 3.6\n\nForce closes when rendering animation after a number of frames and when opening larger blend files. Happens with all files. All drivers up to date and tested memory with no issues. Worked without issue for 6 months, crashing started 1 week ago.\n\nRendering animation with GPU Subdivision unchecked did not trigger a crash", "Freeze when using Object.ray_cast in a driver script\nOperating system: Linux-5.10.15-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.15-1-MANJARO, LLVM 11.0.1) AMD 4.6 (Core Profile) Mesa 20.3.4\n\nBroken: version: 2.91.2, 8dc95f61f3\nWorked: Unknown, fails on at least as old as 2.83.10.\n\nRunning a driver that includes a call to Object.ray_cast will freeze the interface entirely. Still exits normally when sent a SIGTERM. It does not create a crash.txt. Blender crashes with a segmentation fault in version 2.83.10 (hash: `b439a155442b`), and does create a crash.txt (see attached). Blender version 2.93.0 Alpha (hash: `7a608f88a713`) also freezes in the same way as 2.91.2. Using the ray_cast function in a non-driver script appears to function as expected.\n\nIn the attached blend file, run the text block `TurretRayCasting.py`, to put the script into the driver namespace. Next, click \"update dependencies\" in the driver panel. The application should freeze entirely. If `return target.ray_cast(turretTargetSpace, direction)- [x]` is commented out and replaced with `return True`, the application does not freeze.\n\n[driver_freeze2.blend](driver_freeze2.blend)\n\n[driver_freeze2.crash.txt](driver_freeze2.crash.txt)\n\n[system-info-2.91.2.txt](system-info-2.91.2.txt)", "rendering crashed\nOperating system:\nGraphics card:\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n" ]

[ "OpenCL Crashing\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX 5500 XT ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.1 27.20.2001.13001\n\nBroken: version: 2.83.1\n\n\n\nI trying use the opencl gpu, but the blender show to me \"Loading Kernels\", ok... and he some times work, but the mostly he hang and crash the blender. I cant use blender cycles with amd gpu.\n\n", "Loading Render Kernel Crash\nOperating system: Windows 10 Education 18363.1198\nGraphics card: 5700 XT\nCPU: Ryzen 5 3600\nRAM: 32Gb\n\nBroken: (example: 2.90.1\nWorked: (newest version of Blender that worked as expected) - Even Experimental 2.91 Beta didn't work\n\nRendering with GPU in cycles crashes in both rendered viewport and render image after never several minutes of waiting on kernels to load.\nBased on the default startup or an attached .blend file (as simple as possible).\nI go Preferences>System>OpenCL and ensure that my GPU is enabled, Scene>Render Engine: Cycles>Device: GPU Compute, and any attempt at rendering leads to a crash after waiting on kernels to load. Blender benchmark also doesn't work and gives error id: 99dcc67cb7174f5cb1718aca04080024\nI've updated, reinstalled, (downdated?) and every which way with my GPU drivers, blender version, and windows. Nothing seems to work. \n", "OpenCL render on AMD GPU doesn't start\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14736 Core Profile Context 20.11.1 27.20.12033.2007\n\nBroken: version: 2.90.1[log (2).txt](log__2_.txt)\nWorked: At earlier versions of AMD drivers\n\nOpenCL just doesn't render any scene I try to start\n\nI just try to start rendering any scene with GPU and it spits out some errors\nI attached an error log from system console\n\n", "Crash AMD video cards, closes \\ hangs\nOperating system: Win10\nGraphics card: Asrock Radeon RX5700XT \n\nBroken: (example: 2.80 and +, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (Nothing)\n\n**Short description of error** \nDuring real-time rendering, the blender closes on any version of the program, initially I had a \"MSI RX460 2 GB\", now I bought a \"RX5700XT\" but the problem has not changed, it was on both devices. the blender just closes or hangs. Sometimes it closes during normal rendering ... I can't work, and I don't understand what the problem is, at first I thought that Eve and Cycles are poorly compatible with AMD video cards, installed Radeon ProRender, which is adapted for them, but alas, the same trouble. .. I do not know what is the cause of the error, I cannot identify it for a long time.\n\nI found one option when the program freezes exactly, you need to enable real-time rendering of Cycles, Prorender, Eve \\ set the checkbox to work in the CPU + GPU render and continue working. Very often freezes in this mode.", "Blender recognize my gpu but won't use it for render in cycles ( crash )\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n[gpucrash.blend](gpucrash.blend)\n\n\nBroken: 2.90.0\nWorked: none\n\nWhen i want to shading my project with Cycles and render , there is written \"loading render kemels ( may take a few minutes the first time\" , i wait and then it crash without any messages, i can only render with my ryzen 5 3600 and this is lower for renders \n\n\nGo to shading workspace , then use Cycles as render engine, use render shading , choose GPU calcul , and then it crash for me \n\nThank for checking ", "Open CL is not working with my graphics card in cycles.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14736 Core Profile Context 20.11.1 27.20.12033.2007\n\nBroken: version: 2.90.1\n\n[Blender doesn't use open Cl with my Graphics card in Cycles. After enabling open CL by selecting my card in \"user preferences\", blender displays \" loading render canals\" and then closes itself (crashes).]\n\n Step-1: Open blender with the default cube setup.\n Step-2: Go to user preferences.\n Step-3: Open system tab.\n Step-4: Select open CL. \n Step-5: Select Radeon Rx 5700xt ( if you have one) and close the window.\n Step-6: Go to render properties tab and select cycles.\n Step-7: Select GPU in \"device\".\n Step-7: Open rendered view in viewport by pressing \"Z\" key on keyboard.\n\nNo file is attached. This error occurs every time I render something, even with the default blender scene. \n\nThanks for your time! \n\n", "Crash during cycles GPU rendering in viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.3.1 26.20.15029.15007\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional) \n\nBlender crashes when using my GPU to render with cycles. This does not occur when using CPU. This does not occur when using F12 to render, only when in viewport.\nThis occurs when rendering anything, including a basic cube.\nBlender displays \"Loading render kernels\" for a period of time before closing with no error message.\nRunning it via the console shows an LLVM error.\nI have tested it on blender 2.81 as well and it does not work there.\n\n- Open .blend file\n- Set cycles to use opencl with RX5700 XT\n- Set GPU compute in render options\n- Change viewport to render view\n- Wait until crash\n\n[bug.blend](bug.blend)\n\n[2.82 debug logs.txt](2.82_debug_logs.txt)\n\n[2.81 logs.txt](2.81_logs.txt)\n\n", "Crash Blender on GPU render AMD Radeon RX 5700 XT OpenCL\nSystem Information\n\nOperating system: Windows 10 Pro. CPU Intel i7-6700K 4.00 GHz\nGraphics card: AMD Radeon RX 5700 XT 8GB - Driver Version 20.5.1\n\nBlender Version: v2.83.0\n\nShort description of error:\n\nTrying to Render in Cycles Engine with OpenCL - GPU Compute. \nStar the Render Blender Freeze and in the Task Menu the GPU is on 0%\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "Blender closes when rendering anything (including default startup scene) with GPU - Stuck on compiling render kernals unless manual close and restart of render.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\n\n\n\nSo I have tried latest drivers of AMD, latest blender experimental, previous blender experimental and everything results in the same issue using a AMD 5700XT. To replicate this you have to create a new scene, switch to cycles and GPU and then start a render, it hangs on 'compiling render kernals' until the windows time out just closes blender, I have changed to GPU timeout (can't remember what the term is Kdi?) to 60 seconds and seems to crash after that time has lapsed. I have found a workaround where I press esc when it's compiling and then if I restart the render it works straight away and starts rendering! Its a really confusing issue and I guess I can carry on with pressing esc before every render but that will get annoying ha.\n\n", "RX 5700 XT Cycles Crash\nOperating system:\nCPU: AMD Ryzen 5 3600\nGraphics card: AMD Radeon RX 5700 XT\nRAM: Corsair Vengeance rgb pro 16gb 3200mhz\nMotherboard: Asus Prime x570-p\nNVME: Adata sx8200 256 gb \nHDD: Toshiba 1TB\nPower Supply: 700w 80+Gold\n\n\nBroken: 2.83\nWorked: None\n\nBlender crashes on cycles gpu compute, cannot do render view and final render\n\nRender Properties > Render Engine > Cycles > GPU Compute \nand then do render view or final render, blender crashes instantly without any error message", "Radeon 5700 XT - Cycles - crash 2.8.x\nHI, awesome Blender team!!! Greetings from Poland!!\n\nRecently i bought GFX card AMD Radeon RX 5700 XT and i cant use it in cycles. in any case in render cycles Blender is going off. Any tips for old user ? THX...\n\nspecifications/\n\nBlender 2.83.4 - Up to date\n\n     \n\nF12\n\n\n\nRender of This very file without AMD Radeon RX 5700 XT - just On Radeon Vega 11 - before shopping was OK :( but no speed.\n\n\n\nGfx Ati Drivers: Up to date\n\n\nMachine Details:\nOS:\nOperating System: Windows 10 Home 64-bit (10.0, Build 19041) (19041.vb_release.191206-1406)\nLanguage: Polish (Regional Setting: Polish)\nSystem Manufacturer: Micro-Star International Co., Ltd\nSystem Model: MS-7B86\nBIOS: A.70 (type: UEFI)\nProcessor: AMD Ryzen 5 2400G with Radeon Vega Graphics (8 CPUs), ~3.6GHz\nMemory: 32768MB RAM\nAvailable OS Memory: 30668MB RAM\nPage File: 5835MB used, 29441MB available\nWindows Dir: C:\\WINDOWS\nDirectX Version: DirectX 12\nMiracast: Available, with HDCP\n\nGFX:\nCard name: AMD Radeon RX 5700 XT\nManufacturer: Advanced Micro Devices, Inc.\nChip type: AMD Radeon Graphics Processor (0x731F)\nDAC type: Internal DAC(400MHz)\nDevice Type: Full Device (POST)\nDevice Key: Enum\\PCI\\VEN_1002&DEV_731F&SUBSYS_04E21043&REV_C1\nDevice Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] \nDevice Problem Code: No Problem\nDriver Problem Code: Unknown\nDisplay Memory: 23486 MB\nDedicated Memory: 8152 MB\nShared Memory: 15334 MB\nCurrent Mode: 1680 x 1050 (32 bit) (60Hz)\nHDR Support: Not Supported\nDisplay Topology: Clone\n Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709\nColor Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.149414,0.059570), White Point(0.312500,0.329102)\nDisplay Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000\nMonitor Name: Generic PnP Monitor\nMonitor Model: L226W \nMonitor Id: GSM566B\nNative Mode: 1680 x 1050(p) (59.883Hz)\nOutput Type: DVI\nMonitor Capabilities: HDR Not Supported\nDisplay Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP\nAdvanced Color: Not Supported\nMonitor Name: Generic PnP Monitor\nMonitor Model: PHILIPS FTV\nMonitor Id: PHL0000\nNative Mode: 1920 x 1080(p) (60.000Hz)\nOutput Type: HDMI\n\n\nAny advice will be great, i dont know what to do. :(\n\nRegards - Maciej Szczodrowski - 3D artist - and Blender fan!!!!\n", "Blender 2.90.1 crashes while redering with 5700xt\n[system-info.txt](system-info.txt)\n\nThis is my Systeminfo.\nI am trying to render a image with cycle but it always just closes up on the render with no kind of error or something.\nI know that this is already a known problem, but this annoys me very hard and i think it is finally time for a soloution.*\n" ]

[ "Update Tweak Tool behaviour on Right Click Select\nThis has been a long running known issue for the Active Tools when using right click select.\n\n## Issue\nOn RCS, the Tweak Tool in the toolbar is placing the 3D Cursor instead of tweaking elements.\nThis duplicates the behaviour of the Cursor Tool (right next to it in the toolbar).\n\nThe reason for this seemed to be that right click & drag is already using the tweak action.\nIf the Tweak Tool would tweak with left & right click then there is no way of setting the 3D cursor anymore.\n\nBut the Tweak Tool doesn't require the 3D cursor. And this workaround is breaking the tweak tools purpose.\n\n## Solution\n\nThe Tweak Tool needs to tweak with left click & drag.\nThis can be it's own keymap item in the preferences under the Tweak Tool.\nRight click & drag can still use the default tweak action in the preferences.\n\nThe benefits are:\n- The Tweak Tool can be used without a drag threshold with left click & drag, if the option \"Alt Cursor Access\" enabled in the preferences\n- There is a functional distinction between the Tweak Tool and the Cursor Tool.", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "Menu Hotkey do not work in Batch Rename Dialogue\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.0.1\n\nIn the Batch Rename Dialogue there the \"Type\" drop down. In this drop down pressing the underlined characters does not work like in other drop downs and menus.\n\n\n1. Select one or multiple objects\n2. Hit Ctrl + F2 for \"Batch Rename\"\n3. The \"Type\" drop down is set to \"Find/Replace\" by default\n4. Click the \"Type\" Drop Down to open it\n5. press \"S\" \n6. Nothing happens even though the drop down should now be set to \"Set name\" as indicated by the underlined \"S\".\n", "Assign shortcuts: add support for enum menus\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nFor group menus, can't assign shortcuts by right click, and no python tooltips on this. maybe it's not bug, but really need it.\n\n\nscreenshots:\n\n\n\n\n\n\n", "Weight Paint gradient operators wait for mouse input\nOperating system: Linux-6.4.6-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.6-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-50c29e1ffa)\n\nBroken: version: 4.0.0 Alpha\nWorked: --\n\nThis is based on feedback from #108791\nWhen using the gradient operators in weight paint mode, they don't start on shortcut press but require a mouse press to start and release to confirm.\n\nThis worked well with the previous default shortcut with mouse clicks but when reassigned to keyboard shortcuts this is very inconsistent with other operators in Blender and seems unintentional or outdated.\n\nA good counter example for a better behavior is \"Expand by Topology\" in sculpt mode, which only waits for mouse input if started from a menu. If executed with the keyboad shortcut `Shift A` it will start and then confirm with `LMB`.\nIf the shortcut is remapped to a mouse press, it will start on press and confirm with release. \n\n- Enter Weight Paint Mode\n- Press `Shift A` and use the operation\n- Try the same in Sculpt Mode\n\n", "Move Tool Todo\n## Move\n * - [ ] {icon circle color=green} Currently, distances are not well communicated while dragging, only the axis. We can make it much clearer how far you've moved your item, like so:\n\nHere, the distance moved is brighter than the rest of the axis line.\n * - [x] {icon circle color=yellow} The Redo panel for moving items should be simplified. The Constraint Axis controls should be hidden, and the Move X, Y, Z controls should always work. The current UI here is annoying to use and takes up lots of space.\n\n * - [x] {icon circle color=yellow} The tool has 3 names: 'Grab' (in the toolbar), 'Move' (inside the Redo panel), and 'Translate' (Redo panel title). It should have one name. 'Move' is the most universally understood word, that everyone will understand. The other two are ambiguous and unclear. ", "Gpencil: dopesheet selection issues [clicking in summary deselects corresponding ID channel, e.g. breaking \"Jump to keyframe\"]\nBroken: version: 2.92.0 Alpha\nWorked: n/a, tested with 2.91 and didn't work\n\nJump to keyframe command & shortcut doesn't work anymore when you duplicate a keyframe.\nDoesn't matter what amount of layers there are.\n\n1) Draw a keyframe\n2) Draw a nother keyframe at another time = works\n\nDuplicate 1) keyframe = doesn't work, please see the video\n\n\n[gp_duplicate_keyframe_jump.mp4](gp_duplicate_keyframe_jump.mp4)\n\nReason why this happens: clicking in the summary will deselect the corresponding greasepencil ID channel [on which the \"Jump to keyframe\" operator relies]\nClicking in the summary should not deselect every channel there is, but keep the channel representing the selected greasepencil object selected as well [same as for other object types such as meshes].\nThis goes hand in hand with selecting a grease pencil object in the 3DView or Outliner not selecting the corresponding ID channel [this should also be the case (same as for other object types such as meshes)]", "Assign Shortcuts: creates shortcut in the \"wrong\" space\n**OS**: Linux 5.3.8-arch1-1 x86_64\n\n**Blender version**\nBroken: 2.8x (up to and including fc79d27951)\n\nWhen using the context menu to assign shortcut to a button or checkbox, the shortcut is created in a wrong space, which may lead to error popups when pressing that shortcut with mouse hovering over a different space.\n\n\n1. Load the default scene.\n2. In 3D viewport, expand the Overlays popover, right-click the Wireframes checkbox and assign a shortcut through the context menu.\n3. Note that shortcut works while the mouse is over the 3D viewport.\n4. Move the mouse over the Properties and try pressing the shortcut. You'll get an error popup.\n\nThis is due to the shortcut being created in the Window space, not 3D View space.", "No way to distinguish enum buttons that support shift-click to select multiple\nBlender has some buttons that allow shift-click to select multiple, but no way to show the difference. eg:\n\nTransform Tool, Gizmo's (Move / Rotate / Scale)", "Viewport header menu, late/wrong responce to hover and click\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.1.0 Alpha\n\n\nSometimes menu stucks when mouse pointer already over another menu.\n[2021-11-12_14-21-18.mp4](2021-11-12_14-21-18.mp4)", "Gizmo can't display when select two object\n\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.2.0\n\n**Short description**\nTwo conditions are assumed:\n1. Two objects, one is movable and one is locked to move.\n2. The second is a child of the first.\n\nWhen a movable object is selected, the gizmo can be displayed normally\n\n\n\nwhen both are selected, the gizmo cannot be displayed, but they can be moved, so is it against common sense?\n\n\n[gizmo_bug.blend](gizmo_bug.blend)\n\n\n", "Improve keyboard usage for menu search popup\nNA\n\nBroken: example: 2.78\nWorked: >new feature request<\n\nwhen spacebar search menu popups and user start writing the required command, only down-arrow keyboard shortcut are allowed to select the required command, starting from first item on top.\nIt will be very useful and faster if also up-arrow can be usable to select the last item in the list (so starting from bottom).\nSee image as reference: green arrow show the required feature, red one is the only one actually working.\n\n\nnot an error, only UI usage improvement :)\n", "Intersect Selection in edit mode\nOperating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.3.0 Alpha\n\nIntersect existing Selection apply just to what in the viewport frame \nI can t reproduce it with an exact steps\nopen the linked file and select some vertexes with Select Box and with Intersect Mode\nthe intersection apply just to the vertexes shown in the viewport frame \nsame problem in 2.83 - 3.1 - 3.2\n[bug.blend](bug.blend)", "Drag tool-tip stays when mouse leaves the window\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nTool-tips displayed on drag stays after mouse leaves window\n\nOpen any file importer and drag any file, after exit the main window tooltip will still show\n\n\n\n<video src=\"attachment\" title=\"2023-08-18 21-26-50.mp4\" controls></video>\n\n", "Select next active fails in some cases (default cylinder, cube)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: Quadro K2100M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 411.63\n\nBroken: version: 3.1.2\n\nWhen adding object: circle or cylinder, when selecting vertices, it does not select the next vertex at command: shif + ctrl + (+).\nif I select several vertices manually and give the command: shift + ctrl + (-) deselect, it works perfectly.\n\nany other option works, works well with other objects, sphere, monkey sesame, the circle object works if you select two consecutive vertices, if you select one vertex yes one no, it no longer works. .]\n\n- add cylinder object\n- Edit mode\n- Select 2 vertices then {key shift ctrl +}\n\n[2022-05-24 19-58-17.mp4](2022-05-24_19-58-17.mp4)" ]

[ "Regression: Drag Box Selection While (e.g. Transform) Tool is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.0\n\nCaused by 64dbfe714bbae4b4dc0ee2b179243fe1a821d89d\n\nFacing issue with drag selection while Transform tool is on. I am using right click to select. It was working fine with 3.41. After installing 3.5 it stopped working\n\n\n\n\n", "The drag option in the tool menu doesn't work\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.1\nWorked: version: 3.4.1\n\nThe Drag option in the tool menu doesn't work as it did in previous versions. If the Active Tool is not the Select, and the Drag setting is set to any of the selection options (Select Box, Select Circle, Select Lasso), dragging with the left mouse will behave as if the Drag was set to the Active Tool option.\n\n(An example: In version 3.5.1, if the Active Tool is set to Move, and the Drag option is set to the Select Lasso, dragging with the left mouse will move the selected object, while in version 3.4.1 it was using the lasso selection.)\n\n- Open Blender for the first time\n- In the quick setup, set the 'Select With' option to Right and save the new settings\n- In the default scene, set the active tool to Move\n- In the Tool menu, set the Drag option to Select Lasso\n- Select the default cube\n- Drag with the left mouse\n\n", "Regression on drag selection\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41\n\nBroken: version: 3.5.1\n\nI already report this some time ago and was solve but now is here again. For those like me that still continue selecting with right click, when you have any tool different than tweak tool active and drag the only option that works on drag is active tool.\n\n1. Set up blender to work with right click select.\n2. Select move tool(by default is to box select on drag).\n3. Drag cursor on viewport to select something and instead of do what is set on drag option it do the action of the active tool.\n\n" ]

[ "Crash on render\n**System Information** MSI BRAVO 15\nOperating system: WINDOW 11\nGraphics card: RX 6600\n\n**Blender Version**3.6\n\nWhen attempting to render a scene in Blender, the software consistently crashes, causing frustration and hindrance to the rendering process. This issue is hindering users from efficiently creating their projects and requires immediate attention to maintain a stable and reliable rendering environment.\n\n[debug-log](https://projects.blender.orgattachment)\n[system info](https://projects.blender.orgattachment)", "Segfault after F12 render with multi-GPU Intel ARC A770 and experimental oneAPI packages on Debian\nOperating system: Linux-6.4.0-1-amd64-x86_64-with-glibc2.37 (Debian sid)\nGraphics card: two identical Intel ARC A770 Limited Edition 16GB\n\nBroken: 3.6.1, 4.0.0 Alpha, branch: main, commit date: 2023-07-25 19:23, hash: aebc743bf1c7\nWorked: 3.4, 3.4.1, 3.5.1\n\nSegfault when rendering Victor benchmark scene with F12 with second Intel ARC A770. This happens only when the second GPU is chosen as rendering device in Cycles. If both GPUs are selected first one seems to work correctly, but the second one causes a crash/error.\nEmbree on GPU does not seems to matter.\n\nBoth F12 and viewport renders with the second GPU give:\n`oneAPI kernel \"shader_eval_curve_shadow_transparency\" execution error: got runtime exception \"Native API failed. Native API returns: -50 (PI_ERROR_INVALID_ARG_VALUE) -50 (PI_ERROR_INVALID_ARG_VALUE)\"`\n\nRelevant info:\nI'm using following packages from experimental sources (I'm impatient I know :) ), so this crash might be very well caused by their incompatibility with Debian sid:\n`libigc1` - 1.0.13822.1-1\n`libigdfcl1` - 1.0.13822.1-1\n`intel-opencl-icd` - 23.13.26032.7-1\nRest of the packages, including all dependencies are from Debian sid.\n\nFull backtrace:\n\n```\n(gdb) backtrace full\n#0 0x0000000001cfee77 in ?? ()\nNo symbol table info available.\n#1 0x0000000001cffab9 in ?? ()\nNo symbol table info available.\n#2 0x0000000001b0fa9c in ?? ()\nNo symbol table info available.\n#3 0x0000000000f376a3 in ?? ()\nNo symbol table info available.\n#4 0x00007fffebaa63ec in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:444\n ret = <optimized out>\n pd = <optimized out>\n out = <optimized out>\n unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140737147199792, -8317621660586406251, -286296, 11, 140737488344416, 140734520795136, 8317937541230038677, 8317594907036290709}, mask_was_saved = 0}}, priv = {\n pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}\n not_first_call = <optimized out>\n#5 0x00007fffebb26a1c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81\nNo locals.\n(gdb)\n```\n\n1. On Debian sid install experimental packages mentioned above.\n2. Set second ARC GPU as a rendering device in Blender. \n3. Open Victor benchmark scene.\n4. Hit F12 and wait for the crash.", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Blender 2.92.0 crashes when baking steam simulation\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\nCPU: Intel Core i7-8700K\nMemory: 32 GB\n\nBroken: version: 2.92.0\nWorked: I have not tried any other version than 2.92.0 (sorry)\n\nI tried to make a simple steam simulation following the steps described here: watch?v=_K0XsHht6pg. It crashed while baking, and tried to simplify the setup with a minimal set of objects, and it still crashes after baking about 30-50% of the 300 frames.\n\nFollow the steps as described in the video watch?v=_K0XsHht6pg\n\nAttached is .blend file that I tried to make as simple as possible: [steam.blend](steam.blend)\n\n - Open the attached file\n - Press \"Bake Data\" for Physics Properties for the cube\n - Blender crashes after 30%-50% of baking\n\nI have not tried a newer experimental release or an older release.\n\nI was able to reproduce the issue with the default 32 Resolution Divisions (which is way faster to reproduce than the 160 in the included file). I then tried experimenting which exact setting caused the crash. I got it to crash with Adaptive Domain disabled, and Gas Heat 1.5 and Dissolve Time 30, but now I'm not able to reproduce anymore with any setting (at least with 32 Resolution Divisions).\n\nAfter some more experimenting, it seems it randomly crashes and sometimes works. It is definitely reproducible with 32 Resolution Divisions. I kept all settings as I had before, which had worked successfully, but then changed the Time Scale to 0.8, and then it crashed again when baking. However, it had previously crashed at least once with the exact same settings with which I had also successfully baked (and the Time Scale at the default 1.0), so it is not the Time Scale that is causing the issue.", "Crash on forcing laptop to sleep when rendering animation\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78\nCpu AMD Ryzen 7 4800h\n\nBroken: version: 3.3.1\nWorked: Maybe never? (able to reproduce in 2.83)\n\nblender crash when I wake up my laptop , I lost my unsaved file\n\n- Open .blend file\n- Start render animation\n- Force laptop to sleep {nav Start -> Power -> Sleep}\n[test1.blend](test1.blend)\n[test1.crash.txt](test1.crash.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n", "Crash when importing a file using python from the command line with an asset browser open\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.42, 5.15.0-40-generic) AMD 4.6 (Core Profile) Mesa 22.0.1\n\nBroken: version: 3.3.0 Alpha\nWorked: -\n\nBlender crashes with segfault when trying to import a model using `blender --python-expr` when the startup file or the opened file has an asset browser open.\n\nDownload [sample model ](Sponza) from KhronosGroup github.\n\nRun blender with:\n\n```\nblender <path/to/file/with/asswet/browser/open> --python-expr 'import bpy; bpy.ops.import_scene.gltf(filepath=\"/<PATH>/Sponza.gltf\")'\n```\n\nBlender crashes with the follow stack trace:\n\n```\n* thread #1, name = 'blender', stop reason = signal SIGSEGV: invalid address (fault address: 0x5c0)\n * frame #0: 0x0000000004b21c10 blender`filelist_file_ex(filelist=0x0000000000000000, index=-1, use_request=true) at filelist.c:2231:36\n frame #1: 0x0000000004b22070 blender`filelist_file(filelist=0x0000000000000000, index=-1) at filelist.c:2277:10\n frame #2: 0x0000000004b2914e blender`ED_fileselect_active_asset_get(sfile=0x00007fffdaf50988) at filesel.c:472:30\n frame #3: 0x0000000004b2f636 blender`file_listener(listener_params=0x00007fffffffe7a0) at space_file.c:467:38\n frame #4: 0x0000000003ca4f3c blender`ED_area_do_listen(params=0x00007fffffffe7a0) at area.c:163:5\n frame #5: 0x0000000003259301 blender`::wm_event_do_notifiers(C=0x00007ffff3f84388) at wm_event_system.cc:619:11\n frame #6: 0x000000000324f100 blender`WM_main(C=0x00007ffff3f84388) at wm.c:626:5\n frame #7: 0x0000000002a73fe9 blender`main(argc=4, argv=0x00007fffffffe978) at creator.c:547:5\n frame #8: 0x00007ffff7dba290 libc.so.6`__libc_start_call_main + 128\n frame #9: 0x00007ffff7dba34a libc.so.6`__libc_start_main@@GLIBC_2.34 + 138\n frame #10: 0x0000000002a73ba5 blender`_start + 37\n```\n\n**Additional information**\n\nBlender does not crash if the same command is run in the python console when blender is opened.", "The version over 3.5 (3.6 and 3.6.2) crashes for me after using control of view.\nOperating system: Linux-6.2.0-32-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics 650 (Kaby Lake GT3e) (KBL GT3) Intel 4.6 (Core Profile) Mesa 23.0.4-0ubuntu1~22.04.1\n\nBroken: 3.6 and 3.6.2\nWorked: version: 3.5.0\n\n\nI have quite simple scene: 1 table, 1 chair. I change selection from chair to table f.x., then deselection or I make zoom out, the screen freezes, Blender proposes me to closing because not responding\n\n", "Blender crashes with Segmentation fault when selecting Render Preview in Cycles with GPU Compute\nOperating system: Linux-6.1.46-gentoo-gentoo-dist-x86_64-12th_Gen_Intel-R-_Core-TM-_i3-12100F-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 6400 (navi24, LLVM 16.0.6, DRM 3.49, 6.1.46-gentoo-gentoo-dist) AMD 4.6 (Core Profile) Mesa 23.1.6\n\nBroken: version: 3.6.0\nWorked: - (read description)\n\nWhen I try to render using Cycles on my GPU, blender immediately crashes with Segmentation fault, as the error message. Here are the logs that were shown right before the Segmentation fault:\n```\nI0903 17:06:40.864868 14239 device.cpp:511] Mapped host memory limit set to 12,302,073,856 bytes. (11.46G)\nI0903 17:06:40.865039 14239 device_impl.cpp:62] Using AVX2 CPU kernels.\nWriting: /tmp/blender.crash.txt\nzsh: segmentation fault blender-3.6 --debug-all\n```\nIt worked with =dev-libs/rocm-comgr-5.3.3-r2, but started happening after the new update of the package. I used to apply a patch that solved the problem of being unable to select the render device in Blender's options (27552#issuecomment-1379233453), but with the new rocm-comgr package, the original problem solved itself. The old version of Blender (version 3.5.1) that worked before rocm-comgr got the new update, doesn't work now.\n\n1. Open the Render properties tab and set the Render Engine to Cycles.\n2. Set the device to GPU Compute.\n3. Set the viewport shading to Rendered.\n\n", "Combine crash\nOperating system: win 10\nGraphics card: 3090\n\nBlender Version 3.5.1 \n\nWhen using ctrl+j to combine components, blender will crash.\n\n", "Eevee randomly causes system to crash when rendering\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 (8GB memory)\nCPU: Intel Core i9 9900k\nRAM: 32GB DDR4\n\nBroken: 3.0.0\n\n\nI'm new to Blender and currently trying to switch from my usual C4D and Redshift workflow, just to let you know.\n\nI have a fairly simple scene with a 250 frame animation. Everytime I render the animation with Eevee as a .png sequence with an .exr file for the layers, the process causes my system to crash.\nThe amount of samples seems to correlate with the amount of frames I'm able to render before failure. So I guess it might have something to do with memory.\n\nI'm not sure how that can be as more complex scenes never failed me before using Redshift as a render engine.\n[ocean_final.blend](ocean_final.blend)\nThe scene makes use of a lot of volumetric light and I also calculate the bloom.\n\nThere aren't a lot of vertices involved in the scene, but I'm not sure how I can display a value to give you here.\n\nAll drivers are up to date and I also reinstalled Blender.\n\nNot sure, but I attached the .blend file as well as logs created in debug mode.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)", "Crash handling collections in a timer\nOperating system: Mac OS Monterey version 12.0.1\nGraphics card: Radeon Pro 555X 4 GB\n\nBroken 3.0.1\nbroken blender-3.2.0-alpha+master.d3b1cce4000b-darwin.x86_64-release.dmg \n\nBuilding Nodes add-on causes Blender to crash consistently when editing nodes in Building Style Editor window. I've been in communication with the author off the add-on (user name Durman on GitHub), and he has provided the script and instructions to reproduce the crash below.\nCrash log [blender.crash.txt](blender.crash.txt)\nAsan report [F12872713](T95861_asan.txt)\n\n[#95861.blend](T95861.blend)\n\n1. Open the attached file\n4. Push execute button of the text editor\n5. Wait until the crush\n\n", "Blender is crashing instantly to the desktop randomly (solid viewport)\n\nOS: Windows 10 Pro 64bit (Version 21H2, OS Build 19044.2006)\nGPU: Nvidia GeForce RTX 2070 (Driver: Version 517.48 (released 27th September 2022))\nCPU: AMD Ryzen 7 2700\nRAM: 64GB\n\n\nBroken: version: 3.3 (and versions for the last couple of years)\nWorked: none since 2020 approx.\n\n\nBlender crashes seemingly randomly when performing modelling actions such as moving vertices, clicking sliders or buttons, switching to wireframe view, or moving the viewport camera in any way. There may be other actions that cause crashes. Crashes cause Blender to instantly close to desktop, leaving no crash dumps. Crashes occurring over multiple versions since 2020, multiple reinstallations of the OS, and clean reinstallations of graphics driver.\n\nUsing blender_debug_gpu.cmd, I was able to retrieve a log from a crash that has some differences to a normal log:\n\n\"*INFO (gpu.debug): Notification : Buffer usage warning: Analysis of buffer object 82 (bound to GL_SHADER_STORAGE_BUFFER (1)) usage indicates that the GPU is the primary producer and consumer of data for this buffer object. The usage hint supplied with this buffer object, GL_STATIC_DRAW, is inconsistent with this usage pattern. Try using GL_STREAM_COPY_ARB, GL_STATIC_COPY_ARB, or GL_DYNAMIC_COPY_ARB instead.*\"\n\nCurrently, have no way to reproduce the crashes at will, they just seem to happen during my normal work. Load tests using OCCT do not cause crashes.\n\n**Debug log from crash**:\n[blender_debug_output2.txt](blender_debug_output2.txt)\n\n**Normal debug log**:\n[blender_debug_output_normal.txt](blender_debug_output_normal.txt)", "Error when denoising (Optix) large image\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090, 3060 Driver 522.30\n\nBroken: version: 3.3.1\nWorked: Never (3.0 failed, 2.90 did not start rendering)\n\nDenoising large image will fail and may result in crash.\n\nShortened log:\n```\nIllegal address in CUDA queue synchronize (film_convert_float3 filter_guiding_preprocess)\nE1122 18:16:01.843204 7088 denoiser_optix.cpp:470] Error converting denoising passes to RGB buffer.\nIllegal address in CUDA queue copy_from_device ()\n```\n\n[#102515.blend](T102515.blend)\n\nOpen file and render image.", "Debug information not generated upon crash.\nOperating system: Arch Linux 6.4.12-arch1-1\nGraphics card: AMD ATI Radeon 680M\n\nBroken: 3.6.2\nWorked: Could not determine (tried up to 3.5.1, which does not work without a full system downgrade)\n\nBlender crashes immediately upon launch.\n\nLaunching from the command line, I get this:\n```\nWriting: /tmp/blender.crash.txt\nSegmentation fault (core dumped)\n```\n\nThe contents of /tmp/blender.crash.txt are this:\n```\n# Blender 3.6.2, Commit date: 2023-08-14 14:05, Hash ffe93138751e\n\n# backtrace\n\n# Python backtrace\n```\n\nPassing the --debug-all flag, I get no errors. I attached the output of this command as a text file.\n\nWhile Blender crashing on startup is not in and of itself an issue worthy of reporting, the lack of any debug information immediately makes the problem impossible to tackle independently. I have no idea what my next steps should be here.\n\nLaunch blender.\n\n", "Blender randomly crash without reason in 'glDrawElementsInstancedBaseVertex' (in 'OVERLAY_wireframe_draw' or 'workbench_draw_sample')\n|Operating system:|macOS-10.14.6-x86_64-i386-64bit 64 Bits|@MaciejSobolewski\n| -- | -- | -- |\n||macOS Big Sur 11.1 2.4 GHz 8-Core Intel Core i9 64 GB 2667 MHz DDR4|@RonMartin\n||Darwin-18.7.0-x86_64-i386-64bit 64 Bits|@aayerbe\n||Darwin-20.3.0-x86_64-i386-64bit 64 Bits|@Chyiik\n||Mac OS X 10.14.6 (18G7016)|@sahrul\n||macOS 11.2.3 (20D91)|@fahr\n||macOS-10.14.6-x86_64-i386-64bit 64 Bits|@didi404\n---\n|Graphics card:|AMD Radeon Pro 460 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.23|@MaciejSobolewski\n| -- | -- | -- |\n||Intel UHD Graphics 630 1536 MB|@RonMartin\n||Intel Iris Pro OpenGL Engine Intel Inc. 4.1 INTEL-12.10.25|@aayerbe\n||AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15|@Chyiik\n||Intel Iris Plus Graphics 640|@sahrul\n||AMD FirePro [D700](D700)|@fahr\n||AMD Radeon Pro 570X|@didi404\n\nBroken: 2.91, 2.92, 2.93.0 Alpha, commit date: 2021-04-01 21:49\nWorked: 2.81, 2.90\n\nBlender crashes randomly on Mac OS\nIt can crash randomly after startup even if we do nothing like this example.\n\nIt has also been reported that it happens often when try to save the file after several minutes of work (#86565).\n\nCrash Log 1:\n```lines=25\nProcess: Blender [6485]\nPath: /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\nIdentifier: Blender\nVersion: 2.93.0 (2.93.0 2021-04-01)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [6485]\nUser ID: 501\n\nDate/Time: 2021-04-03 13:43:19.501 +0200\nOS Version: Mac OS X 10.14.6 (18G8022)\nReport Version: 12\nBridge OS Version: 3.0 (14Y906)\nAnonymous UUID: 5527B0F5-C330-CDA4-B73E-9CB133041D4E\n\nSleep/Wake UUID: DBADD923-7C0B-4D5E-AEFC-935ECD0B12BA\n\nTime Awake Since Boot: 850000 seconds\nTime Since Wake: 1600 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000e2c\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [6485]\n\nVM Regions Near 0xe2c:\n--> \n __TEXT 000000010cad1000-0000000118885000 [189.7M] r-x/r-x SM=COW /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff3cfe28b5 gleRunVertexSubmitImmediate + 6085\n1 GLEngine \t0x00007fff3cf4c29c glDrawElementsInstancedBaseVertex_GL3Exec + 681\n2 libGL.dylib \t0x00007fff3c2fcd02 glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x000000010d27bf05 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010d27b68c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x000000010d27afdf DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x000000010d2d2819 OVERLAY_wireframe_draw + 41\n7 org.blenderfoundation.blender \t0x000000010d2c2499 OVERLAY_draw_scene + 393\n8 org.blenderfoundation.blender \t0x000000010d2724fa drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x000000010d274643 drw_draw_depth_loop_impl + 1299\n10 org.blenderfoundation.blender \t0x000000010db9670f ED_view3d_depth_override + 239\n11 org.blenderfoundation.blender \t0x000000010dbbe460 ED_view3d_autodist + 48\n12 org.blenderfoundation.blender \t0x000000010db9dc9a ED_view3d_cursor3d_position + 234\n13 org.blenderfoundation.blender \t0x000000010db9dd80 ED_view3d_cursor3d_position_rotation + 144\n14 org.blenderfoundation.blender \t0x000000010db9e417 ED_view3d_cursor3d_update + 279\n15 org.blenderfoundation.blender \t0x000000010db9e7f1 view3d_cursor3d_invoke + 145\n16 org.blenderfoundation.blender \t0x000000010d152629 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x000000010d153bd8 wm_handler_operator_call + 648\n18 org.blenderfoundation.blender \t0x000000010d1531c4 wm_handlers_do_intern + 1588\n19 org.blenderfoundation.blender \t0x000000010d14ec16 wm_handlers_do + 774\n20 org.blenderfoundation.blender \t0x000000010d14e2de wm_event_do_handlers + 2862\n21 org.blenderfoundation.blender \t0x000000010d146b80 WM_main + 32\n22 org.blenderfoundation.blender \t0x000000010cc3691b main + 907\n23 libdyld.dylib \t0x00007fff5f1f93d5 start + 1\n\n(...)\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000e2c rbx: 0x0000000000000011 rcx: 0x00007fff3cfe28b5 rdx: 0x00007fff3cfe3ec8\n rdi: 0x0000000000000004 rsi: 0x0000000000c00000 rbp: 0x00007ffee312d230 rsp: 0x00007ffee312d090\n r8: 0x0000000000000211 r9: 0x00006000055d9f50 r10: 0x000000000000108c r11: 0x0000000000000001\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000108c00049800\n rip: 0x00007fff3cfe28b5 rfl: 0x0000000000010213 cr2: 0x0000000000000e2c\n \nLogical CPU: 4\nError Code: 0x00000004\nTrap Number: 14\n\n\nBinary Images:\n 0x10cad1000 - 0x118884fdf +org.blenderfoundation.blender (2.93.0 - 2.93.0 2021-04-01) <76DA024A-23A9-360A-9B4D-17E1FFF3C70F> /Applications/Blender 2.93/Blender.app/Contents/MacOS/Blender\n 0x11f240000 - 0x11f2acffb +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender 2.93/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x11f81a000 - 0x11f9affff com.apple.audio.units.Components (1.14 - 1.14) <D7C7C00C-202E-3F6B-A395-129A1A69A233> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x121431000 - 0x121435ffb com.apple.audio.AppleHDAHALPlugIn (282.54 - 282.54) <207D25F0-B094-3569-AA6D-09B4EDD72861> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bundle/Contents/MacOS/AppleHDAHALPlugIn\n 0x123231000 - 0x123234ff7 +_opcode.cpython-39-darwin.so (0) <B301C79A-62B7-387B-8FF2-1AA125557218> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_opcode.cpython-39-darwin.so\n 0x123241000 - 0x12325eff3 +libRprSupport64.dylib (0) <E10A8DBC-2DAE-3C5D-A670-E95122180BDF> /Users/USER/Library/Application Support/Blender/*/libRprSupport64.dylib\n 0x123a67000 - 0x123a6affb +_lsprof.cpython-39-darwin.so (0) <390A27D2-FE66-3D62-9D0D-EC24BDD4185E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lsprof.cpython-39-darwin.so\n 0x123c6f000 - 0x123c72047 libobjc-trampolines.dylib (756.2) <5795A048-3940-3801-90CE-33D1B1AF81F4> /usr/lib/libobjc-trampolines.dylib\n 0x124d05000 - 0x124dceff7 com.apple.AMDRadeonX4000GLDriver (2.11.23 - 2.1.1) <C9BBA305-1222-3D05-A096-DF3485CAA6D1> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver\n 0x12a338000 - 0x12a4eaffb +libRadeonProRender64.dylib (0) <7857C60D-5962-34B2-9946-AA62FB25A0FC> /Users/USER/Library/Application Support/Blender/*/libRadeonProRender64.dylib\n 0x12b156000 - 0x12b159fff +_heapq.cpython-39-darwin.so (0) <39FBF3FE-B287-3DE1-9C22-E65F7DE3FBD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_heapq.cpython-39-darwin.so\n 0x12b32f000 - 0x12b33aff3 +math.cpython-39-darwin.so (0) <B182812A-68AA-35BD-A8E8-D26E6BDB8C3F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/math.cpython-39-darwin.so\n 0x12b4cf000 - 0x12b53970f dyld (655.1.1) <EA5BF483-08FB-31C9-B31E-C0D0FD94FE89> /usr/lib/dyld\n 0x12c854000 - 0x12cb0b80f +_ssl.cpython-39-darwin.so (0) <9E0B733D-CC78-37AF-9E27-8D058929365F> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ssl.cpython-39-darwin.so\n 0x12cbdc000 - 0x12cbebff7 +_socket.cpython-39-darwin.so (0) <B1F1427E-EC5E-35BF-8595-3AB7F81B8BFA> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_socket.cpython-39-darwin.so\n 0x12cc3c000 - 0x12cc43fff +select.cpython-39-darwin.so (0) <9F931F33-6B72-314B-9365-C443F0E411CE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/select.cpython-39-darwin.so\n 0x12cc50000 - 0x12cc57fff +array.cpython-39-darwin.so (0) <C6EAB41B-E104-3EF6-923E-5279F64BB2AE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/array.cpython-39-darwin.so\n 0x12cc68000 - 0x12cc6fff7 +_struct.cpython-39-darwin.so (0) <80252227-C14A-3C4F-974E-3F540EDA92B5> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_struct.cpython-39-darwin.so\n 0x12cc80000 - 0x12cc87ff7 +binascii.cpython-39-darwin.so (0) <804000F0-C103-3525-88BB-176B163AC5A4> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/binascii.cpython-39-darwin.so\n 0x12cd14000 - 0x12cd17fff +_bisect.cpython-39-darwin.so (0) <C55FDD46-701F-3112-80AC-1514BA077D76> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bisect.cpython-39-darwin.so\n 0x12cd24000 - 0x12cd27ff3 +_random.cpython-39-darwin.so (0) <17F6835A-5316-353E-89E2-28FA2C7310B6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_random.cpython-39-darwin.so\n 0x12cd34000 - 0x12cd3bff3 +_sha512.cpython-39-darwin.so (0) <FE9A114B-3EB9-331D-9CB2-3F71DA53B2FB> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_sha512.cpython-39-darwin.so\n 0x12cd88000 - 0x12cd97ff7 +_datetime.cpython-39-darwin.so (0) <DD77ED03-5D10-32E9-A860-DEBFE5951394> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_datetime.cpython-39-darwin.so\n 0x12ce6c000 - 0x12d08b0f7 +_hashlib.cpython-39-darwin.so (0) <4EADD130-4A3F-3A9C-BFD5-5226CC3B80BC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_hashlib.cpython-39-darwin.so\n 0x12d12c000 - 0x12d133ff3 +_blake2.cpython-39-darwin.so (0) <47823C31-458F-31C3-939B-3E51CAFB21E9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_blake2.cpython-39-darwin.so\n 0x12d140000 - 0x12d143fff +_queue.cpython-39-darwin.so (0) <B6BD974A-932F-3126-8B07-332D5C1005B1> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_queue.cpython-39-darwin.so\n 0x12d150000 - 0x12d167ff3 +zlib.cpython-39-darwin.so (0) <1357BDA0-EBFF-328F-8CF8-2BAAF0777C3E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/zlib.cpython-39-darwin.so\n 0x12d2d6000 - 0x12d2edff3 +_bz2.cpython-39-darwin.so (0) <F5BE8D18-E1D6-3C23-B906-AB09DBF0FFBF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_bz2.cpython-39-darwin.so\n 0x12d2fa000 - 0x12d329ff3 +_lzma.cpython-39-darwin.so (0) <6D9DCFA1-0480-302F-8AD2-8B32FD3377EE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_lzma.cpython-39-darwin.so\n 0x12d33a000 - 0x12d33dff7 +grp.cpython-39-darwin.so (0) <DCF6B520-1F6E-3ADF-B061-CE405DC2CB4B> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/grp.cpython-39-darwin.so\n 0x12d3d9000 - 0x12d3e0fff +_json.cpython-39-darwin.so (0) <ACB3C18C-E080-3C95-8420-DAE93E2D5E99> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_json.cpython-39-darwin.so\n 0x12d43f000 - 0x12d442ffb +_scproxy.cpython-39-darwin.so (0) <50CE8674-D618-32A2-9E79-A89350AE9BA9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_scproxy.cpython-39-darwin.so\n 0x12d48f000 - 0x12d59aff7 +unicodedata.cpython-39-darwin.so (0) <B1C10C25-AADB-3554-8EA4-2D8EDBA913C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/unicodedata.cpython-39-darwin.so\n 0x12d6cd000 - 0x12d710ff7 +_decimal.cpython-39-darwin.so (0) <DB2C2DBC-0CAC-396C-9DC6-F473D0ED9DD6> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_decimal.cpython-39-darwin.so\n 0x12d731000 - 0x12d734ffb +_statistics.cpython-39-darwin.so (0) <1FC5B98C-DFF6-34A6-B0BB-817D49440624> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_statistics.cpython-39-darwin.so\n 0x12d881000 - 0x12d884ff3 +_posixsubprocess.cpython-39-darwin.so (0) <A047F4C3-E223-3AAB-9298-1E5E46906ADD> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_posixsubprocess.cpython-39-darwin.so\n 0x12db66000 - 0x12dedbfe7 +_multiarray_umath.cpython-39-darwin.so (0) <495E23F2-DD86-34BE-85F2-D8B8FA1CFDFE> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_umath.cpython-39-darwin.so\n 0x12e003000 - 0x131baab4f +libopenblas.0.dylib (0) <03CB01A7-1E7B-3A87-B36F-CD619D546D98> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libopenblas.0.dylib\n 0x131e47000 - 0x131f5eff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgfortran.3.dylib\n 0x131fcd000 - 0x132003fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libquadmath.0.dylib\n 0x132017000 - 0x13202cff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/.dylibs/libgcc_s.1.dylib\n 0x14a03c000 - 0x14a053ffb +_pickle.cpython-39-darwin.so (0) <3559C80E-CFDA-3F33-B6ED-B469333FB0C9> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_pickle.cpython-39-darwin.so\n 0x14a0b2000 - 0x14a0bfff7 +_multiarray_tests.cpython-39-darwin.so (0) <AE0DCAB5-64AB-3F7D-B12A-60B9B9E919FF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/core/_multiarray_tests.cpython-39-darwin.so\n 0x14a116000 - 0x14a131f4f +_ctypes.cpython-39-darwin.so (0) <61595129-0907-3B76-BAD5-E83E12232E92> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_ctypes.cpython-39-darwin.so\n 0x14a1ce000 - 0x14a1cfffb +lapack_lite.cpython-39-darwin.so (0) <ED8E8882-7728-3AFC-B16E-AD65D26C95CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/lapack_lite.cpython-39-darwin.so\n 0x14a1d7000 - 0x14a1f0ffb +_umath_linalg.cpython-39-darwin.so (0) <C031BBC1-676E-3561-971A-817DB290B4CC> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/linalg/_umath_linalg.cpython-39-darwin.so\n 0x14a2c4000 - 0x14a2d5fff +_pocketfft_internal.cpython-39-darwin.so (0) <F874775F-892F-3E6D-AB44-13585A46F440> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/fft/_pocketfft_internal.cpython-39-darwin.so\n 0x14a31e000 - 0x14a38ffff +mtrand.cpython-39-darwin.so (0) <26C3326C-CD5C-3EB6-ADC1-1501DEFF4824> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/mtrand.cpython-39-darwin.so\n 0x14a3ea000 - 0x14a408ffb +bit_generator.cpython-39-darwin.so (0) <0AA58188-F7BE-3259-B73D-F73A44D18892> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/bit_generator.cpython-39-darwin.so\n 0x14a429000 - 0x14a45eff3 +_common.cpython-39-darwin.so (0) <A5274DC2-1EDF-3596-810F-949AFC3280AF> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_common.cpython-39-darwin.so\n 0x14a47b000 - 0x14a4d1ffb +_bounded_integers.cpython-39-darwin.so (0) <C5EA861D-2A70-3753-B812-574045E67644> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_bounded_integers.cpython-39-darwin.so\n 0x14a4f8000 - 0x14a506ffb +_mt19937.cpython-39-darwin.so (0) <317BAC67-09BA-3FCD-951A-1F8665EB2AB2> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_mt19937.cpython-39-darwin.so\n 0x14a517000 - 0x14a523ff3 +_philox.cpython-39-darwin.so (0) <E0D66351-2EA3-3CAC-92B8-9BDD75A35465> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_philox.cpython-39-darwin.so\n 0x14a533000 - 0x14a53dff7 +_pcg64.cpython-39-darwin.so (0) <97A10DFD-6916-3251-84B1-FCCF8D908E08> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_pcg64.cpython-39-darwin.so\n 0x14a54c000 - 0x14a553fff +_sfc64.cpython-39-darwin.so (0) <4A390EEB-7105-3235-85B2-4C8D98B3587C> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_sfc64.cpython-39-darwin.so\n 0x14a560000 - 0x14a5e6ffb +_generator.cpython-39-darwin.so (0) <D25A4A84-E711-357E-9925-2B76BD03BAB0> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/site-packages/numpy/random/_generator.cpython-39-darwin.so\n 0x152b16000 - 0x152b9aff7 +core.so (0) <90E3783C-EA48-3E8D-98E7-E2465548F8C7> /Users/USER/*/core.so\n 0x152e28000 - 0x152e2fff7 +_csv.cpython-39-darwin.so (0) <A88064E5-CC97-3CD9-9422-3148889BB740> /Applications/Blender 2.93/Blender.app/Contents/Resources/2.93/python/lib/python3.9/lib-dynload/_csv.cpython-39-darwin.so\n 0x7fff27936000 - 0x7fff27c8ffff com.apple.RawCamera.bundle (8.15.0 - 1031.4.4) <AB6E8A8F-0BFE-37EE-A135-44ABA4FCB559> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff27c92000 - 0x7fff27d9efff com.apple.AMDMTLBronzeDriver (2.11.23 - 2.1.1) <69902D3A-0267-3D14-9820-D65016305FCC> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver\n 0x7fff27d9f000 - 0x7fff28744ff3 ATIRadeonX4000SCLib.dylib (2.11.23) <CC649A6F-573C-30F6-AC1B-8F0850D85B87> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib\n 0x7fff2caac000 - 0x7fff2d880ff7 com.apple.driver.AppleIntelSKLGraphicsGLDriver (12.10.25 - 12.1.0) <9AE3588C-F533-3A5D-9E4B-602ACEA5493C> /System/Library/Extensions/AppleIntelSKLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsGLDriver\n 0x7fff2d881000 - 0x7fff2dbb2ff7 com.apple.driver.AppleIntelSKLGraphicsMTLDriver (12.10.25 - 12.1.0) <8889F99C-A463-3299-8DE8-ED06FF6A6735> /System/Library/Extensions/AppleIntelSKLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelSKLGraphicsMTLDriver\n 0x7fff2f5b8000 - 0x7fff2f5b8fff com.apple.Accelerate (1.11 - Accelerate 1.11) <762942CB-CFC9-3A0C-9645-A56523A06426> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff2f5b9000 - 0x7fff2f5cfff7 libCGInterfaces.dylib (506.22) <1B6C92D9-F4B8-37BA-9635-94C4A56098CE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff2f5d0000 - 0x7fff2fc69fef com.apple.vImage (8.1 - ???) <53FA3611-894E-3158-A654-FBD2F70998FE> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff2fc6a000 - 0x7fff2fee3ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff2fee4000 - 0x7fff2ff56ffb libBNNS.dylib (38.250.1) <538D12A2-9B9D-3E22-9896-F90F6E69C06E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff2ff57000 - 0x7fff30300ff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff30301000 - 0x7fff30316feb libLinearAlgebra.dylib (1243.200.4) <CB671EE6-DEA1-391C-9B2B-AA09A46B4D7A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff30317000 - 0x7fff3031cff3 libQuadrature.dylib (3.200.2) <1BAE7E22-2862-379F-B334-A3756067730F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff3031d000 - 0x7fff30399ff3 libSparse.dylib (79.200.5) <E78B33D3-672A-3C53-B512-D3DDB2E9AC8D> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff3039a000 - 0x7fff303adfe3 libSparseBLAS.dylib (1243.200.4) <E9243341-DB77-37C1-97C5-3DFA00DD70FA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff303ae000 - 0x7fff30595ff7 libvDSP.dylib (671.250.4) <7B110627-A9C1-3FB7-A077-0C7741BA25D8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff30596000 - 0x7fff30649ff7 libvMisc.dylib (671.250.4) <D5BA4812-BFFC-3CD0-B382-905CD8555DA6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff3064a000 - 0x7fff3064afff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <74288115-EF61-30B6-843F-0593B31D4929> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff307ec000 - 0x7fff315a1ffb com.apple.AppKit (6.9 - 1671.60.109) <F3BB6BCD-F2DF-36E7-8F20-FEC419671841> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff315f3000 - 0x7fff315f3fff com.apple.ApplicationServices (50.1 - 50.1) <7BDB78C7-9021-3B29-823A-1FFDB9F79602> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff315f4000 - 0x7fff3165ffff com.apple.ApplicationServices.ATS (377 - 453.11.2.2) <A258DA73-114B-3102-A056-4AAAD3CEB9DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff316f8000 - 0x7fff3180fff7 libFontParser.dylib (228.6.2.10) <B0B7AF1F-2342-3A95-A7E6-629FC032D4B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib\n 0x7fff31810000 - 0x7fff31852fff libFontRegistry.dylib (228.12.2.4) <6DDE44EC-FF6B-3893-9209-45E0955ABDD5> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff318ac000 - 0x7fff318defff libTrueTypeScaler.dylib (228.6.2.10) <5FE48A9A-8329-3B0D-9A99-DEAC708F8334> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib\n 0x7fff31943000 - 0x7fff31947ff3 com.apple.ColorSyncLegacy (4.13.0 - 1) <E8E9342C-47EB-359D-A373-554AC19B174A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff319e2000 - 0x7fff31a34ff7 com.apple.HIServices (1.22 - 628) <2BE461FF-80B9-30D3-A574-AED5724B1C1B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff31a35000 - 0x7fff31a44fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <F5617A2A-FEA6-3832-B5BA-C2111B98786F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff31a45000 - 0x7fff31a8eff7 com.apple.print.framework.PrintCore (14.7 - 503.8) <E1D0FCBC-155E-372E-A90F-4A20B94FC114> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff31a8f000 - 0x7fff31ac8ff7 com.apple.QD (3.12 - 407.2) <28C7D39F-59C9-3314-BECC-67045487229C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff31ac9000 - 0x7fff31ad5fff com.apple.speech.synthesis.framework (8.1.3 - 8.1.3) <5E7B9BD4-122B-3012-A044-3259C97E7509> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff31ad6000 - 0x7fff31d4dfff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <32487CB2-246B-3B80-8F60-D65DFC367DDC> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff31d4f000 - 0x7fff31d4ffff com.apple.audio.units.AudioUnit (1.14 - 1.14) <B489CFDA-DEF3-38F5-A815-23EC30B8DA03> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff320a8000 - 0x7fff3244afff com.apple.CFNetwork (978.5 - 978.5) <06BB192E-0302-3AE9-B229-A9B15AD4CBF4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff3245f000 - 0x7fff3245ffff com.apple.Carbon (158 - 158) <B955D7C0-ACA6-33EB-9527-1598288532A6> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff32460000 - 0x7fff32463ffb com.apple.CommonPanels (1.2.6 - 98) <1CD6D56D-8EC7-3528-8CBC-FC69533519B5> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff32464000 - 0x7fff3275bfff com.apple.HIToolbox (2.1.1 - 918.7) <88D7F19C-8C9D-384B-BAB5-8205CA282F2C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff3275c000 - 0x7fff3275fff3 com.apple.help (1.3.8 - 66) <A08517EB-8958-36C9-AEE0-1A8FEEACBE3F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32760000 - 0x7fff32765ff7 com.apple.ImageCapture (9.0 - 1534.2) <DB063E87-ED8F-3E4E-A7E2-A6B45FA73EF7> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff32766000 - 0x7fff327fbff3 com.apple.ink.framework (10.9 - 225) <7C7E9483-2E91-3DD3-B1E0-C238F42CA0DD> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff327fc000 - 0x7fff32814ff7 com.apple.openscripting (1.7 - 179.1) <9B8C1ECC-5864-3E21-9149-863E884EA25C> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff32834000 - 0x7fff32835ff7 com.apple.print.framework.Print (14.2 - 267.4) <A7A9D2A0-D4E0-35EF-A0F7-50521F707C33> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff32836000 - 0x7fff32838ff7 com.apple.securityhi (9.0 - 55006) <05717F77-7A7B-37E6-AB3E-03F063E9095B> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff32839000 - 0x7fff3283fff7 com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <3CC050FB-EBCB-3087-8EA5-F378C8F99217> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff32961000 - 0x7fff32961fff com.apple.Cocoa (6.11 - 23) <987A526D-6FD8-345E-9265-4D8067B337D1> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff3296f000 - 0x7fff32abeff7 com.apple.ColorSync (4.13.0 - 3345.6) <356BA478-76DE-3087-86BE-5E884276AB83> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff32c4a000 - 0x7fff32cd0fff com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <E6E4A58D-9BAE-30B1-856E-E1332B98E9ED> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff32d34000 - 0x7fff32d5effb com.apple.CoreBluetooth (1.0 - 1) <4F2DDEF0-1F92-384B-8CDA-4958725D0A8E> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff32d5f000 - 0x7fff330e4fef com.apple.CoreData (120 - 866.6) <132CB39B-8D58-30FA-B8AD-49BFFF34B293> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff330e5000 - 0x7fff331d5ff7 com.apple.CoreDisplay (101.3 - 110.18) <6DD41271-E145-3E99-9D49-7CC8AC1C65B6> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff331d6000 - 0x7fff3361bfff com.apple.CoreFoundation (6.9 - 1575.401) <4D6EA727-F7B9-398A-9B0B-4A30802E49BD> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff3361d000 - 0x7fff33cadfe7 com.apple.CoreGraphics (2.0 - 1265.11) <71E7056D-6AA5-324A-A5B8-9CD35772D87B> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff33caf000 - 0x7fff33fcffff com.apple.CoreImage (14.4.0 - 750.0.140) <11026E39-D2FF-3CF6-8ACE-7BA293F9853E> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff342cc000 - 0x7fff343d0fff com.apple.CoreMedia (1.0 - 2290.14) <2C7A5348-7F19-3E28-97E4-6065A64B1DC9> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff3442d000 - 0x7fff3442dfff com.apple.CoreServices (946 - 946) <8423F2AB-74CB-3BBD-A66E-ED93DE2363C2> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3442e000 - 0x7fff344aaff7 com.apple.AE (773 - 773) <55AE7C9E-27C3-30E9-A047-3B92A6FD53B4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff344ab000 - 0x7fff34782fff com.apple.CoreServices.CarbonCore (1178.33 - 1178.33) <CB87F0C7-2CD6-3983-8E32-B6A2EC925352> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff34783000 - 0x7fff347cbff7 com.apple.DictionaryServices (1.2 - 284.16.4) <746EB200-DC51-30AE-9CBC-608A7B4CC8DA> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff347cc000 - 0x7fff347d4ffb com.apple.CoreServices.FSEvents (1239.200.13 - 1239.200.13) <5913F08D-4AA2-3200-B998-012E6A19A66D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff347d5000 - 0x7fff34986ff7 com.apple.LaunchServices (946 - 946) <A0C91634-9410-38E8-BC11-7A5A369E6BA5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff34987000 - 0x7fff34a25ff7 com.apple.Metadata (10.7.0 - 1191.58) <89DA10B4-5695-3FD9-A920-C34C33957868> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff34a26000 - 0x7fff34a70ff7 com.apple.CoreServices.OSServices (946 - 946) <20C4EEF8-D5AC-39A0-9B4A-78F88E3EFBCC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff34a71000 - 0x7fff34ad8ff7 com.apple.SearchKit (1.4.0 - 1.4.0) <DA08AA6F-A6F1-36C0-87F4-E26294E51A3A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff34ad9000 - 0x7fff34afaff3 com.apple.coreservices.SharedFileList (71.28 - 71.28) <487A8464-729E-305A-B5D1-E3FE8EB9CFC5> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff34e05000 - 0x7fff34f67ff7 com.apple.CoreText (352.0 - 584.26.3.6) <47B18B6F-C53C-357A-8EBA-A2CD340018E6> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff34f68000 - 0x7fff34fa8ff3 com.apple.CoreVideo (1.8 - 281.4) <10CF8E52-07E3-382B-8091-2CEEEFFA69B4> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff34fa9000 - 0x7fff35038fff com.apple.framework.CoreWLAN (13.0 - 1375.2) <A476486C-B863-3941-BAE6-A78BDFED4A3B> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff3528f000 - 0x7fff35294ffb com.apple.DiskArbitration (2.7 - 2.7) <A31C207C-8255-3E93-9DD7-D80C4B179050> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff35458000 - 0x7fff3545aff3 com.apple.ForceFeedback (1.0.6 - 1.0.6) <205B0C3E-4E8D-3347-A993-469F06ABBFF9> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff3545b000 - 0x7fff35808ffb com.apple.Foundation (6.9 - 1575.401) <546CCD67-0069-369A-8E6A-37FB5DD64AA1> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff35877000 - 0x7fff358a6ffb com.apple.GSS (4.0 - 2.0) <E2B90D08-3857-3155-9FCC-07D778988EC9> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff359a6000 - 0x7fff35ab0fff com.apple.Bluetooth (6.0.14 - 6.0.14d12) <0904E4FC-DE05-3B78-BD49-832A5AC2967D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff35b13000 - 0x7fff35ba2fff com.apple.framework.IOKit (2.0.2 - 1483.260.5) <6D560570-9AEB-3046-96B7-12AC1D145C3D> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff35ba4000 - 0x7fff35bb3ffb com.apple.IOSurface (255.6.1 - 255.6.1) <85F85EBB-EA59-3A8B-B3EB-7C20F3CC77AE> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff35c07000 - 0x7fff35d94fe7 com.apple.ImageIO.framework (3.3.0 - 1850.2.11) <5F5F7C36-2A20-3CFE-ACAC-53633B0F2F0A> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff35d95000 - 0x7fff35d99ffb libGIF.dylib (1850.2.12) <060E927C-DFA7-33A7-98E3-F9699D734A8E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff35d9a000 - 0x7fff35e76ff7 libJP2.dylib (1850.2.12) <CEC4FF68-7522-3430-B03D-37648FEB450E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff35e77000 - 0x7fff35e9cfeb libJPEG.dylib (1850.2.12) <F7A6A6EC-24B6-3C45-813F-B2FFA3980B49> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff36172000 - 0x7fff36198feb libPng.dylib (1850.2.12) <B816B90B-2454-31D8-AD34-1489B6350C70> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff36199000 - 0x7fff3619bffb libRadiance.dylib (1850.2.12) <1A67ED5D-00BC-301D-8515-CEDFFE994F2B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff3619c000 - 0x7fff361e9ff3 libTIFF.dylib (1850.2.12) <3FB9D8DC-1D7B-324C-ADE6-DDC794FD2B43> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff3735c000 - 0x7fff37375fff com.apple.Kerberos (3.0 - 1) <DB1E0679-37E1-3B93-9789-32F63D660C3B> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff3762f000 - 0x7fff37639fff com.apple.MediaAccessibility (1.0 - 114.4) <76C449C5-DB45-3D7F-BFAD-3DACEF15DA21> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff376e9000 - 0x7fff37d8ffff com.apple.MediaToolbox (1.0 - 2290.14) <927F9E24-32DB-33F9-9866-4DD8092A51F4> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff37d91000 - 0x7fff37e39ff7 com.apple.Metal (162.2 - 162.2) <B65C71BF-D40E-3BB3-940C-117DDD203551> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff37e55000 - 0x7fff37e74ff7 com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <44CE8362-E972-3697-AD6F-15BC863BAEB8> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff37e75000 - 0x7fff37ef1fe7 com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <EE8440DA-66DF-3923-ABBC-E0543211C069> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff37ef2000 - 0x7fff37f19fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <E64450DF-2B96-331E-B7F4-666E00571C70> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff37f1a000 - 0x7fff38045ff7 com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <F2CF26B6-73F1-3644-8FE9-CDB9B2C4501F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff38046000 - 0x7fff38060fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <B33A35C3-0393-366B-ACFB-F4BB6A5F7B4A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff38061000 - 0x7fff38062ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <69F14BCF-C5C5-3BF8-9C31-8F87D2D6130A> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff38e66000 - 0x7fff38e72ff7 com.apple.NetFS (6.0 - 4.0) <1C8237D6-731D-3E32-8BD5-B92A33D08A30> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS\n 0x7fff391d5000 - 0x7fff391f8ff7 com.apple.audio.OpenAL (1.8 - 1.8) <2EE5236C-775B-36B1-97A8-DEE5FB80F5B5> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff3b907000 - 0x7fff3b90ffe3 libcldcpuengine.dylib (2.11) <AAE49359-EB53-3FD4-ADBF-C60498BD0B34> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib\n 0x7fff3b910000 - 0x7fff3b967ff7 com.apple.opencl (2.15.3 - 2.15.3) <2F6B796C-901C-33AF-8B12-F3522DA05218> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff3b968000 - 0x7fff3b983ff7 com.apple.CFOpenDirectory (10.14 - 207.200.4) <F03D84EB-49B2-3A00-9127-B9A269824026> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff3b984000 - 0x7fff3b98fffb com.apple.OpenDirectory (10.14 - 207.200.4) <A8020CEE-5B78-3581-A735-EA2833683F31> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff3c2df000 - 0x7fff3c2e1fff libCVMSPluginSupport.dylib (17.7.3) <700B3323-3404-3848-91D2-99EFC7E2634A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff3c2e2000 - 0x7fff3c2e7ff3 libCoreFSCache.dylib (166.5) <5BC99EE7-7FFD-3F30-9AEE-EEDC25067AC4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff3c2e8000 - 0x7fff3c2ecfff libCoreVMClient.dylib (166.5) <B8FA5858-8185-3992-AD3B-A81AF08C3CDD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff3c2ed000 - 0x7fff3c2f5ff7 libGFXShared.dylib (17.7.3) <26BA051E-1113-3022-A46A-1F69E7CFA787> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff3c2f6000 - 0x7fff3c301fff libGL.dylib (17.7.3) <16C56C55-327F-395F-810C-C360F7DE9063> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff3c302000 - 0x7fff3c33cfef libGLImage.dylib (17.7.3) <F68F1268-5AD1-3D2E-A255-0BD442A24F4D> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff3c33d000 - 0x7fff3c4afff7 libGLProgrammability.dylib (17.7.3) <92DDEDA1-5E95-36A9-9D2E-A725541B2F93> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff3c4b0000 - 0x7fff3c4eefff libGLU.dylib (17.7.3) <D83871DF-B7DD-3DFD-8D5C-0BA359AC1BF2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff3ce8b000 - 0x7fff3ce9affb com.apple.opengl (17.7.3 - 17.7.3) <62E4CB29-51CA-387E-90BF-F58213D56D62> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff3ce9b000 - 0x7fff3d032ff7 GLEngine (17.7.3) <8C9F33DD-7C81-3D45-80F7-A7D6A877993A> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff3d033000 - 0x7fff3d05cff3 GLRendererFloat (17.7.3) <2B5F700E-9E9B-3543-BC35-949279CB24FF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff3dca4000 - 0x7fff3defbff7 com.apple.QuartzCore (1.11 - 701.14) <B37B1291-4977-34D2-B3F0-509FB3DB5090> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff3e733000 - 0x7fff3ea33ff7 com.apple.security (7.0 - 58286.270.10) <990FF42E-0726-318F-94ED-A8FDF7F41402> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff3ea34000 - 0x7fff3eac0fff com.apple.securityfoundation (6.0 - 55185.260.1) <964F1F81-D8F1-3952-8137-EF21CDD3A7A6> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff3eaf2000 - 0x7fff3eaf6fff com.apple.xpc.ServiceManagement (1.0 - 1) <5055F807-1DD4-3F97-A2A6-4537F51A5736> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff3ee8f000 - 0x7fff3eefcfff com.apple.SystemConfiguration (1.17 - 1.17) <30C8327F-3EFF-3520-9C50-016F8B6B954F> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff3f15b000 - 0x7fff3f4bcfff com.apple.VideoToolbox (1.0 - 2290.14) <30C690CF-8935-39E8-B343-ADB009C84FC5> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff42138000 - 0x7fff421ddfff com.apple.APFS (1.0 - 1) <06284DE8-5883-39F8-B04D-0D5EA74D12ED> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff42bf2000 - 0x7fff42bf3ff7 com.apple.AggregateDictionary (1.0 - 1) <A6AF8AC4-1F25-37C4-9157-A02E9C200926> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff431f6000 - 0x7fff43222ff7 com.apple.framework.Apple80211 (13.0 - 1380.2) <E4D12303-8B12-303C-91E2-3B40F60832BA> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff4334a000 - 0x7fff43359fc7 com.apple.AppleFSCompression (96.200.3 - 1.0) <3CF60CE8-976E-3CB8-959D-DD0948C1C2DE> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff43455000 - 0x7fff43460fff com.apple.AppleIDAuthSupport (1.0 - 1) <2E9D1398-DBE6-328B-ADDA-20FA5FAD7405> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff434a1000 - 0x7fff434eaff3 com.apple.AppleJPEG (1.0 - 1) <4C1F426B-7D77-3980-9633-7DBD8C666B9A> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff4373e000 - 0x7fff43760fff com.apple.applesauce (1.0 - ???) <F49107C7-3C51-3024-8EF1-C57643BE4F3B> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff43824000 - 0x7fff43874ff7 com.apple.AppleVAFramework (5.1.4 - 5.1.4) <FB127E63-853B-3F00-BE2A-12B4BF6FED33> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff438bf000 - 0x7fff438d3ffb com.apple.AssertionServices (1.0 - 1) <456E507A-4561-3628-9FBE-173ACE7429D8> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff43ca2000 - 0x7fff43d8eff7 com.apple.AuthKit (1.0 - 1) <2765ABE9-54F2-3E45-8A93-1261E251B90D> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff43f50000 - 0x7fff43f58fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 57.1) <2A396FC0-7B79-3088-9A82-FB93C1181A57> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff43f59000 - 0x7fff43feefff com.apple.backup.framework (1.10.7 - ???) <5243C2BC-0159-3DBB-9FAB-22EA01E58052> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup\n 0x7fff43fef000 - 0x7fff4405cff3 com.apple.BaseBoard (360.28 - 360.28) <68FA8044-F3CD-3BC6-9DAB-27DACF52BFC0> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff44ebc000 - 0x7fff44f0bff7 com.apple.ChunkingLibrary (201 - 201) <DFE16C42-24E6-386F-AC50-0058F61980A2> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff45cc9000 - 0x7fff45cd2ffb com.apple.CommonAuth (4.0 - 2.0) <93335CB6-ABEB-3EC7-A040-8A667F40D5F3> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff4616b000 - 0x7fff4654efef com.apple.CoreAUC (274.0.0 - 274.0.0) <C71F1581-E73B-3DA0-958B-E912C3FB3F23> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff4654f000 - 0x7fff4657dff7 com.apple.CoreAVCHD (6.0.0 - 6000.4.1) <A04A99B8-DAC5-36FC-BAC7-7431600C1F89> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff469ab000 - 0x7fff469bcff7 com.apple.CoreEmoji (1.0 - 69.19.9) <228457B3-E191-356E-9A5B-3C0438D05FBA> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff46f66000 - 0x7fff46fccff7 com.apple.CoreNLP (1.0 - 130.15.22) <27877820-17D0-3B02-8557-4014E876CCC7> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff47279000 - 0x7fff47281ff7 com.apple.CorePhoneNumbers (1.0 - 1) <11F97C7E-C183-305F-8E6C-9B374F50E26B> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff473fd000 - 0x7fff4742eff3 com.apple.CoreServicesInternal (358 - 358) <DD6EF60D-048F-3186-83DA-EB191EDF48AE> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff477f5000 - 0x7fff47879fff com.apple.CoreSymbolication (10.2 - 64490.25.1) <28B2FF2D-3FDE-3A20-B343-341E5BD4E22F> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff47909000 - 0x7fff47a34ff7 com.apple.coreui (2.1 - 499.10) <A80F4B09-F940-346F-A9DF-4EFADD9220A8> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff47a35000 - 0x7fff47bd5fff com.apple.CoreUtils (5.9 - 590.16) <BF9A990D-24C0-3633-A753-F19F4DFCA663> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff47c29000 - 0x7fff47c8cff7 com.apple.framework.CoreWiFi (13.0 - 1375.2) <7E9CC352-BB06-3C97-A51F-6A35F09EBA16> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff47c8d000 - 0x7fff47c9eff3 com.apple.CrashReporterSupport (10.13 - 938.29) <8A66F5D5-87D1-31C9-BEAE-86E0735F4E92> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff47d2e000 - 0x7fff47d3dfff com.apple.framework.DFRFoundation (1.0 - 211.1) <E3F02F2A-2059-39CC-85DA-969676EB88EB> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff47d3e000 - 0x7fff47d42ff7 com.apple.DSExternalDisplay (3.1 - 380) <787B9748-B120-3453-B8FE-61D9E363A9E0> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff47dc3000 - 0x7fff47e38ffb com.apple.datadetectorscore (7.0 - 590.27) <06FB1A07-7AE6-3ADD-8E7E-41955FAB38E8> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff47e84000 - 0x7fff47ec1ff7 com.apple.DebugSymbols (190 - 190) <6F4FAACA-E06B-38AD-A0C2-14EA5408A231> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff47ec2000 - 0x7fff47ffdff7 com.apple.desktopservices (1.13.6 - ???) <7536F3F3-90F1-3D1C-9249-91B809FE5328> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff48f44000 - 0x7fff4935ffff com.apple.vision.FaceCore (3.3.4 - 3.3.4) <A576E2DA-BF6F-3B18-8FEB-324E5C5FA9BD> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff4cc13000 - 0x7fff4cc14fff libmetal_timestamp.dylib (902.3.2) <05389463-AF2E-33E2-A14F-1416E4A30835> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3902/Libraries/libmetal_timestamp.dylib\n 0x7fff4e2a8000 - 0x7fff4e2b3ff7 libGPUSupportMercury.dylib (17.7.3) <121E8765-3C03-32AB-903E-6B1DD9A4FD4A> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff4e2b4000 - 0x7fff4e2b9fff com.apple.GPUWrangler (3.50.16 - 3.50.16) <1156CF8C-729B-3173-B3CC-00BB17156BCC> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff4e647000 - 0x7fff4e66bff3 com.apple.GenerationalStorage (2.0 - 285.101) <84C2E52C-F2C6-3FF8-87E5-3C88A40D3881> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff4f0c5000 - 0x7fff4f0d4fff com.apple.GraphVisualizer (1.0 - 5) <48D020B7-5938-3FAE-B468-E291AEE2C06F> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff4f23a000 - 0x7fff4f2aeffb com.apple.Heimdal (4.0 - 2.0) <D97FCF19-EAD6-3E2F-BE88-F817E45CAE96> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff505af000 - 0x7fff505b8fff com.apple.IOAccelMemoryInfo (1.0 - 1) <32F6778F-3EB5-36A3-8AF8-55B37A44AC0C> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff505b9000 - 0x7fff505c0ffb com.apple.IOAccelerator (404.15 - 404.15) <06D2C96E-1CF5-3199-A234-9033934D78BF> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff505c4000 - 0x7fff505dcfff com.apple.IOPresentment (1.0 - 42.6) <D2BA3A78-21C6-37B8-9F8F-9EC0F30F953F> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff50984000 - 0x7fff509b1ff7 com.apple.IconServices (379 - 379) <7BAD562D-4FA3-3E11-863C-1EEBE2406D2C> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff50c44000 - 0x7fff50c56ff3 com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <D5DDE47A-E922-3166-BD7F-E7C3DF360DD9> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff50c71000 - 0x7fff50d4cff7 com.apple.LanguageModeling (1.0 - 159.15.15) <3DE3CE61-542B-37B7-883E-4B9717CAC65F> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff50d4d000 - 0x7fff50d89ff7 com.apple.Lexicon-framework (1.0 - 33.15.10) <4B5E843E-2809-3E70-9560-9254E2656419> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff50d90000 - 0x7fff50d95fff com.apple.LinguisticData (1.0 - 238.25) <F529B961-098C-3E4C-A3E9-9DA9BFA1B3F0> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff515b4000 - 0x7fff515b7fff com.apple.Mangrove (1.0 - 25) <537A5B2E-4C30-3CFD-8BDC-79F9A04AC327> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff51a8b000 - 0x7fff51ab3ff7 com.apple.spotlight.metadata.utilities (1.0 - 1191.58) <23E8580B-19C0-3E4F-A9FE-368DA80EAA6F> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff51ab4000 - 0x7fff51b41ff7 com.apple.gpusw.MetalTools (1.0 - 1) <9B542958-6363-3041-A265-EC7AC7BD7A43> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff51b58000 - 0x7fff51b71ffb com.apple.MobileAssets (1.0 - 437.250.3) <8BE5B3A0-8F3A-3FAE-9AFF-32836300183C> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff51d3d000 - 0x7fff51d58ffb com.apple.MobileKeyBag (2.0 - 1.0) <39337CBB-1D39-3DDC-A998-591194C76523> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff51de1000 - 0x7fff51e0bffb com.apple.MultitouchSupport.framework (2450.1 - 2450.1) <42A23EC9-64A7-31C7-BF33-DF4412ED8A3F> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff52047000 - 0x7fff52051fff com.apple.NetAuth (6.2 - 6.2) <0D01BBE5-0269-310D-B148-D19DAE143DEB> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff528b3000 - 0x7fff52904ff3 com.apple.OTSVG (1.0 - ???) <CB2F1DBE-0313-30CB-A95F-2FE75E0A089E> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff53a9d000 - 0x7fff53aacff7 com.apple.PerformanceAnalysis (1.218.2 - 218.2) <65F3DB3E-6D4E-33A0-B510-EF768D323DAB> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff5593e000 - 0x7fff5595cff7 com.apple.ProtocolBuffer (1 - 263.2) <907D6C95-D050-31DE-99CA-16A5135BC6F9> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff55af4000 - 0x7fff55b44fff com.apple.ROCKit (27.6 - 27.6) <756C2253-E8B1-3C48-9945-DE8D6AD24DE2> /System/Library/PrivateFrameworks/ROCKit.framework/Versions/A/ROCKit\n 0x7fff55ca2000 - 0x7fff55cc4fff com.apple.RemoteViewServices (2.0 - 128) <8FB0E4EB-DCBB-32E6-94C6-AA9BA9EE4CAC> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff574ce000 - 0x7fff575ecfff com.apple.Sharing (1288.62.5 - 1288.62.5) <BB647030-839A-3271-B205-D4325346DD3B> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff58401000 - 0x7fff586b0fff com.apple.SkyLight (1.600.0 - 340.55) <1F737945-E242-3F03-A7D6-1A5955AB1298> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff58e54000 - 0x7fff58e60fff com.apple.SpeechRecognitionCore (5.0.21 - 5.0.21) <7A6A67DB-C813-328E-AAFB-D267A5B50B3D> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff594ff000 - 0x7fff5953bff3 com.apple.StreamingZip (1.0 - 1) <046FAD5C-E0C5-3013-B1FE-24C018A0DDCF> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff595b1000 - 0x7fff5963cfc7 com.apple.Symbolication (10.2 - 64490.38.1) <9FDCC98D-5B32-35AD-A9BF-94DF2B78507F> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff59b22000 - 0x7fff59b2effb com.apple.TCC (1.0 - 1) <E3691073-7284-35E4-94F3-16587A7F380F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff59d94000 - 0x7fff59e5cff3 com.apple.TextureIO (3.8.4 - 3.8.1) <7CEAC05A-D283-3D5A-B1E3-C849285FA0BF> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff59f12000 - 0x7fff59f13fff com.apple.TrustEvaluationAgent (2.0 - 31.200.1) <15DF9C73-54E4-3C41-BCF4-378338C55FB4> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff59f19000 - 0x7fff5a0d1ffb com.apple.UIFoundation (1.0 - 551.5) <A0FDC3A4-45C6-3C87-B77F-7DC394374C08> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff5ad4d000 - 0x7fff5ae26fff com.apple.ViewBridge (406 - 406) <3CC6AE31-2CD7-30CA-982C-47EF242EFA30> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff5b5fe000 - 0x7fff5b601fff com.apple.dt.XCTTargetBootstrap (1.0 - 14490.66) <7AE3457F-AF40-3508-93FB-1D9E31EB1C9D> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff5ba02000 - 0x7fff5ba04ffb com.apple.loginsupport (1.0 - 1) <3F8D6334-BCD6-36C1-BA20-CC8503A84375> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff5ba05000 - 0x7fff5ba1afff com.apple.login (3.0 - 3.0) <E168F05D-A5DF-3848-8686-DF5015EA4BA4> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff5bcce000 - 0x7fff5bd02fff libCRFSuite.dylib (41.15.4) <406DAC06-0C77-3F90-878B-4D38F11F0256> /usr/lib/libCRFSuite.dylib\n 0x7fff5bd05000 - 0x7fff5bd0fff7 libChineseTokenizer.dylib (28.15.3) <9B7F6109-3A5D-3641-9A7E-31D2239D73EE> /usr/lib/libChineseTokenizer.dylib\n 0x7fff5bd9d000 - 0x7fff5bd9effb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff5bdd5000 - 0x7fff5c02cff3 libFosl_dynamic.dylib (18.3.4) <1B5DD4E2-8AE0-315E-829E-D5BFCD264EA8> /usr/lib/libFosl_dynamic.dylib\n 0x7fff5c07d000 - 0x7fff5c09cfff libMobileGestalt.dylib (645.270.1) <99A06C8A-97D6-383D-862C-F453BABB48A4> /usr/lib/libMobileGestalt.dylib\n 0x7fff5c09d000 - 0x7fff5c09dfff libOpenScriptingUtil.dylib (179.1) <4D603146-EDA5-3A74-9FF8-4F75D8BB9BC6> /usr/lib/libOpenScriptingUtil.dylib\n 0x7fff5c1dd000 - 0x7fff5c1deffb libSystem.B.dylib (1252.250.1) <C7A55258-8EB2-3202-82B5-AA56E53EE2DA> /usr/lib/libSystem.B.dylib\n 0x7fff5c25a000 - 0x7fff5c25bfff libThaiTokenizer.dylib (2.15.1) <ADB37DC3-7D9B-3E73-A72A-BCC3433C937A> /usr/lib/libThaiTokenizer.dylib\n 0x7fff5c26d000 - 0x7fff5c283ffb libapple_nghttp2.dylib (1.24.1) <6F04250A-6686-3FDC-9A8D-290C64B06502> /usr/lib/libapple_nghttp2.dylib\n 0x7fff5c284000 - 0x7fff5c2adffb libarchive.2.dylib (54.250.1) <47289946-8504-3966-9127-6CE39993DC2C> /usr/lib/libarchive.2.dylib\n 0x7fff5c2ae000 - 0x7fff5c32dfff libate.dylib (1.13.8) <92B44EDB-369D-3EE8-AEC5-61F8B9313DBF> /usr/lib/libate.dylib\n 0x7fff5c331000 - 0x7fff5c331ff3 libauto.dylib (187) <3E3780E1-96F3-3A22-91C5-92F9A5805518> /usr/lib/libauto.dylib\n 0x7fff5c403000 - 0x7fff5c413ffb libbsm.0.dylib (39.200.18) <CF381E0B-025B-364F-A83D-2527E03F1AA3> /usr/lib/libbsm.0.dylib\n 0x7fff5c414000 - 0x7fff5c421fff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib\n 0x7fff5c422000 - 0x7fff5c475ff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib\n 0x7fff5c476000 - 0x7fff5c48bff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib\n 0x7fff5c48c000 - 0x7fff5c48cff3 libcharset.1.dylib (51.200.6) <2A27E064-314C-359C-93FC-8A9B06206174> /usr/lib/libcharset.1.dylib\n 0x7fff5c48d000 - 0x7fff5c49dffb libcmph.dylib (6.15.1) <9C52B2FE-179F-32AC-B87E-2AFC49ABF817> /usr/lib/libcmph.dylib\n 0x7fff5c49e000 - 0x7fff5c4b6ffb libcompression.dylib (52.250.2) <7F4BB18C-1FB4-3825-8D8B-6E6B168774C6> /usr/lib/libcompression.dylib\n 0x7fff5c72b000 - 0x7fff5c741fff libcoretls.dylib (155.220.1) <4C64BE3E-41E3-3020-8BB7-07E90C0C861C> /usr/lib/libcoretls.dylib\n 0x7fff5c742000 - 0x7fff5c743ff3 libcoretls_cfhelpers.dylib (155.220.1) <0959B3E9-6643-3589-8BB3-21D52CDF0EF1> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff5c8e1000 - 0x7fff5c9d9ff7 libcrypto.35.dylib (22.260.1) <91C3D71A-4D1D-331D-89CC-67863DF10574> /usr/lib/libcrypto.35.dylib\n 0x7fff5cbef000 - 0x7fff5cc45ff3 libcups.2.dylib (462.16) <E82021D0-36AD-3FB7-AE47-A03A6947C7D0> /usr/lib/libcups.2.dylib\n 0x7fff5cd79000 - 0x7fff5cd79fff libenergytrace.dylib (17.200.1) <80BB567A-FD18-3497-BF97-353F57D98CDD> /usr/lib/libenergytrace.dylib\n 0x7fff5cdab000 - 0x7fff5cdb0ff7 libgermantok.dylib (17.15.2) <E5F0F794-FF27-3D64-AE52-C78C6A84DD67> /usr/lib/libgermantok.dylib\n 0x7fff5cdb1000 - 0x7fff5cdb6ff7 libheimdal-asn1.dylib (520.270.1) <73F60D6F-76F8-35EF-9C86-9A81225EE4BE> /usr/lib/libheimdal-asn1.dylib\n 0x7fff5cde1000 - 0x7fff5ced1fff libiconv.2.dylib (51.200.6) <2047C9B7-3F74-3A95-810D-2ED8F0475A99> /usr/lib/libiconv.2.dylib\n 0x7fff5ced2000 - 0x7fff5d133ffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib\n 0x7fff5d180000 - 0x7fff5d181fff liblangid.dylib (128.15.1) <22D05C4F-769B-3075-ABCF-44A0EBACE028> /usr/lib/liblangid.dylib\n 0x7fff5d182000 - 0x7fff5d19aff3 liblzma.5.dylib (10.200.3) <E1F4FD60-1CE4-37B9-AD95-29D348AF1AC0> /usr/lib/liblzma.5.dylib\n 0x7fff5d1b2000 - 0x7fff5d256ff7 libmecab.1.0.0.dylib (779.24.1) <A8D0379B-85FA-3B3D-89ED-5CF2C3826AB2> /usr/lib/libmecab.1.0.0.dylib\n 0x7fff5d257000 - 0x7fff5d45bfff libmecabra.dylib (779.24.1) <D71F71E0-30E2-3DB3-B636-7DE13D51FB4B> /usr/lib/libmecabra.dylib\n 0x7fff5d633000 - 0x7fff5d984ff7 libnetwork.dylib (1229.250.15) <72C7E9E3-B2BE-3300-BE1B-64606222022C> /usr/lib/libnetwork.dylib\n 0x7fff5da16000 - 0x7fff5e19bfdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib\n 0x7fff5e1ad000 - 0x7fff5e1b1ffb libpam.2.dylib (22.200.1) <586CF87F-349C-393D-AEEB-FB75F94A5EB7> /usr/lib/libpam.2.dylib\n 0x7fff5e1b4000 - 0x7fff5e1e9fff libpcap.A.dylib (79.250.3) <97B8CE1B-3EF6-3443-95EF-5659733139C9> /usr/lib/libpcap.A.dylib\n 0x7fff5e302000 - 0x7fff5e31affb libresolv.9.dylib (65.200.3) <1FB0982D-84D9-36E0-B3D8-C808891EFF50> /usr/lib/libresolv.9.dylib\n 0x7fff5e36b000 - 0x7fff5e36cff7 libspindump.dylib (267.3) <A584E403-8C95-3841-9C16-E22664A5A63F> /usr/lib/libspindump.dylib\n 0x7fff5e36d000 - 0x7fff5e54afff libsqlite3.dylib (274.26) <6404BA3B-BCA4-301F-B2FE-8776105A2AA3> /usr/lib/libsqlite3.dylib\n 0x7fff5e763000 - 0x7fff5e766ff7 libutil.dylib (51.200.4) <CE9B18C9-66ED-32D4-9D29-01F8FCB467B0> /usr/lib/libutil.dylib\n 0x7fff5e767000 - 0x7fff5e774fff libxar.1.dylib (417.1) <39CCF46B-C81A-34B1-92A1-58C4E5DA846E> /usr/lib/libxar.1.dylib\n 0x7fff5e779000 - 0x7fff5e85cfff libxml2.2.dylib (32.19) <E07AB10E-E2E6-33F2-8550-C24A0EB8FEAC> /usr/lib/libxml2.2.dylib\n 0x7fff5e85d000 - 0x7fff5e885ff3 libxslt.1.dylib (16.7.1) <4A5CB7D5-50F8-36BF-8A80-D526C57EB5D9> /usr/lib/libxslt.1.dylib\n 0x7fff5e886000 - 0x7fff5e898ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib\n 0x7fff5f07c000 - 0x7fff5f080ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib\n 0x7fff5f081000 - 0x7fff5f08bff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff5f08c000 - 0x7fff5f093ff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff5f094000 - 0x7fff5f09dff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib\n 0x7fff5f09e000 - 0x7fff5f122fc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib\n 0x7fff5f1a9000 - 0x7fff5f1e2ff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib\n 0x7fff5f1e3000 - 0x7fff5f20fff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib\n 0x7fff5f210000 - 0x7fff5f210ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib\n 0x7fff5f211000 - 0x7fff5f21dff3 libkxld.dylib (4903.278.56) <A3FF22FA-4AD4-3FF3-9891-B34482DC8572> /usr/lib/system/libkxld.dylib\n 0x7fff5f21e000 - 0x7fff5f21eff7 liblaunch.dylib (1336.261.6) <1F0EEC6F-4D08-38E6-ACF9-6E44D328931F> /usr/lib/system/liblaunch.dylib\n 0x7fff5f21f000 - 0x7fff5f224fff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib\n 0x7fff5f225000 - 0x7fff5f227ff7 libquarantine.dylib (86.270.1) <3F36A3D6-9606-3D90-B520-809BAEF981C3> /usr/lib/system/libquarantine.dylib\n 0x7fff5f228000 - 0x7fff5f229ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib\n 0x7fff5f22a000 - 0x7fff5f241ff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib\n 0x7fff5f242000 - 0x7fff5f242ff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff5f243000 - 0x7fff5f2cafff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib\n 0x7fff5f2cb000 - 0x7fff5f2ceffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff5f2cf000 - 0x7fff5f2d2ff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff5f2d3000 - 0x7fff5f2d9fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff5f2da000 - 0x7fff5f2e0ffb libsystem_dnssd.dylib (878.270.3) <D5352ABD-0311-3327-8E64-93F29EB19BF1> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff5f2e1000 - 0x7fff5f32cffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib\n 0x7fff5f32d000 - 0x7fff5f355ff7 libsystem_kernel.dylib (4903.278.56) <5B0F1BF0-E2F4-3753-87B6-6F91C594F59E> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff5f356000 - 0x7fff5f3a1ff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib\n 0x7fff5f3a2000 - 0x7fff5f3ccfff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff5f3cd000 - 0x7fff5f3d7ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff5f3d8000 - 0x7fff5f3dffff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib\n 0x7fff5f3e0000 - 0x7fff5f3e9fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib\n 0x7fff5f3ea000 - 0x7fff5f3f4ff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff5f3f5000 - 0x7fff5f3f8ff7 libsystem_sandbox.dylib (851.270.5) <20D11F30-783F-3A56-9BD2-6CF38C049332> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff5f3f9000 - 0x7fff5f3fbff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff5f3fc000 - 0x7fff5f403ff3 libsystem_symptoms.dylib (820.267.2) <0DA60956-0403-3456-9D6A-11F2DB9E3819> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff5f404000 - 0x7fff5f419ff7 libsystem_trace.dylib (906.260.3) <5B6FAE61-EF5C-381F-B71B-9B6F6428FEE2> /usr/lib/system/libsystem_trace.dylib\n 0x7fff5f41b000 - 0x7fff5f420ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib\n 0x7fff5f421000 - 0x7fff5f450fff libxpc.dylib (1336.261.6) <522FA3AF-D3B1-3283-8EF4-8B17CB237B65> /usr/lib/system/libxpc.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 1047\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 76643460\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=750.3M resident=0K(0%) swapped_out_or_unallocated=750.3M(100%)\nWritable regions: Total=1.9G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.9G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 3 \nActivity Tracing 256K 1 \nCG backing stores 1320K 2 \nCG image 380K 11 \nCoreAnimation 328K 10 \nCoreGraphics 8K 1 \nCoreImage 32K 4 \nCoreUI image data 704K 8 \nCoreUI image file 540K 5 \nFoundation 4K 1 \nImage IO 256K 1 \nKernel Alloc Once 8K 1 \nMALLOC 868.0M 567 \nMALLOC guard page 32K 7 \nMALLOC_LARGE (reserved) 128K 1 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nMemory Tag 242 12K 1 \nMemory Tag 249 192K 2 \nOpenGL GLSL 256K 3 \nSTACK GUARD 92K 23 \nStack 36.7M 23 \nVM_ALLOCATE 524.9M 572 \nVM_ALLOCATE (reserved) 128.0M 2 reserved VM address space (unallocated)\n__DATA 120.0M 333 \n__DATA_CONST 20K 1 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 283.5M 85 \n__TEXT 467.0M 320 \n__UNICODE 564K 1 \nmapped file 79.5M 26 \nshared memory 4276K 12 \n=========== ======= ======= \nTOTAL 2.8G 2030 \nTOTAL, minus reserved VM space 2.3G 2030 \n\nModel: MacBookPro13,3, BootROM 429.80.1.0.0, 4 processors, Intel Core i7, 2,9 GHz, 16 GB, SMC 2.38f7\nGraphics: kHW_AMDRadeonPro460Item, AMD Radeon Pro 460, spdisplays_pcie_device, 4 GB\nGraphics: kHW_IntelHDGraphics530Item, Intel HD Graphics 530, spdisplays_builtin\nMemory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nMemory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x15A), Broadcom BCM43xx 1.0 (7.77.61.3 AirPortDriverBrcmNIC-1305.11)\nBluetooth: Version 6.0.14d12, 3 services, 27 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.0 Bus\nUSB Device: Wacom Wireless Receiver\nUSB Device: iBridge\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\nThunderbolt Bus: MacBook Pro, Apple Inc., 41.1\n```\n\nCrash Log 2:\n```lines=25\nProcess: Blender [4923]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 2.92.0 (2.92.0 2021-02-25)\nCode Type: X86-64 (Native)\nParent Process: ??? [1]\nResponsible: Blender [4923]\nUser ID: 501\n\nDate/Time: 2021-03-14 13:37:52.807 +0100\nOS Version: macOS 11.2.3 (20D91)\nReport Version: 12\nBridge OS Version: 5.2 (18P4347)\nAnonymous UUID: B5FE06B1-F2A1-95FF-0593-1738C46F37D4\n\nSleep/Wake UUID: CBAA4D96-6C0A-4683-B5C6-D788FF799225\n\nTime Awake Since Boot: 65000 seconds\nTime Since Wake: 5700 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 0 Dispatch queue: com.apple.main-thread\n\nException Type: EXC_BAD_ACCESS (SIGSEGV)\nException Codes: KERN_INVALID_ADDRESS at 0x0000000000000024\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: exc handler [4923]\n\nVM Regions Near 0x24:\n--> \n __TEXT 10016f000-10ab5b000 [169.9M] r-x/r-x SM=COW /Applications/Blender.app/Contents/MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 GLEngine \t0x00007fff6cc64690 gleRunVertexSubmitImmediate + 5632\n1 GLEngine \t0x00007fff6cbeb197 glDrawElementsInstancedBaseVertex_GL3Exec + 807\n2 libGL.dylib \t0x00007fff6cb323cf glDrawElementsInstancedBaseVertex + 45\n3 org.blenderfoundation.blender \t0x0000000100808ec5 draw_call_single_do + 469\n4 org.blenderfoundation.blender \t0x000000010080864c drw_draw_pass_ex + 1692\n5 org.blenderfoundation.blender \t0x0000000100807f9f DRW_draw_pass + 31\n6 org.blenderfoundation.blender \t0x0000000100832048 workbench_draw_sample + 344\n7 org.blenderfoundation.blender \t0x000000010083229c workbench_draw_scene + 76\n8 org.blenderfoundation.blender \t0x00000001007ff33a drw_engines_draw_scene + 186\n9 org.blenderfoundation.blender \t0x00000001007fde5d DRW_draw_render_loop_ex + 1565\n10 org.blenderfoundation.blender \t0x00000001007ff5db DRW_draw_render_loop_offscreen + 155\n11 org.blenderfoundation.blender \t0x000000010111d058 ED_view3d_draw_offscreen + 808\n12 org.blenderfoundation.blender \t0x000000010111d834 ED_view3d_draw_offscreen_imbuf + 692\n13 org.blenderfoundation.blender \t0x000000010111db64 ED_view3d_draw_offscreen_imbuf_simple + 628\n14 org.blenderfoundation.blender \t0x00000001006e6876 wm_save_as_mainfile_exec + 1974\n15 org.blenderfoundation.blender \t0x00000001006e6cb1 wm_save_mainfile_invoke + 289\n16 org.blenderfoundation.blender \t0x00000001006e0bd9 wm_operator_invoke + 521\n17 org.blenderfoundation.blender \t0x00000001006e216c wm_handler_operator_call + 636\n18 org.blenderfoundation.blender \t0x00000001006e1836 wm_handlers_do_intern + 1782\n19 org.blenderfoundation.blender \t0x00000001006dcdbf wm_handlers_do + 31\n20 org.blenderfoundation.blender \t0x00000001006dca1d wm_event_do_handlers + 3373\n21 org.blenderfoundation.blender \t0x00000001006d5360 WM_main + 32\n22 org.blenderfoundation.blender \t0x00000001002b3b8b main + 907\n23 libdyld.dylib \t0x00007fff203ca621 start + 1\n\nThread 1:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 16:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 libdispatch.dylib \t0x00007fff20204c5c _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t0x00007fff2020512e _dispatch_semaphore_wait_slow + 98\n3 org.blenderfoundation.blender \t0x00000001063a8b12 IlmThread_2_4::(anonymous namespace)::DefaultWorkerThread::run() + 50\n4 org.blenderfoundation.blender \t0x00000001063a767e void* std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, std::__1::default_delete<std::__1::__thread_struct> >, void (IlmThread_2_4::Thread::*)(), IlmThread_2_4::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 17:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 com.apple.audio.caulk \t0x00007fff284ad92a caulk::mach::semaphore::wait_or_error() + 16\n2 com.apple.audio.caulk \t0x00007fff2849a6e6 caulk::semaphore::timed_wait(double) + 110\n3 com.apple.audio.caulk \t0x00007fff2849a634 caulk::concurrent::details::worker_thread::run() + 30\n4 com.apple.audio.caulk \t0x00007fff2849a3c0 void* caulk::thread_proxy<std::__1::tuple<caulk::thread::attributes, void (caulk::concurrent::details::worker_thread::*)(), std::__1::tuple<caulk::concurrent::details::worker_thread*> > >(void*) + 45\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 18:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.audio.CoreAudio \t0x00007fff21e9edd5 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 com.apple.audio.CoreAudio \t0x00007fff21d3a467 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 3435\n4 com.apple.audio.CoreAudio \t0x00007fff21eddf2a HALB_IOThread::Entry(void*) + 72\n5 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n6 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 28:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 29:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 30:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 31:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 32:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 33:\n0 libsystem_kernel.dylib \t0x00007fff2037aeba semaphore_wait_trap + 10\n1 org.blenderfoundation.blender \t0x00000001006cbec8 tbb::internal::rml::private_worker::run() + 104\n2 org.blenderfoundation.blender \t0x00000001006cbe59 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n4 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 34:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 com.apple.CoreFoundation \t0x00007fff204a7bf7 __CFRunLoopServiceMachPort + 316\n3 com.apple.CoreFoundation \t0x00007fff204a62ca __CFRunLoopRun + 1315\n4 com.apple.CoreFoundation \t0x00007fff204a56ce CFRunLoopRunSpecific + 563\n5 com.apple.AppKit \t0x00007fff22e4b7c6 _NSEventThread + 124\n6 libsystem_pthread.dylib \t0x00007fff203af950 _pthread_start + 224\n7 libsystem_pthread.dylib \t0x00007fff203ab47b thread_start + 15\n\nThread 35:: Dispatch queue: com.apple.opengl.cvmDoWork\n0 libsystem_kernel.dylib \t0x00007fff2037ae7e mach_msg_trap + 10\n1 libsystem_kernel.dylib \t0x00007fff2037b1f0 mach_msg + 60\n2 libdispatch.dylib \t0x00007fff2021a776 _dispatch_mach_send_and_wait_for_reply + 518\n3 libdispatch.dylib \t0x00007fff2021ab6e dispatch_mach_send_with_result_and_wait_for_reply + 50\n4 libxpc.dylib \t0x00007fff200f11ac xpc_connection_send_message_with_reply_sync + 238\n5 libCoreVMClient.dylib \t0x00007fff6c90670a cvms_element_build_and_get_internal + 229\n6 libCoreVMClient.dylib \t0x00007fff6c90660e cvms_element_build_from_source + 169\n7 libCVMSPluginSupport.dylib \t0x00007fff6c91bf14 cvm_deferred_build_modular(void*) + 422\n8 libdispatch.dylib \t0x00007fff202047c7 _dispatch_client_callout + 8\n9 libdispatch.dylib \t0x00007fff2020a5fe _dispatch_lane_serial_drain + 606\n10 libdispatch.dylib \t0x00007fff2020b0cb _dispatch_lane_invoke + 375\n11 libdispatch.dylib \t0x00007fff20214c5d _dispatch_workloop_worker_thread + 819\n12 libsystem_pthread.dylib \t0x00007fff203ac499 _pthread_wqthread + 314\n13 libsystem_pthread.dylib \t0x00007fff203ab467 start_wqthread + 15\n\nThread 36:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 37:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 38:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 39:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 40:\n0 libsystem_pthread.dylib \t0x00007fff203ab458 start_wqthread + 0\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000024 rbx: 0x00000c3300041000 rcx: 0x00007fff6cc64690 rdx: 0x00007fff6cc65ae8\n rdi: 0x0000000000000006 rsi: 0x0000000000000000 rbp: 0x00007ffeefa8dce0 rsp: 0x00007ffeefa8db50\n r8: 0x0000000000000001 r9: 0x0000600003844bf0 r10: 0x0000000000000001 r11: 0x0000000186600082\n r12: 0x0000000000000000 r13: 0x0000000000000003 r14: 0x0000000000000000 r15: 0x00000c3300041000\n rip: 0x00007fff6cc64690 rfl: 0x0000000000010217 cr2: 0x0000000000000024\n \nLogical CPU: 0\nError Code: 0x00000004 (no mapping for user data read)\nTrap Number: 14\n\nThread 0 instruction stream:\n ff 48 8b 8d 28 ff ff ff-48 8b 44 01 08 e9 b6 f7 .H..(...H.D.....\n ff ff 85 d2 0f 84 84 00-00 00 49 89 fd be 00 00 ..........I.....\n 80 38 66 2e 0f 1f 84 00-00 00 00 00 0f 1f 40 00 .8f...........@.\n 89 d7 8d 14 3f 81 c6 00-00 80 ff f7 c7 00 02 00 ....?...........\n 00 74 ed 81 e2 fe 03 00-00 4c 89 ef 4c 8b ad 08 .t.......L..L...\n ff ff ff eb 4d c1 e6 0d-81 c6 00 00 00 38 eb 42 ....M........8.B\n [8b]08 89 8d 30 ff ff ff-8b 48 04 89 8d 34 ff ff ....0....H...4..\t<==\n ff e9 bc f9 ff ff 8b 08-89 8d 30 ff ff ff 8b 48 ..........0....H\n 04 89 8d 34 ff ff ff 8b-48 08 89 8d 38 ff ff ff ...4....H...8...\n 8b 40 0c 89 85 3c ff ff-ff e9 42 05 00 00 31 f6 .@...<....B...1.\n 31 d2 c1 e2 0d 09 f2 09-ca 89 95 30 ff ff ff 41 1..........0...A\n 83 fd 02 0f 82 e0 03 00-00 0f b7 70 02 89 f1 c1 ...........p....\n \nThread 0 last branch register state not available.\n\n\nBinary Images:\n 0x10016f000 - 0x10ab5afff +org.blenderfoundation.blender (2.92.0 - 2.92.0 2021-02-25) <F92572D3-A6D1-3A9C-9F23-72D19FC8242A> /Applications/Blender.app/Contents/MacOS/Blender\n 0x11191c000 - 0x111988fff +libomp.dylib (0) <535E76BC-1650-3651-9C62-97A995647107> /Applications/Blender.app/Contents/Resources/lib/libomp.dylib\n 0x1186b5000 - 0x118818fff com.apple.audio.units.Components (1.14 - 1.14) <8C3B07AD-A96B-383A-94DC-902CCE4CD511> /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio\n 0x11886d000 - 0x11887cfff libobjc-trampolines.dylib (818.2) <29187EF9-2BD6-3ABF-8088-DE708721B612> /usr/lib/libobjc-trampolines.dylib\n 0x118c6b000 - 0x118d06fff dyld (832.7.3) <0D4EA85F-7E30-338B-9215-314A5A5539B6> /usr/lib/dyld\n 0x118d83000 - 0x119332fff com.apple.audio.AudioDSPComponents (1.0 - 1) <1A7FCA3F-190C-32F0-A48D-1524A11B0910> /System/Library/Components/AudioDSP.component/Contents/MacOS/AudioDSP\n 0x119963000 - 0x119ce2fff com.apple.AMDRadeonX6000MTLDriver (4.2.15 - 4.0.2) <56DBFC8D-9ABB-34AE-873F-CAF3E6A184D5> /System/Library/Extensions/AMDRadeonX6000MTLDriver.bundle/Contents/MacOS/AMDRadeonX6000MTLDriver\n 0x11a0ab000 - 0x11a1fefff com.apple.AMDRadeonX6000GLDriver (4.2.15 - 4.0.2) <6A663F3B-05F2-35F1-9832-C0E3645C7E08> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/AMDRadeonX6000GLDriver\n 0x127eb0000 - 0x127eb1fff +_heapq.cpython-37m-darwin.so (0) <20086BF0-0130-3463-B824-F98C6D51BE39> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/_heapq.cpython-37m-darwin.so\n 0x1280ba000 - 0x1280bffff +math.cpython-37m-darwin.so (0) <F76ADA60-2AAA-34A7-BB31-26405F501673> /Applications/Blender.app/Contents/Resources/2.92/python/lib/python3.7/lib-dynload/math.cpython-37m-darwin.so\n 0x128fe4000 - 0x128fe7fff com.apple.CloudDocsFileProvider (1.0 - 726.1) <AB47EF12-834C-3720-BEE5-22E11638BFB7> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/CloudDocsFileProvider.bundle/Contents/MacOS/CloudDocsFileProvider\n 0x128ff8000 - 0x128ffbfff com.apple.FileProviderOverride (326.3 - 326.3) <54B6F621-7F46-3223-A227-C0757EB3F900> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride\n 0x12900c000 - 0x129027fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (1.0 - 1350.2.10) <EDD7E1EC-AB15-3496-9A57-237C9D3A2CEB> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride\n 0x7fff200e4000 - 0x7fff200e5fff libsystem_blocks.dylib (78) <E644CAA0-65B7-36E4-8041-520F3301F3DB> /usr/lib/system/libsystem_blocks.dylib\n 0x7fff200e6000 - 0x7fff2011bfff libxpc.dylib (2038.80.3) <70F26262-01AA-3CEC-9FAD-2701D24096F0> /usr/lib/system/libxpc.dylib\n 0x7fff2011c000 - 0x7fff20133fff libsystem_trace.dylib (1277.80.2) <87FEF600-48D9-31C9-B8FC-D5249B2AE95D> /usr/lib/system/libsystem_trace.dylib\n 0x7fff20134000 - 0x7fff201d3fff libcorecrypto.dylib (1000.80.5) <1EB11CFB-ABD7-36DD-97C7-C112A6601416> /usr/lib/system/libcorecrypto.dylib\n 0x7fff201d4000 - 0x7fff20200fff libsystem_malloc.dylib (317.40.8) <A498D1EF-E43D-310C-84E8-9C0AADA0C475> /usr/lib/system/libsystem_malloc.dylib\n 0x7fff20201000 - 0x7fff20245fff libdispatch.dylib (1271.40.12) <AD988EEA-1A2F-3404-9A6E-390FC2504223> /usr/lib/system/libdispatch.dylib\n 0x7fff20246000 - 0x7fff2027efff libobjc.A.dylib (818.2) <EB6B543F-D42C-3FB2-A2EC-43407C5F80D3> /usr/lib/libobjc.A.dylib\n 0x7fff2027f000 - 0x7fff20281fff libsystem_featureflags.dylib (28.60.1) <9CECB43A-094E-3CA9-B730-24DEA1A6DE05> /usr/lib/system/libsystem_featureflags.dylib\n 0x7fff20282000 - 0x7fff2030afff libsystem_c.dylib (1439.40.11) <4AF71812-4099-3E96-B271-1F259491A2B2> /usr/lib/system/libsystem_c.dylib\n 0x7fff2030b000 - 0x7fff20360fff libc++.1.dylib (904.4) <B217D905-4F9C-3DE0-8844-88FAA3C2C851> /usr/lib/libc++.1.dylib\n 0x7fff20361000 - 0x7fff20379fff libc++abi.dylib (904.4) <3C9FE530-3CD2-3A64-8A36-70816AEBDF0D> /usr/lib/libc++abi.dylib\n 0x7fff2037a000 - 0x7fff203a8fff libsystem_kernel.dylib (7195.81.3) <AB413518-ECDE-3F04-A61C-278D3CF43076> /usr/lib/system/libsystem_kernel.dylib\n 0x7fff203a9000 - 0x7fff203b4fff libsystem_pthread.dylib (454.80.2) <B989DF6C-ADFE-3AF9-9C91-07D2521F9E47> /usr/lib/system/libsystem_pthread.dylib\n 0x7fff203b5000 - 0x7fff203effff libdyld.dylib (832.7.3) <4641E48F-75B5-3CC7-8263-47BF79F15394> /usr/lib/system/libdyld.dylib\n 0x7fff203f0000 - 0x7fff203f9fff libsystem_platform.dylib (254.80.2) <1C3E1A0A-92A8-3CDE-B622-8940B43A5DF2> /usr/lib/system/libsystem_platform.dylib\n 0x7fff203fa000 - 0x7fff20425fff libsystem_info.dylib (542.40.3) <0C96CFE8-71F5-3335-8423-581BC3DE5846> /usr/lib/system/libsystem_info.dylib\n 0x7fff20426000 - 0x7fff208c1fff com.apple.CoreFoundation (6.9 - 1774.101) <2A0E160E-9EE6-3B23-8832-6979A16EC250> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7fff208c2000 - 0x7fff20af1fff com.apple.LaunchServices (1122.11 - 1122.11) <9ACD5692-3B92-3E6E-8B24-56ADCC911556> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices\n 0x7fff20af2000 - 0x7fff20bc5fff com.apple.gpusw.MetalTools (1.0 - 1) <B1FDD261-7707-3E20-A6C2-99D9AF46356B> /System/Library/PrivateFrameworks/MetalTools.framework/Versions/A/MetalTools\n 0x7fff20bc6000 - 0x7fff20e29fff libBLAS.dylib (1336.40.1) <92702864-A5C6-3E22-86F6-DB329532674A> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib\n 0x7fff20e2a000 - 0x7fff20e77fff com.apple.Lexicon-framework (1.0 - 86.1) <2F429EBD-1BD2-3057-B760-8A81546DBD6F> /System/Library/PrivateFrameworks/Lexicon.framework/Versions/A/Lexicon\n 0x7fff20e78000 - 0x7fff20ee6fff libSparse.dylib (106) <B889DE4E-7356-3CC8-A13E-68D15E2024DF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparse.dylib\n 0x7fff20ee7000 - 0x7fff20f64fff com.apple.SystemConfiguration (1.20 - 1.20) <3518EA0E-C32D-32CC-81B9-0F3C83B6430C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration\n 0x7fff20f65000 - 0x7fff20f9afff libCRFSuite.dylib (50) <970D1F7B-5DBD-355F-80D8-C820AA1626D2> /usr/lib/libCRFSuite.dylib\n 0x7fff20f9b000 - 0x7fff211d2fff libmecabra.dylib (929.1.1) <102A0AD8-D119-340B-B652-B75F0AAB1C7E> /usr/lib/libmecabra.dylib\n 0x7fff211d3000 - 0x7fff21536fff com.apple.Foundation (6.9 - 1774.101) <8D9081B3-3F6A-31A0-9B20-1AE5CD8DD747> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation\n 0x7fff21537000 - 0x7fff21623fff com.apple.LanguageModeling (1.0 - 247.1) <1A05BCD7-232F-3950-936D-EC0F95BA3FB0> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling\n 0x7fff21624000 - 0x7fff2175afff com.apple.CoreDisplay (231.3 - 231.3) <6DD6A260-800F-3284-842C-8E4CB9EA47FF> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay\n 0x7fff2175b000 - 0x7fff219d1fff com.apple.audio.AudioToolboxCore (1.0 - 1180.25) <DEE2C5BA-BFD1-349F-A10A-B10717BA8F7C> /System/Library/PrivateFrameworks/AudioToolboxCore.framework/Versions/A/AudioToolboxCore\n 0x7fff219d2000 - 0x7fff21bbafff com.apple.CoreText (677.3.0.4 - 677.3.0.4) <9A8DC9A0-1A80-3A26-ACA0-A245D3FFF921> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText\n 0x7fff21bbb000 - 0x7fff2225ffff com.apple.audio.CoreAudio (5.0 - 5.0) <801E2D1E-7EA5-37DA-8F44-B6D7DD3CE5B9> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7fff22260000 - 0x7fff225b1fff com.apple.security (7.0 - 59754.80.3) <B377D7C7-EDB6-3737-B492-E9872F4C6469> /System/Library/Frameworks/Security.framework/Versions/A/Security\n 0x7fff225b2000 - 0x7fff22813fff libicucore.A.dylib (66109) <8F8D8A8B-4EE0-3C09-9F45-725A1FBDD38C> /usr/lib/libicucore.A.dylib\n 0x7fff22814000 - 0x7fff2281dfff libsystem_darwin.dylib (1439.40.11) <E016D8F7-C87F-36F8-B8A0-6A61B8E4BACB> /usr/lib/system/libsystem_darwin.dylib\n 0x7fff2281e000 - 0x7fff22b05fff com.apple.CoreServices.CarbonCore (1307 - 1307) <B857EADF-D517-34E8-8053-34C0E6695250> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore\n 0x7fff22b06000 - 0x7fff22b44fff com.apple.CoreServicesInternal (476 - 476) <0DA95074-B315-3B84-B8A3-BAEDC4471A2C> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal\n 0x7fff22b45000 - 0x7fff22b7ffff com.apple.CSStore (1122.11 - 1122.11) <89992991-8538-380B-B2B8-4EA997CBFDBE> /System/Library/PrivateFrameworks/CoreServicesStore.framework/Versions/A/CoreServicesStore\n 0x7fff22b80000 - 0x7fff22c2efff com.apple.framework.IOKit (2.0.2 - 1845.81.1) <49AC0177-35A3-3C96-AD9D-3E59923C4761> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit\n 0x7fff22c2f000 - 0x7fff22c3afff libsystem_notify.dylib (279.40.4) <B2BF20C7-448A-3FBD-A2F5-AB7618D173F6> /usr/lib/system/libsystem_notify.dylib\n 0x7fff22c3b000 - 0x7fff22c86fff libsandbox.1.dylib (1441.60.4) <591F41F3-1FE9-354F-A1F9-BC0CC73333DA> /usr/lib/libsandbox.1.dylib\n 0x7fff22c87000 - 0x7fff239e9fff com.apple.AppKit (6.9 - 2022.30.122) <EA4B3536-A5AF-3E5D-A8E3-A3F795F34F05> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n 0x7fff239ea000 - 0x7fff23c3efff com.apple.UIFoundation (1.0 - 727.3) <5A905085-B5EB-3F71-A663-200428E7A5F4> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation\n 0x7fff23c3f000 - 0x7fff23c51fff com.apple.UniformTypeIdentifiers (633.0.2 - 633.0.2) <2AAE247F-1BA0-3E42-A07B-CBE413747B30> /System/Library/Frameworks/UniformTypeIdentifiers.framework/Versions/A/UniformTypeIdentifiers\n 0x7fff23c52000 - 0x7fff23ddcfff com.apple.desktopservices (1.18 - 1346.3.1) <2144B85E-A433-3F9E-A25D-E8F9D7B6D175> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv\n 0x7fff23ddd000 - 0x7fff23deffff com.apple.metadata.SpotlightLinguistics (1.0 - 1) <7FC34645-4185-3382-8813-9780C822BB15> /System/Library/PrivateFrameworks/SpotlightLinguistics.framework/Versions/A/SpotlightLinguistics\n 0x7fff240a9000 - 0x7fff246ecfff libnetwork.dylib (2288.80.2) <A3F1E999-6D61-32D7-B3F7-67832CEA53CD> /usr/lib/libnetwork.dylib\n 0x7fff246ed000 - 0x7fff24b8afff com.apple.CFNetwork (1220.1 - 1220.1) <04A917FB-DBFB-3432-BA4C-5B860990A420> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork\n 0x7fff24b8b000 - 0x7fff24b99fff libsystem_networkextension.dylib (1295.80.3) <5213D866-7D0E-3FD9-8E1A-03C0E39CEC44> /usr/lib/system/libsystem_networkextension.dylib\n 0x7fff24b9a000 - 0x7fff24b9afff libenergytrace.dylib (22) <33A9FBF3-A2D3-3ECE-9370-B0ADDE3896DE> /usr/lib/libenergytrace.dylib\n 0x7fff24b9b000 - 0x7fff24bf6fff libMobileGestalt.dylib (978.80.1) <C4C7A5DC-C3AD-374D-902A-B6DED14FBB67> /usr/lib/libMobileGestalt.dylib\n 0x7fff24bf7000 - 0x7fff24c0dfff libsystem_asl.dylib (385) <5B48071E-85EB-33B0-AE9B-127AEB398AEC> /usr/lib/system/libsystem_asl.dylib\n 0x7fff24c0e000 - 0x7fff24c25fff com.apple.TCC (1.0 - 1) <2F48471B-68F3-3017-8B18-BEDD4ED5853F> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC\n 0x7fff24c26000 - 0x7fff24f8cfff com.apple.SkyLight (1.600.0 - 570.7) <8034EAA7-787C-3A3E-A301-FF90376F247D> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight\n 0x7fff24f8d000 - 0x7fff25620fff com.apple.CoreGraphics (2.0 - 1463.3.2) <29845645-F6F2-34E0-AC0D-C659773C78ED> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics\n 0x7fff25621000 - 0x7fff25717fff com.apple.ColorSync (4.13.0 - 3473.3.1) <A67D9B0A-E9FB-325A-873B-032DAF45C112> /System/Library/Frameworks/ColorSync.framework/Versions/A/ColorSync\n 0x7fff25718000 - 0x7fff25773fff com.apple.HIServices (1.22 - 714) <780B2B09-80A6-32C8-B9E5-024988196E00> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices\n 0x7fff25b1f000 - 0x7fff25f3dfff com.apple.CoreData (120 - 1044.3) <7BE9684B-4439-3008-A2A7-4093BBCA180A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData\n 0x7fff25f3e000 - 0x7fff25f54fff com.apple.ProtocolBuffer (1 - 285.23.11.29.1) <58CD91DC-64A9-3A97-AE41-6EA30308D617> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer\n 0x7fff25f55000 - 0x7fff26114fff libsqlite3.dylib (321.1) <ACCC6A4C-3257-38A4-8AFB-BA73D906205B> /usr/lib/libsqlite3.dylib\n 0x7fff26115000 - 0x7fff26191fff com.apple.Accounts (113 - 113) <BCB8494A-A340-30A1-928C-9B53E953328D> /System/Library/Frameworks/Accounts.framework/Versions/A/Accounts\n 0x7fff26192000 - 0x7fff261aafff com.apple.commonutilities (8.0 - 900) <8C96D016-2B40-39C0-A51C-9CF687AE7218> /System/Library/PrivateFrameworks/CommonUtilities.framework/Versions/A/CommonUtilities\n 0x7fff261ab000 - 0x7fff2622cfff com.apple.BaseBoard (526 - 526) <3A964BB6-7AB8-3B5D-BAF6-40F56D2BA393> /System/Library/PrivateFrameworks/BaseBoard.framework/Versions/A/BaseBoard\n 0x7fff2622d000 - 0x7fff26278fff com.apple.RunningBoardServices (1.0 - 505.80.1) <4B9FFFB3-310F-350A-BEBB-AB779BD3F405> /System/Library/PrivateFrameworks/RunningBoardServices.framework/Versions/A/RunningBoardServices\n 0x7fff26279000 - 0x7fff262eefff com.apple.AE (918.0.1 - 918.0.1) <9B6B42DB-8768-343B-B10E-A9A5710280CD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE\n 0x7fff262ef000 - 0x7fff262f5fff libdns_services.dylib (1310.80.1) <97EB5DFD-BB41-3834-BF09-1F597D84F324> /usr/lib/libdns_services.dylib\n 0x7fff262f6000 - 0x7fff262fdfff libsystem_symptoms.dylib (1431.40.36) <BC85B46C-02EE-31FF-861D-F0DE01E8F6CF> /usr/lib/system/libsystem_symptoms.dylib\n 0x7fff262fe000 - 0x7fff26482fff com.apple.Network (1.0 - 1) <75C2713C-F0D8-32BA-A839-17A2AE49A061> /System/Library/Frameworks/Network.framework/Versions/A/Network\n 0x7fff26483000 - 0x7fff264a7fff com.apple.analyticsd (1.0 - 1) <4FFF906A-FE79-38F9-B777-AE878A0C99F1> /System/Library/PrivateFrameworks/CoreAnalytics.framework/Versions/A/CoreAnalytics\n 0x7fff264a8000 - 0x7fff264aafff libDiagnosticMessagesClient.dylib (112) <20EDB261-69C7-3E4A-8C00-878814186A62> /usr/lib/libDiagnosticMessagesClient.dylib\n 0x7fff264ab000 - 0x7fff264f7fff com.apple.spotlight.metadata.utilities (1.0 - 2150.7.5) <FB7BF527-2D95-3E82-AAD8-D42B33DAC0F0> /System/Library/PrivateFrameworks/MetadataUtilities.framework/Versions/A/MetadataUtilities\n 0x7fff264f8000 - 0x7fff26592fff com.apple.Metadata (10.7.0 - 2150.7.5) <49187239-597B-31A1-8895-8AA265C818C7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata\n 0x7fff26593000 - 0x7fff26599fff com.apple.DiskArbitration (2.7 - 2.7) <ACFCD23E-05DF-3F96-BCFA-E294AAAFD2CE> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration\n 0x7fff2659a000 - 0x7fff26c40fff com.apple.vImage (8.1 - 544.2) <3EBF95E1-30EB-3162-A9D4-B97BE581B69F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage\n 0x7fff26c41000 - 0x7fff26f0bfff com.apple.QuartzCore (1.11 - 926.8) <04D8759B-1119-3E37-B922-32BDECB7C5D2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore\n 0x7fff26f0c000 - 0x7fff26f4dfff libFontRegistry.dylib (309) <9E9329F6-7384-3C7F-83E7-D52CD7FFBC09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib\n 0x7fff26f4e000 - 0x7fff2708ffff com.apple.coreui (2.1 - 690) <6DB427BB-44CA-3002-A3FF-77F0FEFC2A51> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI\n 0x7fff27090000 - 0x7fff2717bfff com.apple.ViewBridge (551.3 - 551.3) <9F31CEDB-5B8A-3BAE-A638-E9F352EF4E87> /System/Library/PrivateFrameworks/ViewBridge.framework/Versions/A/ViewBridge\n 0x7fff2717c000 - 0x7fff27187fff com.apple.PerformanceAnalysis (1.275 - 275) <2E5E666D-EE93-3949-8C76-692FA748D129> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis\n 0x7fff27188000 - 0x7fff27197fff com.apple.OpenDirectory (11.2 - 230.40.1) <333A7F2E-0F3E-37F1-9E1B-69996F5084D2> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory\n 0x7fff27198000 - 0x7fff271b7fff com.apple.CFOpenDirectory (11.2 - 230.40.1) <25F138F8-9E55-3749-8271-0FDB275C3E2C> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory\n 0x7fff271b8000 - 0x7fff271c0fff com.apple.CoreServices.FSEvents (1290.40.2 - 1290.40.2) <6B70B98B-BCC5-3FBE-A6B5-CD0696AA055A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents\n 0x7fff271c1000 - 0x7fff271e5fff com.apple.coreservices.SharedFileList (144 - 144) <C861FAD6-D3A5-302C-88AE-B2813F7201A7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList\n 0x7fff271e6000 - 0x7fff271e8fff libapp_launch_measurement.dylib (14.1) <2BBB708C-4D91-364E-ABD0-39BF198688A6> /usr/lib/libapp_launch_measurement.dylib\n 0x7fff271e9000 - 0x7fff27231fff com.apple.CoreAutoLayout (1.0 - 21.10.1) <7A2E42E6-3AF2-3ECB-8A16-5C4AC41206EE> /System/Library/PrivateFrameworks/CoreAutoLayout.framework/Versions/A/CoreAutoLayout\n 0x7fff27232000 - 0x7fff27314fff libxml2.2.dylib (34.9) <E0BF29C7-869B-3DD5-82AE-F36E6398091A> /usr/lib/libxml2.2.dylib\n 0x7fff27315000 - 0x7fff27361fff com.apple.CoreVideo (1.8 - 408.4) <50857F8D-C7CC-3609-B0DB-FC3C7382243B> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo\n 0x7fff27362000 - 0x7fff27364fff com.apple.loginsupport (1.0 - 1) <B149BCAF-854C-3820-809D-15C6077FFB8B> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport\n 0x7fff27365000 - 0x7fff2738dfff com.apple.aps.framework (4.0 - 4.0) <D86ED827-F22D-3A52-B055-251478B29AE1> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService\n 0x7fff2738e000 - 0x7fff273abfff com.apple.UserManagement (1.0 - 1) <B6B35079-3860-384F-B7A2-584192BAAE70> /System/Library/PrivateFrameworks/UserManagement.framework/Versions/A/UserManagement\n 0x7fff273ac000 - 0x7fff2754bfff com.apple.cloudkit.CloudKit (970 - 970) <58BD254C-AAF1-3CC5-AAB7-2EF0A70BA033> /System/Library/Frameworks/CloudKit.framework/Versions/A/CloudKit\n 0x7fff2754c000 - 0x7fff275cefff com.apple.CloudDocs (1.0 - 726.1) <EDBE33B4-1629-3323-902F-F6DABE66D552> /System/Library/PrivateFrameworks/CloudDocs.framework/Versions/A/CloudDocs\n 0x7fff282c8000 - 0x7fff28345fff com.apple.corelocation (2420.12.16 - 2420.12.16) <8BD49018-78D4-3A81-88AD-47DE1A8E3BFE> /System/Library/Frameworks/CoreLocation.framework/Versions/A/CoreLocation\n 0x7fff28346000 - 0x7fff28356fff libsystem_containermanager.dylib (318.80.2) <6F08275F-B912-3D8E-9D74-4845158AE4F3> /usr/lib/system/libsystem_containermanager.dylib\n 0x7fff28357000 - 0x7fff28368fff com.apple.IOSurface (289.3 - 289.3) <029C5E16-2E04-3E98-BE25-CC8BAE5E3D19> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface\n 0x7fff28369000 - 0x7fff28371fff com.apple.IOAccelerator (439.52 - 439.52) <41EDF102-E1B5-3FBA-A74A-6C583CAA5D24> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator\n 0x7fff28372000 - 0x7fff28497fff com.apple.Metal (244.32.7 - 244.32.7) <829B9C4D-2DB6-38C9-9FE8-E6544FB3BDCC> /System/Library/Frameworks/Metal.framework/Versions/A/Metal\n 0x7fff28498000 - 0x7fff284b4fff com.apple.audio.caulk (1.0 - 70) <3FFEB564-C7CC-3F3E-B193-3F4E7B7C6764> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7fff284b5000 - 0x7fff2859efff com.apple.CoreMedia (1.0 - 2765.6.4.2) <8E50C806-C6A2-3B96-B3D2-DA1FFC73D2A8> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia\n 0x7fff2859f000 - 0x7fff286fbfff libFontParser.dylib (305.3.0.1) <2CD3B3C9-7022-34DD-BF53-D48D79DEF726> /System/Library/PrivateFrameworks/FontServices.framework/libFontParser.dylib\n 0x7fff286fc000 - 0x7fff289fbfff com.apple.HIToolbox (2.1.1 - 1061.2) <82B316E1-E47F-334D-8C33-DB1B7E8A4F71> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox\n 0x7fff289fc000 - 0x7fff28a0ffff com.apple.framework.DFRFoundation (1.0 - 265) <4B26DB42-BFDD-3B0D-8966-3D0926A3A5B7> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation\n 0x7fff28a10000 - 0x7fff28a13fff com.apple.dt.XCTTargetBootstrap (1.0 - 17500) <D279B67B-7108-3A16-93E5-5A429B898DAA> /System/Library/PrivateFrameworks/XCTTargetBootstrap.framework/Versions/A/XCTTargetBootstrap\n 0x7fff28a14000 - 0x7fff28a3dfff com.apple.CoreSVG (1.0 - 149) <D88B5A7D-F9F7-36C2-A346-87D7163605A0> /System/Library/PrivateFrameworks/CoreSVG.framework/Versions/A/CoreSVG\n 0x7fff28a3e000 - 0x7fff28c78fff com.apple.ImageIO (3.3.0 - 2130.3.5) <3558ABA9-6522-36A8-A49D-8641A9D7FCE1> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO\n 0x7fff28c79000 - 0x7fff28ff6fff com.apple.CoreImage (16.2.0 - 1130.1) <29BE82F7-93BE-336A-AF66-9DD3F48B8565> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage\n 0x7fff28ff7000 - 0x7fff29052fff com.apple.MetalPerformanceShaders.MPSCore (1.0 - 1) <287C79B5-4E13-3DF6-BDC4-439EC621E010> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSCore.framework/Versions/A/MPSCore\n 0x7fff29053000 - 0x7fff29056fff libsystem_configuration.dylib (1109.60.2) <4917D824-4DE8-32CC-9ED2-1FBF371FEB9F> /usr/lib/system/libsystem_configuration.dylib\n 0x7fff29057000 - 0x7fff2905bfff libsystem_sandbox.dylib (1441.60.4) <5F7F3DD1-4B38-310C-AA8F-19FF1B0F5276> /usr/lib/system/libsystem_sandbox.dylib\n 0x7fff2905c000 - 0x7fff2905dfff com.apple.AggregateDictionary (1.0 - 1) <E6C1A91D-4ADE-33CB-AA47-2F573811BFD9> /System/Library/PrivateFrameworks/AggregateDictionary.framework/Versions/A/AggregateDictionary\n 0x7fff2905e000 - 0x7fff29061fff com.apple.AppleSystemInfo (3.1.5 - 3.1.5) <4F8A1D06-3EFF-3174-BE9C-C4B70A3EA290> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSystemInfo\n 0x7fff29062000 - 0x7fff29063fff liblangid.dylib (136) <E8044658-AE79-3930-A902-07A38BB22382> /usr/lib/liblangid.dylib\n 0x7fff29064000 - 0x7fff29104fff com.apple.CoreNLP (1.0 - 245.1) <6C49B26B-CB39-3504-AD5E-9C3333FFE086> /System/Library/PrivateFrameworks/CoreNLP.framework/Versions/A/CoreNLP\n 0x7fff29105000 - 0x7fff2910bfff com.apple.LinguisticData (1.0 - 399) <B059FF7F-731A-38F1-884A-588C6C8CA7F2> /System/Library/PrivateFrameworks/LinguisticData.framework/Versions/A/LinguisticData\n 0x7fff2910c000 - 0x7fff297c9fff libBNNS.dylib (288.80.1) <C5CD30D8-114B-3104-9020-E5C05E68CEE8> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib\n 0x7fff297ca000 - 0x7fff2999dfff libvDSP.dylib (760.40.6) <4CCEE561-A72B-33BC-B9F9-77A6CF2E7AF0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib\n 0x7fff2999e000 - 0x7fff299b0fff com.apple.CoreEmoji (1.0 - 128) <D43F3FFA-6692-3D56-ACBA-DDA40C566DDE> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji\n 0x7fff299b1000 - 0x7fff299bbfff com.apple.IOMobileFramebuffer (343.0.0 - 343.0.0) <B15E9DA1-1C81-3ECF-94C7-FD137AD6C5E2> /System/Library/PrivateFrameworks/IOMobileFramebuffer.framework/Versions/A/IOMobileFramebuffer\n 0x7fff299bc000 - 0x7fff29a8efff com.apple.framework.CoreWLAN (16.0 - 1657) <35927D28-3324-3CAB-9255-276A7022EADC> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN\n 0x7fff29a8f000 - 0x7fff29c8efff com.apple.CoreUtils (6.5 - 650.6) <184C48A4-7F66-395B-81DB-DAA1641383CF> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils\n 0x7fff29c8f000 - 0x7fff29cb1fff com.apple.MobileKeyBag (2.0 - 1.0) <0F83FED4-709A-37A0-9E04-EFFD71CB1272> /System/Library/PrivateFrameworks/MobileKeyBag.framework/Versions/A/MobileKeyBag\n 0x7fff29cb2000 - 0x7fff29cc2fff com.apple.AssertionServices (1.0 - 505.80.1) <A00B802D-7BB8-3F6B-A79D-E9697F7D0ABB> /System/Library/PrivateFrameworks/AssertionServices.framework/Versions/A/AssertionServices\n 0x7fff29cc3000 - 0x7fff29d4ffff com.apple.securityfoundation (6.0 - 55240.40.4) <72AC63B1-0B72-394F-97E8-BA9B114DD0A9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation\n 0x7fff29d50000 - 0x7fff29d59fff com.apple.coreservices.BackgroundTaskManagement (1.0 - 104) <EC15118E-62BD-3C24-A880-3B9B74318B0B> /System/Library/PrivateFrameworks/BackgroundTaskManagement.framework/Versions/A/BackgroundTaskManagement\n 0x7fff29d5a000 - 0x7fff29d5efff com.apple.xpc.ServiceManagement (1.0 - 1) <FD031028-B702-3909-B2AF-3916404DD4A8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement\n 0x7fff29d5f000 - 0x7fff29d61fff libquarantine.dylib (119.40.2) <40D35D75-524B-3DA6-8159-E7E0FA66F5BC> /usr/lib/system/libquarantine.dylib\n 0x7fff29d62000 - 0x7fff29d6dfff libCheckFix.dylib (31) <74E17BB2-1A3C-3574-92DD-63ABE39E3FF9> /usr/lib/libCheckFix.dylib\n 0x7fff29d6e000 - 0x7fff29d85fff libcoretls.dylib (169) <B33BEF87-3275-356D-9815-D0E94122D2EB> /usr/lib/libcoretls.dylib\n 0x7fff29d86000 - 0x7fff29d96fff libbsm.0.dylib (68.40.1) <D71EF121-D4B0-306E-9843-9FAFD558E3A4> /usr/lib/libbsm.0.dylib\n 0x7fff29d97000 - 0x7fff29de0fff libmecab.dylib (929.1.1) <1F424683-4213-3594-9BF5-EFCCCDAA83A5> /usr/lib/libmecab.dylib\n 0x7fff29de1000 - 0x7fff29de6fff libgermantok.dylib (24) <E40EFA11-E95C-36D1-A8BE-8CA5B1DD179D> /usr/lib/libgermantok.dylib\n 0x7fff29de7000 - 0x7fff29dfcfff libLinearAlgebra.dylib (1336.40.1) <0D017F3F-6FD6-38DB-AA14-A64523A4D093> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib\n 0x7fff29dfd000 - 0x7fff2a024fff com.apple.MetalPerformanceShaders.MPSNeuralNetwork (1.0 - 1) <8FA469B3-48BE-315B-B3A0-C868CD541608> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNeuralNetwork.framework/Versions/A/MPSNeuralNetwork\n 0x7fff2a025000 - 0x7fff2a074fff com.apple.MetalPerformanceShaders.MPSRayIntersector (1.0 - 1) <613BB6F1-3588-3E25-B523-059022FBE56E> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSRayIntersector.framework/Versions/A/MPSRayIntersector\n 0x7fff2a075000 - 0x7fff2a1bcfff com.apple.MLCompute (1.0 - 1) <01B968D9-A464-3667-8B8E-C99AEBA1FF79> /System/Library/Frameworks/MLCompute.framework/Versions/A/MLCompute\n 0x7fff2a1bd000 - 0x7fff2a1f3fff com.apple.MetalPerformanceShaders.MPSMatrix (1.0 - 1) <B988D5F6-4E54-335D-A654-12C74FD668EA> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSMatrix.framework/Versions/A/MPSMatrix\n 0x7fff2a1f4000 - 0x7fff2a231fff com.apple.MetalPerformanceShaders.MPSNDArray (1.0 - 1) <51ECDE6B-39F8-3BAB-ADC1-84C958F40A3F> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSNDArray.framework/Versions/A/MPSNDArray\n 0x7fff2a232000 - 0x7fff2a2c2fff com.apple.MetalPerformanceShaders.MPSImage (1.0 - 1) <D009508B-DCDF-3421-B1CB-40FDF4A68E93> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/Frameworks/MPSImage.framework/Versions/A/MPSImage\n 0x7fff2a2c3000 - 0x7fff2a2d2fff com.apple.AppleFSCompression (125 - 1.0) <879A04AA-F9A1-3640-A9EF-F5D0813C852A> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression\n 0x7fff2a2d3000 - 0x7fff2a2e0fff libbz2.1.0.dylib (44) <E163D5F9-E202-3A53-817B-8BC40B9293C0> /usr/lib/libbz2.1.0.dylib\n 0x7fff2a2e1000 - 0x7fff2a2e5fff libsystem_coreservices.dylib (127) <529A0663-A936-309C-9318-1B04B7F70658> /usr/lib/system/libsystem_coreservices.dylib\n 0x7fff2a2e6000 - 0x7fff2a313fff com.apple.CoreServices.OSServices (1122.11 - 1122.11) <8D30829B-426E-361E-B2A9-5850F1E5513D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices\n 0x7fff2a314000 - 0x7fff2a445fff com.apple.AuthKit (1.0 - 1) <4A9B2D94-7AB0-3417-8D4E-A9C6C31C31D4> /System/Library/PrivateFrameworks/AuthKit.framework/Versions/A/AuthKit\n 0x7fff2a4e9000 - 0x7fff2a4fbfff libz.1.dylib (76) <6E2BD7A3-DC55-3183-BBF7-3AC367BC1834> /usr/lib/libz.1.dylib\n 0x7fff2a4fc000 - 0x7fff2a543fff libsystem_m.dylib (3186.40.2) <DD26CC5C-AFF6-305F-A567-14909DD57163> /usr/lib/system/libsystem_m.dylib\n 0x7fff2a544000 - 0x7fff2a544fff libcharset.1.dylib (59) <D14F9D24-693A-37F0-8F92-D260248EB282> /usr/lib/libcharset.1.dylib\n 0x7fff2a545000 - 0x7fff2a54afff libmacho.dylib (973.4) <C2584BC4-497B-3170-ADDF-21B8E10B4DFD> /usr/lib/system/libmacho.dylib\n 0x7fff2a54b000 - 0x7fff2a566fff libkxld.dylib (7195.81.3) <DE05C188-D9FE-30DC-8299-DF3DC9F837A5> /usr/lib/system/libkxld.dylib\n 0x7fff2a567000 - 0x7fff2a572fff libcommonCrypto.dylib (60178.40.2) <822A29CE-BF54-35AD-BB15-8FAECB800C7D> /usr/lib/system/libcommonCrypto.dylib\n 0x7fff2a573000 - 0x7fff2a57dfff libunwind.dylib (200.10) <1D0A4B4A-4370-3548-8DC1-42A7B4BD45D3> /usr/lib/system/libunwind.dylib\n 0x7fff2a57e000 - 0x7fff2a585fff liboah.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/liboah.dylib\n 0x7fff2a586000 - 0x7fff2a590fff libcopyfile.dylib (173.40.2) <39DBE613-135B-3AFE-A6AF-7898A37F70C2> /usr/lib/system/libcopyfile.dylib\n 0x7fff2a591000 - 0x7fff2a598fff libcompiler_rt.dylib (102.2) <62EE1D14-5ED7-3CEC-81C0-9C93833641F1> /usr/lib/system/libcompiler_rt.dylib\n 0x7fff2a599000 - 0x7fff2a59bfff libsystem_collections.dylib (1439.40.11) <C53D5E0C-0C4F-3B35-A24B-E0D7101A3F95> /usr/lib/system/libsystem_collections.dylib\n 0x7fff2a59c000 - 0x7fff2a59efff libsystem_secinit.dylib (87.60.1) <E05E35BC-1BAB-365B-8BEE-D774189EFD3B> /usr/lib/system/libsystem_secinit.dylib\n 0x7fff2a59f000 - 0x7fff2a5a1fff libremovefile.dylib (49.40.3) <5CC12A16-82CB-32F0-9040-72CFC88A48DF> /usr/lib/system/libremovefile.dylib\n 0x7fff2a5a2000 - 0x7fff2a5a2fff libkeymgr.dylib (31) <803F6AED-99D5-3CCF-B0FA-361BCF14C8C0> /usr/lib/system/libkeymgr.dylib\n 0x7fff2a5a3000 - 0x7fff2a5aafff libsystem_dnssd.dylib (1310.80.1) <E0A0CAB3-6779-3C83-AC67-046CFE69F9C2> /usr/lib/system/libsystem_dnssd.dylib\n 0x7fff2a5ab000 - 0x7fff2a5b0fff libcache.dylib (83) <1A98B064-8FED-39CF-BB2E-5BDA1EF5B65A> /usr/lib/system/libcache.dylib\n 0x7fff2a5b1000 - 0x7fff2a5b2fff libSystem.B.dylib (1292.60.1) <83503CE0-32B1-36DB-A4F0-3CC6B7BCF50A> /usr/lib/libSystem.B.dylib\n 0x7fff2a5b3000 - 0x7fff2a5b6fff libfakelink.dylib (3) <D939A124-9FD5-37A2-B03B-72E98CBC98FE> /usr/lib/libfakelink.dylib\n 0x7fff2a5b7000 - 0x7fff2a5b7fff com.apple.SoftLinking (1.0 - 1) <EF2AC5FF-B98D-3252-ABA8-2FC721CBA942> /System/Library/PrivateFrameworks/SoftLinking.framework/Versions/A/SoftLinking\n 0x7fff2a5b8000 - 0x7fff2a5effff libpcap.A.dylib (98.40.1) <DE5787F8-D011-3E71-8323-936B35976D9E> /usr/lib/libpcap.A.dylib\n 0x7fff2a5f0000 - 0x7fff2a6e0fff libiconv.2.dylib (59) <AD10ECF4-E137-3152-9612-7EC548D919E8> /usr/lib/libiconv.2.dylib\n 0x7fff2a6e1000 - 0x7fff2a6f2fff libcmph.dylib (8) <A5D1EBB3-70A1-3ECA-A3C7-E97FBAD36ECF> /usr/lib/libcmph.dylib\n 0x7fff2a6f3000 - 0x7fff2a764fff libarchive.2.dylib (83.40.4) <9061C767-43FD-3483-9C48-73973AF82DC1> /usr/lib/libarchive.2.dylib\n 0x7fff2a765000 - 0x7fff2a7ccfff com.apple.SearchKit (1.4.1 - 1.4.1) <6243D4C0-3572-30A6-889A-B8690A5EAC24> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit\n 0x7fff2a7cd000 - 0x7fff2a7cefff libThaiTokenizer.dylib (3) <47CDE3EE-60AB-38CE-9494-5CC047CACA7F> /usr/lib/libThaiTokenizer.dylib\n 0x7fff2a7cf000 - 0x7fff2a7f6fff com.apple.applesauce (1.0 - 16.26) <4A637FE0-A740-32F0-AE70-4593F6DF1573> /System/Library/PrivateFrameworks/AppleSauce.framework/Versions/A/AppleSauce\n 0x7fff2a7f7000 - 0x7fff2a80efff libapple_nghttp2.dylib (1.41) <A2F6DE8D-2B38-3669-A16E-E1BD54108F24> /usr/lib/libapple_nghttp2.dylib\n 0x7fff2a80f000 - 0x7fff2a821fff libSparseBLAS.dylib (1336.40.1) <FC45F7FD-6B10-3F8D-A553-F57C757F6717> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib\n 0x7fff2a822000 - 0x7fff2a823fff com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <F37DBCE9-20CD-33D4-806B-93B326E08422> /System/Library/Frameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders\n 0x7fff2a824000 - 0x7fff2a828fff libpam.2.dylib (28.40.1) <FA3308D0-E7B4-3A2C-AE39-0E085F6CDEE0> /usr/lib/libpam.2.dylib\n 0x7fff2a829000 - 0x7fff2a841fff libcompression.dylib (96.40.6) <9C42DB2C-0A6D-38CE-BB8D-899A9B34B695> /usr/lib/libcompression.dylib\n 0x7fff2a842000 - 0x7fff2a847fff libQuadrature.dylib (7) <55EE1866-623B-3C10-91FB-C8B06EB83995> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib\n 0x7fff2a848000 - 0x7fff2abe4fff libLAPACK.dylib (1336.40.1) <2F92E8CD-396D-3665-88EB-41A4E1A9CB31> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib\n 0x7fff2abe5000 - 0x7fff2ac33fff com.apple.DictionaryServices (1.2 - 341) <5D0B1BB2-995B-32EB-AE75-F5F27127ACAF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices\n 0x7fff2ac34000 - 0x7fff2ac4cfff liblzma.5.dylib (16) <168D84A7-8E54-361E-9161-B661D96C0C9A> /usr/lib/liblzma.5.dylib\n 0x7fff2ac4d000 - 0x7fff2ac4efff libcoretls_cfhelpers.dylib (169) <80AF345B-1989-3C88-AEF4-8FF18A366A9C> /usr/lib/libcoretls_cfhelpers.dylib\n 0x7fff2ac4f000 - 0x7fff2ad49fff com.apple.APFS (1677.81.1 - 1677.81.1) <E48CCAAC-34B5-377E-8E5D-06CDBD411C2F> /System/Library/PrivateFrameworks/APFS.framework/Versions/A/APFS\n 0x7fff2ad4a000 - 0x7fff2ad57fff libxar.1.dylib (452) <FAA7B36E-21EC-3ADF-AA6A-E3742737CA3A> /usr/lib/libxar.1.dylib\n 0x7fff2ad58000 - 0x7fff2ad5bfff libutil.dylib (58.40.2) <0A268749-08E7-3551-8969-442210651CCA> /usr/lib/libutil.dylib\n 0x7fff2ad5c000 - 0x7fff2ad84fff libxslt.1.dylib (17.3) <1C5219FB-B504-3658-B23B-2C45A3BA28F1> /usr/lib/libxslt.1.dylib\n 0x7fff2ad85000 - 0x7fff2ad8ffff libChineseTokenizer.dylib (37) <718400BF-9911-3CB6-8CCE-4C2D7C35D80A> /usr/lib/libChineseTokenizer.dylib\n 0x7fff2ad90000 - 0x7fff2ae4efff libvMisc.dylib (760.40.6) <9D11FCFC-6C30-32B6-864B-9CC3ED7D1143> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib\n 0x7fff2ae4f000 - 0x7fff2aee7fff libate.dylib (3.0.4) <42707DFB-86A4-3F56-A5AF-E6DAA7E49DC7> /usr/lib/libate.dylib\n 0x7fff2aee8000 - 0x7fff2aeeffff libIOReport.dylib (64) <8DEEA01D-B715-340A-900E-B448AB22720E> /usr/lib/libIOReport.dylib\n 0x7fff2aef0000 - 0x7fff2af1efff com.apple.CrashReporterSupport (10.13 - 15047.1) <EA306EDB-2A02-3FB6-8812-F5EAA337AEE6> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport\n 0x7fff2b00b000 - 0x7fff2b012fff libMatch.1.dylib (38) <DE8B7844-BFB2-3E3E-9FD0-1C9AD1DC1736> /usr/lib/libMatch.1.dylib\n 0x7fff2b013000 - 0x7fff2b09efff libCoreStorage.dylib (554) <044E6815-6340-31D5-BEE9-760C354E92A3> /usr/lib/libCoreStorage.dylib\n 0x7fff2b09f000 - 0x7fff2b0f2fff com.apple.AppleVAFramework (6.1.3 - 6.1.3) <E3BE877B-1C78-3ABF-8C41-66FE9B6971C7> /System/Library/PrivateFrameworks/AppleVA.framework/Versions/A/AppleVA\n 0x7fff2b0f3000 - 0x7fff2b10cfff libexpat.1.dylib (26) <1D978F91-674E-3A44-8A93-773C7E3E513C> /usr/lib/libexpat.1.dylib\n 0x7fff2b10d000 - 0x7fff2b116fff libheimdal-asn1.dylib (597.80.1) <8F6CD867-FB45-375D-82C1-E0AE79558C8C> /usr/lib/libheimdal-asn1.dylib\n 0x7fff2b117000 - 0x7fff2b12bfff com.apple.IconFoundation (479.3 - 479.3) <3563C4B4-ABF6-3DE0-8381-D3667DFE2B80> /System/Library/PrivateFrameworks/IconFoundation.framework/Versions/A/IconFoundation\n 0x7fff2b12c000 - 0x7fff2b199fff com.apple.IconServices (479.3 - 479.3) <B6859735-701D-307E-8061-298BA2296E47> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices\n 0x7fff2b19a000 - 0x7fff2b237fff com.apple.MediaExperience (1.0 - 1) <14E84D66-28B8-390E-A499-9F24B7628EC7> /System/Library/PrivateFrameworks/MediaExperience.framework/Versions/A/MediaExperience\n 0x7fff2b238000 - 0x7fff2b261fff com.apple.persistentconnection (1.0 - 1.0) <B3FE85C5-8034-38D5-8566-5317B49ECF61> /System/Library/PrivateFrameworks/PersistentConnection.framework/Versions/A/PersistentConnection\n 0x7fff2b262000 - 0x7fff2b270fff com.apple.GraphVisualizer (1.0 - 100.1) <A7393BC4-4441-31B5-BB15-5A5A70738BEC> /System/Library/PrivateFrameworks/GraphVisualizer.framework/Versions/A/GraphVisualizer\n 0x7fff2b271000 - 0x7fff2b68cfff com.apple.vision.FaceCore (4.3.2 - 4.3.2) <23CD0C8A-E300-3E28-BD5B-DDCDA4521C54> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore\n 0x7fff2b68d000 - 0x7fff2b6d7fff com.apple.OTSVG (1.0 - 677.3.0.4) <827396F3-F3A7-3A4F-BE7F-171077501137> /System/Library/PrivateFrameworks/OTSVG.framework/Versions/A/OTSVG\n 0x7fff2b6d8000 - 0x7fff2b6defff com.apple.xpc.AppServerSupport (1.0 - 2038.80.3) <C78E9D22-5110-349B-AF8E-6BA893A20214> /System/Library/PrivateFrameworks/AppServerSupport.framework/Versions/A/AppServerSupport\n 0x7fff2b6df000 - 0x7fff2b6f0fff libhvf.dylib (1.0 - $[CURRENT_PROJECT_VERSION]) <F0974976-30C0-35EB-92F1-B4CF1E974F11> /System/Library/PrivateFrameworks/FontServices.framework/libhvf.dylib\n 0x7fff2b6f1000 - 0x7fff2b6f3fff libspindump.dylib (295.1) <3B4701CB-8F66-3E50-A38A-BEEC992AAC31> /usr/lib/libspindump.dylib\n 0x7fff2b6f4000 - 0x7fff2b7b4fff com.apple.Heimdal (4.0 - 2.0) <69768234-4F4F-3AB6-B116-4AE249E6417A> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal\n 0x7fff2b7b5000 - 0x7fff2b7cffff com.apple.login (3.0 - 3.0) <B9BEC3A1-688C-3999-B705-2D50B8756E62> /System/Library/PrivateFrameworks/login.framework/Versions/A/login\n 0x7fff2b94f000 - 0x7fff2b952fff libodfde.dylib (26) <47160F56-2A36-3147-B721-279BE2F8B4A6> /usr/lib/libodfde.dylib\n 0x7fff2b953000 - 0x7fff2b9bdfff com.apple.bom (14.0 - 233) <F4B7C353-8A65-3B54-9E01-2C93CB3F55A3> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom\n 0x7fff2b9be000 - 0x7fff2ba08fff com.apple.AppleJPEG (1.0 - 1) <7F3819DE-BCE7-32B7-BB33-10C1DB2BA512> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG\n 0x7fff2ba09000 - 0x7fff2bae7fff libJP2.dylib (2130.3.5) <2DFE6642-4309-30BD-A402-F93E28F1F065> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib\n 0x7fff2bae8000 - 0x7fff2baebfff com.apple.WatchdogClient.framework (1.0 - 98.80.2) <C257C950-F430-3762-BC72-15D314D99556> /System/Library/PrivateFrameworks/WatchdogClient.framework/Versions/A/WatchdogClient\n 0x7fff2baec000 - 0x7fff2bb1ffff com.apple.MultitouchSupport.framework (4400.28 - 4400.28) <4243F7DC-7EB9-3750-BE36-527B0BADF36C> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport\n 0x7fff2bb20000 - 0x7fff2bc72fff com.apple.VideoToolbox (1.0 - 2765.6.4.2) <425BDD2D-6C26-3D09-AD9F-942EA387B2A4> /System/Library/Frameworks/VideoToolbox.framework/Versions/A/VideoToolbox\n 0x7fff2bc73000 - 0x7fff2bca5fff libAudioToolboxUtility.dylib (1180.25) <83DBFA98-F85B-3B63-B58F-C9989BAC9611> /usr/lib/libAudioToolboxUtility.dylib\n 0x7fff2bca6000 - 0x7fff2bcccfff libPng.dylib (2130.3.5) <9046A7B7-6C31-32C5-B610-6AEA6F6B2D48> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib\n 0x7fff2bccd000 - 0x7fff2bd2cfff libTIFF.dylib (2130.3.5) <CAAF5746-3171-38B1-9722-8CB9B650C627> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib\n 0x7fff2bd2d000 - 0x7fff2bd49fff com.apple.IOPresentment (54 - 37) <5AD7B6E0-1744-3C8D-8A95-FE425DEA005C> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment\n 0x7fff2bd4a000 - 0x7fff2bd50fff com.apple.GPUWrangler (6.2.2 - 6.2.2) <60363868-111B-36CF-9CDF-2643DF82002D> /System/Library/PrivateFrameworks/GPUWrangler.framework/Versions/A/GPUWrangler\n 0x7fff2bd51000 - 0x7fff2bd54fff libRadiance.dylib (2130.3.5) <71EBA416-A317-380A-984A-F6B0A0695A65> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib\n 0x7fff2bd55000 - 0x7fff2bd5afff com.apple.DSExternalDisplay (3.1 - 380) <010F8260-BC46-361E-BE59-540F765EFE74> /System/Library/PrivateFrameworks/DSExternalDisplay.framework/Versions/A/DSExternalDisplay\n 0x7fff2bd5b000 - 0x7fff2bd7ffff libJPEG.dylib (2130.3.5) <4BFCC012-7CDD-320D-845D-E475243D3ECE> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib\n 0x7fff2bd80000 - 0x7fff2bdaffff com.apple.ATSUI (1.0 - 1) <6C45783D-CF90-3F11-BA86-92D31A9B68CA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATSUI.framework/Versions/A/ATSUI\n 0x7fff2bdb0000 - 0x7fff2bdb4fff libGIF.dylib (2130.3.5) <0C91C2A9-5D71-3042-A0D2-AA8F1F09012E> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib\n 0x7fff2bdb5000 - 0x7fff2bdbefff com.apple.CMCaptureCore (1.0 - 80.20.5) <2B7E468B-D901-3EA9-85CF-82FD753785BD> /System/Library/PrivateFrameworks/CMCaptureCore.framework/Versions/A/CMCaptureCore\n 0x7fff2bdbf000 - 0x7fff2be06fff com.apple.print.framework.PrintCore (16 - 531) <DB939B2B-D47D-3035-8C02-01006D21C5A7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore\n 0x7fff2be07000 - 0x7fff2bed3fff com.apple.TextureIO (3.10.9 - 3.10.9) <50BA07A4-02E8-38EE-B0B9-B12C277B563B> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO\n 0x7fff2bed4000 - 0x7fff2bedcfff com.apple.InternationalSupport (1.0 - 60) <DE997943-6AD5-32DA-B48E-78170C1EAA7B> /System/Library/PrivateFrameworks/InternationalSupport.framework/Versions/A/InternationalSupport\n 0x7fff2bedd000 - 0x7fff2bf58fff com.apple.datadetectorscore (8.0 - 674) <A4EBFF22-F861-321A-AF28-1DB8ECB9A4FF> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore\n 0x7fff2bf59000 - 0x7fff2bfb7fff com.apple.UserActivity (435 - 435) <12250395-D660-3CC1-81DB-565340F2651B> /System/Library/PrivateFrameworks/UserActivity.framework/Versions/A/UserActivity\n 0x7fff2bfb8000 - 0x7fff2c723fff com.apple.MediaToolbox (1.0 - 2765.6.4.2) <C8645EA0-643D-38CF-AA88-3253339192B1> /System/Library/Frameworks/MediaToolbox.framework/Versions/A/MediaToolbox\n 0x7fff2cbdd000 - 0x7fff2cc05fff com.apple.locationsupport (2420.12.16 - 2420.12.16) <63AB1284-8E33-3E9D-A857-9370F492B343> /System/Library/PrivateFrameworks/LocationSupport.framework/Versions/A/LocationSupport\n 0x7fff2cc06000 - 0x7fff2cc37fff libSessionUtility.dylib (76.7) <6AAD02A0-9590-3CED-9568-36E05C59AA2B> /System/Library/PrivateFrameworks/AudioSession.framework/libSessionUtility.dylib\n 0x7fff2cc38000 - 0x7fff2cd68fff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <8E53C25F-9FE2-372E-8374-6A598D72C4C1> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox\n 0x7fff2cd69000 - 0x7fff2cdd0fff com.apple.audio.AudioSession (1.0 - 76.7) <F696F4EC-9344-3C85-941E-6E5EF5CEF585> /System/Library/PrivateFrameworks/AudioSession.framework/Versions/A/AudioSession\n 0x7fff2cdd1000 - 0x7fff2cde3fff libAudioStatistics.dylib (25.4) <303533DD-D001-3CE8-A5A4-EC29F464FC3A> /usr/lib/libAudioStatistics.dylib\n 0x7fff2cde4000 - 0x7fff2cdf3fff com.apple.speech.synthesis.framework (9.0.51.2 - 9.0.51.2) <14F3382B-2B8E-31E5-8C73-73F0B8DD05F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis\n 0x7fff2cdf4000 - 0x7fff2ce5ffff com.apple.ApplicationServices.ATS (377 - 516) <3DD60168-A0F3-3388-8DDE-69F81280AE91> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS\n 0x7fff2ce60000 - 0x7fff2ce78fff libresolv.9.dylib (68) <7B043B4A-71CE-3F6E-91F0-CBBED47A9EA9> /usr/lib/libresolv.9.dylib\n 0x7fff2ce79000 - 0x7fff2ce8cfff libsasl2.2.dylib (214) <7EE1EE13-9D86-3612-A6BC-3E6B5D578267> /usr/lib/libsasl2.2.dylib\n 0x7fff2cfab000 - 0x7fff2d08afff libSMC.dylib (20) <B207FDFF-8D80-3800-B968-03C718FFBF3F> /usr/lib/libSMC.dylib\n 0x7fff2d08b000 - 0x7fff2d0eafff libcups.2.dylib (494.1) <CDF6F483-017E-3DED-B107-C50FC3CADD65> /usr/lib/libcups.2.dylib\n 0x7fff2d0eb000 - 0x7fff2d0fafff com.apple.LangAnalysis (1.7.0 - 254) <14703020-3124-3C62-A9DB-6DD28024CD42> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis\n 0x7fff2d0fb000 - 0x7fff2d105fff com.apple.NetAuth (6.2 - 6.2) <D40BF56F-DF5F-3ECB-AAC2-FE6F13E9D120> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth\n 0x7fff2d106000 - 0x7fff2d10dfff com.apple.ColorSyncLegacy (4.13.0 - 1) <F3AEB77A-456F-3F9F-98CC-3E29ABAF5D0C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSyncLegacy.framework/Versions/A/ColorSyncLegacy\n 0x7fff2d10e000 - 0x7fff2d119fff com.apple.QD (4.0 - 416) <F65D0944-C775-33FB-A345-C046789667B7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD\n 0x7fff2d11a000 - 0x7fff2d788fff com.apple.audio.AudioResourceArbitration (1.0 - 1) <6A293E4C-1E2D-36DA-B416-FBED7286CD6E> /System/Library/PrivateFrameworks/AudioResourceArbitration.framework/Versions/A/AudioResourceArbitration\n 0x7fff2d789000 - 0x7fff2d795fff com.apple.perfdata (1.0 - 67.40.1) <A9D2E8CD-9D74-304E-BD99-A7704F3CD38B> /System/Library/PrivateFrameworks/perfdata.framework/Versions/A/perfdata\n 0x7fff2d796000 - 0x7fff2d7a4fff libperfcheck.dylib (41) <5AFDC5C6-EBB6-33E4-9215-1AACE6C6F6EE> /usr/lib/libperfcheck.dylib\n 0x7fff2d7a5000 - 0x7fff2d7b4fff com.apple.Kerberos (3.0 - 1) <02FFA3CA-F8AF-3211-9159-36BC29612650> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos\n 0x7fff2d7b5000 - 0x7fff2d804fff com.apple.GSS (4.0 - 2.0) <5D06022E-C963-390A-9487-90BD1B61BC20> /System/Library/Frameworks/GSS.framework/Versions/A/GSS\n 0x7fff2d805000 - 0x7fff2d815fff com.apple.CommonAuth (4.0 - 2.0) <C4418557-FA52-3B80-804F-2BC7AF760FD6> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth\n 0x7fff2d816000 - 0x7fff2d83cfff com.apple.MobileAssets (1.0 - 659.60.1) <62F25002-C547-3C6C-87D1-0824DD058C82> /System/Library/PrivateFrameworks/MobileAsset.framework/Versions/A/MobileAsset\n 0x7fff2d86a000 - 0x7fff2d88cfff com.apple.security.KeychainCircle.KeychainCircle (1.0 - 1) <6F4B051F-BC33-3880-81B2-5C62DABFF02D> /System/Library/PrivateFrameworks/KeychainCircle.framework/Versions/A/KeychainCircle\n 0x7fff2d88d000 - 0x7fff2d895fff com.apple.CorePhoneNumbers (1.0 - 1) <AA493452-21D3-3EC6-953C-42DBF75F4EB9> /System/Library/PrivateFrameworks/CorePhoneNumbers.framework/Versions/A/CorePhoneNumbers\n 0x7fff2d9ea000 - 0x7fff2d9eafff liblaunch.dylib (2038.80.3) <C7C51322-8491-3B78-9CFA-2B4753662BCF> /usr/lib/system/liblaunch.dylib\n 0x7fff2e1e5000 - 0x7fff2e32cfff com.apple.Sharing (1579 - 1579) <4925CAB3-09C0-373C-A5D3-9BB5FF025A4F> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing\n 0x7fff2e32d000 - 0x7fff2e44dfff com.apple.Bluetooth (8.0.3 - 8.0.3d9) <C6FFFDA7-CD91-339A-8529-7D094338949D> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth\n 0x7fff2e44e000 - 0x7fff2e462fff com.apple.AppContainer (4.0 - 509.60.2) <F294CD92-94FA-3D7D-9E59-AA5544504264> /System/Library/PrivateFrameworks/AppContainer.framework/Versions/A/AppContainer\n 0x7fff2e463000 - 0x7fff2e466fff com.apple.SecCodeWrapper (4.0 - 509.60.2) <1BEC89D6-6AC8-36C2-89AE-41662D14DC50> /System/Library/PrivateFrameworks/SecCodeWrapper.framework/Versions/A/SecCodeWrapper\n 0x7fff2e467000 - 0x7fff2e4c0fff com.apple.ProtectedCloudStorage (1.0 - 1) <88EF8B12-617E-316C-9036-18357E27BC0A> /System/Library/PrivateFrameworks/ProtectedCloudStorage.framework/Versions/A/ProtectedCloudStorage\n 0x7fff2e714000 - 0x7fff2fc0afff com.apple.GeoServices (1.0 - 1757.23.11.29.3) <72B73209-98B3-3E90-8D5D-B69C81784E5D> /System/Library/PrivateFrameworks/GeoServices.framework/Versions/A/GeoServices\n 0x7fff2fc0b000 - 0x7fff2fc16fff com.apple.DirectoryService.Framework (11.2 - 230.40.1) <4DB85BA3-9323-304B-BDC3-6E13B9AAA1C2> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryService\n 0x7fff2fc17000 - 0x7fff2fc42fff com.apple.RemoteViewServices (2.0 - 163) <661A448B-2901-33CD-B13C-362D61AFD998> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices\n 0x7fff2fc43000 - 0x7fff2fc52fff com.apple.SpeechRecognitionCore (6.1.12 - 6.1.12) <B24969AE-43BA-36C2-80F9-2CBBC3F63CC8> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore\n 0x7fff2fc53000 - 0x7fff2fc5afff com.apple.speech.recognition.framework (6.0.3 - 6.0.3) <8C33ECFF-2FBF-30FF-87EA-32A508860543> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition\n 0x7fff2fe9e000 - 0x7fff2fe9efff libsystem_product_info_filter.dylib (8.40.1) <20310EE6-2C3F-361A-9ECA-4223AFC03B65> /usr/lib/system/libsystem_product_info_filter.dylib\n 0x7fff2ff79000 - 0x7fff2ff79fff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <8CD6F55A-8E4F-3653-A367-427D0ED3DD16> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib\n 0x7fff2ffa0000 - 0x7fff2ffa0fff com.apple.CoreServices (1122.11 - 1122.11) <E59859C6-7221-3324-BB58-F910B2199959> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices\n 0x7fff3026e000 - 0x7fff3026efff com.apple.Accelerate (1.11 - Accelerate 1.11) <2423F0F6-A3A4-37AB-971E-FCFC7645D282> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate\n 0x7fff302af000 - 0x7fff302bafff com.apple.MediaAccessibility (1.0 - 130) <264B30DF-646A-30EC-98B6-20429E9718CB> /System/Library/Frameworks/MediaAccessibility.framework/Versions/A/MediaAccessibility\n 0x7fff302bb000 - 0x7fff302dafff com.apple.networking.AlgosScoreFramework (1.0 - 1) <8713D2A4-ECB6-3B96-BE39-F47851EEF900> /System/Library/PrivateFrameworks/AlgosScoreFramework.framework/Versions/A/AlgosScoreFramework\n 0x7fff302db000 - 0x7fff302dffff com.apple.AppleSRP (5.0 - 1) <3BF95CAF-2EC5-393A-95B7-429C0C5F8F13> /System/Library/PrivateFrameworks/AppleSRP.framework/Versions/A/AppleSRP\n 0x7fff302e0000 - 0x7fff302ebfff com.apple.frameworks.CoreDaemon (1.3 - 1.3) <D73E7719-09C8-30E6-B92D-AFC1BB356D92> /System/Library/PrivateFrameworks/CoreDaemon.framework/Versions/B/CoreDaemon\n 0x7fff302ec000 - 0x7fff30323fff com.apple.framework.SystemAdministration (1.0 - 1.0) <9275DC16-B898-326A-B6AD-6CDF34F0CF77> /System/Library/PrivateFrameworks/SystemAdministration.framework/Versions/A/SystemAdministration\n 0x7fff30ae5000 - 0x7fff30b47fff com.apple.CoreBluetooth (1.0 - 1) <B88DEE8B-6268-36BA-BF6C-088F3BD8C652> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth\n 0x7fff30b48000 - 0x7fff30b51fff com.apple.SymptomDiagnosticReporter (1.0 - 79.40.12) <83B5E330-D786-34D2-AEE6-6F7B34D6FE9C> /System/Library/PrivateFrameworks/SymptomDiagnosticReporter.framework/Versions/A/SymptomDiagnosticReporter\n 0x7fff30b52000 - 0x7fff30b65fff com.apple.PowerLog (1.0 - 1) <3A076F54-AE8C-3550-8262-5655B5026489> /System/Library/PrivateFrameworks/PowerLog.framework/Versions/A/PowerLog\n 0x7fff30b66000 - 0x7fff30b72fff com.apple.AppleIDAuthSupport (1.0 - 1) <964BA0DB-E86E-3F81-BB82-CC27184B6D20> /System/Library/PrivateFrameworks/AppleIDAuthSupport.framework/Versions/A/AppleIDAuthSupport\n 0x7fff30b73000 - 0x7fff30c1bfff com.apple.DiscRecording (9.0.3 - 9030.4.5) <2B9AA549-63FD-36BB-AE05-ABD5DAC41279> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording\n 0x7fff30c1c000 - 0x7fff30c4ffff com.apple.MediaKit (16 - 927.40.2) <D1056292-E38F-313F-B202-EFD871195729> /System/Library/PrivateFrameworks/MediaKit.framework/Versions/A/MediaKit\n 0x7fff30c50000 - 0x7fff30d3bfff com.apple.DiskManagement (14.0 - 1733.80.1) <9281E3F8-EAFE-3367-B7D5-23687AA6EB70> /System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/DiskManagement\n 0x7fff30d3c000 - 0x7fff310f6fff com.apple.CoreAUC (322.2.0 - 322.2.0) <DAE981E0-5FED-39FD-8443-BD91D6957901> /System/Library/PrivateFrameworks/CoreAUC.framework/Versions/A/CoreAUC\n 0x7fff310f7000 - 0x7fff310fafff com.apple.Mangrove (1.0 - 25) <61919815-50C9-3358-836F-B81ED66CCD84> /System/Library/PrivateFrameworks/Mangrove.framework/Versions/A/Mangrove\n 0x7fff310fb000 - 0x7fff31128fff com.apple.CoreAVCHD (6.1.0 - 6100.4.1) <B123866C-3945-37E7-92EF-BE36AEDD620D> /System/Library/PrivateFrameworks/CoreAVCHD.framework/Versions/A/CoreAVCHD\n 0x7fff31129000 - 0x7fff31249fff com.apple.FileProvider (326.3 - 326.3) <C5007E6E-897B-308F-B173-4F5C6BF3968D> /System/Library/Frameworks/FileProvider.framework/Versions/A/FileProvider\n 0x7fff3124a000 - 0x7fff3126dfff com.apple.GenerationalStorage (2.0 - 322) <974A1465-7AA4-347E-8606-CF35160FFA92> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage\n 0x7fff31ac0000 - 0x7fff31afffff com.apple.AppleVPAFramework (3.21.1 - 3.21.1) <4E96F781-3689-3086-9DF3-60F20487FB9E> /System/Library/PrivateFrameworks/AppleVPA.framework/Versions/A/AppleVPA\n 0x7fff31bd0000 - 0x7fff31c0cfff com.apple.DebugSymbols (195.1 - 195.1) <12A5A6E2-6C84-3FCA-9927-8B9E241C607F> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols\n 0x7fff31c0d000 - 0x7fff31ccafff com.apple.CoreSymbolication (12.2 - 64541.4) <F1A41B4E-671A-335E-8AE0-B99688F255C8> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication\n 0x7fff31ccb000 - 0x7fff31cd4fff com.apple.CoreTime (284) <D80E792D-33D1-3D07-B39F-F0A1A7F74E24> /System/Library/PrivateFrameworks/CoreTime.framework/Versions/A/CoreTime\n 0x7fff32b61000 - 0x7fff32bc4fff com.apple.framework.Apple80211 (17.0 - 1728) <A62689A7-7C22-33B3-90FA-730E4AAEE5B5> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211\n 0x7fff32bc5000 - 0x7fff32d17fff com.apple.CoreWiFi (3.0 - 341) <F3D8F158-611A-3A5E-9F1D-E5FC273A4C74> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi\n 0x7fff32d31000 - 0x7fff32d68fff com.apple.LDAPFramework (2.4.28 - 194.5) <246874E6-4FD1-35A5-A039-4141999D8CD6> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP\n 0x7fff32d69000 - 0x7fff32d6afff com.apple.TrustEvaluationAgent (2.0 - 35) <6FEF60A0-F80F-34E3-8845-FEEC92840920> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent\n 0x7fff32d6b000 - 0x7fff32e6efff libcrypto.44.dylib (56.60.2) <7D8D4B1B-625D-3D00-A626-C21AFEE0462E> /usr/lib/libcrypto.44.dylib\n 0x7fff32e6f000 - 0x7fff32e9cfff libssl.46.dylib (56.60.2) <E02ED3C9-4956-39C4-AF0A-B541EEDD3F1B> /usr/lib/libssl.46.dylib\n 0x7fff32e9d000 - 0x7fff32f4cfff com.apple.DiskImagesFramework (595.40.1 - 595.40.1) <3139EC22-A8F2-3F26-8953-7961C97E7CEF> /System/Library/PrivateFrameworks/DiskImages.framework/Versions/A/DiskImages\n 0x7fff32f84000 - 0x7fff32f93fff com.apple.xpc.RemoteServiceDiscovery (1.0 - 2038.80.3) <78AF1606-37D8-3424-92AE-071A9F43AA0F> /System/Library/PrivateFrameworks/RemoteServiceDiscovery.framework/Versions/A/RemoteServiceDiscovery\n 0x7fff32f94000 - 0x7fff32fabfff com.apple.xpc.RemoteXPC (1.0 - 2038.80.3) <C4BFF5FC-FC9C-3161-9612-7070EDAE9989> /System/Library/PrivateFrameworks/RemoteXPC.framework/Versions/A/RemoteXPC\n 0x7fff32ff3000 - 0x7fff32ff6fff com.apple.help (1.3.8 - 71) <6074D81C-4507-35A6-88D7-D82309F81587> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help\n 0x7fff32ff7000 - 0x7fff32ffefff com.apple.EFILogin (2.0 - 2) <B06CCD1C-A4D1-34D2-89C5-0DB69FE65234> /System/Library/PrivateFrameworks/EFILogin.framework/Versions/A/EFILogin\n 0x7fff32fff000 - 0x7fff3300afff libcsfde.dylib (554) <9CDB9580-DD1C-347E-91C5-6D92D96F52F5> /usr/lib/libcsfde.dylib\n 0x7fff3300b000 - 0x7fff33070fff libcurl.4.dylib (121.40.2) <77010EA9-4AD1-3F4A-B3EF-2FFE739FB349> /usr/lib/libcurl.4.dylib\n 0x7fff33071000 - 0x7fff33078fff com.apple.LoginUICore (4.0 - 4.0) <7225326A-7704-362D-B64E-4ABF4A221F88> /System/Library/PrivateFrameworks/LoginUIKit.framework/Versions/A/Frameworks/LoginUICore.framework/Versions/A/LoginUICore\n 0x7fff33238000 - 0x7fff33238fff com.apple.ApplicationServices (48 - 50) <42B48E32-1918-3178-8DE0-E8126B9EC088> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices\n 0x7fff33539000 - 0x7fff33539fff libHeimdalProxy.dylib (79) <85526E13-1E48-377A-A700-EE3F5648A6E3> /System/Library/Frameworks/Kerberos.framework/Versions/A/Libraries/libHeimdalProxy.dylib\n 0x7fff335ec000 - 0x7fff335ecfff com.apple.audio.units.AudioUnit (1.14 - 1.14) <8CF768B8-836B-3DA8-9F0A-8CF840348202> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit\n 0x7fff33611000 - 0x7fff33653fff com.apple.StreamingZip (1.0 - 1) <157C7AC0-9F73-3FF5-A276-54EC3CAE958A> /System/Library/PrivateFrameworks/StreamingZip.framework/Versions/A/StreamingZip\n 0x7fff33696000 - 0x7fff3369bfff com.apple.PushKit (1.0 - 1) <4D0A6539-611C-3B9C-A67D-D45CDEEC8CDC> /System/Library/Frameworks/PushKit.framework/Versions/A/PushKit\n 0x7fff3369c000 - 0x7fff336d2fff com.apple.C2 (1.3 - 569) <817D8F9D-1801-3E6D-846A-7002174B59CB> /System/Library/PrivateFrameworks/C2.framework/Versions/A/C2\n 0x7fff33705000 - 0x7fff33f12fff com.apple.vision.EspressoFramework (1.0 - 256.2.2) <70E23334-A179-3671-A930-A7AB9EC77BDD> /System/Library/PrivateFrameworks/Espresso.framework/Versions/A/Espresso\n 0x7fff33f13000 - 0x7fff33f2afff com.apple.ANEServices (4.52 - 4.52) <50EF6199-93EF-3227-B64A-313BC1DF41AE> /System/Library/PrivateFrameworks/ANEServices.framework/Versions/A/ANEServices\n 0x7fff342c7000 - 0x7fff3458afff com.apple.spotlight.index (10.7.0 - 2150.7.5) <0056D8F9-D6CF-3586-974C-80902DF8952A> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/SpotlightIndex\n 0x7fff345a3000 - 0x7fff345f3fff com.apple.ChunkingLibrary (334 - 334) <CBEBDC8A-CCE4-3A21-915C-D2F3FB20B900> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary\n 0x7fff34ebf000 - 0x7fff34ed5fff com.apple.CoreML.AppleNeuralEngine (1.0 - 1) <A2E78405-4382-3A23-8638-56E1A5D14543> /System/Library/PrivateFrameworks/AppleNeuralEngine.framework/Versions/A/AppleNeuralEngine\n 0x7fff3503b000 - 0x7fff3503efff com.apple.Cocoa (6.11 - 23) <B0F6AF8E-B85C-3C5C-9812-9CD8BC07ADB2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa\n 0x7fff36482000 - 0x7fff3649dfff com.apple.openscripting (1.7 - 190) <E3815884-A406-3CF6-82C1-BEDC772A9081> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting\n 0x7fff3649e000 - 0x7fff364a1fff com.apple.securityhi (9.0 - 55008) <F7E1C957-65AF-39E5-8BBA-9D7C7C9D30B6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI\n 0x7fff364a2000 - 0x7fff364a5fff com.apple.ink.framework (10.15 - 227) <E3D118A5-7A62-3893-ADAC-E0A9F45314C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink\n 0x7fff364a6000 - 0x7fff364a9fff com.apple.CommonPanels (1.2.6 - 101) <F46676FA-60F3-30CC-BF48-F5BB6E66E576> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels\n 0x7fff364aa000 - 0x7fff364b1fff com.apple.ImageCapture (1708.1 - 1708.1) <AC709D2F-7C16-3645-BB20-19DD1414E210> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture\n 0x7fff3949f000 - 0x7fff394a2fff com.apple.OSAServicesClient (1.0 - 1) <201350F5-56C4-3342-AD10-4BE20772C52B> /System/Library/PrivateFrameworks/OSAServicesClient.framework/Versions/A/OSAServicesClient\n 0x7fff3c090000 - 0x7fff3c24bfff libFosl_dynamic.dylib (200) <83EE0261-E5F6-3607-8897-B03B2B954B15> /usr/lib/libFosl_dynamic.dylib\n 0x7fff3d1a8000 - 0x7fff3d1abfff com.apple.print.framework.Print (15 - 271) <F3F40AFD-1743-34E6-8BD3-6A577E3BD590> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print\n 0x7fff3d1ac000 - 0x7fff3d1affff com.apple.Carbon (160 - 164) <7395C7E9-AE3B-3547-8773-4F3A70B241AA> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon\n 0x7fff3d434000 - 0x7fff3d453fff com.apple.private.SystemPolicy (1.0 - 1) <29F5E3FE-CF12-3242-9FD3-4950DA38E4D0> /System/Library/PrivateFrameworks/SystemPolicy.framework/Versions/A/SystemPolicy\n 0x7fff3d600000 - 0x7fff3d61dfff com.apple.sidecar-core (1.0 - 228) <78195DB7-D409-3B46-B8C8-3B70538D3CDC> /System/Library/PrivateFrameworks/SidecarCore.framework/Versions/A/SidecarCore\n 0x7fff3dd7d000 - 0x7fff3dd88fff com.apple.MallocStackLogging (1.0 - 1) <507894FA-6738-372B-9A10-C38AFC9DA079> /System/Library/PrivateFrameworks/MallocStackLogging.framework/Versions/A/MallocStackLogging\n 0x7fff3dd9e000 - 0x7fff3ddb0fff libmis.dylib (274.60.2) <6C720DC2-E50E-3A8D-8494-F8C007DF8DF4> /usr/lib/libmis.dylib\n 0x7fff3ddb1000 - 0x7fff3ddb4fff com.apple.gpusw.GPURawCounter (17.3 - 12.0) <070CF9B7-EE89-39F3-B0F6-26D4974AD3A8> /System/Library/PrivateFrameworks/GPURawCounter.framework/Versions/A/GPURawCounter\n 0x7fff3e2c0000 - 0x7fff3e2d1fff com.apple.sidecar-ui (1.0 - 228) <E0B4A84C-7E8D-338B-8269-DAA5AE1ED094> /System/Library/PrivateFrameworks/SidecarUI.framework/Versions/A/SidecarUI\n 0x7fff4153a000 - 0x7fff41569fff libncurses.5.4.dylib (57) <CAD79205-84C0-3731-AED8-EDEF51ACC872> /usr/lib/libncurses.5.4.dylib\n 0x7fff4156a000 - 0x7fff41573fff com.apple.IOAccelMemoryInfo (1.0 - 1) <544B95BE-810E-3D94-AEB1-D5C117D946D7> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo\n 0x7fff419aa000 - 0x7fff419c8fff libCGInterfaces.dylib (544.2) <2BC461CE-B7FA-33F3-A36B-64F54FB371B5> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib\n 0x7fff43fb8000 - 0x7fff44231fff com.apple.RawCamera.bundle (9.10.0 - 1430) <3E7403EB-156C-36C7-93AD-1356447D5310> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera\n 0x7fff46cb9000 - 0x7fff46cc4fff libGPUSupportMercury.dylib (18.1.1) <1321060E-8F56-3917-8F4D-510A4DB45798> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib\n 0x7fff48327000 - 0x7fff48376fff com.apple.osanalytics.OSAnalytics (1.0 - 1) <CADD88A2-87A8-3879-8759-D3C112A6844F> /System/Library/PrivateFrameworks/OSAnalytics.framework/Versions/A/OSAnalytics\n 0x7fff4c3d2000 - 0x7fff4c3d5fff com.apple.FinderSyncPriv (1.3 - 1350.2.10) <121C1E64-B0BE-389F-A35D-DD44D84129E8> /System/Library/PrivateFrameworks/FinderSyncPriv.framework/Versions/A/FinderSyncPriv\n 0x7fff522ff000 - 0x7fff52391fff com.apple.Symbolication (12.2 - 64541.7.1) <FA39B702-6E08-3F11-953F-5EC1EFB993BB> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication\n 0x7fff564d5000 - 0x7fff564d8fff com.apple.ForceFeedback (1.0.6 - 1.0.6) <8782199E-5556-3FB6-87E8-03472B480BAA> /System/Library/Frameworks/ForceFeedback.framework/Versions/A/ForceFeedback\n 0x7fff5eada000 - 0x7fff5ef6afff com.apple.driver.AppleIntelKBLGraphicsMTLDriver (16.1.12 - 16.0.1) <2B7EEE40-F4BD-32CD-B5A3-51F67B57AA69> /System/Library/Extensions/AppleIntelKBLGraphicsMTLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsMTLDriver\n 0x7fff5ef6b000 - 0x7fff5f97efff libSC.dylib (4.2.15) <86667FD2-E9BB-39FE-82E9-7B1F0230A922> /System/Library/Extensions/AMDShared.bundle/Contents/PlugIns/libSC.dylib\n 0x7fff5fcc7000 - 0x7fff60caafff com.apple.driver.AppleIntelKBLGraphicsGLDriver (16.1.12 - 16.0.1) <7E0C9E81-E41B-3D24-AB0B-84295B61FADF> /System/Library/Extensions/AppleIntelKBLGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelKBLGraphicsGLDriver\n 0x7fff6a490000 - 0x7fff6a494fff libmetal_timestamp.dylib (31001.161) <DF0A6F36-E486-3656-A6F2-9BA9A0CF2159> /System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/31001/Libraries/libmetal_timestamp.dylib\n 0x7fff6c8fe000 - 0x7fff6c904fff libCoreFSCache.dylib (177.22) <44489BD1-3963-35DF-86F1-DE95778AC0DB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib\n 0x7fff6c905000 - 0x7fff6c909fff libCoreVMClient.dylib (177.22) <989F6CBF-CCEF-340D-9CB5-EC4133707040> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib\n 0x7fff6c90a000 - 0x7fff6c919fff com.apple.opengl (18.1.1 - 18.1.1) <F70AF1B3-D17A-3A0E-A8AC-9D45C5B52BA9> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL\n 0x7fff6c91a000 - 0x7fff6c91cfff libCVMSPluginSupport.dylib (18.1.1) <AF77D964-9A4C-3690-AF62-4E05825DC9BF> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib\n 0x7fff6c91d000 - 0x7fff6c925fff libGFXShared.dylib (18.1.1) <45A1FFDC-03B7-3D64-AFAF-16D321B53D28> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib\n 0x7fff6c926000 - 0x7fff6c959fff libGLImage.dylib (18.1.1) <16D10CE1-C2A1-3E24-A617-766CB6E9133C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib\n 0x7fff6c95a000 - 0x7fff6c996fff libGLU.dylib (18.1.1) <F0DD35B5-3692-3BE5-AD3D-4F6B237EF6AD> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib\n 0x7fff6c997000 - 0x7fff6cb2bfff libGLProgrammability.dylib (18.1.1) <F8A8DACC-1932-3DEF-A269-396E4981B4D0> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib\n 0x7fff6cb2c000 - 0x7fff6cb36fff libGL.dylib (18.1.1) <68ABAADE-2DB4-3412-9F36-CA1AEAC8E9F6> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib\n 0x7fff6cb37000 - 0x7fff6ccb2fff GLEngine (18.1.1) <2C9F1F38-F0CA-3416-9A6E-C0E3F40C3AAC> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine\n 0x7fff6ccb3000 - 0x7fff6ccdcfff GLRendererFloat (18.1.1) <A66AB383-EE4C-325C-8115-78F2B3FFECC7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat\n 0x7fff6df6d000 - 0x7fff6dfc5fff com.apple.opencl (4.5 - 4.5) <40B70A3B-D981-3E4A-9BEC-F22EF84118F5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL\n 0x7fff6eee8000 - 0x7fff6ef37fff ATIRadeonX6000SCLib.dylib (4.2.15) <E3B416D3-3876-3218-A68F-A745B103F160> /System/Library/Extensions/AMDRadeonX6000GLDriver.bundle/Contents/MacOS/ATIRadeonX6000SCLib.dylib\n 0x7fff6f857000 - 0x7fff6f879fff com.apple.audio.OpenAL (1.8 - 1.8) <43D5D99A-39C3-30F3-BB9E-5B83EEA9DAFD> /System/Library/Frameworks/OpenAL.framework/Versions/A/OpenAL\n 0x7fff78132000 - 0x7fff78139fff libRosetta.dylib (203.30) <44C477D9-013F-3A6D-A9FE-68A89214E6A5> /usr/lib/libRosetta.dylib\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 4\n thread_create: 0\n thread_set_state: 0\n Calls made by this process:\n task_for_pid: 0\n thread_create: 0\n thread_set_state: 0\n Calls made by all processes on this machine:\n task_for_pid: 55959\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.0G resident=0K(0%) swapped_out_or_unallocated=1.0G(100%)\nWritable regions: Total=8.8G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8.8G(100%)\n \n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 512K 4 \nActivity Tracing 256K 1 \nCG backing stores 3456K 6 \nCG image 1180K 10 \nCoreAnimation 84K 9 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreServices 36K 1 \nCoreUI image data 904K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 6.8G 341 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.5G 16 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 164K 41 \nStack 73.8M 42 \nVM_ALLOCATE 92.1M 777 \n__CTF 759 1 \n__DATA 89.4M 371 \n__DATA_CONST 17.6M 215 \n__DATA_DIRTY 918K 116 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 545.7M 25 \n__OBJC_RO 60.5M 1 \n__OBJC_RW 2449K 2 \n__TEXT 461.6M 370 \n__UNICODE 588K 1 \nmapped file 260.7M 39 \nshared memory 40K 4 \n=========== ======= ======= \nTOTAL 10.2G 2421 \nTOTAL, minus reserved VM space 8.3G 2421 \n\nModel: MacBookPro16,1, BootROM 1554.80.3.0.0 (iBridge: 18.16.14347.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC \nGraphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin\nGraphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -\nAirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Sep 11 2020 17:01:15 version 9.30.440.2.32.5.61 FWID 01-1d69e4b4\nBluetooth: Version 8.0.3d9, 3 services, 25 devices, 1 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB 3.1 Bus\nUSB Device: USB Receiver\nUSB Device: Apple T2 Bus\nUSB Device: Composite Device\nUSB Device: Touch Bar Backlight\nUSB Device: Touch Bar Display\nUSB Device: Apple Internal Keyboard / Trackpad\nUSB Device: Headset\nUSB Device: Ambient Light Sensor\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: Apple T2 Controller\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\nThunderbolt Bus: MacBook Pro, Apple Inc., 63.5\n```\n\n- Random\n" ]

[ "Crash on startup\nOS: Windows 7 Home Premium (64Bit)\nCPU: Intel Core i5-4670K (3.40GHz)\nMainboard: Gigabyte Technology Co. Ltd. H87-HD3\nRAM: 8GB DDR3 Dual-Channel\nGPU: Nvidia GeForce GTX 660 TI (Treiber: 347.88)\nResolution: 1920x1080 (60Hz)\nPython: 2.7 and 3.4\nDisplay: Terra LCD/LED\nSystempath(%path%): C:\\ProgramData\\Oracle\\Java\\javapath;C:\\Program Files (x86)\\NVIDIA Corporation\\Ph\nysX\\Common;C:\\Program Files (x86)\\Intel\\iCLS Client\\;C:\\Program Files\\Intel\\iCLS\n Client\\;C:\\Windows\\system32;C:\\Windows;C:\\Windows\\System32\\Wbem;C:\\Windows\\Syst\nem32\\WindowsPowerShell\\v1.0\\;C:\\Program Files\\Intel\\Intel(R) Management Engine C\nomponents\\DAL;C:\\Program Files\\Intel\\Intel(R) Management Engine Components\\IPT;C\n:\\Program Files (x86)\\Intel\\Intel(R) Management Engine Components\\DAL;C:\\Program\n Files (x86)\\Intel\\Intel(R) Management Engine Components\\IPT;C:\\Program Files (x\n86)\\Intel\\OpenCL SDK\\3.0\\bin\\x86;C:\\Program Files (x86)\\Intel\\OpenCL SDK\\3.0\\bin\n\\x64;C:\\Program Files\\Java\\jdk1.7.0_45\\bin;C:\\Program Files\\OpenVPN\\bin;C:\\Progr\nam Files\\Java\\jre7\\bin;C:\\Python27;C:\\Python34;C:\\Program Files (x86)\\Mikero\\DeP\nboTools\\bin;C:\\Program Files (x86)\\Skype\\Phone\\;C:\\Program Files (x86)\\Steam\\Ste\namApps\\common\\GarrysMod\\garrysmod\\..\\bin\n\n\nBroken: 2.74(Installer);2.74(ZIP);2.72(Installer);2.72(ZIP);2.73(Installer)\nWorked: Every Version I tried didn't work\n\nAfter executing blender:\nConsole opens\nBlender Window opens and immediately closes.\n\nI tried it with a Ubuntu VM(VirtualBox):\nIt worked\n\nI got a crash report in %appdata%\\Local\\Temp\\blender.crash.txt\n\nHere is its content:\n\n# Blender 2.74 (sub 0), Commit date: 2015-03-31 13:39, Hash 000dfc0\n\n# backtrace\n99: PyInit_mathutils_noise_types - 0x40429230\n98: fftw_plan_many_dft - 0x3F7B47B0\n97: fftw_plan_many_dft - 0x3F7B47B0\n96: fftw_plan_many_dft - 0x3F7B47B0\n95: UnhandledExceptionFilter - 0x779B9220\n94: MD5Final - 0x77AD3950\n93: _C_specific_handler - 0x77A550AC\n92: RtlCompareUnicodeString - 0x77A754D0\n91: RtlTimeToSecondsSince1970 - 0x77A556F0\n90: KiUserExceptionDispatcher - 0x77A8FE1A\n89: log - 0xED7E28F0\n88: PyMapping_Length - 0x1D662B80\n87: PyMapping_Length - 0x1D662B80\n86: PyMapping_Length - 0x1D662B80\n85: PyMapping_Length - 0x1D662B80\n84: PyMapping_Length - 0x1D662B80\n83: PyMapping_Length - 0x1D662B80\n82: PyMapping_Length - 0x1D662B80\n81: PyMapping_Length - 0x1D662B80\n80: PyMapping_Length - 0x1D662B80\n79: PyMapping_Length - 0x1D662B80\n78: PyMapping_Length - 0x1D662B80\n77: PyMapping_Length - 0x1D662B80\n76: PyMapping_Length - 0x1D662B80\n75: PyMapping_Length - 0x1D662B80\n74: PyMapping_Length - 0x1D662B80\n73: PyMapping_Length - 0x1D662B80\n72: PyMapping_Length - 0x1D662B80\n71: PyMapping_Length - 0x1D662B80\n70: PyMapping_Length - 0x1D662B80\n69: PyMapping_Length - 0x1D662B80\n68: PyMapping_Length - 0x1D662B80\n67: PyMapping_Length - 0x1D662B80\n66: PyMapping_Length - 0x1D662B80\n65: PyMapping_Length - 0x1D662B80\n64: PyMapping_Length - 0x1D662B80\n63: PyMapping_Length - 0x1D662B80\n62: PyMapping_Length - 0x1D662B80\n61: PyMapping_Length - 0x1D662B80\n60: PyMapping_Length - 0x1D662B80\n59: PyMapping_Length - 0x1D662B80\n58: PyMapping_Length - 0x1D662B80\n57: PyMapping_Length - 0x1D662B80\n56: PyMapping_Length - 0x1D662B80\n55: PyMapping_Length - 0x1D662B80\n54: PyMapping_Length - 0x1D662B80\n53: PyMapping_Length - 0x1D662B80\n52: PyMapping_Length - 0x1D662B80\n51: PyMapping_Length - 0x1D662B80\n50: PyMapping_Length - 0x1D662B80\n49: PyMapping_Length - 0x1D662B80\n48: PyMapping_Length - 0x1D662B80\n47: PyMapping_Length - 0x1D662B80\n46: PyMapping_Length - 0x1D662B80\n45: PyMapping_Length - 0x1D662B80\n44: PyMapping_Length - 0x1D662B80\n43: PyMapping_Length - 0x1D662B80\n42: PyMapping_Length - 0x1D662B80\n41: PyMapping_Length - 0x1D662B80\n40: PyMapping_Length - 0x1D662B80\n39: PyMapping_Length - 0x1D662B80\n38: PyMapping_Length - 0x1D662B80\n37: PyMapping_Length - 0x1D662B80\n36: PyMapping_Length - 0x1D662B80\n35: PyMapping_Length - 0x1D662B80\n34: PyMapping_Length - 0x1D662B80\n33: PyMapping_Length - 0x1D662B80\n32: PyMapping_Length - 0x1D662B80\n31: PyMapping_Length - 0x1D662B80\n30: PyMapping_Length - 0x1D662B80\n29: PyMapping_Length - 0x1D662B80\n28: PyMapping_Length - 0x1D662B80\n27: PyMapping_Length - 0x1D662B80\n26: PyMapping_Length - 0x1D662B80\n25: PyMapping_Length - 0x1D662B80\n24: PyMapping_Length - 0x1D662B80\n23: PyMapping_Length - 0x1D662B80\n22: PyMapping_Length - 0x1D662B80\n21: PyMapping_Length - 0x1D662B80\n20: PyMapping_Length - 0x1D662B80\n19: PyMapping_Length - 0x1D662B80\n18: PyMapping_Length - 0x1D662B80\n17: PyMapping_Length - 0x1D662B80\n16: PyMapping_Length - 0x1D662B80\n15: PyMapping_Length - 0x1D662B80\n14: PyMapping_Length - 0x1D662B80\n13: PyMapping_Length - 0x1D662B80\n12: PyMapping_Length - 0x1D662B80\n11: PyMapping_Length - 0x1D662B80\n10: PyMapping_Length - 0x1D662B80\n9: PyMapping_Length - 0x1D662B80\n8: PyMapping_Length - 0x1D662B80\n7: PyMapping_Length - 0x1D662B80\n6: PyMapping_Length - 0x1D662B80\n5: PyMapping_Length - 0x1D662B80\n4: PyMapping_Length - 0x1D662B80\n3: PyMapping_Length - 0x1D662B80\n2: PyMapping_Length - 0x1D662B80\n1: PyMapping_Length - 0x1D662B80\n0: PyMapping_Length - 0x1D662B80\n\n\n" ]

[ "Window title shows unsaved indicator while loading\nOperating system: Linux-4.15.0-45-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: May 18 2021, hash: `1f9eb7e2c6`\n\nWhile Blender loads a file, the window title shows the unsaved indicator: `Blender* [/path/to/blend]`.\n\n- Create a .blend file which takes long to load. A simple example involves creating huge amounts of geometry with Array modifier, then applying the modifier.\n- Open the startup file (ctrl+N) so the window title is cleared (makes it easier to see what changes, but not required).\n- Open the .blend you created earlier, you will see the unsaved indicator in the title until loading finished.\n\n", "Dynamic Paint doesn't update to original values on start frame\nOperating system: win10 64\n\nBroken: 2.81\n\nAdd *Dynamic Paint (Canvas)* to any mesh and try to set 0 as a start frame of simulation.\n\n1. Open file and see how Displace modifer doesn't affect mesh\n2. Run animation -> bake current cache\n3. First problem: see how weight is empty at the mesh origin (Displace modifier works except begining of animation)\n4. Second problem: return to frame 0 -> weight doesn't updated to original values (Displace modifier still active on vertex group)\n\n[dyn_paint.blend](dyn_paint.blend)", "Boolean Exact Mode failing\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: 3.5.0 - 3.6.0\nWorked: Unknown.\n\nIn the attached `v8 bug daily.blend` file, an object mysteriously vanishes at frame 36, then reappears in frame 37. Changing various minor things makes the problem go away.\n\nThat file uses a simple armature to animate the rotation of the \"Rotor\" object. \n\nIf you change the end frame of the animation from 60 to 61 and move the last keyframe from frame 61 to frame 62--i.e., stretch out the animation just a little bit--the problem goes away.\n\n- Open the [Boolean_exact_difference__bug.blend](attachment) file\n- Enable the boolean modifier\nor \n- Open the [v8 bug daily 03b.blend](107388#:~:text=Save-,v8%20bug%20daily%2003b.blend,-1006%20KiB) file\n- Go to frame 36", "Causing other objects to be named .001 doesn't immediately update the Viewport Name Display\nI found this in 3.0.0 but happens the same in 3.1.0.\n\nWhen you turn on Viewport Name Display:\n\n\nAnd then you rename a new object the same as object that was already in the scene:\n\n\nThe name of the original doesn't update until you somehow \"touch\" the object by moving it, entering Edit Mode etc.\n\nIt doesn't get fixed by simply affecting something else.\n\nIn the .blend you need to select the object with name \"Plane.001\" and rename it to \"Plane\" then the object on the left stays named as Plane until you somehow affect it.\n[Bug-ViewportDisplayName.blend](Bug-ViewportDisplayName.blend)", "Knife Tool: incorrect interaction with Array modifier when the Merge \"First Last\" option is set\nOperating system: Win10\nGraphics card: nVidia 1070\n\nBroken: 2.80 (sub 44), branch: master, commit date: 2019-02-14 04:22, hash: caa8e7ff2894\nWorked: not sure\n\nWhen the Merge First Last option is set for an Array modifier, it seems like hidden, virtual geometry is picked up while using the knife tool to cut across the surface of the primary shape.\n\nThis results in an improper cut.\n\nBad in-progress cut:\n\n\nBad confirmed cut: \n\n\nGood cut -- with the First Last option turned off:\n\n\n[array-bug.blend](array-bug.blend)\n- Create a simple shape and array it in a radial fashion so that the first/last vertices of the shape are eligible for merge\n - Or just load the attached .blend\n\n- Attempt to make a cut across the main shape with the Merge First Last option set\n- Notice that the cut line is picking up some hidden edges somehow -- perhaps due to triangulation?\n- Confirm the cut and notice it's still incorrect and pretty weird", "Gesture selection does not deselect on nothing if collection is hidden\nOperating system: Linux-6.4.8-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.37 64 Bits, X11 UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.8-gentoo) AMD 4.6 (Core Profile) Mesa 23.3.0-devel (git-57b0db63e1)\n\nBroken: version: 4.0.0 Alpha\nWorked:\n\nThis is an inconsistency in the selection behavior.\nIf you select on nothing, it will deselect all objects in the viewport and the outliner. This is the case for click selection and selection tools/operators.\n\nBut if selected objects are hidden, they are not affected by this with selection tools (gesture selections such as box & lasso). Selected objects and collections stay selected in the outliner.\nThe expected behavior is that gesture selection and single click selection have the same effect on hidden objects and collections.\n\n1. Create two collections each with an object in it\n2. Select a collection and its object in the outlliner\n3. Select on empty space (Notice how the object and collection are deselected)\n4. Repeat 1 & 2\n5. Do a lasso/box selection on empty space (Notice how the outliner selection isn't cleared)\n\n", "Object drivers driven by outliner visibility not updating automatically\nOperating system: Windows 10\nGraphics card: GTX 1060 6gb\n\nBroken: 2.90.0-874af5301cdf (June 20)\n\n\nDrivers on object modifiers that are driven by outliner settings (Hide in viewport, hide in render, etc.) won't work when toggling said outliner settings and has to be forced manually with Update Dependencies.\n\n\n\n\n\n\n - Have 2 cubes in a scene, Cube 1 and Cube 2.\n - Add a modifier on Cube 2 (In my case, a mask, in which Cube 2 is subdivided twice and has a vertex group)\n - Add a driver on the Realtime button on said mask modifier.\n - Have it be driven by Cube 1's \"Disable in Viewports\" button with the following settings:\n\n\nSingle Property\nProperty: Object Cube 1\nPath: hide_viewport\n\n\n\n 6. Disabling Cube_1 from the viewport in the Outliner will not enable the driver on Cube_2's mask modifier.\n 7. Updating Dependencies in the driver editor will correct this.\n\n\n\nAfter updating dependency, enabling Cube_1 will disable the mask in the viewport, although the mask is still enabled in the modifier tab. Clicking once in the viewport will correct this.\n\nExample .Blend File \n[BrokenDriverTest.blend](BrokenDriverTest.blend)", "Problem with parent_vertices attribute\nOperating system: Microsoft Windows 10 Professionnel\nGraphics card: Nvidia Gefroce RTX 2080 Super\n\nBlender 3.0.0, hash: f1cca3055776 , branch: master\n\n**Short description of the bug**\nThe attributes parent_vertices is by default to [0,0,0] but it cause some problem :\nWhen you select the 0th vertex of a mesh and parent an other object with the vertex_parent_set() function the list still be the same [0,0,0].\nSo when the parent mesh is deleted you cannot know if there were a parent before. \nMaybe set the default list to [None, None, None] will avoid the problem.\n", "Dynamic vertex groups (Dynamic Paint, Weight Proximity modifier, Geometry Nodes, ...) do not update density of particles in viewport display\nOperating system: windows 10\nGraphics card: Quadro M620\n\nBroken: 2.90\nWorked: Never\n\nI want to use my dynamic vertex group to generate particles on a plane.\nIt just works when I change parameters during the playback but it's not realtime when I hit play.\n\n- Open attached file\n- Play animation\n- Change any property of the particle during the playback\n[dynamic_paint_test.blend](dynamic_paint_test.blend)", "Library overrides does not work well with Materials.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.3.1 Release Candidate\nWorked: No\n\nAfter saving and reloading, the object's material changes unexpectedly.\nThis bug only appears on objects that have library overrides.\n\n\n**Exact steps for others to reproduce the error**[bug check.zip](bug_check.zip)\n\n1. Download bug check.zip\n2. Open the t2.blend file. You can see that the cube contains red and green.\n3. Then select mat2a in the material list and save it as t4.blend.\n4. Reload t4.blend, and the cube is only red.\n\nMy current bypassing method:\nBefore saving, choose the same material slot as t1.blend. Only in this way can the object's material do not turn into another.\n\nt1.blend is the original data.\nt2.blend is a link of t1.blend, and then replace the data material to the object material.\nt3.blend is wrong, just like the t4.blend you get.\n\n", "Modifier are still evaluated even when not required.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.0.0\nWorked: never\n\nModifiers are evaluated, even when blank, for example a lattice modifier without any lattice, would still make depth graph calculation or something like that, that make each action (select, move, rotate, etc.) verry slower.\n\nCreate/ import a large object (60M poly mesh for example).\nAdd lattice modifier, let all option blank. \nDisable viewport visibility of this modifier.\nTry to move/rotate/scale the object in the viewport, the performance is really low.\n\nIn order to transform your mesh, you need to remove all modifiers, and add then back once transform is convenient.\n", "Properties window's tool settings don't update if UI is loaded without header.\nOperating system: macOS 12.0.1\nGraphics card: M1 Macbook Pro\n\nBroken: 2.93.5 (2.93.5 2021-10-06)\n\nI have my startup file set to hide the header in the properties window, and noticed that the Tool Settings tab does not update to show the current tool unless hovered over with the cursor. It updates on tool changes once the header is shown again, and continues to work (even without the header) until the UI is loaded again on opening a file or restarting Blender. \n\n- Open default file\n- In properties tab: {nav Right Click > Uncheck Show Header option}\n- Switch to Active tool and workspace settings\n- Change the active tool from toolbar\n\n---\nor\nLoad the UI from the attached blend file and try switching tools in the 3d view's toolbar. Then show the header in the properties window and try switching tools again.[startup.blend](startup.blend)\n\n[tools.mp4](tools.mp4)", "Scene statistics not updating depending on geometry node behaviour\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98\n\nBroken: version: 3.6.0\nWorked: Never.\n\nIt seems that the scene statistics (both in the viewport and in the status bar) are not updating to reflect the number of vertices after a deleting operation through geometry nodes.\nHowever it does update if I move to another frame in the timeline.\nIt may be a design choice to limit the computation needed but I thought useful to report\n\nIn the attached blender file go to the modifiers tab and change the LOD value in the geometry nodes setup, you'll see no change in the scene statistics despite the mesh displayed has a different amount of objects. If you move to any other frame it will update accordingly\n\n", "Linked Mesh Editing Doesn't Work As Expected When Using Data Transfer Modifier\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: 2.81 (sub 16)\n\nObject instances doesn't work as in blender 2.81\n\n\nIn blender 2.81, after entering the edit mode, all instances become active. You can see changes in real time.\nScreen below:\n\n\nIn Blender 2.82 it work ok till some time. I couldn't determine at what moment it breaks...\n\n\nChanges appears only after You enter to object mode.\n\n\n\nHere is blend file to test\n[instances_issue.blend](instances_issue.blend)\n\n\n", "Colection instances can't render if duplicated while instanced on a mesh with array\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.1\n\ncol instances disapear from render view if duplicated when instanced on an array\n\nmake a plane, add aray modifier. \nput anythng in a collection, instance it \nput the instance as child of the aray, toggle face instances on.\nduplicate the col instance: the previous one(s) will disapear from render.\n\nin this blend file, just turn render view and you'll see only the lastest col instance renders.\n\n" ]

[ "Regression: Array Caps broken on empty mesh in 3.5.\nBroken: 3.5.0\nWorked: 3.4\n\nCaused by 8b2556e8d895c54012526b3eaa66eaf96cb7721c\n\n\nIn (all?) previous versions of Blender, an Array modifier with a Start Cap or End Cap would show its cap regardless of the geometry (or lack thereof) in the base mesh:\n\n\n\nIn Blender 3.5.0, the Cap is not shown if the base mesh is empty:\n\n\n\n1. Download the attached Blender file.\n2. Open it in an affected version of Blender.\n\n" ]

[ "UV Loop Select with Double Click and Shift+Double Click to Extend. Need to triple click to Extend + Border Extend problem\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.0.0 Alpha\nBroken: 2.93.1\nWorked: probably none of the versions\n\nInconsistent behavior for selecting multiple edge/face loop.\n\nChange keymap values:\nUV Loop Select: `dbl-Left Mouse`\nUV Loop Select (Extend): `Shift dbl-Left Mouse`\nWith custom key for UV Loop Select, selecting with extend become a problem\n\n\n- Load factory settings.\n- Change keymap as suggested\n- Click on UV Edge or Face selection\n- dbl-click selects loop\n- Shift + dbl-click - does not select the loop, need to click 3 or more times\n[UV_Loop_Selecting_Issue.mp4](UV_Loop_Selecting_Issue.mp4)\n\n", "Unwrap to same bounding box in UV space\nAdditional property option to the unwrap operator. Sample the bounding box of the current selected components (face,edges, verts), unwrap the selection and then position the selection within the same bounding box again. Use the same orientation by storing the position of 3 arbitrary(?) uv points of the selection before unwrapping and then orient the newly unwrapped uv’s to the roughly same orientation.\n\n**Related tasks**\n#78396 (Pack to the same bounding box)\n\n\n**Starting point**\n\n\n\n - Green outline = bounding box\n - Blue outline = uniform bounding box\n\n\nThe goal is to unwrap only the selected uv island and keep it in the uniform bounding box.\n\n\n\n\n**Undesired result.**\n\nThe unwrapped uv island is scaled to fit into the uv 0-1 space (aka UDIM 1001)\n\n\n\n\n**Desired result**\n\nThe uv island is unwrapped and fitted into the original uniform bounding box. Note that this might result in overlap in some cases where uv islands are packed tight, but that is expected\n\n\n\n", "Transform orientation undo is inconsistent.\n\nBroken: 3.0\nWorked: ?\n\nTransform orientation undo is inconsistent. It works in object mode, but doesn't work properly in edit mode. In edit mode it sometimes won't undo, or undoes together with another different step(like changing mode, or moving vertex).\n\n- Open default startup;\n- Change the Transform Orientation from Global to something else\n- Undo/redo - it works;\n\n---\n- Reopen default file\n- Go to edit mode\n- move vertex\n- Change the Transform Orientation\n- undo multiple times - Will never undo the Transform Orientation. (now deselect cube and perform undo operation: will revert selected transform orientation)\n\n", "EXR reading : dimensions are based on dataWindow (not displayWindow), leading to e.g. Renderman Cryptomatte processed wrongly by Blender compositor\nOperating system: MacOS Sonoma Beta\nGraphics card: AMD RX6600XT \n\nBroken: ( 3.6, c7fc78b81ecb, release, 2023-06-27 )\nWorked: (none)\n\nRenderman cryptomatte pass images are read wrongly by blender compositor. It is changing the height of the image, based on the alpha, instead of keeping a fixed size. Even Blender 3.6.1 latest version has same issue. \n\n1. create a simple scene with spheres and cubes. leave empty space at the top of frame. \n2. render images with crypto matte using render man addon. \n3. bring the images into blender compositor using cryptomatte node.\n\n", "Object transforms affecting Sculpt Mode Brush behaviour\nThis is a design proposal to change some underlying behaviour of the brush system in Sculpt Mode.\n\n**The issue:**\nWhen scaling or rotating an object and then proceeding to sculpt on it in Sculpt Mode, the brush behaviour is generally affected by the transforms of the object.\nSo if the scaling is 1 on X & Y but 3 on Z, the brush radius will be 3 times as high. \nIf the object is scaled down in general, the brush strength will be lower in total.\nIf the object is also rotated, the brush radius will be as well and rake effects like for the Snake Hook brush will be badly affected since the object rotation is added to the rotation of the brush.\n\nIn recent versions the brush radius is at least reflecting the object transforms, which helps spotting these negative influences and reminding the user to apply the object transforms before sculpting.\nBut there is not benefit to having the Sculpt Mode being affected by the object transforms, so this is just a limitation of the current system.\nIt's also good to add that on the other hand Edit Mode is not negatively affected by the transforms of the object.\n\n[2020-03-02 11-42-04.mp4](2020-03-02_11-42-04.mp4)\n\n**The proposal:**\n\nTo make the sculpting workflow easier on the user it would be ideal if the brushes are not affected by the local transforms of the object but are instead based on the world scale & orientation.\nOnly symmetry options should be directly influenced bu the local transforms.", "Changing the Orientation of Modifiers\nCurrently, LineArt is created in 3D space, however, the Modifiers can be oriented incorrectly.\n\nIn this example, the Noise Modifier is moving the Grease Pencil points on the Normal but not up and down on Z. There is currently no way to change it.\n\n[Noise - Position.mp4](Noise_-_Position.mp4)\n\nThis is a request for a way to change the orientation of the Modifiers.", "UI: Merge Text Style \"Widget Label\" into \"Widget\", Add \"Tooltip\"\nWhen controlling how big interface elements are displayed, users can not only change the Resolution Scale and Region Zoom but can change the size and styles of some elements separate from others. This document proposes changes to our Text Styles.\n\nIf you go to Preferences / Themes / Text Style you will see that you can change the size of different UI elements independent of the overall UI scale. You can make it so that regardless of scale you always have Header text twice as large as regular text, for example.\n\nBut the design is not fleshed out well. We have just \"Panel Title\", \"Widget\", and \"Widget Label\". There are many areas where one type of UIBut uses one when it should use another. There are assumptions, like in #102687, that \"Widget\" and \"Widget Label\" are the same size. The function mentioned in that bug report - `ui_text_icon_width_ex()` - is trying to estimate an element's width but does not have the information needed to know what style to use, so just uses UI_FSTYLE_WIDGET, which is hardcoded for the \"widget\" style.\n\nIt seems like a nice idea that we can have labels displaying differently to the inputs beside it. And I have personally proposed adding to these options to include width, weight, slant, spacing and other text features.\n\nHowever, our interface is laid out programmatically using quite rough rules. We necessarily have a very tabular layout. For example we don't have (and might not be able to supply) a \"line height\": the vertical spacing between interface rows. This value is calculated from UI element width, considering scale and line width. So can't for example, leave the resolution scale the same but change the line-height to better accommodate languages that use fonts that are very tall (Arabic) or squat (Chinese).\n\nThis all means that we have little chance to make Label and Widget have varying sizes. The line-height can't vary with the largest of them, and we have to keep all interface rows the same height anyway.\n\nI propose that we merge \"Widget Label\" into \"Widget\" text styles, leaving us with only two styles \"Header\" and \"Widget\". And then add a third back for \"Tool Tips\" because that text size is currently set as a hardcoded fraction of the widget size - and I can imagine some users with vision impairment wanting those proportionally larger.\n\nThe only real downside is this would remove the ability for \"Widget\" and \"Widget Label\" to have differences unrelated to the size. There could be some users who have the same size but have them differ in shadow. Right now the only non-size changes possible are shadow-related but, as mentioned, we could add other options. For example we could allow one to be bold and the other italicized. But I don't personally think this is important. I don't like our text shadowing and use of weight and slant differences should be more selective than this, having sematic meaning. I would rather embolden important words, italicize special sections, etc.\n\n", "Outliner: Alt+disable is work for all selected, but Alt+Enable is not\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n{key Alt LMB} generally enables a feature that repeats the operation on all selected items in the outliner.\nBut that seems to work only if the object is selected in 3d View.\n[2020-01-12_20-44-23.mp4](2020-01-12_20-44-23.mp4)\n\nOpen:\n[untitled4.blend](untitled4.blend)\n- select the three objects (either in 3d view or outliner).\n- {key Alt LMB} click on the icon that disables object in viewports.\n- {key Alt LMB} again to try to enable them all.\nOnly one object is enabled, because the others are not selected in 3dview.\n\n", "modifier offset slider step value being driven by the mouse looses one order of magnitude worth of accuracy when units are metric vs none\nwin 10\n2080ti\n\nBroken: 2.80+\n\nSince blender 2.8 has switched to real world units the modifier slider step(when driven by the mouse) value has lost one order of magnitude worth of accuracy, 0.001 instead of 0.0001 \nIt is possible to switch the unit system back to none to get the higher accuracy. \nThey should be consistent and both work to the higher level of accuracy as this level is essential when working on real work scale small items e.g. a watch\n\n\n- with scene unit type set to \"metric\" add a bevel modifier the standard cube\n- press shift while clicking and dragging the bevel modifier offset slider and notice how the smallest amount possible to move is 0.001 m\n- switch scene unit type to \"none\"\n- press shift and click drag the modifier offset slider and notice the smallest amount possible to move is 0.0001 m\n", "Multi-Object (Weight) Painting\nMulti-object weight painting would be extremely useful when rigging characters with clothing pieces that are separate objects. If a character has a shirt and a jacket, they both have to be weight painted identically, but separately.\n\nThe objects could be combined, but that would mean they must share a modifier stack, which is not always an option. We could also paint one then transfer the weights, but that only works between very similar objects. So we are stuck with meticulously weight painting both clothing pieces, while making sure the weights match between them.\n\nWith multi-object weight paint, the same brush strokes could affect both meshes, so they would be a lot easier to keep in sync.\n\nThe bare minimum functionality that I would consider useful:\n- Be able to select an armature then several meshes that are rigged to it, and enter weight paint mode\n- Selecting a bone activates the relevant vertex group on all meshes\n- Brush strokes affect all meshes\n- Can switch to multi-object edit mode\n- Geometry masking features work\n\nIn my personal workflow, supporting multiple armatures is not important.\nIf anyone thinks this is important, please comment with a use case example.\n\nAdditional functionality that would be nice to have:\n- Indicating active object in the 3D View. So far this hasn't been necessary, since it was always just one object.\n- Changing the active object without leaving weight paint mode. Symmetry settings are stored on the mesh, so this would be needed to be able to access those.\n- All of the above for Vertex and Texture Paint :)\n\nI tried to keep wall of text to a minimum, I hope this is not too bad @ideasman42 :)", "Click selection and box selection in 3D view do not work properly in scenes with many objects\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580X OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\n[In my environment, if there are close to 100,000 objects, the objects can not be selected normally]\n[select_bug.mp4](select_bug.mp4)\n\nUploaded blend file has nearly 100,000 simple cubes\nClick on an object in the 3D view to select a distant object\nEven a box selection can make a crazy choice\nBut lasso selection and circle selection work fine\n[test_file.blend](test_file.blend)\n\n", "UV: Opening an image in UV Editor changes zoom\n1) Open default cube\n2) Tab to enter edit mode\n3) Open UV Editor\n4) Observe scale of unit square\n5) Open an image (Click \"open\" and choose an image file)\nBug, unit square is no longer in same location.\n\nThanks @BlenderBob for the initial report!\n\n", "Scaled Rigid Body causes issue (moving origin or mesh breaks collision, double transforms on negative scale)\nOperating system: Ubuntu 18.04 LTS\nGraphics card: Intel HD 4000\n\nBroken: 3.0\nBroken: 2.90.1\nWorked: I don't know if this works with any other version, I created the file using 2.90.1.\n\n\nSee the attached .blend file. This file contains two errors with Rigid body simulation. I'm filing both errors in one bug because these may be related (both happen in one example simulation).\n\nError 1: object origin distance from another object changes interaction between objects\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that \"Ball\" is attached to the chain.\n3. Stop the animation and jump to first frame.\n4. Select object \"Ball\" and from menu Object - set Origin - Origin to Center of Mass (Volume)\n5. Play the animation to verify that \"Ball\" is no longer attached to the chain.\n\nError 2: Rigid body type \"Active\" changes orientation of the object\n\n1. Open attached example case (.blend file)\n2. Play the animation to verify that chain is attached to the object \"Cube\".\n3. Stop the animation and jump to first frame.\n4. Change \"Cube\" Physics properties - Rigid body - Type: Active and Settings: Dynamic\n5. Play the animation and notice that Cube is now rotated 180 degress around the X axis. Obviously this results in chain no longer connected to the cube as expected and chain and Ball drop directly down during the animation.\n\nExample .blend file (cannot simplify more because Blender seems to be unstable with this file):\n[physics-test.blend](physics-test.blend)\n\n**Additional information**\nIt seems that I can work around Error 1 by selecting all items and applying \"Rotation & Scale\". I think this should not be required to get two objects to interact during simulation so I'm reporting the problematic file as-is. I cannot figure out the reason nor workaround for Error 2.\n\n$ apt policy blender\nblender:\n```\nInstalled: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nCandidate: 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0\nVersion table:\n```\n *** 2.90.1--release~98526-3e85bb34d0d-0thomas~bionic0 500\n 500 ubuntu bionic/main amd64 Packages\n", "Change UV Channels from the UV Editor on multiple selected objects\nWhen multiple objects are selected and user is in edit mode in the 3d viewport, she/he can change uv channel of the**active object** in the top right corner in the UV Editor. It would be a nice change to **iterate through each selected object**and if the iterated object has a uv channel with the current name in the UI, that uv channel will be made active on the iterated object.\n\n", "Custom data split normals are taking active object from the area even if the active object is overriden\nBlender 3.5\n\n\nOperators `customdata_custom_splitnormals_add` and `customdata_custom_splitnormals_clear` if called from properties panel seem to take active object from currently active area even if you `context.temp_override(object=obj)` or `context.view_layer.objects.active = obj` to change active object which is counterintuitive and contradicts with how other operators active object override work.\n\nFound a workaround - if you `context.temp_override(area=None, object=obj)` it will take active object into account.\n\n\n1. Open attached .blend file\n2. Run the script\n3. (Make sure all objects are selected)\n4. Go to Custom Split Normals section (in Object Data Properties after Geometry Data).\n5. Try \"Add CSN\" - it wouldn't work\n6. Try \"Add CSN override area\" - it doesk work.\n\n" ]

[ "Changing dimension on multiple objects no-longer works\nOperating system: Windows\n**working version:**\n2.79b\n**Last known *working* version:**\nblender-2.80.0 Beta (dec 2018)\nHash: e4dbfe0a98c1\nBransh blender2.7\n2.80.39\n**Earliest known *broken* version**\nblender-2.80.0 Beta (april 2019)\nHash: 480a09a92f7f\nBransh blender2.7\n2.80.60→2.83.2→2.90.0 Alpha\nManipulating the values in ‘`3d view`→`n-panel`→`dimensions:`' with ‘alt-key’ held down and dragging the mouse cursor will no-longer affect all the selected objects, only the parent.\n(feature still present for '`Location`', '`Rotation`', '`Scale`'.)\n\n1. Duplicate the default cube and move it so both cubes are visible.\n2. select both cubes and go to ‘`3d view`→`n-panel`→`Dimensions:`'\n3. With both cubes selected, hold down the alt-key and start manipulate the value by dragging your cursor in one of the three fields for 'Dimensions'\n\n**PS.** feature did not have the same affect as just scaling the objects, (see animated gif bellow)\n\n[dimbug.blend](dimbug.blend)\n" ]

[ "Grease Pencil mask error\nOperating system:windows10\nGraphics card:GTX1060ti\n\nBroken: 2.83&2.9\nWorked:greasepencil-Mask error\n1.When 2.83 or later, creates two objects, the masks collide, causing a strange phenomenon, and in 2.82 there are no errors.\n2.And creating two masks under the same object can cause problems too。\niJlqkf556sA\n[GP剪贴测试.blend](GP剪贴测试.blend)", "Self-referencing driver works in viewport, but not in render.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional) 2.79b\n\nRotation property of object is updated in viewport, but not in render.\nIf run same script in 2.79 - all works fine both in viewport and render.\n\n```\ndef rotator():\n var1=bpy.data.objects[\"Suzanne\"].rotation_euler.z\n var3=bpy.data.scenes[\"Scene\"].render.fps\n\n new_value=var1+math.radians(var3)\n\n return new_value\n```\n\n\n[Script_bug_2.8.2.blend](Script_bug_2.8.2.blend)\n\n- run the file Script_bug_2.8.2 ('Run script', 'Update Dependecies')\n- play in the viewport - the animation works correctly\n- render (Ctrl + F12) - the animation does not work;\n\nViewport:\n[bug_video_render0001-0050.mkv](bug_video_render0001-0050.mkv)\n\nRender:\n[bug_video_render_20001-0050.mkv](bug_video_render_20001-0050.mkv)\n\n2.79 file:\n[Script_work_2.79.blend](Script_work_2.79.blend)\n\n", "Impossible to move with G key an object scale to 0 and parent to an empty\nOperating system: Windows 7\nGraphics card: GTX 780\n\nBroken: 3.5.1\nWorked: \n\nWhen an object is parented to an empty, and this object is scale to 0, you cannot move it anymore with the G key. But you can move it in the transform menu location.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n1. Open blend.\n2. Try to move object with G key.\n3. It is possible with Transfom menu.\n\nThanks a lot !\ndono", "Snap cursor gets too small sometimes\nBroken: version: 2.93.6 Release Candidate\nWorked: Never\n\nWhen the snap cursor doesn't snap anything (or is snapped to grid) and you zoom in on the scene, it gets too small.\n|||\n| -- | -- | -- |\n\nNOTE: the cursor displays increments that are not actually used for snapping. This can be confusing when trying to increment over small distances.\n\n- Enable the `Add Cube` tool (to display the cursor)\n- Point to a region of the Grid further in the background.\n- Zoom In\n\n", "Issues with Fluid sim INSIDE objects\nOperating system: Win 10\nGraphics card: Twin GTX 1070\n\nBroken: 2.92\nWorked: 2.91\n\n**Fluid sim inside properly meshed objects does not work at all**\n- Create a tube with a curb or a Cylinder,\n- add a solidify modifier and apply it,\n- put a icosphere and downscale it to fit inside the tube,\n- keep icosphere selected and go to Object -> Quick Effects -> Quick Liquid.\n- scale the domain to fit everything inside.\n- Use tube as effector (planar or not does not work either way)\n- Try to bake a sim.\nAll settings that used to work in 2.93 and 2.91 do not work AT ALL in 2.92. Looks like it considers the mesh as a closed object.\n\nThanks in advance", "UI bug in preset window after repeated remove\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29\n\nBroken: version: 3.2.0\n\nWhen you remove a preset the textfield with the +/- moves one entry up\n[2022-07-15 09-17-07.mp4](2022-07-15_09-17-07.mp4)\n\n1. Go to the scene tab\n2. Create several new presets\n3. Remove all the new created presets in one go without moving the mouse away.\nI think the textfield with the +/- moves should just stay at the bottom and the window should shrink from the top.", "Double click list renaming not working on heavy scenes\nVista64, 2.7a, gtx470\nWhen the scene is heavy, so that interface becomes slightly laggy, double click list rename stops working, especially for fast clicking.\n\n - Add subdivision modifiers to any mesh until interface becomes laggy.\n - Add a vertex group or UV map.\n - Double click to rename - renaming is not activated.\n", "2.7x interface ctrl tab breaks/inconsistent in weight paint\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.93.0 Beta\nBroken: version: 2.92.0\nBroken: version: 2.91.0,\nWorking: version: 2.90.1\nWorking: version: 2.83.14\nDiscounting LTS, this has been broken for a few versions, although I can't tell you exactly the last time it worked. Probably 2.83 or 2.91. Sorry, I've been lazy with reporting bugs.\n\nUsing ctrl tab to switch out of weight painting mode sometimes fails to switch modes.\n\n\nInstall Blender. At your initial startup options, choose 2.7x interface (+spacebar search, your basic pre-2.8 settings). I believe this is necessary to get ctrl-tab mode switching.\n\nSelect your starting cube. Ctrl tab to enter weight paint mode. Ctrl tab to return to object mode. Repeat as desired; this is expected functionality.\n\nCtrl tab to enter weight paint mode. Tab to enter edit mode, then tab to return to weight paint mode. So far, this is expected. Ctrl tab to try to return to object mode and nothing happens. LTS and previous versions take you to object mode.\n\nI believe there are other operations that break the mode switching out of weight paint, but I chose tab to edit as a simple, easily reproducible example.\n\n", "Touchscreen 'Continuous Grab'\nOperating system: Linux-4.15.0-54-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Mesa DRI Intel(R) Haswell Mobile Intel Open Source Technology Center 4.5 (Core Profile) Mesa 19.0.2\n(bug also tested on Windows 10)\n\n\nBroken: version: 2.80 (sub 74)\nWorked:\n\n\n* Activate a gizmo using the **touchscreen** on a computer. (The 3D navigation gizmo for example)\n* Drag your finger outside the original editor\n* The gizmo is manipulated incorrectly\nThis bug disappears if \"*continuous grab*\" is disabled in the User Preferences.\nI think it's a matter of auto-disabling *continuous grab* while receiving touch input, like how pen tablets are handled.", "Keymap: custom key modifiers work inconsistently\nOperating system: Arch Linux, no DE, i3wm\nGraphics card: GTX 960\n\nBroken: 2.80\nWorked: 2.79\n\nI'm left-handed on the tablet, so I bind my sculpt hotkeys to the numberpad. Binding NumpadEnter+LMB to sculpt inverted (same as holding Ctrl) no longer works in 2.80. However, binding NumpadEnter+MMB to pan the view does work. Not sure where the conflict is. This setup did work in Blender 2.79.\n\nLoad factory settings\nImport .py keymap provided (or bind manually; sculpt.brush_stroke and view3d.move)\nEnter sculpt mode\nAttempt to sculpt inverted by holding NumpadEnter+LMB\n\n[system-info.txt](system-info.txt)\n[custom_modifier_bug.py](custom_modifier_bug.py)\n\nSimilar bugs from ages ago:\nT44349\nT34822", "UI: Drag Tool option is misaligned and should not use colon\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha\n\nDrag Tool option is misaligned and should not use colon:\n{[F11087908](image.png), size=full}\n\nBtw. `Gizmos:` shouldn't use colon either\n\n", "Changing Resolution Preset doesn't allow to Undo\nBroken: 3.6.0\n\nChanging Resolution Preset and then trying to undo doesn't work, like if the action is not registered.\n\n\n- Open Blender\n- Click on the Format panel on the right icon to change preset\n- Select a preset\n- Undo\n\n", "Surface tension is not working\nOperating system:Windows-10-10.0.19041-SP0 64Bits\nGraphics card:NVIDIA GeForce RTX 2080/PCIe/SSE2\n\nBroken:3.1.0 Alpha, branch: K-Cycles, commit date: 2022-01-16 15:45, hash: 164a13275cf8\nWorked: \n\nIn mantaflow fluid simulation, change the value of 'surface tension' does not work at all, My cpu is Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz, i tried different version of blender, it didn't work either\n[surface1.blend](surface1.blend)", "Modal keymap for snapping in the `Corner Pin` widget has no effect\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nThe bottom bar states that pressing ^ will enable snapping, but it seems it does nothing.\n\n\n\n1. Create a new default file;\n2. Go to the compositor;\n3. Enable nodes;\n4. Add a viewer node (this allows you to resize and test different sizes for the `Corner Pin` Gizmo);\n5. Add a `Corner Pin` node;\n6. Edit the `Corner Pin` widget and try to snap.\n", "Known-issues with interaction handling inside pop-ups\n# Known-issues with interaction handling inside pop-ups\n\n*Pop-up in this case includes menus and popovers.*\n\nThere are quite some old and some new issues with pop-ups. Their increased usage after 2.80 means that users run into them more and more.\n\nIn this task all related known issues should be listed, to give a good view over the situation. Eventually it should help deciding how to move forward.\n\n* Resetting default value does not work in popovers or menus. (#69200)\n* Context Manual Help Operator does not work in context menus. (#67201)\n* Add Driver : Clicking the picker doesn't work. (#58341)\n* Popover: Color Sampling doesn't work. (#63890)\n* No color drag'n'drop in Viewport Shading popover. (#70654)\n* Eyedropper does nothing on \"New\" in Uv image editor (button is disabled as workaround). (#32396)\n* ~~Most ID selectors (like e.g. the 'target' ones in constraints and modifiers) do not show difference between local and linked IDs. Even worse, they do not allow to select linked ones when a local one exists with the same name. (#73156)~~ (d6cefef98f)\n* Double-click not working in UI_Lists in popovers (e.g., grease pencil layers renaming) (#66286)\n* #76833 (Eyedropper in object selection box doesn't work)\n* #76124 (Cannot use keyframes, File select, File picker (eyedropper), etc. in modal Operators/Panels called by WindowManager)\n\nMost of these issues probably have similar roots (e.g. code not checking if `CTX_wm_menu()` can be used over `CTX_wm_region()`, but often times the former returns `NULL` when it shouldn't)." ]

[ "Tablet pressure sensitivity only working in original main window.\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\nGraphis Tablet: Huion Kamvas Pro 20 (Window's Ink)\n\nBroken: version: 2.81 (sub 15) AND 2.8 release \nWorked: (didn't work in any version I tried)\n\nAfter creating a new window, main or otherwise, tablet pressure sensitivity doesn't work in that window but remains working in the original window.\n\nCreate new window, add object to sculpt on, try to sculpt with pen with pressure sensitivity on.\n\n" ]

[ "GPencil: Missing functionality in Vertex Paint mode Selection tool (left-click-select)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.0 Beta\n\nWhen Points select is enabled in Vertex Paint mode, the Selection tool doesn’t behave like in Edit mode:\n- it cannot select a single vertex,\n- a left click away from points doesn’t deselect them.\n\nAdditionally there is no color picker when this tool is selected, so if you select some points to use the Set Color Attribute operator on them, you can’t see the current color or choose a different color, unless you switch to a different tool.\n\nMake sure you use Left Click Select in Preferences > Keymap\nAs shown in video, open any stroke in Vertex Paint mode, enable Points select and select the Selection tool.\n- You can box select points but can’t left click on a point to select it and you can’t click away to deselect points.\n- There is no color picker.\n<video src=\"attachment\" title=\"Selection Bug-1.mp4\" controls></video>\n\n", "Display as behaviour in rendered view inconsistent between Eevee and Cycles\nOperating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19\n\nBroken: version: 2.82 (sub 4)\n\nWhen objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered. \n\nFor any object, under object properties -> viewport display, set display as to \"bounds\" or \"wire\". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.", "Shader color affects Shadow Pass in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Super with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.1.0\n\nShadow Pass is not working as it should in Cycles. It somhow works much better in EEvEE (altough other problems arise).\n\nEasiest setup is just adding a plane, a sphere and setup cycles as a render engine.\nActivate **Shadow Pass** (not the Shadow Catcher Pass).\nDo an image render and everything works, more or less, as expected. So you get as a result a Black and White image (right side) where black is shadow and white is none:\n\n\nBut, as soon as you texture the objects with any image you get the darkest areas of those images in the Shadow pass (something like if one of the rgb channels is leaking to the final image):\n\n\nI have already tested it in Blender 2.83, 2.93, 3.1, 3.2 and 3.3 alpha and I have got always the same behaviour... so no idea if it ever worked or not as it should do. Right now it is absolutelly useless as you can't compose it without textures afecting the masked shadow.\n\nAs I said I already tested in EEvEE and it works better:\n\nBut another problem arises, tesselation of the objects aren't smoothed, like if it is not using Smooth Shade setting at all.\n\n\nI attach a scene that reproduces the problem: [Shadow_Pass_3.1_Packed.blend](Shadow_Pass_3.1_Packed.blend)\n\nAs a last detailed behaviour, in the scene I'm actually working, I nottice that some Specularity and Diffuse are also \"leaking\" to the Shadow Pass:\n\n\nI hope it can be fixed.\n\nOf course, If I can somehow workaround it let me know as it would be of much help as I didn't found, yet, a way to overpass the trouble other than creating a new scene with untextured materials.\n\nThanks in advance, and cheers!\nIgnasi.\n\n", "Crushed Velvet Eevee render problems in Cycles\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: \n- 2.93.0 Alpha\n- 2.82 (sub 7)\nWorked: ?\n\n\nThe *Crushed Velvet* material from the *Material Library* does not render properly with Cycles when setting the device to *GPU*.\n\n- Load the simplified material attached below\n- Set the render device to *CPU* and render. The output should be all black\n# Set the render device to *GPU* and render.. Depending whether you have only GPU(s) activated in the preferences or also CPU(s) you should see one of the following. When only GPU(s) are enabled you should get a proper render. When CPU(s) are also enabled you should get dark render tiles that are rendered on the CPUs.\n\n[VelvetTestSimplified2.blend](VelvetTestSimplified2.blend)\n\n---\n\nOriginal description:\nI'm attaching the .blend file I used to test this issue. I'm not even sure this is a bug or simply me not being overly familiar with materials yet, but it feels like a bug. An dit may be a Blender bug and nothing to do with this add-on. Obviously, this material renders fine in Eevee, but it also renders fine in Cycles when using CPU to render, but has major artifacts when using GPU to render. I've attached a render to show what I'm getting in case you don't experience it.\n\nThe steps I took to get here are, \n\nBasically, I have a default scene I use to do my modeling or as a start point. It's very basic. I was experiencing this issue in another project I was working on and noticed it went away when I changed the material on one object. \n\n- I loaded up my basic start file\n- selected the sphere\n- Scrolled down to the Material Library VX panel in the Material Properties tab\n- Loaded the Sample Library\n- Chose the Crushed Velvet Eevee material and clicked Apply to Selected\n\nThat's it. I had initially thought it was simply a problem rendering in Cycles but for my first render, I forgot to switch from CPU to GPU and noticed it rendered fine. So I did a few more tests and it renders fine with CPU every time, but not with GPU.\n\n[VelvertTest.blend](VelvertTest.blend)\n\n", "Display Workbench Textures On Curve Objects\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon HD - FirePro [D500](D500) OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.24\n\nBroken: version: 2.82 (sub 6)\nSame on Windows version with same hash as well as in older versions of the 2.8x series.\n\nWorked: (optional)\nWorked in 2.7x Blender viewport ('Texture' mode)\n\nTextures don't display on curve extrusions in 'Solid' viewport shading mode even when UVs are assigned and 'Texture' is chosen as the object color. Instead, Curve extrusions simply stay gray.\nThese same textures show up fine on regular mesh objects in the same viewport. Also the curves display as intended in Material Preview and Rendered modes.\n\n\nIdeally open attached blend file to see the issue right away.\n\nAlternatively :\n1. Create a curve object and give it depth and UVs and apply a material\n2. Import a bitmap texture, attach to the curve's material and select it\n3. Switch to Solid shading mode and activate Texture as object color\n4. Compare look in Solid and Material Preview\n5. Repeat the above steps for a mesh object with UVs\n\n\n[textures_on_curves.blend.zip](textures_on_curves.blend.zip)", "Sample texture color dialog isn't dismissed after use\nOperating system: W10\nGraphics card: GTX 970\n\n2.82a\n\nAfter use of the pipette in the Image Texture Editor, the 'F9' dialog box is not dismissed until an UNDO operation is performed.\n\n\nSample file included; Launch file. Switch to Texture Paint. In the Texture Image Editor, invoke the sample function with the S hotkey. Observe the dialog.[Sample Dialog Dismiss.blend](Sample_Dialog_Dismiss.blend)", "Data Transfer modifier works only for Byte Color & Face Corner color attributes\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 3.2.0\n\nIf a target color attribute Domain is *Vertex* or it's Data Type is *Color*, the data are not transferred.\n\n[data-transfer-color-attr-bug.blend](data-transfer-color-attr-bug.blend)\nYou can see in the attached .blend that the Data Transfer modifier is set correctly, but the Col attribute isn't updated.\nAfter doing Convert Attribute -> Domain: *Face Corner*, Data Type: *Byte Color*, it starts to work correctly.\n\n\n", "Texture Node editor --->creating image , then use created image as input node in texture node editor \nwin 10 \namd radeon \nintel i5\n\n Blender 2.8\n3d8cbb534f82\n\n\n First of all ,this is specifically about the \"texture node editor set to brush for creating an image , then using the created image as an image input in the (brush ) node editor , and again paiting in the SAME image ...\nIt totally makes sens that blender crashes because it is trying to create an image where the brush is that image itself , thus creating a feedback loop \n\n\nSteps to reproduce crash\n\n\n- Create plane \n- Go to the shader editor and create an image texture node \n- Create a new file , let's call this one ''crash'' and route it the shader's colour input \n- Go to the 'texture node editor and from the dropdown select 'brush''\n- Click the 'new tab' and enable úse nodes , by default we are presented with the checker pattern \n- go to the image editor and draw something , we are presented with a checker pattern \n- Now go back to the texture node editor'' and select ímage 'from the input nodes and route it to the tout\n- Select çrash 'as image \n- Now paint something in the image editor \n\nCrash \n\nIn the provided file , everything is already set up , al you have to do is paint in the image editor , and then route the module labeled çrash'to the output of the texture node editor [feedback crash .blend](feedback_crash_.blend)\n\n ", "EEVEE Shading: string sockets node group interface value doesn't work\nBroken: version: 3.0.0 Alpha\nWorked: n/a\n\nin shading, String sockets exposed via node group interface don't use the value from the node group interface\n\nSteps to illustrate the problem\n\n* Use a quick smoke effect on a cube\n* Add a principled volume and connect it to material volume output\n* Change the Density Attribute to other text\n* Group the principled volume\n* Change the Density Attribute back to density\n\n[volume.blend](volume.blend)\n\n", "Eyedropper values are slightly off from target color\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nEyedropper values are slightly off from target color, unless in hex mode press enter.\n\nIn attached file using eyedropper replace green color of selected strip with grey from above strip -> result is a bit darker color\nGo to hex color mode, place cursor at value and hit enter -> color is ok\n[color_picker.blend](color_picker.blend)", "Preview Texture Blend\nOperating system: Arch Linux\nGraphics card: GTX 1060 6GB\n\nBroken:\n(example: 2.79b release)\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\n\nTexture gradient is not displayed correctly. Texture Blend.\nWhen you configure the texture, the preview displays the texture view.\nThe preview is more white than black.\n\n\n\n\nIf the texture to use as brush, you can see that the boundary particle moves wrong.\n\nIf in 2.8 open the file created in 2.7.\nThe texture is displayed differently.\nBut it works the same way as in 2.7.\n\n\n\nRun the attached files, see how the particles behave.\n[Blend.zip](Blend.zip)\n", "Default theme: Data types corresponding with modes\nFor the release of Blender 2.83, we have removed the use of the crosshair cursor for Edit Mode, because it was conflicting with tool cursors. \n\nInstead, we can use other things to help clarify to users which mode is active. \n\n{[F8383208](Screenshot_2020-03-02_at_11.07.10.png), size=full}\n\nCurrently, selection in all modes is orange. But, as you can see above, we already color code different kinds of data in Blender. Object data (mesh, curve etc) is set to green, so we could use that as the edit mode selection color.\n\n\n## Examples:\n\nVertex:\n{[F8383329](theme_vertex.png), size=full}\n\nEdge:\n{[F8383332](theme_edge.png), size=full}\n\nFace:\n{[F8383334](theme_face.png), size=full}", "Shader to RGB node is ignoring shading and just using color socket data directly\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.4\n\n\nIf you have a Shader that is converted with the Shader to RGB node, and then the resulting Color is plugged into another shader node and rendered, the output of Eevee's Color pass for that shader shows color plugged to socket of shader that is converted to RGB. In example file it is pure white, when you would expect to see the converted shader to RGB.\n\nProblem exists with Diffuse, Glossy, and Emission shaders and passes with the exception that an Emission converted to RGB going into another Emission will show up properly in the emission pass.\n\nSee Node graph in attached image, or attached file.\n\n\n[shader_to_rgb_eevee_pass.blend](shader_to_rgb_eevee_pass.blend)", "Texture Paint: Color Palette operator issues with Undo/Redo -- Vertex Paint is fine though\nOperating system: Darwin-15.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: ATI Radeon HD 5770 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.42.15\n\nBroken: version: 2.83.0\n\n\nIn Texture Paint mode (contrary to vertexpaint mode or gpencil), the palette operators dont work with Undo/Redo\n\nFrom the default startup file:\n- go to vertexpaint mode\n- (a) in the Active Tool tab in the Properties Editor, under Brush Settings > Color Palette, add a palette\n- (b) add a color to the palette\n- (c) Undo --> should be working [color is removed again]\n- so far everything is working\n- go to texture paint and do the same a, b, c --> color is not removed again, Undo is not working\n\nThis is what is probably the cause for the following more specialized original report (but also there the same thing works fine in vertex paint mode)\n\n## original report\n\nWhile in texture mode users press S to activate a color picker (not sure why this isnt the GUI nor the tools palette?)\nWhen its active, we have the options menu (used to be F6 i believe) There is this option \"Add to Palette\".\nThis however always adds colors. When you uncheck it, it will enable itself the next time your use the S key and pick a color.\n\n01. Open the attached scene.\n02. Start texture paint mode\n03. Use S key to enable color picker\n04. Options menu (bottom left) shows \"Add option to palette\" > Deactivate it.\n05. Use S key again > Notice colors are still being added but option is unchecked.\n06. When you let go of the S key, its checked again\n\n\n\n\n[IMport Palette - Blank.blend](IMport_Palette_-_Blank.blend)", "Create the shadow catcher in eevee give a black result\nOperating system: Windows 10 64bits\nGraphics card: NVIDIA GeForce RTX 2060\nBroken: 2.90, 2.91, 2.92, 2.93\nWorked: 2.83.12\n\nI followed the tutorial how to make a shadow catcher on eevee (). But it makes the result totally black when using version 2.90 and i've tried 2.91, 2.92, and 2.93. But the result is the same\n\n\n\nIn 2.83 the result is like this\n\n\n\n[shadow_bug.blend](shadow_bug.blend)" ]

[ "Vertex paint color picker not acaccurate\nOperating system: manjaro linux\nGraphics card: AMD 580RX\n\nBroken: 2.80 beta\nWorked: (optional)\n\nUsing the color picker in the vertex paint the 'picked' color in not the actual vertex colors. \nInstead it seems like its taking a screen grab of the viewport and sampling the pixel color.\nThe expected behavior should be to pick the vertex colors of the mesh.\nAlso note that changing the color management/profiles in blender plays around with these colors also!\n\nApply some color to a mesh.\nThen use the color picker to pick the color from the mesh. Notice that if a face is selected the colors chosen are lighter. Or if there is lighting, it picks the color of the lighting." ]

[ "Python Operators that add/remove ID data without an undo step crash Blender\nOperating system: Win 10\nGraphics card: GTX 1070\n\nBroken: 2.8.3, 2.9 aed11c673efe\nWorked: 2.8.0\n\nUndoing after object linking to the scene crashes blender. I used the latest daily build\n\n1. Load the crash blend file [crash_modal.blend](crash_modal.blend)\n2. Run the script attached\n3. Click in viewport to add a new object, and then press ESC\n4. Press Ctrl+Z to undo\n5. Crash..\n\n", "Crash with certain file. Sculpt mode. Vertex color fill + edge.\nOperating system: Windows-8.1-6.3.9600-SP0 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Alpha\n\nWhen I try to apply vertex color Fill (Sculpt mode) on edge in this particular file, I get crash\nAnd all fine for shapes/triangle.\n\n[VC + edge crush.blend](VC___edge_crush.blend)\n\n[debug_logs.7z](debug_logs.7z)\n", "Hair particle system altering display percentage crashes Blender.\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nChanging the percentage value in the Viewport Display section causes Blender to instantly crash.\n\nSet the display percentage with the currently active particle system\n[field_3400_autosave.blend](field_3400_autosave.blend)", "MacOS: Eevee render crashes with GPU hang occurred\nLaptop: 2019 Macbook Pro 16\" \nOperating system: Mac OS Big Sur 11.1\nGraphics card: AMD Radeon Pro 5300M / Intel UHD Graphics 630 1536 MB\nProcessor: 2.6 GHz 6-Core Intel Core i7\nMemory: 16 GB 2667 MHz DDR4\n\nBroken: \n2.91.0 and 2.91.1 \n\nRender engine: eevee \nBlender crashes in rendered view or after hitting F12 (Render Image)\n> GPU hang occurred, msgtracer returned -1\n\n\nlast step taken in this file before crashing:\nMath node > function power > right side render tab > render: 64 *sample: 256* distribution: 1000\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n- \"Render image\" with render engine Eevee.\n[nebula.blend](nebula.blend)\n\nI'm completely new to blender, so I hope I wrote this down correctly! \n\n\n- adding crash report file \n[crashreport.docx](crashreport.docx)\n", "Geometry Nodes + Shader Editor + Asset Browser bug\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.5 `7bf75231e8c5` , 3.4.1 `55485cb379`\nWorked: (latest 3.3.2 for Mac Intel)\n\nGeometry Nodes Editor + Shader Editor loads in all marked, related assets from Asset Browser causing crash and memory overload\n\n- Extract Asset.zip\n- Open default blender scene and assign asser library path as shown in the image\n- Open node editor\n- SHIFT+A action cause immediate memory overload from Asset Browser\n\n\n\n[Assets.zip](Assets.zip)\n\n[asset-library-indices.zip](asset-library-indices.zip)", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Texture Paint - bad behaving operator \"Save All Images\"\nGo to Texture Paint Mode with some Textures loaded. In T-Panel go to the Slots Tab. There you will find a Button labeled \"Save All Images\". However, do not push this Button !\nThis Button overwrites all involved/edited Textures in the Texture Paint Slots at once and instantly, without further inquiry, to the directory of the origins.\n\nIt's not a bug, it's working pretty well !\n\n \n", "Crashing and freezing when working on files with assets\nOperating system: macOS-12.6.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon RX 580 1.2\n\nBroken: version: 3.5.0\n\nCrashing and freezing when working on files with assets\n\nif I open the demo file cube_diorama.blend the whole system freezes and either crashes or logs out needing to login again.\nevery blender crash a WindowsServer log is created.\n\n cube_diorama.blend never crashed in previous versions of blender for me.\n\n", "Crash when rendering animation\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.0\n\n\nI was rendering a simple camera animation overnight, Blender crashed about 2/3rd the way through. Here's the crash log.\n", "Blender 3.5.1 + Mac + Metal + Crash\nOperating system: MONTEREY 12.6.3\nGraphics card: AMD Radeon Pro 5500 XT 8 GB\n\nBroken: Blender 3.5.1\nWorked: Blender 3.4.1\n\nBlender 3.4.1 will render a given scene with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" in 1 min 58 sec\n\nBlender 3.5 and 3.5.1 will crash on the same scene set on \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\" - \nIt has to be run with \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"CP\" and now takes 5 min 53 sec.\n\nI have lost computing power with the latest versions.\n\nJust run the file with GPU BACKEND turned on and \"RENDER PROPERTIES\" -> \"DEVICE\" set to \"GPU COMPUTE\"\n\nI could not include the file as it is a project I am working on - if there is no other way to check up on this issue I will try to create another file that I can send\n\n", "Generated images with disabled alpha can have alpha but are saved with no alpha, losing user's work\n## Simplified Report\n\n- Create a new image with Alpha disabled.\n- Set the generated color to fully transparent.\n- Set up this image for 3D texture painting on a simple plane and paint some opaque strokes.\n- Execute the Same All Images operator in the textures slots panel.\n- The image is saved as RGB and alpha is lost, losing some of the user's work without warning.\n\nThis can be even less clear, because some operators like the Lightmap Pack operator can create images with no alpha implicitly, and the user doesn't know this until the alpha data is lost.\n\n## Original Report\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\n\nwhen you create a new image texture through the Lightmap Pack feature and paint on it can display as RGBA but the alpha channel gets discarded on save and reopening the file. Images created through other means (like the image shader node or the image panel) do save with alpha channel.\n\n1. go into edit mode on the default cube.\n2. UV > Lightmap pack. choose new image.\n3. in the image panel, select the image, go to the Image tab on the right, set Source to Generated and Color to Transparent.\n4. make a material using the texture. Set the alpha mode to hashed/clip/blend doesn't matter.\n5. apply it to the cube.\n6. draw something on it in texture paint mode.\n7. under Texture Slots click 'save all images'.\n8. close blender and reopen the file.\n9. the texture lost it's alpha.\n\nThe reason seems to be that lightmap pack generates an RGB file, but it can still appear as RGBA throughout blender until you hit refresh in the image panel or re-open the file. Ideally for my own workflow the lightmap pack feature would allow for creating RGBA files (perhaps an alpha checkbox if it's important for other workflows to not have an alpha channel)\n\nattached file: white cube was made through image shader node, blue cube through image panel generate option, green cube through lightmap pack.\n\n[bug.blend](bug.blend)", "Crash when delete linked object in scenes outliner\nOperating system: Windows 10\n\nBroken: 3.6, 3.5, 3.3 LTS, 2.93 LTS\nBroken: 2.91.0\nWorked: 2.90.1\n\nCaused by b0741e1dcbc5e4549e95745b1f1b501f8cd33add\n\nBlender is crash when delete linked object in scenes outliner\n\n1. Open start scene\n2. Create new scene \"Scene.001\"\n3. Click on Cube, Ctrl+L, Link objects to scene \"Scene.001\"\n4. In Outliner switch to \"Scenes\"\n5. Select \"Cube\" object in Scenes Outliner in \"Scene.001\"\n6. Move cursor to Outliner, press key \"X\" or \"Delete\"\n7. Blender is crashing\n\n", "Segmentation Fault Crashing Blender when Rendering\nOperating system: Linux-5.19.0-46-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.54.03\n\nBroken: version: 3.6.1\n\nDuring rendering, Blender will often crash with segmentation fault \"Memoryblock MORE THAN 1 MEMORYBLOCK CORRUPT: error in header\" message.\n\nNeed guidance to help provide a blend file to reproduce the issue.\n\nThe issue occurs 100% of the time with an old version of a large blend file on certain frames. I have attached the debug and crash reports. \n\nMy workaround was to turn on subframes and render subframes either slightly earlier or later than the main frame. For example, if the frame I wanted to render was 187, I would render frame 187.1 or 187.2 until blender would render the frame.\n\nI believe the problem relates to a model I had commissioned, but I cannot recreate the issue in other blend files with that model.\n\nGPU memory usage is about 7.6/8 Gb, so there is headroom, and there is plenty of RAM. It does not matter if it is rendered on GPU/CPU, GPU only or CPU only it will always crash.\n\nI have tested on 2 other Windows computers with the same results, so it is not Ubuntu related.\n\nOther frames render perfectly.\n\nThere is no issue with viewport render mode. Often I get \"out of memory\", but that is only because Blender does not dump some things from memory before viewport rendering an updated scene. It's bound to be a known issue and easy to work around.\n\nI have prepared the file to upload here, but it's 1.9 Gb zipped. Before I send it there maybe some advice about troubleshooting my end someone might know and can help me with. I have spent 3 solid weeks trying to troubleshoot this and the only reliable way I know of reproducing the issue is with the full file.\n\nN.B. The update to 3.6.1 saw me return to this with an updated and improved version of the file. Background rendering will SOMETIMES render problem frames. I have included debug files for this as well.\n\nIs there any advice I can get as to how to narrow down this problem?\n\n", "Image syncing between Editors via active image canvas \nThis is related to [D16811](D16811) and similar improvements.\n\n## Issue\n\nThe purpose of this design is to avoid unintended syncing of images between the image editor, 3D viewport and shader editor.\nThe syncing is currently tied to the last active image texture node in the material. But since this is triggered with selection it leads to many accidents.\nThis has lead users to avoid using the syncing all together by pinning images and not using the \"Material\" texture selection in the 3D viewport.\n\n## Solution\n\nThe goal is to make the syncing an explicit action by\n- Using the active texture paint slot/canvas, instead of the last active image texture node\n- Indicating the active image canvas on any image texture node that uses it with an icon (Eye icon for example)\n- Changing the active image canvas in the node editor via an explicit action (Clicking the icon)\n- For faster use, add a shortcut (like double clicking on an image texture node) to make the image canvas active\n- For reference, add a context menu entry with the used shortcut\n\n\n\nThis also affects other areas where currently the active image texture node is being used:\n\n- General Image editor display\n- 3D viewport solid shading with color set to Texture\n- Baking target texture\n- UV editing image aspect ratio\n\nThis wouldn't contradict current cases of icons in the top-right corner.\n\n", "Rendering object in Cycles X preview hard crashes whole system\nOperating system: Windows 10 x64\nGraphics card: nVidia RTX 8000\n\nBroken: blender-3.5.0-alpha+universal-scene-description.1f9e90bb1cf3-windows.amd64-release\n\nRendering of scene in Cycles preview hard crashes whole system. System screen goes to black and the fans go to max.\n\nLoad blend file at link: brutes_set1C_trimmed.blend?dl=0\n\nSet screen to Render preview and navigate around.\n\n" ]

[ "Blender crashes when saving new texture image from texture context tab\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: Radeon RX 560 Series ATI Technologies Inc. 4.5.13541 Core Profile Context 25.20.14003.1010\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nWhen you add a texture (in my case, for displacement modifier), and make new image for the texture, if you try to save image from Texture context tab, save dialog opens, name a file and blender closes when you click \"Save as image\".\n\nDefault startup file. Default cube will do for this.\nSwitch to image editor. Make a new image, and paint something on it, but don't save it from image editor. Now, add, for example, a displace modifier. Make a new texture, and switch to Texture context. Choose an image that you made in the image editor, and you will see the option to save it in the Texture context tab. Click Save, the dialog opens. Give it a name and the moment you click \"Save as image\", Blender crashes.\n", "Blender crashes when trying to save baked by Cycles texture.\nOperating system: Windows 10 pro 64\nGraphics card: 1080TI\n\n**Blender 2.80rc2**\nBroken: Blender 2.80rc2\nWorked: (optional)\n\nBlender crash after texture baking with Cycles and trying to save to disk *\n\n\n1. Create a UV spere\n2. add a Multiresolution modifier to it\n3. Subdivide 3-4 times\n4. Go to Sculpt mode and sculpt some strokes on the subdivided sphere.\n5. Return to Object mode and add Material to the sphere\n6. Go to Texture context on the Properties tab and add new texture 1024x1024 defaults is fine\n7. Go to Shader editor and add new Image texture choosing the Untitled - previously created in step 6 texture.\n8. Switch to Cycles renderer, go to Bake tab and for type specify Normal and bake (defaults tangents etc.) \n9. Switch back to Texture context on the Properties tab and click Save - to save the baked texture.\n10. After specifying where to save the texture in my case d:\\Untitled.png click \"Save as Image\" => Blender crashes \n\nI tried this on 3 machines with rc2 and rc1.\n\nThanks,\nMartin" ]

[ "Keyframed parameters are not preserved when frame_change_post handler is used\nOperating system: Win 10 Pro\nGraphics card: GTX 1080\n\nBroken: v2.81, master, 2018-11-26\nWorked: (optional)\n\n---\n\n\n**EDIT** by @EAW \n\n\n> In the .blend file setup, the 'mesh_cache' object would instance a cube over the vertices for display in rendering. An ocean modifier is added to the object with 'Geometry' set to Displace and the 'time' parameter is keyframed over a frame range. \n> \n> Playback in the viewport shows the ocean modifier evolving shape during the animation. If the animation is rendered, the ocean modifier does not evolve over time and the render result is static.\n> \n\n\n\n> Here is a script that generates a 2d grid of vertices in the frame_change_post handler:\n> \n> ```\n> import bpy\n> \n> def frame_change_post(scene, depsgraph):\n> # Generate a 2d grid of vertices. A cube object is set to be instanced over the vertices for rendering\n> vertices = []\n> for j in range(100):\n> for i in range(100):\n> vertices.append((i * 0.05, j * 0.05, 0.0))\n> \n> mesh_cache_object = bpy.data.objects.get(\"mesh_cache\")\n> mesh_cache_object.data.clear_geometry()\n> mesh_cache_object.data.from_pydata(vertices, [], [])\n> \n> depsgraph.update()\n> \n> \n> bpy.app.handlers.frame_change_post.append(frame_change_post)\n> ```\n> \n\n\n\n\n> Here is the .blend file including the script: [keyframed_modifier_bug.blend](keyframed_modifier_bug.blend)\n> \n> How to reproduce:\n> 1. Open .blend file\n> 2. Press 'Run Script'\n> 3. Blender > Render > Render Animation\n> \n> The result is a static animation.\n\n\n**End Edit**\n\n---\n\n\n\nI have created a FlipFluids simulation in Blender 2.81 ( 2019-11-25 21:45) and added an Ocean modifier in displacement mode to the fluid_surface. Then I have baked the complete sim from within FlipFluids.\nWhen I move from keyframe to keyframe in the default timeline everything is moving as desired in the default 3D window:\nOcean modifier waves, FlipFluids waves & wake, flags, radars...\n\nWhen I render the complete animation everything EXCEPT the ocean modifier waves are moving. The ocean modifier waves remain static but the FLIPFLUIDS waves move on that surface.\nALL modifiers and elements ARE enabled for renderings. D-NOISE: AI Denoiser is on (switching denoiser off did not help).\nComputer is a HP Z800 with dual Xeons, 72 GB of vRAM and a GTX 1060.\n\nIf I render & save the keyframes manually individually by hand the ocean surface moves! Which means I get the proper result.\n\nAs its working when rendering&saving each frame manually as image (Png) and its not giving the same result when saving out the same images (Png) when I hit render animation, I do suppose this might be a bug in 2.81.\nRunning indiviual frames via Renderpilot did not yield the proper result either. So I do suspect it might be that there is not enough time gap between saving the last frame and rendering the next. Or, something does not get purged properly.\n\nFor propriatary reasons I can not share the blend file.", "Asset Browser preview generation not updating untill hovering over Preview menu\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.1\n\nWhen trying to generate an asset preview using `Render Active Object` the preview **won't display** until hovering over the `Preview` menu.\n\nOpen `Blender` -> Open `Asset Browser` -> Mark any **object** as asset -> Open `Asset Details` -> In the `Preview` Menu you will find `Render Active Object Button`\n\n[2022-12-08 21-59-59.mp4](2022-12-08_21-59-59.mp4)", "AlembicObjectPath has a fixed-size char[]\nAlembicObjectPath (see `DNA_cachefile_types.h`) has a fixed-size char- [ ] buffer. \n\n> In 3128600a8a#142412, @LazyDodo wrote:\n> if the object path can be arbitrarily large it's gonna be a matter of time before someone comes with a file with 4097 byte object path, why not just allocate the ram you need? \n\n\nI think that's a good idea, and that's what this task is for.\n", "Persistent Base of Layer brush resets when selecting another object\nOperating system: gentoo ~amd64\nGraphics card: 1060\n\nBroken: all\nWorked: none\n\nPersistent Base resets in local mode\n1 select default cube\n2 subdivide it (Edit mode > W> Subdivide to 100 > Object mode)\n3 go to sculpt mode\n4 select layer brush\n5 select \"Persistent\" chbox\n6 Push Set Persistent Base\n7 Draw\n8 Draw with CTRL (it now worked like undo brush)\nNow all good works, and i can change anu brush - super useful\nbut\n9a select any other object/collection\n9b go to other mode ant went tot sculpt mode\n9c go to local mode (hotkey /) and went back\n10 Draw with CTRL (now it don't work right - it draw without Persistent Base)\n\nPlease see my screencast\n[2020-05-26 09-58-50.mp4](2020-05-26_09-58-50.mp4)\nIn global mode all works perfect\nIn local mode Persistent Base was gone\nThank you for great opensource sculpt tool!\n\nUpdate\n[2020-05-26 10-09-57.mp4](2020-05-26_10-09-57.mp4)\nBug happend If object has been selected agane too", "Cycles does not respect Object->Holdout option.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0\nWorked: Never (Goes as far back as 3.0 where the object->holdout option is added)\n\n\nCycles does not respect Object->Holdout option.\n\n\n- Open the provided file.\n- Press render.\n- The plane which is set as \"holdout\" doesn't mask the image.\n - Expected: the region of the plane should be zero alpha.\n", "Context override of bpy.ops.object.mode_set does not work\nOperating system: Ubuntu 18.04.5 LTS\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 440.100\n\nBroken: version: 2.93.0 Beta, branch: master, commit date: 2021-05-04 23:07, hash: 96abe5ebbc55\n\nSetting the object whose edit mode you want to enter via context overrides does not work.\n\nAlthough the active object is changed via the context override, the following line still switches into edit mode of the object selected in the UI:\n\n\n\n```\nbpy.ops.object.mode_set({\"active_object\": bpy.context.scene.objects[\"Cube\"]}, mode='EDIT')\n```\n\nI also tested:\n```\nbpy.ops.object.mode_set({\n\"active_object\": bpy.context.scene.objects[\"Cube\"]\n\"object\": bpy.context.scene.objects[\"Cube\"]\n\"selected_objects\": [bpy.context.scene.objects[\"Cube\"]]\n\"selected_editable_objects\": [bpy.context.scene.objects[\"Cube\"]]\n}, mode='EDIT')\n```\n\nAnd \n\n\n```\ncontext = bpy.context.copy()\ncontext[\"active_object\"] = bpy.context.scene.objects[\"Cube\"]\ncontext[\"object\"] = bpy.context.scene.objects[\"Cube\"]\ncontext[\"selected_objects\"] = [bpy.context.scene.objects[\"Cube\"]]\ncontext[\"selected_editable_objects\"] = [bpy.context.scene.objects[\"Cube\"]]\nbpy.ops.object.mode_set(context, mode='EDIT')\n```\n\nBoth do not work.\n\nThe only thing that works is:\n\n\n```\nbpy.ops.object.select_all(action='DESELECT')\nbpy.context.view_layer.objects.active = bpy.context.scene.objects[\"Cube\"]\nbpy.context.scene.objects[\"Cube\"].select_set(True)\nbpy.ops.object.mode_set(mode='EDIT')\n```\n\nBut it would be great to be able to do that simply via context overrides, as it also can be done for other operators.\n\n- Open Startup Scene\n- Duplicate Cube\n- Select Cube.001\n- Enter \"bpy.ops.object.mode_set({\"active_object\": bpy.context.scene.objects[\"Cube\"]}, mode='EDIT')\" in console\n- > The edit mode of Cube.001 is activated, however it should be the one of Cube", "Recursive Purge Orphans datablocks on file save\nFully deleting datablocks from a blend file doesn't happen as easily as most users might expect, since \"delete\" is often used in the UI when \"un-link\" is what is actually meant. This can cause a lot of confusion and uncertainty during production. Proper deletion of datablocks requires that they are first un-linked, then they can be purged via File->Clean Up->Recursive Unused Datablocks. This works beautifully, and I would like to propose adding an option to have this operation executed after existing deletion operators. For example, after deleting a collection of objects, it would then also delete everything that was used only by those objects, such as their mesh and shape key datablocks, materials, actions, textures, etc.\n\nMy previous proposal was to have an option to execute Recursive Purge only on file save, which seemed to make sense to everyone I talked to at the time. (@dr.sybren @mont29 @JulianEisel @SimonThommes ) \nI still think that solution would be a step forward, but the new proposal above would achieve the same goals in an even more foolproof way. \n\n### Use case\nCurrently, this can very easily happen:\n- Animator duplicates an overridden character. All its objects get a .001 suffix.\n- Animator deletes that copy, saves their file, and later re-opens it. Only one \"layer\" of unused objects has been cleaned, so there can still be orphan object datablocks lying around unseen.\n- Animator duplicates the character again. Now the number suffix of their objects are all over the place. Some of them have .001 and others have .002.\n\nAs they continue working and duplicating characters, the old, unused objects slowly get deleted, and the name suffixes really get all over the place. It's not nice to get your objects names all mixed up like this, as things get really confusing when trying to troubleshoot problems in a production file, since everywhere where one object references another, the mismatching suffixes give the troubleshooter anxiety and uncertainty. The only way to avoid this currently is to tell the entire production team to always run a recursive Purge after deleting anything, which is very error-prone. \n\n\n### Potential issues\n\n- ~~The current recursive purge purges Text datablocks, which is bad because they don't have the possibility of a \"Fake User\", so they should be excluded (or better yet, be included in the \"fake user\" system, and get a fake user by default). ~~ (Fixed by [D10983](D10983))\n- Actions don't have fake user enabled by default. The long standing issue of Action datablocks \"disappearing\" on users and making them lose hours of work if they forget to click Fake User would be exacerbated by this change. This could be trivially fixed by giving Actions a fake user on creation, and forcing users to clean up their unused Actions themselves.", "Blender continuosly freezes when transforming an object\nOperating system: Ubuntu 20.04.4 LTS\nGraphics card: ntel Corporation Skylake GT2 [HD Graphics 520] (rev 07)\n\nBroken: 3.1.2\n\n\nBlender continuosly freezes when transforming an object.\n\nCreate a General project (With the default cube). Scale the cube in every direction. Continue doing this and it the app will freeze. The debug log is filled with the following message:\n\n\n> INFO (gpu.debug): Notification : memory mapping a busy \"miptree\" BO stalled and took 0.039 ms.\n\n\n\n\n", "BMain locking during the 'after liblink' doversion\nin 6a850f3cc8, `Main.is_locked_for_linking` was added, and is currently only used in versioning code (both before and after liblink), to prevent adding or deleting IDs from Main.\n\nHowever, exceptions have already been added to allow creation of workspaces and collections in that context. And {[D12722](D12722)#inline-108272} adds nodetrees to the exceptions.\n\nProblem\n----------\n\nWhile preventing before-liblink doversion to add or remove any ID makes total sense, I do not understand why after-liblink doversion should have this constraint.\n\nTo me the bug fixed by the commit is a bug in the (removed) doversion code, not something inherently forbidden at this stage?\n\nProposed Solution\n---------------------\n\nRemove that lock check altogether in after-liblink doversion.\n\nI think however that we could use that lock on all other Mains besides the one being processed (to ensure doversion code does not create/delete things outside its own scope). And do-version code there should be smart enough to check when it runs on the local main, or a lib main, and adapt its code accordingly.\n\n~~Another thing to fix is in `BKE_libblock_alloc`, which should assign `main->curlib` to the newly created ID's `id->lib` (and tag it as indirectly linked). That way if doversion needs to create an ID in a library context, that new ID is properly created as a 'virtual' indirectly linked data, and does not break Main consistency (even if doing stupid things like generating default brushes for a lib main).~~ Done in 7681326acd", "Clearing a CollectionProperty of ID pointers will dereference duplicate IDs below zero\n## Simplified Report\n\n- Execute the first script below in a new scene with a Cube.\n- The first script will add the cube 10 times to the collection property.\n- Save the file and reopen.\n- Execute the second script.\n- The second script will clear the collection.\n- The cube will get dereferenced to a user count below zero. With this assert:\n - `ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0`\n- Saving the file again and reopening will remove the cube since it has no users. Even though it was linked to the scene.\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nfor i in range(0):\n```\n item = bpy.context.window.view_layer.test_list.add()\n item.object = bpy.data.objects[\"Cube\"]\n```\n```\n\n```lang=python\nimport bpy\n\nclass TestPropertyGroup(bpy.types.PropertyGroup):\n```\n object: bpy.props.PointerProperty(type=bpy.types.Object)\n```\n\nbpy.utils.register_class(TestPropertyGroup)\nbpy.types.ViewLayer.test_list = bpy.props.CollectionProperty(type = TestPropertyGroup)\n\nbpy.context.view_layer.test_list.clear()\n```\n\n## Original Report\n\n\nOperating system: Linux-5.15.0-46-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.3.0\nWorked: version 3.1.2\n\n`ERROR (bke.lib_id): source/blender/blenkernel/intern/lib_id.c:322 id_us_min: ID user decrement error: OBCube (from '[Main]'): 0 <= 0` occurs when calling `.clear()` on a CollectionProperty attached to a ViewLayer. In the attached example, the CollectionProperty is a PropertyGroup containing a PointerProperty to bpy.types.Object.\n\n\n1. register properties and operators with provided script\n2. run `bpy.ops.view_layer.test_add_objects_operator()` to add selected objects to the view layer property\n3. save and close file\n4. open file and register properties and operators\n5. bpy.context.view_layer.test_attribute_list.clear() to get error\n\nstart with provided 'untitled.blend' to just run steps 4 and 5\n{F13493946}\n", "Auto keyframing causes Duplicate Linked object to change location \nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 3.1.0\nWorked: Never (2.8+)\n\n- Open new general animation template,\n- Turn on auto keyframing\n- Add a mesh object\n- Alt+D create few Duplicate Linked objects,\n# Change frame\n\nDuplicate Linked objects will change location.\n", "Blender keeps crashing relocating linked library [3.5.1]\nOperating system: Windows-10-10.0.25357-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\nRelocating linked library file results in instant crash when different file is chosen. I need this because i work on both OSX and Windows. While testing file version, i had issue with indirectly linked files. These are nested files so to say. They are linked blend files inside another linked blend file. \n\n- Download and Unzip attached `RML-test file-bl350.zip` file\n- open file \"RML-test file-bl350.blend\"\n- go to `Outliner` > `Blender File` and select the linked lib file with exclamation mark \"linked object\"\n- Right click and select \"Relocate\"\n- Point to the file \"linked object-bl293\"\n\nBlender file browser closes and crashes short after.\n\nSide note\nThe linked lib blend file is name \"linked object\", if i rename the \"linked object-bl293\" to \"linked object\" it works. But because i work on both OSX and Windows and sometimes also with different version. I need to rename linked files so i dont break anything.\n\nHowever, i jsut tested these 2 files in an issue folder i created and then it links just fine. When these files are linked in the original folder, blender crashes right after i pick that file \"linked object-bl293.blend\". See attached screengrab.\n\n\n", "creating a new collection in linked scene (same blend file) causes objects placed in it to dissapear from the outliner in the first scene.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\nWorked: unknown\n\nCreating a new collection in linked scene (same blend file) causes objects placed in it to disappear from the outliner in the first scene.\n\n1. Open default blender scene.\n2. Click the new scene button and choose linked copy.\n3. In the new scene, create a new collection and drag the cube into it.\n4. Go back to the first scene.\n5. The cube is gone and the new conllection not listed in the outliner.\n\n", "Linked group breaks Object Mapping in Texture Coordinates\nWindows 10\n\nBroken: 2.79b official release\n\nLinked group breaks Object Mapping in Texture Coordinates, when:\n- a texture (on a plane) uses another object (empty) as texture coordinates\n- all objects are in the same group\n\nFurther explanation in the blend file.\n\n1) Link the group \"object_mapping\" from the blend file\n2) move the group in any direction\nDespite the gradient texture on the plane using the empty's coordinates, this is completely ignored once linked as a group\n[object_mapping.blend](object_mapping.blend)", "Geometry Node boolean input socket broken when recursive linked file is reloaded in the Outliner\nOperating system: Windows 10 19044.1645\nGraphics card: GeForce RTX 3070\n\nBroken: 3.6.1, 8bda729ef4dc, branch: blender-v3.6-release, 2023-07-17\nWorked: none\n\nGeometry Node with boolean group input socket will show error \"Property type does not match input socket (socket name)\" and the input socket will not get evaluated if the recursively linked source file is reloaded in the Outliner 'Blender File' view mode.\n\nBrief description of the file linking structure\n\"01_source_GN-bool-Input.blend\" is the blend file that contains the source geometry node.\n\n\"02_GN_linked_level1.blend\" linked the \"01_source_GN-bool-Input.blend\" geometry node and using it on a local object.\n\n\"03_GN_linked_level2.blend\" linked \"02_GN_linked_level1.blend\" \"GN Cube\" object.\n\nTested with Integer input socket, works as expected in the above file linking condition.\n\n1. Open the attached blend file \"03_GN_linked_level2.blend\"\n2. In the Outliner 'Blender File' view mode (on the middle right of the UI from file), right click on the file \"//02_GN_linked_level1.blend\" and click \"Reload\"\n3. Noticed that the boolean input 'Switch' checkbox is now showing error \"Property type does not match input socket \"(Switch)\"\"\n\n" ]

[ "Render with \"linked\" object N times slower then with \"appended\". Possibly \"Persistent data\" issue when object is \"Linked\"\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.01\n\nBroken: version: 3.2.1\n\nIt seems that when object is linked, persistent data are not working and all object subcomponents are loading each frame again, which can be tedious.\n\nI could not examine the issue in detail, but in render window, it says \"synchronising object XY\" every frame of the animation.\nThis does not happen when object is directly in the scene and persistent data option is on. EDIT: actually is also syncing objects, just way faster\n\n\nLINK high-poly and texture heavy mesh with multiple objects, render, then try to APPEND it, render. \nDifference in my scene is 60sec linked vs 25sec when appended.\n\nUnfortunately I dont have any NDA-free geometry to provide\n\n" ]

[ "Running multiple instances of Cycles HIP ends in segfault\nOperating system: Windows 10\nGraphics card: 2x Radeon W6800 32GB\n\nBroken: 3.0.0, 3788003cdaeb, master, 2021-11-30\nWorked: Never\n\nWhen I have 2 instances of Cycles rendering using HIP at the same time on a particular production scene, one instance will crash with the following error: \n\n\n```\n...\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.57 | Mem:1469.81M, Peak:1469.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Furniture_Roughness.png\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.70 | Mem:1533.81M, Peak:1533.81M | Scene, View Layer | Updating Images | Loading Metal02_nrm.jpg\nFra:441 Mem:8965.99M (Peak 8965.99M) | Time:00:21.73 | Mem:1569.81M, Peak:1569.81M | Scene, View Layer | Updating Images | Loading Scene2_Garage_Objects_normal.png\nFra:441 Mem:9030.99M (Peak 9030.99M) | Time:00:21.73 | Mem:1570.69M, Peak:1570.69M | Scene, View Layer | Updating Images | Loading Tires_rough.png\nMalloc returns null: len=37748736 in Cycles Aligned Alloc, total 1149156740\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFED98C853D\nModule : amdhip64.dll\nThread : 00000734\n\n```\nI was unable to reproduce it in a simple scene or any commonly available demo scenes such as classroom or Barbarshop. And unfortunately I cannot share the particular scene that's causing the issue. But the scale of the scene that's crashing should easily fit onto the GPU vram three times.\n\nI've attached the crash report. If more info is needed I will try to create a dummy scene that show the same behavior.\n\n[Anim-A-Garage.crash.txt](Anim-A-Garage.crash.txt)", "Loop Cuts and Inset Faces cutting Meshes\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce GTX 750 TI\n\nBroken: 3.2\n\nTrying to add regular edge loops with Control + R, or even trying inset a face, they are cutting my mesh, or merging the ends. (I shared this on reddit, and it was suggested I create bug for it. \n\nAll I did was delete the bottom face of the mesh since I would not need it, but somehow I created invalid geometry and when I add an edge loop near the end it merges. If I try to inset the faces, it gives me weird end geometry.\n\n(This is what was noted from someone on Reddit: Update: just checked the file and here are my findings:\n\n```\n Adding a loop, be it length ways, long ways, or any other way seems to works just fine with the CTRL-R shortcut\n```\n\n```\n The loop cut tool also works just fine.. except if you try and loop cut around the XY plane instead of the XZ plane (drawing a line around the thinnest faces) at which point the mesh seems to collapse to zero height\n```\n\n```\n Insetting faces also works fine, be it via the tool or pressing I... but if you then try and extrude the inset suddenly the model collapses\n```\n\nOther things of note: the face orientation is inside out for this mesh (turning on Face Orientation in the Overlays menu (two overlapping circles in the header) shows them as red) and the object-level scale hasn't been applied. Fixing both of these doesn't correct any of the above issues -- although it IS normally advised since it prevents a few shading and modelling issues -- but it does, for some reason, change how the errors manifest, like the model collapsing in a slightly different way or the CTRL-R shortcut suddenly causing the same issues the tool version of loop cut and slide has.\n\nConclusion: you've somehow managed to turn this mesh into some form of invalid geometry that Blender can't seem to handle properly. You may wish to report it as a bug, including this file as a demonstration.\n\n- Open .blend file\n- enter edit mode and select face mode\n- press numpad 3 for YZ plane view\n- Add loopcut on visible face side (it'll merge the edges)\n\n---\n- repeat first 2 steps from above\n- press numpad1 for XZ plane view\n# select visible face -> extrude + scale (will merge edges). Works with inset tool\n\nTest File:\n[Issues Build2.blend](Issues_Build2.blend)", "Ngon with more edge crash blender when using Multires/Subdivision Modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha, 2.93.2, \nWorked: None\n\nPlease check the video, it shows the difference when blender deal will small ngon(edge < 10) and large ngon (~=600).\nI think it should take over aleast 5000 points ngon(for some svg file)\n[2021-08-15 17-50-41.mp4](2021-08-15_17-50-41.mp4)\n\nCreat a ngon with more than 600 points\nextrude it and add Subdivision Modifier\ncrash\n[test.blend](test.blend)\n", "AMD - Blender Crashes When I Start Render - Cycles GPU Compute\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon RX 6800 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\n\n[Whenever I start Rendering, It crashes when using cycles on GPU compute. Doesn't happen on CPU option.]\n\n[On render engine, select cycles. Then set it to GPU Compute. Then click on render on top left corner. Then select render image.]\n\n", "Set as Background crashes blender instantly.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti and RTX 3060\n\nBroken: 3.62\n\nI'm trying to do object tracking. Have tracked an object and clicked Solve Object Motion, then when I click on Set as Background Blender crashes instantly. Trying to load in a 400 frame 1920x1080 png sequence. Blender also crashes if I try to load the background image sequence via the camera properties (Background Images > Add Image).\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Blender 3.3 crashing unnecessarily/ unexpectedly/ frequently/ no apparent reason until now\nOperating system: Windows 10 Pro\nGraphics card: Intel i3\n\nBlender 3.3\n\n\n\nWhenever I open blender with some projects...whenever I enter material preview mode or try to render (sometimes even in solid mode...still slow) Whenever I try to apply a material and the crashes even when the project is simple and not finished or being rendered....it was working just fine and started to act weirdly during the last couple of days...I even tried, manually, to allocate more RAM to the program but that just crashed the whole thing. \n\n\nExact steps for others to reproduce the error:\n\nopen the blender file I attached as an example (The project that blender doesn't tolerate) try to apply a texture or render \n\nNOTE: I'm looking for a software solution...I don't think reproducing the error on a RTX 3090 is fair...so...we'll probably look for software solution or tweak the settings.\n\n", "Blender crashes in edit mode in wireframe view\nOperating system: Linux Mint 21.1\nGraphics card: geforce gtx 1060\n\nBroken: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc, type: release\nWorked: 3.5.1\n\nOn the attached file, selecting the bear head and going into edit mode, then switching to wireframe, or switching to edit mode while in wireframe mode, blender crashes and exit.\n\nSelect the bear head, switch to edit mode in wireframe. It crashes. It doesn't happen with a default cube in an empty file. The bear has geometry node hairs attached to it on the fur layer, but the geometry nodes are disabled. It also has an armature.\n\nThe problem also happens on windows10 on the same computer.", "Knife Tool produces bad geometry in certain cases (disconnected edges/vertices, overlapping faces)\nif i use tools knife i see this bug.\n\n\n\n", "Box with beveled vert will damage, if use multires modifier in simple mode.\nOperating system: Fedora 32, 64bit\nGraphics card: GTX 650Ti\n\nBroken: version: 2.91.0 Alpha\nWorked: blender-2.82a-windows64\n\nAdd cube, bevel one vert (1 segments) add multires modifier, select simple mode, and subdivide 2 or 3 times. Mesh will damaged.\nIf beleled 2 or more verts subdivision works stability, but not always. Sometimes it will damaged, sometimes properly.", "Crash when baking Dynamic Paint Image Sequence multiple times in loop\nBroken: 2.90.0 Alpha\nWorked: blender-2.80-windows64\n\nBlender crashes when baking dynamic paint image sequence in for loop. Depending on wait time crash will have differens stack traces.\n\n[#74052.blend](T74052.blend)\n\n- Open file\n- Run script", "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "Particle Edit mode for non hair particles - point select mode crash\nOperating system: Linux-5.6.0-050600-lowlatency-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.64\n\nBroken: version: 2.90 (sub 3)\n\nBlender crashes when entering into the Particule Edit mode\n\n- Delete all objects from the default scene\n- Create a plane\n- Add a particle system\n- Set end frame to 50\n- Bake the particle system\n- Switch to the Particle Edit mode\n- Select Point select mode\n\n- > Crash\n\n[blender.crash.txt](blender.crash.txt)\n\n\n", "Viscoelastic springs (particle system fluid emitter) crashes blender 2.90.1 (and probably in all versions)\nOperating system: Windows 10\nGraphics card: Nvidia GTX 1060 6gb\nCPU: Ryzen 7 3700x\n\nBroken: 2.90.1, 2.91, 2.92\nWorked: 2.83.x\n\nEnabling viscoelastic springs and try playing the simulation, or baking, it will crash at about frame 5. However when you put springs settings to 0 and turn on it doesn't happen, but doesn't have any effect either.\nThe project files I provide is for 2.90.1. the setup is default cube with particle system, below it another cube with collision with default settings.\n\n[BrokenViscoelastics.blend](BrokenViscoelastics.blend)\n\n- Open the attached file\n- Enabled Vicoelastic Springs\n- Bake", "3D cursor sometimes can't do absolute grid snap\nOperating system: windows 10 v2004\nGraphics card: GTX 970\n\nBroken: 2.83.5\nWorked: none\n\n3D cursor sometimes can't do absolute grid snap.\nHere is the link of the bug capture. \n[Bug capture on YouTube](QzOqgiRM97c)\n\n\n\nDon't know how to reproduce from scratch, but many of my blender files has the same problem.\n[base.blend](base.blend)", "Suspected asset library crash by `json_sax_dom_parser`\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nI dont completely know why but blender crashes very often for me.\nIts doing something no idea what it is doing.\nSorry for being vague, but it seems to mostly happen when i have the viewport set to cycles render and i am trying to modify materials, in the shader editor.\n\n" ]

[ "[2.8 Crash] Program crash when extruding+face snap\nwin 7 x64 \nNvidia 1070 (Gigabyte G1) Drivers: 398.36\n\nBroken: Hash: 66a00b64c5c (date: 2018-07-29 02:12)\n\nCrashes when extruding.\nThe windows console prints this error after crash\n\n\n\n\n1-Open [crash3.blend](crash3.blend)\n2- Select an edge of the \"RETOPO\" object\n3- use E to extrude. \n4-if doesn't crash try a few times. \n\n[Demo Video]\nI know that video its not the way to report bugs but i wasn't able to get an example to properly crash first try, the crashes in the video are lucky first try crashes.\nwatch?v=lyjg734Tg2o\n" ]

[ "Rendering animation using \"Generate\" type modifiers after animated displacement texture crashes Blender\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0 Alpha\nWorked: 2.83.10\n\nIf 2 high poly (~100k faces per obj) objects in modifiers properties have after Displacement modifier (with animated texture) \"Generate\" type modifiers (I've tried Boolean and Decimate), Blender cant run Animation render (but still can run Image render). \nCrash happens on 2.9 and higher. I've tested this on 2.83.10 LTS (from steam) and everything worked fine there.\nCrashes with Decimate a little bit hard to recreate. So I will go with steps for \"Boolean crash\"\n\n- create Cude, Empty and Icosphere\n- Add Subdivision mod. to Cube: set it to \"Simple\" and 7 levels\n- Add Displacement mod. to Cube and set texture (Clouds) coordinates to object - Empty\n- Add Boolean mod. (difference) and select object Icosphere\n- Select Cude with Icosphere and duplicate them\n- Save and press Render Animation\n[bug.blend](bug.blend)\n[bug.crash.txt](bug.crash.txt)\n\n```lines\n## 3883==ERROR: AddressSanitizer: heap-use-after-free on address 0x61500034ec08 at pc 0x000016fc795d bp 0x7fffc19dd6c0 sp 0x7fffc19dd6b0\nREAD of size 8 at 0x61500034ec08 thread #15\n - 0 0x16fc795c in blender::gpu::GLBatch::verts_(int) const /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112\n - 1 0x17013501 in blender::gpu::GLVertArray::update_bindings(unsigned int, GPUBatch const*, blender::gpu::ShaderInterface const*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_array.cc:124\n - 2 0x16fa900b in blender::gpu::GLVaoCache::vao_get(GPUBatch*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:273\n - 3 0x16fa84d8 in blender::gpu::GLVaoCache::base_instance_vao_get(GPUBatch*, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:234\n - 4 0x16fa9d3e in blender::gpu::GLBatch::bind(int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:317\n - 5 0x16fa9f3f in blender::gpu::GLBatch::draw(int, int, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.cc:328\n - 6 0x16eca2be in GPU_batch_draw_advanced /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_batch.cc:282\n - 7 0x16fc1207 in blender::gpu::GLDrawList::append(GPUBatch*, int, int) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_drawlist.cc:122\n - 8 0x16efa9f5 in GPU_draw_list_append /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_drawlist.cc:52\n - 9 0x5978acc in draw_indirect_call /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:598\n - 10 0x5978acc in draw_call_batching_flush /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:795\n - 11 0x597c5f0 in draw_call_batching_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:891\n - 12 0x597eae7 in draw_shgroup /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1056\n - 13 0x597f89f in drw_draw_pass_ex /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1113\n - 14 0x597fe50 in DRW_draw_pass /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager_exec.c:1153\n - 15 0x5c51bc0 in EEVEE_velocity_resolve /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:466\n - 16 0x5c5202b in EEVEE_draw_effects /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_effects.c:486\n - 17 0x5a21f42 in EEVEE_render_draw /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_render.c:671\n - 18 0x59b1dbc in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:559\n - 19 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 20 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 21 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 22 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 23 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 24 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 25 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 26 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 27 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 28 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 29 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 30 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n - 31 0x7ffff6f46292 in __clone (/lib/x86_64-linux-gnu/libc.so.6+0x122292)\n\n0x61500034ec08 is located 8 bytes inside of 512-byte region [0x61500034ec00,0x61500034ee00)\nfreed by thread #15 here:\n - 0 0x7ffff76927cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)\n - 1 0x18e0eab0 in MEM_lockfree_freeN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:129\n - 2 0x16ef56c6 in blender::gpu::GLVertBuf::operator delete(void*) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x17018021 in blender::gpu::GLVertBuf::~GLVertBuf() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:35\n - 4 0x16f8bb19 in blender::gpu::VertBuf::reference_remove() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer_private.hh:94\n - 5 0x16f877f5 in GPU_vertbuf_discard /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:161\n - 6 0x5a0eab8 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:449\n - 7 0x59b1bef in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:542\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\npreviously allocated by thread #15 here:\n - 0 0x7ffff7692bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)\n - 1 0x18e0f510 in MEM_lockfree_mallocN /home/dev/01-data/01-git/blender-git/blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:276\n - 2 0x16ef5676 in blender::gpu::GLVertBuf::operator new(unsigned long) /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_vertex_buffer.hh:57\n - 3 0x16ef70a2 in blender::gpu::GLBackend::vertbuf_alloc() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_backend.hh:121\n - 4 0x16f85d10 in blender::gpu::VertBuf::duplicate() /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:77\n - 5 0x16f8750d in GPU_vertbuf_duplicate /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/intern/gpu_vertex_buffer.cc:149\n - 6 0x5a0ee06 in EEVEE_motion_blur_cache_finish /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_motion_blur.c:467\n - 7 0x59b1953 in eevee_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/engines/eevee/eevee_engine.c:507\n - 8 0x5948820 in DRW_render_to_image /home/dev/01-data/01-git/blender-git/blender/source/blender/draw/intern/draw_manager.c:1909\n - 9 0x14ff1d77 in engine_render_view_layer /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:786\n - 10 0x14ff40a3 in RE_engine_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/engine.c:914\n - 11 0x1501aafb in do_render_3d /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1132\n - 12 0x1501c24a in do_render /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1209\n - 13 0x1501e036 in do_render_composite /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1349\n - 14 0x15022789 in do_render_all_options /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:1615\n - 15 0x15027839 in RE_RenderFrame /home/dev/01-data/01-git/blender-git/blender/source/blender/render/intern/pipeline.c:2015\n - 16 0xd7b42cf in render_startjob /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:630\n - 17 0x4fed4f1 in do_job_thread /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:389\n - 18 0x18de408d in tslot_thread_start /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:231\n - 19 0x7ffff7566608 in start_thread /build/glibc-ZN95T4/glibc-2.31/nptl/pthread_create.c:477\n\nThread #15 created by T0 here:\n - 0 0x7ffff75bf805 in pthread_create (/lib/x86_64-linux-gnu/libasan.so.5+0x3a805)\n - 1 0x18de42b9 in BLI_threadpool_insert /home/dev/01-data/01-git/blender-git/blender/source/blender/blenlib/intern/threads.cc:245\n - 2 0x4fee516 in WM_jobs_start /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_jobs.c:484\n - 3 0xd7b88bd in screen_render_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/render/render_internal.c:1041\n - 4 0x4f8f3ba in wm_operator_invoke /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1293\n - 5 0x4f912f2 in wm_operator_call_internal /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1500\n - 6 0x4f91551 in WM_operator_name_call_ptr /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:1548\n - 7 0x90f1c95 in ui_apply_but_funcs_after /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:932\n - 8 0x917b8d0 in ui_handler_region_menu /home/dev/01-data/01-git/blender-git/blender/source/blender/editors/interface/interface_handlers.c:10809\n - 9 0x4f88a9b in wm_handler_ui_call /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:636\n - 10 0x4f9ec36 in wm_handlers_do_intern /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2757\n - 11 0x4f9fc78 in wm_handlers_do /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:2865\n - 12 0x4fa537f in wm_event_do_handlers /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm_event_system.c:3288\n - 13 0x4f732cf in WM_main /home/dev/01-data/01-git/blender-git/blender/source/blender/windowmanager/intern/wm.c:635\n - 14 0x34f58fa in main /home/dev/01-data/01-git/blender-git/blender/source/creator/creator.c:522\n - 15 0x7ffff6e4b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /home/dev/01-data/01-git/blender-git/blender/source/blender/gpu/opengl/gl_batch.hh:112 in blender::gpu::GLBatch::verts_(int) const\nShadow bytes around the buggy address:\n 0x0c2a80061d30: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d40: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d50: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d60: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fa\n 0x0c2a80061d70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n# >0x0c2a80061d80: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061d90: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061da0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061db0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c2a80061dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c2a80061dd0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\nShadow byte legend (one shadow byte represents 8 application bytes):\n```\nAddressable: 00\nPartially addressable: 01 02 03 04 05 06 07 \nHeap left redzone: fa\nFreed heap region: fd\nStack left redzone: f1\nStack mid redzone: f2\nStack right redzone: f3\nStack after return: f5\nStack use after scope: f8\nGlobal redzone: f9\nGlobal init order: f6\nPoisoned by user: f7\nContainer overflow: fc\nArray cookie: ac\nIntra object redzone: bb\nASan internal: fe\nLeft alloca redzone: ca\nRight alloca redzone: cb\nShadow gap: cc\n```\n", "Hair particles crashing when baking or animating\nOperating system: windows 10 64 , windows 8 64\nGraphics card: intel, nvidia\n\nBroken: blender-2.81-9bd0d8b5505a-windows64\nWorked: (optional)\n\nwhen trying to bake a hair particles the system hangs giving this message\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7CEBD24A4\nModule : C:\\Users\\dribeiro\\Desktop\\blender-2.81-9bd0d8b5505a-windows64\\blender.exe\n\n\nopen the file\nclick 'play' on timeline or bake on hair particles\n\nNEW INFO\nremoving the hair particles the animation runs normally\n[giselle.blend](giselle.blend)", "Blender crashes after GPU spike (Specially when we have a character with Rigify)\nOperating system: Windows 10\nGraphics card: RTX 2070 Super\n\nBroken: 3.4.1\nWorked: 3.3\n\nEvery time I'm working in Blender, after 2 minutes if I start to move around on a rig made based on Rigify, or work on geometry nodes, Blender Crashes. It happens even faster if I'm working in eeve.\n\n- Open a blender file\n- Import a character using rigfy with Linked Library\n- Library override\n- Turn Eeve on\n- Start working\n- Eventually, blender will crash.\n\nI noticed that if I don't import a character with rigfy, it doesn't have the GPU spike\n[Christmas.crash.txt](Christmas.crash.txt)\n[KalyAndAkrasiel 3.5.crash.txt](KalyAndAkrasiel_3.5.crash.txt)", "Blender GUI freezes when using activate_init = True\nOperating system: W10 64bit\nGraphics card: nVidia GTX 970\n\nBroken: blender-2.83-71b1ee940bb0-windows64\n\n\nOnce this bug T71112 was fixed I tried to \"use activate_init = True\" in my addon, but I'm still getting Blender GUI to freeze.\n\n* Open up [bugreport.blend](bugreport.blend) and run the script in Text Editor\n* Search for \"Name Location\" operator and run it\n* Type a text and hit OK. An Empty object is placed into the scene, named by what you typed in, but whole GUI becomes unresponsive.\n", "Blender 3.2 crashes on opening a specific file\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: 3.2.0\nWorked: unknown\n\n**problem**\nBlender immediately crashes when opening the file steam_engine.blend\n\nThe latest object I was working on, was UV-unwrapping a mesh which I think I called 'greenthingy' or something like that. There was no crash prior to re-opening the file. I attach the file (hope it's not too big and apologies for the mess...). crash report and system_info.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[steam_engine.crash.txt](steam_engine.crash.txt)\n\n**Steps for others to reproduce the error**\n[steam_engine.blend](steam_engine.blend)\n[#99105.blend](T99105.blend)\n\nAfter opening `steam_engine.blend` file Blender crashes. \n`#99105.blend` is same file as `steam_engine.blend`, but material preview panel has beeen collapsed. This file does not crash. Interestingly it does not crash even when panel is re-opened. Tested with GPU and CPU\n", "Blender freezes when using Texture paint or Weight Paint\nOperating system: Windows 10 Insider build19592\nGraphics card: GTX 1660Ti Max Q 6GB\nProcessor: i7-9750H\nRAM: 32GB DDR4-2666Mhz\n\nBroken: version: 2.83 (sub 11)\nWorked: Never (2.79, 2.8+)\n\nBlender freezes or stops responding when using Texture Paint or Weight Paint. Tried game ready and Studio drivers, still the same issue.\nMoreover, RAM consumption spikes up to more than 20GB. This happens when the brush size is increased and starts painting. \n\nAssigned GPU in Preferences>System>CUDA, but the GPU is been barely used.\n\n[Blender.rar](Blender.rar)", "Frequent crashes when performing minor adjustments with rigid body constraints\nOperating system: macOS-11.5.2-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) UHD Graphics 630 Intel Inc. 4.1 INTEL-16.5.2\n\nBroken: version: 3.0.0 Alpha\n\nWith a simple rigid body setup (see attached file), there are frequent crashes when doing simple adjustments such as moving the constraint around, rotating it, starting/stopping the animation, undoing some steps. There is not a single scenario leading to a crash, but performing a combination of these actions in succesion consistently leads to a crash (segmentation fault) within about 30-60s.\n\n[Rigid body crash.blend](Rigid_body_crash.blend)\n[Rigid body crash.txt](Rigid_body_crash.txt)\n\nI closed #91025 because I thought it was fixed, but it turns out the crashes still occur. I have found one reproducible way to get the crash:\n- With factory preferences, open attached blend file.\n- Press spacebar to start the animation\n- Press command-Z to undo and then shift + left arrow to restart at the first frame\n- Repeat the last step (command + z and then shift + left arrow) a few times\n- Blender will crash usually after repeating 2-3 times, sometimes a few more.\n", "Crash Guide during render complete 2 December 9, 2022\nOperating system: macOS-13.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.51\n\nBroken: version: 3.4.0\n\nCrash Guide during render 2\n\nSame crash guide during render before and today.\nSee youtube: ZeCA2p5wISY\n\nHistory previous.\nT100691\n\n\n\n\n[Blender-2022-12-09-161546.ips](Blender-2022-12-09-161546.ips)\n\n[Horizontal Video.zip](Horizontal_Video.zip)", "blender crash if boolean + very very big scale\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.2.1, 3.2\n\n[2022-07-21 19-15-24.mp4](2022-07-21_19-15-24.mp4)\n\n1. add boolean modifier\n2. scale any object on very very big value", "It says when I try to put my render into the downloads file permission denied can somebody help?\nOperating system: ?\nGraphics card: ?\n\nBroken: ?\nWorked: ?\n\n?\n\n?", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Crash while using several rigid bodies and some force fields.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon R9 M370X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nThe scene is pretty simple, a house with some elements used as rigid bodies and some force field, vortex and wind force are applied.\n\nWhen I play the animation, it starts and around frame 140-200 it crashes.\n\nAttached blend file. The only thing to do is to play the animation and wait for the crash.\nAttached crash report.[Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash](Blender_2019-08-26-215345_MacBook-Pro-de-Kote.crash)\n\n[casaFalla.blend](casaFalla.blend)\n\n", "Viewport animation render crashes when collapsing the viewport.\nBroken: version: 2.91.0 Beta (and 2.83, 2.80, ...)\nWorked: never\n\nViewport animation render crashes when collapsing the viewport.\n\n[0001-0485.mp4](0001-0485.mp4)\n[Viewport render crash.blend](Viewport_render_crash.blend)\n\n", "Mantaflow: Crash when setting a Guide Fluid Effector\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.3.0\n\nAfter setting a mesh as a \"Guide\" fluid effector, checking the \"Guides\" box in the fluid domain settings crashes Blender. \n\n- Open attached file,\n- go to the fluid domain settings\n- check the \"Guides\" box. \n[Fluid_Guide_Crash_01.blend](Fluid_Guide_Crash_01.blend)\n\n", "Blender crashes after rendering a few frames of an animation\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\nI've never had this kind of problem - Blender crashes randomly after rendering a few frames of the animation. The only \"new\" thing I'm doing is I started using geometry nodes in this scene. I have plenty of VRAM left, shouldn't be a GPU issue. Tried both in 3.4 and 3.5\n\n\n" ]

[ "Animations/Actions not working in BGE\nasus laptop\n{[F152046](BUNNYgame.blend1)}win 8.1 64bit\n8gb ram\n500gb hdd\nnvidia geforce 720m 2gb ram\n\n**Broken:2.73a**\nWorked: 3 weeks\n\n**i have properly set up my action in my logic editor but the actions/animations don't play at all.**\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Specific Rig Crashes blender when going into pose mode\nOperating system: Linux-5.10.7-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 2.92.0 Alpha\nWorked: not sure but pre 2.80\n\nThis specific file, containing only one armature, crashes when selecting the armature and attempting to enter pose mode.\n\nFirst load the included file, then:\n- select the rig if it isn't already selected,\n- press ctrl tab or otherwise enter pose mode\nat this point blender crashes.[bug_posemode.blend](bug_posemode.blend)\n\n", "Render cause crash guide many time August 10, 2022\nOperating system: macOS-13.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.39\n\nBroken: version: 3.2.2\n\nRender crash too many\n\nFor Mac only. Do not use Windows please.\n\n\n\n\n\nSee blender 3.2.2 on Cycle-x picture\n\n\nCommand + F12 then render for a while few minutes cause crash many times.\n\n[Blender report a ticket August 10 2022.zip](Blender_report_a_ticket_August_10_2022.zip)", "Cycle crash\n[System Information](https://projects.blender.orgattachment)\n\nBlender version: 3.4.1\n\nCrash when switching from Material Preview to Rendered in Viewport Shading and GPU Compute was set for Cycles. In CPU mode it's OK.\n\n\nOpen project.\nSelect CPU in Cycles settings.\nSwitch from Material preview to Rendered in Viewport shading.\nNow it works.\nChange to GPU Compute in Cycles settings.\nCrash...\n\n", "dual monitor will sometimes cause blender to freeze\nOperating system:win10\nGraphics card:2080s\n\nBroken: 3.4.1\nWorked: \n\ni have two monitors (4k and 2k) scrolling timeline or doing anything on one monitor and displaying cycles render viewport on the other monitor will sometimes cause blender to freeze forever\n\nit is not specific to this scene it will freeze on all kinds of scenes, might be related to the muti-monitor bug i have been reporting T96248\nhere is a screenshot of what it looks like when freezing \n\nmake some animation\nhave 2 monitors and use cycles rendered view on one monitor and scrolling timeline on the other monitor", "Eevee crashes when rendering some of the Blender Studio rigs\nOperating system: Windows 10 Home\nGraphics card: Intel(R) HD Graphics 4600\n\nAlso tested on Debian 11 on both GNOME and MATE. It didn't make much of a difference, the GNOME session crashes and takes me back to the login manager meanwhile on MATE the program gets killed after it freezes for too long. I'd say that this is just a difference in the behaviour of the two desktop environments, but I can't say for sure.\n\nAlso asked a friend of mine to test it on their MacBook Pro, they claim to have seen the same results as I have. Just keep in mind that they're busy and I don't have access to their hardware.\n\nTried opening it on multiple versions:\n3.0.1 (stable), 3.5.1 (stable) and 4.0.0 (alpha) with [66d20c8723e6](66d20c8723e6) being the latest commit.\n\n(Windows/Linux/Mac)\nWhen opening it from the list of recent files I see the Blender project being displayed on the screen, but apparently for only one frame then freezes. I can see the prompt that asks for script execution to be enabled, the model itself, the pose library, etc. It just freezes afterwards.\nSame thing happens for when opening it via File -> Open, but I only see the default cube project before the crash.\nGot it from .\n\n1. Run Blender\n2. Open `ellie_animation.blend`\n\nSomething else worth noting is that apparently a group of people on the Blender Artists forums are experiencing the same issue: 1342795\n\n`blender-stdout.txt` and `blender-stderr.txt` were generated like so:\n`C:\\Users\\Mustafa\\blender-4.0.0-alpha+main.66d20c8723e6-windows.amd64-release>blender --factory-startup --debug-all > blender-stdout.txt 2> blender-stderr.txt`\nI've even provided a file (`gdb-blender.txt`) containing the output of interactively debugging blender with the GNU Debuger, in case you'll need it.\nAll debug logs and related files were created on Windows.\n\nThanks in advance! It'd take a miracle to get such a huge open source project going and you're doing a great job, I appreciate your hard work on Blender.\n", "Intel GPUs: 3.6.2 crash on initializing Eevee rendered view\nOperating system: Linux-6.5.3-300.fc39.x86_64-x86_64-with-glibc2.38 64 Bits, WAYLAND UI\nGraphics card: Mesa Intel(R) Arc(tm) A770 Graphics (DG2) Intel 4.6 (Core Profile) Mesa 23.2.0-rc3\n\nBroken: version: 3.6.2\nWorked: 6 months ago :)\n\nBlender crashes when you opened the attached project and switch to rendered view.\n\n", "Blender crashes with Noise Texture Node + Hair Particle System + Eevee\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon RX 480 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.18\n\nBroken: 8dc95f61f3\nBroken: version: 2.92.0\nBroken: version: 2.91.2\nWorked: version: 2.83.12\n\nBlender 2.92 with AMD crashes with **Noise Texture Node**and **Hair Particle System** with render engine Eevee.\nWith Blender 2.91.2 with AMD it doesn't crash but colors are incorrect.\n\nWith 8dc95f61f3 with Intel GPU, there's no crash but colors are incorrect in the same way as in AMD - 2.91.2.\n\n1. Open attached .blend file\n2. Viewport shading to: Render \n3. Play animation by tapping space bar\n\n[particle_loop.blend](particle_loop.blend)\n[blender_2_92_crash.txt](blender_2_92_crash.txt)\n\n**Blender 2.92**\n[blender_2_92.mp4](blender_2_92.mp4)\n\n**Blender 2.91**\n[blender_2_91_2.mp4](blender_2_91_2.mp4)\n\n**Blender 2.83.12**\n[blender_2_83_12.mp4](blender_2_83_12.mp4)", "Pack UV's crashes blender\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken: version: 3.6.0\n\nwith all uv's selected, using \"pack uv's\" crashes blender\n\nopen provided file. Go in edit mode. Select all\nin uv editor go UV > Pack UV\n\nBlender crashes\n\n", "Blender crashes if simplify is turned on while baking multires\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14742 Core Profile Context 21.7.2 27.20.22021.1002\n\nBroken: version: 3.0.0 Alpha\nWorked: --\n\n\nBlender crashes if simplify is turned on while baking multires data\n\n\n- Grab any object and add multiresolution to if, subdivide at least once.\n- Activate simplify, and turn the max subdivisions on viewport to 0\n- Create a material and try to bake the multiresolution. Blender will crash instead of giving an error message or just baking normally \n\nTest File:\n[multires_crash.blend](multires_crash.blend) ", "Blender 3.5.1 keeps crashing on occasion\nOperating system: Mac OS Ventura 13.3.1 (a) (22E772610a)\nGraphics card: Apple M1 Ultra (64-Core GPU)\n\nBroken: Version 3.5.1 (3.5.1 2023-04-25)\nWorked: N/A\n\nBlender occasionally crashes on my new Mac Studio (I used to work on a Windows PC beforehand and never had that problem). I'm guessing it is a saving error.\n\n- Download and open the demo-file `Blender 3.4 – “Charge” Open Movie` from demo-files/\n- Change the engine from Eevee to Cycles GPU\n- Set \"Viewport Shading\" to \"Rendered\" - nothing happens\n- Go back to Solid View - blender freezes\n\nAttached is is a video demonstrating what is happening, but in a few words:\n\nThe same happens with some of my heavy(ish) project in 3.6.0 beta\n\nIn 3.5.1 the same project responds in render view as it should be.\n\nWhen I try to reopen the same project blender doesn’t load the project but either freezes or crashes ( one of these crash logs is also attached)\nI manage to reopen the project after a few crashes.\n\nI hope it helps! \n\n\n", "Crash going to material preview or rendered shading mode Blender 2.83.0\nMacBook Pro 15 inch Early 2013\n2.7 GHz Intel Core i&\n16 GB 1600 Mhz DDR3\n|Operating system:|MacOS 10.12.5 - @Tramfabriek\n| -- | -- |\n||Mac OS X 10.12.6 (16G2136) - @johan-eds\n|| macOS 10.12.6 - @UmbertoOldani\n\n|Graphics card:|NVIDIA GeForce GT 650M 1024 MB + Intel HD Graphics 4000 1536 MB - @Tramfabriek\n| -- | -- |\n||NVIDIA GeForce GTX 775M, PCIe, 2048 MB - @johan-eds\n|| NVIDIA GeForce GTX 680MX 2048 MB - @UmbertoOldani\n\nBisected to find the bad commit: 804e90b42d\n\nCrash when clicking on Viewport Shading >Material Preview or >Rendered\nThis did happen already in the 2.83 betas, but none of the 2.82 and earlier version had this problem on this computer running this same OS at least since Blender 2.79.\n\n**System crash report 1** (crash in `UI_draw_roundbox_aa` -> `GPU_batch_draw `. Probably the material render icon):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff909add42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff90a9b457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff909134bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff9091342f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff88cdbfbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff76297390 0x7fff7607a000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff88cdd524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff76385867 0x7fff7607a000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff763554fd 0x7fff7607a000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff76282a2b 0x7fff7607a000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff7626ee9a 0x7fff7607a000 + 2051738\n11 com.apple.GeForceGLDriver \t0x00007fff76289654 0x7fff7607a000 + 2160212\n12 com.apple.GeForceGLDriver \t0x00007fff7626af97 0x7fff7607a000 + 2035607\n13 com.apple.GeForceGLDriver \t0x00007fff763851ad gldUpdateDispatch + 1041\n14 GLEngine \t0x00007fff7ff1d32a gleDoDrawDispatchCoreGL3 + 520\n15 GLEngine \t0x00007fff7fecebd9 gleDrawArraysOrElements_Entries_Body + 128\n16 GLEngine \t0x00007fff7fecaab4 glDrawArraysInstanced_GL3Exec + 220\n17 org.blenderfoundation.blender \t0x0000000109614f2c GPU_batch_draw_advanced + 428\n18 org.blenderfoundation.blender \t0x0000000109614d6c GPU_batch_draw + 124\n19 org.blenderfoundation.blender \t0x0000000105218c51 UI_draw_roundbox_aa + 353\n20 org.blenderfoundation.blender \t0x0000000104f3d96c ED_region_do_draw + 1372\n21 org.blenderfoundation.blender \t0x0000000104b6d49c wm_draw_update + 2092\n22 org.blenderfoundation.blender \t0x0000000104b6b010 WM_main + 48\n23 org.blenderfoundation.blender \t0x0000000104827762 main + 962\n24 libdyld.dylib \t0x00007fff9087f235 start + 1\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5b521f78 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5b521fa0 rsp: 0x00007fff5b521f78\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x000000011ab85cf8 r13: 0x0000000000000000 r14: 0x00007fff998033c0 r15: 0x000000011ab85000\n rip: 0x00007fff909add42 rfl: 0x0000000000000206 cr2: 0x00007fff960d0b58\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n\n**System crash report 2** (crash in `blf_batch_draw ` -> `GPU_batch_draw `):\n```lines=10\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 libsystem_kernel.dylib \t0x00007fff8b1dfd42 __pthread_kill + 10\n1 libsystem_pthread.dylib \t0x00007fff8b2cd457 pthread_kill + 90\n2 libsystem_c.dylib \t0x00007fff8b1454bb __abort + 140\n3 libsystem_c.dylib \t0x00007fff8b14542f abort + 144\n4 libGPUSupportMercury.dylib \t0x00007fff83587fbf gpusGenerateCrashLog + 158\n5 com.apple.GeForceGLDriver \t0x00007fff71040390 0x7fff70e23000 + 2216848\n6 libGPUSupportMercury.dylib \t0x00007fff83589524 gpusSubmitDataBuffers + 560\n7 com.apple.GeForceGLDriver \t0x00007fff7112e867 0x7fff70e23000 + 3192935\n8 com.apple.GeForceGLDriver \t0x00007fff710fe4fd 0x7fff70e23000 + 2995453\n9 com.apple.GeForceGLDriver \t0x00007fff7102ba2b 0x7fff70e23000 + 2132523\n10 com.apple.GeForceGLDriver \t0x00007fff71017f8e 0x7fff70e23000 + 2051982\n11 com.apple.GeForceGLDriver \t0x00007fff7100b6bc 0x7fff70e23000 + 2000572\n12 com.apple.GeForceGLDriver \t0x00007fff7100bec2 0x7fff70e23000 + 2002626\n13 com.apple.GeForceGLDriver \t0x00007fff7101113f 0x7fff70e23000 + 2023743\n14 com.apple.GeForceGLDriver \t0x00007fff7143f25e 0x7fff70e23000 + 6406750\n15 com.apple.GeForceGLDriver \t0x00007fff7143f4e6 0x7fff70e23000 + 6407398\n16 com.apple.GeForceGLDriver \t0x00007fff7143f5d7 0x7fff70e23000 + 6407639\n17 com.apple.GeForceGLDriver \t0x00007fff71013d3d 0x7fff70e23000 + 2035005\n18 com.apple.GeForceGLDriver \t0x00007fff7112e1ad gldUpdateDispatch + 1041\n19 GLEngine \t0x000000011925232a gleDoDrawDispatchCoreGL3 + 520\n20 GLEngine \t0x0000000119203bd9 gleDrawArraysOrElements_Entries_Body + 128\n21 GLEngine \t0x00000001191ffab4 glDrawArraysInstanced_GL3Exec + 220\n22 org.blenderfoundation.blender \t0x000000010b288f2c GPU_batch_draw_advanced + 428\n23 org.blenderfoundation.blender \t0x000000010b288d6c GPU_batch_draw + 124\n24 org.blenderfoundation.blender \t0x000000010b283d82 blf_batch_draw + 418\n25 org.blenderfoundation.blender \t0x000000010b282359 BLF_batch_draw_end + 9\n26 org.blenderfoundation.blender \t0x0000000106fc2163 view3d_draw_region_info + 8515\n27 org.blenderfoundation.blender \t0x0000000106936dbd DRW_draw_callbacks_post_scene + 445\n28 org.blenderfoundation.blender \t0x00000001069376cd DRW_draw_render_loop_ex + 1757\n29 org.blenderfoundation.blender \t0x0000000106fc2668 view3d_main_region_draw + 136\n30 org.blenderfoundation.blender \t0x0000000106bb157e ED_region_do_draw + 366\n31 org.blenderfoundation.blender \t0x00000001067e149c wm_draw_update + 2092\n32 org.blenderfoundation.blender \t0x00000001067df010 WM_main + 48\n33 org.blenderfoundation.blender \t0x000000010649b762 main + 962\n34 libdyld.dylib \t0x00007fff8b0b1235 start + 1\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff598ab4b8 rdx: 0x0000000000000000\n rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff598ab4e0 rsp: 0x00007fff598ab4b8\n r8: 0x0000000000000000 r9: 0x0000000000989680 r10: 0x0000000008000000 r11: 0x0000000000000206\n r12: 0x0000000120bebcf8 r13: 0x0000000000000000 r14: 0x00007fff93fe13c0 r15: 0x0000000120beb000\n rip: 0x00007fff8b1dfd42 rfl: 0x0000000000000206 cr2: 0x00007fff8b1c727d\n \nLogical CPU: 0\nError Code: 0x02000148\nTrap Number: 133\n```\n\n1. Open Blender\n2. Click to remove start up information panel\n3. Click on Viewport Shading >Material Preview or >Rendered\n\nResult:\nCrash", "Blender crash after maximizing/unmaximizing an editor (debug build only)\n\nBroken: master - debug build\nWorks: master - release build\nOS: Tested on both Windows and Linux\n\nWith a debug build, Blender crashes after maximizing an editor + moving mouse + unmaximizing.\nIt does not seem to be reproducible with a release build.\n\n\n- Open Blender default scene\n- Maximize the 3D viewport with CTRL+SPACE\n- Move the mouse\n- Unmaximize with CTRL+SPACE\n\n**Debug info**\nThe crash happens in `wm_event_do_handlers` when calling `wm_region_tag_draw_on_gizmo_delay_refresh_for_tweak(wmWindow *win, bScreen *screen)`.\nIn that case, `screen` points to invalid (freed?) memory.", "Crash when using OCIO v2\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.0.0 Release Candidate\n\nWhen I used OCIO v2 config file and used Cycles for rendering with Optix, it worked for viewport rendering. But if I pressed F12 for final render, Blender 3.0 crashed when the render was finsihing.\nI tried with a few scenes even if the Blender default scene still crashed. Then I tried rendering with CPU, it still crashed.\nI also tried in Blender 2.93.5. It crashed again even if the render didn't start.\nI downloaded the OCIO v2 config file from ocio_v2_demo.html.\n\nWhen I used OCIO v1.2 config file, Blender worked perfectly.\n\n[test-ocio2.txt](test-ocio2.txt)\n- Set the OCIO environment variable to the location of the test-ocio2.txt config file.\n- Start blender and set Cycles as the render engine\n- F12\n\n-----\nOCIO v2 Config\n{[F12676993](image.png) size=full}\n\nBlender 3.0 crash video\n[Crash.mp4](Crash.mp4)\n", "Render can not be cancelled and crashes\n\n\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: AMD Radeon R9 200 Series ATI Technologies Inc. 4.5.13570 Core Profile Context 19.7.2 26.20.13001.16003\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nHello,\n\nI wanted to export some scene using the Eevee render. When I render a frame, the image processing statut is still at 0%. Thus, when I try to cancel it, Blender hangs / crashes.\n\nI launched it using the GPU debug tool\n\nI'm assuming it comes from the hardware.\n\n\nThanks in advance.\n\n\n\n[eevee_logs.txt](eevee_logs.txt)\n\n\n[blender2.8.blend](blender2.8.blend)\n\n\n\n\n\n- Open the file\n- Render image {key F12}\n- Progress will hang at 0% for too long time\n- Cancel rendering\n\nRender job is not cancelled immediately / Blender crashes with low VRAM\n\n", "Crash - Blender crashes if an assetbrowser editor has no asset library ref.\nOperating system: Linux-6.0.9-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GT 1030/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.5.0 Alpha\nWorked: version: 3.4.0 Beta\nFor this particular file, crash started to happen after 1efc94bb2f\n\nLooks like the asset lib ref is None and it crashes? It looks blank but may have an underlying variable. \n\nNot completely sure how to reproduce this error from scratch.. Could be a legacy ref issue? To get this crash, I needed to open an old file.\nI duplicated the workspace that causes the issue and gave it a ref. \n\n\n\n\nFrom the [**crash-Asset_Editor.blend**] file:\n1. Open blender\n2. Switch to workspace \"Asset_Library_Ref=None\"\n\n----\nYou can open this file in Stable and Beta without any problems.\n[crash-Asset_Editor.blend](crash-Asset_Editor.blend)\n\nThe crash report doesn't give anything to go by.\n[crash-Asset_Editor.crash.txt](crash-Asset_Editor.crash.txt)\n\n\n" ]

[ "Crash on Exiting Texture Paint With Multiresolution (Image Editor involved)\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.90.1 release, 2.91 alpha ba8233174cd7\nWorked: 2.83.7\nIntroduced by: {1ceb91d1b3947fda67a70a2eff785a964e625ca2}\n\nSwitching from *Texture Paint* mode to *Object Mode* with an object that has a *Multiresolution* modifier, after sampling and then painting, crashes every time.\nThis makes Texture Painting with Multires impossible to use.\n\n[texturepaint_exit.blend](texturepaint_exit.blend)\n1. Open the file.\n2. Press the \"S\" key while hovering over the object to sample a color.\n3. Paint one stroke. (Observe that in the *Image Editor* panel, the wireframe becomes more sparse after the stroke.)\n4. Switch to Object Mode. It crashes immediately." ]

[ "Dyntopo: detail flood fill with smoothed mask expands too much\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.90.0 Alpha\n\n\n\n[#78755.blend](T78755.blend)\n- Open file\n- Dyntopo > Detail Flood Fill (this is still expected, sticks to unmasked area)\n- Undo\n- Mask > Smooth Mask (this already has a bit of an unexpected shape)\n- Dyntopo > Detail Flood Fill (this spreads out)\n\nTo reproduce: create icosphere with 5 subdivisions, mask spot, invert mask, soften mask, make detail flood fill\n[2020-07-09_09-38-22.mp4](2020-07-09_09-38-22.mp4)", "Sculpt Mode Performance\n**Status:** Prototype implemented in [D8983](D8983) with all optimizations included for Meshes, but only for some tools and features. Needs to be split into multiple patches and implement all remaining features.\n\n---\n\n**Team**\n**Commissioner:** @DanielBystedt \n**Project leader:** @PabloDobarro\n**Project members:** `-` \n\n**Description**\n**Big picture:** Improve the performance of Sculpt Mode brushes and tools.\n\n[Sculpt performance demo.mov](Sculpt_performance_demo.mov)\n\n**Use cases**:\n* Edit geometry surface detail in high poly meshes without performance issues\n\n**Design:**\nRemove all unnecessary calculations and updates from the PBVH when an editing operation is active, making all the Sculpt Mode code work only with the relevant vertices per brush step. The PBVH should only be used to get the affected area by the stroke as fast as possible.\n\n**Engineer plan:**\n* Get the PBVH code ready to have much smaller leaf node sizes\n* Store draw buffers in intermediate nodes to reduce the size of the leaf nodes of the PBVH.\n* Make proxies, bounding box and normal updates optional per tool and per symmetry options.\n* Do fast bounding box recalculations by updating the bounding boxes when deforming and propagating them from children to parents nodes to the root of the tree.\n* Implement optional fast normal updates (single loop) for brushes that require them.\n* Replace per node undo with a per vertex undo, which will also be used to get the original data during the stroke.\n\n* Remove BMesh based dyntopo (to be replaced with a better implementation).\n* Remove all loops over nodes from the code that runs when a stroke is active. \n* Configure the optimal settings of the scheduler per tool.\n* Make special tools (Pose, Boundary, Elastic Deform) not use the PBVH for getting the affected area. Cache the affected area of these tools once their data is initialized.\n\n**Work plan**\n\n**Milestone 1 - optional name**\n*Optimize PBVH queries and drawing*\nTime estimate: `2 - 3 weeks`\n\n**Milestone 2 - optional name**\n*Rewrite task scheduling and per vertex updates.*\nTime estimate: `3 - 4 weeks`\n\n---\n\n**Relevant links**:\n* #68873\n* #73934", "Weighted normals modifier produces different results on objects of different scales\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.0\n\n\nWeighted normals modifier is not consistant on small objects \n\nOpen Blender\nCreate a cube 1mmx1mmx1mm, scale applied, \nadd bevel and weighted normals modifiers\nYou can notice the différence by doing the same process on a 1mx1mx1m cube\n\nI can do a work around by modifying the unit scale parameter but I think it should work on 1mm objects, like a lot of watch pieces. \n\n[weightednormals_defect.blend](weightednormals_defect.blend)\n", "Edit Dyntopo Detail Size operator is not working with all methods.\nOperating system: Ubuntu 18.04\nGraphics card:\n\nBroken: master #e7dc3c91ad82\nWorked: 2.90\n\nEdit Dyntopo Detail Size operator was recently replaced to have a better gizmo.\nThat only works with Constant Detailing method.\n\nShift D is doing nothing when Relative or Brush detailing method are used.\nThat is a regression. It is pertinent to change the size for those methods, too.\n\nProbably, gizmo should work differently for a Brush Method. But, at least, shortcut should allow to change Detail Size like in 2.90. \n\n\n\nIssue in Master :\nEnter into Sculpt Mode.\nEnable Dyntopo mode.\nPress Shift D. Nothing happens.\nChange Detail Method from Relative to Constant. \nPress Shift D. New Gizmo is available.\nChange Detail Method from Constant to Brush.\nPress Shift D. Nothing happens. \n\nRepeat same steps In 2.90 :\nCircle gizmo is adapted to used method.\nRelative method is relative to screen. So, circle does not go above a certain limit.\nConstant/Manual method is relative to World Space. Size of Circle is not limited.\nBrush Method is relative brush size. Gizmo is showing a percentage.\n", "Fix operators that affect hidden geometry\n(NOTE) This task is part of the community & sub tasks of the workboard. Anyone is free to pick up this task and contribute. For any questions or needed reviewers, please tag @JosephEagar and @JulienKaspar .\n\nThere are a number of operators in sculpt mode that affect hidden geometry. As a general rule this should be avoided.\n\n- [ ] `bpy.ops.sculpt.face_set_edit` to Grow/Shrink, Fair or Delete face sets needs to have the \"Modifiy Hidden\" property disabled by default and disabled in all menu and keymap entries.\n\nList of further operators:\n- [ ] `bpy.ops.sculpt.face_sets_init` \n- [ ] `bpy.ops.sculpt.face_sets_create(mode='SELECTION')`\n- [ ] `bpy.ops.mesh.paint_mask_extract()`\n- [ ] `bpy.ops.mesh.paint_mask_slice()`\n\n", "unsubdivide of Multires bug\n**Blender Version**2.91\n\nI try to use unsubdivide of Multires function in blender ,but the result is error.So I test in Zbrush with same modle, it work rightly.\n\nThe thing is,I want sculpt with tank top with no thickness,and add thick ness at last.So I first sculpt with Multires (3 level subdivide),and apply it,and I loop cut the edge with 7 loop cut.After that I add Multires,and use unsubdivide,the result go wrong.\n\nI use the same modle in Zbrush,it work rightly.[unsubdivide error.zip](unsubdivide_error.zip)", "Sculpt Trim tools are very slow\nOperating system: macOS Mojave 10.14.6 \nGraphics card:\n\nBroken: Version 2.91.0 (2.91.0 2020-11-25) & Version 2.92.0 (2.92.0 2020-12-27)\nWorked: n/a\n\n\nUsing Box Trim is very slow. If you use the tool and then switch to another program like a web browser before the task is done, Blender becomes unresponsive and you have to force quit it.\n\nSee video of the slowness.\n\n[boxtrim.mov](boxtrim.mov)", "Box Trim has no effect (operates on undeformed geometry)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.97\n\nBroken: version: 2.91.0\n\nI have recorded [a video here ](watch?v=YEyFAvftycs)\nAs one can see, the Box Trim sculpting has no effect in this case.\n\n[stack3.blend](stack3.blend)\nPlease proceed as show in the video.", "Sculpting, Auto-Mask Topology does not work when dynamic topology is active\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.1\nWorked: Don't know, tried with 3.0.1 and also didn't behave as expected\n\nIn sculpting, auto-mask topology is ignored if Dyntopo is on.\nWeirdly it works with the smooth brush.\n\n- New file\n- Edit mode on cube, duplicate mesh\n- Sculpt mode, take any brush except smooth\n- Enable Advanced -> Auto-Masking -> Topology\n- With dynamic topology off it behaves as expected\n- With dynamic topology on the setting is ignored\n(Except it works both times with the smooth brush)\n\nExample attached. Move scrape brush over the cubes, will affect both. Turn off dyntopo, will affect only one.\n[sculpt-topology-automask.blend](sculpt-topology-automask.blend)\n\n", "Sculpt Mode - Face Set FK, mirror X is wrong when Scale/Translate using Pose brush with Lock Rotation When Scaling\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\n\nBroken: 2.92, 3.5.0 Alpha\nWorked: Never.\n\n\n- Change to pose brush.\n- Change brush deformation mode to Scale/Translate.\n- Enable brush Lock Rotation When Scaling.\n- Try to pose the hand.\n- The other hand is flipped.\n\n\n\n\n\nThis is the file I'm using:\n\n[20221205_model_human_sculting_pose_brush_using_facecets_0001.blend](20221205_model_human_sculting_pose_brush_using_facecets_0001.blend)\n", "Armature modifier slows down any transforms on an object\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.27\n\nBroken: version: 2.92.0\n\nHaving the armature modifer on an object with a slightly high polycount slows down any transformations (move, scale, rotation) done to it in the viewport.\nEven with the modifier disabled in view still slows down its movement.\nThis slowdown is very impactful to the smooth playback framerate of projects.\n\nHere's a video of the steps (I started out in the default scene and deleted all the starting objects)\n0Bgx_1JEouc\n\n- Make a high poly mesh (Eg. Suzanne subdivided 5 times)\n- Add Modifier: Armature\n- Transform the high poly object (Mode, rotate ...) and note the delay in fps", "Performance bottleneck with many nested nodes\nOperating system: win 10\nGraphics card: 1050 ti\n\nBroken: 3.2.0 Alpha\n\nSeems like *Domain Size* performance drops if using nested groups.\n \nIn attached file mute *Float to Integer* node (yellow color) and look how *Domain Size*'s executing time is drastically increasing.\n[domain_size_performance.blend](domain_size_performance.blend)", "Editing an object that is referenced in a disabled modifier (of another object) forces the other modifiers on the same stack to update\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.20\n\nBroken: version: 2.82 (sub 6)\n\nWhen there are two Boolean modifiers, and the second one is disabled, editing its shape still recalculates the Boolean operation if the first one is enabled.\nEven when both modifiers are disabled, editing their shapes is slower than editing the same shape that is not targeted by a Boolean modifier.\n\nAs an example:\n\n[2020-01-17_18-02-50.mp4](2020-01-17_18-02-50.mp4)\n\n\n- Open [#73199-testboolean.blend](T73199-testboolean.blend) (or add two cubes, make a dense mesh, add Boolean modifiers to the dense mesh each targeting a cube).\n- Switch off a single Boolean modifier.\n- Edit the mesh that is targeted by that Boolean modifier. This is slow.\n- Switch off the other Boolean modifier.\n- Edit the same mesh as above. This is now much faster.\n- Add a third cube and edit it. This is still faster than in the previous step.\n\n", "Sculpt Mode: Improve Expand performance\nWith [D16434: Sculpt Mode: Invert Expand behavior for masking consistency](D16434) it will be a stronger focus to highlight the Expand operators as a core feature in sculpt mode to create masks & face sets.\n\nThe issue is that the operator tends to be too slow to initialize on high res meshes.\nThis is especially the case for the geodesic expanding method.\n\nWe need to address these performance issues.\nOne usggestion was to incrementally calculate the distances while the operator is running.", "Unnecessary Proportional editing in Sculpt Mode.\nOperating system: Windows-10-10.0.1709 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.81 and 2.82 (sub 1)\nWorked: (optional)\n\nthis is probably not a bug but more of a design since Sculpt mode now has regular transform tools.\n\nI accidentally found out that if you enable Proportional editing then going to Sculpt mode the Transform tools will show Proportional editing & it's hotkeys in the Status bar.\n\n * Enable Proportional editing in Object mode.\n * Enter Sculpt mode.\n * Use any tool of the Transform tools.\n" ]

[ "Elastic Deform brush becomes extremely slow when Dyntopo is active\nOperating system: Windows 10 Pro 64-bit\nGraphics card: NVIDIA GeForce RTX 2080 Ti\n\nBroken: Blender 2.90 Alpha, f9d0f59bed4d\nWorked: ?\n\nI don't know if this can be considered to be a bug / error, but it is inconsistent and inconvenient behaviour:\n\nUsing the Elastic Deform brush while Dyntopo is active makes the effect agonizingly slow.\n\nThis results in constantly having to Control + D before and after activating Elastic Deform, while this isn't necessary when using the Grab brush. Dyntopo is automatically inactive when using Grab, but you don't need to deactivate Dyntopo.\n\nIf this could be fixed, that would make me a happy camper again. Thanks in advance.\n\nAdd three levels of subdivision to a Suzanne mesh and apply the modifier.\nEnter Sculpt Mode\nActivate Dyntopo (I'm using Constant Detail), and increase the Dyntopo resolution to 30 or more.\nUse the Elastic Deform brush. It will be very slow.\nSwitch off Dyntopo and use the Elastic Deform brush again. It will work smoothly." ]

[ "Glare Node set to \"Fog Glow\" in Real-Time Compositor vastly different from actual render results\nOperating system: Windows 10\nGraphics card: RTX3070 FE\n\nBroken: 3.6 A\nWorked: N/A\n\nWhen using the Glare Node in Real-Time compositor, the results in the viewport are turned up way higher than the actual render and Backdrop preview.\n\n\n\n1. Open attached .blend file\n2. Set to Rendered view, enable Real Time Compositor\n3. Compare the Glare effect in an F12 render to the effect previewed in the viewport\n\n", "Texture Paint: Wrong active Texture Slot\nOperating system:win10\nGraphics card:GTX 740m\n\nBroken: version: 2.92.0, branch: master, commit date: 2021-02-24 16:25, build date: 2021-02-25, 09:31:14, hash: 02948a2cab\n\nVpqy7BmMKaA\n\n- Open attached file or:\n - Go to \"texture painting mode\" (in default workspace)･\n - Create 2 base color textures\n - Open Shader Editor\n- In the Shader Editor, select non -active texture (\"Material Base Color 2\")\n- in the View 3D, paint texture\n- Nothing happen in visual.\n- The other texture slot is changed instead of current active texture.\n[tex_slot_problem.blend](tex_slot_problem.blend)\n\n", "Eevee: Soft shadows causing flickering in animation and temporal AA in scenes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.80\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nEevee soft shadows in objects with thin reflections causes flickering in animation and temporal AA in still images. This type reflections common in interior Arch Viz.\n\nScene 1 example of flickering of soft shadows in animation. I have remove all light probes and effects to focus only light and shadows. Open attach file \"Scene1_AA_eevee.blend\".\nRender the animation with Soft Shadows ON. Then Render animation with Soft Shadows OFF.\n[Scene1_AA_eevee.blend](Scene1_AA_eevee.blend)\n\nAnimation with Soft Shadows ON. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_eevee.mp4](Scene1_AA_eevee.mp4)\n\nAnimation with Soft Shadows OFF. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_No_SShadow_eevee.mp4](Scene1_AA_No_SShadow_eevee.mp4)\n\nAnimation in Cycles for comparison. Make sure to play video at full size. If not video will be alias by the video player.\n[Scene1_AA_cycles.mp4](Scene1_AA_cycles.mp4)\n\n******************************************************************************************************\nScene 2 example of temporal anti-aliasing cause by soft shadows. I have simplify the scene 2 to focus only light and shadows. Open attach file \"Scene2_AA_eevee.blend\".\nRender Image with Soft Shadows ON. Then Render Image with Soft Shadows OFF.\n[Scene2_AA_eevee.blend](Scene2_AA_eevee.blend)\n\nRender image with Soft Shadows ON. Make sure to view at full size. Notice the temporal AA on the edges on horizontal counter, vertical counter, oven handle and oven racks.\n\n\nRender image with Soft Shadows OFF. Make sure to view at full size. Notice the temporal AA is gone.\n\n\nRender image with Cycles for comparison. Make sure to view at full size.\n\n\n", "EEVEE: Add support for extracting alpha channels from a color\nI mistakenly filed a bug report --> #72856 EEVEE transparency problem with mtpaint PNG\n\nI didn't fully understand the bug and attached a blender file that didn't show the bug properly.\nPacking the image file with blender command 'Pack' makes the image\nopaque so it is worthless to include a blender document. I will\ninclude a mtpaint PNG image instead and you can load it into\nblender 2.81 yourself and see how it renders in EEVEE versus cycles.\n\nI noticed that your forum converts the image to opaque if I try to attach to this post\nso I'll use a shareable link that preserves the transparency:\n\nopen?id=1TjfSjzabYEmVHXTODPFymGVNwuL02SnJ\n\nHere is how I created the mtpaint image to reproduce the problem...\n\n1) Launch GIMP -->new gimp document -no alpha channel - paint with brush\n2) save as PNG format with no alpha channel\n3) Launch mtpaint ---> open the PNG document\n4) 'Save as' to output the document - one color chosen to be transparent - PNG format\n5) Launch blender 2.81 (linux) - images > Images as planes\n\nEEVEE rendering doesn't respect the transparent region.\nCycles rendering does respect the transparent region.\n\n\nNot a high priorty.", "Alpha Blend material has inconsistent behavior with Geometry nodes\nOperating system: win 10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nAlpha Blend material renders differently on the object, which is referenced inside Geometry Nodes tree of another object, despite this another object is already hidden and has muted GN modifier.\n\nIn attached file:\n* Remove/Select *Shell* object inside GN tree of object *Mesh*\n* Activate/Deactivate *Viewport Disable* for *Collection* or object *Mesh*\nIn both cases material becomes transparent or not\n\n", "Color > Multiply doesn't multiply alpha channels\nOperating system: Win11\nGraphics card: RX580\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) 4.0.0 alpha\nWorked: (newest version of Blender that worked as expected) 3.6.2\n\nThe Color > Multiply section in a video sequencer strip no longer multiplies the alpha channel when that feature is pretty important for creating outlines using the glow effect. Perhaps adding an option whether to multiply alpha or not would be beneficial?\n\nStart up blender 4.0.0\nSwitch to Video Editing workspace\nAdd a white color strip with 0.1 opacity\nAdjust the Color > Multiply value and notice how it doesn't affect alpha anymore\n\n", "Missing Letter V and Black Screen\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.0\n\nWhenever I open Blender, the viewport is black and the letter v is not displayed in any of the menus. Here is a link to a screenshot: VZui9.png \n\nIt simply appears like this on startup.\n\n", "EEVEE baking\n", "Overlay: Edit-Mode: Anti-Alliasing not working with constructive modifiers\n```\nOperating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce 610M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116\n\n\nBroken: version: 2.80 (sub 69)\nWorked: (optional)\n\n```\n\nthe bug is really intresting so... when you add mirror modifier to object.. and u enter edit mode and u select face or edges etc... the AA goes crazy it is so pixelised like even worse than tottaly without AA.\n\n\n\n\n\n\n\n", "Cannot disable shadows if an object is set to holdout.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: Confirmed on Version 3.4 to version: 3.5.0\nWorked: Never (Goes as far as 3.0, since the addition of the \"Object Properties -> Visibility -> Holdout\"option)\n\nCannot control an objects shadow visibility if the object is set to holdout. Having a shadow on a holdout object does not work as expected, especially when trying to use the holdout object as a 3d mask.\n\n\n- Set scene renderer to Eevee.\n- Create an object, set \"Shadow Mode\" to none in the material shader of said object.\n- The object will no longer have a shadow, as expected. \n- Set the object to holdout via \"Object Properties -> Visibility -> Holdout\" option, and the shadow reappears. Can not turn off shadow as long as this option is on.\n - However, if use Holdout shader in the nodes and connect it directly to the Surface output, no shadow will appear (this matches expectation).\n\nAdded a file that directly shows the issue.", "Broken textures and shading\nOperating system: Linux-5.15.0-40-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.73.05\n\nBroken: version: 3.2.0\n\nBroken textures when starting up blender and loading object textures and shading issues\n\n[Blender Texture Bug.mp4](Blender_Texture_Bug.mp4)\n\nPossible causes:\n * Not loading the parent asset blend file before the asset in another scene (opening it first seems to fix the issue in my testing) \n * 4k textures (i've heavily used 4k textures in the asset)\n * Viewport Texture size limit setting (Changed it to 2k)\n\n\n[untitled.blend](untitled.blend)\n", "Rendering Error in viewport for Intel Iris and Xe GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (but I am using windows 11 ????)\nGraphics card: Intel(R) Iris(R) Xe Graphics Intel 4.5.0 - Build 30.0.101.1692\n\nBroken: version: 3.5.1\n\nViewport rendering errors appear on my new laptop for semi transparent objects. I assume the issue is related to the Intel Iris GPU. This issue never appeared on other PCs. All of them were using Nvidia GPUs.\nThe issue occurs when a semi transparent object is overlapping another object. See image/video. \n\n1. Use a computer with an intel iris GPU (Issue did never appear on my other pcs with Nvidia GPUs).\n2. Make sure that the Viewport is set to SOLID and the Viewport Color Type is set to Object.\n3. Create an opaque cube \"CubeA\".\n4. Duplicate the cube and make it bigger \"CubeB\".\n5. Go to Object Preferences > Viewport Display > Color.\n6. Change the alpha value of CubeB to be partially transparent.\n\nThis results in rendering errors of the overlapping objects. \nExample file and video are attached.\n\n", "EEVEE - Screen space reflections artifacts\nOperating system: Linux-5.3.0-7625-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.44\n\nBroken: version: 2.83 (sub 2)\nWorked: ?\n\nSSR shows some strips when I have bad data for normals.\n\nOpen the file:\n[ssr_sripts.blend](ssr_sripts.blend)\n\nIf you click anywhere multiple times, viewport gets darker and darker.\n\nBefore:\n\n\nAfter clicking the glossy node header a few times:\n\n", "Compiling shaders for Eevee locks up the viewport until the process is complete (MacOS)\nOperating system: macOS-11.2.3-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 71.0.7\n\nBroken: version: 2.93.0 Beta\nWorked: I don't believe this has ever been good on the Mac platform\n\nWhen working in a heavy scene (the spring or barbershop demo, for example), the UI will \"beach ball\" or lock up while blender calculates Eevee shaders. On a pc, these calculations don't appear to lock up the interface the way it does on Mac. The expected behavior would be that the UI remains responsive at all times.\n\nOpen the Spring or Barbershop demos. Switch the viewport to full Eevee interactive rendering. The UI will lock up while Blender calculates the shaders. Once this process is complete, the viewport will return to normal behavior.\n\n", "Regression: Ambient Occlusion causes shading artifacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 2.93.1\nWorked: 2.91, 2.92\n\n Under lookdev mode, when object has \"alpha blend\" turned on in the shader, \"ambient occlusion\" with \"bent normal\" option enabled will cause shading artifact that looks like the object is shading flat. \n\nSwitch the scene to lookdev mode. \nCreate a UV sphere\nShade it smooth\nTurn on Ambient Occlusion and make sure \"Bent Normals\" is checked. \nAssign a material to the sphere. \nUnder the material settings turn on \"Alpha Blend\". \nNow the object will look like it's shaded flat/without smoothing. \n\n[Eevee_bug_scene.blend](Eevee_bug_scene.blend)\n\n" ]

[ "Material shadows not updated with rna_Material_draw_update\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nWhen we change material shadow mode, for example, the shadows are not updated in the viewport\n\n\nSteps:\n\n- open this .blend: \n\n[Material_shadow_mode.blend](Material_shadow_mode.blend)\n\nwith last 2.8\n\n- go in \"rendered\" shading mode with eevee\n\n- change shadow mode from opaque to alpha hashed for example\n\n- > the shadows are not updated\n\nNote:\n\nThis patch (which is not a fix):\n\n[p.diff](p.diff)\n\nforces the shadows update when we switch several times between shadow modes.", "EEVEE Alpha Clip/Hashed shadows don't auto-refresh every frame in the viewport\nOperating system: Xubuntu 19.04\nGraphics card: Nvidia GTX 860M\n\nBroken: 2.80 official release\n\nWhen the current scene is being played back, materials with Image Sequences or Movies with alpha channels and the Shadow Mode set to \"Alpha Clip\" or \"Alpha Hashed\" don't update the shadow ***in the viewport*** until the frame is changed by scrubbing the timeline.\n[duwane.mp4](duwane.mp4)\n\nYou may import this video as a plane and set its shadow mode to Alpha Clip or Hashed.\nOr download it and throw it into your shitpost folder. I won't judge.\n[duane.avi](duane.avi)" ]