Datasets:

---

mano-wii

/

blender_duplicates

like 0

[ "Renaming an ID through RNA does not consistently increment OTHER or CURRENT ID in case of name collision\nRenaming an ID through RNA does not consistently increment either the current ID or the other ID in case of name collision. This depends on the existing order of the data-blocks before the rename happens.\n\nAs pointed out in the comment below by @ideasman42, fixing this in one way or the other is trivial. But we have to choose one of the two solutions:\n* Add incremented number suffix to renamed ID (this seems to be the soundest solution, as it will ensure we never silently rename a random other ID).\n* Add incremented number suffix to the other ID.\n\nNote that it should also be ensured that behavior is consistent with Outliner renaming code as well.\n\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 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\nwhen we try to rename an object with an already used name,, it will rename the existing occurence, not the incoming one\n\nworks with the default scene (with Cube, Light, Camera) :\n- take the Cube, x2 clic on the name, rename it in \"Camera\". Enter\n- the original Camera (previously named \"Camera\") will be renamed in \"Camera.001\" and the Cube will be renamed in \"Camera\"\n\nI gess it should be the opposite : the incoming similar name is incremented, but the original name stays the same\n\n", "Drivers of sub-ID properties do not get removed along with the sub-ID\nBy \"Sub-ID\" I mean things like Modifiers, Constraints (bone & object), custom properties, shape keys, bones, VSE strips, etc. Not sure how to get a complete list of these types of things.\n\nWhen one of these things, such as a modifier, is removed, drivers on its driven properties are not removed. This makes it easy to leave behind broken drivers that now target nothing. These can be cleared up in the Driver Editor UI fairly easily, but the fact that we must do so is annoying. Experienced users end up learning that you can't just remove a modifier or constraint without removing its drivers first - Just to save you a trip to the Driver Editor.\n\nForgetfulness in this habit results in console warnings, which in a production environment trickle down from assets to shot files, and contribute to the users' sense of \"console warnings aren't important, I will ignore them\".\n\nI always thought this was a known issue but @Sergey told me it's fixable and that I should make a report. Here ya go! \n\nThis would be a really, really welcome improvement for the studio and probably the whole world.\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", "Redo panel overlaps part of the interface\nIn the image editor, the redo panel covers part of the pixel values. \nWould be nice if such panel could be dismissed, or if it would take into account the possible presence of the pixel value subheader.\n\n[open_image_overlay.mov](open_image_overlay.mov)", "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)", "Denoise + Pixel Size + Render Region = Artifacts in Viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: \nNVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84, \nNVIDIA GTX 1080.\nOptix is used.\n\nBroken: version: 3.2.0 Alpha\nWorked: Don't know.\n\nWhen the pixel size for render preview is increased, (2X, or 4X), Render region is set, and viewport denoiser is turned on, the viewport render gives weird artifacts.\n\n\nTurn on render preview, and zoom in this file:\n[Pixl Size Denoise Render region.blend](Pixl_Size_Denoise_Render_region.blend)\n\n", "Undo in Armature Edit Mode does not undo Custom Properties\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.5 Beta\n\nUndo in Armature Edit Mode does not undo changes to Armature Custom Properties\n\n- [optionally] In default scene delete all objects\n- Add an \"Armature\" object\n- Go to `Edit Mode`\n- In `Object Data Properties` add a `Custom Property`\n- Change the value of the property (to for example `0.0`) in order to add an Undo step\n- Try undo (`Ctrl+Z`)\n\nThe step is not undone in edit mode.\nInterestingly, changes to the Custom Properties of Bones are correctly undone in Edit mode.\nThis makes it seem that changes to Armature Custom Properties were perhaps missed in the Armature Edit Mode Undo Context.\n\n---\n**Original Report**\n[Video](3RZNWd5tRQI)\nNote when changing the **head size** in the redo panel, you can observe how the number of elements in in the Collection Property `bones_for_delete` grows.\n\n1. Execute the script generate_rig.py from the file, if you do not have automatic script execution enabled\n2. After execution, the Generate Rig panel will appear in the Rig category\n3. Select Empty.021 first, then Armature.001. Switch to armature editing mode, and click Generate Rig on the panel\n4. The bones will appear, and also the text on the panel will notify that there are elements in bones_for_delete. After that, you can scroll the **head size** on the redo panel, or simply undo the operator. the label in the panel will notify you that the number of items will not change\n\n", "Its possible to create Built-in attributes with wrong metadata\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\n```\nCode marked as unreachable has been executed. Please report this as a bug.\nError found at C:\\Users\\blender\\git\\blender-vdev\\blender.git\\source\\blender\\blenkernel\\intern\\attribute.cc:486 in BKE_id_attribute_remove.\nSaved session recovery to \"C:\\Users\\rfnei\\AppData\\Local\\Temp\\quit.blend\"\n```\n\n1. Create any attribute on mesh.\n2. Rename it to `material_index`.\n3. In debug: try to delite this.\n\n", "LibOverride: Sanitize handling of library pointer in resync process.\n`BKE_lib_override_library_create_from_tag` takes an 'owner library' data, which is the library owning the currently resync overrides. However, `lib_override_library_resync` always calls it with nullptr library, and later reassign proper lib pointer...\n\nThis needs to be checked, there is likely better/more sensible and straightforward way to handle this. Also somewhat related to #107847.\n\n", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "Cycles Regression: Changing \"Start Samples\" in denoiser resets viewport render\nOperating system: Linux-5.14.0-3-amd64-x86_64-with-glibc2.32 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.29.05\n\nBroken version: 3.0.0 Alpha\nWorked: Prior to Cycles-X merge\n\nChanging the `Start Samples` value for the viewport denoiser resets the viewport rendering. This did not happen prior to the Cycles-X merge.\n\n1. Create a scene that has noticeable amounts of noise in Cycles.\n2. Enable viewport denoising.\n3. Enter rendered viewport mode.\n4. Change the `Start Samples` value of the viewport denoiser. You will notice that viewport rendering will reset back to 1 sample. This did not happen prior to the Cycles-X merge.", "Cycles - Viewport render preview stucked on the first sample - in a scene a DupliVerts objet parenting instances owned by more than one Groups\nBlender 2.78 (2.78 2016-10-24, Blender Foundation)\nMac Book Pro Retina 2013\n2.6 Ghz Intel Core i7 - 16GO 1600 MHz DDR3\nOSX 10.9.2\n\nUsing Cycles\n\nIn my scene with a parent DupliVerts object (Properties /Object / Duplication / Verts), with inside of if instances of Group.\nWhen those childs instances are from one group, that's ok.\nBut when they are from several groups, the 3D viewport render preview is stucked to the sample 1, rendered without ending !\n\nGood for heating the room ;)\n\nTo test, simply [Shift] - [x] in 3d the viewport in my blend to see this issue\nHope this help, keep the good work !\n[DupliVerts_and_Groups_BUG_with_Render_ViewPort_Cycles.blend](DupliVerts_and_Groups_BUG_with_Render_ViewPort_Cycles.blend)", "Fix preview flickering when using \"Adjust Last Operation\"\nTweaking properties in the \"Adjust Last Operation\" panel removes all previews for a moment, causing quite drastic and annoying flickering.", "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", "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" ]

[ "Custom presets but with the name of builtin presets cannot be deleted\n\nBroken: Blender 2.83.5, blender-2.90.0-21cb6f09ffa8-windows64, blender-2.91.0-396d39c6b904-windows64\n\nThe original sampling presets in Cycles can't be deleted. However, it is possible to create presets of the same name. These presets become undeletable, because Blender assumes them to be the default presets.\n\n\n\n\nCreate sampling preset with name \"Preview\" or \"Final\". Try deleting new presets. \n", "Presets can't be deleted if named as the default ones\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.90.1\nWorked: \n\nIf you create a preset and you name it the same way as the built-in presets, they can no longer be deleted and Blender recognizes them as defaults.\n\n\n\n\n\nGo to any tab in the properties with customizable presets> click on the Presets icon> name the preset the same as the Blender built-in ones and add it> click on the minus icon to remove the preset. \n[Presets naming bug.blend](Presets_naming_bug.blend)\n\n" ]

[ "Can't browse mounted server volumes\nOperating system: macOS-12.1-arm64-arm-64bit 64 Bits\nGraphics card: Apple M1 Apple 4.1 Metal - 76.3\n\nBroken: version: 3.1.0 Alpha\n\nWhen I try use the open or import functions to browse a network volume, it won't let me traverse the volume. Clicking on it does not have any effect and does not work in any mode, thumbnail, horizontal list or vertical list\n\nMake sure you have a network volume mounted on your desktop and then try to traverse it within Blender\n", "Asset Browser - Current File doesn't place objects in active collection\nOperating system: Windows 11\nGraphics card: RTX 4070ti\n\nBroken: 3.5.0\nWorked: Supposedly never (tested 3.0-3.6)\n\nWhen adding an object into the scene from the Current File category in the Asset Browser, objects are placed into the same collection as the assets they originate from instead of the collection you are currently working in.\n\n- Move default cube into a new collection\n- Mark as asset\n- Ensure the scene collection is active, not the cube collection\n- Drag cube asset from Asset Browser Current File category into the scene\n- It will appear in the same collection as the asset reference object\n", "Geometry instances cannot mix with other instancing\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 Alpha\nWorked: 3.0 alpha\n\n\n\n[cant scatter.blend](cant_scatter.blend)\n[2021-11-02 19-08-07.mp4](2021-11-02_19-08-07.mp4)\n\n", "Using a File Picker element in a popup window causes the popup to go away\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 2.93.4\nWorked: Not sure if it has, at least not for a while.\n\nIf I put a string property with a subtype of \"DIR_PATH\" or \"FILE_PATH\" to have the folder/file picker show up for a user to easily select a folder/file in an operator's props and then call it with a window manager invoke_props_dialog (or any of the other popup panel ops), after the user has selected a folder/file the file window goes away but so does the panel without executing the operator.\n\n1. Open included blend file\n2. Run 'Popup File Picker Test' script in text editor\n3. In the Object section of the Properties area, under \"Popup File Picker Test Panel\" click 'Test Popup'\n4. In the popup window use the folder picker button to select a folder and hit \"Accept\"\n5. If it worked, the popup should still be there for you to continue to change other props. If it ran execute instead there should be a statement in the info area and in the console window saying \"Ran execute\". Otherwise it most likely made the popup to disappear without running the operator\n\n[popup_file_pick_test.blend](popup_file_pick_test.blend)\n\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)", "Assigning shortcut to Sequencer data is wrongly 'hooked' the Scene instead of Scene's VSE data\nThis error shows all the time when I right click on the viewscreen, and I have to right click and press ESC, so the message disappears and I keep working this way, right click, a message appears, ESC.\nIt suddenly started to happen and even deleting and downloading blender again, even with the other 2.8 version it happens.\n\nThank you, I love your work guys\nJust trying to help\n\nOperating system: Windows 10 Home, Core i7 - 7500U @ 2.70GHz, 8.00 GB RAM\nGraphics card: AMD Radeon R7 M440 32GB, 4.00 Gbps\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional) ", "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", "Improve thumbnail loading from blend files.\nThumbnails are cached in tmp folder but can be outdates or not available. When this is the case the thumbnails are extracted from the blend file.\n\nCurrently the logic is as follow\n\n```\nfor each thumbnail to load:\n open file\n read all names of the same category\n read all preview images of the same category\n find the preview image that was needed as it is assumed that the name list and preview list are in the same order!\n discard the rest of the preview images (that will probably be reread in the following loop)...\n```\n\nRelated functions:\n* `IMB_thumb_load_blend`\n* `BLO_blendhandle_get_previews`\n\nOther improvements are:\n* - [ ] store preview images closer to the bhead.\n* - [x] [D12312: #90908: Reduce loading times when extracting thumbnails from Blendfiles.](D12312)\n* - [ ] add an preview index at the end of the blend file that can act as a hashmap between IDname and preview index. So we don't need to go over the whole file. \n\n", "UI: File Browser Incorrect uiFontStyles\nOperating system: All\nGraphics card: All\n\nBroken: 3.1\nWorked: 2.79\n\nFile Browser uses an odd mixture of uiFontStyles to draw interface\n\nEdit / Preferences / Themes / Text Style\nChanging \"Widget\" points changes the font size of \"Bookmarks\", \"Recent\", the browsed directory, and the line height of the entries:\n\n{[F11861179](FBWidget.gif),width=100%}\n\nChanging \"Widget Label\" changes Volumes, System, and the text size (but not line height) of entries:\n\n{[F11861234](FBLabel.gif),width=100%}\n\n", "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", "Blender file browser replaces dot with underscore\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 466.27\n\nBroken: version: 3.0.0 Alpha\nWorked: Never\n\nThe renderfarm service I'm using decides to use a dot in the middle of naming the frames. It's stupid but it is what it is and I don't have control over it.\n\n\n\nTry to set the render path like this\n\nAs soon as you press enter it decides to rename like this\n\n\nBlender keeps changing the dot for an underscore but only on windows, on linux it leaves the dot alone!\n\n\nOn a **Windows** machine:\n- Invoke file open dialog\n- Input filename `test.`\nFilename will be changed to `test_`\n", "UI: File Browser System Root View\nCurrently the File Browser can allow you to easily browse to any location on any of your drives. I propose adding a new area: the root of all your drives and shares.\n\nUsing Windows locations for examples, I can be browsing in folders on my \"D\" drive, and I can hit the \"parent directory\" button on the header until it am in the root of the \"D\" drive. I propose that hitting that button one more time will take me to the System Root. This has been something I have wanted since 2.8, and is the reason that we have large versions of some icons in the project:\n\n\n\nThe System Root would include all items that you currently have in the sidebar \"Volumes\" list, followed by the items in the \"System\" list, then (possibly) your \"Bookmark\" items. Like other File Browser views you could choose to see them as a vertical list, horizontal list, or with large icons.\n\nThe primary reason for this is that it allows use of File Browser when space is constrained, so that you can browse anywhere without needing the left-side Sidebar. For a great example of this need select File / New / Video Editing. In this layout there is very little room for the File Browser and you can't get to all your files without opening the side panel.\n\nThis shouldn't be considered until File Browser is separated from Asset Browser. I have made some attempts at implementing this over the years but have had little luck so far for various reasons and so would need some assistance.\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) ", "Support dragging to change tabs in the side-bar\nNote, this was reported as a bug however it's a TODO (wasn't supported in 2.7x).\n\n----\n\n\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.39\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (version before the click transparent passthrought)\n\n\nCannot drag on the tabs to select other tab like normal tab behavior on Blender.\n\n- Factory defaults\n- Press 'N' on the 3D View.\n- Try to drag on the tabs on the \"WM_OT_context\", the result is the box selection.\n\nSee attached gif (ignore the mouse cursor offset, that is due to 4k display with only 125% scale applied.)\n\n\n\n\n", "\"Assign Material Slot\"-Shortcut is created in the wrong place\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\n\"Assign Material Slot\"-Shortcut is created in the wrong place, therefore does not work.\n\n\n[Material Shortcuts.blend](Material_Shortcuts.blend)\n\nBy rightclicking, the shortcut is created in the Input Preferences under `3D-View > Object Mode > Object Mode (Global)` which is wrong. It simply does nothing in Object mode. In order to work it has to be manually created under `3D-View > Mesh > Mesh (Global)` with the same entry name.\n\n\n\n" ]

[ "Blender 3.0 beta Cannot open folder shortcuts under Windows \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\n\nBroken: version: 3.0.0 Beta 901fa96b7f\nWorked: 901fa96b7f~\n\nOn Windows cannot open folders shortcuts (by either double or single clicking on them).\n\n\n1. Click a folder shortcut (e..g, on Desktop pointing to My Documents).\n2. Use File --> Open.\n3. Navigate to the folder containing the shortcut and try to go inside it (e.g., in the Desktop folder try to enter the My Documents shortcut)." ]

[ "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Vega GPU crash during render\nOperating system: Debian 11 bullseye x86_64 Linux 5.10.0-17-amd64\nGraphics card: gfx900 AMD/ATI Vega 10 XTX [Radeon Vega Frontier Edition]\n\nHip info: \n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release hipconfig\nHIP version : 5.2.21152-4b155a06\n\n== hipconfig\nHIP_PATH : /opt/rocm-5.2.1\nROCM_PATH : /opt/rocm-5.2.1\nHIP_COMPILER : clang\nHIP_PLATFORM : amd\nHIP_RUNTIME : rocclr\nCPP_CONFIG : -D__HIP_PLATFORM_HCC__= -D__HIP_PLATFORM_AMD__= -I/opt/rocm-5.2.1/include -I/opt/rocm-5.2.1/llvm/bin/../lib/clang/14.0.0 -I/opt/rocm-5.2.1/hsa/include\n\n== hip-clang\nHSA_PATH : /opt/rocm-5.2.1/hsa\nHIP_CLANG_PATH : /opt/rocm-5.2.1/llvm/bin\nAMD clang version 14.0.0 (llvm-project roc-5.2.1 22204 50d6d5d5b608d2abd6af44314abc6ad20036af3b)\nTarget: x86_64-unknown-linux-gnu\nThread model: posix\nInstalledDir: /opt/rocm-5.2.1/llvm/bin\nAMD LLVM version 14.0.0git\n Optimized build.\n Default target: x86_64-unknown-linux-gnu\n Host CPU: znver2\n\n Registered Targets:\n amdgcn - AMD GCN GPUs\n r600 - AMD GPUs HD2XXX-HD6XXX\n x86 - 32-bit X86: Pentium-Pro and above\n x86-64 - 64-bit X86: EM64T and AMD64\nhip-clang-cxxflags : -std=c++11 -isystem \"/opt/rocm-5.2.1/llvm/lib/clang/14.0.0/include/..\" -isystem /opt/rocm-5.2.1/hsa/include -isystem \"/opt/rocm-5.2.1/include\" -O3\nhip-clang-ldflags : -L\"/opt/rocm-5.2.1/lib\" -O3 -lgcc_s -lgcc -lpthread -lm -lrt\n\n=== Environment Variables\nPATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/home/ian/.local/bin\n\n== Linux Kernel\nHostname : *****Linux***** 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64 GNU/Linux\nNo LSB modules are available.\nDistributor ID:\tDebian\nDescription:\tDebian GNU/Linux 11 (bullseye)\nRelease:\t11\nCodename:\tbullseye\n```\n\nBroken: blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release\nWorked: N/A\n\nBlender crashes when attempting to render more complex scenes on Vega GPU.\n\n[lone monk demo](lone-monk_cycles_and_exposure-node_demo.blend)\n./blender ../lone-monk_cycles_and_exposure-node_demo.blend\nrender on gpu\n\n```\n➜ blender-3.3.0-beta+v33.6a4f4810f38b-linux.x86_64-release ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | tee log.txt\nRead prefs: /home/ian/.config/blender/3.3/config/userpref.blend\nRead blend: /home/ian/Downloads/lone-monk_cycles_and_exposure-node_demo.blend\nWARNING: Shader warning [node_vertex_color]: Invalid attribute.\nMemory access fault by GPU node-1 (Agent handle: 0x7f2683fa6400) on address 0x7f2400000000. Reason: Unknown.\n[1] 25965 abort ./blender ../lone-monk_cycles_and_exposure-node_demo.blend | \n 25966 done tee log.txt\n```\n\n```\n:0:rocdevice.cpp :2652: 2702732952 us: 249488: [tid:0x7f1dd0b76640] Device::callbackQueue aborting with error : HSA_STATUS_ERROR_MEMORY_APERTURE_VIOLATION: The agent attempted to access memory beyond the largest legal address. code: 0x29\n[1] 249488 abort ./blender --factory-startup --debug-all\n```", " EXCEPTION_ACCESS_VIOLATION when entering Edit Mode\nOperating system: Windows 10 1903 (18362.239)\nGraphics card: Intel HD Graphics 4000\n\n***Broken:***\nBlender 2.80 (sub 75) / 2019-07-29 09:44 AM Windows / Stable\nBlender 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash: 6f9cbbc8ec4f\n***Worked:***\nBlender 2.79 (copied mesh over through copybuffer.blend)\n\n\nWhen entering edit mode of a specific object Blender crashes with EXCEPTION_ACCESS_VIOLATION. Logs and example .blend provided.\n\nThe issue shouldn't be in my GPU, since the same issue persists even with Software Rendering.\n\n1. Open up example file\n[window_broken.blend](window_broken.blend)\n\n2. Select `window_panes` and enter Edit Mode\n3. Get EXCEPTION_ACCESS_VIOLATION\n\n**Logs (2.80 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n**Logs (2.81 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "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 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.", "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", "(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", "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)", "Normal map support in Cycles standalone\nWindows 8.1 64-bit\n\n**Cycles Version**\nd553b8de7180\n\n\nIn the latest version available in the Cycles standalone repository, commit d553b8de7180, using a normal map node in a shader graph will cause Cycles to crash. This behavior was not present in release 1.7.0 but has been added since then.\n\nThis looks to be caused by an improperly initialized member variable in the ccl::NormalMapNode type. Upon creating an object of type NormalMapNode, the ustring named 'attribute' is initialized such that attribute.c_str() will return a nullptr.\n\nCycles crashes when the nullptr used to construct a std::string in NormalMapNode::attributes in this bit:\n\n```\t\n\t\telse {\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent\").c_str()));\n\t\t\tattributes->add(ustring((string(attribute.c_str()) + \".tangent_sign\").c_str()));\n\t\t}\n```\n\n\nI have attached a simple cycles standalone scene that triggers this error here: [sample_scene.xml](sample_scene.xml)", "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", "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", "Cycles: UV render pass corrupted in viewport\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9664\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.93 LTS\n\nWhen switching the render passfrom normal to UV the UVs are not displayed correctly.\n\n\nDownload bmw demo file.\nin viewport switch to render mode\nEnable the normal render pass. After that enable the uv render pass.\n\n{[F11785393](uv_render_pass.png) width=100%}\n\n`Film::update_passes` sets `shader->need_update_uvs`. The problem is that in 3.0 this is called as part of scene update after all syncing, instead of immediately after updating the render passes. That means this information is not available when we sync the geometry.\n\nNote: you can get the proper UVs back if you click on the UVMap in the Property Editor `UV Maps` panel", "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", "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>" ]

[ "System freezes when movig in viewport shading / cycles GPU enabled.\nOperating system: Linux-5.13.0-51-lowlatency-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 6800 XT (sienna_cichlid, LLVM 14.0.6, DRM 3.45, 5.13.0-51-lowlatency) AMD 4.6 (Core Profile) Mesa 22.1.7 - kisak-mesa PPA\n\nBroken: version: 3.3.0\nWorked: (newest version of Blender that worked as expected) : none\n\nSystem freeze after rotating an object (MMB) in viewport shading, cycles GPU enabled\n\nOpen the attached blend file, go in viewport shading with cycles GPU enabled. Select the object named \"body_linux\" and play a bit with rotating around the object (MMB). After a few times (could be one time, could be 15 times) the system freezes, ugly screen, mouse pointer style \"alive\" but nothing to click on. If I do a few \"ctrl-alt-del\" I can go back to the session login screen and re-enter my session. But I noticed there is still an instance of blender running in background.\nNo issue at all if I use RadeonProRender.\n\n[dmesg.txt](dmesg.txt)\n\n[journalctl-b-1](journalctl-b-1)\n\n[aegis_V4_crash.blend](aegis_V4_crash.blend)\n\n\n" ]

[ "Sculpt Mode: Wrong Transform pivot point when set to 3D Cursor\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.4.1\n\nWrong Transform pivot point in sculpt mode.\nIf you set transform pivot point to 3d cursor and perform a rotation after it won't take orientation pivot into account. Only works on the second input. See the videos for details.\n\n - enter sculpt mode\n - enable symmetry\n - set pivot to 3d cursor \n - enable transform tool\n - mask part of the mesh\n - set pivot\n - perform rotation\n - perform second rotation\n[Blender 2023-01-27 12-14-10.mp4](Blender_2023-01-27_12-14-10.mp4)", "Apply Parent inverse dose not take scale in to account\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.61\n\nBroken: version: 3.5.1\n3.6 alpha\n\nApply Parent inverse dose not take scale in to account while using alt+g , alt+r , alt+s to restore the coordinate\n\nnot sure if this is design intended.\n\n**Exact steps to reproduce the error**\n\nBased on the default startup\n1. create 2 cubes in same size ( display in wire frame mode for easier visual)\n2. Scale 2 cube independently in any size\n3. Parent them in either way , using any following parenting method below.\n\nParent object \nParent object Keep transform\nParent object (keep transform without inverse)\n\n*** Parent object (without inverse) works fine as intended there is no need to try on this ***\n\n4. Select child cube Apply Parent inverse\n5. Select both cube alt+g , alt+r , alt+s restore the coordinate , you will see child cube is not at the same size as parent\nbut the transform panel is displaying 1,1,1 both on the child and parent cube\n\n--------------------------------------------------------------\nrelated issue been reported \n97648\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", "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", "Wrong teleport behaviour if scene scale is greater than 1.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47\n\nBroken: version: 3.3.1\n\nCalling teleport using a scene scale greater than 1 will place the camera in a wrong position whose height is greater than expected\n\n\nPreferences>Navigation>View height = 1.7m (default value)\nSceneProperties>Units>Units Scale = 10 (10x default value)\nAdd a plane, it will act as a ground, scale it to 50x\nAdd a cube (default 2m)\nusing Walk navigation, enable gravity with tab, the camera will stay more or less on the same height as the cube. (1.7m ~ 2.0m), everything works as expected.\nbut, if you teleport to any location on the plane, the new camera position will be the cursor position + 17m on the Z axis instead of 1.7m on the Z axis.\nThe blend file contains a scene with a plane and a cube, all done using scene scale 10.\n\n[Scale10Problem.blend](Scale10Problem.blend)\n\n", "Mirror Uv\nThere already exists an operator called Copy Mirrored UV Coords. This could be extended to support the features described below\n\n\n- From +X to -X for example (source can be positive or negative X, Y or Z) \n- Options:\n - By object space\n - By world space\n - By topology \n\n\n\n**Starting point**\n\n\n**Desired result**\n\n", "Autokey function hinders execution of drivers\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 3.0.1\nWorked: Never (2.80+)\n\n- Open General template\n- Enable auto-keyframing in preferences for new scenes\n- Create new scene\n- Add cube\n- To Location X type `#frame`\n- Scrub timeline\n\nDriver won't update\n", "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", "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", "2d curve bevel ignores direction iff the curve is cyclic\nOperating system: Linux-5.4.0-89-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.74\n\nBroken: version: 2.93.5\nWorked: unknown\n\n\nWhen a 2D curve is NOT cyclic, reversing the direction of segments changes the orientation of the bevel. When the curve is cyclic, reversing it has no effect.\n\n\n\n1. Create two 2D curves: \"Profile\" and \"Shape\". In the Shape curve, set the bevel to use the Profile curve. Set the Shape curve to not be cyclic (in \"Active Spline\"). Give them some shape so you can tell them apart. Or download attached blend file.\n\n2. Enter edit mode on the Shape curve. Select all segments/control points, and click the menu: Segments -> Switch Direction. Notice that the Profile switches between inside and outside when you do this.\n\n3. Now turn on \"Cyclic U\" for the Shape curve, and try to switch the direction of the segments once more. It now has no visible effect. (However, it has still switched the direction of the curve, which can be seen by turning off Cyclic U after switching direction while it is on - it is just that the direction is ignored whenever Cyclic U is on.)\n\nBlend file with this situation set up:\n\n[2d-curve-bevel-bug.blend](2d-curve-bevel-bug.blend)", "Rigid body : the animation of the angle constraint parameters does not work with an animated object\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: 2.92\nWorked: don't know \n\n\nRigid body : A rigid body \"animated\" object + a another rigid body object connected with hinge rigid constraint. The animation of the angle constraint parameters does not work with an animated object. I have bugs sometimes also with other parameters like breakable . (see the blend)\n\n[rigidconstraint.blend](rigidconstraint.blend)\n\n", "Fly and walk navigation in AZERTY issues\nOperating system: windows 10\nGraphics card: rtx 3060\n\nBroken: Blender 3.6.1 (Steam)\n\n\nHello,\nIm on a AZERTY keyboard and the problem is that when i change my movements keybinds for fly (or walk) navigation it keeps repeating the action (even if i unpress the key) for the binds that i changed. For exemple i changed \"forward\" key by Z and when i press Z the camera will keep going forward forever.\n\n- Go in the View 3d fly (or walk) modal keymap settings\n- In \"Forward\" replace W by Z, \"Left\" Q by A, \"Down\" A by Q, \"Z axis correction\" Z by W\n- Go in fly (or walk) navigation mode\n- Try to move with ZQSD, A and E\n- Then when you press S,D or E it will work normaly but if you press Z, Q or A and release the key it will keep going in that direction exept if you press the opposit direction key (S for Z, D for Q, E for A)\n\nThanks for paying attention, lov u <3\n\n", "Improve auto offset when inserting new node\nIn the example below the Noise Texture node should be moved automatically as well, not just the Set Position node.\n\n[screen_recording-2021-12-13_17.34.37.mp4](screen_recording-2021-12-13_17.34.37.mp4)\n\nThe exact behavior in more complex trees still has to be designed.", "Double transform of grease pencil with lattice modifier\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.1\n\nWhen GP layer is parented to bone and then deformed with Lattice modifier, the deformation occurs in incorrect place.\nIn sample file, deformation is simplified to moving all vertices.\n\nHere is original file, where actual deformation occurs, but I think relationships could be optimized a bit:\n[simple eye lattice in gp.blend](simple_eye_lattice_in_gp.blend)\n\n\n[#89943.blend](T89943.blend)\n\n- Open file\n- Move \"handle\" bone - works as expected\n- Move \"base\" bone - not as expected", "Curves sculpting collision with surface.\n" ]

[ "Inverse Kinematics constraint written as \"Inverse Kinemarics\" when using hotkeys to bring up menu in Pose Mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.1.0 Release Candidate\n\nI'm very sorry if this has been reported, I looked but I couldn't find anything. It's a small typo where in Pose Mode, if you use \"shift + control + c\" to bring up the Bone Constraints menu, \"Inverse Kinematics\" is misspelled as \"Inverse Kinemarics\". When opening the menu from the Bone Constraints Properties, it's written correctly as \"Kinematics\".\n\nCreate an armature, add 1 or 2 bones in Edit Mode, then go to Pose Mode. Select at least two bones and use \"shift + control + c\" to bring up the bone constraints menu, and you'll see that it's written as \"Inverse Kinemarics\".\n\n" ]

[ "Cutter Tool Not Working When Lines are Drawn with the Draw Tool Using Guides\nOperating system: Windows 10\nGraphics card: Gigabyte GeForce RTX 3080\n\nBroken: 3.5.1\nWorked: Never tried it in older versions\n\nI use the Guides function to draw in perspective; however, the Cutter tool won't cut the lines correctly when the Guides function is used to draw the lines. Sometimes, it cuts them oddly. Most of the time, it doesn't cut them at all. When I use the Draw tool and manually draw in perspective (without using the Guides function), the Cutter tool works fine. \n\nStrokes drawn with \"guide\" options are not cleared in some cases with cutter tool\n\n- Use the Cutter tool on these to cut the lines from the intersections. I've named the layers appropriately.\n", "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)", "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", "Curve / Geometry / Bevel Objects don't accept Mirror Curve\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n[i try to use a curve with mirror modifier, to use it as Bevel Object in ObjectDataProperties Curve. Now i see the half , it miss the modifier]\n\nCreate curve with mirror modifier, add it to new curve inside ObjectDataProperties Bevel Objet\n[CurveBevelMirror.blend](CurveBevelMirror.blend)\n\n", "Attribute Editing\n## Attribute Editing\n\nFor the original design task see #97168\n\n* Mesh, curves, and point clouds\n* Edit mode\n * Use case is as an input for procedural generators\n * Miscellaneous features like randomize attributes, etc.\n * Operators act on the active attribute\n * All attributes are displayed for the active element in the viewport sidebar \"Attributes\" panel\n * For multiple selection\n * The buttons/sliders \"offset\" the mean value\n * Operator to set all selected elements to a value (prefilled with active value)\n * Attribute overlay for active attribute\n * Drawing edge attributes\n * Thick wireframe drawing like seams, bevel weights, etc.\n * Gizmos to edit original data (for later)\n * Checkboxes for booleans\n * For vectors: directions, offsets, etc.\n * Rotation gizmos\n * Connects to the node tools project a bit\n* Attribute paint modes\n * Artistic paint mode\n * Supports meshes\n * Point and corner domain and color types and float attributes/textures\n * Sculpt color implementation should apply to any attribute type (within reason)\n * Technical paint mode\n * Supports meshes, curves, points\n * Supports any domain and any type with special tools for some types, also supports textures\n * In between edit mode and the more artistic painting currently in sculpt mode\n * Choose a value of any type and paint it directly\n * More advanced painting\n * Flow maps\n * Face set interaction like sculpt mode\n * An option on the attribute chooses whether it shows in the more artistic mode\n * Paint canvas\n * Texture canvas\n * Choose between a list of all textures associated with an object\n * The canvas can be sourced from (1) material + layer stacks; (2) modifiers; (3) attributes\n * The source is used for filtering and visual clues\n * Embrace syncing the active texture between the node editor and the paint modes\n * Make setting the active texture canvas active an explicit action\n * UV is set per layer stack, or sourced automatically from the node texture\n * Multi-object texturing\n * Painting on the same texture across multiple objects\n * Bleeding should be smart about other users of the same texture\n\n", "Implement drag and drop in ID text fields (ID name and/or paths)\nWindows 7 x64\n\nBroken: 705c43b\n\nwhen drag dropping images in the texture node's path field, it should replace the current texture name with the dragged and dropped one, but instead it does like if you dropped in empty space and adds a new texture node.\n\nOpen attached file, replace one of the windows with a file browser in a location where you have some images. Then drag that image over the texture name filed of the texture node. Tooltip shows that the field is recognised correctly by changing from 'add new node' to 'paste name'. But if you drop, it will do as if you dropped in empty space and add a new node.[bug drag and drop tex node.blend](bug_drag_and_drop_tex_node.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", "Artefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel\nWindows 7 Ultimate, 64-bit SP1\nGeForce GTX 750 Ti\n\nversion: 2.79 (sub 1), branch: master, commit date: 2017-10-10 07:26, hash: 8d73ba5, type: Release\nbuild date: Tue 10/10/2017, 10:00 AM\n\nArtefacts on render passes Shadow and Diffuse Direct when rendering image texture with zero value in a channel. The scene is lighted with 3 spots each absolute red, green and blue.\n\n- Create a texture image file with absolute 0 spots in one channel. Or use this one: \n- Create a scene with 3 spots lights, each colored with an absolute red, green and blue color.\n- Add a random object with uvs\n- Assign the texture image file to the object (Tested with Principled BSDF, Diffuse BSDF, Toon BSDF).\n- Add Diffuse Direct and Shadow pass.\n- Render, get this: \n\n**Additionnal infos**\n- Other channels render correctly\n- Scene is lighted only with direct lights, bounces are set to 0.\n- Clamping lowest values to 1 in the texture map resolves the artefact partially.\n- Also shortly tested on unix system.\n- Blender file: \n[bug_cycles.blend](bug_cycles.blend)", "Unbaked Dynamic Paint Not Displayed in Rendered Output but Shows in Viewport\nOperating system: Manjaro 18.0.1 Illyria / x86_64 Linux 4.14.90-1-MANJARO\nGraphics card: Nvidia 1080 Ti\n\nBroken: 2.80 (sub 39), Commit date: 2018-12-29 18:10, Hash 266b1e2cdbc1\nWorked: 2.79 (sub 6), Commit date: 2018-10-22 16:17, Hash 86dbbd156fa\n\nUnless baked, dynamic paint does not affect the final rendered image but is properly displayed in viewport.\nThe default and expected behavior is to be able to render the effect regardless if baked or not. This is how 2.7x operated in the past.\nMoreover this problem, which I assume has something to do with vertex colors [has caused other issues ]] with different [[ https:*github.com/hsab/tensionmap | addons ](https:*github.com/JacquesLucke/animation_nodes/issues/989) that depend on similar workflows of modifying the vertex color using the python API (eg. proximity, stress mapping etc.) \nNot sure if #51214 is related since it's from April 2017. If so please close as a duplicate.\n\nTwo blend files attached, one for 2.8 and one for 2.79.\n2.79 file works as expected.\n2.8 file is broken unless baked.\n\n2.79.6 Render:\n\n\n2.80.0 render:\n\n\n[dynamicpaint2.8.blend](dynamicpaint2.8.blend)\n[dynamicpaint2.79.blend](dynamicpaint2.79.blend)", "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", "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", "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.", "Graph Editor: Curve drawing improvements\nProblem: keyframe dots can be somewhat hard to see, especially behind the current frame marker line.\n\n\n\n**Proposal**:\n- Change the default theme to draw the keyframe dots larger. The current theme draws at 6px, for modern displays this should probably be increased to 7-9px. It's probably better to defer a concrete choice for this until #68982 (Graph Editor: UI Scale effect on Curves drawing) is done.\n- Draw keyframe dots of selected keyframes on top of current frame line. Keep drawing unselected keyframe dots behind the line.\n", "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", "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" ]

[ "Sculpt: curve stroke method Draw Curve button does not 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 54)\nWorked: (optional)\n\n\nthere does not seem to be a way to draw a curve in sculpting please see video link (very sorry if I just don't understand how it works but i cant find any documentation on it)\nopen?id=1LvjeMgiCQPuSbTp9J_RqnStwUMm_TQXg \n\n\n" ]

[ "Broken/weird Continuous Grab behaviour\nOperating system: Linux-5.8.0-43-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: SVGA3D; build: RELEASE; LLVM; VMware, Inc. 3.3 (Core Profile) Mesa 20.2.6\n\nBroken: version: 2.93.0 Alpha\n\nbroken/weird behaviour under VMWare Player/Workstation 14.1.2+, Ubuntu 20.04.2 LTS\nEdit -> Preferences -> Input -> Continuous Grab\n|[2021-02-27 03-11-16.mp4](2021-02-27_03-11-16.mp4)|[cursorbug.mp4](https://archive.blender.org/developer/F13560997/cursorbug.mp4)\n| -- | -- |\n\n- activate grab mode (G-key) in the viewport or in any blender's area which support 'Continuous Grab'\n- drag mouse toward area top or bottom edge\n\nAlternatively:\n- Active walk navigation and quickly move the mouse outside of the Blender window. \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", "Sculpted models in Solid or Wireframe viewports do not update in other Material or Rendered viewports when changes are undone (Undo). This can cause a desync that the artist may not notice until it's too late.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.90.0\n\nSuppose there are two viewports, one in Material Preview or Rendered shading mode and the second viewport in Solid or Wireframe shading. I sculpt the mesh in the Solid or Wireframe (I don't sculpt in Wireframe at all, but this problem occurs in that mode as well) viewport and then undo the changes, but the undo does not update the model in the Material Preview or Rendered viewports.\n\nWhy I sculpt this way and why this error (or by design) is problematic and annoying:\n- I can see the topology much better in Solid shading with matcaps. However, I also want to be able to see how the sculpt looks under more finalized lighting settings in real-time while I edit and experiment with different sculpting or placement of facial features, for example.\n- I am constantly undoing brush strokes in a sort of error-correction method of sculpting. Naturally, reducing undoing strokes would be more efficient overall, but not being able to see the reverted mesh from undoing strokes absolutely debillitates confidence of an artist when they're suddenly not working on the most updated model.\n- This can cause bad sculpting errors as one looks from one viewport to the other to \"sanity check\" or simply check progress and be fooled into thinking that the models are synced, when they're actually desynced. The artist might not notice this and continue sculpting, which will update both views again, but it can cause unintentional sculpting errors.\n\nI'm not sure if this was a conscious design choice (2.82 also has this problem. I did not test pre-2.79 versions), but if it was, it makes absolutely no sense why there is even the possibility of anything desyncing between viewports, no matter how the artist works. It just makes me question all the time whether or not me activating Undo actually did anything at all, which causes even more frustration.\n\n1) Create a sphere.\n2) Split window into two viewports.\n3) Change shading mode of one viewport to either Material Preview or Rendered and the other viewport to Solid or Wireframe.\n4) Sculpt sphere in solid mode.\n5) Ctrl+Z to Undo.\n6) Undo is not updated in Material Preview or Rendered viewports.\n\n\n", "Serious problems with visibility when linking a character\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.3\n\n\nwhen linking a collection containing a character model, rig, etc., oddities occur with the visibility of the armature: when the overlays are turned off/ on, the armature is not displayed until some event occurs (this bug applies to the file where the model is located). undo ignores hiding bones (scene with linked and override character) for clarity, two animation files will be attached. in both, sometimes both of these bugs occur, while it is absolutely unpredictable\n[2022-09-16 02-20-35.mp4](2022-09-16_02-20-35.mp4)\n\n[broken_7.zip](broken_7.zip)\n\nfile with character in broken_7/stalker/\nfiles with animation in broken_7/3d_projects/tests/animation/\n", "Undo of operations on modifiers is inconsistent when object is in edit mode\nBroken: version: 2.79, 2.82 (sub 1), branch: master, commit date: 2019-11-22 18:14, hash: 373e936e3e\n\n\nwhen a modifier that has been **added in edit mode** to a object and is **deleted in edit mode,** it is not restored when using undo. \nThe operation shows up in the undo history but does nothing.\n\n\n1. go into edit mode\n2. add a modifier\n3. delete the modifier\n4. use undo, notice modifier is not restored.\n\ncreating the modifier in object mode or deleting it in object mode will restore it when using undo. this is a very confusion inconsistency that i noticed with the new undo method.\n", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "VSE Transform Tools: Images moved outside the preview area disappear\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\n\nImages moved outside the preview area disappear when unselected.\n\nWhen moving elements outside the visible area, they're drawn under the dark area, so they simply disappear if you deselect them. They should be drawn on top of the dark area instead. In the 3d view elements are not covered by black, so this is also inconsistent behaviour. \n\n{[F10405609](outside.gif), size=full}\n\nD12105#326398\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", "Keymap changes are not reflected for the local view setting\nOperating system: Linux-5.18.10-arch1-1-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.57\n\nBroken: version: 3.3.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked:\n\nWhen I turn off frame selected in keymap -> local view and restore it to its default it keeps the old behavior until blender is restarted.\n\nI tested changing delete in object mode (x) key to disable confirm and when I restored it it worked as expected so I think it is related to local view specifically.\n\n- Open default scene\n- In Preferences > Keymap: search for local view and uncheck `Frame selected` checkbox\n- use the shortcut in viewport. Notice frame select operation is not performed (which is expected)\n- In keymap, restore changes\n- Again use shortcut to switch to local view (frame selected operation is expected to execute but it doesn't)\n\n\n", "Viewport view resets after navigating within the Camera view\nOperating system: Pop!_Os 20.04\nGraphics card: Nvidia GTX 1080ti\n\nBroken: 3.0 Beta, 7a5b8cb20284, master, 2021-11- 05, 2.83, 2.79... etc\nWorked: Has never worked\n\nWhen navigating in camera view, if the user goes back to Viewport view it will reset the Viewport back to the world origin\n\n- New File\n- Add Camera\n- Navigate anywhere in Viewport view\n- Go into Camera view\n- Navigate again inside Camera view (use walk navigation)\n- Go back into Viewport view\n- Viewport will reset back to world origin\n\nNOTE: this only happens if you navigate inside the camera, if you go back to Viewport view using the middle mouse button it wont happen\n\n| Blender 3.0 | 2.83.16 | 2.79 |\n| -- | -- | -- |\n| [Peek 2021-11-07 04-54.mp4](Peek_2021-11-07_04-54.mp4) | [Peek 2021-11-07 05-05.mp4](Peek_2021-11-07_05-05.mp4) | [Peek 2021-11-07 05-09.mp4](Peek_2021-11-07_05-09.mp4) |\n", "Viewport switches needlessly to perspective mode, when changing from camera-view to local-view // Auto perspective is turned OFF.\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.59\n\nBroken: version: 3.3.0\n\nWhen in camera-view and hitting Numpad Dash to get into local view of selected object, the 3D-Viewport ALWAYS goes into perspective mode needlessly. **Auto-perspective is turned off.**\n\n\n- Open attached .blend file.\n- Cube is already selected.\n- Camera-view **(Numpad 0**) is also already set\n- Hit **Numpad Dash** to go to local view of selected Cube. (**3D-Viewport is now in perspective mode.**)\n[Perspective.blend](Perspective.blend).\n\n\n\n**To further add to the unnecessary switch of view-mode:**\nWhile in perspective local view of the cube as described above, hit **Numpad 5** to switch to orthographic view.\nNow tab**Numpad 0** to go back to camera-view.\nHit **Numpad Dash** again to go to local-view of the cube again.\nOnce again, you are needlessly in perspective mode.\n\nThanks for any fix on this issue.", "Unable to adjust Opacity of Camera Background Image\nOperating system: Linux-5.11.0-43-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: Mesa Intel(R) Xe Graphics (TGL GT2) Intel 4.6 (Core Profile) Mesa 21.0.3\n\nBroken: version: 3.0.1; Also tested broken in Blender 2.93.1 and 2.93.5.\n\nWorked: (newest version of Blender that worked as expected) 2.83.18\n\n\n**Opacity of camera background image cannot be adjusted.**\n\n\n\n\n- select camera\n- switch to active camera view\n- check camera background image\n- add camera background image\n- adjust opacity slider (Nothing happens - image remains at 100% opacity)\n\n\n\n\n\n", "Regression: Unable to move camera/area light with gizmo (intel GPU)\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics Intel 4.5.0 - Build 30.0.101.1122\n\nBroken: version: 3.2.0, 3.3\nWorked: 3.1\nCaused by 5045968f24\n\ni cant move my camera using move tool or tranform tool on left side bar\n\n- select camera\n- Choose move or transform tool\n- Move camera with gizmo (won't be able to move)\n\n[bug camera.blend](bug_camera.blend)\n[blender 3.2.mkv](blender_3.2.mkv)", "Viewer Node from Compositor is not updated in Camera's Background Image\nOperating system: Arch Linux\n\nBroken: 3.2.2\nWorked: never\n\nThe viewer node result from compositor is not propagated in the 3D viewport as a camera background image when selected. This might be really useful in many cases. I often use compositor to edit input videos and I want to adjust the 3D scene according to the video. Especially with the grease pencil, there might be a case when the animator wants to draw an animation over an existing one. It is really strange that the option to use the node is there but it's unusable, related to #73188.\n\n**Possible problems**\nRecursion mentioned in #73182. Might be resolved by overriding the order when the node is used in the camera or letting the user change the order somewhere.\n\n**Workaround**\nExport the composited result in a video and then use as a background image or hit F12 after every frame and use the render result in the background image.\n\n1. Create a setup in compositor that changes over time\n2. Connect the result to Viewer node\n3. Use Viewer node as camera background image in the 3D scene\n4. Move to another frame - no change in the background image\n\nIncluded the project file with simple texture animation and two workspaces. One with split screen where both compositor and 3D view are visible. When the compositor is hidden, the background image is not changed at all. When it's visible, it's updated but from the previous frame or state. It seems like the camera first takes the compositor result as the background and then the new compositing takes place. Yes, I understand that it's the design of these stages but this is still a trick to somehow make it work, the image does not update at all without the compositor window being active as shown in the second workspace.\n\n[viewerNodeInCamera.blend](viewerNodeInCamera.blend)", "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" ]

[ "No undo when moving viewport with camera locked to view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Quadro P5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.5\n\nWhen the camera is locked to the viewport, moving the viewport with the MMB moves the camera, as expected. However there is no undo if the user accidentally moves the viewport (which happens all the time).\n\nin the N side-menu check view>Lock>Camera to View\nhit 0 to enter camera view in a 3D viewport\nrotate the view with the MMB\nUndo\nExpected: camera goes back to default position\nObserved: camera stays in niew position\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", "Generated Texture Coordinate Node In Shader Creates Broken Pattern Upon Applying Subdivision After Armature Modifier \nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.3.1\nWorked: Blender 3.2\n\nWhen I use the Generated value of a Texture Coordinate node, and have a modifier stack with an Armature above and a Subdivision below, it creates a really weird result [broke.blend](broke.blend)\n\n\n - Check the .blend file and simply activate the Subdivision modifier on the model\n\n\n\n\n", "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", "Object Font does not respect Text Offset X/Y\nOperating system: Linux-5.10.96-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 2.93.7 Release Candidate\nWorked: ?\n\nObject Font respects all of the text-placement features (character, word, line spacing, size, text-box size and text-box offset), but it does not respect simple Offset X/Offset Y.\n\nOpen the .blend file, fiddle with the values, and observe.\n(Of note: it also doesn't respect the 'Shear' feature, but I don't think this is a bug.)\n[text_bug_2.blend](text_bug_2.blend)\nThanks.\n\n", "Graph Editor generator for angles works in Radians while the graph editor displays the result in degrees.\n**System Information:**\nN/A\n\nBroken: Blender 2.80 Beta (18e5540a48b6) and Blender 2.79 (e290a0b0568e)\n\n**Short description of error:**\nIf you use the \"generator\" modifier in the graph editor for an angle, the generator will work in radians while the graph editor will display the output in degrees.\n\n1. Open the startup file.\n2. Select the default cube and key frame one of the rotational axis.\n3. Open a graph editor and give the \"key framed rotation\" an \"generator\" modifier.\n4. When entering values into the modifier such as 0 and 1 so your polynomial is y=x, the result shown on the graph editor is y=57.3x. This is because the values input to the generator is read as radians while the scale in the graph editor is read in degrees.\n\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", "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", "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)", "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", "Regression: Changes in curve normal behavior\nBroken: 3.0\nWorked: 2.92\n\nInstead of a simple arrow, the scene is something very remotely in the neighbourhood of that shape plus random extruded edges. \n\nOpen example file.\n\n", "Curve Deform Node\nNOTE: The design below is outdated. A curve deform node should be a field node now, with a vector input and output, and a curve input. Arguably it should just be a node group too.\n\n\n| {[F10152887](image.png) size=full}| {[F10152878](image.png) size=full} | {[F10152882](image.png) size=full} |\n| -- | -- | -- |\n\n\nThis is task is for a port of the \"Curve\" modifier to a node.\n{[F10150643](image.png), size=50%}\n\n\n**Details**\n* Any geometry component with a position attribute is supported by this node.\n* Only the first spline of the curve is used for deformation.\n* Two input modes modes are available. \n**The position mode uses point positions for the curve parameters.*** The position input is provided for convenience. In most common cases, a single axis of the position is used as a parameter for the curve.\n***The position is mapped to the curve based on length. So \"x=5m\" means, transform by traveling 5m along the spline. This is how the modifier works.** The attribute input mode uses any float attribute between zero and one, as a factor along the length of the curve.\n** For convenience, a \"Float\" option is available for the attribute when the whole geometry should have the same parameter.\n* Extrapolation should be handled by a separate node that can extrapolate a spline.\n \n\n**Further Questions**\n* Is an \"influence\" attribute input really necessary? The same thing could be achieved by mixing a copied position attribute before starting the operation.\n** The answer to this question will apply to other operations as well.\n* Which of the three \"Curve Deform\" settings are necessary in this node? \"Use Radius\" is likely not necessary, the attribute could just be filled beforehand.\n\n**Related Nodes**\n* A \"Curve Sample\" node could do a similar operation, but instead of deforming positions, it would sample an attribute along the length of a curve based on the same mapping controls.\n** This could be useful to have more flexible control of attributes with curves.\n\n\n**Implementation**\nThe implementation should be straightforward. Sampling arbitrary points along the curve is an natural extension of the uniform sampling that is already implemented.\nCurve parameters should be sorted before, and then changed into evaluated point indices and factors.\nThen, interpolation between the transform of neighboring evaluated points should be quite simple.\n", "Mesh Deform modifier doesn't deform after binding\nBlender 3.3.0 (hash: 0759f671ce1f)\n\nMesh Deform modifier simply doesn't work. The cage mesh doesn't deform the effected mesh.\n\nI modeled my base mesh (a simple array of duplicated rectangles). Then i added a cube, as a separate object, entered Edit Mode, adjusted the size to fit my base mesh, added some loop cuts, exited Edit Mode. Selected my base mesh, added the Mesh Deform modifier, chose the object to deform with, clicked on Bind. \n\n[mesh deform.blend](mesh_deform.blend)\nThe deformation mesh is a solid geometry. I just changed the Viewport Display option to Wire. ", "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", "Curve \"solidify\" modifier glitch\nOperating system: Windows 7\nGraphics card: GT750M\n\nBroken: 2.80, 2019-02-28\nWorked:\n\nWhen applying a \"Solidify\" modifier to a bezier curve shape (or imported SVG), it creates random height vector points, creating strange triangles. This can be fixed by simply selecting the errored vector point then selecting one of the transform value (in my case it was Y) in the panel and either pushing enter (keeping the same value) or unselecting the vector point.\n\n\nAttached blend file with imported SVG.\n\n", "Constrain axis always draws on top [covers mesh in unfavorable ways]\nThe mesh outline is not visible when extruding or moving along the axes. The axes overlap the faces of the mesh themselves, and because of this, it is not convenient to precisely position the extruded faces.\nIt exists on all versions of the 2.8x blender.\n\nTo repeat the problem, you can select an edge in the editing mode and simply drag along the y axis. In this case, the contour will not be visible by how much it is moved from its actual position.\n\n\n\nWith the same action in 2.79, I see black the contours of the mesh as far as it changes when moving.\nBring it back as it was in 2.79" ]

[ "Simple Deform modifier in bend mode doesn't work on thin geometry\nOperating system: Windows 10\nGraphics card: GTX1080Ti\n\nBroken: 2.8 latest master\nWorked: Probably never\n\nSimple Deform modifier in Bend mode doesn't work on thin geometry, such as plane. It's a very common workflow to bend a simple rectangular plane.\n\n1, In a new blender file, create a plane\n2, Enter edit mode of the plane, and subdivide the plane a few times to get enough topological density for bending\n3, Exit edit mode and apply Simple Deform modifier on the plane\n4, Switch Simple Deform mode to Bend\n5, Notice that despite Deform angle being set to 45°, the modifier has no effect on X axis\n6, Switch to Y axis and notice the modifier has also no effect\n7, Switch to Z axis and notice the modifier has effect, although Z axis is the least likely axis user will want to bend a plane along.\n\nResult: Simple Deform modifier set to Bend mode works only on Z axis if the geometry is thin (planar)\n\nExpected: Simple Deform modifier in Bend mode works on any kind of geometry." ]

[ "Unexpected behavior when applying Geometry Nodes modifier on top of the Multires.\nThis is a more comprehensive report on a bug that was recently posted and closed [HERE ](T97603)\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1+\n\nApplying Geometry Nodes on top of the Multires modifier does not give expected results. Multires is an exception from the \"Applying a modifier will apply it as if it was first in the stack\" rule, when a modifier is applied on top of the Multires, the mesh changes will be applied to the currently visible subdivision level. Quick video below.\n[Multires GNodes Bug.mp4](Multires_GNodes_Bug.mp4)\nAnd the Example .blend file > [Multires GN Bug.blend](Multires_GN_Bug.blend)\n\nHow should applying the Geometry Nodes behave ? When the Geometry Nodes modifier doesn't change the vertex count and simply deforms the mesh, it should behave just like any other modifier, see example video with the Shrinkwrap modifier. \nSo what when Geometry Nodes does change the vertex count ? I say we keep the same behavior that solidify modifier has, it skips Multires and applies it as it would be first in the stack. While of course this will bring broken results, this is a already an existing behavior so i think it would be completely fine.\n\nSeries of images presenting how applying a Solidify modifier on top of Multires behaves. (Intended behavior)\n\n\n\n\n\n\n\n", "Cloth simulation does not work for a basic plane, having some specific location values.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: AMD Radeon R5 M335 ATI Technologies Inc. 4.5.13587 Core Profile Context 19.50.26 26.20.15026.1\n\nBroken: version: 3.6.1\nWorked: Nothing found, same error with 3.3, 3.4, 3.5, 4.0 versions\n\nCloth physics in Blender seems to have a bug. It does not work correctly when the cloth object has some specific locations. Exact steps to reproduce the error are given below. The same cloth physics without any change seems to again work when the object is moved to another location. I could not establish any specific pattern between the location and the working/non-working status, but changing the location randomly solves the issue - although temporarily. If we again move it back to the previous location, cloth physics again stops to work. This is happening with all versions of Blender from 3.3 to 4.0 as far as I could test. I am reporting this officially for 3.6.1 latest version.\n\n1. Start with the default scene and delete the default cube.\n2. Add a plane, change X-rotation to 90 and Y-location to -2 (minus 2).\n3. Go to edit mode, right-click and subdivide, set subdivision level to 6.\n4. Select only the top-left & bottom-left vertices (blend file is attached for reference).\n5. Create a new vertex group and assign the selected vertices to this vertex group.\n6. Back to the object mode, add cloth physics with all default options.\n7. Enable self collisions, and select the above vertex group in the Pin group.\n8. Now run the simulation, or bake it and run. The cloth physics does not work.\n9. Now change the Y-location to zero. Cloth physics starts working after a few frames.\n10. Again change the Y-location to minus 2. Cloth physics stops working like before.\n\n", "Edge overlay seems to do nothing expected\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 511.23\n\nBroken: version: 3.1.0\nWorked: 2.79\n\nBack in 2.79, we could disable the \"edge\" overlay in edit mode. This was useful I.E. in cases where highlighting edges in vertex selection mode made things hard to read :\n\n\nIn the current stable version, this option seems to do nothing:\n\n\n\nActually, when in solid mode, it seems to display another layer of wireframe on top of the already existing one, which definitely looks weird and pointless. GIF demo:\n\n\n\nOn a mesh in edit mode, try toggling the edge overlay on and off.\n\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}", "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", "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", "Box tool in Ortho does not behave as expected.\nPlace the 3D Cursor where you want the box to appear. Go to an orthographic projection view of X Y or Z. Trying to create a box results in a box with max value dimensions and sometimes crashes Blender.\n\nExpected behavior would be to go to the X orthographic view, draw a rectangle for the X and Z dimensions, and be able to type in the X dimension, see a callout for the X or type in the X dimension.\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.45\n\nBroken: version: 2.90.0 Alpha\n\n\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", "Symmetry on sculpt mode won't work with auto masking topology enabled\nOperating system: Windows-11\nGraphics card:Quadro RTX 3000/PCIe/SSE2\n\nBroken: Blender 3.5.0\nWorked: N/A\n\nSymmetry on sculpt mode won't work with auto masking topology enabled.\n\n\n- Have a mesh that has two disconnected parts across a symmetry axis.\n- Enter sculpt mode, turn on \"Advanced -> Topology\" (topology auto masking).\n- Turn on X symmetry for sculpting brushes.\n- Sculpt on one part of the mesh, the opposite side doesn't change.\n", "can't use boolean modifier to mask out Geometry Node text, bleed text & flickering in some frames\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: Quadro P4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 397.93\n\nBroken: version: 3.1.0 Alpha\n\ncan't use boolean modifier to mask out Geometry Node text, bleed text & flickering in some frames.\n\nin frame 139, 148, 149, 306, 353 text bleed out of mask_text box Boolean object\n\n[2021_Ecard_1920x976_23d.blend](2021_Ecard_1920x976_23d.blend)\n\n[2021_Ecard_1920x976_23d0001-0420.mp4](2021_Ecard_1920x976_23d0001-0420.mp4)\n\nThanks for your help!", "Cache loading via animation system\nCurrently the Cache Sequence modifier is used for loading geometry data from Alembic files, and the Transform Cache constraint is used for loading transformation data. This approach poses a few limitations:\n- A modifier is either generative or deforming, whereas the Cache Sequence modifier is both (depending on the particular frame-to-frame changes in the Alembic file).\n- Non-mesh geometry data (like curves) are troublesome to load, as the modifier system can only produce an evaluated mesh (#51311).\n- Non-geometry, non-transform properties, if loaded at all, are loaded at import time, but after that are static (#54050, #50725). This can be solved by having per-property F-curve modifiers ([D2324](D2324)), but this is cumbersome and unintuitive to handle.\n\nThis task proposes a new approach, adding a 'cache' step to the `AnimData` struct. If set, cached data would be loaded by the animation system first, before applying F-curves and drivers as usual. This would allow the cache loader to influence properties in a more general way:\n- It's a new system, so no pre-existing separation between 'generative' and 'deforming'.\n- Any ID datablock that supports animation can use this, so no distinction between mesh and non-mesh geometry.\n- Any property can be animated.\n\nI'll study the current animation system, and then update this task with more technical details on how to approach this.\n", "Bevel Bug\nblender-2.80-07765499abee-win64 \n\n**cylinder :**\non the cylinder with a lot of segments, bevel doesn't merge in one point. Create nice see n-gon(normal we must see the only verts in one point)\n\n\n**Cube :**\nThe middle loop has deformed when we bevel sharp corner for small mesh. On the large mesh, we cant see this deform .\n\n\n[Cylinder_Bevel_Bug.blend](Cylinder_Bevel_Bug.blend)\n\n[Cube_Bevel_Symmetry_Bug.blend](Cube_Bevel_Symmetry_Bug.blend)\n ", "Surface Deform modifier always updates when selecting objects\nOperating system: Windows 10\nGraphics card: NVidia GTX1080\n\n2.93.1, 2.93.3\n\nSurface Deform modifier causes click lag even if object or/and the modifier is disabled in viewport. It doesn't affect camera panning or rotation.\nWhile I'm at it, it also seems to keep unnecessary data in saved file. I wanted to provide an example file, but it turned out to be over 1 GB. I don't see why it keeps the deformed mesh in the file rather than recalculating it when we enable it or open the file.\nIt seemed to me to be the best way of making a chainmail, but I can't work with the lag.\n\n1. Subdivide the default cube with 7-10 cuts (7 enough for my PC, if in the end it doesn't lag, try more divisions).\n2. Duplicate the cube.\n3. Add subdivision modifier (level=6) to 2nd Cube, then add Surface Deform, set the source to 1st Cube, bind.\n4. Disable both objects in viewport, you can even disable the modifiers.\n5. Add a new Cube to the scene. Try selecting and deselecting in in the viewport. There's a lag. Camera panning and rotation works fine. The only way to fix the lag is to apply or remove the Surface Deform modifier.\n6. Save the file. Our file is just 396 faces with modifiers applied. It's over 1GB in size.\n\nVideo: hEQnVVvPEGU\n\nor\n- Open .blend file\n- Bind mesh to the target\n- Try to select the Cube.001 in viewport\n[#90985.blend](T90985.blend)\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)", "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" ]

[ "Simple deform modifier - bend seems broken 2.80, 2.81\nOperating system: Win 10\n\nBroken: 2.80 release, 2.81 e2df789c4800 \nWorked: Probably, never (Not since the axis selection was implemented)\n\nThe simple deform modifier bends an object around an absolutely arbitrary point in space. \n\n1. Subdivide the default cube a bunch of times, scale it up by X in edit mode.\n2. Add Simple deform modifier, set mode to bend, angle to 45, axis to Z. Look at the expected behavior, remember it well.\n2. Change axis to Y. Look at the unexpected behavior.\n\n\n(The red outline is what I would expect it to do)\n\nIt looks like the problem is that the object doesn't bend around it's origin, but around some arbitrary point in space.\nThe problem persists when trying to bend an object around another object using the offset origin option. The result is absolutely unpredictable.\n[bend.blend](bend.blend)" ]

[ "QuadriFlow remesh does not work on tiny objects\nOperating system: Linux-6.2.9-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits\nGraphics card: Mesa Intel(R) Iris(R) Plus Graphics (ICL GT1.5) Intel 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 3.5.0\nWorked: None (I only tested 3.4)\n\nQuadriFlow does not work for tiny objects, but the same mesh works if scaled up.\n\n1. Start blender, create an icoSphere\n2. Scale it down a lot (about 1/5000), apply scale\n3. Now try to QuadriFlow remesh the sphere\n\nBlender says \"QuadriFlow: The mesh needs to be manifold and have face normals that point in a consistent direction\", but the mesh is clearly good and clean.\n\nIf we scale the object up to the original size and apply scale, QuadriFlow works again.\n\nWhy this matters: when using a custom scene unit scale, models that look normal can be mapped to tiny sizes internally, and the error message is very misleading.\n\nI attached a reproducing blend file. The sphere cannot be QuadreFlow remeshed, but if the scale is applied, remesh works again.\n\n", "Bevel: Weird result for 6-edge star corner\nOperating system: Windows-11 22H2 22621.1194 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.5.1\nWorked: Never.\n\nNon correct bevel working\n\nNon correct bevel working with shape value = 1 on specific angled polygons. It can be seen on screenshots and in .blend file below\n\n", "Bisect Tool rotation handle does not work from some preset orthographic views\nOperating system: Windows 10\nGraphics card: RTX 2070\n\nBroken: 2.91.2\n\n\nBisect Tool rotation handle does not work from some preset orthographic views.\n\n* Select default cube\n* Enter edit mode\n* Press numpad 1 to enter front orthographic view\n* Select all verts\n* Click bisect tool\n* Draw line across cube\n* Click circle widget to rotate bisection <- fails\n\nWorks fine from top orthographic view and from arbitrarily orientated perspective views.", "bevel (Miter Outer) + mirror modifier gives inconsistent result.\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\n\nMirror + Bevel modifier sometimes give some inconsistent result when using the \"Miter Outer\" options.\n\nOpen the file to see the error.\nThank you\n\n\n[bevel.blend](bevel.blend)\n\n\n\n\n\n", "Material glitches at joints when using Bevel modifier\nOperating system: Ubuntu 20.04.3 LTS\nGraphics card: GeForce RTX 2060\n\nBroken: 3.1.2, cc66d1020c3b, master, 2022-03-31\nWorked:\n\n\nI know people experience no end of unexpected Bevel behavior due to issues with their geometry. But I think this is a genuine bug - as do people who responded to my Blender SE question: 124535\n\nRobin Betts commented there that \"it looks like a bug. But at least a consistent, and therefore traceable bug. It seems to be in the 'Automatic' (-1) material offset setting, which should split the bevel down the middle at material boundaries. It's getting the boundary 1-off at the end of a patch/arc spread of faces.\"\n\nAt joints where two materials meet, the Bevel modifier seems to miscalculate which faces of the bevel should contain one material and which the other, as shown here:\n\n\n\nIf I apply the modifier, I can then correct the issue by hand.\n\nThe above picture is from Blender 3.1.2. The problem seems to have been there for a long time, things look different but are still incorrect in 2.93.7:\n\n\n\nThe complete mesh is fairly simple (I cut it out of a larger object for this bug report) and I've confirmed there are no overlapping vertices etc.:\n\n\n\nI actually started with a much simpler mesh but converted to triangles to ensure the issue wasn't somehow n-gon related (it isn't):\n\n\n\n\nCreate a simple shape like the one shown in the last image above and use two different materials for your object, e.g. above, I've applied one material to the darker colored faces and the other to the lighter colored faces.\n\nThen apply a *Bevel* modifier and then look at the object in a *Viewport Shading* mode that shows materials, e.g. *Material Preview* or *Rendered* (you can even see the issue with *Solid* viewport shading if you set the *Viewport Display* for one of the materials to be a different color to the default grey).\n\nHere are two small `.blend` files - the first created in Blender 3.1.2 and the second in Blender 2.93.7:\n\n[bevel-3.1.2.blend](bevel-3.1.2.blend)\n\n[bevel-2.93.7.blend](bevel-2.93.7.blend)\n\nYou can find a larger `.blend` file containing the original full mesh in my Blender SE question: 124535", "Cycles: principled BSDF thin surface support\n[D2354: Thin surface approximation for Cycles Disney BSDF](D2354)\n\nRebase and benchmark performance impact.", "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", "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", "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", "Spreadsheet not reading evaluated `bevel_weight_edge` attribute\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 535.98\n\nBroken: version: 4.0.0 Alpha\n\nthe `bevel_weight_edge` isn't being displayed with the correct value in the spreadsheet, both for GN geometry[^1] and original[^2] geometry [not made in GN]; both when the bevel weight is set in GN[^1], and when it's set in edit mode[^2].\nalthough, when using the *viewer node* the correct value is displayed[^1].\n\nThis could be happeding with other attribute, but I haven't tested.\n\nset the bevel weight (any way you'd like) and look in the spreadsheet.\n\n[^1]: <video src=\"attachment\" title=\"2023-07-08 22-47-22.mp4\" controls></video>. \n[^2]:<video src=\"attachment\" title=\"2023-07-08 23-02-16.mp4\" controls></video>\n\n", "Bevel when part of mesh is hidden results sometimes in wrong selection of vertices\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 3.2.0 Alpha\nalso broken in the latest official release of version 3.1.2, also broken in 2.93.\n\nBevel when part of the mesh is hidden and the selected points are not all connected results sometimes in the wrong selection of vertices and lines. I have noticed that the selection is wrong if the number of segments in the bevel attrributes is odd.\n\nOn the default startup file do the following:\n1. Edit the default cube, inset the top and bottom face \n2. Inset again, but only 0.001 \n3. Scale the selection in the Z by 0, \n4. Expand the selection (CTRL++)\n\n5. Shift+H to hide everything currently not selected\n6. Only select the top and bottom \n7. Try beveling, play a little with the segments and switch between vertex and line selection, you will see that not all the lines and not all the vertices that should be selected are selected. It seems to be wrong when you try odd number of segments\n\n\n\n\n\n\n\n", "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.", "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", "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "NURBS subdivision wrong.\nCurve>>segments>>Subdivide\n```\n for NURBS circle changes the shape to a rounded rectangle.\n```\nThis seems to be wrong for all NURBS.\n\nThe Bohm algorithm for dividing a single interval is (this is for a cubic NURBS)\n\n Q_i = P_i for i <= j-3\n Q_i = (1-a_i) P_i-1 + a_i P_i for j-2 <= i <= j\n Q_i+1 = P_i for j+1 <= i\n\n a_i=(t' - t_i)/(t_i+3 - t_i)\nThe interval being divided is between t_j and t_j+1, and is split at t'.\nQ_i are the new control points.\nP_i are the old control points.\n\nThis is taken from Computer Graphics: Principles and Practice\nby Foley, van Dam, Feiner and Hughes, page 509.\n\n\nThe Oslo algorithm for multiple divisions can be found in\n\"Discrete B-Splines and Subdivision Techniques in Computer-Aided Geometric Design and Computer Graphics\" by Cohen, E.T. Lyche and R. Riesenfeld\nCGIP 14(2), October 1980 87-111.\n\n\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Bevel issues with big/small meshes\nWindow 7 64bit GTX 680\n\nBroken: (2.70a )\nWorked: (2.69)\n\nWhen apply scale in big or small object bevel create artifacts\n\nwhit the default cube scale it at .0001 and after CTRl+A abd apply the scale enter in edit mode and try to bevel one edge, if you increase the number of step, the profile don't change and stay flat, with bigger scale it work better but flicker the flat/smooth profile while changin the dimension of the bevel\n\nthanks\n\nLoris\n", "Bevel on single edge amount can't go under 0.001m and mantain 0.5 profile\nMacOS X 10.6.8 - 2.8 GHz Quad-Core Intel Xeon - 6GB 1066Mz DDR3 - ATI Radeon HD 5870 1024Mb VRAM\nWindows 8.1 64 bits - i5-3320M - 8GB DDR3 - NVIDIA GeForce GT 635M 2048Mb\n\nBlender 2.70a\n\nThe same error occurred in these two systems. When you select an edge and apply bevel, with 2 or more segments and you can't go bellow 0,001 meter in the amount and mantain the profile at 0.5... The bevel is still visible but under 0,001 meter, but it goes flat.\n\nSet units to meter, i didn't try otherwise, create some mesh object, active edit mode, select one or more edges, apply bevel, set segments to 2 or more with the mouse wheel, set the profile to 0.5 and the amount to less than 0.001.\n\nI hope can figure out what's the problem and solve it because this feature is very important to reproduce real world precise machinary.\n\nThanks for the excelent 3D package and keep pushing! Best regards!" ]

[ "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", "--render-output command line argument and backslash\n## Commandline Rendering\n\nOperating system: Windows 11\nGraphics card: NVIDIA GTX 3060 Ti\n\n3.4.1\n\n\nIf the value for \"-o\" or \"--render-output\" ends with a backslash no rendering occur and Blender exits clean (0) with no error.\n\n### Example\n\nRender blender-file in current folder to subfolder with a space.\n\n>blender -b myfile.blend -o \"my folder\\\\\" -F PNG -f 1\n\n```\nBlender 3.4.1 (hash 55485cb379f7 built 2022-12-20 01:51:19)\nRead prefs: C:\\Users\\***\\AppData\\Roaming\\Blender Foundation\\Blender\\3.4\\config\\userpref.blend\nRead blend: c:\\blender\\myfile.blend\n\nBlender quit\n```\n\n**Observed behavior**\nNo render. No errors. No information of what went wrong.\n\n**Expected behavior**\nBlender should render to generic file \"0001.png\" in folder \"c:\\blender\\my folder\".\nBlender should provide some information why nothing got rendered.\n\n\n", "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\n\n", "Cloth physics cache gets reset by changing object materials\nOperating system: Darwin-19.4.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.8.24\n\nBroken: version: 2.83 (sub 11)\nWorked: unknown\n\nWhen using a cloth physics simulation, if you add or remove a material from an object, the cloth system cache is reset (\"cache is outdated\"). I don't think the material affects the cloth physics in any way (as it seems you can change any parameter within the material without the cache resetting), and therefore this should probably not happen. Please correct me if I am wrong and the material does affect the physics somehow.\n\nIn the default scene, enable cloth physics for the cube. Let the playback run for a few frames, building up the cache. Add a material to the cube; now the cache gets reset.\n\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\n\n", "Split Asset and File Browser frontend, implement Grid View\nHaving the Asset Browser be a sub-editor of the File Browser turned out to cause a whole number of issues. These are not easy to fix in the existing code, which is hard to work with additionally. The Asset Browser shouldn't be based on the File Browser's file-list design, but on the asset system.\n\nIn context, this works towards this architecture: \nEssentially, this task covers the following:\n- Split the Asset and File Browser into separate editors\n- Introduce a new grid view system (similar to the new [tree-views ](Tree_Views)) providing general UI functionality and optimized display of big data-sets.\n- The grid view would support features like activating, selecting (including box select, walk select, etc.), drag & drop controllers, custom context menus, filtering, sorting, ...\n- Use and improve performance of custom previews/icons\nThe File Browser can be ported to the new [view ](Views) based design as well, some initial work is done for that already.\n\nWork on this is ongoing in the `asset-browser-grid-view` branch.\n\n----\n\n- [x] New Asset Browser space type\n- [x] Basic grid view\n- [x] Support reading and writing the editor\n- [x] Support active item\n- [ ] Selection\n - [x] Select all\n - [x] Mouse (incl ctrl)\n - [ ] Mouse range select (shift)\n - [ ] Walk select\n - [ ] Box select\n- [x] Add metadata sidebar\n- [ ] Asset import method toggle\n- [x] Fix too bright mouse hover highlight\n- [x] Add Editor pulldown menus back\n- [ ] Show fallback previews/icons for assets without preview\n- [ ] Asset dragging\n- [ ] Add filtering\n- [ ] Useful operators (period to jump to active, etc.)\n- [ ] Context menu\n- [ ] Catalog filtering per asset list user (per asset browser/view)\n- [ ] Preview size toggle\n- [ ] Update industry compatible keymap\n- Performance:\n - [x] Preview icon loading from OS thumbnail cache (731c1be92a, [D14144](D14144))\n - [ ] Initial preview icon loading (not yet in OS cache)\n - [ ] Prioritize icons that are currently in view, or don't generate icons that are not in view anymore (e.g. when just scrolling over assets)\n - [x] Avoid O(n^2) comparisons of grid-view items in `AbstractGridView::update_from_old()` (9ae2259db5)\n- [ ] Polish:\n - [x] Scrollbars (hide horizontal one for grid view)\n - [ ] Reduce drawing size of view-item tiles (leave more space between them)\n\nNice-to-have:\n- [x] Improved preview lazy-loading (UI level) -- (done I think? 16ab6111f75)\n- [ ] Show loading icon for previews while loading\n\nBugs:\n- [x] UI doesn't redraw/refresh(?) while loading library (878477f250)\n- [ ] Some previews don't load sometimes\n- [ ] Disabled hints missing in tooltips (catalog tree view, \"All\" library).\n\n----\n\nAddresses the following:\n- #89783 (Files don't appear in File Browser while Asset Browser loads assets)\n- #93726 (Fix preview flickering when using \"Adjust Last Operation\")\n- Blender becoming unresponsive (pretty much unusable) when loading big asset library (~3000 assets)\n- Blender becoming unresponsive for seconds when changing catalogs of a big asset library.", "Misuse of 'U.pixelsize' in code\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: -\n\n\nThe `U.pixelsize` is the user preference for line width in the UI. Go to \"Preference\" > \"Interfece\" > \"Line Width\".\nChanging the \"Line Width\" has an undesirable effect in some cases.\n\n- [ ] Zooming value with MMB-drag in Clip and Image editors\n- [ ] Dynamic-topology Detail Size\n- [ ] Width of tooltips block\n\nThere's an old list of places that need to be re-checked:\nD9604\n\n", "use-after-free crash after setting scene's render.engine inside custom render engine context\nOperating system: Ubuntu 20.04.2LTS\n\nBroken: 2.93.0 Beta, branch: master, commit date: 2021-05-19 10:14, hash: a294670bacb1, type: release\nAlso Broken: 0efb627bbd3ac3e53afb95591ae4e244bd1f8af4\n\nBlender crashes when setting some scene's render.engine property inside `__init__` or the `view_update` context of a custom render engine to a different one than the custom engine.\n\n[T88404_asan_report.txt](T88404_asan_report.txt)\n**Code to reproduce the error**\n```\nimport bpy\nimport bgl\n\nclass CustomRenderEngine(bpy.types.RenderEngine):\n bl_idname = \"CUSTOM\"\n bl_label = \"Custom\"\n bl_use_preview = True\n \n def __init__(self):\n return\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def __del__(self):\n pass\n\n def view_update(self, context, depsgraph):\n scene = bpy.data.scenes.new(\"foo\")\n scene.render.engine = \"CYCLES\"\n bpy.data.scenes.remove(scene)\n\n def view_draw(self, context, depsgraph):\n pass\n\ndef get_panels():\n exclude_panels = {\n 'VIEWLAYER_PT_filter',\n 'VIEWLAYER_PT_layer_passes',\n }\n\n panels = []\n for panel in bpy.types.Panel.__subclasses__():\n if hasattr(panel, 'COMPAT_ENGINES') and 'BLENDER_RENDER' in panel.COMPAT_ENGINES:\n if panel.__name__ not in exclude_panels:\n panels.append(panel)\n\n return panels\n\n\ndef register():\n bpy.utils.register_class(CustomRenderEngine)\n\n for panel in get_panels():\n panel.COMPAT_ENGINES.add('CUSTOM')\n\n\ndef unregister():\n bpy.utils.unregister_class(CustomRenderEngine)\n\n for panel in get_panels():\n if 'CUSTOM' in panel.COMPAT_ENGINES:\n panel.COMPAT_ENGINES.remove('CUSTOM')\n\nif __name__ == \"__main__\":\n register()\n```\n\n1) Copy code from above into a new script file inside of Blender\n2) Run the script\n3) Select \"Custom\" as Render Engine inside Render Properties\n4) Select \"Material Preview\" as display method in the viewport.\n\n[crash.blend](crash.blend)\n\nCrash log:\n```\n# Blender 2.93.0, Commit date: 2021-05-19 10:14, Hash a294670bacb1\nEngine 'CUSTOM' not available for scene 'Scene' (an add-on may need to be installed or enabled) # Error\nbpy.ops.text.run_script() # Operator\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0xa63c950]\n./blender() [0xf6082a]\n/lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f7ce17be210]\n./blender(GPU_framebuffer_blit+0x2f) [0x8664faf]\n./blender() [0x1485fc3]\n./blender() [0x14597fe]\n./blender(DRW_draw_render_loop_ex+0x242) [0x1459a72]\n./blender(view3d_main_region_draw+0x8f) [0x1d3570f]\n./blender(ED_region_do_draw+0x851) [0x189c771]\n./blender(wm_draw_update+0x52e) [0x130cc9e]\n./blender(WM_main+0x30) [0x130aa20]\n./blender(main+0x319) [0xe881c9]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f7ce179f0b3]\n./blender() [0xf5d1bc]\n\n# Python backtrace\n```", "Assign Shortcut Missing when Right Clicking Undo History.\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.1.2\nWorked: Blender 3.0 Unsure of exact version I had installed but I was not on 3.1.\nChanged in 0e1bb232e6\n\nUnable to assign shortcut to Undo History using Right Click Menu. \n\nRight Click Menu only shows \"Assign to Quick Favorites\"\n\nUsing default startup file, Edit > Right Click Undo History \n\n\nI recently had my OS SSD fail and had to reinstall Windows as well as all my applications fresh. Going through my setup of a new install of Blender 3.1.2 I wanted to reassign my previous shortcut for the Undo History Menu (Ctrl + Alt + Z) but was unable to view the Assign Shortcut option when right clicking. \n\n\n\nUndo History was also missing from the \"Blender\" Keymap when searching. \n\n\n\nTo resolve this, I switched to the Blender 2.7X Keymap which did have the Undo History shortcut, copied the shortcut \"ed.undo_history\" and assigned that manually in the default \"Blender\" Keymap. \n\n\n\n", "Can't uninstall completely and clean\nwindows 7 SP1 64 bit\n\nBroken: 2.75a c27589e\n\nCan't uninstall completely when used \"Uninstall blender\" from Start menu, and need to manually delete\n\n\nthe old version (with .exe packed ) has an option that let's you select \"leave user setting\" or \"remove all things\" when you uninstall, but the new version (with .msi packed) no this option for uninstall, and will leave some files on your computer, by the way, it's have't choice for your install, e.g. create a desktop shortcut, use blender for .blend flies, and create start menu, all blender default at install, and I can't custom setting for this, although this no affect for our used, but i'm a little OCD :D\n\nsorry for my bad English :)\n", "Quick Favorites: add support for operator/prop enums (e.g. \"Set origin\")\nOperating system: Windows 10\nGraphics card: Nvidia GTX1080\n\nBroken: 2.80, 16fc62e15f0, blender2.8, 2018-12-12\nWorked: 3d92afca7eb\n\nThe Set origin menu is not possible to put into quic favourites.\n\n3dView -> Object menu -> Right click on \"Set origin...\" -> empty menu.", "Breaking UI API changes for 4.0\n- [ ] Remove grid display for UI lists - Never worked well and is badly maintained. May have been added for an oudated asset UI design even?\n- [ ] Remove asset-view UI template - Should be replaced by the [asset shelf](102879).\n- [ ] Replace/deprecate UI lists? - Probably too much work, would require UI views to be exposed to Python. But can at least be converted to use UI views internally and benefit from its features.\n\n", "AssetBrowser: Add cleanup operator for asset index.\nUsers can rename/relocate/remove asset libraries. When they do created indexes would lead to files that will not be used anymore. Having a cleanup operation would help the user to free space on their storage device.\n\n## Approach\n\nUsers can have multiple blender versions installed with different asset libraries configured. The challenge here is that you when cleaning up automatically you can clean up indexes that are still used.\nThe approach to help the user would be to have an operation with an option to filter what indexes should actually be cleaned.\n\n### Requirements\n\n- User should be able to remove all indexes [OP1].\n- User should be able to only remove indexes that aren't used by the current open blender version [OP2].\n- User should be able to remove indexes of a specific asset library [OP3].\n\n## Design questions\n\nThere are 4 locations where such an operation makes sense:\n- **Blender Icon->System menu**: Current cleanup operation works on the opened blend file, very hidden.\n- **File -> Cleanup menu**: Currently only shows cleanup operations on the opened blend file. [OP1, OP2]\n- **Blender Preferences -> File Paths -> Asset Libraries**: The cleanup operations we want to introduce works on multiple asset libraries so it might be a good location. Concern is that it is hidden far away and is very specific. [OP1, OP2, OP3]\n- **Asset Browser Space** -> Only shows/works on a single asset library. Adding a cleanup operation here might be confusing, or only when it targets the current index. What is already done automatically, so might not make much sense. [OP3] might fit here.\n\n| **System Menu** | **Operation Fit OP1** | **Operation Fit OP2**| **Operation Fit OP3** |\n| -- | -- | -- | -- |\n| Blender Icon | Not very discoverable| Not very discoverable| Not very discoverable |\n| File menu | Ok fit | Ok fit | Nok fit as the current library could not be visible in the current screen |\n| Preferences | Ok fit| Ok fit| Ok/Nok fit, when user actually want to use it the operator is far away |\n| Asset Browser | Nok | Nok | Ok |\n\nLooking at the table above I would propose to add OP1, OP2 to the preferences and OP3 to the asset browser space inside the edit menu.\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.", "Brush Asset - Technical Core-level Design\n\nThis task is to design and keep track of how handling brushes will be done in the new Brush Asset system, from the Core module perspective mainly.\n\n## Changes in Brush Handling\n\n\nBrushes are now (in most cases) purely run-time data.\n* - [x] They do exist in the Main data-base.\n* - [x] They have a new ID tag to mark them as not writable (`LIB_TAG_RUNTIME`? Also related to #88555 (ID Management: Sanitize and clarify our ID tags) to some extent). b93025db59\n * `RUNTIME` IDs **do not** make linked data 'directly linked'.\n * `RUNTIME` IDs **are** written in global undo steps.\n* - [x] Brushes are **not** covered by Undo, they always remain in their state when applying undo/redo steps.\n* - [x] Brushes are **not** cleared when loading a new .blend file within a same Blender session. However:\n * They do get cleared when reloading startup or factory startup files.\n * Brushes in newly loaded .blend file are also kept, and replace potential existing ones in old blendfile in case of conflict. *This is to allow opening an asset library .blend, otherwise local brushes there would always be removed on opening.* \n * This implies a conditional mechanism to re-use brushes from old Main and copy them into new Main on file load (similar to other UI-related IDs like WindowManager e.g.).\n* - [x] A weak reference to the active brush must be stored in the toolsettings when writing a .blend file, such that it can be reloaded automatically on file opening when there is no active brushes in the current editing session.\n* - [ ] Several brushes with the same name (coming from different asset repositories/libraries) must be supported.\n * Displaying them in the asset browser/asset shelf should not be an issue? (*Check with @JulianEisel*).\n * Local runtime overrides however need a unique name. One idea could be to hide their `.xxx` number suffix in the UI?\n* - [x] It is assumed that only Brush data itself needs to be editable, its dependencies (textures, etc.) can remain linked and readonly.\n\nTypically, real local brush data should only exist in files part of an asset repository.\n\nBrushes are reset when closing and re-opening Blender, however they are kept across file opening within and editing session. So they are handled in a similar way to UI data (WindowManager etc. IDs) when 'load UI' is disabled, and moved from old to new Main on file loading.\n\n## Selecting a Brush\n\n\nWhen selecting the asset:\n* - [x] Brush is linked from asset .blend file (path given by asset system).\n* - [x] Existing local runtime liboverride of linked brush is searched for. If none is found, a new one is created.\n* - [x] That local runtime liboverride is assigned as active brush.\n\n## Undo & File Loading\n\nNo undo support should be needed for brush usage nor editing. Brushes can therefore be fully ignored by undo system, and existing brushes should just be re-used as-is.\nBrushes are also kept across file loading within a same Blender session, unless the (factory) startup file is loaded, or when loading to/from a brush asset library file.\n\nTechnically this has several complex implications, especially in `setup_app_data` part of the file loading process, mainly due to the fact that brushes can use other data-blocks. Currently:\n* Dependencies are not fully guaranteed to be handled by the new behavior:\n * [x] In **undo** case, other IDs are handled like any other data-block, i.e. changes to them are undone or redone (so editing an image or texture of a brush will be undoable). This is not ideal, but extremely hard to avoid in current situation.\n * [x] In **file loading** case, other dependencies can be brought over from the old bmain into the new one. This implies that e.g. is a locale texture is assigned to a runtime only liboverride of a brush while editing `file_a.blend`, and then user open `file_b.blend`, a copy of that locale texture will become part of `file_b.blend`.\n* [x] Opening another .blend file, in general:\n * All fully local, non-asset brushes are preserved *(necessary for old brushes compatibility)*.\n * All fully local, asset brushes are discarded.\n * All local overrides of asset brushes are preserved (besides special cases noted below).\n * All linked brushes are preserved (besides special cases noted below).\n* [x] Opening a file that is a library of current file (typical case: opening a Brush Asset library file):\n * Reset related brush assets to their status in the library (linked brushes and their local overrides are not preserved).\n * Have clear UI visibility of local assets having 'pending changes' in drafts.\n * Warn user that by opening the library file, they will lose their current non-drafted changes in these assets.\n * Requires detection of these cases.\n* [x] Opening a .blend file that is using as library the current blend file.\n * *Local asset brushes must be discarded in that case, this is covered by the general case described above*.\n\n\n## do_version\nFor modes moved to the new BrushAssets system, existing local brushes in older .blend files are often redundant and should be cleaned up.\n* [ ] Local non-asset brushes which names and values match the current default 'embedded' brushes should be removed.\n * *'Matching' here is used as 'essentially equal', in the sense that some properties (like e.g. size) should not be considered in the comparison.*\n * This implies keeping (or making) old brushes available for do_version code.\n* [ ] The others (non-matching) will be kept as local, non-asset brushes. Up to the user to clean them up or transform them into assets.\n\nLocal brushes that are not defined as assets will not be shown to the user in the UI (they will only be reachable through the Outliner editor, python API, etc.).\n\n## To Be Investigated\n\n\n### Toolslot\nThe 'toolslots' system is used at least by the 'smooth mode' toggle option of stroke code, which does a weird 'hot-swap' between current brush and a smooth brush, searched first in the relevant entry of the toolslot. This needs to be investigated further.\n\n> **Note**\n> One idea to fix the 'smooth mode' issue is that this toggle would not anymore search for an actual existing smooth brush, but would rather generate it's own private temp smooth brush, with default settings.\n" ]

[ "No way to remove Favorites folder that is no longer there\nOperating system: Windows 10, 64 bit\nGraphics card: 2 gpus: Nvidia GTX 1080 8gb, GTX 1070 8 gb\n\nBroken: blender-2.80-699193713fc0-win64\nWorked: (optional)\n\n\nHello wonderful Blender devs! It's probably not a bug but a papercut.\n\nIt seems that there is no way to remove Favorites folder that is no longer there in the File browser! Once folder is added to favorites and if it changed it’s path it just becomes greyed out and you can’t select it to delete it. \n\nHere’s a screenshot, I had a folder called Godot projects and then changed it’s name and path using Windows’ File browser. Now the folder is greyed out and I can’t select it. I thought I could delete it by pressing minus key and eventually getting to it, but I ended up just deleting all my favorites folders and was left with a greyed out folder not being able to do anything about it. IMO, I should be able to select it and have a choice to update the path or just delete it.\n\n\n\n\n - Add folder to favorites\n - Turn off Blender\n - Change the path to the folder in your file browser\n - See that folder is being greyed out and can’t be selected to be deleted so that you could update the path to that folder\n\nI know I can revert to factory defaults to fix that, but I don’t want to do it because of one invalid path! Setting up all my custom settings, hotkeys, theme, scripts is quite time consuming, so this is my paper-cut as of now. =((\n\n", "File browser cannot remove non-existent favorite directories \n**System Information** existent\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.75\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIf I delete or change the name of a directory that had been added to favorites in the file browser, I cannot remove it from favorites.\n\n1. Add a directory to favorites in blender.\n2. Delete or rename the directory.\n3. Now Blender still shows the greyed out favorite item, but you cannot remove or modify it." ]

[ "Attribute node (Type: View Layer) doesn't update in real time in Cycles\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09\n\nBroken: version: 3.4.0\nWorked:\n\nWhen using an Attribute node (type: View Layer) to get the position or angle of an object, the Attribute is not immediately updated in Cycles if Viewport Shading is Rendered.\nBut It works correctly in EEVEE and Material Preview.\n\n - Open attached file\n - Set Viewport Shading to Rendered\n # Move Empty and Rotate Sun\n\n[AttributeNodeBug.blend](AttributeNodeBug.blend)\n[221212_022211.mp4](221212_022211.mp4)\n\n", "Erase Alpha in vertex paint not working\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: latest 2.7 nightly build date 2019/06/27\n\nErase Alpha not showing in viewport.\n\ngo to vertex paint set mode to erase alpha and when painting nothing happens.\nalso found no ways to use the alpha data.\n\nVertex Alpha painting are needed for asset creation on some game engines like creation engine.\n", "Cycles viewport render doesn't resize if an animation is playing.\nOperating system: macOS-13.0-arm64-arm-64bit 64 Bits\nGraphics card: Apple `M1` Pro Apple 4.1 Metal - 83\n\nBroken version: 3.5.0 Alpha\nBroken version: 3.3.1\n\nIf a .blend file contains a animation, and the animation is playing, and you're in the Cycles rendered viewport mode, then the viewport resolution/size will not update as you adjust it's size.\n\n1. Create a scene that has a colour that differs from the standard background colour of the 3D viewport.\n2. Animate something in the scene (E.G. Animate the movement of an object)\n3. Change the render engine to Cycles (This issue only appears in Cycles for me.)\n4. Enter the rendered viewport mode so you're now seeing a Cycles viewport.\n5. Start playing the animation.\n6. While the animation is playing, start adjusting the size of the 3D viewport editor and notice how the Cycles rendered view isn't updating with the change in size. This is the issue. Once you stop playing the animation, it will update.\n\nHere is a video demonstrating the issue:\n\n[Cycles preview doesn't resize.mp4](Cycles_preview_doesn_t_resize.mp4)\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", "Viewport rendering bug : unable to make the render progress (infinite calculation)\nOperating system: Windows 11\nGraphics card: RTX 3090\n\n**3.0.1**\n\nI installed the latest studio drivers for the graphic card (28 january 2022 version), and then :\n\nI encounter a really strange bug when using the viewport rendering (with or without denoising) on some projects. This bug only happens on this new computer, not on my iMac.\n\nDescription : it's like the viewport rendering \"never stops\" and fails to progress. I see the object, but in the \"worst\" rendered version only. It doesn't progress at all and I can hear the graphic card working infinitely, trying to calculate it.\n\nThe bug is present both using CUDA and Optix. Notice that normal rendering works really fine.\n\nUPDATE : The bug is also present with an old version of the studio drivers.\n\nBlend file : [realistic-atom-1.blend](realistic-atom-1.blend)\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", "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", "Regression: 3.0.0: The curve is not hidden in the Viewport if there is a Bevel value\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: 3.0.0 `d046a1f2fa `\nWorked: 3.0.0 `1275ce61b1`\n\nHiding the curve display in the viewport as an object does not work\n\nIf you add a curve to the scene and try to hide its display and the ability to select in View Object Types, then hiding works.\nIf you add a profile for a curve or Bevel, then hiding does not work. In this form, the curve is hidden only when it is done as a hide mesh.\nPerhaps this is the correct behavior.\n\n[2022-12-28 16-39-53.mp4](2022-12-28_16-39-53.mp4)\n", "Blender 3.5: Cursor warping usable on windows remote desktop (RDP)\nOperating system: Windows 10 21H1 19043.2130\nGraphics card: GTX1650 4GB\n\nBroken: 3.5.0 Alpha, hash: 508fd044b44a\nWorked: 3.4.1, hash: ef9ca44dee7f\n\nI'm using Blender through Windows Remote Desktop (RDP) for quite a long time.\nNow in the new alpha 3.5 the Blender UI acts weird and non controllable anymore when using mouse middle click to pan viewport or left clicking into number fields to drag values up or down.\n\nAt this point for me Version 3.5 alpha is not usable anymore through an RDP connection - which is quite important for me! - while at least in Blender Version 3.4.1 everything worked fine!\n\n- Open blender from a Windows computer on another Windows computer via remote session\n- use {key MMB} to pan viewport or {key LMB} into number fields to drag values up or down.\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", "Viewport display broken for fire- solid and rendered mode (Cycles & Eevee)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\n[Fire seems to get 'stuck' in the viewport (as in it does not disappear), it does however behave correctly when F12 rendered.\nThis happens in 2.83Alpha and 2.82Beta (both downloaded as of today, approx 16:00 Sydney time 15 Jan 2020)]\n\n[Bake the attached and observe.\nhere's what it looks like-\n[ViewportFire_2-82+2-83.mp4](ViewportFire_2-82_2-83.mp4)\n\nIt works Ok when F12 rendered as seen here-\n[Fire26Nov20190001-0050.mp4](Fire26Nov20190001-0050.mp4)\nI couldn't be bothered to render out the clip in Cycles but stills show the error is only in the viewport-\n\n\nHere's the .blend-\n[Fire2.83A.blend](Fire2.83A.blend)\n\nThis works properly in the 26November2019 build, here's what that looks like-\n{[F8279386](ViewportFireMantaflow_26-11-19Build.mp4)}]\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", "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.", "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", "Cycles: UV render pass corrupted in viewport\nOperating system: Windows-10-10.0.18363-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9664\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.93 LTS\n\nWhen switching the render passfrom normal to UV the UVs are not displayed correctly.\n\n\nDownload bmw demo file.\nin viewport switch to render mode\nEnable the normal render pass. After that enable the uv render pass.\n\n{[F11785393](uv_render_pass.png) width=100%}\n\n`Film::update_passes` sets `shader->need_update_uvs`. The problem is that in 3.0 this is called as part of scene update after all syncing, instead of immediately after updating the render passes. That means this information is not available when we sync the geometry.\n\nNote: you can get the proper UVs back if you click on the UVMap in the Property Editor `UV Maps` panel" ]

[ "Camera Viewport Display Sensor doesn't show\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Vega 3 Graphics ATI Technologies Inc. 4.5.13596 Core Profile Context 20.10.28 27.20.1028.1\n\nBroken:\n - 2.92.0 Alpha\n - 2.91.0 \nWorked:\n - 2.83.9\n\nThe camera sensor size is not display in camera view.\n\n- Switch to camera view (Numpad 0)\n- In the camera's *Object Data Properties > Viewport Display* enable *Sensor*\n\n" ]

[ "Playback locks to frame with Sync-to-Audo, when changing Sound Settings\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 466.11\n\nBroken: version: 3.0.0 Alpha\n\nWhen playing the animation, while using Sync to audio, changing the Sound Settings will lock the playback. \nThe UI will show the fps etc but will not move beyond one frame.\n\n- Start Blender, set playback sync to Sync to Audio.\n- Press play.\n- Change anything in the Sound Settings of the User Preferences. \n- The UI will appear to as though animation is playing but the frame won't change: fps would be visible. (Inserting keyframes shows that scene doesn't actually change.)\n- If you move the timeline frame manually, when you stop it will only move forward one frame.\n\n[T88679_m.blend](T88679_m.blend)\n|Device|If fps shows with frame paused|\n| -- | -- |\n|CoreAudio|No, frame is set to 0, fps disappears, playback stops|\n|SDL on mac| yes |\n|SDL on windows| no|\n|OpenAL| yes|\n|OpenAl built-in input|yes|\n|SDL|yes|\n|pulseaudio|?|\n|WASAPI|?|\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", "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", "2x RTX 3090 Bugg\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84 x2\n\nBroken: version: 3.0.0\n\n[PHello so u just got my secound rtx 3090 card its and msi geforce, got the gigabyte rtx 3090 before so now i have 2 cards. When rendering with optix denoising in the viewport i get a light bleed even if i have no lights on. \n\nWhen i open a file from 2.92 and open it in 3.0 and hit viewport render and only have one card active it works fine, if i activate both cards it crashes everytime. ]\n\n[When rendering with optix denoising in the viewport i get a light bleed even if i have no lights on. \n\nWhen i open a file (kate) from 2.92 and open it in 3.0 and hit viewport render and only have one card active it works fine, if i activate both cards it crashes everytime. using optix denoiser ]\n\n\n[Kate.blend](Kate.blend)\n\n", "Fill material act weird when two layers masks each other and one of them has Fill Holdout material \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.1.0\nfill material act weird when two layers masks each other and one of them use holdout material and inverting mask.\nalso that happen when we use stroke material as holdout or both stroke and material holdout\n see video \n[0001-1466.mp4](0001-1466.mp4)\n", "Add Image/Sequence to video editing Squencer: number of images are truncated\nOperating system: Win10\nGraphics card: GeForce GTX 1050Ti\n\n**Blender Version** \nbroken: 2.8 RC3\nworked: 2.8 build from ca 1 month ago\n\nWhen you add images by drag 'n drop in de video sequencer, the number of images in the resulting strip is truncated aaround 27. \n\n(1) Open Blender\n(2) from the splash-screen choose: video editing\n(3) Open a windows explorer and select ca 100 jpg files;\n(4) use drag n drop to drop the files in the sequencer;\n\nYou then have a strip of just 27 frames where the selected number of files is expected. This used to work in the beta's", "UI: Sequencer/Preview jumps to cover entire preview area\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\n\n- In the Sequencer Preview, select Sequencer/Preview.\n- Adjust regions so both Preview and Sequencer are visible.\n- Adjust the height of the area.\n- Notice that when the area height meets the region height, the Sequencer region jumps to fill the entire area.\nExpected behaviour: that the sequencer region doesn't jump to cover the entire area, but is scaled with the change of the area height. Or in other words that the sequencer region height is scaled to the area height, instead of being fixed. \n{[F10144522](sequencer-preview-jump.gif),size=full}\n\nAn additional annoyance is when changing the area height:\n{[F10144525](sequencer-preview-jump2.gif),size=full}\n", "Blender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\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 535.98\n\nBroken: version: 3.6.0\nWorked: I dunno\n\nBlender crashed when increasing Strand Steps in the Viewport Display on the Particle tab\n\n<video src=\"attachment\" title=\"Crash when particle edit.mp4\" controls></video>\n\n1, Open the attached Blender file\n2, Rekey it to have a higher keypoints\n3, Increase the Strand Steps in the Viewport Display on the Particle tab\n\n", "Incorrect Areas affected by Timeline Playback settings\nVersion: 2.80 rc2 (Linux 64)\n\n[Timeline_bug.blend](Timeline_bug.blend)\n\nTo reproduce:\n\n - Open the example file (enable \"Load UI\" too)\n - With the mouse cursor in the 3d view, play the animation using Shift + Space (or Alt + A, whatever your keymap is)\n - Ignore the 3d view. Notice which animation editors show a moving playhead.\n - Inspect the playback settings in the timeline editor.\n - Disable \"All 3d Viewports\" and repeat step 2.\n - Now Enable \"Active Editor Only\" and repeat step 2.\n\nWith certain settings, the Dope Sheet and Timeline show playback even when the Graph Editor and NLA do not. It's as if these windows think they are 3d viewports!", "OSL on the GPU displays all black for Voronoi Distance > Bump Height\nSystem:\nWindows 11\nRTX3090Ti gpu\n\nBump output is pitch black when using Voronoi (Distance) output into Bump Height. Colorramp in between does not fix it. Noise output into Bump Height works fine.\n(Blender 3.5 in cycles)\n\nedit: more useful info + screenshot + isolated blend file\n\nRunning OSL on the CPU works fine, only the new GPU support seems affected.", "Mantaflow - Flickering Square pattern of the particles\nOperating system: Windows 10\nGraphics card: Quadro RTX 4000\nCPU: Ryzen Threadripper 2950x\nRAM: 64GB\n\nBroken: (2.90.0 // 2.83.5)\n\n\nI got the Problem both in the 2.83 LTS & 2.9 Version:\nIf i bake the fluid simulation in Mantaflow the particles of Bubble & Foam result in flickering squares: In one frame the particles are present and in the next frame they are abscent (in a square pattern). If I render an animation sequence out of this the video is flickering. I added the .blend-File for the used Settings and also two screenshots to demonstrate the square Pattern. Furthermore a rendered animation of another scene of mine shows the flickering result when rendered. \n\n\n[Mantaflow Flickering.avi](Mantaflow_Flickering.avi)\n\n[2020_09_19 - Fluid Test.blend](2020_09_19_-_Fluid_Test.blend)\n\n\n\n\n\nJust bake the attached .blend File (You need to change the saving location)", "VSE: Sound strips without valid source shrink to 0 length on project frame rate selection\nOperating system: Linux-5.4.0-81-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\nA sound strip without a valid data source will shrink to 0 length as soon as the project frame rate selection is touched (i.e. changed, or even current frame rate re-selected).\n\n[sound-strip-without-valid-source-shrinks-to-zero-length-on-project-frame-rate-selection.blend](sound-strip-without-valid-source-shrinks-to-zero-length-on-project-frame-rate-selection.blend)\n- Add sound strip\n- Remove source file on disk or change source file name in strip settings to an invalid file name\n- Select any value in project frame rate drop-down\n- Sound strip will \"disappear\" to 0 length", "Regression: Passepartout Flickers when using Solid Viewport Shading and Background > Viewport\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 2.93, 3.5\nWorked: 2.83\n\nThe Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport\n\n1. Create a 2D Animation workspace\n2. Zoom out to see the Passepartout\n3. Switch to Solid Viewport Shading and set the Background to Viewport\n\nIn this screencast, the Passepartout flickers with every Viewport interaction when using Solid Viewport Shading and the Background set to Viewport. In the video, it stops flickers when switching to World, however it is doing now. It does stop when using Material Preview Shading.\n\n[Passepartout.mp4](Passepartout.mp4)\n", "(Video editing) Different audio/video lenght after import strip\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 2.92.0\n\nAs shown in these images, the same media file (with audio and video) shows different lengths between audio and video in VSE:\n\n\n\n\n\n\n-\n\n", "Sequencer Preview : area_join() doesn't join well\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nI join two Sequencer preview areas with a script and both stay, but one is like broken. If I resize the view, it goes back as expected : the residual broken view disappears.\n\n- Open the provided blend file\n- There are two Sequencer preview views\n- Run the script in the text editor\n- The display of one view changes a bit and you cannot resize it.\n- Resize the main view, the residual view disappears.\n- NB: You can run the script again to split views and re-run it to join them again. The bug remains the same.\n\n[BugSplitView.blend](BugSplitView.blend)" ]

[ "Video Sequencer glitch\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 22.8.2.220819\n\nBroken: version: 3.3.0\nWorked: 2.79\n\nI probably found a little glitch in the video sequencer, when the window is too small this appears G4BAgv5\n[Glitch.mp4](Glitch.mp4)\n\n- Resize the sequences area of the Video Sequence editor\n\n\n" ]

[ "Action editor key frames not displaying sometimes\nSometimes when working with multiply animations and switching through them in the action editor. The Keyframes stop displaying for certain action. \nWhen the Panel with the action editor View is removed and added again, the displaying is working again.\nThis bug was seen in Version 2.76 and daily Build from 10/30/2015.\n\nError:\n\nFixed after closing and opening action editor view\n\n\nMy Project without Mesh. Bug is seen in walk_back_cycle action.\n[animation_editor_error_project.blend](animation_editor_error_project.blend)\n\nThis bug is very annoying in my workflow.\n\nGreetings and thank you for your work!", "USDZ IO - Occlusion Texture gets stripped\nOperating system: Windows 11\nGraphics card: RTX 3090\n\nBroken: (3.60, 6daa3f6b8a9b)\nWorked: NA\n\n\nWhen importing a sample USDZ file it imports correctly but has no Occlusion applied on the shader. When exporting back out to USDZ the Occlusion map is not included inside the USDZ anymore. \n\nWhen checking the original file (extract the usdz via a 7zip) it does have the AO texture inside the directory.\n\n1. Download sample USDZ file from Apple: Rock.usdz\n2. Import USDZ into Blender\n3. Go to Shading Tab\n4. Export USDZ from Blender\n5. Extract USDZ file via 7zip to check for embedded textures\n6. The directory only contains color and normal maps\n\n", "Error in Message of Linked data is Missing\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6 beta\n\nThe message about the lost linked data mentions Proxies that have been removed since 3.0. Perhaps it should be replaced with \"Library Overrides\"? The error is not only in the pop-up window, but also in the Info editor\n\n\n\nOpen this file\n[bandit_anim_2.blend](attachment)\n\n", "Blender 3.5 - Python - Excluding Collections that have child collections is not consistant\nOperating system: Linux-5.4.0-131-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.141.03\n\nBroken: version: 3.5.0 Alpha\nBroken : 3.2.1\n\nWe have a custom render manager which enables / disables collections on demand.\nIf you have a collection, that gets excluded via script, then included. all child collections get excluded and not re-included\n\n1. Open Attached blend file \n2. Toggle Collection on and off and Collection 2 on and off\n3. Notice how when Collection is toggled, Collection 2's exclusion is remembered, whether it is excluded or not\n4. Make sure Collection 2 is not excluded, and Collection 1 is excluded.\n5. Run Example script\n6. Notice how Collection 2 is now excluded\n\nThe expected behaviour, is that Collection 2 should remember what its previous state was, whether it was excluded or not. This is causing issues at render time when we are toggling collections on / off and objects are not rendering because of it.\n\n[bug.blend](bug.blend)\n\n", "Cycles: path guiding\n**Status**\n\nRequired for Blender 3.4\n\n- [x] Release notes\n- [x] Manual documentation\n- [x] Update to latest OpenPGL release\n- [x] Investigate volume direct light correctness, see TODO in `shade_volume.h`\n- [ ] Tests\n - [ ] Enable once deterministic sampling is added\n - [ ] More complete regression .blends\n\nOther\n\n- [ ] Closure support\n - [x] Diffuse BSDF\n - [ ] Translucent BSDF\n - [x] Specular BSDF\n - [ ] BSSRDF\n - [x] Volume Phases\n- [ ] Performance\n - [ ] Reduce deterministic training overhead?\n - [ ] Learn guiding vs. BSDF sampling probability?\n- [ ] MNEE compatibility\n- [ ] GPU support\n\n**Background**\n\nFor more efficient rendering of difficult light setups, including caustics to some extent.\nindex.htm\n\nBased on integrating Intel Open Path Guiding Library:\nopenpgl", "Particles not visible in render\nOperating system: Windows 10 Home 21H1 v. 19043.1466\nGraphics card: PowerColor RX 6600 XT OC\nCPU: AMD Ryzen 7 2700 Pro\n\nBroken: version: 3.0.0 LTS\nWorked: 2.93\n\n**Short description of the error**\nWhile rendering Spring demo with Blender 3.0, the grass is missing for some reason, only flowers is left\n\n**Exact steps to reproduce:**\n\n1. Download and run Blender 3.0 LTS: download/\n2. Download and open Spring demo (Blender 2.8): 5d2607ee6b3001d49bab798a\n3. Render as-is (this impacts both CPU and GPU rendering)\n\nPossibly this can be fixed by manipulating the original file's node system, I just want to know if this is a bug or just some hair/particle systems are no longer supported.\n\n", "Cycles X: Camera-visible lamps are not affected by holdout\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\nBlender 3.0 adds a feature where camera ray visibility can be enabled on lamps, making them directly visible. However, if this option is enabled simultaneously with the holdout option, the lamp will remain visible. Holdout should override camera visibility, as holdout can be changed per-view layer. With the current behavior, a directly-visible lamp will appear again on holdout layers, copying it's direct brightness for every layer it appears as a holdout in.\n\nSee attached .blend file, which contains a point lamp with holdout and camera visibility both enabled. Note that the lamp remains visible. In fact, the holdout option seems to have no affect at all.\n\n[holdout_lamp_bug.blend](holdout_lamp_bug.blend)\n\n", "Cycles shadow catcher improvements\n- [x] Indirect light support\n- [x] Option to include/exclude lights\n- [x] Dedicated shadow catcher pass\n- [ ] Dedicated compositor node for easier setup\n- [ ] Separate shadow and reflection passes\n- [ ] Shadow catcher behind sharp reflection and refraction?\n- [ ] Optimization to share more shader evaluation and sampling until path diverges?\n\n[devtalk thread ](691) with user feedback\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", "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", "GPencil: Layers used as mask and with viewlayer filter applied are rendered in all passes. \nOperating system: Linux-5.4.43-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: 2.90.0 Alpha\n\n\nLayers, used by other layers as masks, are always rendered when they have a viewlayer filter applied in all render passes.\nI feel a layer used as a mask for other layers and with viewlayer filtering it should work as a mask even when it is not rendered in a pass.\nI don't know if this is intentional, a time limitation, or a complex implementation.\nAssess whether this squares as a bug or feature recuest. Thank you very much for your wonderful work.\n\n- Download the blend file.\n- Note that the layer called \"masc\" is used as a mask for the other two and all layers are filtered in viewlayer filter.\n- Render and note that the mask appears in both passes.\n[GP bugreport viewlayerfilter and layers mask.blend](GP_bugreport_viewlayerfilter_and_layers_mask.blend)\n", "VSE: Transform settings doesn't get copied across scenes\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\nTransform settings doesn't get copied across scenes\n\nCopy a strip, which doesn't match the render resolution, across scenes:\n{[F10121941](copy_missing_transform.gif),size=full}\n\n", "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", "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)", "GPencil: Fill tool Ignore Transparent strokes setting broken\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 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n" ]

[ "Shadow Pass removed from Blender 3.5 (needs mention in the release notes)\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\nWorked: 3.41\n\nThe boolean toggle for shadow passes in Blender 3.5 Cycles is missing. I'm not sure if this is intended for this version, there is no mention of it anywhere I can see. \n\nBased on deafult startup.\n1. Open Blender\n2. Switch to Cycles\n3. Go to View Layer properties and check the Lighting section \n4. Shadow pass is missing. \n\nDiscrepancy between 3.41 and 3.5 can be seen below.\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", "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", "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", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\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\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\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", "Blender sometimes crashes when loading a file with unregistered nodes\nOperating system: Windows 10 64 Bit\nGraphics card: Nvidia Geforce GTX 750 Ti\n\nBroken: 2.83.7 release\n\nSometimes when opening a file with unregistered custom nodes, Blender will crash with an `EXCEPTION_ACCESS_VIOLATION` error.\n\n**Stack trace from Visual Studio:**\n```\nblender.exe!node_free_node(bNodeTree * ntree, bNode * node) Zeile 2033\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (2033)\nblender.exe!ntree_free_data(ID * id) Zeile 227\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (227)\nblender.exe!BKE_libblock_free_datablock(ID * id, const int UNUSED_flag) Zeile 136\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\lib_id_delete.c (136)\nblender.exe!DEG::deg_free_copy_on_write_datablock(ID * id_cow) Zeile 1073\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1073)\nblender.exe!DEG::deg_update_copy_on_write_datablock(const DEG::Depsgraph * depsgraph, const DEG::IDNode * id_node) Zeile 952\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (952)\nblender.exe!DEG::deg_evaluate_copy_on_write(Depsgraph * graph, const DEG::IDNode * id_node) Zeile 1088\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1088)\nblender.exe!std::invoke<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, Depsgraph * && _Arg1, DEG::IDNode * & <_Args2_0>) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<std::_Unforced,0>::_Call<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & <_Vals_0>, Depsgraph * && <_Vals_1>, DEG::IDNode * & <_Vals_2>) Zeile 1658\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1658)\nblender.exe!std::_Call_binder<std::_Unforced,0,1,void (__cdecl*)(Depsgraph *,DEG::IDNode const *),std::tuple<std::_Ph<1>,DEG::IDNode *>,std::tuple<Depsgraph * &&>>(std::_Invoker_ret<std::_Unforced,0> __formal, std::integer_sequence<unsigned __int64,0,1> __formal, void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, std::tuple<std::_Ph<1>,DEG::IDNode *> & _Tpl, std::tuple<Depsgraph * &&> && _Ut) Zeile 1388\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1388)\nblender.exe!std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>::operator()<Depsgraph *>(Depsgraph * && <_Unbargs_0>) Zeile 1427\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1427)\nblender.exe!std::invoke<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & _Obj, Depsgraph * && _Arg1) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<void,1>::_Call<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & <_Vals_0>, Depsgraph * && <_Vals_1>) Zeile 1641\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1641)\nblender.exe!std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>,void,Depsgraph *>::_Do_call(Depsgraph * && <_Args_0>) Zeile 904\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (904)\nblender.exe!std::_Func_class<void,Depsgraph *>::operator()(Depsgraph * <_Args_0>) Zeile 952\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (952)\nblender.exe!DEG::`anonymous namespace'::evaluate_node(const DEG::`anonymous-namespace'::DepsgraphEvalState * state, DEG::OperationNode * operation_node) Zeile 117\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (117)\nblender.exe!DEG::`anonymous namespace'::deg_task_run_func(TaskPool * pool, void * taskdata, int thread_id) Zeile 129\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (129)\nblender.exe!BLI_task_pool_work_and_wait(TaskPool * pool) Zeile 939\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (939)\nblender.exe!BLI_task_pool_work_wait_and_reset(TaskPool * pool) Zeile 970\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (970)\nblender.exe!DEG::deg_evaluate_on_refresh(DEG::Depsgraph * graph) Zeile 403\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (403)\nblender.exe!DEG_evaluate_on_refresh(Main * bmain, Depsgraph * graph) Zeile 65\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc (65)\nblender.exe!scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain, bool only_if_tagged) Zeile 1329\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1329)\nblender.exe!BKE_scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain) Zeile 1367\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1367)\nblender.exe!wm_event_do_depsgraph(bContext * C, bool is_after_open_file) Zeile 360\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (360)\nblender.exe!wm_event_do_refresh_wm_and_depsgraph(bContext * C) Zeile 387\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (387)\nblender.exe!wm_event_do_notifiers(bContext * C) Zeile 552\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (552)\nblender.exe!WM_main(bContext * C) Zeile 456\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c (456)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Zeile 530\n\tunter C:\\blender-git\\blender\\source\\creator\\creator.c (530)\nblender.exe!invoke_main() Zeile 79\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (79)\nblender.exe!__scrt_common_main_seh() Zeile 288\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (288)\nblender.exe!__scrt_common_main() Zeile 331\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (331)\nblender.exe!mainCRTStartup() Zeile 17\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp (17)\nkernel32.dll!00007ffca1667bd4()\nntdll.dll!00007ffca1e0ce51()\n```\n\nThe exception in line 2033 of node.c says that there is an access violation when reading at position `0xFFFFFFFFFFFFFFFF`. `node->typeinfo` does exist (is not null), but `freefunc` (and actually most of the other attributes) point to `0xdddd...`. Because of that, I think that this bug might be caused by a similar issue as described in #72833.\n\nI'm not sure if a core dump helps you, it's quite large (1GB + another GB for the .pdb file) so if you need it I can look for a way to make it available to you. I'm not a C or C++ dev so I don't know what is helpful.\n\n**EDIT**: I think this crash is caused by opening files files with nodes that were registered while the file was originaly saved but not anymore.\n\nIt's a bit complicated because it doesn't happen all the time. The particular file(s) where I observed this issue use nodes from an addon (Armory3D) which supports per-project custom nodes which get registered via a `on_load_post()` handler (so there is a delay between opening the file and registering the nodes). I'm not entirely sure, but it seems like the crash occurs when the nodes are registered again. The crash even occurs when unregistering the nodes before saving the file.\n\nBecause of that complicated setup (addon required + project setup + custom node package) I will go without an example file. If you aren't able to find the cause without one, please tell me so that I can prepare a minimal project setup for you.\n\nThank you very much!\n\n*Original issue*: 1890", "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 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) ", "Unable to undo subdivision with Multiresolution modifier\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86\n\nBroken: version: 2.93.6\n\n**Bug**: If i subdivide with Multiresolution modifier after a sculpt action it doesn't undo subdivision but it needs to undo the sculpt action to undo that subdivision done with Multisolution modifier.\n**Note**: If no sculpt action is done before subdivision with Multiresolution modifier, the undo for subdivision just works (No need to undo the action done just before the subdivision to get the result back).\n**Mode** : Sculpt\n\n**Steps**:\n1. File> New> Sculpting. \n2. Add Multiresolution modifier.\n3. Sculpt with Grab brush.\n4. Subdivide once at Multiresolution modifier.\n5. Undo (Doesn't work).\n\n**File**:[Multiresolution_subdivision_bug.blend](Multiresolution_subdivision_bug.blend)\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", "Reliable GPU hang on common Intel cards (Linux)\nOperating system: Linux Fedora 32\nGraphics card: UHD Graphics 620 (rev 07) Intel\n\nBroken: 2.80.x, 2.90.0-x\n\n\n\nBlender crashes the computer, freezing, dmesg command shows a GPU Hang error.\n\n\nOnly with Intel GPU (Intel Corporation UHD Graphics 620 (rev 07) here)\n\nOpen the given blend file [F8892221](gpuhangtest.blend) (Thanks @HDMaster84 ) and activate lookdev or render view - the graphic server hangs.\n\nI followed the dmesg output that says to create an issue on freedesktop gitlab: 2422 (you can see my dmesg and gpu error) - anyway, thos problem only happens with Blender.\n\nThe problem started from 2.80 if I'm not wrong, not with others earlier versions.\n\n", "bpy.ops.fluid.free_all() can cause a crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.77\n\nBroken: version: 2.93.0\n\npython script to free and re-bake smoke can cause a crash in 2.9x\n\nThe description of this bug is clearly documented along with the example blend file in [this blender stackexchange question ](python-script-to-bake-two-fluid-domains-aborting-cmd-line).\nIf I comment out the lines that contain:\n\n```\nbpy.ops.fluid.free_all()\n```\n\nin the following script, and instead manually free the bakes, all is fine. Otherwise the application crashes with console messages like:\n\n```\nUnable to remove directory\nor\nUnable to delete file\n```\neven if run from cmd line as Administrator\n\n\n```\nimport bpy\n\ndomain = bpy.data.objects['Smoke Domain Purple']\ndomain.select_set(True)\nprint(\"free Purple\")\nbpy.ops.fluid.free_all()\nprint(\"bake Purple\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\ndomain = bpy.data.objects['Smoke Domain Blue']\ndomain.select_set(True)\nprint(\"free Blue\")\nbpy.ops.fluid.free_all()\nprint(\"bake Blue\")\nbpy.ops.fluid.bake_data()\ndomain.select_set(False)\n```\n\n[dual smoke.blend](dual_smoke.blend)\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 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 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" ]

[ "Blender seems to crash in combination with the new undo system and dynatopo in sculpt mode\nWindows 10 / Nvidia GTX 970\n\nBroken: 2.79-c84b8d4\nWorked: 2.79b\n\nIf I'm in sculpt mode and use dynatopo and use Scrape/Peaks for example and undo it and sculpt again blender crashed everytime. I tested it also on a other PC(from a friend...Windows 7) on a blender build without any modfikations and it happen everytime.\n\n1. Start Blender\n2. Switch to sculpt mode and activate dynatopo\n3. Switch in the setting in dynatopo from relative detail du brush detail\n4. Switch to the Scrape/Peaks brush and flat the edge from the cube with it\n5. Undo the steps and try again to flatten something\n\nIt should crash than.\n\nHere also a Video do demonstrate it twice:\nl7tQMuqjCXY\n\n\nCheers!\n" ]

[ "Crashes when trying to mirror particles\nOperating system: Windows 11\nGraphics card: Nvidia RTX 2060\n\nBroken: 3.6.1\n\nWhen I try to mirror hair particles Blender crashes. I've tried it multiple times and it happens every single time. Ive tried applying the mirror modifier I have on the character but it still crashes.\n\nI have a retopologized character. I make a particle system for eyebrows. I try to mirror the eyebrows by selecting all the particles, going to particles and selecting mirror and blender crashes.\n\n", "Geometry Nodes: Crashes when the curve resampling node length is 0\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 3.6.0\n\n\n\n\nThis is an irregular operation, but I hope it is not a crash but a warning.\nI don't know if this is a bug or a feature request. \nThere is also a possibility that if the length is close to zero, it will cause the computer to have 100% CPU.\n\n", "Sculpt undo bug, mixing sculpt brush and multi-res modifier changes.\nWith current master (also 2.83).\n\nThe following steps show and error when redoing sculpt mode undo, when mixing multi-res subdivisions.\n\n- Startup file\n- Add multi-res modifier.\n- Enter sculpt mode.\n- *Repeat this 3-5 times.*\n - Multi-res subdivide.\n - Brush Stroke.\n\n- Now undo until the very beginning.\n- Now redo until the very end.\n\nWhen redoing, there are glitches where the multi-res has tearing/artifacts.\n\nSee video: [sculpt_undo_bug.mp4](sculpt_undo_bug.mp4)", "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```", "Blender crashes right after loading up a blend file or when creasing a specific mesh on a slightly older version of said blend file\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.77\nCPU: Ryzen 7 3700X\nRAM: 16GB, roughly 7GB available when loading\n\nBroken: version: 3.2.0\n\nFollowing a sculpting course i'm currently trying to crease the claws of a model in the attched blend file.\nBlender keeps crashing without further notice when doing so. I managed to save in the specific state that causes the crash, but can also reproduce it by creasing the front-left hoof/claw-thing in the older state\n\nLoad up file, change to sculpt mode without hiding linked duplicates (feet/hooves)\n[dog!.blend](dog_.blend)\n\nOld:\nLoad up attached blend file -> Crash immediately after apparently successfully loading the scene\n[dog!.blend](dog_.blend)\nLoad up attached blend1 file, crease said claw region with Dyntopo active -> Crash soon after doing so\n[dog!.blend1](dog_.blend1)", "Merging vertices keeps vertex groups from one vertex, discards others\n[merge_vgroup_bug.webm](merge_vgroup_bug.webm)\nBroken: 2.80, d3870471edd7, 2019-02-12\n\nWhen merging vertices (either directly or using \"Remove Doubles\"), vertex groups are only inherited from one vertex and the others are discarded (effectively at random). Expected behavior is that all vertex groups assigned to the vertices to be merged will be inherited.\n\nDoing the same but with materials instead of vertex groups results in expected behavior (all materials assigned to the vertices to be merged are inherited), so I guess there's a case to be made for consistency.\n\n - Open the attached .blend file\n - Note that the vertex group \"top_group\" contains all top vertices and \"bottom_group\" contains all bottom vertices\n - Select all vertices\n - Remove Doubles\n # Note that the merged vertices only inherited vertex groups from either \"top_group\" or \"bottom_group\", instead of both\n[merge_vgroup_bug.blend](merge_vgroup_bug.blend)", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "Region overlap crashes when interacting with action zones\nEnable region overlap user preference.\n\nIn the default 3D viewport, press NKey, then drag on the corner widget. -> Blender crashes.\n\nAttached asan output: [region_overlap_azone.txt](region_overlap_azone.txt), [region_overlap_azone_2020_01_28_update.txt](region_overlap_azone_2020_01_28_update.txt) (found while investigating #46764).\n\nUpdated asan output\n\n\n----\n\nNote: Blender internals aren't well suited of handling regions being manipulated like this while the rest of Blender is being used. We could either prevent interaction during the fade, or disable it since its not really needed.", "Bevel Bug\nblender-2.80-07765499abee-win64 \n\n**cylinder :**\non the cylinder with a lot of segments, bevel doesn't merge in one point. Create nice see n-gon(normal we must see the only verts in one point)\n\n\n**Cube :**\nThe middle loop has deformed when we bevel sharp corner for small mesh. On the large mesh, we cant see this deform .\n\n\n[Cylinder_Bevel_Bug.blend](Cylinder_Bevel_Bug.blend)\n\n[Cube_Bevel_Symmetry_Bug.blend](Cube_Bevel_Symmetry_Bug.blend)\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.", "Geometry nodes crash involving point translation and points to volume\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: AMD Radeon RX 5700 XT ATI Technologies Inc. 4.5.14830 Core Profile Context 21.4.1 27.20.21002.112\n\nBroken: version: 3.0.0 Alpha\nWorked: Unknown.\nCannot open reference file in stable (crashes immediately). \nMy oldest 3.0 from 2021-08-01 (`836aeebf7077`) also has the issue.\n\nBlender crashes in certain setups involving point translation and points to volume.\n\n- Open .blend file\n- Connect \"Crash\" node with Reroute\n\nUpon some more testing I found that there are more specific values or ranges that cause the problem, when using the power node one is around 2 to the power of 24.003.\nKnowing values that crash, the attribute fill node can be used:\n\n\n[attribute-fill.blend](attribute-fill.blend)\n[attribute-power.crash.txt](attribute-power.crash.txt)", "Regression: Crash with boolean modifier\nOperating system: Fedora Linux 36 (Workstation Edition)\nGraphics card: Nvidia Geforce RTX 3080\n\nBroken: 3.2.1, 3.3 alpha\nWorked: 3.1\n\nCrash with boolean modifier\n\n- Open .blend file\n- In boolean modifier tab -> select `dot cutter` for boolean operation\n[yin_yang-v1.blend](yin_yang-v1.blend)\noriginal file: [F13292564](yin_yang.blend)", "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", "Crash when duplicating and \"Use Clump Curve\" is turned on for hair particles\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 497.09\n\nBroken: version: 3.1.0 Beta\n\nA crash occurs when a curve guide force field is applied and \"Use Clump Curve\" is turned on. Doing this then duplicating the object crashes Blender.\n[blender_puASiznJH9.mp4](blender_puASiznJH9.mp4)\n\nFrom Default Start up\n1. Create Hair particle on cube\n2. Create curve, and add \"Curve Guide\" force field\n3. In Hair particle settings, turn on \"Children: Simple\" and \"Use Clump Curve\"\n4. Attempt to duplicate cube. It should crash here\n\nFrom attached:\nJust turn on \"Use Clump curve\" then duplicate. \n[haircrash.blend](haircrash.blend) \n\n\n\n\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." ]

[ "Blender 3.0 crashes when performing Mesh -> Clean Up -> Merge By Distance in Edit Mode\nOperating system: Windows 10\nGraphics card: Nvidia\n\nBroken: 3.00, 4c26bb02327f, master, 2021-08-09\nWorked: 3.00, 17243337d731, master, 2021-08-01\n\nBlender 3.0 crashes when performing Mesh -> Clean Up -> Merge By Distance in Edit Mode\nI also noticed that the edge of the mesh is not shown properly in the view port - Solid Mode\n\n1. Load the attached untitled2.blend\n2. Switch to Edit Mode\n3. Select all vertices\n4. Perform Mesh -> Clean Up -> Merge By Distance\n\nI also captured the crash file, attached as untitled2.crash.txt.\n\n[untitled2.blend](untitled2.blend)\n[untitled2.crash.txt](untitled2.crash.txt)" ]

[ "Render engine support for curves data-block\nSeveral features need to be supported in Cycles, workbench and EEVEE.\nMost of the relevant code is shared between EEVEE and workbench as part of the draw manager.\nInitially at least, NURBS curves can be supported by computing the weights for each evaluated\npoint on the CPU (see `blender::bke::curves::nurbs::BasisCache`), and just doing interpolation\nof attributes on the GPU.\n\nFor EEVEE/Viewport, supporting different curve types, segment counts, and cyclic values\ncould be done by batching curves with similar data. For example, all curves with segment\ncounts in between two powers of 2 could be batched together, with padding triangles added\nat the final point.\n\nCurves have a resolution attribute which makes the current \"subdivisions\" settings redundant.\nRender engines should support the resolution instead. Further changes to the evaluation\nresolution can be part of the standard \"Simplify\" options.\n\n- [ ] EEVEE/Viewport\n - [ ] Curve types\n - [x] Camull Rom\n - [ ] Bezier\n - [ ] Poly\n - [ ] NURBS \n - [ ] Cyclic\n - [ ] Radius Attribute Support\n - [x] Generic attribute rendering\n - [x] Curve domain generic attributes cd968a3273\n - [x] Point domain attributes cd968a3273\n - [ ] Curve segment count\n - [ ] Remove drawing pass that resamples curves\n - [ ] Support drawing arbitrary segment length curves\n - [ ] Tube/cylinder drawing\n - [ ] Resolution attribute support\n- [ ] Cycles\n - [ ] Curve types\n - [x] Camull Rom\n - [ ] Bezier\n - [ ] Poly\n - [ ] NURBS \n - [ ] Cyclic\n - [x] Radius attribute Support\n - [x] Generic attribute rendering\n - [x] Curve domain generic attributes\n - [x] Point domain attributes\n - [ ] Resolution attribute support\n- [ ] Move curve render settings from scene to object data\n- [ ] Add curve resolution limit to render \"simplify\" settings", "Curve Pen Error\nOperating system: macOS-13.3.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Pro 1.2\n\nBroken: version: 4.0.0 Alpha\n\nNothing happened when I left click my mouse using Curve Pen in Edit Mode, but it is fine with blender on my windows laptop.\n\nI added a Bezier and I enter the edit mode, I deleted all the vertices and decided to draw a line using Curve Pen. However, it did not work.\n\n", "Switching Curve Shapekeys in Edit Mode go haywire if relative to one another\nOperating system:\nLinux\n\nBroken in 2.79 onwards\nWorked in 2.78\n\nPossibly caused by\n6f1493f68f\n5e1d4714fe\n\nShapekeys on curves do not reset properly when switching between them in edit mode, and one shapekey is relative to another.\n\nSelect the circle and enter edit mode. Repeatedly switch between shapekeys 'Key 1' and 'Key 2' while staying in edit mode. 'Key 2' will change over time from just this.\n[bug_report_shapekeys_curve.blend](bug_report_shapekeys_curve.blend)\n\n**How to reproduce the scene**\nCreate a Curve object. Add Basis, Key 1, Key 2 shapekeys. Set 'Key 2' relative to 'Key 1'. Select 'Key 1' and translate/scale it. ", "Split Draw curve tool in two distinct tools [properties of one mode dont make sense for other mode]\nOperating system: Win10 x64\nGraphics card: GTX 1080Ti\n\nBroken: 2.82 - 2.90\n\nDraw Curve F9 \"Error\" slider doesn't do anything if curve is set to Poly\nIn fact, none of the provided settings work\n\n\nMake a new curve\nEdit mode\nUse toolbar draw curve (Toolbar - 9)\nSwitch it's type to Poly in N - Tool - Active tool\nDraw any curve\nF9 to adjust the Error slider - no effect\nOther settings also have no effect\nSwitch mode to Bezier and the slider works", "Geometry Nodes: Disabled from viewport object is not visible as instance\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: Current main.\nWorked: Never.\n\nDisabled from viewport object is not visible as instance.\n\nOpen attached file and check/uncheck `As Instance` option of _Object Info_ node.\n\n", "Joining curves overrides other materials\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.92.0\n\nJoining two or more curve objects together will result in the curves being assigned the active object's material rather than keeping the material assigned to their points. \n\nOpen the below file:\n[curve_material_bug.blend](curve_material_bug.blend)\nUse Ctrl+J to join the two curves together. \n\n", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Geometry Nodes: Mesh Boolean-Union node anamoly when boolean does not alter input mesh\nBroken: Current main.\nWorked: Never.\n\nI was trying to see if the simulation node group would get rid of internal geometry by incrementally using the **Mesh Boolean-Union** node in the **Simulation node group** but it **seems to delete some outer geometry instead.** \n\n## Without Simulation Nodes:\n| Operating as expected without Mesh Boolean Union node enabled (**creates internal geometry see red arrow**) | Operating as expected with Mesh Boolean Union node enabled (**no internal geometry**) |\n| -- | -- |\n|  |  |\n\n## With Simulation Nodes:\n\n| Description | Show |\n| -- | -- |\n| Operating as expected without Mesh Boolean Union node enabled (creates internal geometry see red arrow) |  |\n| Not Operating as expected with Mesh Boolean Union node enabled (no internal geometry but missing outer geometry) |  |\n| It should look something like this (no internal geometry but it should have \"external\" geometry also see red arrow |  |\n\nThe reason I'm trying to use the boolean mesh-union node within the simulation node group is because on some large meshes the boolean mesh-union node will fail or crash blender. \n105652#issuecomment-931240\n\nMy logic is if you have to finish an entire pie in one sitting (think of a pie eating contest) it's easier to cut them up into little pieces and eat them one at a time. **So I'm incrementally running the boolean mesh-union node on smaller pieces in the simulation node group to get rid of internal geometry therefore it's less likely to crash / fail like it does trying to do this all at once on larger meshes.**\n\nSee attached blend file: [cube repeat.blend](https://projects.blender.orgattachment)", "new boolean difference meshing issue with surfaces\nOperating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX 775M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: New Boolean code - version: 2.91.0\nWorked: Old Boolean code works\n\nnew boolean code does seem to have mesh intersection issues\nwhen dealing with a solid it works better\n\nintersect to surfaces \nadd a boolean difference modifier\n\nto make it work add a solidify modifier before the boolean modifier\n\n[Boolean Issue.blend.zip](Boolean_Issue.blend.zip)\n\n\n\n\n", "Set Material Index node does not work on some GN-created geometry\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 537.13\n\nBroken: version: 3.6.2\nWorked: Never.\n\nThe scene contains 3 objects:\n1. Mesh object with GN which creates Mesh Cube primitive\n2. Curve object with GN which creates Mesh Cube primitive\n3. Curve object with GN which creates geometry using Curve to Mesh node\n\nAll 3 objects have their Material linked to Object, not Object Data\n\nThe Set Material Index node works on 1. and 2. but does not work on 3.\n\n1. Open the attached blender file: [curvematerialbug.blend](attachment)\n2. Check Geometry Nodes setups on all 3 objects\nResult: Set Material Index Node does not work on Geometry generated by Curve to Mesh node.\nExpected: Set material Index Node works on any geometry.\n\n", "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", "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.", "GPU subdivision option with subdivision surface modifier collapses geometry (AMD GPU)\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\n\nSubdivision surface modifier with GPU Subdivision enabled produce geometry that appear to be lost\n\n1. Open default scene.\n2. Add subdivision surface modifier to an object.\n3. Make sure GPU Subdivision option is enabled.\n4. ~~Uncheck Use Limit Surface~~\n5. ~~Disable GPU Subdivision to see correct result.~~\nLast two steps are not necessary for recreation of the bug since this change- 118a219e9d\n[Subdiv GPU Use Limit Surface 2022-01-15 22-13-33.mp4](Subdiv_GPU_Use_Limit_Surface_2022-01-15_22-13-33.mp4)\n\n------\n\nNOTE: This bug seems to only occur on AMD cards on Windows.\n\n**Reproducible on:**\n\n| Operating System | GPU | Driver |\n| ----------------|-------------|---------|\n| Windows 10 | AMD Radeon HD 7800 Series | 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 |\n| Windows 10 | AMD Radeon (TM) RX 480 | 4.5.14760 Core Profile Context 20.45.37.01 27.20.14537.1001 |\n| Windows 10 | AMD Radeon(TM) 535 | 4.5.14831 Core Profile Context 21.5.2 27.20.21003.8013 |\n\n**Not reproducible on:**\n\n| Operating System | GPU | Driver Version |\n| -----------------|-------------|---------|\n| Linux Mint 20 | AMD Radeon RX550 | 4.5.14800 Core Profile Context 21.40 |\n| Linux Mint 20 | AMD Radeon RX550 | 4.6 (Core Profile) Mesa 21.3.0-devel |\n| Windows 10 | Intel(R) UHD Graphics 620 | |\n| Windows 10 | NVIDIA GeForce GTX 1050 | 472.39 |\n| Linux Mint 20 | NVIDIA RTX 2070 | 510.47.03 |\n| Linux | NVIDIA GeForce GTX 970M | 495.44\n|Windows-10-10.0.19043-SP0 64 Bits|Radeon (TM) RX 480 Graphics| 21.30.23.01, 22.2.3, 21.10.2 |\n", "Blender development todo list -- Import/Export\nNOTE: this is a direct dump of Import_Export (without cherrypicking the [still] valid items)\n\n## Blender files and Library linking\n\n- [ ] Mixing \"direct\" and \"indirect\" data not well supported #26706\n- [ ] Making local data which is still used in libraries, causes problems #44321\n\n## All Formats\n\nCurrently negative scales will flip faces for formats which don't store object transformations (obj, ply, stl ... etc). #35892\n\n## FBX\nSee [[Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX]].\n\n## Alembic\n- [ ] While Alembic exports particles as points and supports ParticleInstance modifiers it could also support particle duplication (dupliobjects etc.), see #54703\n", "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)" ]

[ "2.8 convert curve to mesh not working\nin the 2.8 version of blender the convert curve to mesh feature was working without an issue until today open a brand new project and create a path curve as well as a circle curve. select the path curve and in edit mode under geometry you'll find the bevel feature, apply curve circle as curve paths bevel. the curve path should resemble a cylinder without a bottom or top. back in object mode with the curve path selected right click for object context menu and select the convert to mesh option. For whatever reason this deletes the cylinder shape which never happened before today." ]

[ "Meshes are invisible if any objects are set to display 'In Front'\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) HD Graphics 6000 Intel Inc. 4.1 INTEL-12.10.14\n\nBroken: version: 2.83.0\nWorked: 2.82\n\nIf any objects are set to display as 'in front' in a project, all meshes will display only as faint outlines. In edit mode, meshes display similar to how they would if they were set to display as wireframe.\n\nAdd a new mesh, curve, or armature to the scene.\nObject properties -> Viewport display -> Enable 'In Front'\n\n", "Breaking change? Curve point tilt default orientation rotated by 90°\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.40\n\nBroken: version: 3.6.0\nWorked: 2.80\n\nThe default orientation (0°) of curve points has changed by 90°. If the curve is used for another object's curve modifier, the result between Blender 2.80 is different to newer versions (reproduced with 2.81...3.6). This is a change that I did not find listed in the release notes, so this is either a bug or by design. In any case, it's a breaking change.\n\n2.80 vs 3.6:\n\n\n\n1. Open the attached project in Blender 2.80 and in 3.6\n2. If you compare the two, you see that the normal orientation is different, consequently the result of the curve modifier affecting the mesh is different.\n\nAfter migrating a bigger project this causes several issues that would need to be fixed. Or Blender needs to be fixed.\nThis is an old issue, so I hope it's not a duplicate. Didn't find it.\nThank you.\n\n", "Mesh Optimization Project Progress\n### Committed\n\n- 2b640622ff\n- aa6f0f3d1f\n- deb71cef38\n- 5f749a03ca\n- 44d2479dc3\n- c2fa36999f\n- 496045fc30\n- e4c6da29b2\n- d8b8b4d7e2\n- bcefce33f2\n- 8a1860bd9a\n- 6bef255904\n- 174ed69c1b\n- b3f0dc2907\n- 513f566b40\n- 2d60c496a2\n- 27da305a40\n- 51568030e9\n- b5542c1ea4\n- 2d4ec90497\n- 4f9ef65dac\n- 04313f1bb5\n- 0f201049b4\n- f9c9e000ca\n- 1b4d5c7a35\n- 25c2875e0f (depending on 8839b4c32a)\n- 178086d581\n- 4ba06ad0a8\n- 39b2a7bb7e\n- 399b6ec76c\n\n### Differentials\n\n*Remove once committed.*\n\n- [D11294: DrawManager: Use threading for ibo.fdots_nor/hq](D11294)\n- [D11969: Depsgraph: Implement 'ID_RECALC_GEOMETRY_DEFORM' - Second solution](D11969)\n", "Bevel Bug\nblender-2.80-07765499abee-win64 \n\n**cylinder :**\non the cylinder with a lot of segments, bevel doesn't merge in one point. Create nice see n-gon(normal we must see the only verts in one point)\n\n\n**Cube :**\nThe middle loop has deformed when we bevel sharp corner for small mesh. On the large mesh, we cant see this deform .\n\n\n[Cylinder_Bevel_Bug.blend](Cylinder_Bevel_Bug.blend)\n\n[Cube_Bevel_Symmetry_Bug.blend](Cube_Bevel_Symmetry_Bug.blend)\n ", "Realize Instances lost Z rotation of Curve Line in certain situations\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 527.56\n\nBroken: version: 3.5.0 Beta\nWorked: N/A, 3.4.1 is also affected\n\n\nDiscovered in Blender.chat, Realize Instances doesn't appear to passthrough some type of curve rotation, for example Z rotation on a (0,0,0) to (0,0,1) curve line is lost during the process.\n\n\n- Download the attached blend file\n- Observe the curve line have random rotation per instances, but didn't result in rotated meshes\n- Disable Realize Instances and observe the instanced meshes are rotated as expected.\n- Enable Realize Instances, instead put an additional (0.001) rotation to X axis with the Combine XYZ node, observe this rotation are kept after Realize Instances.\n- I believe this behaviour should be consistent across all possible rotations.\n\n", "Mesh modeling performance regressions\nList of performance issues that we would like to fix or investigate for 2.80:\n\n* Transforming vertices in edit mode on high poly meshes is slow, due to overhead of depsgraph, mesh updates and and batch creation. Verify if there is anything unexpected happening here.\n* BMesh to mesh conversion was happening all the time at some point, is this still the case? See check_rendered_viewport_visible, it now always happens when a 3D viewport is visible, and could be quite problematic for edit mode performance.\n* Verify if custom data is only being preserved through modifier stack when needed (vertex colors, vertex groups, UVs)\n* Manipulate modal callback performance may be problematic: #55458\n", "Unselected nurbs vertices occlude selected ones\nBroken: 2.80 , 2.92\nWorked: 2.79\n\nCan't select Nurbs Sphere's top points with simple left click. It's only selectable with box selection.\n\n\nAdd nurbs sphere\nEdit mode\ntry to left click select the central top points.", "Apply Base (Multiresolution Modifier) on mesh with shape keys distorts the mesh\nBroken: version: 2.83 (sub 8)\nWorked: Doesn't Work even in Blender 2.79b official release. I haven't tested versions earlier than that.\n\nPressing Apply base using the multires modifier on a mesh with a stored Basis shape key causes artifacting and mesh corruption. Undo still works though.\n\n1. Delete Default Cube\n2. Add Plane mesh (Shift+A > Mesh > Plane)\n3. Add Basis Shape Key.\n4. Add Multiresolution modifier\n5. Subdivide multiple times. (Either Catmull-Clark or Simple type)\n6. (optional) Apply brush strokes in Sculpting mode. \n7. Press Apply Base in Modifier Properties.\n\nor\n\n1. Open attached file\n2. Press Apply Base in the Modifier Properties.\n\n[Shape key Multires Bug.blend](Shape_key_Multires_Bug.blend)\n\n", "New Curves data block\nThis is a follow up task based on discussions we had about #94193.\n\nCurrently, the curve object contains three distinct object types: curves, surfaces and text. We want to split those up into separate types, because there is no real reason for why they are combined into a single type. \nThis task focuses on introducing a new `Curves` data type which we will also need for hair and geometry nodes processing of curves.\n\nInitial steps:\n* - [x] Rename existing (experimental) `Hair` data block to `Curves`. In the ui it will be called `Hair Curves` for now to distinguish it from the old curve type. \n* - [x] Decide on and implement exact data structure used for curves.\n * Should be stored compactly in continuous arrays.\n * Should support arbitrary attributes on points and splines.\n * Ideally, the actual curve data structure is embedded into the `Curves` data block as a separate struct, so that the same struct could e.g. be used for grease pencil.\n* - [x] Refactor geometry nodes to use the `Curves` data block instead of `CurveEval`. (#95443)\n* - [x] Remove the runtime-only `CurveEval` data structure added for geometry nodes.\n* - [ ] Render geometry nodes curves as with the new type in Cycles and Eevee (#96455)\n* - [x] Curves sculpt mode that is mostly focused on hair use cases\n* - [ ] Curves edit mode, similar to existing curve edit mode\n\nFurther in the future:\n* - [ ] Add existing necessary features from the legacy curve object (features like shape keys may add complexity)\n* - [ ] Use versioning to convert legacy curve objects to the new curves object\n* - [ ] Add support for simulations through a generic simulation system involving geometry nodes\n* - [ ] Use versioning to convert hair particle systems to the new curves object\n\n", "Bezier Splines: Support different interpolation options\nBezier splines have the option of different interpolation methods between control points.\nTo achieve feature parity with the old curve implementation, these should be supported\nfor geometry nodes curves as well.\n\n{[F11838239](image.png) size=full}\n\nBecause of the generalized way attributes are handled in geometry nodes, supporting\na different interpolation method for the `tilt` and `radius` is much more complicated,\nand would require special cases in many areas of the code. I propose merging the two\noptions, so a spline can only have one interpolation method that applies to all attributes.\nIf one wants to interpolate tilt and radius differently, it would always be possible by changing\nthe interpolation mode procedurally and capturing the result as an anonymous attribute.\n\nMeeting notes: 21733", "Render engine support for curves data-block\nSeveral features need to be supported in Cycles, workbench and EEVEE.\nMost of the relevant code is shared between EEVEE and workbench as part of the draw manager.\nInitially at least, NURBS curves can be supported by computing the weights for each evaluated\npoint on the CPU (see `blender::bke::curves::nurbs::BasisCache`), and just doing interpolation\nof attributes on the GPU.\n\nFor EEVEE/Viewport, supporting different curve types, segment counts, and cyclic values\ncould be done by batching curves with similar data. For example, all curves with segment\ncounts in between two powers of 2 could be batched together, with padding triangles added\nat the final point.\n\nCurves have a resolution attribute which makes the current \"subdivisions\" settings redundant.\nRender engines should support the resolution instead. Further changes to the evaluation\nresolution can be part of the standard \"Simplify\" options.\n\n- [ ] EEVEE/Viewport\n - [ ] Curve types\n - [x] Camull Rom\n - [ ] Bezier\n - [ ] Poly\n - [ ] NURBS \n - [ ] Cyclic\n - [ ] Radius Attribute Support\n - [x] Generic attribute rendering\n - [x] Curve domain generic attributes cd968a3273\n - [x] Point domain attributes cd968a3273\n - [ ] Curve segment count\n - [ ] Remove drawing pass that resamples curves\n - [ ] Support drawing arbitrary segment length curves\n - [ ] Tube/cylinder drawing\n - [ ] Resolution attribute support\n- [ ] Cycles\n - [ ] Curve types\n - [x] Camull Rom\n - [ ] Bezier\n - [ ] Poly\n - [ ] NURBS \n - [ ] Cyclic\n - [x] Radius attribute Support\n - [x] Generic attribute rendering\n - [x] Curve domain generic attributes\n - [x] Point domain attributes\n - [ ] Resolution attribute support\n- [ ] Move curve render settings from scene to object data\n- [ ] Add curve resolution limit to render \"simplify\" settings", "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", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "Geometry Nodes/Curve to Mesh: BLI_ASSERT_UNIT_V3 failure for curve normals in `math_rotation.cc#rotate_direction_around_axis` when using Minimum Twist \nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\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: 3.5.0 Alpha, branch: master, commit date: 2022-12-14, hash: `rBUnknown`\nWorked:?\n\nWhile debugging and testing changes in `curve_to_mesh_convert.cc`, I came across a `BLI_ASSERT_UNIT_V3` failure for curve normals in `math_rotation.cc#rotate_direction_around_axis`.\n\n```\nRead blend: /tmp/rotate_direction_around_axis_normalize_bug.blend\nBLI_assert failed: source/blender/blenlib/intern/math_rotation.cc:16, rotate_direction_around_axis(), at '!(fabsf(_test_unit - 1.0f) >= 0.0002f) || !(fabsf(_test_unit) >= 0.0002f)'\nAbort trap: 6\n```\n\n`rotate_direction_around_axis` is called from `CurvesGeometry::evaluated_normals()... curves::poly::calculate_normals_minimum()` when using `Minimum Twist` (no assert failure in `Z-up` mode). No apparent negative effect when tested with non debug release. It seems to be due to the fact that `curve_geometry.cc#rotate_direction_around_axis()` does not normalize its returned value. It happens on a fairly big curve with ~200k control points that I created to test curve_to_mesh performance. \n\nFull backtrace:\n[rotate_direction_around_axis_normal_assertion_failure.txt](rotate_direction_around_axis_normal_assertion_failure.txt)\n\n**How to reproduce:**\nStart Blender (compiled in debug mode) from command line to see standard output, open the test file and switch the Set Curve Normal to \"Minimum Twist\". `BLI_assert` message should appear on the standard output.\n\ntest file:\n[rotate_direction_around_axis_normalize_bug.blend](rotate_direction_around_axis_normalize_bug.blend)\n\n**Suggested change:**\n\nNormalize the result of `rotate_direction_around_axis`:\n\n```\nlang=diff\ndiff --git a/source/blender/blenlib/intern/math_rotation.cc b/source/blender/blenlib/intern/math_rotation.cc\nindex 454862c8d18..92eb7832eb8 100644\n--- a/source/blender/blenlib/intern/math_rotation.cc\n+++ b/source/blender/blenlib/intern/math_rotation.cc\n@@ -20,7 +20,7 @@ float3 rotate_direction_around_axis(const float3 &direction, const float3 &axis,\n const float3 diff = direction - axis_scaled;\n const float3 cross = math::cross(axis, diff);\n \n- return axis_scaled + diff * std::cos(angle) + cross * std::sin(angle);\n+ return math::normalize(axis_scaled + diff * std::cos(angle) + cross * std::sin(angle));\n }\n \n float3 rotate_around_axis(const float3 &vector,\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" ]

[ "(2.80) Convert Curve to Mesh no longer functions at all\nOperating system: Xubuntu 18.04, 64 bit\nGraphics card: Nvidia GTX 860M\n\nBroken: 2.80.71\nWorked: in a previous 2.80 version\n\nAny curve object WILL NOT convert to a mesh.\nAny." ]

[ "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", "Re-saving 16bit PNG image with straight alpha multiple times corrupts the image\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.2.1\nWorked: ?\n\n\nRe-saving 16bit PNG image with straight alpha multiple times corrupts the image.\nAs far as I can tell it's broken only for 16/32bit images and works for 8bit\n\n[Texture.zip](Texture.zip)\n1) Open the file, paint something half-transparent (optionally)\n2) Press \"Save image\"\n3) Press \"Reload image\"\n4) Image should look different than before saving", "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.", "Texture Paint tools lead to incorrect colors on bright HDR textures in 3D\nOperating system: Linux-5.12.0-19.1-liquorix-amd64-x86_64-with-glibc2.31 64 Bits\nGraphics card: AMD Radeon RX 5700 (NAVI10, DRM 3.40.0, 5.12.0-19.1-liquorix-amd64, LLVM 11.0.0) AMD 4.6 (Core Profile) Mesa 21.0.1\n\nBroken: version: 2.93.0\nBroken: version: 3.0.0 Alpha\nWorked: N/A\n\nI am trying to touch up an HDR lightmap using the Texture Paint mode.\nAttempting to soften, smear or clone HDR images in 3D view in Texture Paint mode will lead to pixel values being clamped up to 1.0, unexpectedly removing bright spots. 2D view is not affected and the tools behave as expected. See video:\n[blendertexpaint.mp4](blendertexpaint.mp4)\n\nI have found that this line is responsible for this issue. Commenting it out fixes the problem.\nimageprocess.c#l219\nLine 219: `clamp_v4(outF, 0.0f, 1.0f);`\n\nI am unsure about the purpose of this line, or any unintended consequences of removing it. Someone else needs to take a look.\n\n1. Assign an HDR texture to an object's material.\n2. Enter Texture Paint mode\n3. Attempt to use the Soften, Smear or Clone tools to edit the texture in 3D view, in spots where the value of a pixel's R, G or B component is greater than 1.0\n4. The bright spots will unexpectedly become dark as they are touched by the tools.\n[Sample.blend](Sample.blend)\n\n", "Undo doesn't consider changes in nodetree when object is in edit and texture paint mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.79-3.4\n\nFor reference: this is due to this commit 4a08b974f4\nFrom the commit message:\n\"don't store undo steps for property changes in paint & edit modes.\"\n\nWhen in edit and texture paint mode, I can't undo changes, that I made in the shader editor. \n\n\n - Open .blend\n - Move some verts.\n - Change a shader node setting.\n - Press {key Ctrl Z}.\n # The verts move back, but the node setting remains.\n[#71895-undo-not-undoing-shader-nodes.blend](T71895-undo-not-undoing-shader-nodes.blend)", "GPencil: Hardlight blend issue\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\n\nThe semi-transparent textures of Grease Pencil material turn black when their layer is in HardLight blend mode.\n\n- open the provided blend file\n- see, wrong alpha blending\n- NB: change the blend mode and it works as expected\n\n[GP-hardlight-blend-issue.blend](GP-hardlight-blend-issue.blend)\n\n", "Wrong result mixing 2 nodes of an image texture\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.3, 2.93\nWorked: unsure\n\nWhen using 2 nodes of the same texture and connecting the Color output from one and the Alpha from another, the result looks different in comparison when using both outputs from one node. Broken in EEVEE\n\n1) Open the file, switch to material preview/rendered\n2) Reconnect the color (or the alpha) link to another texture\n[Bug1.blend](Bug1.blend)", "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. ", "Grease Pencil Alpha/Opacity bug\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31\n\nBroken: version: 3.1.0\n\nGrease pencil objects containing strokes with stroke materials can not be seen through separate grease pencil objects with either a stroke with fill material with an alpha value >0 or <1, a layer with opacity value >0 or <1. \nWhen the grease pencil object with the alpha material (or layer opacity) has its location moved forward in object mode, the other grease pencil object's stroke can be seen beneath it as expected.\n\n\n\n\n\n\n\n\n\n - Create grease pencil object\n - Create stroke with material with alpha value >0 or <1\n - Set Stroke depth Order to 3D location\n - Move layer location Y forward (-0.05m)\n - Create other grease pencil object\n - Create stroke with stroke material\n\n[grease_pencil_alpha_error.blend](grease_pencil_alpha_error.blend)\n\nThank you :D\n\n", "'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", "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", "Exchanging a color in Grease pencil from a color attribute is bugged\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 3.4.1\n\n**Short Description**\nExchanging a color in Grease pencil from a color attribute is bugged\n\n- Go into 2D animation\n- Draw a shape with a fill color using a color attribute\n- Change color attribute and draw another fill stroke\n- In materials tab create a new fill color\n- Assign that color in edit-mode to the shape to replace color attribute. \nIt doesn't look like it got applied. Go into viewport shading with material view and the assigned color is there. Pressing F12 shows the color that is supposed to be overwritten.[Color error.blend](Color_error.blend)", "Face orientation - no colors in X-Ray\nOperating system: windows 10\nGraphics card: NVIDIA GeForce GTX 1070 \nsame issue on different pc Samsung NP900X3C\n\nBroken: 2.83.2 and 2.90.0-f319eec88186 (latest 2020 jul 14)\nWorked: 2.80 ~ 2.82\n\n**Face orientation in X-Ray view does not show transparent colors(blue and red)**\n\n1) turn on face orientations ; \n2) turn on toggle X-Ray\n\n![2020-07-14 21-26-43.mkv_snapshot_01.48_[2020.07.14_21.57.56].png](2020-07-14_21-26-43.mkv_snapshot_01.48__2020.07.14_21.57.56_.png)\nhere how it works in 2.83.2 & 2.90.0 [2020-07-14 22-43-43.mkv](2020-07-14_22-43-43.mkv)\nand how it should like in 2.80 ~ 2.82 [2020-07-14 22-49-24.mkv](2020-07-14_22-49-24.mkv)", "Undo doesn't work with paint mask selection (texture paint vs. vertex/weightpaint)\nOperating system: Linux-5.2.10-arch1-1-ARCH-x86_64-with-arch 64 Bits\nGraphics card: Radeon RX 580 Series (POLARIS10, DRM 3.32.0, 5.2.10-arch1-1-ARCH, LLVM 8.0.1) X.Org 4.5 (Core Profile) Mesa 19.1.5\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nUndo does not work with paint mask selections. The expected behavior here is that undo should work as in other selection modes.\n\nClick on texture paint.\nSelect single image and create a texture.\nTurn on paint masking, and then select the \"select box\" tool.\nclick on a face on the cube to select it.\nPress ctrl-z.", "Paint Mode: Color Sampling\nNOTE: This task is currently to document the requirements for an updated color sampler for painting workflows. This should be the basis for discussions on the implementation.\n\n# Goal\n\nSampling colors is implemented in various different ways throughout Blender, each implementation with their own advantages and features.\nThe goal here is to combine all needed features into an easily accessible operator, with additional options to get other sampling effects.\nThis operator will then be used for color sampling in sculpt/paint mode and paint mode in the image editor.\n\nThe basic implementation in sculpt mode is already usable for now.\n\n# Requirements\n\n## Existing Features\n\n- Sample Merged (Only available in the keymap options or with the color picker button)\n- Add to Palette (Already available via left click)\n- Sample Size (Only in the image editor sample tool)\n- Live sample values for XY, RGBA, CMGB, HSVL, color (Only in the image editor sample tool)\n- Sample Interpolated vs Closest (Automatic for textures. Always picks closest in Weight painting. Not implemented for color attributes. Needs more investigation on what would be most useful.)\n\n## Accessibility\nThe easiest way to access the color sampling should always be with a shortcut.\nFor now the established default is `S`. We should follow this wherever possible to stay consistent.\n\nPotentially the best usable way to implement this in the UI is as a button in the color picker instead of an active tool.\nThe disadvantages of making this an active tool are \n- that it doesn't directly relate to any particular color or brush/tool\n- it's more intuitive to use as a temporary one-click operation (No needs to keep it active)\n\n## Sample other Objects\n\nIt's already possible to pick any color of the screen when sampling merged colors.\nWhen sampling the current paint slot of the Canvas this is not the case.\nMulti-object workflows are very common so there needs to be an implementation to instantly sample local colors from another object.\n\n**Use active Canvas picker mode**\nOne straight forward implementation would be to use the Canvas picker mode of the active object to define which colors will be picked. This mode can be set to:\n- Color Attribute\n- Image Texture\n- Material\n\nEach of the other visible objects will have an active color attribute, image texture and node in the material.\nSo the desired approach is to look for that data and use it for color sampling other objects whenever the option \"Sample Merged\" is not used.\n\n## Color Sample Overlay\n\nWhen painting for materials there will be cases where it is not obvious what color will be picked. \nFor example when picking from a greyscale image texture that is used for roughness, while you see the final material in Eevee with additional colors and procedural roughness textures mixed in.\n\nThis color sampling preview would ideally be shown directly on the brush cursor, comparing it side-by-side with the currently set color." ]

[ "Image Editor \"Erase Alpha\" brush erases all channels of float images\nLinux 64-bit\n\nBroken: 2.92\nNote: In versions 2.83 and earlier, Alpha was not premultiplied (this started in 4212b6528a, unsure if this should be the case if we are only looking at the Color without Alpha?).\n\nErasing the alpha on float images erase the RGB channels as well.\n[erase_alpha_bug.mp4](erase_alpha_bug.mp4)\n\n - Open the attached file. (Left image is a Non-float while right image is Float, both have Alpha channel. We are seeing only the RGB channels).\n - Use the brush \"Erase Alpha\" to erase part of the non-floating-point image (on the left).\n - Use shift-click to sample the pixel-values of this image. The RGB channels have **NOT** actually been affected and the image only appears to have been premultiplied.\n - Use the brush \"Erase Alpha\" on the floating-point image (on the right).\n # Use shift-click to sample the pixel-values of this image. **ALL** channels were erased!\n\nIt may look like the same bug as #86866 but it isn't! The brush works as expected; it's the RGB display that's wrong.\n[image editor bug.blend](image_editor_bug.blend)\n\n", "Image Editor \"Erase Alpha\" brush blending mode affects all channels\nOperating system: Linux 64-bit\n\n2.92\n\nWhen used on floating point images, the \"Erase Alpha\" brush blend mode erases not only the Alpha channel, but the RGB channels as well. This makes it impossible for the user to paint the alpha channel of an image without affecting the RGB channels. Although this is not the case with non-float images, it may appear to be at first glance; this will be submitted as a second but related bug.\n[image editor bug.blend](image_editor_bug.blend)\n - Open the attached file. Note that both images have an alpha channel but are currently viewed in RGB and not RGBA.\n - Use the default brush in \"Erase Alpha\" mode to erase a hole in the floating-point image on the right.\n - Use shift-click to sample the pixel-values of the image to confirm that the RGB channels have been multiplied/reduced.\n - This is also apparent when you try to use \"Add Alpha\" to un-erase the image- the completely erased parts do not come back.\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.", "VSE strip can't be seen with frame all\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` blender-2.90.0-ba2d1c889819-windows64` (BF Build Bot)\n\n\nChannel 32 can't been seen with Frame All\n\n\n|  |  |\n| -- | -- |\n\n\nHave at least 2.00 Display Scaling\n\n[Channel_32.blend](Channel_32.blend)", "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 ", "Breaking UI API changes for 4.0\n- [ ] Remove grid display for UI lists - Never worked well and is badly maintained. May have been added for an oudated asset UI design even?\n- [ ] Remove asset-view UI template - Should be replaced by the [asset shelf](102879).\n- [ ] Replace/deprecate UI lists? - Probably too much work, would require UI views to be exposed to Python. But can at least be converted to use UI views internally and benefit from its features.\n\n", "Preferences window lags with add-ons preferences UI raises an exception\nOperating system: Windows 10 1903\nGraphics card: GTX970\n\nBroken: blender-2.80-9c5d54bfaf48-win64\nWorked:blender-2.80-8ac0fef4dfd1-win64\n\n\nWhen you click on a triangle in the addons list which is corresponds to an addon which contains VISIBLE_IPO_ON in code, it starts to incredibly lag. Seriously, one frame per second or two. Everything is quick and snappy until you press that goddam triangle. After that whole Preferences window behave like this till the restart of Blender. Other windows are unaffected.\nObserve: \nwatch?v=9fObpt0L8B0\n\nIn a log I can see a long and sad error: Traceback (most recent call last):\n```\nFile \"C:\\Users\\ostap\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\DECALmachine\\ui\\UILists.py\", line 16, in draw_item\n row.prop(item, \"isvisible\", text=\"\", icon=isvisibleicon, emboss=False)\n```\nTypeError: UILayout.prop(): error with keyword argument \"icon\" - enum \"VISIBLE_IPO_ON\" not found in ('NONE', 'QUESTION', 'ERROR', 'CANCEL', 'TRIA_RIGHT', 'TRIA_DOWN', 'TRIA_LEFT', 'TRIA_UP', 'ARROW_LEFTRIGHT', 'PLUS', 'DISCLOSURE_TRI_RIGHT', 'DISCLOSURE_TRI_DOWN', 'RADIOBUT_OFF', 'RADIOBUT_ON', 'MENU_PANEL', 'BLENDER', 'GRIP', 'DOT', 'COLLAPSEMENU', 'X', 'DUPLICATE', 'TRASH', 'COLLECTION_NEW', 'NODE', 'NODE_SEL', 'WINDOW', 'WORKSPACE', 'RIGHTARROW_THIN', 'BORDERMOVE', 'VIEWZOOM', 'ADD', 'REMOVE', 'PANEL_CLOSE', 'COPY_ID', 'EYEDROPPER', 'AUTO', 'CHECKBOX_DEHLT', 'CHECKBOX_HLT', 'UNLOCKED', 'LOCKED', 'UNPINNED', 'PINNED', 'SCREEN_BACK', 'RIGHTARROW', 'DOWNARROW_HLT', 'FCURVE_SNAPSHOT', 'OBJECT_HIDDEN', 'PLUGIN', 'HELP', 'GHOST_ENABLED', 'COLOR', 'UNLINKED', 'LINKED', 'HAND', 'ZOOM_ALL', 'ZOOM_SELECTED', 'ZOOM_PREVIOUS', 'ZOOM_IN', 'ZOOM_OUT', 'DRIVER_DISTANCE', 'DRIVER_ROTATIONAL_DIFFERENCE', 'DRIVER_TRANSFORM', 'FREEZE', 'STYLUS_PRESSURE', 'GHOST_DISABLED', 'FILE_NEW', 'FILE_TICK', 'QUIT', 'URL', 'RECOVER_LAST', 'THREE_DOTS', 'FULLSCREEN_ENTER', 'FULLSCREEN_EXIT', 'LIGHT', 'MATERIAL', 'TEXTURE', 'ANIM', 'WORLD', 'SCENE', 'OUTPUT', 'SCRIPT', 'PARTICLES', 'PHYSICS', 'SPEAKER', 'TOOL_SETTINGS', 'SHADERFX', 'MODIFIER', 'BLANK1', 'FAKE_USER_OFF', 'FAKE_USER_ON', 'VIEW3D', 'GRAPH', 'OUTLINER', 'PROPERTIES', 'FILEBROWSER', 'IMAGE', 'INFO', 'SEQUENCE', 'TEXT', 'SOUND', 'ACTION', 'NLA', 'PREFERENCES', 'TIME', 'NODETREE', 'CONSOLE', 'TRACKER', 'ASSET_MANAGER', 'NODE_COMPOSITING', 'NODE_TEXTURE', 'NODE_MATERIAL', 'UV', 'OBJECT_DATAMODE', 'EDITMODE_HLT', 'UV_DATA', 'VPAINT_HLT', 'TPAINT_HLT', 'WPAINT_HLT', 'SCULPTMODE_HLT', 'POSE_HLT', 'PARTICLEMODE', 'TRACKING', 'TRACKING_BACKWARDS', 'TRACKING_FORWARDS', 'TRACKING_BACKWARDS_SINGLE', 'TRACKING_FORWARDS_SINGLE', 'TRACKING_CLEAR_BACKWARDS', 'TRACKING_CLEAR_FORWARDS', 'TRACKING_REFINE_BACKWARDS', 'TRACKING_REFINE_FORWARDS', 'SCENE_DATA', 'RENDERLAYERS', 'WORLD_DATA', 'OBJECT_DATA', 'MESH_DATA', 'CURVE_DATA', 'META_DATA', 'LATTICE_DATA', 'LIGHT_DATA', 'MATERIAL_DATA', 'TEXTURE_DATA', 'ANIM_DATA', 'CAMERA_DATA', 'PARTICLE_DATA', 'LIBRARY_DATA_DIRECT', 'GROUP', 'ARMATURE_DATA', 'COMMUNITY', 'BONE_DATA', 'CONSTRAINT', 'SHAPEKEY_DATA', 'CONSTRAINT_BONE', 'CAMERA_STEREO', 'PACKAGE', 'UGLYPACKAGE', 'EXPERIMENTAL', 'BRUSH_DATA', 'IMAGE_DATA', 'FILE', 'FCURVE', 'FONT_DATA', 'RENDER_RESULT', 'SURFACE_DATA', 'EMPTY_DATA', 'PRESET', 'RENDER_ANIMATION', 'RENDER_STILL', 'LIBRARY_DATA_BROKEN', 'BOIDS', 'STRANDS', 'LIBRARY_DATA_INDIRECT', 'GREASEPENCIL', 'LINE_DATA', 'LIBRARY_DATA_OVERRIDE', 'GROUP_BONE', 'GROUP_VERTEX', 'GROUP_VCOL', 'GROUP_UVS', 'FACE_MAPS', 'RNA', 'RNA_ADD', 'MOUSE_LMB', 'MOUSE_MMB', 'MOUSE_RMB', 'MOUSE_MOVE', 'MOUSE_LMB_DRAG', 'MOUSE_MMB_DRAG', 'MOUSE_RMB_DRAG', 'PRESET_NEW', 'DECORATE', 'DECORATE_KEYFRAME', 'DECORATE_ANIMATE', 'DECORATE_DRIVER', 'DECORATE_LINKED', 'DECORATE_LIBRARY_OVERRIDE', 'DECORATE_UNLOCKED', 'DECORATE_LOCKED', 'DECORATE_OVERRIDE', 'TRACKER_DATA', 'HEART', 'ORPHAN_DATA', 'USER', 'SYSTEM', 'SETTINGS', 'OUTLINER_OB_EMPTY', 'OUTLINER_OB_MESH', 'OUTLINER_OB_CURVE', 'OUTLINER_OB_LATTICE', 'OUTLINER_OB_META', 'OUTLINER_OB_LIGHT', 'OUTLINER_OB_CAMERA', 'OUTLINER_OB_ARMATURE', 'OUTLINER_OB_FONT', 'OUTLINER_OB_SURFACE', 'OUTLINER_OB_SPEAKER', 'OUTLINER_OB_FORCE_FIELD', 'OUTLINER_OB_GROUP_INSTANCE', 'OUTLINER_OB_GREASEPENCIL', 'OUTLINER_OB_LIGHTPROBE', 'OUTLINER_OB_IMAGE', 'RESTRICT_COLOR_OFF', 'RESTRICT_COLOR_ON', 'HIDE_ON', 'HIDE_OFF', 'RESTRICT_SELECT_ON', 'RESTRICT_SELECT_OFF', 'RESTRICT_RENDER_ON', 'RESTRICT_RENDER_OFF', 'RESTRICT_INSTANCED_OFF', 'OUTLINER_DATA_EMPTY', 'OUTLINER_DATA_MESH', 'OUTLINER_DATA_CURVE', 'OUTLINER_DATA_LATTICE', 'OUTLINER_DATA_META', 'OUTLINER_DATA_LIGHT', 'OUTLINER_DATA_CAMERA', 'OUTLINER_DATA_ARMATURE', 'OUTLINER_DATA_FONT', 'OUTLINER_DATA_SURFACE', 'OUTLINER_DATA_SPEAKER', 'OUTLINER_DATA_LIGHTPROBE', 'OUTLINER_DATA_GP_LAYER', 'OUTLINER_DATA_GREASEPENCIL', 'GP_SELECT_POINTS', 'GP_SELECT_STROKES', 'GP_MULTIFRAME_EDITING', 'GP_ONLY_SELECTED', 'GP_SELECT_BETWEEN_STROKES', 'MODIFIER_OFF', 'MODIFIER_ON', 'ONIONSKIN_OFF', 'ONIONSKIN_ON', 'RESTRICT_VIEW_ON', 'RESTRICT_VIEW_OFF', 'RESTRICT_INSTANCED_ON', 'MESH_PLANE', 'MESH_CUBE', 'MESH_CIRCLE', 'MESH_UVSPHERE', 'MESH_ICOSPHERE', 'MESH_GRID', 'MESH_MONKEY', 'MESH_CYLINDER', 'MESH_TORUS', 'MESH_CONE', 'MESH_CAPSULE', 'EMPTY_SINGLE_ARROW', 'LIGHT_POINT', 'LIGHT_SUN', 'LIGHT_SPOT', 'LIGHT_HEMI', 'LIGHT_AREA', 'CUBE', 'SPHERE', 'CONE', 'META_PLANE', 'META_CUBE', 'META_BALL', 'META_ELLIPSOID', 'META_CAPSULE', 'SURFACE_NCURVE', 'SURFACE_NCIRCLE', 'SURFACE_NSURFACE', 'SURFACE_NCYLINDER', 'SURFACE_NSPHERE', 'SURFACE_NTORUS', 'EMPTY_AXIS', 'STROKE', 'EMPTY_ARROWS', 'CURVE_BEZCURVE', 'CURVE_BEZCIRCLE', 'CURVE_NCURVE', 'CURVE_NCIRCLE', 'CURVE_PATH', 'LIGHTPROBE_CUBEMAP', 'LIGHTPROBE_PLANAR', 'LIGHTPROBE_GRID', 'COLOR_RED', 'COLOR_GREEN', 'COLOR_BLUE', 'TRIA_RIGHT_BAR', 'TRIA_DOWN_BAR', 'TRIA_LEFT_BAR', 'TRIA_UP_BAR', 'FORCE_FORCE', 'FORCE_WIND', 'FORCE_VORTEX', 'FORCE_MAGNETIC', 'FORCE_HARMONIC', 'FORCE_CHARGE', 'FORCE_LENNARDJONES', 'FORCE_TEXTURE', 'FORCE_CURVE', 'FORCE_BOID', 'FORCE_TURBULENCE', 'FORCE_DRAG', 'FORCE_SMOKEFLOW', 'RIGID_BODY', 'RIGID_BODY_CONSTRAINT', 'IMAGE_PLANE', 'IMAGE_BACKGROUND', 'IMAGE_REFERENCE', 'NODE_INSERT_ON', 'NODE_INSERT_OFF', 'NODE_TOP', 'NODE_SIDE', 'NODE_CORNER', 'SELECT_SET', 'SELECT_EXTEND', 'SELECT_SUBTRACT', 'SELECT_INTERSECT', 'SELECT_DIFFERENCE', 'ALIGN_LEFT', 'ALIGN_CENTER', 'ALIGN_RIGHT', 'ALIGN_JUSTIFY', 'ALIGN_FLUSH', 'ALIGN_TOP', 'ALIGN_MIDDLE', 'ALIGN_BOTTOM', 'BOLD', 'ITALIC', 'UNDERLINE', 'SMALL_CAPS', 'HOLDOUT_OFF', 'HOLDOUT_ON', 'INDIRECT_ONLY_OFF', 'INDIRECT_ONLY_ON', 'CON_CAMERASOLVER', 'CON_FOLLOWTRACK', 'CON_OBJECTSOLVER', 'CON_LOCLIKE', 'CON_ROTLIKE', 'CON_SIZELIKE', 'CON_TRANSLIKE', 'CON_DISTLIMIT', 'CON_LOCLIMIT', 'CON_ROTLIMIT', 'CON_SIZELIMIT', 'CON_SAMEVOL', 'CON_TRANSFORM', 'CON_TRANSFORM_CACHE', 'CON_CLAMPTO', 'CON_KINEMATIC', 'CON_LOCKTRACK', 'CON_SPLINEIK', 'CON_STRETCHTO', 'CON_TRACKTO', 'CON_ARMATURE', 'CON_CHILDOF', 'CON_FLOOR', 'CON_FOLLOWPATH', 'CON_PIVOT', 'CON_SHRINKWRAP', 'MODIFIER_DATA', 'MOD_WAVE', 'MOD_BUILD', 'MOD_DECIM', 'MOD_MIRROR', 'MOD_SOFT', 'MOD_SUBSURF', 'HOOK', 'MOD_PHYSICS', 'MOD_PARTICLES', 'MOD_BOOLEAN', 'MOD_EDGESPLIT', 'MOD_ARRAY', 'MOD_UVPROJECT', 'MOD_DISPLACE', 'MOD_CURVE', 'MOD_LATTICE', 'MOD_TINT', 'MOD_ARMATURE', 'MOD_SHRINKWRAP', 'MOD_CAST', 'MOD_MESHDEFORM', 'MOD_BEVEL', 'MOD_SMOOTH', 'MOD_SIMPLEDEFORM', 'MOD_MASK', 'MOD_CLOTH', 'MOD_EXPLODE', 'MOD_FLUIDSIM', 'MOD_MULTIRES', 'MOD_SMOKE', 'MOD_SOLIDIFY', 'MOD_SCREW', 'MOD_VERTEX_WEIGHT', 'MOD_DYNAMICPAINT', 'MOD_REMESH', 'MOD_OCEAN', 'MOD_WARP', 'MOD_SKIN', 'MOD_TRIANGULATE', 'MOD_WIREFRAME', 'MOD_DATA_TRANSFER', 'MOD_NORMALEDIT', 'MOD_PARTICLE_INSTANCE', 'MOD_HUE_SATURATION', 'MOD_NOISE', 'MOD_OFFSET', 'MOD_SIMPLIFY', 'MOD_THICKNESS', 'MOD_INSTANCE', 'MOD_TIME', 'MOD_OPACITY', 'REC', 'PLAY', 'FF', 'REW', 'PAUSE', 'PREV_KEYFRAME', 'NEXT_KEYFRAME', 'PLAY_SOUND', 'PLAY_REVERSE', 'PREVIEW_RANGE', 'ACTION_TWEAK', 'PMARKER_ACT', 'PMARKER_SEL', 'PMARKER', 'MARKER_HLT', 'MARKER', 'KEYFRAME_HLT', 'KEYFRAME', 'KEYINGSET', 'KEY_DEHLT', 'KEY_HLT', 'MUTE_IPO_OFF', 'MUTE_IPO_ON', 'DRIVER', 'SOLO_OFF', 'SOLO_ON', 'FRAME_PREV', 'FRAME_NEXT', 'NLA_PUSHDOWN', 'IPO_CONSTANT', 'IPO_LINEAR', 'IPO_BEZIER', 'IPO_SINE', 'IPO_QUAD', 'IPO_CUBIC', 'IPO_QUART', 'IPO_QUINT', 'IPO_EXPO', 'IPO_CIRC', 'IPO_BOUNCE', 'IPO_ELASTIC', 'IPO_BACK', 'IPO_EASE_IN', 'IPO_EASE_OUT', 'IPO_EASE_IN_OUT', 'NORMALIZE_FCURVES', 'VERTEXSEL', 'EDGESEL', 'FACESEL', 'CURSOR', 'PIVOT_BOUNDBOX', 'PIVOT_CURSOR', 'PIVOT_INDIVIDUAL', 'PIVOT_MEDIAN', 'PIVOT_ACTIVE', 'CENTER_ONLY', 'ROOTCURVE', 'SMOOTHCURVE', 'SPHERECURVE', 'INVERSESQUARECURVE', 'SHARPCURVE', 'LINCURVE', 'NOCURVE', 'RNDCURVE', 'PROP_OFF', 'PROP_ON', 'PROP_CON', 'PROP_PROJECTED', 'PARTICLE_POINT', 'PARTICLE_TIP', 'PARTICLE_PATH', 'SNAP_OFF', 'SNAP_ON', 'SNAP_NORMAL', 'SNAP_GRID', 'SNAP_VERTEX', 'SNAP_EDGE', 'SNAP_FACE', 'SNAP_VOLUME', 'SNAP_INCREMENT', 'STICKY_UVS_LOC', 'STICKY_UVS_DISABLE', 'STICKY_UVS_VERT', 'CLIPUV_DEHLT', 'CLIPUV_HLT', 'SNAP_PEEL_OBJECT', 'GRID', 'OBJECT_ORIGIN', 'ORIENTATION_GLOBAL', 'ORIENTATION_GIMBAL', 'ORIENTATION_LOCAL', 'ORIENTATION_NORMAL', 'ORIENTATION_VIEW', 'COPYDOWN', 'PASTEDOWN', 'PASTEFLIPUP', 'PASTEFLIPDOWN', 'VIS_SEL_11', 'VIS_SEL_10', 'VIS_SEL_01', 'VIS_SEL_00', 'AUTOMERGE_OFF', 'AUTOMERGE_ON', 'UV_VERTEXSEL', 'UV_EDGESEL', 'UV_FACESEL', 'UV_ISLANDSEL', 'UV_SYNC_SELECT', 'GIZMO', 'ORIENTATION_CURSOR', 'NORMALS_VERTEX', 'NORMALS_FACE', 'NORMALS_VERTEX_FACE', 'SHADING_BBOX', 'SHADING_WIRE', 'SHADING_SOLID', 'SHADING_RENDERED', 'SHADING_TEXTURE', 'OVERLAY', 'XRAY', 'LOCKVIEW_OFF', 'LOCKVIEW_ON', 'AXIS_SIDE', 'AXIS_FRONT', 'AXIS_TOP', 'NDOF_DOM', 'NDOF_TURN', 'NDOF_FLY', 'NDOF_TRANS', 'LAYER_USED', 'LAYER_ACTIVE', 'SORTALPHA', 'SORTBYEXT', 'SORTTIME', 'SORTSIZE', 'SHORTDISPLAY', 'LONGDISPLAY', 'IMGDISPLAY', 'BOOKMARKS', 'FONTPREVIEW', 'FILTER', 'NEWFOLDER', 'FILE_PARENT', 'FILE_REFRESH', 'FILE_FOLDER', 'FILE_BLANK', 'FILE_BLEND', 'FILE_IMAGE', 'FILE_MOVIE', 'FILE_SCRIPT', 'FILE_SOUND', 'FILE_FONT', 'FILE_TEXT', 'SORT_DESC', 'SORT_ASC', 'LINK_BLEND', 'APPEND_BLEND', 'IMPORT', 'EXPORT', 'LOOP_BACK', 'LOOP_FORWARDS', 'BACK', 'FORWARD', 'FILE_CACHE', 'FILE_VOLUME', 'FILE_3D', 'FILE_HIDDEN', 'FILE_BACKUP', 'DISK_DRIVE', 'MATPLANE', 'MATSPHERE', 'MATCUBE', 'MONKEY', 'HAIR', 'ALIASED', 'ANTIALIASED', 'MAT_SPHERE_SKY', 'MATSHADERBALL', 'MATCLOTH', 'MATFLUID', 'WORDWRAP_OFF', 'WORDWRAP_ON', 'SYNTAX_OFF', 'SYNTAX_ON', 'LINENUMBERS_OFF', 'LINENUMBERS_ON', 'SCRIPTPLUGINS', 'SEQ_SEQUENCER', 'SEQ_PREVIEW', 'SEQ_LUMA_WAVEFORM', 'SEQ_CHROMA_SCOPE', 'SEQ_HISTOGRAM', 'SEQ_SPLITVIEW', 'IMAGE_RGB', 'IMAGE_RGB_ALPHA', 'IMAGE_ALPHA', 'IMAGE_ZDEPTH', 'VIEW_PERSPECTIVE', 'VIEW_ORTHO', 'VIEW_CAMERA', 'VIEW_PAN', 'VIEW_ZOOM', 'BRUSH_BLOB', 'BRUSH_BLUR', 'BRUSH_CLAY', 'BRUSH_CLAY_STRIPS', 'BRUSH_CLONE', 'BRUSH_CREASE', 'BRUSH_FILL', 'BRUSH_FLATTEN', 'BRUSH_GRAB', 'BRUSH_INFLATE', 'BRUSH_LAYER', 'BRUSH_MASK', 'BRUSH_MIX', 'BRUSH_NUDGE', 'BRUSH_PINCH', 'BRUSH_SCRAPE', 'BRUSH_SCULPT_DRAW', 'BRUSH_SMEAR', 'BRUSH_SMOOTH', 'BRUSH_SNAKE_HOOK', 'BRUSH_SOFTEN', 'BRUSH_TEXDRAW', 'BRUSH_TEXFILL', 'BRUSH_TEXMASK', 'BRUSH_THUMB', 'BRUSH_ROTATE', 'GPBRUSH_SMOOTH', 'GPBRUSH_THICKNESS', 'GPBRUSH_STRENGTH', 'GPBRUSH_GRAB', 'GPBRUSH_PUSH', 'GPBRUSH_TWIST', 'GPBRUSH_PINCH', 'GPBRUSH_RANDOMIZE', 'GPBRUSH_CLONE', 'GPBRUSH_WEIGHT', 'GPBRUSH_PENCIL', 'GPBRUSH_PEN', 'GPBRUSH_INK', 'GPBRUSH_INKNOISE', 'GPBRUSH_BLOCK', 'GPBRUSH_MARKER', 'GPBRUSH_FILL', 'GPBRUSH_ERASE_SOFT', 'GPBRUSH_ERASE_HARD', 'GPBRUSH_ERASE_STROKE', 'SMALL_TRI_RIGHT_VEC', 'KEYTYPE_KEYFRAME_VEC', 'KEYTYPE_BREAKDOWN_VEC', 'KEYTYPE_EXTREME_VEC', 'KEYTYPE_JITTER_VEC', 'KEYTYPE_MOVING_HOLD_VEC', 'HANDLETYPE_FREE_VEC', 'HANDLETYPE_ALIGNED_VEC', 'HANDLETYPE_VECTOR_VEC', 'HANDLETYPE_AUTO_VEC', 'HANDLETYPE_AUTO_CLAMP_VEC', 'COLORSET_01_VEC', 'COLORSET_02_VEC', 'COLORSET_03_VEC', 'COLORSET_04_VEC', 'COLORSET_05_VEC', 'COLORSET_06_VEC', 'COLORSET_07_VEC', 'COLORSET_08_VEC', 'COLORSET_09_VEC', 'COLORSET_10_VEC', 'COLORSET_11_VEC', 'COLORSET_12_VEC', 'COLORSET_13_VEC', 'COLORSET_14_VEC', 'COLORSET_15_VEC', 'COLORSET_16_VEC', 'COLORSET_17_VEC', 'COLORSET_18_VEC', 'COLORSET_19_VEC', 'COLORSET_20_VEC', 'EVENT_A', 'EVENT_B', 'EVENT_C', 'EVENT_D', 'EVENT_E', 'EVENT_F', 'EVENT_G', 'EVENT_H', 'EVENT_I', 'EVENT_J', 'EVENT_K', 'EVENT_L', 'EVENT_M', 'EVENT_N', 'EVENT_O', 'EVENT_P', 'EVENT_Q', 'EVENT_R', 'EVENT_S', 'EVENT_T', 'EVENT_U', 'EVENT_V', 'EVENT_W', 'EVENT_X', 'EVENT_Y', 'EVENT_Z', 'EVENT_SHIFT', 'EVENT_CTRL', 'EVENT_ALT', 'EVENT_OS', 'EVENT_F1', 'EVENT_F2', 'EVENT_F3', 'EVENT_F4', 'EVENT_F5', 'EVENT_F6', 'EVENT_F7', 'EVENT_F8', 'EVENT_F9', 'EVENT_F10', 'EVENT_F11', 'EVENT_F12', 'EVENT_ESC', 'EVENT_TAB', 'EVENT_PAGEUP', 'EVENT_PAGEDOWN', 'EVENT_RETURN')\n\nAnd after changing VISIBLE_IPO_ON/OFF to HIDE_OFF/ON in the mentioned file issue disappears. Of course you may say that it's the issue with an un-updated addons. but that's weird. when Blender starts to misbehave instead of showing error message about the issue, isn't it?\n\n1. Open any scroll of the addon with VISIBLE_IPO_ON in it. \n2. Enjoy the performance. ", " 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", "Animation channels list UI\nThere are various problems with the animation editor's channel list. Many affordances from the Outliner are missing here, making it difficult to select, navigate and see clearly what is selected. We can also optimize how you switch between visible F-curves, which currently requires users to manually enable or disable visibility toggles.\n\n**List of changes**\n\nFunctional changes:\n- - [ ] Add an option, on by default, to only show the selected channel curves. When enabled, don't show the eye toggle, since it becomes redundant. \n- - [ ] Update the channel list to behave like the Outliner:\n - Hold Shift to do range selections (Ctrl to do normal extend)\n - Highlight the entire row on mouse-over.\n - Use arrows for walk-selection, also in combination with Shift to extend\n - Filter the icon columns like the restriction columns in the outliner. For example, not everybody uses modifiers, so having a column of buttons to disable modifiers can be useless.\n- - [ ] Replace box-select with click-drag (like buttons). This will give more immediate feedback of which channels are selected, rather than seeing that feedback only when releasing the mouse.\n- - [ ] Auto-scroll the list back into view when all the list entries are outside the view (happens when changing selections)\n- - [ ] Auto-scroll the channel list when drag-selecting.\n\n\nVisual changes:\n\n- - [x] Separate the eye toggle from the Graph Editor curve color indicator ([D5882](D5882))\n- - [ ] Use alternating lines (see Outliner)\n- - [ ] Highlighted row should use solid colored background (see Outliner)\n- - [ ] Rolling over rows should highlight them (see Outliner)", "If the user changes the OS terminal to one that cannot be hidden by its clients, then blender cannot hide it\nOperating system: Win11 (also probably true on Win10)\nGraphics card: 3090\n\nBroken: 3.1\nWorked: probably N/A\n\nWhen Windows Terminal is set as the default terminal Blender will launch under it, but can't hide it - the terminal will always be visible and Window>Toggle System Console doesn't work.\n\nUpdated from Harleys comment - since Blender can't work with Windows Terminal and it breaks the use model and menu choice, change this to a request to have Blender only use the old style Windows terminal regardless of the default terminal. \n\nWindows Terminal is a Microsoft replacement for the default cmd window, supporting tabs, settings and other advanced features. \n\n - Install Windows Terminal (Microsoft Store or otherwise)\n - Open it, on the tab bar click the down arrow\n - Click Settings in the menu (or just hit Ctrl-,)\n - Set Default terminal application to Windows Terminal\n - Close, start blender which launches from a Windows Terminal\n - Close the terminal and Blender quits\n - Toggle System Console doesn't work either\n```\n\n```\n\n", "Incorrect Areas affected by Timeline Playback settings\nVersion: 2.80 rc2 (Linux 64)\n\n[Timeline_bug.blend](Timeline_bug.blend)\n\nTo reproduce:\n\n - Open the example file (enable \"Load UI\" too)\n - With the mouse cursor in the 3d view, play the animation using Shift + Space (or Alt + A, whatever your keymap is)\n - Ignore the 3d view. Notice which animation editors show a moving playhead.\n - Inspect the playback settings in the timeline editor.\n - Disable \"All 3d Viewports\" and repeat step 2.\n - Now Enable \"Active Editor Only\" and repeat step 2.\n\nWith certain settings, the Dope Sheet and Timeline show playback even when the Graph Editor and NLA do not. It's as if these windows think they are 3d viewports!", "VSE: 'Reverse Frames' is reversing the source input and not the strip \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.90.1\n\n'Reverse Frames' is reversing the source input and not the strip.\n{[F9358967](Reverse_Frames.gif), size=full} \n\nDownload this file with a counter video included:\n[Reverse_Frames_bug.blend](Reverse_Frames_bug.blend)\nNotice that the video is counting up from zero to 4 sec. \nSplit the movie strip at 2 sec.\nSelect left side.\nCheck Reverse Frames for the left side strip.\nIt is now counting down from 4 sec to 2 sec.\nIt should count from 2 sec to zero sec. \n\nSo, currently this is not a Strip setting, but a Source setting. Question is if this should be moved into the Source panel or be properly implemented as a strip setting?\n\nBtw. the function `Strobe`, which is repeating frames, but keeping sync, has the wrong name: strobe \nWhen doing this process on celluloid-film-stock the this process is called \"Step Printing\": step_printing/\n\n", "VSE: \"Speed Factor\" property for Sound strips should presumably be removed\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.67\n\nBroken: version: 4.0.0 Alpha\n\nIn Blender 3.6.1, most strip types (Movie, Sound, Scene and even Image) have a \"Speed Factor\" property in the Sidebar -> Strip -> Time panel.\nIn Blender 4.0, this property has been removed from most strip types, no doubt in favor of the new Retime tool. However, Sound strips still have it, which looks like it could be an oversight.\n\n", "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.**", "Sound Strips in VSE retain hard length limits when Sound Datablock is changed\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n3.2.1 official\n\nIf the source of a sound strip in the VSE is changed to a different existing datablock, the length of the strip will not be updated and it will retain the same hard limits with regard to duration as the original sound, even if the new sound is longer.\n\n[SoundStripBug.blend](SoundStripBug.blend)\n - Open attached file\n - Select the shorter sound strip.\n - In the Source panel, change the sound for the strip from \"GetSomeCoffee.wav\" to \"Joe_trombone.wav\"\n - Despite having a longer sound now, you can't grab the right handle of the strip to make it any longer.\n # You can change the duration of the strip manually in the Time panel, but the highlighted duration of the original sound is still visible on the strip. If you grab the right handle, it will snap back.\n\n", "VSE View menu - missing hotkeys for sidebar and toolbar in Preview mode\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\n\n\"Caused\" by 6aef124e7d\n\nThe VSE is missing the default hotkeys to open the sidebar and toolbar in Preview mode. T and N\n\nWhen you add them by yourself, then these hotkeys gets added in the Window section. Which can lead to override conflicts.\n\n\n- Open Blender\n- Switch to VSE\n- Watch the View menu in the upper Preview window\n\n\n\n\n\n\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" ]

[ "Setting Sequencer view type to \"preview\" causes \"both\" to no longer work\nOS: Ubuntu 14.04\nLinux kernel: 3.13.0-24-generic\nGraphics:\nVGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)\n3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1)\n\nBroken: blender-2.71-8365ceb-linux-glibc211-x86_64\n\n\nClicking on the preview button in the Sequencer View buttons (in the VSE header) causes something to go wrong - you can no longer click on the \"both\" Sequencer View button.\n\n\n1) Open new .blend file and go to the VSE\n2) (optional) SHIFT+A -> Scene -> Scene\n3) Toggle between \"sequencer\" and \"both\" in the Sequencer View buttons and verify it works well. (in the info window, this outputs: \"bpy.context.space_data.view_type = 'SEQUENCER_PREVIEW'\", and then \"bpy.context.space_data.view_type = 'SEQUENCER'\")\n4) Hit the preview button (which displays \"bpy.context.space_data.view_type = 'PREVIEW'\" in info window)\n5) Try step 3 again and you'll see that the 'SEQUENCER_PREVIEW' view does not work properly, it just displays either the sequencer or the preview, but not both.\n\nHere's a .blend with steps 1-4 completed: [VSE_views_bug.blend](VSE_views_bug.blend)\n", "VSE does not display properly when in \"Both\" mode\n**Duplicates**: #36457\n\n\n%%%--- Operating System, Graphics card ---\nWindows 7, no graphics card (the issue is not related to either factor)\n\n\n - Blender version with error, and version that worked ---\n\nAll 2.5x and later versions have this behavioral problem.\n\n\n - Short description of error ---\nWhen VSE is set to \"Both\" view (mode), Blender should split the window and show both views (\"Sequencer\" and \"Preview\") simultaneously.\n\nInstead, it shows the \"Sequencer\" mode (view) ONLY. To a new user, this is confusing (looks like the command failed).\n\nFurther, the user is expected to drag a tiny + button downward from the right-hand-top corner of the window.\nHere, another unexpected thing happens: As soon as he drags the button, the \"preview\" panel springs open and occupies the WHOLE window.\nThe user cannot see the \"preview\" view at all. \n\n(Expected behavior: When the user drags the + button, the dividing line between the \"Sequencer\" and \"Preview\" views would be dragged smoothly, so the user can set the panes for both views exactly as he likes.) \n\nInstead, Blender has a strange way to make the \"Sequencer\" view visible: The user has to grab the lower wedge of the window and pull it down.\nAs the entire window re-sizes, the \"Sequencer\" view opens gradually. \nThis also is very odd behavior.\n\n - Steps for others to reproduce the error (preferably based on attached .blend file) ---\n\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", "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)", "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", "Particle hair simulation not working\nOperating system: Windows 10\nGraphics card: GTX 1070ti\n\nBroken: 2.93.4\nWorked: unknown\n\nI modeled particle-hair and try to make it dynamic, for whatever reason I cannot make it to work and sometimes Blender crashes.\n\n[Test.blend](Test.blend)\n\n[Test.crash.txt](Test.crash.txt) \n\nIf I try another simple particle-hair system on the-same object it does work. \n\nTry to get the hair in attached file to simulate.", "VSE: Tool option Drag options exposed in Annotation & Sample Tool\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 options shouldn't be exposed in the Annotation and Sample Tool, as it doesn't make sense to change dragging behaviour in these tools:\n\n\n", "percent bevel by weight doesn't work properly\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\n\nBroken: version: 3.4.1\n\npercent bevel by weight doesn't work properly \n\n\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", "Freestyle doesn't render hair\nOperating system: Win10 64bit\nGraphics card: gtx1050ti\n\nBroken: 2.8-155c62b070a9\nWorked: 2.79b\n\nRender file with Cycles in 2.79b and 2.8. In 2.8 only mesh is outlined.\n[free.blend](free.blend)", "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", "Cycles: Pointiness has artefacts on extremely small mesh size\nOperating system:\nGraphics card:\n\nBroken: version: 3.6.0 Alpha\nWorked: Never\n\nPointiness has artefacts on extremely small mesh size. \n\n| Normal size | Small size | Smaller size |\n| -- | -- | -- |\n|  |  |  |\n\n1. Create cube with beveling edges. Create small copies on vertices (as on example pictures).\n2. Set shader to cube. Shader with:\n a. Inputs: Geometry -> Pointiness.\n b. Map range: From Min: 0.5, From Max: 0.54.\n c. Material Output.\n3. Render that cube with applied different sizes.", "Interpolated hair curves clipping into meshes with subdivision modifiers unapplied\nOperating system: Windows 10\nGraphics card: RTX 2080 Super Max-Q\n\nBroken: 3.51\nWorked: N/A\n\nInterpolated hair curves clip into meshes with unapplied subdivision modifiers. Will stop clipping once subdivision is applied.\n\n1. Create a mesh (i.e. suzanne) and add a subdivision modifier with any amount of subdivision. \n2. Add 'fur' hair curves and do a basic groom\n3. Notice (hopefully) that there a bald spots. No amount of extra guide curves will remove these bald spots\n4. Applying the subdivision modifier should remove these bald spots.\n\n", "The X or Delete button does not work in the outliner (Blender File)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\n[The X or Delete button does not work in the outliner (Blender File)]\n\n- Open default startup file\n- {nav Outliner >Display Mode > Blender File}\n- In outliner {nav Brush > RMB > Delete > RMB > Assign Shortcut > X}\n- Attempt to delete any brush with hotkey (will not delete brush)\n- Change hotkey (eg {key Shift X}) and now attempt to delete brush with hotkey\n\nwhen you press X items in:\n| Broken | Brushes, Cameras, Images, Lights, Line Styles, Materials, Meshes, Palettes, Workspaces, Worlds |\n| -- | -- |\n| worked | Collections, Objects, Scenes |\n\n\n\n\n[Delete _X_ Button.blend.py](Delete__X__Button.blend.py)\n\n{[F12271213](Delete__X__Button.blend)}]\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", "Render Region widgets do not appear when active object is not a camera\nOperating system: Linux-5.19.0-41-generic-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.105.01\n\nBroken: version: 3.5.1\nAlso broken: version: 3.6.0 Alpha\n\nWhen there is any active object in scene the render region widgets are invisible.\n\nDefault scene.\nCtrl+B to set render region\nNo widgets are visible\n\nDelete all objects\nThe render region widgets are visible and accessible.\n\n\n", "Edge overlay seems to do nothing expected\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 511.23\n\nBroken: version: 3.1.0\nWorked: 2.79\n\nBack in 2.79, we could disable the \"edge\" overlay in edit mode. This was useful I.E. in cases where highlighting edges in vertex selection mode made things hard to read :\n\n\nIn the current stable version, this option seems to do nothing:\n\n\n\nActually, when in solid mode, it seems to display another layer of wireframe on top of the already existing one, which definitely looks weird and pointless. GIF demo:\n\n\n\nOn a mesh in edit mode, try toggling the edge overlay on and off.\n\n" ]

[ "Clipping region doesn't clip\nOperating system: Linux - Debian Stable\nGraphics card: Nvidia gtx 970\n\nBroken: version: 3.5.0 Alpha, branch: master (modified), commit date: 2022-12-27 16:50, hash: d7dad425c0d0, type: Release\nWorked: Not sure. It was broken in a build from last week though.\n\nAlt-B to set clipping region displays the shaded clipping region area but has no effect on visibility of anything in the scene otherwise.\n\n\n\nReproduce:\n1. Default scene with default cube\n2. Alt-B (or whatever) to set a clipping region\n\n", "Regression: Clipping Region in the viewport its not working\nOperating system: Linux-5.15.0-56-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: version: 3.5.0 Alpha\nWorked: 3.4.0\nCaused by bfb6ea898b\nIts Clipping Region not clipping.\n| 3.5 alpha | 3.4 official |\n| -- | -- |\n|  |  |\n\n1- dont delete the default cube\n2- alt+b and box select a part of the cube.\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```", "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", "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", "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.", "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", "Rigid Body System stops working when particle system added\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon RX Vega ATI Technologies Inc. 4.5.13587 Core Profile Context 20.2.2 26.20.15019.15019\n\nBroken: version: 2.82 (sub 7) & 2.83 (sub 5)\nWorked: -\n\nI have a rigid body collision setup with various chained constraints - if I add a particle system to any of the active rigid body objects, the simulation ceases to run.\n\nBlender file attached. Try adding a particle system to the 'Brick to test particle system' object in the main collection (or any other active object, the specified one simply for convenience). \n\nThe simulation will not run. Remove the particle system, the simulation runs again. \n\nI would like to add particles emitting from the objects to simulate debris/dust but hit this issue and can't find any workaround. \n\nAny insight much appreciated!\n\n\n\n[Wall destruction march v1.blend](Wall_destruction_march_v1.blend)\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 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.", "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", "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", "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", "Particle hair (chilrden) not showing up on viewport - Blender 3.1\nOperating system: macOS-12.3.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.15\n\nBroken: version: 3.1.2\nWorked: 3.0.1\n\nHey guys, Not sure if I am doing something wrong but on 3.1 + 3.1.2. hair particles are not showing up after a certain number on the \"display amounts\" - For the attached project for example if I go beyond 16 on the display amounts, all the hair disappears. The same happens if I increase the Stand steps on the Viewport Display panel\n\nmay that be a bug ? I am not sure, it looks like one because in 3.0 the problem does not appear. \n\n\nIncrease the number of the Children Display amount.\n\nthanks a lot! \n\n\n[hair-particles-issue-Mac-AMD-3-1.blend](hair-particles-issue-Mac-AMD-3-1.blend)", "Regression: Crash when Sculpting on a mesh from a GP Lineart Modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (W11)\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.2, 4.0.0 Alpha\nWorked: 3.1\n\n\nWhen trying to sculpt a mesh in an assigned collection that a grease pencil lineart modifier references and the layer it is drawing to contains Grease Pencil strokes - it will instantly crash Blender. \n\n\n1. Download and extract zip to get the test blend file\n2. Load attached file with Load UI off\n3. Select the bust, it is in a GP lineart modifier collection \n4. Go to sculpt mode\n5. Try sculpt\n6. Crash\n\nAlternative steps:\n1. Create new scene\n2. Create a sphere\n3. Create a Grease Pencil object\n4. Add sphere to a new collection\n5. Select the GP object and add a lineart modifier\n6. Reference the sphere collection in the modifier\n7. Assign layer and material to the modifier\n8. Draw in the same layer in Draw mode of the GP\n9. switch to sculpt mode\n10. Try sculpt over sphere surface\n11. Instant crash\n\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)", "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" ]

[ "Selecting Particle Edit integration mode will cause blender to crash\n10.13.6 (17G65) NVIDIA GeForce GTX 780M 4096 MB Web Driver 387.10.10.10.40.105\n\nBroken:2.8 Alpha d28d202fd1\n\n[edit-particle.blend](edit-particle.blend)\n\nUsing attached blend file.\n1. Select 'Particle Edit' from interaction mode\n2. Blender crashes\n\nMacOS Crash Report:\nNotes: Translocated Process\n\nCrashed Thread: 1\n\nException Type: EXC_CRASH (SIGSEGV)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Signal: Segmentation fault: 11\nTermination Reason: Namespace SIGNAL, Code 0xb\nTerminating Process: blender [1190]\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 com.nvidia.web.GeForceGLDriverWeb\t0x0000000125698cc1 0x12530a000 + 3730625\n1 libGPUSupportMercury.dylib \t0x00007fff58ae1fa3 gldUpdateTransformFeedbackState + 14\n2 org.blenderfoundation.blender \t0x000000010fab4945 GPU_shader_transform_feedback_enable + 101\n3 org.blenderfoundation.blender \t0x000000010fae3d2e drw_draw_pass_ex + 1102\n4 org.blenderfoundation.blender \t0x000000010fadc41b DRW_draw_render_loop_ex + 1227\n5 org.blenderfoundation.blender \t0x000000010f5c525c view3d_main_region_draw + 124\n6 org.blenderfoundation.blender \t0x000000010f7d26ca ED_region_do_draw + 362\n7 org.blenderfoundation.blender \t0x000000010f4dd6f3 wm_draw_update + 1619\n8 org.blenderfoundation.blender \t0x000000010f4d8fe0 WM_main + 48\n9 org.blenderfoundation.blender \t0x000000010f4d4e8c main + 972\n10 libdyld.dylib \t0x00007fff67ea1015 start + 1", "Blender 2.8 Particle edit crash\n{[F5081919](crash.mp4)}MacOS with intel core i5 and NVIDIA GeForce 640M 512 MB\n\n**version**: Blender 2.8 Alpha 2 (latest MacOS version as of 14 oct 2018)\n\nWhen entering particle edit mode, Blender will always crash (I have tried repeatedly and did various changes (adding material, changing shape, altering hair count). This bug has been in the system in Alpha version 1 for MacOS too. Also now is a good time to point out that hair for any object looks very dodgy when added but the issue resolves itself when entering edit mode and out.\n\n**To get the bug**\nOpen any new file and add any shape. Add a particle system and set it to hair. Enter Particle Edit mode.\nBlender crashes. Video included\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", "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 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)", "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 3.5 crash on render with Intel 4600 integrated GPU\nOperating system: WIndows 10 x64\nGraphics card: Intel 4600\n\nBroken: 3.5 \nWorked: 3.4.1\n\n\nBlender crashes when attempting to render in Evee. Cycles seems to work.\n\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)", "Sculpt Texture Paint: Seam Bleeding errors\nOperating system: Linux-6.1.12-gentoo-x86_64-AMD_Ryzen_Threadripper_1950X_16-Core_Processor-with-glibc2.36 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.89.02\n\nBroken: version: 3.6.0 Alpha\nWorked: ---\n\n\nWith the experimental `Sculpt Texture Paint` preference there are still some seam bleeding issues.\n\n\n\nThis task is for @Jeroen-Bakker to look into.\n\n**.blend file**\n[bug.blend](attachment)\n\n", "Crash on render on some of the frames\nOperating system: Linux-4.4.0-154-generic-x86_64-with-debian-stretch-sid 64 Bits\n8x Tesla V100 SXM2 NVLINK Accelerator Cards\nDual XEON Scalable 4208 CPUs\n192 GB RAM\n\nBroken: version: 2.82 (sub 7)\nI also tested recent 2.83 build\n\nBlender crash when it renders scene frames from 346-639, the rest of the frames are fine.\nIt crashes for CPU anf GPU as well.\n\nIn order to render above frames I workaround the assert:\n\n```\n--- a/intern/cycles/kernel/kernel_compat_cpu.h\n+++ b/intern/cycles/kernel/kernel_compat_cpu.h\n@@ -74,8 +74,10 @@ CCL_NAMESPACE_BEGIN\n template<typename T> struct texture {\n ccl_always_inline const T &fetch(int index)\n {\n- kernel_assert(index >= 0 && index < width);\n- return data[index];\n+ //kernel_assert(index >= 0 && index < width);\n+ if (index < 0) return data[0];\n+ else if (index >= width) return data[width];{F8410049}\n+ else return data[index];\n }\n #if defined(__KERNEL_AVX__) || defined(__KERNEL_AVX2__)\n /* Reads 256 bytes but indexes in blocks of 128 bytes to maintain\n```\n\nThe scene is complex and I couldn't make it very simply and narrow the problem.\nPlease find the scene attached.\n\n[animation_002_02_part01.blend](animation_002_02_part01.blend)\n\n1. Open Blender 2.82\n2. Open attached scene\n3. Set frame 346, start render (F12)\n4. After one minute or so it will crash\n\n\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)", "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", "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", "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)", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Assert in debug for dyntopo sculpt\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: Today main.\n\nSee attached stack trace file.\n\nIn debug:\n1. Sculp mode.\n2. Enable Dyntopo option.\n3. Do something.\nSee the crash.\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" ]

[ "Crash when switching to UVEditing or Texture Paint\nOperating system: ArchLinux\nGraphics card: Nvidia GTX 1080\n\nBroken: 2.80, Manual build from today commit c358da6b21158792bc05fa17fa00440675d0e76e\nWorked: 2.80, Manual build from yesterday (c041e10c9a94)\n\nBlender crashes when switching to the UV Editing tab or Texture Paint tab in default startup.\nAnother type of crash stack trace is generated opening the file from this issue #63969, and then switching to the Animation tab as soon as possible.\n\nJust open Blender and switch to UV Editing or Texture Paint.\n\n[crash_uvedit.txt](crash_uvedit.txt)\n[crash_texturepaint.txt](crash_texturepaint.txt)\n[crash_T63969.txt](crash_T63969.txt)\n\nI did not split the bugs because they are probably related, but tell me if you would like them to be filed separately.", "Crash when selecting \"UV Editing\" or \"Texture Paint\" workspaces\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.31\n\n\nBroken: version: 2.80 (sub 60)\nWorked: version: 2.80 (sub 60)\n\n\nWhen I try to switch to \"texture paint\" or \"uv editing\" workspace, Blender quits.\n\n- Open Blender\n- Click on \"Texture Paint\" or \"UV Editing\" tab\n\n", "Blender 2.8 crashes when I click UV Editing or Texture Paint tabs\nOperating system: Linux-4.15.0-48-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 415.27\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nBlender 2.8 crashes when I click UV Editing or Texture Paint tabs. Always, in any conditions. Even just downloaded and unpacked.\n\n\n**Steps to reproduce error**\nRun Blender. Click UV Editing tab or Texture Paint tab. It crashes. In /tmp/blender.crash.txt we can see:\n# Blender 2.80 (sub 60), Commit date: 2019-05-08 22:27, Hash e2d04229c38b\nbpy.ops.paint.texture_paint_toggle() # Operator\nTool 'builtin_brush.draw' not found for space 'IMAGE_EDITOR'. # Warning\n\n# backtrace\n./blender(BLI_system_backtrace+0x1d) [0x134d2ed]\n./blender() [0x1166ad9]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7f295aa15f20]\n./blender() [0x2a842ce]\n./blender(DRW_mesh_batch_cache_get_uv_edges+0x13) [0x2a85593]\n./blender(ED_uvedit_draw_main+0xc45) [0x40df395]\n./blender() [0x2cc4747]\n./blender(ED_region_do_draw+0x851) [0x2d63901]\n./blender(wm_draw_update+0x462) [0x1528812]\n./blender(WM_main+0x30) [0x1526020]\n./blender(main+0x30a) [0x10ccdea]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f295a9f8b97]\n./blender(_start+0x2a) [0x11633ea]", "Switching to Texture Paint crashes the application\nOperating system: Linux-4.15.0-48-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 415.27\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nBlender crashes if to switch to Texture Paint tab\n\nStart application. Click to Texture Paint tab\n\n", "Blender crash when selecting Texture Paint tab\nOperating system: MacOS Mojave v 10.14.4\nGraphics card: Intel Iris Graphics 540 1536 MB\n\nBroken: 2.80, 7c9e649015d4, master, 2019-05-09 09:38\nWorked: (optional)\n\nThe Blender crash once press on Texture Paint Tab\n\nNo need to do anything just press the Texture Paint and it will crash.", "Blender Beta crashes when you press texture paint\nOperating system: Windows\nGraphics card: Intel(R) UHD Graphics 620\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nBeta 2.8\nWorked: (optional)\n\ncrashes\nBased on the default startup or an attached .blend file (as simple as possible).\ngo in blender 2.8 and press the texture paint tab" ]

[ "Crash/Assert with two modifiers that require normals data [e.g. DataTransfer]\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.90.0\n\nCrash/Assert with two modifiers that require custom normals data [e.g. DataTransfer]\n\nIn a Debug build:\n\n[#84664.blend](T84664.blend)\n- Open File\n- add another modifier that requires normal data (e.g. Displace), or just duplicate the existing modifier\n\n[un2.blend](un2.blend)\n- Try to go to edit mode of \"Vert.011\"\n- Blender will crash.\n\n", "Metal backend: View Port drawing issue with face orientation\nOperating system: macOS-13.4-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API Intel(R) Iris(TM) Plus Graphics 1.2\n\nBroken: version: 3.5.1, 3.6-beta, 4.0\nWorked: with OpenGL backend\n\nWhen enabling \"face orientation\" in the view port the display does not update until I rotate the model. When rotating the model the face orientation colour overlay display is broken.\n\nSee attached screen movie showing the issue.\n\nTo reproduce:\n1. start with a new default scene\n2. enable face orientation overlay from view port overlays menu\n3. rotate the cube\n\nThis was observed using the default startup cube.\n\n", "Remove DerivedMesh: subsurf-uv unwrap\nCurrently UV unwrap uses derived mesh, see: `construct_param_handle_subsurfed`", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "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.", "Assertion reloading space_headers.blend (UI test file)\nLinux-6.3.3\n\nBroken: `b567b249d40488e5d90235e1a89c98853c5fd099` (4.0 main branch)\nWorked: (needs investigation)\n\n\nLoading `lib/tests/ui_tests/space_headers.blend` twice asserts.\n\n\n1. Run `blender ../lib/tests/ui_tests/space_headers.blend`.\n2. Ctrl-O (and open the file again).\n\nBlender exits with:\n```\nBLI_assert failed: source/blender/editors/space_file/filesel.cc:1094, ED_fileselect_init_layout(), at 'layout->rows != 0'\n```", "Face overlay still not resolve.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: 3.4.1\n\nDepth offset in Metal overlay is much larger than seen in OpenGL\n| OpenGL | Metal |\n|---|---|\n|  |  |\n\n\n- Open attached .blend file\n\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", "Test bf_imbuf_save fails with an assert in debug builds (DPX 8-bit save)\nOperating system: Linux-6.2.0-10007-tuxedo-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce RTX 3070 Ti Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03\n\nBroken: version: 3.6.0 Beta\n\n\n\n- Compile a debug version of v3.6-release\n- run `ctest -R imbuf_save` \n\nIt fails with the assert:\n```\nBLI_assert failed: source/blender/imbuf/intern/colormanagement.cc:2530, IMB_colormanagement_imbuf_for_write(), at '!(byte_output && linear_\nfloat_output)'\n```\n\n", "Incorrect Fresnel layer weight shading on backfacing geometry\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 470 Graphics ATI Technologies Inc. 4.5.13587 Core Profile Context 20.4.2 26.20.15029.27017\n\nBroken: version: 2.91.0 Alpha\n\nFresnel layer weight creates a sharp boundary instead of a smooth falloff when viewed on backfacing geometry.\nIn this example there are 2 hemispheres with the same material, but the left one has inverted face normals.\n\n\n[fresnel bug.blend](fresnel_bug.blend)\n", "Crash and assert hit when converting empty hair to mesh\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 512.78\n\nBroken: 3.5, 3.6\nWorked: never? (conversion for \"Curves\" is added in 3.5 release)\n\nCrash triggers when converting empty hair object to mesh due null pointer access and\nassert hit at `BLI_assert(mesh_src->id.tag & LIB_TAG_NO_MAIN)` and `BLI_assert(mesh_dst == ob->data)`\n\n- Open default scene\n- Select default cube and Add empty hair object\n- Convert to > Mesh\n\n```\n \tblender.exe!_BLI_assert_abort() Line 47\tC\n>\tblender.exe!BKE_mesh_nomain_to_mesh(Mesh * mesh_src, Mesh * mesh_dst, Object * ob) Line 1113\tC++\n \tblender.exe!object_convert_exec(bContext * C, wmOperator * op) Line 3397\tC++\n \tblender.exe!wm_operator_invoke(bContext * C, wmOperatorType * ot, const wmEvent * event, PointerRNA * properties, ReportList * reports, const bool poll_only, bool use_last_properties) Line 1539\tC++\n \tblender.exe!wm_operator_call_internal(bContext * C, wmOperatorType * ot, PointerRNA * properties, ReportList * reports, const wmOperatorCallContext context, const bool poll_only, const wmEvent * event) Line 1727\tC++\n \tblender.exe!WM_operator_name_call_ptr(bContext * C, wmOperatorType * ot, wmOperatorCallContext context, PointerRNA * properties, const wmEvent * event) Line 1776\tC++\n \tblender.exe!WM_operator_name_call_ptr_with_depends_on_cursor(bContext * C, wmOperatorType * ot, wmOperatorCallContext opcontext, PointerRNA * properties, const wmEvent * event, const char * drawstr) Line 1969\tC++\n \tblender.exe!ui_apply_but_funcs_after(bContext * C) Line 1029\tC++\n \tblender.exe!ui_popup_handler(bContext * C, const wmEvent * event, void * userdata) Line 11541\tC++\n \tblender.exe!wm_handler_ui_call(bContext * C, wmEventHandler_UI * handler, const wmEvent * event, const bool always_pass) Line 814\tC++\n \tblender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3305\tC++\n \tblender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3422\tC++\n \tblender.exe!wm_event_do_handlers(bContext * C) Line 4044\tC++\n \tblender.exe!WM_main(bContext * C) Line 649\tC\n \tblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 597\tC\n```\n\n", "Calling operator from handler that saves bmesh freezes blender forever\nBlender version: 3.5.1\n\nI setup some shader to run on top of blender viewport and connected it’s update to `SpaceView3D.draw_handler_add`. The idea was that shader will only work in EDIT mode and if user exists it then it will automatically trigger some operator.\nLine that freezes Blender is `bm.to_mesh(context.object.data)` although it doens’t freeze right away.\n\nWhat I’ve found that if I call operator that edits mesh from bmesh then it freezes Blender entirely.\nCurrently as a workaround I moved operator’s code to some function and call it instead of because `bm.to_mesh(context.object.data)` doesn’t seem to freeze Blender when it’s called from handler without operator.\n\n\nEasy way to reproduce (create default scene, make sure cube is selected, run the script):\n\n```python\nimport bpy\nfrom bpy.types import SpaceView3D\nimport bmesh\n\nclass TestHandler:\n installed = None\n\n @classmethod\n def install(cls, context):\n handler = cls()\n cls.installed = SpaceView3D.draw_handler_add(\n handler, (context, ), \"WINDOW\", \"POST_VIEW\"\n )\n\n @classmethod\n def uninstall(cls):\n try:\n SpaceView3D.draw_handler_remove(cls.installed, \"WINDOW\")\n except ValueError:\n pass\n cls.installed = None\n\n def __call__(self, context):\n obj = context.object\n if obj.mode != \"EDIT\":\n TestHandler.uninstall()\n bpy.ops.test.test()\n print('HANDLER CALL FINISHED') # never printed\n return\n \n print('HANDLER FINISHED')\n\nclass TestOperator(bpy.types.Operator):\n bl_idname = \"test.test\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST OPERATOR CALLED')\n bm = bmesh.new()\n\n # WITHOUT THIS LINE IT DOESN'T FREEZE\n bm.to_mesh(context.object.data)\n\n # still printed\n print('TEST OPERATOR FINISHED')\n return {\"FINISHED\"}\n \nclass TestSetupOperator(bpy.types.Operator):\n bl_idname = \"test.test_setup\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST SETUP OPERATOR CALLED')\n TestHandler.install(context)\n return {\"FINISHED\"}\n\n\nbpy.utils.register_class(TestOperator)\nbpy.utils.register_class(TestSetupOperator)\nbpy.ops.object.mode_set(mode=\"EDIT\")\nbpy.ops.test.test_setup()\n# freezes on the next step\nbpy.ops.object.mode_set(mode=\"OBJECT\")\n```\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\".", "Add support to tessellate 'ngons with holes' in mesh's validate() func? Much useful for importers (FBX, OBJ...)\n\n\n2.76\n\n fbx does not import NGON. But it imports into Modo.\nBlender:\n\n\nModo:\n\n\nFile:\n[exchange.fbx](exchange.fbx)\n\n\nimport fbx\n", "Bevel improvements for \"Correct Face Attributes\"\n@mano-wii recently made a new commit {4387aff99e01} for adjusting uv's during mesh transformation. After discussing with him and @ideasman42 I was asked to add a new task with suggestion for improvement to the bevel operator so that it works well with **correct face attributes** like mesh transform does. \n\n---\n**Relevant links**\n\n#78671 (Improvements to \"Correct Face Attributes\")\n\n---\n\nSettings for **correct face attributes** can be found in the top right corner of the 3d viewport.\n \n\n\n**Bevel - bevel edge(s) currently does not work with **Correct face attributes****\n\n[bevel does not correct uv.mp4](bevel_does_not_correct_uv.mp4)\n\n**Suggested behavior for bevel**\nStep 1 - selection\n\n\nStep 2 - bevel\nCreated face inherits uv coordinate from one face and then uv coordinates are corrected. UV overlap are expected in a lot of cases.\n\n" ]

[ "Assertion at bmesh_polygon.c:961 ... BM_face_is_normal_valid(f)\nDebian, git build, 3.3.0 alpha from 2022-06-26 (but my own branch).\n\nWhile the assertion handles with the 3d Print Toolbox addon, I am uncertain if this report belongs classified as addon related.\n\nTo reproduce, load attached blend, and click Check All (with a debug build that asserts()).\n\n*Note: The active object was created from another object in the scene, which uses a mask (and displace) modifier to generate it from a base object (also in the scene). Its modifiers were applied to create this final \"simple\" mesh, but the others are available for reference.\n\n```\nblenderd(BM_face_triangulate+0x8e) [0x4b90327]\nblenderd() [0x4cb55ce]\nblenderd(BM_mesh_triangulate+0x8c1) [0x4cb606b]\nblenderd(bmo_triangulate_exec+0xe3) [0x4c42844]\nblenderd(BMO_op_exec+0x71) [0x4b7a3ba]\nblenderd(BPy_BMO_call+0x2ff) [0x52b2937]\nblenderd(_PyObject_MakeTpCall+0x88) [0x10a3fea8]\nblenderd(_PyEval_EvalFrameDefault+0xa26e) [0x400ec3e]\nblenderd() [0x10afe534]\nblenderd(_PyEval_EvalFrameDefault+0x843a) [0x400ce0a]\nblenderd() [0x10afe534]\nblenderd(_PyEval_EvalFrameDefault+0x843a) [0x400ce0a]\nblenderd() [0x10afe534]\nblenderd(PyVectorcall_Call+0x5f) [0x10a3fb2f]\nblenderd() [0x529c836]\nblenderd() [0x5235060]\nblenderd() [0x49e1437]\nblenderd() [0x49e1a7a]\nblenderd(WM_operator_name_call_ptr+0x86) [0x49e1c73]\nblenderd(WM_operator_name_call_ptr_with_depends_on_cursor+0xd5) [0x49e221f]\nblenderd() [0x5d9a850]\nblenderd() [0x5db6d42]\nblenderd() [0x49df91f]\nblenderd() [0x49e586c]\nblenderd() [0x49e5dee]\nblenderd(wm_event_do_handlers+0x8dd) [0x49e7c13]\nblenderd(WM_main+0x30) [0x49d9037]\nblenderd() [0x400f768]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f6e77459d0a]\nblenderd(_start+0x2a) [0x400f17a]\nBLI_assert failed: source/blender/bmesh/intern/bmesh_polygon.c:961, BM_face_triangulate(), at 'BM_face_is_normal_valid(f)'\n```\n\n[mask-3dnormals.blend](mask-3dnormals.blend)\n\nAlternate example:\n- With 3d print toolbox enabled...\n- Load attached blend\n- Duplicate the selected object -- Has a Displace and Mirror modifier on it\n- Convert to mesh\n- 3d Print toolbox -> Check All\n[fff.blend](fff.blend)" ]

[ "Mesh selection in viewport broken with scenes using a high number of models\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 528.02\n\nBroken: version: 3.5.0 Alpha\nWorked: Never (2.8+)\nWe are working on a commercial project with imported SketchUp scenes using 55K+ models and running more and more into broken scenes with selection issues in the viewport.\n\n`What we figured out so far:`\n- Selection in the outliner works\n- Some models can be selected by a point and click\n- Other models can't be selected by a point and click\n- Models at a different location will be selected by a point and click and not at the mouse pointer location\n- Box select is messed up and doesn't work overall (selects just parts of the model or fails completely)\n- Lasso select seems to work as intended\n- Circle select seems to work as intended (but can freeze Blender)\n- Some random models can cause a hard crash of Blender when selecting them by a point and click\n**When we delete all my other scenes in the Blender file and purge the data the selection modes work again.**\n\n\n\n\n[T104008_Selection_Bug_350_v006_CUBES_REPORT.blend](T104008_Selection_Bug_350_v006_CUBES_REPORT.blend)\n\nTry to select cubes.\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", "OptiX denoiser creates dark artifacts in viewport when used with 2 GPUs\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.98\n\nBroken: version: 3.3.1\n\nThe OptiX denoiser creates several black sectors in the viewport. The smaller the area to be cleaned the more visible the error is.\nThis is only present when I have my 2 GPUs activated at the same time (3070 and 2060s). And it works normally when I enable only one of them.\n\n\n\n1. Activate both GPUs in preferences (OptiX or CUDA)\n2. Select Cycles render > GPU\n3. Activate viewport denoise and select OptiX.\n4. In viewport (Ctrl + B) set a small render region.\n[Based on the default startup]\n\n", "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", "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", "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)", "Blender 3.5 crash on render with Intel 4600 integrated GPU\nOperating system: WIndows 10 x64\nGraphics card: Intel 4600\n\nBroken: 3.5 \nWorked: 3.4.1\n\n\nBlender crashes when attempting to render in Evee. Cycles seems to work.\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>", "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)", "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", "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)", "Regression: Crash on deleting NLA strip in tweak mode\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.0, 3.6.0\nWorked: 2.93\n\nWhen using the 'Previous Layer' function of the Action Editor to tweak NLA strips, trying to delete a (green) strip in tweak mode crashes Blender.\n\n\n- Open `109430.blend`\n- In the NLA area, press X to delete the green strip.\n- Blender crashes\n\nOriginal/from fresh file:\n\n- In the default startup file, open 2 areas; a Dope Sheet set to Action Editor, and a Nonlinear Animation.\n- Keyframe any property of the default cube.\n- In the Action Editor, click Push Down on the newly created action.\n- Also in the Action Editor, click the 'Previous Layer' button (the small down arrow). This activates tweaking for the NLA strip.\n- In the NLA area, click the green strip so it's highlighted.\n- Press X to delete it. Blender crashes.\n\n", "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", "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)", "Cycles: GPU Optix kernel loading with Bevel/Ambient Node.\nXMGNEO17 Laptop AMD Ryzen9 5900HK Radion.\nOperating system: Windows 11 Home. 21H2\nGraphics card: Nvidia Geforce RTX 3080 Laptop GPU. 16 GB VRAM.\n\nBlender 3.2-3.4 show the error. Blender 3.1 and before not.\n\nThe error happens when ever an Ambient Occlusion or Bevel Node is used and connected in a shader and GPU option OPTIX is enabled for rendering in Cycles. It does not happen with CUDA or CPU.\nBlender will start render process and stops with the line: Preparing for rendering, this can take time.. etc. At that point the UI is still working, but will freeze after trying to cancel rendering. Blender can only be forced to shut down. Scene changes are lost. \n\nThe but is very simple to reproduce:\n1. Open Blender and apply a shader to the cube. \n2. Add a bevel/Ambient node to the shader and connect it to any input. Doesn't really matter which.\n3. Enable Optix in the preferences and set cycles as render. Make sure its set to use GPU.\n4. Switch viewport to preview render.\n5. Blende will stop preparing the scene and won't move further. Its UI is still reacting until trying to stop the process." ]

[ "Open Image Denoise Crash\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0 Alpha\n\nOpen Image Denoise Crashes Blender when switching input passes to Color only in render view.\n\n1.Open default cube scene\n2.use Cuda GPU+CPU\n3.Choose Cycles (supported) and GPU Compute\n4.Enable Denoise-Viewport-Open image denoise\n5.Go to rendered View\n6.Switch Input Passes from Color + Albedo to Color Only\n7.Crash\n\n" ]

[ "bpy.ops.object.transform_apply no working after physics simulation\nOperating system: Windows 10 Pro\nGraphics card: 2x Nvidia 1080 GTX\n\nBroken: 2.8, b46245470f79, 2018-04-18\nWorked: 2.7x\n\nWhen running a rigid body simulation, it is not currently possible to apply transformation to freeze a specific frame. If you start scrubbing in the timeline, the object either goes back to original position or jumps to random position that was generated during the simulation.\n\n - add a plane and add a passive rigid body\n - add a suzanne and add an active rigid body\n - run the simulation\n - choose a frame\n - select the suzanne object\n - apply transformation/apply visual transformation\n # scrub in the timeline\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "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", "Snap to Grid in Perspective View performed only at ground level\nGenerally you are not sure which grid point the object is in the perspective view because you need to consider the current depth of the object on the screen.\nThis option would only limit movement at ground level under those conditions.", "Some transform modes don't apply absolute grid snaping \nOperating system: Windows 10 \nGraphics card: GTX 1080 ti \n\nBroken:\nBlender 2.8 January 31, 01:48:40 - 8c8979067490 Beta\nBlender 2.79 (It worked)\nBlender 2.77 (It worked)\n\nAbsolut grid snaping dont work with \"Face Inset\" and neither with loop cuts. \n\nTurn on the snaping (increment) -> turn on absolut grid snaping -> spawn a plane -> try to snap while loop cutting or inseting faces.", "Cycles: Keyframing motion blur shutter value fails to apply it properly when generating animation\nOperating system: Windows 10\nGraphics card: Nvidia RTX 3090\n\nBroken: 3.6, 4.0\n\n\nIf we keyframe shutter property of motion blur, the updated shutter value is not considered during the final render.\nSuppose shutter value is 0 at the start of render, it will remain 0 thorught the animation even if we've keyframed the value.\n\n- Open attached file\n- select cycles render Engine\n- Start animation render (Ctrl-F12)\n", "Keyframing Stretch property in IK won't work properly - iTaSC Solver\nDoesn't work in all versions 2.79b, 2.83, 3.00\n\nWhen using iTaSC solver for an armature, you can't keyframe or use a driver for the bone stretch property. If you do it will be buggy and won't work as expected.\n\nThe Stretch property I'm talking about\n\n\n1. Make a a small armature with iTaSC Solver\n2. Add IK Bone Constraint\n3. Animate the stretch property whether in the bone constraint or the bone property\n4. Keyframe your rig and see that it's not behaving properly\n\n**note: I know it may seem incomprehensible but if you click constantly \"Update Dependencies\" in the drivers panel you will see the expected result**\n\n[Bug report.blend](Bug_report.blend)", "inconsistancy in runing script console vs editor, pose mode bones transformations.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 2.93.2\n\nthere is difference when running script from blender editor vs blender python console \n\n\n1. the example suppose to place bones from one armature (B) on another (A) while in pose mode.\n\n2. when running the script in editor mode the result is unpredictable and you can click few times and get different results.\n\n3. when copying the whole script and run it in the blender console its seem to work just fine. \n\n4. keep up the great work.\n\nTest File:\n{[F10327076](bone_to_bone_test03.zip)}[tests02_no_try.zip](https://archive.blender.org/developer/F10325225/tests02_no_try.zip)", "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", "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", "IK constraints that are disabled or have influence set to zero, result in jerky movement of the bones until the IK constraint or target are deleted.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.2 to 3.4 alpha\nWorked: not sure.\n\nPlease note there are no dependancy issues as all constraints are turned off. I've also updated the blend file so that there are no dependency issues even when the constraints are turned on.\n[boney bug.blend](boney_bug.blend)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[2022-08-23 20-55-41.mp4](2022-08-23_20-55-41.mp4)\n\n", "Bone chains frozen when using Auto IK and X-Axis Mirror\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\nWorked: Has happened for as long as I remember\n\nDisabling X-Axis Mirror while using Auto IK can cause a mirrored bone chain to become \"locked\" and not movable with Auto IK. \nThe \"locked\" bone will be highlighted in orange both when trying to move a child bone in the chain as well as moving a bone on the mirrored chain.\n\nSeems to be the same issue as #75810, even down to the same steps to reproduce\n\n| trying to move the locked chain | moving the mirrored chain |\n| -- | -- |\n|  |  |\n\nOpen the attached blend and enter pose mode, then:\n1. Select the `Arm.L` bone\n2. enable X-Axis Mirror\n3. Rotate the `Arm.L` bone slightly\n4. disable X-Axis Mirror\n5. Try grabbing the `Arm.R.002` bone and move it\nResult: bone chain is locked in place\n\n", "Bone Heat weighting: failed (due to none of the vertices in an island being visible to any bones)\n**Win 10 64. gtx 970**\n\n**Blender 2.75a Hash c27589e**\n\n**Bone Heat weighting: failed to find solution for one or more bones**\n\nI attach the blend file and two prints..\n\nAlso the same broblems apper when i try to \"assign automatic from bones\" by individual bones in Weight Paint. Like one by one. Please see print2.\n\n\n\n\n\n[cat.blend](cat.blend)\n", "Rigid body baked cache not invalidated\nOperating system: Windows 10 Pro 64-bit\nGraphics card: 4095MB NVIDIA GeForce GTX 1080 (NVIDIA)\n\nblender-2.80rc1-windows64\nWorked: (optional)\n\nSimple physics object is trapped in previous (deleted) animated properties.\n\nI have included a blend file which consist of just a cube with physics properties added.\nIt is supposed to fall but it moves to the origin and stays there.\nThe file is a working file from which everything has been deleted and a cube added.\nRun the animation and the cube will behave oddly.\nIf the cube is deleted and a different mesh added, say a sphere and moved and basic physics assigned. It will do the same.\nThis is likely to be a problem with my file from which everything has been deleted??\n[physics-problem.blend](physics-problem.blend)", "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", "Crash when deleting one rigidbody from constraint during simulation\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 3080 Laptop GPU\n\nBroken: master branch\nWorked: Don't know if it ever worked\n\nDeleting one rigidbody that is part of a constraint during simulation causes a crash.\n\n**Steps to Reproduce**\n- Add two cubes to a scene. Add a rigidbody to both cubes.\n- Add an empty object to the scene. Add a fixed rigidbody constraint to the cube. Set the cubes as the first and second object in the constraint.\n- Play the simulation for a few frames and then pause the simulation.\n- Delete either cube, then continue playing the simulation.\n- Crash" ]

[ "Blender stales when changing the ghosting range\nWindows 10\nIntel HD 4600\n\nBroken: dd0de53\nWorked: (optional)\n\nBlender stales when changing the ghosting range.\nI also tried testing the bug with a debug build however, it did not give any information on the source of the bug.\n\n- Add an armature\n- Animate it (2 frames)\n- Ghost --> and entering a range value Range value will cause the Freeze\n" ]

[ "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "unable to use 'grid fill' or 'fill' on screwed object\nOperating system: Window 10\nGraphics card: NVIDIA GeForce RTX 2060 SUPER\n\nBroken: Blender 2.83\nWorked: Blender 2.76 \n\n\nI am trying to create a solid spring using Screw modifier. After applied grid fill, I expected a full capped end of the screwed object, but it turns out to be like figure below. The complete file also attached in this post. Hope to get your response soon. \n\n[screw.blend](screw.blend)\n\nBased on the default startup or an attached .blend file (as simple as possible).", "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", "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", "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.", "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", "Blender becomes unstable/crashes after using \"Reload Scripts\" if using any \"ShaderNodeCustomGroup\" nodes.\nOperating system: Windows 10\nGraphics card: NVIDIA\n\nBroken: 2.81\n\nIf you manipulate a \"ShaderNodeCustomGroup\" node after having used the \"Reload Scripts\" operator (F8) Blender will become unstable.\n\nAttached is a small addon that implements a minimal custom node group.\n1. Enable the addon and switch to the shader editor.\n2. Create the custom node (Add->Test Category->TestNodeCustomGroup)\n3. Trigger 'Reload Scripts' (F8 key).\n4. Adjust the color input of the custom node.\n5. Repeat steps 3/4 until you crash (usually crashes on first or second try for me)\n[node_custom_test.py](node_custom_test.py)", "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", "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", "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 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", "Blender 2.8 UI designs (parent task)\nThis is a parent task for all the confirmed UI tasks for Blender 2.8. We are targeting these changes for Blender 2.80. Other UI and tools updates can be added for future releases.\n\nThis list serves as a reference for developers, and is especially important for after the Code Quest has ended. These items are grouped by topic here:\n\n### Tools\n - #55036 Tool System Todo\n - #54858 Command Settings Cleanup\n - #55043 Tool Settings Editor\n - #54885 2.8 UI Tools: Toolbar Ordering\n - #54582 2.8 UI Tools: Tools Design\n - #55039 2.8 UI Tools: Tool Tweaking UI\n - #55027 2.8 UI Tools: Favourites Bar / Specials Menu Design\n - #54950 3D Cursor Design\n - #55386 2.8 UI Tools: Top Bar, Tool Properties & Toolbar Update\n - #54661 Tools Manipulators design\n\n### Asset Manager\n - #54642 Asset Manager UI\n\n### Keymaps\n - (Todo) Input Device-Agnostic Keymap\n - #55162 Blender Default Keymap Changes\n - #54963 Industry Compatible Keymap\n\n### Viewport\n - #54723 Viewport Manipulator Design\n - #54908 Workbench & Shading UI design\n\n### Addons\n - #55407 2.8: Addons UI\n\n### Outliner & Collections\n - #54707 Outliner Collections Interaction Design\n\n### Status Bar\n - #54861 Status Bar Design\n\n### Properties Editor\n - #54951 Properties Editor Design\n - #54862 Multi-Object Properties Editing\n\n### Top Bar & Workspaces\n - (Todo) Workspaces & Mode design\n\n### Default User Experience\n - #54943 Blender 2.8 Defaults\n - #54943 Default Theme\n\n### Other\n - #55353 Multi-Object Edit Mode/Pose Mode/Sculpt Mode UI\n - #54989 FaceMaps Phase 1: bone selection & bone display", "Blender 3.5 and 3.5.1 are crashing while using Metal as backend\nOperating system: macOS 12.6.3\nGraphics card: Radeon Pro 580 8GB\n\nBroken: 3.50, 3.51 (Metall Backend)\nWorked: 3.50, 3.51 (OpenGL Backend)\n\nBlender simply hang. I use eevee, if you switch to rendered viewport shading it crashed complete system. I use Metall as backend, if I choose OpenGL it works fine. \n\n \nI attached an .blend file for example.\n\n", "Crash while switching to edit mode with EEVEE + Geometry Nodes\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.0.0\n\nWhen switching to edit mode in while the viewport's set to render it crashes (see attached video)\n[blender crash 2021-12-17 21-54-00.mp4](blender_crash_2021-12-17_21-54-00.mp4)\n\n1 load the attached file\n2 switch to rendered view in the viewport\n3 switch to edit vertex mode\n4 that's a crash!\n\n[transitions_001_blender3.blend](transitions_001_blender3.blend)", "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)" ]

[ "blender 2.80 Alpha crash report\nwindows 10 and Radeon HD 6450\n\nBroken: 2.80 Alpha\n\n**Crash Report**\n\n**Sculpt mode** *Dyntopo* > constant detail sample mesh detail on click point CRASH\n\n\n\n\n", "Sculpt mode-dyntopo (constant detail mode) crash.\nWindows 10 64bit, nvidia gtx 980ti\n\nBroken: 2.8 alpha\nWorked: 2.79\n\nIn sculpt mode with dyntopo on (detailing mode: constant detail), blender crashes when using the eyedropper tool (sample mesh detail on clicked point)\n\nable to reproduce on the default startup file with the default cube\n", "2.8 Alpha Crash at using \"Sample the mesh detail at click point\" in sculpt mode, Dynatopo, Constant Detail.\nOS: Windows 10 Pro\nGPU: NVidia GTX 1070 Ti\n\n2.8 alpha, 98d2055)\n\n\nCrash at using \"Sample the mesh detail at click point\" in sculpt mode, Dynatopo, Constant Detail.\n\n", "Dyntopo Resolution Sampler\nWindows 10\nGtx 1080ti\nGtx 1070\n\n\nBroken: 2.80 0e8bd6ba8a2\n\n\nBlender crashes in sculpt mode, using Dyntopo in constant detail mode when use the picker for take a resolution sample\n\n- Enter in sculpt mode\n- Activate dyntopo\n- change to Constant Detail in (detailing)\n- use the picker to take a sample of the resolution of the mesh\n\n", "Dyntopo, picking resolution for constant detail crash\nWindows 8.1\n\nrenderer:\t'GeForce GTX 770/PCIe/SSE2'\nvendor:\t\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 398.36'\n\n\nversion: 2.80 (sub 20), branch: blender2.8, commit date: 2018-07-12 19:43, hash: 6f8a141, type: Release\nbuild date: Fri 07/13/2018, 04:29 AM\n\n\nCrash when using eydropper tool with dyntopo enabled while picking resolution for constant detail.\n\nGo into sculpt mode and enable dyntopo, then use \"constant detail\" and use the eyedropper tool = Crash\n", "Blender 2.8 dyntopo mesh crash\nWindows 10 64-bit, intel hd 4400, i3 4005U.\n\nBlender 2.8 \nSculpting mode, dyntopo crash mesh\n\nwhen going into sculpting mode and turning on dyntopo options. This is when I start sculpturing my model, it suddenly breaks, but only when I'm in the carving mode. After entering the grid editing mode, everything is ok.\n\n", "Sample detail (dyntopo) crash\nKubuntu 18.04 + GeForce 930M\n\n2.80 alpha 2 build 13th Aug 2018\n(blender-2.80-0e8bd6ba8a2-linux-glibc219-x86_64)\n\nCrash on sample detail (dyntopo)\n\n1. create / append a mesh\n2. enter sculpt mode\n3. select brush\n4. enable dyntopo\n5. change method to \"CONSTANT DETAIL\"\n6. click sample detail on Resolution.\n7. crash\n\nworks on any mesh.\n", "Crash when trying to use the eyedropper in the dyntopo to get current mesh res.\n****\n# Blender 2.80 (sub 20) System Information\n****\n\n\nBlender:\n****\n\nversion: 2.80 (sub 20), branch: blender2.8, commit date: 2018-07-04 17:33, hash: 53c63db2ee1, type: Release\nbuild date: 2018-07-05, 01:23:30\nplatform: Linux\nbinary path: '/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/blender'\nbuild cflags: -Wall -Wcast-align -Werror=implicit-function-declaration -Werror=return-type -Werror=vla -Wstrict-prototypes -Wmissing-prototypes -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wlogical-op -Wundef -Winit-self -Wnonnull -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wformat-signedness -Wrestrict -Wuninitialized -Wredundant-decls -Wshadow -Wno-error=unused-but-set-variable -Wimplicit-fallthrough=5 -fuse-ld=gold -std=gnu11 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing -msse2\nbuild cxxflags: -Wredundant-decls -Wall -Wno-invalid-offsetof -Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Werror=return-type -Werror=implicit-function-declaration -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wunused-parameter -Wwrite-strings -Wundef -Wformat-signedness -Wrestrict -Wuninitialized -Wundef -Wmissing-declarations -Wimplicit-fallthrough=5 -fuse-ld=gold -std=c++11 -msse -pipe -fPIC -funsigned-char -fno-strict-aliasing -msse2\nbuild linkflags: -Wl,--version-script='/home/sources/buildbot-x86_64-slave/linux_glibc219_x86_64_cmake/blender.git/source/creator/blender.map'\nbuild system: CMake\n\nPython:\n****\n\nversion: 3.6.2 (default, Sep 21 2017, 13:57:40) \n[GCC 7.2.0]\npaths:\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons_contrib'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/startup'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python/lib/python36.zip'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python/lib/python3.6'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python/lib/python3.6/lib-dynload'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python/lib/python3.6/site-packages'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/freestyle/modules'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/modules'\n\t'/home/Barracuda/.config/blender/2.80/scripts/addons/modules'\n\nPython (External Binary):\n****\n\nbinary path: '/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/python/bin/python3.6m'\nversion: Python 3.6.2\n\nDirectories:\n****\n\nscripts:\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/modules'\n\t'/opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts'\nuser scripts: '/home/Barracuda/.config/blender/2.80/scripts'\npref scripts: None\ndatafiles: '/home/Barracuda/.config/blender/2.80/datafiles/'\nconfig: '/home/Barracuda/.config/blender/2.80/config/'\nscripts : '/home/Barracuda/.config/blender/2.80/scripts/'\nautosave: '/home/Barracuda/.config/blender/2.80/autosave/'\ntempdir: '/tmp/blender_x59G4W/'\n\nFFmpeg:\n****\n\navcodec: '57, 64, 101'\navdevice: '57, 1, 100'\navformat: '57, 56, 100'\navutil: '55, 34, 100'\nswscale: ' 4, 2, 100'\n\nSDL:\n****\n\nVersion: Unknown\nLoading method: dynamically loaded by Blender (WITH_SDL_DYNLOAD=ON)\nWARNING: Blender could not load SDL library\n\nOther Libraries:\n****\n\nOpenColorIO: 1, 0, 9\nOpenImageIO: 1, 7, 15\nOpenShadingLanguage: 1, 7, 5\nOpenSubdiv: 3, 1, 1\nOpenVDB: 3, 1, 0\nAlembic: 1, 7, 1\n\nOpenGL:\n****\n\nrenderer:\t'GeForce GTX 1080/PCIe/SSE2'\nvendor:\t\t'NVIDIA Corporation'\nversion:\t'4.5.0 NVIDIA 390.67'\nextensions:\n\tGL_AMD_multi_draw_indirect\n\tGL_AMD_seamless_cubemap_per_texture\n\tGL_AMD_vertex_shader_layer\n\tGL_AMD_vertex_shader_viewport_index\n\tGL_ARB_ES2_compatibility\n\tGL_ARB_ES3_1_compatibility\n\tGL_ARB_ES3_2_compatibility\n\tGL_ARB_ES3_compatibility\n\tGL_ARB_arrays_of_arrays\n\tGL_ARB_base_instance\n\tGL_ARB_bindless_texture\n\tGL_ARB_blend_func_extended\n\tGL_ARB_buffer_storage\n\tGL_ARB_clear_buffer_object\n\tGL_ARB_clear_texture\n\tGL_ARB_clip_control\n\tGL_ARB_color_buffer_float\n\tGL_ARB_compressed_texture_pixel_storage\n\tGL_ARB_compute_shader\n\tGL_ARB_compute_variable_group_size\n\tGL_ARB_conditional_render_inverted\n\tGL_ARB_conservative_depth\n\tGL_ARB_copy_buffer\n\tGL_ARB_copy_image\n\tGL_ARB_cull_distance\n\tGL_ARB_debug_output\n\tGL_ARB_depth_buffer_float\n\tGL_ARB_depth_clamp\n\tGL_ARB_depth_texture\n\tGL_ARB_derivative_control\n\tGL_ARB_direct_state_access\n\tGL_ARB_draw_buffers\n\tGL_ARB_draw_buffers_blend\n\tGL_ARB_draw_elements_base_vertex\n\tGL_ARB_draw_indirect\n\tGL_ARB_draw_instanced\n\tGL_ARB_enhanced_layouts\n\tGL_ARB_explicit_attrib_location\n\tGL_ARB_explicit_uniform_location\n\tGL_ARB_fragment_coord_conventions\n\tGL_ARB_fragment_layer_viewport\n\tGL_ARB_fragment_program\n\tGL_ARB_fragment_program_shadow\n\tGL_ARB_fragment_shader\n\tGL_ARB_fragment_shader_interlock\n\tGL_ARB_framebuffer_no_attachments\n\tGL_ARB_framebuffer_object\n\tGL_ARB_framebuffer_sRGB\n\tGL_ARB_geometry_shader4\n\tGL_ARB_get_program_binary\n\tGL_ARB_get_texture_sub_image\n\tGL_ARB_gl_spirv\n\tGL_ARB_gpu_shader5\n\tGL_ARB_gpu_shader_fp64\n\tGL_ARB_gpu_shader_int64\n\tGL_ARB_half_float_pixel\n\tGL_ARB_half_float_vertex\n\tGL_ARB_imaging\n\tGL_ARB_indirect_parameters\n\tGL_ARB_instanced_arrays\n\tGL_ARB_internalformat_query\n\tGL_ARB_internalformat_query2\n\tGL_ARB_invalidate_subdata\n\tGL_ARB_map_buffer_alignment\n\tGL_ARB_map_buffer_range\n\tGL_ARB_multi_bind\n\tGL_ARB_multi_draw_indirect\n\tGL_ARB_multisample\n\tGL_ARB_multitexture\n\tGL_ARB_occlusion_query\n\tGL_ARB_occlusion_query2\n\tGL_ARB_parallel_shader_compile\n\tGL_ARB_pipeline_statistics_query\n\tGL_ARB_pixel_buffer_object\n\tGL_ARB_point_parameters\n\tGL_ARB_point_sprite\n\tGL_ARB_polygon_offset_clamp\n\tGL_ARB_post_depth_coverage\n\tGL_ARB_program_interface_query\n\tGL_ARB_provoking_vertex\n\tGL_ARB_query_buffer_object\n\tGL_ARB_robust_buffer_access_behavior\n\tGL_ARB_robustness\n\tGL_ARB_sample_locations\n\tGL_ARB_sample_shading\n\tGL_ARB_sampler_objects\n\tGL_ARB_seamless_cube_map\n\tGL_ARB_seamless_cubemap_per_texture\n\tGL_ARB_separate_shader_objects\n\tGL_ARB_shader_atomic_counter_ops\n\tGL_ARB_shader_atomic_counters\n\tGL_ARB_shader_ballot\n\tGL_ARB_shader_bit_encoding\n\tGL_ARB_shader_clock\n\tGL_ARB_shader_draw_parameters\n\tGL_ARB_shader_group_vote\n\tGL_ARB_shader_image_load_store\n\tGL_ARB_shader_image_size\n\tGL_ARB_shader_objects\n\tGL_ARB_shader_precision\n\tGL_ARB_shader_storage_buffer_object\n\tGL_ARB_shader_subroutine\n\tGL_ARB_shader_texture_image_samples\n\tGL_ARB_shader_texture_lod\n\tGL_ARB_shader_viewport_layer_array\n\tGL_ARB_shading_language_100\n\tGL_ARB_shading_language_420pack\n\tGL_ARB_shading_language_include\n\tGL_ARB_shading_language_packing\n\tGL_ARB_shadow\n\tGL_ARB_sparse_buffer\n\tGL_ARB_sparse_texture\n\tGL_ARB_sparse_texture2\n\tGL_ARB_sparse_texture_clamp\n\tGL_ARB_spirv_extensions\n\tGL_ARB_stencil_texturing\n\tGL_ARB_sync\n\tGL_ARB_tessellation_shader\n\tGL_ARB_texture_barrier\n\tGL_ARB_texture_border_clamp\n\tGL_ARB_texture_buffer_object\n\tGL_ARB_texture_buffer_object_rgb32\n\tGL_ARB_texture_buffer_range\n\tGL_ARB_texture_compression\n\tGL_ARB_texture_compression_bptc\n\tGL_ARB_texture_compression_rgtc\n\tGL_ARB_texture_cube_map\n\tGL_ARB_texture_cube_map_array\n\tGL_ARB_texture_env_add\n\tGL_ARB_texture_env_combine\n\tGL_ARB_texture_env_crossbar\n\tGL_ARB_texture_env_dot3\n\tGL_ARB_texture_filter_anisotropic\n\tGL_ARB_texture_filter_minmax\n\tGL_ARB_texture_float\n\tGL_ARB_texture_gather\n\tGL_ARB_texture_mirror_clamp_to_edge\n\tGL_ARB_texture_mirrored_repeat\n\tGL_ARB_texture_multisample\n\tGL_ARB_texture_non_power_of_two\n\tGL_ARB_texture_query_levels\n\tGL_ARB_texture_query_lod\n\tGL_ARB_texture_rectangle\n\tGL_ARB_texture_rg\n\tGL_ARB_texture_rgb10_a2ui\n\tGL_ARB_texture_stencil8\n\tGL_ARB_texture_storage\n\tGL_ARB_texture_storage_multisample\n\tGL_ARB_texture_swizzle\n\tGL_ARB_texture_view\n\tGL_ARB_timer_query\n\tGL_ARB_transform_feedback2\n\tGL_ARB_transform_feedback3\n\tGL_ARB_transform_feedback_instanced\n\tGL_ARB_transform_feedback_overflow_query\n\tGL_ARB_transpose_matrix\n\tGL_ARB_uniform_buffer_object\n\tGL_ARB_vertex_array_bgra\n\tGL_ARB_vertex_array_object\n\tGL_ARB_vertex_attrib_64bit\n\tGL_ARB_vertex_attrib_binding\n\tGL_ARB_vertex_buffer_object\n\tGL_ARB_vertex_program\n\tGL_ARB_vertex_shader\n\tGL_ARB_vertex_type_10f_11f_11f_rev\n\tGL_ARB_vertex_type_2_10_10_10_rev\n\tGL_ARB_viewport_array\n\tGL_ARB_window_pos\n\tGL_ATI_draw_buffers\n\tGL_ATI_texture_float\n\tGL_ATI_texture_mirror_once\n\tGL_EXTX_framebuffer_mixed_formats\n\tGL_EXT_Cg_shader\n\tGL_EXT_abgr\n\tGL_EXT_bgra\n\tGL_EXT_bindable_uniform\n\tGL_EXT_blend_color\n\tGL_EXT_blend_equation_separate\n\tGL_EXT_blend_func_separate\n\tGL_EXT_blend_minmax\n\tGL_EXT_blend_subtract\n\tGL_EXT_compiled_vertex_array\n\tGL_EXT_depth_bounds_test\n\tGL_EXT_direct_state_access\n\tGL_EXT_draw_buffers2\n\tGL_EXT_draw_instanced\n\tGL_EXT_draw_range_elements\n\tGL_EXT_fog_coord\n\tGL_EXT_framebuffer_blit\n\tGL_EXT_framebuffer_multisample\n\tGL_EXT_framebuffer_multisample_blit_scaled\n\tGL_EXT_framebuffer_object\n\tGL_EXT_framebuffer_sRGB\n\tGL_EXT_geometry_shader4\n\tGL_EXT_gpu_program_parameters\n\tGL_EXT_gpu_shader4\n\tGL_EXT_import_sync_object\n\tGL_EXT_memory_object\n\tGL_EXT_memory_object_fd\n\tGL_EXT_multi_draw_arrays\n\tGL_EXT_packed_depth_stencil\n\tGL_EXT_packed_float\n\tGL_EXT_packed_pixels\n\tGL_EXT_pixel_buffer_object\n\tGL_EXT_point_parameters\n\tGL_EXT_polygon_offset_clamp\n\tGL_EXT_post_depth_coverage\n\tGL_EXT_provoking_vertex\n\tGL_EXT_raster_multisample\n\tGL_EXT_rescale_normal\n\tGL_EXT_secondary_color\n\tGL_EXT_semaphore\n\tGL_EXT_semaphore_fd\n\tGL_EXT_separate_shader_objects\n\tGL_EXT_separate_specular_color\n\tGL_EXT_shader_image_load_formatted\n\tGL_EXT_shader_image_load_store\n\tGL_EXT_shader_integer_mix\n\tGL_EXT_shadow_funcs\n\tGL_EXT_sparse_texture2\n\tGL_EXT_stencil_two_side\n\tGL_EXT_stencil_wrap\n\tGL_EXT_texture3D\n\tGL_EXT_texture_array\n\tGL_EXT_texture_buffer_object\n\tGL_EXT_texture_compression_dxt1\n\tGL_EXT_texture_compression_latc\n\tGL_EXT_texture_compression_rgtc\n\tGL_EXT_texture_compression_s3tc\n\tGL_EXT_texture_cube_map\n\tGL_EXT_texture_edge_clamp\n\tGL_EXT_texture_env_add\n\tGL_EXT_texture_env_combine\n\tGL_EXT_texture_env_dot3\n\tGL_EXT_texture_filter_anisotropic\n\tGL_EXT_texture_filter_minmax\n\tGL_EXT_texture_integer\n\tGL_EXT_texture_lod\n\tGL_EXT_texture_lod_bias\n\tGL_EXT_texture_mirror_clamp\n\tGL_EXT_texture_object\n\tGL_EXT_texture_sRGB\n\tGL_EXT_texture_sRGB_decode\n\tGL_EXT_texture_shared_exponent\n\tGL_EXT_texture_storage\n\tGL_EXT_texture_swizzle\n\tGL_EXT_timer_query\n\tGL_EXT_transform_feedback2\n\tGL_EXT_vertex_array\n\tGL_EXT_vertex_array_bgra\n\tGL_EXT_vertex_attrib_64bit\n\tGL_EXT_window_rectangles\n\tGL_EXT_x11_sync_object\n\tGL_IBM_rasterpos_clip\n\tGL_IBM_texture_mirrored_repeat\n\tGL_KHR_blend_equation_advanced\n\tGL_KHR_blend_equation_advanced_coherent\n\tGL_KHR_context_flush_control\n\tGL_KHR_debug\n\tGL_KHR_no_error\n\tGL_KHR_parallel_shader_compile\n\tGL_KHR_robust_buffer_access_behavior\n\tGL_KHR_robustness\n\tGL_KTX_buffer_region\n\tGL_NVX_blend_equation_advanced_multi_draw_buffers\n\tGL_NVX_conditional_render\n\tGL_NVX_gpu_memory_info\n\tGL_NVX_nvenc_interop\n\tGL_NV_ES1_1_compatibility\n\tGL_NV_ES3_1_compatibility\n\tGL_NV_alpha_to_coverage_dither_control\n\tGL_NV_bindless_multi_draw_indirect\n\tGL_NV_bindless_multi_draw_indirect_count\n\tGL_NV_bindless_texture\n\tGL_NV_blend_equation_advanced\n\tGL_NV_blend_equation_advanced_coherent\n\tGL_NV_blend_minmax_factor\n\tGL_NV_blend_square\n\tGL_NV_clip_space_w_scaling\n\tGL_NV_command_list\n\tGL_NV_compute_program5\n\tGL_NV_conditional_render\n\tGL_NV_conservative_raster\n\tGL_NV_conservative_raster_dilate\n\tGL_NV_conservative_raster_pre_snap_triangles\n\tGL_NV_copy_depth_to_color\n\tGL_NV_copy_image\n\tGL_NV_depth_buffer_float\n\tGL_NV_depth_clamp\n\tGL_NV_draw_texture\n\tGL_NV_draw_vulkan_image\n\tGL_NV_explicit_multisample\n\tGL_NV_fence\n\tGL_NV_fill_rectangle\n\tGL_NV_float_buffer\n\tGL_NV_fog_distance\n\tGL_NV_fragment_coverage_to_color\n\tGL_NV_fragment_program\n\tGL_NV_fragment_program2\n\tGL_NV_fragment_program_option\n\tGL_NV_fragment_shader_interlock\n\tGL_NV_framebuffer_mixed_samples\n\tGL_NV_framebuffer_multisample_coverage\n\tGL_NV_geometry_shader4\n\tGL_NV_geometry_shader_passthrough\n\tGL_NV_gpu_program4\n\tGL_NV_gpu_program4_1\n\tGL_NV_gpu_program5\n\tGL_NV_gpu_program5_mem_extended\n\tGL_NV_gpu_program_fp64\n\tGL_NV_gpu_shader5\n\tGL_NV_half_float\n\tGL_NV_internalformat_sample_query\n\tGL_NV_light_max_exponent\n\tGL_NV_multisample_coverage\n\tGL_NV_multisample_filter_hint\n\tGL_NV_occlusion_query\n\tGL_NV_packed_depth_stencil\n\tGL_NV_parameter_buffer_object\n\tGL_NV_parameter_buffer_object2\n\tGL_NV_path_rendering\n\tGL_NV_path_rendering_shared_edge\n\tGL_NV_pixel_data_range\n\tGL_NV_point_sprite\n\tGL_NV_primitive_restart\n\tGL_NV_query_resource\n\tGL_NV_query_resource_tag\n\tGL_NV_register_combiners\n\tGL_NV_register_combiners2\n\tGL_NV_robustness_video_memory_purge\n\tGL_NV_sample_locations\n\tGL_NV_sample_mask_override_coverage\n\tGL_NV_shader_atomic_counters\n\tGL_NV_shader_atomic_float\n\tGL_NV_shader_atomic_float64\n\tGL_NV_shader_atomic_fp16_vector\n\tGL_NV_shader_atomic_int64\n\tGL_NV_shader_buffer_load\n\tGL_NV_shader_storage_buffer_object\n\tGL_NV_shader_thread_group\n\tGL_NV_shader_thread_shuffle\n\tGL_NV_stereo_view_rendering\n\tGL_NV_texgen_reflection\n\tGL_NV_texture_barrier\n\tGL_NV_texture_compression_vtc\n\tGL_NV_texture_env_combine4\n\tGL_NV_texture_multisample\n\tGL_NV_texture_rectangle\n\tGL_NV_texture_rectangle_compressed\n\tGL_NV_texture_shader\n\tGL_NV_texture_shader2\n\tGL_NV_texture_shader3\n\tGL_NV_transform_feedback\n\tGL_NV_transform_feedback2\n\tGL_NV_uniform_buffer_unified_memory\n\tGL_NV_vdpau_interop\n\tGL_NV_vertex_array_range\n\tGL_NV_vertex_array_range2\n\tGL_NV_vertex_attrib_integer_64bit\n\tGL_NV_vertex_buffer_unified_memory\n\tGL_NV_vertex_program\n\tGL_NV_vertex_program1_1\n\tGL_NV_vertex_program2\n\tGL_NV_vertex_program2_option\n\tGL_NV_vertex_program3\n\tGL_NV_viewport_array2\n\tGL_NV_viewport_swizzle\n\tGL_S3_s3tc\n\tGL_SGIS_generate_mipmap\n\tGL_SGIS_texture_lod\n\tGL_SGIX_depth_texture\n\tGL_SGIX_shadow\n\tGL_SUN_slice_accum\n\nImplementation Dependent OpenGL Limits:\n****\n\nMaximum DrawElements Vertices:\t1048576\nMaximum DrawElements Indices:\t1048576\n\nGLSL:\nMaximum Varying Floats:\t124\nMaximum Vertex Attributes:\t16\nMaximum Vertex Uniform Components:\t4096\nMaximum Fragment Uniform Components:\t4096\nMaximum Vertex Image Units:\t32\nMaximum Fragment Image Units:\t32\nMaximum Pipeline Image Units:\t192\n\nCycles:\n****\n\nCPU device capabilities: SSE2 SSE3 SSE41 AVX AVX2\n\nOpenCL device capabilities:\nNumber of platforms: 1\nPlatform #0\n\tPlatform Name: NVIDIA CUDA\n\tPlatform Vendor: NVIDIA Corporation\n\tPlatform Version: OpenCL 1.2 CUDA 9.1.84\n\tPlatform Profile: FULL_PROFILE\n\tPlatform Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer\n\tNumber of devices: 1\n\t\tDevice: #0\n\t\t\tDevice Name: GeForce GTX 1080\n\t\t\tDevice Vendor: NVIDIA Corporation\n\t\t\tDevice OpenCL C Version: OpenCL C 1.2 \n\t\t\tDevice Profile: FULL_PROFILE\n\t\t\tDevice Version: OpenCL 1.2 CUDA\n\t\t\tDevice Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer\n\nCUDA device capabilities:\n\tGeForce GTX 1080\n\t\tCU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_BLOCK\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_X\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Y\t\t\t1024\n\t\tCU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Z\t\t\t64\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_X\t\t\t2147483647\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Y\t\t\t65535\n\t\tCU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Z\t\t\t65535\n\t\tCU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_BLOCK\t\t\t49152\n\t\tCU_DEVICE_ATTRIBUTE_SHARED_MEMORY_PER_BLOCK\t\t\t49152\n\t\tCU_DEVICE_ATTRIBUTE_TOTAL_CONSTANT_MEMORY\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_WARP_SIZE\t\t\t32\n\t\tCU_DEVICE_ATTRIBUTE_MAX_PITCH\t\t\t2147483647\n\t\tCU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_BLOCK\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_REGISTERS_PER_BLOCK\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_CLOCK_RATE\t\t\t1771500\n\t\tCU_DEVICE_ATTRIBUTE_TEXTURE_ALIGNMENT\t\t\t512\n\t\tCU_DEVICE_ATTRIBUTE_GPU_OVERLAP\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MULTIPROCESSOR_COUNT\t\t\t20\n\t\tCU_DEVICE_ATTRIBUTE_KERNEL_EXEC_TIMEOUT\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_INTEGRATED\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_MODE\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_HEIGHT\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_NUMSLICES\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_SURFACE_ALIGNMENT\t\t\t512\n\t\tCU_DEVICE_ATTRIBUTE_CONCURRENT_KERNELS\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_ECC_ENABLED\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_TCC_DRIVER\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MEMORY_CLOCK_RATE\t\t\t5005000\n\t\tCU_DEVICE_ATTRIBUTE_GLOBAL_MEMORY_BUS_WIDTH\t\t\t256\n\t\tCU_DEVICE_ATTRIBUTE_L2_CACHE_SIZE\t\t\t2097152\n\t\tCU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_MULTIPROCESSOR\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_ASYNC_ENGINE_COUNT\t\t\t2\n\t\tCU_DEVICE_ATTRIBUTE_UNIFIED_ADDRESSING\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_CAN_TEX2D_GATHER\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH_ALTERNATE\t\t\t8192\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT_ALTERNATE\t\t\t8192\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH_ALTERNATE\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_TEXTURE_PITCH_ALIGNMENT\t\t\t32\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_LAYERS\t\t\t2046\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_HEIGHT\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_HEIGHT\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_DEPTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_LAYERS\t\t\t2048\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_LAYERS\t\t\t2046\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LINEAR_WIDTH\t\t\t134217728\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_WIDTH\t\t\t131072\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_HEIGHT\t\t\t65000\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_PITCH\t\t\t2097120\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_WIDTH\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_HEIGHT\t\t\t32768\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MAJOR\t\t\t6\n\t\tCU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MINOR\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_MIPMAPPED_WIDTH\t\t\t16384\n\t\tCU_DEVICE_ATTRIBUTE_STREAM_PRIORITIES_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_GLOBAL_L1_CACHE_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_LOCAL_L1_CACHE_SUPPORTED\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_MULTIPROCESSOR\t\t\t98304\n\t\tCU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_MULTIPROCESSOR\t\t\t65536\n\t\tCU_DEVICE_ATTRIBUTE_MANAGED_MEMORY\t\t\t1\n\t\tCU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD\t\t\t0\n\t\tCU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD_GROUP_ID\t\t\t0\n\n\nEnabled add-ons:\n****\n\nio_scene_3ds (version: UNKNOWN, path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_scene_3ds/__init__.py)\nio_scene_fbx (version: (3, 9, 1), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_scene_fbx/__init__.py)\nio_anim_bvh (version: UNKNOWN, path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_anim_bvh/__init__.py)\nio_mesh_ply (version: UNKNOWN, path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_mesh_ply/__init__.py)\nio_scene_obj (version: (2, 3, 6), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_scene_obj/__init__.py)\nio_scene_x3d (version: (1, 2, 0), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_scene_x3d/__init__.py)\nio_mesh_stl (version: (1, 1, 2), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_mesh_stl/__init__.py)\nio_mesh_uv_layout (version: (1, 1, 1), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_mesh_uv_layout/__init__.py)\nio_curve_svg (version: UNKNOWN, path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/io_curve_svg/__init__.py)\ncycles (version: UNKNOWN, path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/cycles/__init__.py)\nspace_view3d_pie_menus (version: (1, 1, 8), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/space_view3d_pie_menus/__init__.py)\npie_menus_official (version: (1, 1, 5), path: /opt/blender-2.80-53c63db2ee1-linux-glibc219-x86_64/2.80/scripts/addons/pie_menus_official/__init__.py)\n\nCrash when trying to use the eyedropper in the dyntopo to get current mesh res.\n\n\n# Blender 2.80 (sub 20), Commit date: 2018-07-04 17:33, Hash 53c63db2ee1\nbpy.ops.object.delete(use_global=False) # Operator\nbpy.ops.mesh.primitive_plane_add(radius=1, view_align=False, enter_editmode=False, location=(0, 0, 0), layers=(True, False, False, False, False, False, False, False, False, False, False, False, False, False, False, False, False, False, False, False)) # Operator\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.mesh.merge(type='CENTER') # Operator\nbpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={\"mirror\":False}, TRANSFORM_OT_translate={\"value\":(-1.30863, 0.839408, 3.08477), \"constraint_axis\":(False, False, False), \"constraint_orientation\":'GLOBAL', \"mirror\":False, \"proportional\":'DISABLED', \"proportional_edit_falloff\":'SMOOTH', \"proportional_size\":1, \"snap\":False, \"snap_target\":'CLOSEST', \"snap_point\":(0, 0, 0), \"snap_align\":False, \"snap_normal\":(0, 0, 0), \"gpencil_strokes\":False, \"cursor_transform\":False, \"texture_space\":False, \"remove_on_cancel\":False, \"release_confirm\":False, \"use_accurate\":False}) # Operator\nbpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={\"mirror\":False}, TRANSFORM_OT_translate={\"value\":(1.94841, 1.85942, -2.07036), \"constraint_axis\":(False, False, False), \"constraint_orientation\":'GLOBAL', \"mirror\":False, \"proportional\":'DISABLED', \"proportional_edit_falloff\":'SMOOTH', \"proportional_size\":1, \"snap\":False, \"snap_target\":'CLOSEST', \"snap_point\":(0, 0, 0), \"snap_align\":False, \"snap_normal\":(0, 0, 0), \"gpencil_strokes\":False, \"cursor_transform\":False, \"texture_space\":False, \"remove_on_cancel\":False, \"release_confirm\":False, \"use_accurate\":False}) # Operator\nbpy.ops.mesh.extrude_region_move(MESH_OT_extrude_region={\"mirror\":False}, TRANSFORM_OT_translate={\"value\":(0.747162, -0.763019, -1.99146), \"constraint_axis\":(False, False, False), \"constraint_orientation\":'GLOBAL', \"mirror\":False, \"proportional\":'DISABLED', \"proportional_edit_falloff\":'SMOOTH', \"proportional_size\":1, \"snap\":False, \"snap_target\":'CLOSEST', \"snap_point\":(0, 0, 0), \"snap_align\":False, \"snap_normal\":(0, 0, 0), \"gpencil_strokes\":False, \"cursor_transform\":False, \"texture_space\":False, \"remove_on_cancel\":False, \"release_confirm\":False, \"use_accurate\":False}) # Operator\nbpy.context.space_data.context = 'MODIFIER' # Property\nbpy.ops.object.modifier_add(type='SKIN') # Operator\nbpy.ops.object.skin_root_mark() # Operator\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.object.modifier_add(type='SUBSURF') # Operator\nbpy.context.object.modifiers[\"Subsurf\"].levels = 2 # Property\nbpy.context.object.modifiers[\"Subsurf\"].levels = 3 # Property\nbpy.ops.transform.translate(value=(-0.279138, -0.620852, 0.00903034), constraint_axis=(False, False, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1) # Operator\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.transform.translate(value=(-0.00624544, 0.163682, -0.947847), constraint_axis=(False, False, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1) # Operator\nbpy.ops.object.editmode_toggle() # Operator\nbpy.ops.transform.translate(value=(0, -0.564443, 0), constraint_axis=(False, True, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1) # Operator\nbpy.ops.transform.translate(value=(0, 0.0542979, 0), constraint_axis=(False, True, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1, release_confirm=True) # Operator\nbpy.ops.transform.translate(value=(-0.399156, 0, 0), constraint_axis=(True, False, False), constraint_orientation='GLOBAL', mirror=False, proportional='DISABLED', proportional_edit_falloff='SMOOTH', proportional_size=1, release_confirm=True) # Operator\nbpy.ops.sculpt.sculptmode_toggle() # Operator\nbpy.ops.sculpt.sculptmode_toggle() # Operator\nbpy.ops.object.modifier_apply(apply_as='DATA', modifier=\"Skin\") # Operator\nbpy.ops.object.modifier_apply(apply_as='DATA', modifier=\"Subsurf\") # Operator\nbpy.ops.sculpt.sculptmode_toggle() # Operator\nbpy.ops.sculpt.dynamic_topology_toggle() # Operator\nbpy.context.scene.tool_settings.sculpt.detail_type_method = 'CONSTANT' # Property\n\n# backtrace\n./blender(BLI_system_backtrace+0x20) [0x19c92a0]\n./blender() [0x100c5a8]\n/lib64/libc.so.6(+0x362f0) [0x7fde439422f0]\n./blender(ED_view3d_win_to_origin+0x7) [0x10ffc87]\n./blender() [0x10fff63]\n./blender(ED_view3d_win_to_segment+0x27) [0x1100417]\n./blender() [0x132562b]\n./blender() [0x1326618]\n./blender() [0x1326712]\n./blender() [0x10150bc]\n./blender() [0x1015a6f]\n./blender() [0x1015f7c]\n./blender(wm_event_do_handlers+0x211) [0x10165f1]\n./blender(WM_main+0x20) [0x100d280]\n./blender(main+0x31d) [0xfae91d]\n/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fde4392e445]\n./blender() [0x10092ae]\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "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", "Smoke: \"changing Flow Type\" does not affect already computed frames.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: version: 2.93.0 Beta, f903e3a3fd003e5295f7aea35710a77b2e74f846\n\nAfter \"Quick Smoke\" changing \"Flow Type\" for already computed frames has no effect.\n\nNew Scene, delete cube and add Suzanne (optional probably).\nSelect object, F3, \"smoke\" enter on \"Quick Smoke\".\nPress space bar to play the scene, you should see smoke rising around the object.\nPress space bar again to stop the sim around say frame 150.\nIn the Physics Properties, change the Flow Type from Smoke to Smoke+Fire or Fire.\nPress space bar to resume the playback.\n\nObserve that new frames not previously computed will reflect the new Flow Type, but when it wraps around to the previously computed frames it only shows the original \"Smoke\" flow type. \n\nIf you save the scene and re-load it, then the currently selected flow type will affect the scene correctly from frame 1.\n\nSo when changing \"Flow Type\" it does not clear frames that have been computed/cached under the previous value. \n\nI looked for some place to explicitly clear that cache without any luck but maybe I just didn't fine it. Since reloading the scene resets the now incorrect frames, it seems to me that changing the Flow Type should immediately invalidate any now-obsolete frames that were computed using the old setting.", "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)", "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", "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", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\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\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\n\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)", "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 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 Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\nOperating system: Windows 10 - 22H2\nGraphics card: 3090ti 31.0.15.3667\n\nBroken: (3.5, 3.5.1, 3.6.1)\nWorked: None\n\nBlender Cycles \"Launch failed in CUDA queue copy from device (integrator_intersect_shadow)\"\n\nI have a volumetric setup in the scene. To show up as haze on the horizon. Error only occurs when Volumetric is active.\n\nEnsure the WorldSphere is enabled for render and just render animation for 1279. \nIt will do 1 - 10 frames before throws the error attached. \n\nFile is too big for the attacher, please get blend file from google drive link.\n\nview?usp=drive_link\n\nSimplified: view?usp=drive_link\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)", "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", "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", "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", "Force fields don't work on a fire simulation with Flame Smoke 0\nOperating system: Windows 7 (64 bits)\nGraphics card: Radeon R7 200\n\nBroken: 2.83, 2.92.0\nWorked: -\n\nSetting the Flame Smoke to 0 makes the fire simulation to ignore all forces except gravity.\n\n* create a Quick Smoke simulation\n* set the Flow object to Fire, behaviour to Inflow\n* set Domain object Flame Smoke to 0 in the domain object of a fire simulation\n\nI've also added a particle system to visualize the force, while the fire remains unaffected:\n\n\nHere's a test file:[fire-test.blend](fire-test.blend)" ]

[ "smoke simulation broken\nOperating system: windows 10\nGraphics card: gtx 1080\n\nBroken: blender 2.8 beta\n\nim unable to make smoke simulations.\njust select the default cube, and set it to smoke domain, it crashes right away." ]

[ "Slower frame-change with many objects in the scenes collection\nWhen objects are in the scenes collection (instead of a sub-collection), changing frames using left/right keys is slower.\n\nThere is also a slowdown when animation playback restarts.\n\nThis occurs in 3.5x `ab63fe9eab8fd01d4a763199442987191d105c55` and 3.4x release.\n\nTo reproduce the problem:\n\n- With a new file paste the script inlined at the bottom of the report into a text editor and run it.\n- Press Spacebar in the 3D viewport to play back animation.\n- Note the FPS (~13.1 FPS here).\n\n- Start again, doing the previous steps with `USE_SCENE_COLLECTION = True` in the script.\n- Note the FPS is much lower (~3.46 FPS here).\n\n---\n\n#### Explanation\n\n- This is an issue I ran into when investigating why objects in collections were being re-populated during animation playback in some files, see !104553.\n- The cause of the problem is the scene is tagged by the depsgraph (see: `ANIMPLAY_FLAG_JUMPED`). _(note: the jumped flag is set when changing frame via arrow keys & when the animation restarts)._\n- When `ANIMPLAY_FLAG_JUMPED` is set `scene` is tagged with `ID_RECALC_FRAME_CHANGE`.\n- This causes the scene to be copied (see `blender::deg::deg_update_copy_on_write_datablock`).\n- The `scene->master_collection` is copied (non recursively).\n\n - When `scene->master_collection` contains many objects, copying has a noticeable performance penalty.\n - When it only contains some collections, the problem isn't noticeable.\n\n#### Other Notes\n\n- This is mainly noticeable when loading files pre 2.8x which load objects directly into `scene->master_collection`.\n- This report mentions animation playback speed because it's easily measurable, however many other operations trigger this (left/right arrow keys to change frames, every update when dragging scene number buttons \"Sampling\" (Render or Viewport) for e.g.).\n- In the test script the start and end frames are the same to so the playback is continually restarting to accentuate the problem and match the slowdown from changing frames via arrow keys.\n\n---\n\nThis script adds many objects to the factory settings file, hides them, adds some keyframes to the Light and sets the 3D viewport full-screen, ready for animation playback.\n\n\n```python\nimport bpy\n\nUSE_SCENE_COLLECTION = False\nOBJECT_NUMBER = 20_000\n\ndef objects_create(object_num):\n objects = []\n new = bpy.data.objects.new\n for i in range(object_num):\n objects.append(new(hex(i), None))\n return objects\n\n\ndef objects_collection_link(collection, objects):\n link = collection.objects.link\n for ob in objects:\n link(ob)\n\n\ndef main():\n from bpy import context\n\n bpy.ops.wm.read_homefile(use_factory_startup=True)\n\n if USE_SCENE_COLLECTION:\n collection = context.scene.collection\n else:\n collection = context.collection\n\n # Keyframe the lamps location, this is important as without this\n # the scene is not considered \"animated\".\n ob_lamp = bpy.data.objects[\"Light\"]\n ob_lamp.keyframe_insert(\"location\", frame=1)\n\n # The short frame range shows the problem most,\n # as this tags the scene to be tagged to update on frame-change.\n context.scene.frame_start = 1\n context.scene.frame_end = 1\n \n # Attempt max FPS.\n context.scene.render.fps = 1000\n\n objects = objects_create(OBJECT_NUMBER)\n objects_collection_link(collection, objects)\n \n # Hide everything, except the lamp.\n bpy.ops.object.select_all(action='SELECT')\n window = bpy.data.window_managers[0].windows[0]\n area = next(area for area in window.screen.areas if area.type == 'VIEW_3D')\n \n # Hide needs an 3D viewport (but select doesn't, hrm..).\n with context.temp_override(window=window, area=area):\n bpy.ops.object.hide_view_set(unselected=False)\n ob_lamp.hide_set(False)\n \n # Fullscreen 3D view (rule out slowdown from drawing other areas).\n with context.temp_override(window=window, area=area):\n bpy.ops.screen.screen_full_area()\n \n\nif __name__ == \"__main__\":\n main()\n```\n\n", "Viewport display of multiple Dupli-Collections when different draw-types are used : wireframe might disappear (only selected are garuanteed to draw)\nOperating system: Windows 10 / Ubuntu 20.04\nGraphics card: GTX 1080 / RTX 3080\n\nBroken: 2d9d08677e a2d59b2dac \nBroken: all versions >= 2.8\nWorked: 2.79\n\nViewport display of Dupli-Collections is inconsistant.\nDigging deeper into it, it looks to be when there are different draw types on the same dupli-collection\n\n1. Open attached blend file\n2. select the empties in the middle of the screen which do not look like they have anything attached\n3. notice how they randomly appear / disappear upon selection.\n4. note that one of instancer is set to `Textured` draw type, the other to `Wire`, if all are set to `Wire` the issue is gone\n\nThis has happened in quite a few of our production scenes.[bug.blend](bug.blend)\n\nNOTE: Might boil down to be the same as #101822 (Collection instance set to Display As Wire doesn't show in Solid mode when not selected) or #86732 (Instanced wire objects are hidden in solid mode instead wire appearance)\n\n", "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", "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)", "Unify the various copy procedures used in node editor\nNode editor has current 5 different places where copying nodes takes place (search for uses of `bke::node_copy_with_mapping`):\n* [Node tree copy](node.cc#L133)\n* [Duplicate nodes](node_edit.cc#L1251)\n* [Group Separate (copies nodes from the group tree into another tree)](node_group.cc#L442)\n* [Clipboard (both copy to clipboard and paste into node tree)](clipboard.cc#L185)\n* [Shader node tree branch copy for execution](node_shader_tree.cc#L562)\n\nThe core stages of the copy procedure are roughly the same in each operator, but with differences in implementation that lead to a lot of code duplication. For example, `node_map` in clipboard uses `const bNode *` keys, while the duplicate operator uses non-const keys.\n\nCopy operators should share these pieces to avoid too much code duplication:\n1. Copy nodes themselves\n2. Build an _old -> new_ node map\n3. Build an _old -> new_ socket map for connections\n4. Remap parent/child relationships of new nodes\n5. Copy and remap internal and external links between nodes\n6. Update selection\n7. Update topology cache\n8. Perform generic tree update to handle potential changes\n\n", "\"New material\" tooltip should be \"Copy current material\"\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.25\n\nBroken: version: 4.0.0 Alpha\nWorked: Unknown\n\nThe tooltip in the image is not correct and might cause confusion. Clicking the button instead of just creating a new material, it copies the material to a new one, instead of creating a new material from a blank template.\n\nHover mouse over the icon pointed by the red arrow in the attached image (located in the shader editor).\n\nThe tooltip says: \"New material\".\nI think the tooltip should say:\n\"Copy material\"\n\"Creates a new material by duplicating the current one\"\n\n**Observation**\nThis issue is similar to issue #107625, but in another part of Blender.", "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", "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).", "Crash with lineArt modifier and Armature\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nExperienced with 2.93.2\n\nHaving a line art object in the scene applied to an object 'A' when there is an armature on object 'B' makes blender very unstable. A simple scroll in the timeline will crash instantly.\n\n\nIn the attached file, what I did : \n- Create a cube, subdivided along Y, add a simple armature, keyframe it with a simple motion.\n- Duplicate the cube, apply the armature.\n- Select the second cube, shift-a -> Object Line Art\nFrom there : \n- Scroll the timeline... Crash.\n\nIf I delete the animated cube, scrolling works fine. Disabling it in viewport as well.\n\n\nI also tried adding a simple cube, instead of duplicating the initial \"armatured\" cube, and adding the Object Line Art to it, but the same crash occurs.\n\n[LineArtCrash.blend](LineArtCrash.blend)\n\n", "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", "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", "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", "Cycles render artifacts relating scene scale\nOperating system: Windows 10\nGraphics card: tested multiple graphics cards with same issue\n\nBroken: 2.83.6 (file originally made in 2.79 and had the same issue)\n\nThere exists in the blend file data only two objects - the camera and a simple plane. Yet when rendering, the result does not match the viewport and there seems to be another ghost object appearing in the scene.\n\nBased on the following startup file: [strange-error.blend](strange-error.blend)\n\n1. Switch to rendered view in the viewport. This is how things should look.\n2. Now render the current frame at frame 97. Notice the strange ghosting effect in the center of the frame.", "Properties don't update focus when copy/paste an object\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 511.79\n\nBroken: version: 3.0.1, 3.1.2\nWorked: I don't know\n\nIf you **Copy/Paste** object with **Ctrl+C**, **Ctrl+V** the Property window will still have focus on the old object (although a new one is selected).\nIn this case, the **Duplicate** operation works correctly, the focus is on the new object (the one that is selected).\nReproduce on **Scene objects** and on **Nodes** in node editor. I think there are many more places.\n\n[filename700.mp4](filename700.mp4)\n[filename704.mp4](filename704.mp4)\n\nIn node editor\n1) Select any node.\n2) Copy and paste node with Ctrl+C/Ctrl+V.\n3) Change any properties, you can see that you are changing the previous object, although a new one is selected.\n\n", "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)" ]

[ "UI bug in Outliner Editor: Right Mouse Click over 'Scene Collection'.Panel displayed shows entries that are repeated\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\nBroken: version 2.83\nWorked: 2.82\nCaused by changes in 92113e2da7\n\n1. In Blender Right Mouse Click over 'Scene Collection'\n2. Entries are repeated.\n\n\n\n\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", "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", "NLA Visual Bake of Actions (with Rigify character) Gives broken results.\nOperating system: Windows 10 Home 64bit\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e15, type: release, build date: 2022-03-09, 00:44:13\nWorked: 3.0 and later - All that can open this file correctly.\n\n**Description**\n(Files provided for testing)\nyou'll find a stack of NLA Action strips resulting in desired animation.\nBaking those actions into a single Action using visual keying results in Broken looking animation (baked action is set to Replace).\nAdditionally even though the resulting strip is set to replace and placed as the top layer. Turning Layers on/off below it affects the resulting pose on the character.\nOne would expect once the top layer is set to Replace, anything happening in the lower layers should have no apparent effect and could safely be removed from the NLA.\n\nAttached Viewport Renders of Pre and Post Bakes for reference.\nAttached Character rig used as a Library override (save and relocate the library override from the outliner in the Animation file)\nAttached The Animation File in which I am attempting to Bake.\n\n[MomoDebug_A_rig.blend](MomoDebug_A_rig.blend)\n\n[BadBakeNLAActions.blend](BadBakeNLAActions.blend)\n\n- Open file BadBakeNLAActions.blend. MomoDebug_A_rig.blend is linked, so may need relocating\n- Delete The top NLA track - it is my failed bake.\n# Turn on all other tracks below\n\n- Run Object > Animation > Bake Action. Use Visual keying option.\n- Turn off all the layers below (EXCEPT for the WORLD PLACER, that one doesn't get baked because it affects the rig Object itself rather than the bones)\n\nResult:\nI couldn't remove the layers below without breaking the animation.\n\n", "Particles animation dont show\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nemitter particles animation don't show movement when i press G shortcut to move the model that contain the particles but they don't show any movement, so i can't do an autokeying animation whit the desire movement of the mouse.\n\nadd a cube, put particle emitter, press space bar and G key to move, the particles don't show movement only flickering.\n", "Collection Assets: To Instance or Not to Instance\nWhen using collections as assets, it needs to be defined when dropping a collection should use instancing and when not. Instancing collections basically means a non-editable version of the collection is added to the scene, with an empty acting as the pivot point. So the collection can be transformed by transforming the empty, but the contents of the collection aren't editable without further steps.\n\ncollection.html\n\n## Proposal: Operator Option\n\nWhile we could just add another option for instancing to the Asset Browser, next to the *Import Type* option, it adds clutter and also requires setting up things before dragging: If you dragged in an asset and used the wrong setting or change your mind afterwards, you'd have to undo and perform the operation again, or manually replace the collection.\nSo it violates the [Operate -> Settings design paradigm ](Paradigms#Operate_-.3E_Settings) of Blender. Instead the proposal is to have this controlled via an operator option, whereby the option will remember what it was set to last. Another setting could still be added, but the operator setting should be useful either way.\n\n***Current File* Asset Library**\n\nIn the *Current File* asset library we often reuse data, but not as often as with the *Append (Reuse Data)* option. E.g. materials are shared, but objects are duplicated including their mesh. [D12879](D12879) tries to make things more unified & explicit, but it's on hold.\n\nNo strong opinion on how this should be handled, I'd say let's avoid confusing users by sharing meshes. So:\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Other Asset Libraries**\n\n**Link:**\n- Use drop operator option to determine if instancing should be used (*Instance* option)\n\n**Append:**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, all objects will be duplicated.\n\n**Append (Reuse Data):**\n- If the *Instance* operator option is...:\n - ... true: Create a new collection instance.\n - ... false: Add a new collection (no instance). If the collection already exists in the file, a new collection is created but the object's meshes are shared.\n\n**Determining the Drop Location & Rotation**\n\nIdea is to make the drop location and rotation be defined visually. So when dropping a collection, it is transformed to land under the mouse cursor (and later use bounding-box snapping), regardless of where the instance empty is, or regardeless of the collection instance offset. They are reverse applied.\n\nNotes:\n- The drop transform will have to be applied to all added objects, including objects used by the objects inside the collection, which are not in the collection itself. E.g. if an object has a parent or a boolean modifier, the parent or boolean-object is imported along, and the relative transform needs to be preserved. We already do this for dropping object assets, code can be shared.\n- When linking without instancing, the dropped collection will use the drop location of the source file.\n\n**What Should be the Default**\n\nThere seems to be some agreement that in production environments, instancing should be the default. However for beginners (or anybody unfamiliar with collection instancing) this may be a bit confusing. Needs some feedback, for now instancing can be the default behavior.\n\n", "Geometry nodes. Objects with negative scale have positive scale as instances\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.3.3\n3.4.1 and 3.5 are broken too\n\nWhen I instance from collection, objects with negative scale passes only positive scale to instances.\nCheck file and video.\n\n", "Bake texture then the colour of texture is changed\nOperating system: Windows 10\nGraphics card: NVIDIA GTX 1050\n\nBroken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd76f, type: Release\nWorked: Never (2.80+)\n\nWhen I bake texture to a new UV colour is changed. After bake, I use the colour picker to define the colour.\nThe original texture of the cube has colour #41FF6A. Cube texture with new UV has #40FE69.\nI tried to bake at the same object and from one object to another - bug is here too.\n!!! Importantly !!! The bug is here if the original texture does not save to a file (jpg, tif, etc). if I save the original texture to file before baking the bug is not here.\n\n1. Add two cube.\n2. Cubes have to have different UV.\n3. Set colour #41FF6A as image texture at first cube (does not save texture in a file).\n4. Set Bake Type to Diffuse and uncheck Direct and Indirect in Bake.\n5. Bake.\n6. Take colour picker (I use ColorMania) and compare colours both cubes (the second cube will be #40FE69).\n", "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", "Random Per Island does not work on instances\nOperating system: Linux-6.0.5-arch1-1-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06\n\nBroken: version: 3.4.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\n\nMaterials which use the \"Random Per Island\" geometry attribute do not work correctly on instances generated via geometry nodes.\nI am not sure if this is actually a bug, because maybe the attribute is only intended to work for meshes. But I think as an artist you would expect it to work?\n\nIn the following video I have a cube with an array modifier applied to it. I then added a geometry nodes modifier after the array modifier which instances cubes on the array of cubes.\n[2022-10-29 13-56-24.mp4](2022-10-29_13-56-24.mp4)\n\n[random_per_island_instances.blend](random_per_island_instances.blend)\n\n", "Point Clouds only support one material\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken version: Current main.\nWorked: Never\n\nWhen using the `Join Geometry` node in Geometry nodes to join two points together, their material is reset to default. This only happens when joining two or more \"lone\" points.\n\n1. Recreate the geometry node setup found in the image below\n2. Change the render engine Cycles (necessary to see points with a material)\n3. Render the scene.\n4. Notice that the materials you assigned to the points are not applied.\n\nI have also included a .blend file with steps 1 and 2 done.\n[Missing Material - Join Geometry.blend](attachment)\n\n\n", "Crash after Disk Cache Particle bake while set to render as path\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nsame results on daily 3.1 build\n\nBlender crashes after finishing baking the particles to disk.\nThen proceeds to delete the baked files upon reopening the file. \n(don't know if the deletion is intended behaviour or not, but it stops you from being able to salvage the bake unless you rename / duplicate the cache folder beforehand)\n\nSeems to only happen with disk cache bake and not baking to memory. \nChanging the 'render as' setting to anything but 'path' seems to stop the crashing.\n\nOpen file, bake the particle system\n[Particle Bake to DiskCache Crash.blend](Particle_Bake_to_DiskCache_Crash.blend)", "Point Instance node doesn't instance meta objects.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\nBroken: version: 2.93.0 Alpha\n\nFor Geo Nodes, Point Instance node doesn't work (doesn't copy) meta objects (like metaball). \n\nI used a very basic setup. The original input and output nodes plus one point instance node. I selected the object to be a meatball. Nothing happens! I selected any other object (non-meta). The object is instanced. Geo nodes were added to the default cube. \n", "Clicking \"Bake All Dynamics\" causing various crashes.\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 536.99\n\nBroken: version: 3.6.2\n\nUsing \"Bake All Dynamics\" is beyond finicky and crashes Blender in many different use cases. Many little \"tricks\" are needed to make it work. I am using Disk Cache for all below situations, but I believe the crashes happen with or without this.\n\nSituations where it crashes:\nClicking \"Bake All Dynamics\" within the Cloth cache settings. It seems it's required to click \"Bake All Dynamics\" button within the context of the Rigid Body system, or else it crashes instantly.\n\nClicking \"Bake All Dynamics\" in the context of hair dynamics seems to do nothing. Same goes for \"Update All to Frame\"\n\nIf a rigid body simulation has been baked, clicking \"Delete All Bakes\", then clicking \"Bake All Dynamics\" immediately will also crash blender. The only workaround for this is to \"move\" an object even if using a zero value, before clicking \"Bake All Dynamics\" again. This prevents the crash. \n\n\nCreate a Rigid Body Sim, create a Cloth Sim. Check \"Disk Cache\" as an option. Try the various methods listed above.\n\n", "Particle simulations dont generate valid disk caches\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.30\n\nBroken: version: 2.93.1\n\nand I tried on the blender-2.83 LTS and it has the same issue.\n\nBlender stops simulating particle systems. if I'm baking them it just puts noting in the bake if I'm rendering without baking first if doesn't do anything except make my fans run full blast.\n\ncreate a bunch of particle sims. Use I used the script in the blend to do it.\nrun bake all dynamics. Only the first few of them actually generate anything.\n\nOf don't bake and just try to render. It freeze.\n\n[bugReportFireworks.blend](bugReportFireworks.blend)", "In Particle Edit mode, Emitter particles are not visible in the viewport\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 455 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.21\n\nBroken: version: 2.83 (sub 0)\nWorked: 2.79.7, 2.79b\n\nThe Particle Edit mode does not work with Emitter type particle. The particle (particle paths) are not visible in the viewport.\n\n- Open this file: [#73168-particle-edit-crash.blend](T73168-particle-edit-crash.blend) (or add a particle system, Emitter type, and bake to memory)\n- Switch to \"Particle Edit\" mode (particle disappear).\n- Click on Sidebar > \"Tool\" > \"Options\" > \"Viewport Display\" > \"Particles\" (blender crash).\n\nReports:\n\n[blender.crash.txt](blender.crash.txt)\n[macos.crash.txt](macos.crash.txt)" ]

[ "Particle objects that are emitted are ignored in cycles for baking normal maps.\nWindows 8.1 Nvidia GeForce GTX 670MX\n\nBroken: 2.76 RC Date 2015/09/21 00:32 Hash : 034cc85\n\nParticle objects are not baked when normal map baking in cycles. This works as expected in Blender internal. Is this something that is deliberately left out of cycles normal map baking?\nBlend file is included. \n\nset up a particle system on an object, set it to use an object or a group as the rendered particle. \ncreate an image that can be baked to and selected in the material node editor. \nSelect the object with the particle system, the object/s that make up the group in the particle system and then make a plane to be the object to be baked to. (ensuring it is unwrapped and is the active object).\nSet the bake settings to be of a 'normal' type and then select 'selected to active'. \n\nIn cycles the particle objects will be ignored, in blender internal they'll be taken into consideration. \n\nNOTE : Some cycles passes such as ambient occlusion DO seem to be affected by the particle objects, but the particle objects themselves wont be rendered. [BlenderCyclesParticleBake.blend](BlenderCyclesParticleBake.blend)\n", "Crash when baking normals with Cycles from object with dupli children\nOS: Arch Linux\nGPU: Nvidia GeForce GT 220\n\nBroken: buildbot version 2.79.2, Date: 2018-02-21, Hash: 5d5c6bb5efe\nDoesn't crash, but doesn't bake either: release 2.79, Date 2017-09-11, Hash: 5bd8ac9abfa\n\nTrying to bake a normalmap with Cycles from a plane with duplicated children to another uv-unwrapped plane crashes Blender.\n\nOpen attached blend file:\n- Selected: PlaneDupli, has a child DupliObject that is duplicated on the plane's faces\n- Active: PlaneBake, is uv-unwrapped and has a material with selected image texture to bake to\n\nHit bake:\nBlender buildbot version segfaults and closes, see attached dupli-bake-normal.crash.txt.\nBlender release 2.79 doesn't crash, but baked normal map is plain grey.\n\n[dupli-bake-normal.blend](dupli-bake-normal.blend)\n[dupli-bake-normal.crash.txt](dupli-bake-normal.crash.txt)\n", "Baking ignores instancieted objects when using \"selected to active\" (Cycles baking maps)\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.9.15\n\nBroken: version: 2.91.0\n\n\nWhen baking textures in cycles, if you have instancieted object those do not appear on the baking maps but they appear on the render. Fun that the ambient occlusion show the shadows of the objects but not the objects.\n\nTrying to bake normal or ambient occlusion or any map... from objects that have instancieted objects ignores the instancieted objects, look at the screenshot.\n\n[IMAGE SCREENSHOOT ](noBaking_image.png)\n\nnoBaking_image.png\n\nCreate an object instanciate several time using \"instancing\" option on top of another surface, try to bake those objects with cycles using another mesh and using the option \"selected to active\".\n\nBlender File: NoBakingInstantiated.blend\n\n\n", "Cycles dupli object baking issues\nnvidia g880m\n\nBroken: blender-2.73-d56c9fb-win64\nWorked: (optional) probably never\n\nwhen assigning object as duplis to some mesh, and then trying to bake these duplis to another mesh, duplis appear black. But in normals mode, it works, so they are there, just without material or something.\nAlso, you can see that the duplis are there actually twice, one offset quite strongly. In some other file, I got them also four times...\n\n\n[bakebug.blend](bakebug.blend)\nopen the file, hit bake. \nthe group of objects in the ceter bakes to the cube.\n\nalso, you can see another group of objects, where duplis have been made \"real\" and it works well, it's group of objects called \"fine\", baking to the cube works well with seemingly same meshes.\n" ]

[ "Texturing with anchored type stroke\nOperating system: Linux-5.4.0-47-generic-x86_64-with-debian-bullseye-sid 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.51.06\n\nBroken: version: 2.91.0 Alpha\n\nTexture paint with stroke set to anchored while using texture significantly slows down blender up to non responsive state and crash while paint texture is larger than 2k.\n\n[Texture pain stroke ty[e anchored.blend](Texture_pain_stroke_ty_e_anchored.blend)\n", "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", "Smear tool painting vertex colors corrupts color info: part 2\nvertex colors get corrupted under certain blend mode combinations. 3.0.1 master.\n\nusing the smear tool over blue colors introduce green, magenta, yellow, gray and orange not present inside the blue ranges.\n\npainting with blue results in grays instead. \n\ni had this problem in 3.2 alpha using sculpt vertex colors, but when i got back to a project in 3.0.1 it happened with vanilla vertex colors tool. \n\nincluded a file this time\n\n[vertex colors bug.blend](vertex_colors_bug.blend)\n\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\nWorked: (newest version of Blender that worked as expected) 2.93\n\nSmear tool painting vertex colors corrupts color info\n\nuse paint brush with blue color. paints gray instead.\nuse smear brush. it should smear blues and not oranges and greens.\n", "Visual bug when using strenght tool in 3D space left for Tool Panel\nOperating system: Windows 10 64Bit\nGraphics card: Nvidia GTX 960M\n\nBroken: 2.80 RC\n\nVisual bug in Sculpt mode, Vertex Paint, Weight paint and Texture paint\n\n1. Go to Texture Paint mode\n2. Set strength tool to 1.0 (shift F)\n3. Use strenght tool hotkey (Shift F) in the narrow 3D space left for the Tool Panel\n\n", "Lagging out when using pose brush\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 517.48\n\nBroken: version: 3.5.0\nWorked: (also had issue on 3.4)\n\nlags out when trying to use the pose brush, particularly after unchecking \"connected only\" getting rid of the multires modifier seems to fix the issue but I'd like to be able to use the pose brush while preserving my resolution.\n\n\"connected only\" is already unchecked in the attached file, so to see the error just try to move the mouse/use the pose brush and you will see the lag. This is a majorly cut down version of the file so it is much worse in the full version to the point where the file is completely unusable.\n\n", "Texture Paint mode tools swap when exiting maximized area\nOperating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.68.02\n\nBroken: version: 3.3.0 Alpha\nWorked: unknown\n\n[texture_paint_tool_swapping-2022-05-10_12.52.16.mp4](texture_paint_tool_swapping-2022-05-10_12.52.16.mp4)\n\n- Go to texture paint mode\n- open second image editor\n- maximize the area of the 3D viewport\n- change the active tool\n- un-maximize the area\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", "Missing undo push for Paint Mask and Vertex Selection in weight paint\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 466.77\n\nBroken: version: 3.0.0 Alpha\n\nEnabling or disabling of the Paint Mask and Vertex Selection modes is missing an undo push\n\n\n\n[Weight.blend](Weight.blend)\nEnable Paint Mask\n\nPaint on the model\nUndo\nResult: Both the paint and the paint mask mode are undone", "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", "Use Scene Spacing Distance by default\nNOTE: This design is still being investigated and discussed. \n\n# Issue\n\nThe default for brushes in every mode has always been to use view based spacing for each stroke.\nThis wasn't always an issue since brushes used to work via a projected falloff.\n\nBut when using a spherical falloff on curved surfaces this can lead to inconsistent spacing artefacts.\nSince more painting and sculpting modes are implementing brushes with a spherical falloff by default, it is a reasonable adjustment to make the spacing also scene based.\n\n# First Steps\n\nBefore changing any defaults we should investigate any remaining issues, downsides or bugs if this behaviour would be implemented by default for all brushes.\nOnce it is clear that this change would be an overall improvement, and how feature might need to change.\n\n### Fix remaining bugs and issues\n\nFurther issues from using Scene Spacing need to be investigated.\nThe currently known reports are:\n- #98111 (Sculpt mode: Draw Sharp brush artefacts when using Scene Spacing in stroke settings)\n- #99638 (Line stroke method not working with Scene spacing)\n- #99642 (Clay strips brush freeze when coming from outside the horizon of surface curvature)\n- #99644 (Draw Sharp brush stops on anchored during the stroke)\n\n# Proposal\n\nScene spacing currently accomplishes two distinct behaviours:\n1. The spacing is consistent in 3 dimensions\n2. The spacing is consistent in world space (especially when zooming in/out)\n\nInstead of just making Scene Spacing Distance the default, we should change the \"View\" scene spacing to work 3 dimensionally for a better brush behaviour in general.\nThis could be accomplished by associating these two different behaviours with distinct settings:\n\n1. Setting the falloff to be Spherical or Projected = 3D or projected spacing distance\n2. Switching between View & Scene spacing distance = The spacing is a percentage of the relative brush size diameter or an absolute world size\n\nThe UI should then also reflect that change, by changing the spacing slider value:\n- View = Percentage\n- Scene = Distance in units\n\nThis updated View spacing then needs to be integrated in every mode for 3D painting/sculpting.", "Scene Line Art problem when used with Grease Pencil objects.\nOperating system: Windows 10\nGraphics card: Radeon RX 590\n\nBroken: (2.93.0 Beta, 0f66dbea904f, master, 2021-04-21)\nWorked: ()\n\nScene Line Art or Object Line Art are located in front of the Grease Pencil objects.\n\n\n[SceneLineArt_and_GPencil.blend](SceneLineArt_and_GPencil.blend)", "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)", "Grease pencil: unstable offset height (surface drawing)\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\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\n", "Can't select bone while Weightpaint with Face PaintMask\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.91.0\nWorked: Never (2.79+)\n\nBones can't be selected while in Weightpaint mode and Face Paintmaks option is activated.\n\nBased on the Select with Left Mouse button option and Default Blender Keymap:\n\n[PaintMaskAndWeightPaint.blend](PaintMaskAndWeightPaint.blend)\n\n1- Open the attached file called PaintMaskAndWeightPaint.blend\n2- You see the Cube rigged with 2 bones already in pose mode and cube in Weightpaint mode\n3- You can change Bone selection while weightpainting pressing the CTRL + LMB (Left Mouse Button), there is any problem for now\n4- Now, if you activate the Face Paint Mask button at the top-left and try to select another bone like before pressing CTRL+LMB on a bone, bone will not be selected, instead of that, you select a face mask. \n5- If you go to keymap options, and deactivate the option \"**Select**\" from \"**Weight paint**\" to avoid select faces with CTRL + LMB, now if you try to select another bone, it will not select another mask face, but it will not select the new bone and will exit the Weight Paint mode.\n", "Texture paint undo sometimes changes texture slot\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 2.80 (sub 48), 2019-03-12 13:53, hash: 936014ea8c74\n\nWhen texture painting on a particular texture slot, then undoing that painting, sometimes the selected paint slot will change.\n\nI couldn't reproduce from the default startup file, so I've stripped down the file that's having problems as much as I can.\n\n1. Open attached file\n2. Select paint slot \"Skin mask\" from either topbar or properties panel.\n3. Paint some strokes on the model or image editor\n4. Press Ctrl-Z\n5. Notice the paint slot is no longer set to \"Skin mask\"\n\n- - -\n\n- Change to the Skin Mask slot.\n- Paint a single stroke in the image editor.\n- Undo two times.\n- Paint another single stroke in the image editor.\n- Undo one time.\n- Notice that the slot changed.\n[texturepaintbug.blend](texturepaintbug.blend)" ]

[ "Gradient Tool on Weight Paint Mode ignores X-Axis Symmetry Option\nOperating system:\nTEST #01 Unknown (I'm reporting a bug from someone else, forgot to ask OS specifications)\nTEST #02 5.4.0-122-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 Desktop: Xfce 4.16.0 tk: Gtk 3.24.20 wm: xfwm4 dm: LightDM Distro: Linux Mint 20.3 Una; base: Ubuntu 20.04 focal\n\nGraphics card:\nTEST #01 Unknown\nTEST #02 Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0102; Display: x11 server: X.Org 1.20.13 driver: modesetting unloaded: fbdev,vesa; resolution: 1024x768~60Hz; OpenGL: renderer: Mesa Intel HD Graphics 2000 (SNB GT1); v: 3.3 Mesa 22.1.3 - kisak-mesa PPA direct render: Yes\n\nBroken: 3.2.0 and 3.2.1\nWorked: None\n\nWhen you've got like a humanoid character Mesh Object, conventionally Symmetric on the X-Axis, but not using a Mirror Modifier, only the *Enable symmetry on the X Axis* Option on Weight Paint Mode, when you try the Gradient Tool (differently from Brush Tool and perhaps from any other Tool on Tool Shelf / T-Panel) then that Symmetry Option just fails to work: Gradient Tool doesn't get automated Symmetry from this Symmetry Option as any other Weight Painting Tool gets. This issue doesn't occur when using Mirror Modifier (with only a one-sided Mesh character), so it looks like a behavior relating Gradient Tool and Symmetry Options specifically; maybe this bug would be a generic Gradient Tool in Blender on other \"painting\" Modes, and not just on Weight Paint Mode.\n\n\n\n\n\n\n[bug1.mp4](bug1.mp4)\n\n- Have some X-Axis symmetric Mesh Object centralized (better have enough Mesh Geometry on it). Note: don't Delete half of the model, as we don't want to create a Mirror Modifier.\n- Go to Weight Paint Mode,\n- turn ON X-Axis Symmetry Option,\n- try the different Weight Painting Tools from Tool Shelf:\nWhen it comes to Gradient Tool, it just ignores the Symmetry Option, while Tools like Brush Tool respect it as expected.\n\nPS: Those uploaded files are related to 3.2.0 version of Blender only.\n\n¡Thank you for checking and good luck!" ]

[ "Poisson Disk distribution method is uneven with selection mask\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.2.0\n\nPoint cloud is not decent, if using selection mask to *Point Distribution* node. Applying it directly to input mesh geometry makes distribution even.\n\nIn attached file mute/unmute *Separate Geometry* node to see how point distribution is performing.\n[point_distribution_problem.blend](point_distribution_problem.blend)", "Adding texture to particle emission density breaks particle simulation\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\nPlease see attached file, after adding cloud texture and enabling Density in Texture influences, the simulated particles either stick to the surface or fly of into infinity as a group. \n\nOpen attached file and play animation, note some particles either sticking or a large group of particles incorrectly flying of.[particle_system_broken.blend](particle_system_broken.blend)\n\n", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "Optix denoising is not working everywhere.\nOperating system:\nLinux : 5.6.0-0.bpo.2-amd64 #1 SMP Debian 5.6.14-2~bpo10+1 (2020-06-09) x86_64 GNU/Linux\nNvidia : Driver Version: 440.82 CUDA Version: 10.2\nCPU :AMD Athlon 2 with 8Gio RAM\nGPU: Nvidia Gtx 750 2Gio VRAM\n\nBroken: 2.90 dev master\n\nThe Nvidia optix denoising does not work on the entire frame. It just makes a circle denoised; the rest is denoised strangely. This results in a not efficient render.\n\n\nOpen Blender 2.90 master with startup config. In settings, change to device Optix, then in the scene, go into Cycles). Replace the cube by a plane. Add a material to the plane with 0.2 Roughness. Then remove the light and put the camera near the plane. Then, put the samples to 2 for render and view-port. Activate denoising with optix, and start a render preview in the view-port.\n[bug.blend](bug.blend)", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "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.**", "EEVEE-Next: Improve refraction denoising\nAs of now, the refraction rays reuse the same denoising pipeline as reflection rays. However this overblurs the results for low roughness.\n\nThis is because refraction lobe is dependent on IOR and roughness. So we need a way to compute the effective roughness of the glass based on its IOR and roughness.\n\nOne way to do that would be to fit a cone to the refracted lobe and try to match the reflective GGX roughness associated with a cone of the same angle.\n\n", "Eevee Alpha Blend artifacts in lookdev and VR with Viewport Denoising enabled\nOperating system: Windows 10\nGraphics card: Nvidia GTX 970\n\n\nBroken: version: 3.0.0 Alpha, branch: master (modified), commit date: 2021-07-26 13:54, hash: 3059853732d7\nBroken: version: 2.93.1, branch: master, commit date: 2021-06-22 05:57, hash: 1b8d33b18c2f, type: release\nBroken: version: 2.83.16, branch: master, commit date: 2021-06-15 08:46, hash: 051567553d29, type: release\nWorked: Unknown\n\n\n\nNavigation within a viewport (such as panning / orbiting the scene) with objects that have a material with Alpha Blend enabled results in visual artifacts for those materials, seemingly regardless of the alpha channel itself (i.e. it affects materials with an alpha of one).\n\nIn my case I first saw the artifacts while using the VR mode in blender where these artifacts feel extremely exaggerated in some cases. I have an environment with foliage billboards that appear like they are slightly head-locked and they sway around a lot when moving in VR. I later realised I could reproduce similar artifacts outside of VR and then realised that disabling denoising avoided the artifacts in the editor and in VR.\n\nIt seems that Eevee's denoising introduces some kind of latency related to how the alpha blending is handled which results in temporal, visual artifacts while the viewport's perspective is changing.\n\nI'd say the reproduction below probably doesn't represent how significant the artifacts feel in VR but I think it highlights the same underlying issue (the same two workarounds that affect the editor, also help in VR).\n\nTurn on Viewport Shading: Material Preview or Rendered\n\nDelete cube\nAdd plane\nAdd material (default principled BSDF is fine, though in my case I'm working with emissive shaders and I have a modified build of Blender supporting equirectangular image textures that let me access their alpha channel)\nSet material Base Color to an Image Texture.\nCreate a new image and generate a Color Grid to set as the base color. (with or without Alpha)\nSet material blend mode to 'Alpha Blend'\n\nGyrate/pan/orbit the viewport view. (Note the artifacts are related to the viewport navigation that needs to move around, and just moving/rotating the plane itself won't show artifacts)\n\n(For the Color Grid the artifacts mainly look like shimmering, and glints on the white letters. That's quite different to the original artifacts I saw in VR for my use case but still it seems to represent the same underlying issue.)\n\nUnder render properties, toggle Viewport Denoising and perform the same viewport movements to compare.\nWith Viewport Denoising back on, switch to using Alpha Clip instead of Alpha Blend and again compare.\n\n[eevee-denoise-artifacts.blend](eevee-denoise-artifacts.blend)", "Particle hair with density influenced by texture is (partially) invisible with cycles CUDA backend\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.0 up to latest (version: 3.3.0 Alpha)\nWorked: 2.9.3 (from memory since these blend files can no longer be opened)\n\nThe particle hair in the given example file does not show up properly when switching to rendered preview using GPU compute and CUDA specifically. Switching to Optix, or CPU render makes the hair appear shaded. With not showing up properly I mean that the grid lines behind the hair does get obscured (only very faintly visible in the screenshots), but they are clearly not shaded. Disabling texture density influence also makes the hair appear in the GPU compute and CUDA combination.\n\nI understand that the particle system is deprecated, but figured I might as well report this issue so it does hopefully not occur in the replacement.\n\n 1. Open the attached blend file. \n\n [hair_invisible.blend](hair_invisible.blend)\n 2. Make sure that CUDA is used as the GPU compute backend, and that the device is set to GPU compute.\n 3. Switch to rendered view.\n 4. Observe that the hair is only obscuring the grid lines, but not shaded. Next there are several possibilities.\n\n 5. Switch to CPU backend for cycles and observe that the hair appears.\n 7. Or, disable texture density influence and observe that the hair appears.\n\n 8. Reduce the children to 23 and observe that some part of the hair appears within some bounding box. Further reducing the children makes it appear and disappear occasionally until everything appears (as above) at 9 children.\n\n", "Clipping Region in blender v3.2 and up is causing a werid artifact\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003\n\nBroken: version: 3.3.1\n\nweird colorful noise when using Clipping region ALT+B\n\nit happens by simply using the clipping region, it happens in both object mode and edit mode\n\n**Diagnosis that I tried** (USEFUL NOTES{[F13703419](Untitled.png)} FOR FIXING THE PROBLEM)\nwhat is causing it?: \n- I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by \"viewport overlay smooth wires\" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part.\n\nis it gpu driver problem?\n- it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use\n\nWhat versions of blender does it happen in?\n- I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho\n\nP.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug \n\n\n\n\n\n\n\n[untitled.blend](untitled.blend)", "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 Node Editor Using nodes causes weird issues in sculpt mode.\nOperating system: Linux-5.15.0-48-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.76\n\nBroken: version: 3.3.1\nWorked: perhaps never? (can redo in 2.83)\n\nAdding an image from the nodes of the texture editor for example, a sculpting brush, causes really weird issues. Disabling nodes and using the texture properties does not have this issue.\n\n- Check the blend file. Try sculpting, you will see weird noise being displaced with the texture.\n- Now disable the nodes and set the texture type from the texture properties to the same image. Sculpting again you see the issue is not happening.\n[bug.blend](bug.blend)\n\n\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", "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" ]

[ "Recent halo fix appears to bug out with glare node and NLM denoising\nOperating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: Radeon RX Vega (VEGA10, DRM 3.23.0, 4.15.0-50-generic, LLVM 7.0.0) X.Org 4.5 (Core Profile) Mesa 18.2.8\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\nProbably worked ok prior to the de-noise halo fix.\n\nDestroyed render in some cases when using compositing glare node (fog glow high, mix 1, threshold 5, size 9) on denoised image. Using the noisy image output gives expected results. I doubt only the glare node is affected, but I didn't check.\n\nIn attached file, hit F12 (render) and get the attached result.\nMy startup.blend is very custom with tons of math library and texture stuff, but all this is purged.\n[BuggyHaloFix_UsingNoisyImageForGlareNodeIsOk.blend](BuggyHaloFix_UsingNoisyImageForGlareNodeIsOk.blend)\n\n" ]

[ "Optix fails when geometry nodes instance has animated translation and scale 0 and motion blur is on\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18\n\nBroken: version: 3.6.0 Alpha\nAlso broken in 3.4.1\n\nRendering will not start. It stops at \"Building OptiX acceleration structure\"\n\n\n\nThe culprit seems to be a combination of animated Translation and Scale 0 together with animated Rotation of the object and motion blur.\n\n\n\nDoesn't work in OptiX. Cuda and CPU both work.\n\nOpen the .blend file and render the frame.\n\n", "Nodes: Changing Input position with a Driver\nBroken: 3.1 and 3.2 Alpha\n\nIn Geometry Nodes editor, shift an input socket above a socket having a Driver and it will switch the Driver.\n[2022-03-12 15-58-02.mp4](2022-03-12_15-58-02.mp4)\n\n- Enter Group Node\n- Shift \"Vertices Y\" input above\n[Test.blend](Test.blend)", "Dynamic paint sub-steps don't work when the brush position is set in geometry nodes\n\nI believe this **may** be the same issue as T40597\n\nIn order to have a brush follow a potentially very large collection of curves in sequence, I'm using geometry nodes to set the position, which avoids the pain of having to join the curve paths or painstakingly tweak the offsets and influence keyframes for each and every one.\n\nThis works, but with sub-steps enabled it seems that the nodes are still only being updated once/frame. Or, if they are being updated, then the `seconds` input from the `Scene Time` node is being derived from the `frames` value which is clamped to an integer.\n\n\n[text_path_test.blend](text_path_test.blend)\n", "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", "Materials linked to the object's data are lost when removing attributes from instances in geometry nodes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nMaterials linked to the object's data are lost when removing attributes from instances in geometry nodes.\n\n1.Instance a collection using geometry nodes.\n2.Remove an attribute from the instances (the attribute doesn't need to exist).\n3.Materials stored on the object data are now lost.\n\n\n[BugExample.blend](BugExample.blend)\n\n\n", "Color Attribute not affecting \"bump\" shader node\nOperating system: Windows 10\nGraphics card: RTX 3080\n\nBroken: 3.50 beta (03 March 23)\n\nUsing a mesh's color attribute as an input to the \"bump\" shader node does not result in the expected behavior. Using the color attribute for practically every other value (including the normal map node, roughness, metalness etc.) works as expected.\n\nCreate a mesh and paint a color attribute with, for example, a black-and-white pattern.\nGive the mesh a material and add the color attribute.\nPlug the color attribute into the \"height\" input of the bump node, and view the result. There is no difference compared to the \"height\" input being left disconnected.\n\nOther inputs (such as a noise texture) result in the expected behavior.\n\n", "Set Material Index node does not work on some GN-created geometry\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 537.13\n\nBroken: version: 3.6.2\nWorked: Never.\n\nThe scene contains 3 objects:\n1. Mesh object with GN which creates Mesh Cube primitive\n2. Curve object with GN which creates Mesh Cube primitive\n3. Curve object with GN which creates geometry using Curve to Mesh node\n\nAll 3 objects have their Material linked to Object, not Object Data\n\nThe Set Material Index node works on 1. and 2. but does not work on 3.\n\n1. Open the attached blender file: [curvematerialbug.blend](attachment)\n2. Check Geometry Nodes setups on all 3 objects\nResult: Set Material Index Node does not work on Geometry generated by Curve to Mesh node.\nExpected: Set material Index Node works on any geometry.\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)", "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.", "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", "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", "Cycles: Refraction shaders work incorrectly with normals as mesh attributes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: Last main.\nWorked: Never?\n\nNormals created as Normal input node in Geometry Nodes. Captuted on mesh and saved as named attribute.\n- Dot product return 1.0f (~+some error) result for shader Geometry normals and named attrbite.\n- Distance between shader Geometry normals and named attribute is 0.0f.\n\nBoth normals are the same (?). But shader node produce different results for both kinds:\n\n| Normals | Refraction materials |\n| -- | -- |\n|  |  |\n\nSee attachet example file.\n\nFrom scrath:\n1. Create mesh with Geometry Nodes modifier.\n2. Connect Normal input node to output of Geometry Nodes modifier node tree.\n3. Set the name for modifier output.\n4. Appy modifier.\n5. Add Material.\n6. In material, create Geometry input node and Named Attribute.\n7. Add Refraction Shader node and try to put both normals and see results.", "Geo Nodes crash, when updating old node group with new (using user_remap()) \nOperating system: Linux-5.15.21-1-MANJARO-x86_64-with-glibc2.33 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.47.03\n\nBroken: version: 3.1.0 Beta\nWorked: I think it always crashed\n\nLets say I have two geo nodes: **old_node** group and **new_node** group. I want to update old to new using python:\n\n```\nold_ng.user_remap(new_ng)\n```\n\n\nBlender will crash after running code above, if scene has Cube object with geonodes modifier that uses **old_ng**. Crash happens only if modifiers tab is visible, and you re-select the cube. It wont crash, if new nodegroup does not have additional input.\n\n1. Run script from attached blend file ( it remaps old_ng to new_ng) \n2. re-select 'CubeOld' object. Blender will crash\n\n [gn_update_crash.blend](gn_update_crash.blend)\n\n", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n", "python display_shape don't work in GeometryNodeTree\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 496.76\n\nBroken: version: 3.1.0 Alpha\n\nWhen adding a custom node with custom socket to the GeometryNodeTree you can't alter the display_shape of the socket and the bpy.types.NodeSocketFloat or any socket type doesn't matter when connecting nodes it always stay red.\n\n\nAttached a blend file with the script for quick testing\n[tst.blend](tst.blend)\n\nThis is not a problem in the Shader or Compositing editors:\n\n" ]

[ "Material set to default on Remesh modifier after geometry nodes modifier primitive object and set material\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51\n\nBroken: version: 3.3.0 Alpha\n\nWhen you use the remesh modifier after a geometry nodes(GN) modifier where the GN is made from a primitive and a material is set on it, the remesh modifier will not keep the set material, instead it will revert to the default material.\n\nAlso, interestingly enough it only happens when material is set on a geometry node primitive. And the material is kept when the original input geometry is fed through the geometry node modifier.\n(there is a work around to make a GN after the remesh modifier, however is impractical. And I don't know if doing this is how it was intended to work)\n\nOpen attached blend file [Blender Remesh and Material Bug.blend](Blender_Remesh_and_Material_Bug.blend)\nturn on and off the remesh modifier visibility in the viewport\n\n\n\n\n\n\n\n\nThanks Blender Developers!! What you do is so cool! Have a nice day", "Applying Geometry Nodes modifier creates a new empty material slot on the resulting mesh\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 496.76\n\nBroken: version: 3.1.0 Alpha\n\nIn some circumstances, when applying GN modifier or converting GN object to mesh, this operation will add a new, empty material slot on the top of the material slot stack. This creates significant issues when exporting GN-generated object to external game engines, where proper material assignment relies on consistent material slot order.\n1,\n\n2,\n\n3,\n\n1. Open the attached .blend file: [MatSlotBug.zip](MatSlotBug.zip)\n2. Observe there is only one material slot on the object and it contains the same material which is assigned through GN.\n3. Apply the GN modifier on the object\nResult: Applying the GN modifier adds a new, empty material slot on top of the material slot list\nExpected: Applying the GN modifier does not cause creation of new, empty material slots.", "Set Material Node does not reuse existing empty slot\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\nIf I set material with Set material node, it will not appear after remesh modifier.\nNo matter if i set material to initial instance or to final geometry after Realize node.\nHere the file for tests and demo\n[remesh after GN.blend](remesh_after_GN.blend)\n\n\n\n[2021-11-29_01-09-32.mp4](2021-11-29_01-09-32.mp4)\n\n[2021-11-29_01-13-43.mp4](2021-11-29_01-13-43.mp4)\n\n", "Solidify in Complex mode prevents display of materials assigned to generated geometry\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.2.0 Alpha\nWorked: N/A\n\n*Solidify*modifier in *Complex*mode prevents showing of materials assigned (via *Set Material*) to geometry generated inside Geometry Nodes. There are two exceptions I noticed:\n\n - Materials do show if you have at least two materials slots on the object. They don't need to be filled, just exist as slots.\n - Materials do show if you use either a *Duplicate Elements* or a*Geometry to Instance* node before *Set Material*.\n\nHere's a video demoing the situation and the two exceptions:\n\n[20220415190922.mp4](20220415190922.mp4)\n\n \n\n - In the attached file, create a second material slot; red color should show.\nor\n - In the attached file, link either *Duplicate Elements*or *Geo to Instance* output to the *Set Material* node; red color should show.\n\n[Bug_GN_SolidifyComplex.blend](Bug_GN_SolidifyComplex.blend)\n\n", "Remesh modifier after a Geometry Nodes modifier destroys the material\nOperating system: Win 10\nGraphics card:\n\nBroken: 3.2.0 fc259d4c30cb\n\n\nAdding a Remesh modifier destorys the materials either coming from a geonodes material assigment or from the object's own material assignments, makes itt impossible to assign a material.\n\n\n[blender_z5bz6pFiOX.mp4](blender_z5bz6pFiOX.mp4)\n\nLoad the attached .blend file\nEnable and disable the remesh modifier to see what happens with the material\n\n\n[no_mat_15032022_1156_53.blend](no_mat_15032022_1156_53.blend)\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", "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", "(Unneccessarily) restricted execution in scripted expression drivers (using e.g. \"self\", \"bpy.data\")\nOperating system: Linux-5.15.0-69-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.2.5\n\nBroken: version: 3.5.0\n\nself causes error in scripted expression drivers\n\nIn scripted expression drivers using expression \"self.location.x\" from Blenders manual and \"self.location[0]\" from online examples both fail with \"ERROR: Invalid Pythpn expression\".\nI have enabled \"Use Self\" in driver and \"Auto Run Python Scripts\" in preferences\n\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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "\"Illegal address in CUDA queue\" error occurs when I use both Principled BSDF and Adaptive Subdivision\nOperating system: Windows 11 Pro 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\n\n-**\"Illegal address in CUDA queue\"** error occurs when I activate both Principled BSDF and Adaptive Subdivision at the same time.\n-It would work fine if I don't use both at the same time.\n-Here are the possibilities of the error occurring when I use different settings:\n1. Principled BSDF + Adaptive Subdivision = **error**\n2. Texture Coordinate surface + Adaptive Subdivision = **no error**\n3. Principled BSDF + NO Adaptive Subdivision = **no error**\n\n-I can use a high poly count without Adaptive Subdivision *(e.g. Level viewport = 7)*, works fine. But as soon as I turn it on *(even with low poly count, e.g. Dicing scale = 1)* combined with Principled BSDF, the error occurs.\n\nIn the file I sent, I've already activated Principled BSDF + Adaptive Subdivision, you need to turn on the \"Rendered Viewport Shading\" and then slide the Scale parameter of the Noise Texture very quickly and the error should occur.\n", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software.", "CYCLES abnormally high graphic memory usage on RTX 4090\nOperating system: WINDOWS 11 Professional\nGraphics card: RTX 4090\n\n[blender_system_info.txt](blender_system_info.txt)\n\n3.3.1\n\nCYCLES used too much graphic memory (19GB) for a simple scene that only included 6 characters made by Character Creator 4. And \nstop rendering due to \"System out of graphic memory\" when the viewport uses cycles at the same time\n\n\n\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n- Download .blend file bellow\n- Render (key {key F12})\n- Compare VRAM of RTX 4090 vs RTX 3080\nview?usp=sharing", "USD: Crash when loading the Intel Moore Lane demo asset (related to Color Attributes)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nBroken: version: 4.0.0 Alpha\nWorked: version: 4.0.0 Alpha\n\nCrashes during import of the Intel 4004 Moore Lane asset. Seemingly related to Color Attribute processing though the stack traces for the crash are not related.\n\n- Download the \"4004 Moore Lane v 1.1.0\" asset: 4004-moore-lane/\n- Attempt to import the `USD\\4004MooreLane_III_03_ASWF.usd` file with default settings --> observe crash\n- Attempt to import the same file but with the \"Color Attributes\" option unselected --> works\n\nOddly, the crashing stack occurs inside tbbmalloc and while seemingly dealing with mesh normals...\n```\n...\ntbbmalloc.dll!00007ffd7fa29f4e()\tUnknown\nblender.exe!MEM_lockfree_mallocN_aligned(unsigned __int64 len, unsigned __int64 alignment, const unsigned char * str) Line 310\tC\n[Inline Frame] blender.exe!blender::GuardedAllocator::allocate(unsigned __int64) Line 47\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::allocate(__int64) Line 425\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::get_buffer_for_size(__int64) Line 419\tC++\n[Inline Frame] blender.exe!blender::Array<blender::VecBase<float,3>,4,blender::GuardedAllocator>::{ctor}(__int64) Line 122\tC++\nblender.exe!blender::bke::mesh::mesh_normals_loop_custom_set(blender::Span<blender::VecBase<float,3>> positions, blender::Span<blender::VecBase<int,2>> edges, const blender::offset_indices::OffsetIndices<int> faces, blender::Span<int> corner_verts, blender::Span<int> corner_edges, blender::Span<blender::VecBase<float,3>> vert_normals, blender::Span<blender::VecBase<float,3>> face_normals, const bool * sharp_faces, const bool use_vertices, blender::MutableSpan<blender::VecBase<float,3>> r_custom_loop_normals, blender::MutableSpan<bool> sharp_edges, blender::MutableSpan<blender::VecBase<short,2>> r_clnors_data) Line 1368\tC++\nblender.exe!blender::bke::mesh::mesh_set_custom_normals(Mesh * mesh, float[3] * r_custom_nors, const bool use_vertices) Line 1642\tC++\nblender.exe!blender::io::usd::USDMeshReader::process_normals_face_varying(Mesh * mesh) Line 797\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh_sample(blender::io::usd::ImportSettings * settings, Mesh * mesh, double motionSampleTime, bool new_mesh) Line 853\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_mesh(Mesh * existing_mesh, USDMeshReadParams params, const char * * __formal) Line 1094\tC++\nblender.exe!blender::io::usd::USDMeshReader::read_object_data(Main * bmain, double motionSampleTime) Line 249\tC++\nblender.exe!blender::io::usd::import_startjob(void * customdata, bool * stop, bool * do_update, float * progress) Line 288\tC++\n\n```\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", "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)", "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", "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", "Installation fails when desktop permission to write is denied\nOperating system: Windows 10\nGraphics card: N/A\n\nBroken: 3.6 lts\nWorked: Unknown\n\n**Short Description**\n\nBlender setup error : An error occurred while attempting to create the directory DESKTOP_PATH\nOptions are Retry or Cancel.\nSelecting cancel give a confirmation prompt and then rolls back the installation.\n\n- - -\nI do not want every program I install to create icons on my desktop so have remove permissions to prevent this which is why this error occurs. Even so setup should not fail simply because a desktop Icon can not be created.\n\n", "Sequencer Render does not render overlays and always uses original media\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\nBroken:\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` blender-2.91.0-010c1370aff6-windows64` (BF Build Bot)\n\n\nClicking Sequencer Render will not render the image as set in the sidebar view settings like: Show Overexposed, Safe Areas or Proxies don't work.\n\n\n\nTrying to render proxies:\n\n\n - Open and Viewport render\n\n\n[Render_Proxy.zip](Render_Proxy.zip)" ]

[ "Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array prefix_sum)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.0.0 Release Candidate\nWorked: 2.8\n[The following error pops up when trying to render out my animations in PNG format. \n\"[DEVIN _TATTOO.blend](DEVIN__TATTOO.blend)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n{[F13341200](blender_debug_output.txt)}\"]\n\n[Render out an animation. Sometimes it renders 9 frames, sometimes 20, sometimes 40, but the error above stops the rendering process until I quit and restart. I have attached the debug files as well as the blend file. I have updated GPU drivers many times, but to no avail.]\n\n\n", "Illegal address in CUDA queue copy_from_device.\nOperating system: Windows 10 Pro\nGraphics card: RTX 2080 Ti\nCPU: i9 9900K\nRAM: 32 GB DDR4 3600 MT/s CL 16\n\nBroken: All that I have tried. Currently using 3.1.\nWorked: None.\n\nDuring rendering of animation it randomly gets this CUDA address error. I then have to restart Blender for it to work again. This stops the render and also messes with the viewport too.\n\nStart rendering. Random error somewhere.\n[GrievousGround.blend](GrievousGround.blend)\n\nI will also add that the computer is completely stable in all other applications and games. CPU temperatures max out at around 65 C and GPU temperatures max out at about 40 C as the whole system is liquid cooled.", "Illegal address render error\n{[F13505239](room3.blend)}Operating system: Windows 10 build 19044.2006\nprocessor: 3900x 32 gigs ram\nGraphics card: gigabyte windforce 2070 8 gig (not a super)\n\nBroken: 3.2,3.0\nWorked: going back to blender 2.8 seems to work, but it effectively is a different renderer and it would take my machine days to render one image so I cannot effectively test this..\nDuring render application stops rendering with error \"Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths array prefix_sum). I've tried reverting to 3.0 and 2.8, reducing the poly count in any way I can, and so on. Nothing has worked, if anything the problem has gotten worse. It used to make it almost 2k cycles before dying now it stops somewhere round 1k and occasionally at 100 or less.\nBased on the default startup or an attached .blend file (as simple as possible).", "CUDA errors\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 517.40\n\nBroken: version: 3.3.0\n\n1- While making a render using cycles randomly occurs errors — \"Illegal address in CUDA queue copy_from_device (inntegrator_intersect_closest integrator_queued_paths_array)\"\nAfter that If I close rendering window and try to change engine \"cycles\" –> \"eevee\" –> \"cycles\" the viewport doesn't change and error reads — \"Failed to create CUDA context (Illegal address)\"\n\n2- Sometimes it occursin the vieport while using cycles and making amendmends in shader editor.\n\nTried different drivers and benchmmarks. Outside Blender there are no error or problems. It occurs in different files and randomly\n\n", "GPU rendering error: Illegal Address in CUDA queue copy_from_device\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.1.2\n\nI've been using blender for a few months now. And recently I got a PC with an Intel i5 12600k and a Gigabyte 3070 Ti (I do a lot of video work and gaming too). Everything works fine with the games(such as getting high fps and all) but when I use blender is when the problems arise. All the modelling and texturing works fine, but when I go into rendered view with my GPU Compute (and CUDA selected in my edit>preference>system tab with my graphics card checked) on, the rendering in the viewport starts but always ends but freezing and with an error message of Illegal Address in CUDA queue copy_from_device (integrator _shade surface integrator_sorted_paths_array prefix sum). This happens for complex projects with different textures, as well as for a simple project with the default cube only.\n\nBut when I switch to CPU with no other settings changed, the render completes itself in the viewport. And if I change it back to GPU compute, the screen turns completely grey and another error message appears - Failed to create CUDA context (Illegal address).\n\nThis is the same in the case of OptiX as well, when in CPU in the cycles menu, it works completely fine, but as soon as I switch to GPU compute, the screen turns grey with the same message - Failed to create CUDA context (Illegal address).\n\nI've done quite a few things such as looked for the newest drivers for my Graphics card and updating them regularly, and I have opted for the Studio drivers over the Game drivers as well. I'm currently running on blender 3.1.\n\nThis happens on the test blender files that we find on the internet as well, so I guess no steps are required to reach it in my system. It just happens as soon as render in the viewport with GPU.\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).", "Measure tool multi 3dview and quad view inconsistencies\nUbuntu 20.04 5.4.0-48-generic\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBlender 2.91 master build from 8335c26119bf5ba78b2afa4e2f65bb3d04b42abe\n\nMeasure tool multi 3dview and quad view inconsistencies\n\nOpen default scene. Enable Measure tool in toolbar and add a measurement.\nEnable quad view with ctl+alt+q.\nGo to top view and adjust measurement. Do not do anything else.\nDo the same with front and side view, you now have 4 different measurements visible.\nYou can zoom, move and rotate views and you still have 4 measures, but if you select an other object it will change to the last adjusted measurement.\nSame if you split 3dview.", "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", "Walk navigation stylus issues in 2.92 - no mouse input until alt tabbing (regression)\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.92.0 Alpha\nWorked: version: version: 2.91.0 *\n\nWalk mode seems to be a bit broken in 2.92 alpha (with both mouse and wacom tablet)\n- The issue only happens if Walk mode is entered via keyboard shortcut\n- alt tabbing out and back into the blender seems to fix the mouse lock\n\n\n*Important note:\nI noticed that this issue is a bit less severe in an older 2.92 build !!2.92.0 Alpha!!, there was still an issue where wacom stylus had to be lifted from tablet surface and placed down again in order for blender to start registering mouse movement in walk mode. (The mouse worked fine, this is pen tablet only issue)\n\n**Here's a short video demonstrating issue**\n- Example 1: Blender 2.91 hash: `0f45cab862` - Works as intended\n- Example 2: Blender 2.92 hash: `c1740e9ad0` - Works BUT only if stylus is lifted from screen (note stylus diagnostic screen on right side)\n- Example 3: Blender 2.92 hash: `acbda123ad` - Only works if user alt tabs from the window itself\n[2021-01-13 00-09-24.mp4](2021-01-13_00-09-24.mp4)\n\n\n- Default document\n- 3D Viewport > View > Navigation > Walk Navigation - Assign a keyboard shortcut (eg: Shift + F)\n- Press the previously defined shortcut\n- Walk mode crosshair appears but mouse is locked\n- Alt tab out and back into blender\n- Now walk mode works ", "Scrollbar of Clip Editor's Graph and Dopesheet View does not update\nOperating system: elementaryOS 0.4.1\nGraphics card: GTX 1080\n\nBroken: 2.80, 58bfe93db614\n\nWorked: apparently never...\n\nIf you change the endframe of your scene, the scrollbar in the Clip Editor's Graph and Dopesheet view does not reflect the changes.\n\nOpen startup .blend\nGo to Motion Tracking Layout.\nSet Endframe to 1000.\nNotice how the scrollbar down in the Graph View of the Clip Editor does not change its length.\nNow try the same with any other Animation Editor, for example in Animation workspace\nIf you set the endframe to anything that makes the scene longer, the scrollbar will update accordingly and become shorter, indicating that you do not see the full range of your scene.", "Tooltip for the Drag tool setting\n## Issue\nRecently for Blender 3.0 the \"Drag\" option in the header tool settings was included for most active tools. This allows right click select users to make use of this feature by using the option \"Right Mouse Selection Action = Selection Tool\" in the keymap preferences.\nThe issue is that these options still have no tooltip so it can be hard to understand how or why to use this feature.\n\n\n\n### Proposal\nWe need a simple tooltip with the following information:\n\n- General information\n- Sub Tooltip (From what it is currently set to)\n- Shortcut of the Pie Menu for quick access\n- Context sensitive information based on keymap settings (right or left click select)\n\nSo this would be:\n\n> Action when dragging anywhere in the editor with left click: Select Box\n> Select items using box select.\n> *Shortcut: Alt + W*\n\n\nOr when right click is used in the keymap preferences:\n\n> Action when dragging anywhere in the editor with right click: Select Box\n> Select items using box select.\n> *Shortcut: Alt + W*.\n\n\n## Related issues\n\nThe tooltip for the setting \"Active Tool\" needs to be changed. \nIt currently says:\n> Action when dragging in the viewport: Active Tool\n\n\nIdeally this would be changed to something that fits the other options.\n\nAnother thing to keep in mind is that the tooltip Tweak for tweak on right click select is still \"Set the location of the 3D Cursor\".\nThis is since recently wrong and needs to be updated. \n\nAlso there are never shortcuts for pie menus mentioned in tooltips so far, even though they are heavily used.\nPie menu shortcuts that also aren't mentioned are for example: `Tab` for modes, `Z` for shading, `.` for Pivot Point and `,` for Orientation.\nThis can be handled as a separate task: #92478", "Cutter Tool Not Working When Lines are Drawn with the Draw Tool Using Guides\nOperating system: Windows 10\nGraphics card: Gigabyte GeForce RTX 3080\n\nBroken: 3.5.1\nWorked: Never tried it in older versions\n\nI use the Guides function to draw in perspective; however, the Cutter tool won't cut the lines correctly when the Guides function is used to draw the lines. Sometimes, it cuts them oddly. Most of the time, it doesn't cut them at all. When I use the Draw tool and manually draw in perspective (without using the Guides function), the Cutter tool works fine. \n\nStrokes drawn with \"guide\" options are not cleared in some cases with cutter tool\n\n- Use the Cutter tool on these to cut the lines from the intersections. I've named the layers appropriately.\n", "Current value 0 matches no enum in error with creating a new keymap from Industry Compatible or Blender 27x keymap\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.1.0 Alpha\n\nWhen you create a new keymap from the industry compatible keymap or the Blender 2.7x keymap, then you get errors in the console about this and that operator does not match current value 0 in enum ...\n\nRelated task: T92754\n\n\n\n- Open Blender\n- Open Preferences\n- Switch to Industry compatible Keymap\n- Create a new keymap\n- Watch the console\n- Repeat with the Blender 27x keymap as the base ...\n\n\n\n\n\n\n\nEDIT, the params.action_mouse parameter could be the cause.\n\n\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", "Curve extrude offset default value is 1 (instead of 0)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon RX 5500M ATI Technologies Inc. 4.5.13587 Core Profile Context 19.40.30.02 26.20.14030.2002\n\nBroken: version: 2.93.0\nWorked: -\n\nCurve > Object Data Properties > Geometry > Offset\nIf you reset the \"Offset\" value with right click+*Reset to Default value* or by pressing backspace the value is set to 1\n\n - Open blender\n - Create a curve\n - Extrude it\n - Reset the offset to the default value\n - Offset is set to 1 instead of 0\n\n**Expected behaviour**\nThe default value for this should be 0. If a curve is created the value is 0 without any changes\n\n[curve reset offset.blend](curve_reset_offset.blend)\n", "Grease pencil brush sizes incorrect\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.92.0 Beta\n\nGrease pencil brush sizes are not accurate, not even close. A 500px radius(!) size brush (which should be 1000 pixels wide since we're talking about a \"radius\") has actually about a 50px radius.\n\nOpen a new 2D animation file, increase brush size to the max of 500px, draw a line. Does that look like 1000pixels wide to you? Or ist it me? Maybe I need to work all the way zoomed into the canvas to see the accurate size? How big is the factory canvas?\n\n", "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", "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.", "GPencil: Brush and stroke size related issues\n**Description**\n\nWhen drawing in grease pencil, control over the brush size and the thickness of the stroke is of course extremely important. Currently, there are some inconsistencies and confusing behavior that need to be addressed. Here is a list of current issues and some new proposals.\n\n - **Brush Radius:** Currently, the brush size can be changed via this slider in draw mode.  The name displays \"Radius\" and the tooltip reads \"Radius of the brush in pixels.\", but this is not consistent with the thickness of the strokes. If the user sets the **radius** to 100px and the *Stroke Thickness* option in the object data properties is set to *Screen Space* the stroke has a **diameter** of 100 pixels. If the *Stroke Thickness* is set to *World Space* the stroke has a **diameter** of 0.1 meters. A simple solution is to change the UI name from \"Radius\" to \"Size\" and clarify in the tooltip that the thickness or diameter of the stroke is meant.\n - **Radial Control:** When the user changes the brush size via the radial control (shortcut {key F}) the control has a **radius** of the given pixel value, not (like mentioned before) a **diameter** of the pixel value set.  \n - **Brush size in World Space** When the *Stroke Thickness* in the object data properties is set to *World Space* the displayed thickness of the strokes in that grease pencil object are calculated via the following formula: `((line_change + stroke_thickness) * pressure * pixel_factor) / 1000.0f` E.g. when all adjustment values are set to their default value then **1px (stroke thickness) = 1mm (world space)**. Currently, there is no way for the user to know this. The UI gives no indication of this and the manual also does not mention it. A possible solution is to change the units of the brush from pixels to meters and also do the right conversion so that the size is correctly displayed in the UI.\n - **Drawing in screen space/world space:** The user can change the stroke thickness (screen space/world space) in the object data properties. That means that *all* strokes in the grease pencil object will be either drawn using the screen space thickness in pixels or the world space thickness in meters. But there is currently not a way to choose the brush size to be in screen or world space. In sculpt mode, the user can choose the brush size \"reference\" (Radius Unit).  This would also be useful for grease pencil. \n # **Brush size indicator:** At the moment there is no visual feedback on how big the current brush is. A solution could be a \"ring\" around the cursor and deactivate it during drawing so it only shows up before starting the stroke.\n\n---\n**Related reports:**\n#83675, ", "\"Input Pending\" for Loop Cut and Slide when called from menu.\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 1660Ti\n\nBroken: 3.3.2\nWorked: 2.93\n\n**Caused by:** da2ba402689d7ed752b0b37ad49dce1a5851cc77\n\n**Reproducing the error:**\n\n- Ctrl+R on default cube edit mode, regardless of selection mode, loop cut slide works as usual.\n- Use search menu or header->edge menu and select loop cut slide, header bar only shows \"Input Pending\", if pressed left mouse, then operator runs correctly. If pressed right mouse, then operator is cancelled.\n\n\n\n" ]

[ "CTRL+C does not copy ruler value like it says in documentation\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 24.20.100.6194\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nOfficial documentation claims that pressing CTRL+C will copy a ruler's value.\nI was unable to reproduce this result.\n\n\nFailure 1 (Edit mode):\n\nCreate any mesh object.\ntype `t` to open the tools.\nSelect measuring tape tool.\nclick close to a vertex to snap the measuring tape's first point to it.\nhold `CTRL` and click near another vertex to measure the distance between them.\nYou get measurement.\nPress `CTRL+C`.\nAttempt to paste this value in a field. It will fail regardless of what mode you are in.\n\nFailure 2 (Object mode):\n\nVerify that this fails in object mode as well by measuring any space in object mode and as soon as you see the measurement, press `CTRL+C`. Attempt to paste this value in a field. It will fail." ]

[ "volumes breaking data passes\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: 4.0.0 Alpha\nWorked: never\n\npixel data for surface data passes and shader AOV's are rendering black if there's a volume.\n\n\n1. Open attached file\n2. go to compositor\n3. render frame\n4. check the data and aov passes\n\nexamples:\n\n\n\n\nI understand it's necessary for the volume to affect the colour passes that build the combined pass, but for data passes and custom AOV's that only represent the surface, it would be useful for that data to not be obscured. For example if you want to replace textures in comp, or add vector motion blur to an object which is behind a volume etc. I think rule of thumb should be, if something doesn't have that type of data, then it shouldn't affect passes of that type of data.\n\nIt makes it impossible to make use of the data otherwise, forcing the user to render twice. Perhaps data and custom AOV's could have exclude lists where users could specify which objects shouldn't have any influence on the pass? Would be nice to have that on the environment pass too, so shadow catchers wouldn't mask the environment?\n\n", "Reflection plane significantly reduces intensity of normal maps on affected surfaces\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU\n\nBroken: Currenct main.\nWorked: Never.\n\nWhen a reflection plane capture is added to any scene in EEVEE, the resulting reflections on surfaces affected by said capture will be significantly less affected by shader-based normal maps.\n\nComparison:\n| Without a Reflection Plane | With a Reflection Plane |\n| -- | -- |\n|  |  |\n\nThis is unexpected behavior, and although I do not fully know the intricacies of how the reflection plane capture functions, it would ideally not affect surfaces in this way.\n\nOpen the included demo file and switch to rendered view.", "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 ", "Holdout Fill not working as expected with Grease Pencil\nOperating system: Win 10\nGraphics card: Nvidia GTX 1060\n\nBroken: 2.93\nWorked: unknown\n\nI would expect holdout fills to render as 100% transparent. In Blender's image viewer, they don't - their opacity seems to change based on how bright they are, so white is 100% opaque, but grey is semi-transparent.\n\nSaving the same image to a PNG file, the holdouts are fully transparent, but with aliased artefacts around the edge of the surrounding black strokes, in the colour of the holdout fill. If there is another grease pencil object positioned behind the holdout fill, instead of vanishing, its strokes are tinted the colour of the holdout fill.\n\n\n(The artefacts are more noticeable against a dark or checkered background.)\n\nTry rendering the simple drawing in the attached .blend, exporting a PNG and examining it in an image editor. [holdouttest.blend](holdouttest.blend)", "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)", "4.0A producing specular reflections of area lights on diffuse surfaces, 3.6.1 doesn't behave this way.\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.1 & 4.0 Alpha\n\nArea lights in 4.0 Alpha producing specular reflections on diffuse only (specular = 0) surfaces in 4.0.\n\nI tried to report this discrepancy to the developer forum but can't seem to post it there, so I figured maybe whoever monitors this could help. \n\nIn 3.6.1, if a material has no specular component, area lights only produce diffuse illumination. But in the 4.0 alpha (build downloaded 8/14), the area light produces a specular reflection. I don't know if this is a new intentional development thing, or if it's somehow related to the light linking feature.\n\n", "Optix Viewport Denoiser Makes Objects Glow When Using High Exposure Even When There is no Light in the Scene\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce MX130/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\n\nThe latest build added the feature to let non-RTX GPUs use the denoiser, so I tested it on my scene right away. However, the objects in the scene start glowing when the denoiser starts working. The scene was lit using the Physical Lights feature that the Photographer 3 addon has provided, which offers units like Lumen and Candela, etc. And since physically correct light values can sometimes be very dim (like a candle = 1 candela), sometimes be very bright (like the Sun at noon 111,000 lux), Photographer offers real life camera's settings for modifying the exposure in the color management in the render settings to adjust the overall brightness. And in my scene, I used a candle, which is very dim. Therefore the exposure has been set very high. It has been fine until the denoiser came. \n\nBased on the default startup\n1. Delete the default point light\n2. Turn the World Background Strength to 0\n3. Turn the Exposure in the Render Settings under Color Management to 10\n4. Change the render engine to Cycles\n5. Turn on render view, you should see nothing but complete darkness\n6. Turn on the Optix Viewport denoiser\n7. Wait for a while and see the default cube glowing\n\nI don't know if this is a bug or not, if it is not, please at least get some work around. Like making the denoiser refresh when the exposure changes or something?\n\n", "Hidden Particle paths draw solid [2.79 draws them half transparent]\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 15)\nWorked: (optional)\n\nComparison of particle hiding Blender 2.81 beta and 2.79. I wrote earlier that the particles are not hiding, and this is so fixed?\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", "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", "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)", "Cycles Bake Selected to Active with transparency gives undesirable results\nSystem Information:\nOperating system: Windows-8.1-6.3.9600 64 Bits\nGraphics card: GeForce GT 635M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\nBroken: version: 2.81 (sub 16)\n\n\nBug or unintended behavior:\nBaking using \"Selected to Active\" does not take into account transparency \n\nHow to reproduce:\nCreate two objects with materials and textures assigned to each;\n```\n One texture to be baked to\n One texture with an alpha channel (optionally a normal map)\n```\n\nIn the shader editor, modify the material of the object with a transparency channel\n```\n Join the transparent textures' alpha into the alpha of the shader that is being used\n (optionally join the color of a normal map)\n```\n\nIn render properties, enable Selected to Active and use an appropriate ray distance\n```\n Finally bake.\n```\n\nResult:\nWhen baking combined or most channels, the transparent areas will assume the color as if it were completely opaque,\nWhen baking normals with transparency, the transparent areas will mix with the normal of the geometry that is being baked to the active selection.\nBoth outcomes are unfavorable when working with transparent cards/ribbons.\n\n[bugreport.blend](bugreport.blend)\n\nI packed the textures edited the project to make the issues that I am having more clear.\n\n{[F8286028](image.png), size=full}\nThere are now 3 overlapping objects with transparency.\nAfter baking normals or color, none of the colors or normals behind the transparent objects appear because the object appears to draw over top without transparency.\nThis example also shows that with full normal transparency, the normal will then be the geometry normal of the object rather than a flat normal or anything that is below the object.", "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", "Grid lines showing up when origin is far from mesh\nOperating system: Win 10 Home\nGraphics card: GTX 1070\n\nBroken: (example: 3.2.1, a2d59b2dac9e, master, 2022-07-05, as found on the splash screen)\n\n\nGrid lines showing up when origin is far from mesh but only when bumping out the normals in the shader editor, more testing required. (only happens in cycles regardless of optix/cuda or cpu rendering)\n\nopen the attached blend file and go to camera view, then switch to viewport shading or render an image. you will notice a grid on the surface of the plane in certain areas. And the grid goes away when origin is set to centre of mesh. Or you disable the bump node in the shader editor. Seems to be a rendering bug.", "Workbench: Strange anti-shadow when clipping cuts landscape\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 473.04\n\nBroken: version: 3.1.2\n\n\nAs title says. This shadow looks like this:\n\n\nDemo:\n[2022-05-06_01-02-27.mp4](2022-05-06_01-02-27.mp4)\n\nYou can test it by your own with my file\n[WB shadowbug.blend](WB_shadowbug.blend)\n\n" ]

[ "shadow catchers isnt working\nOperating system: Windows-10-10.0.10240-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 3.0.0 Alpha\n\n\n\n" ]

[ "Regression: Some particles have darker faces\nOperating system: Windows 10 1909\nGraphics card: GTX 1070 512.15\n\nBroken: 3.1 (also 3.1.1 RC)\nWorked: 3.0.1\n\nSome object instances, in a hair particle system, have darker faces\n\n3.0.1\n\n\n3.1 and 3.1.1 RC\n\n\nPress F12 in this test file:\n[Dark Particles.blend](Dark_Particles.blend)", "Workbench: shadow/face still visible at clipped side of view\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\n\nClipping view do not clip shade effect\n\n\n\n[untitled.blend](untitled.blend)\n", "blender3.4 alpha new eevee a rendering on the flashback\nOperating system:windows10 21h1\nGraphics card: amd 6800xt （22.7.1 driver opengl doubled the performance of a version)\n\nBroken: blender-3.4.0-alpha+master.ca172677b1a7-windows.amd64-release\nWorked: There is no version that can be tested\n\n\nScene any scene including cube, whether window rendering or f12, directly exit the software.", "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)", "Caustics not work as expected\nHi,\nI'm going crazy with shadow caustics.\nOddly they work when they turn off.\nIn the attached scene [caustics_not_work.blend](caustics_not_work.blend), if you disabled caustics on lights or objects, they will be displayed, otherwise no caustics will be displayed.", "Workbench refactor causes significant performance regression with workbench shadows\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.75\n\nBroken: version: 2.83.0\nCaused by c476c36e40\n\nWorked: 2.82a\n\n2.83 solid viewport shading work slowly than 2.82 when shadows is on\n\nReduction of performance in viewport very high in heavy scenes as example scene with sculpts 6 millions of triangles\n\n", "IES led bar not working\nOperating system: WINDOWS 10\nGraphics card: GTX 1080 \n\nBroken: blender 3.6 alpha \n\n\nHello, I'm working for a lighting company, we have led bars and their IES doesn't work on blender (I use cycle) the point light to which I apply the IES doesn't take into account that it's a light bar and the light comes from a single point. I've put together a comparison with Vray used on 3DSMAX (software we want to leave to migrate to blender) so that you can understand what I'm explaining in more detail.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n", "Grease Pencil Lighting - World light not influencing GP object correctly\nOperating system: Manjaro Linux (Kernel 5.4.18-1-MANJARO)\nGraphics card: Intel Haswell-ULT\n\nBroken: 2.83 (sub 2), c650ea9a13f9, greasepencil-refactor, 2020-02-11, 18:37\nWorked: unknown\n\nGrease Pencil Object (Strokes) unaffected by Background Light \n\nOpen either the General or the 2D Animation default file. Add a grease pencil monkey and a basic mesh, set some background color and change the strength settings once to 0 and once to 1.\nThe shading of the Suzanne object stays the same. When adding a spotlight and aiming it towards Suzanne it gets lit properly.\nThe [demo video ](GP_lighting.mp4) of the grease pencil lighting shows correct black objects where no scene light is hitting them.\n\n", "Shadow catcher punching holes through objects below it\nOperating system: **Windows 10 Home (Unregistered)**\nGraphics card: AMD **Radeon RX Vega 11 (Integrated. CPU: 2400G)**\n\nBroken: **2.91.2**\nWorked: **None**\n\nThe shadow catcher punches holes through any objects that are below it. I think this is intentional but I don't see any option to toggle it. I remember it working before, could be a hardware issue since I was using a different machine at that time (2nd Gen i3)\n\n\nAdd a shadow catcher and a plane below it to the default scene. Choose Cycles Render and enter rendered view.\n[SCBug.blend](SCBug.blend)", "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", "Blender 2.81 — Shadow glitches with Workbench render-engine (in viewport and same at render)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 2.81 (sub 9)\n\n\nBroken shadows \"traced path\" glithc effect in the air in places where geomety have \"complex area\" (when you use shadows from Workbrench render and same in viewport).\n[Screenshot ](l2ZRNEjhzLYbl2.jpg)\nHere is on [video ](#!0OoB2I7R!h1qq3DB20nOOgoxoYw9QT_kyoZO-a-1C7OSqRifExcs) uou can see it. Sorry for broken english.\n\n\nDon't know how to reproduce it step by step, so I've put the file here: \n[broken.blend](broken.blend)\n\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.", "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", "Interpolated children on object rendered particles not working\nOperating system: Manjaro Linux\nGraphics card: AMD Radeon rx570\n\nBroken: 2.60, 2.79, 2.80, 2.81, 2.82, 2.82a, 2.83, 2.90Alpha\nWorking: Couldn't find any\n\nCan't see any particles when there set to render as an object with an object selected and interpolated children\n\n\n1. Open this file: [particle_child_interp_bug_2_79.blend](particle_child_interp_bug_2_79.blend)\n2. Play animation\n3. In the particle children settings, set Interpolate \nor \n1. Create a particle system on a uv sphere,\n2. set the render type to object,\n3. select a 2nd uv sphere as the render object\n4. set the children to interpolated\n[Daily Challenge 80(particles galore).blend](Daily_Challenge_80_particles_galore_.blend)", "Eternal compilation of Eevee shaders\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro Vega 64 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29\n\nBroken: version: 3.0.0 Beta\n\nIn layout, clicking shading workspace ta brings spinning when of death.\n\n- Open attached file\n- click in the Shading workspace\n[tudor-bedroom 2.blend](tudor-bedroom_2.blend) \n\n" ]

[ "shadow catcher problem. when i am using this that plane is not going to transparent..\nOperating system: Windows-10-10.0.10240-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4400 Intel 4.3.0 - Build 20.19.15.4531\n\nBroken: version: 3.0.0 Alpha\n\n\n\n" ]

[ "Geometry Nodes modifier input: Show More descriptive names in the dopesheet\nRight now animated geometry nodes modifier properties get an infamous label such as \"Input_2\". It should instead show the name that is shown in the UI, just like the other (non-geometry nodes) modifier properties.\n\n{[F13048799](image.png), size=full}\n\n[modifier.blend](modifier.blend)\n\nA proposed solution by @HooglyBoogly + @JulianEisel is to introduce \"labels\" to the UI data of ID Custom Properties.\n\n*This doesn't touch the Python API.*", "Geometry Nodes fouling up motion blur\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.1.0\nWorked: N/A\n\nGeometry Nodes applied to a spline which affect its shape over time do not blur when Motion Blur is enabled.\n\nLoad attached simple file. Render frame zero. There is no blur at all. Render frame 1, *everything* is blurred, despite only part of the spline is in motion. It would appear the entire spline is blurred according to how the base object is moving, not how the spline is deformed as a result of the applied Geometry Nodes.\n\nNote that same file loaded into 3.3.1 causes Blender to crash (GPU rendering only - it's a stack corruption bug in the nVidia driver, but 3.1 doesn't cause a problem). I previously reported that crash but it was rejected due to possibly being related to the Photographer add-on, which I have uninstalled. It still crashes.[Motion Blur Bug.blend](Motion_Blur_Bug.blend)", "Crash while using the Cloth Filter brush with collisions enabled\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14739 Core Profile Context 21.6.1 27.20.22001.14011\n\nBroken: version: 3.0.0 Alpha\n\nUsing the cloth filter brush with collisions enabled on *both* the deforming object and the non-deforming object causes Blender to crash.\n\n- Open the attached .blend file with a minimal scene where this error can be observed. Everything has been already set up.\n- With the pre-selected *Cloth Filter* brush set to *Gravity* and both *Use Collisions* and *Use Face Sets* enabled, `LMB` on the \"Skirt\" mesh, and start dragging to the left of the screen, causing the \"Skirt\" mesh to start flying upwards.\n- After a brief while, release `LMB` and repeat the above operation by dragging to the right. Note how the direction of the cloth filter brush was not reversed this time.\n- Almost as soon as this new sculpting operation is initiated, typically Blender crashes. Occasionally it might take a few more attempts.\n\n[facesets-crasher.blend](facesets-crasher.blend)\n\n**Additional notes**\nIf extensive changes are performed to the \"Collisions\" mesh, the bug will not be able to be reproduced anymore.", "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", "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", "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", "Materials linked to the object's data are lost when removing attributes from instances in geometry nodes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.5.0 Alpha\n\nMaterials linked to the object's data are lost when removing attributes from instances in geometry nodes.\n\n1.Instance a collection using geometry nodes.\n2.Remove an attribute from the instances (the attribute doesn't need to exist).\n3.Materials stored on the object data are now lost.\n\n\n[BugExample.blend](BugExample.blend)\n\n\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", "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)", "Blender 3.6 crashes when opening 3.5 files with library overrides / shape keys.\nOperating system: Windows 10\nGraphics card: RTX 3080Ti \n\nBroken: 3.6.3 Release Candidate (71b55b491e9c) \nWorked: 3.5\n\nI recently switched from 3.5 to 3.6 but I noticed that many of my Blender 3.5 .blend files make Blender 3.6 crash whenever I open them. The issue seems to be a null pointer reference in `shapekey_owner_pointer_get` in one of my mesh assets with shape keys. The debug build aborts with a failed assertion:\n\n```\nBLI_assert failed: X:\\blender\\source\\blender\\blenkernel\\intern\\key.cc:98, shapekey_owner_pointer_get(), at 'key->from != nullptr'\n```\n\nAll of my problematic .blend files use library overrides of mesh objects with shape keys. Additionally, some of the included assets were changed (in 3.5, maybe in 3.6).Blender 3.5 simply logs some missing meshes as usual but does not crash. Also these do _not_ include the specific mesh that Blender 3.6 crashes on, that one was unchanged AFAIK. However, after opening and saving in 3.5, I can succesfully open them in 3.6 so the missing meshes may somehow play a role.\n\nI have not been able to reproduce this in a simple setup and I cannot share my production files. However I have bisected and the following commit introduced this behavior:\n\n```\n89bd7b64026ef56ec659db25bf455ced705f5601 is the first bad commit\ncommit 89bd7b64026ef56ec659db25bf455ced705f5601\nAuthor: Bastien Montagne <[email protected]>\nDate: Tue May 23 15:03:21 2023 +0200\n\n Fix #105889: LibOverride: Overrides of shape keys reset on resync.\n\n The usual special ShapeKey case needs yet another extra corner case\n special handling... See comments in code for details about that specific\n issue.\n\n NOTE: May be worth checking if this can be backported to 3.3 LTS too.\n\n source/blender/blenkernel/intern/lib_override.cc | 27 +++++++++++++++++++++++-\n 1 file changed, 26 insertions(+), 1 deletion(-)\n\n```\n@mont29 So under some circumstances, this fix results in `key->from` being `NULL` in `shapekey_owner_pointer_get()` (`key.cc:98`). Hopefully this is enough information to solve that. Otherwise I will continue to try and reproduce this in a simple setup and post an example `.blend` file.\n\n", "Regression: Crash when Sculpting on a mesh from a GP Lineart Modifier\nOperating system: Windows-10-10.0.22621-SP0 64 Bits (W11)\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.2, 4.0.0 Alpha\nWorked: 3.1\n\n\nWhen trying to sculpt a mesh in an assigned collection that a grease pencil lineart modifier references and the layer it is drawing to contains Grease Pencil strokes - it will instantly crash Blender. \n\n\n1. Download and extract zip to get the test blend file\n2. Load attached file with Load UI off\n3. Select the bust, it is in a GP lineart modifier collection \n4. Go to sculpt mode\n5. Try sculpt\n6. Crash\n\nAlternative steps:\n1. Create new scene\n2. Create a sphere\n3. Create a Grease Pencil object\n4. Add sphere to a new collection\n5. Select the GP object and add a lineart modifier\n6. Reference the sphere collection in the modifier\n7. Assign layer and material to the modifier\n8. Draw in the same layer in Draw mode of the GP\n9. switch to sculpt mode\n10. Try sculpt over sphere surface\n11. Instant crash\n\n", "Geometry Node: Changing modifier input values with python no cause update\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0 Alpha\n\n\nChanging modifier input values with python no cause update.\nBy code:\n\n```\nbpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_1\"][0] = 13.8\n```\n\nValue in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated.\n\n\n\n- Open attached file\n- Run the code `bpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_7\"] = 1.0` in the python console\nThe modifier UI may change, but the Viewport does not.\n[geom_node_py_bug.blend](geom_node_py_bug.blend)\n\n", "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", "Geometry Nodes: Support materials in simulation state.\nCurrently, the simulation state in geometry nodes cannot contain materials. The main reason is that those separate IDs which are not serialized as part of simulation baking. Ideally, baking materials would just work, at least in the most common circumstances.\n\nWhile this task is about materials, the same thoughts also apply to other referenced IDs like object/collection instances.\n\nThere are two main possible solutions:\n1. Serialize materials as part of the simulation state.\n2. Only store a reference to the material in the simulation state.\n\n### 1. Serializing Materials\n\nSerializing materials has the benefit that it could just work. We'd have to store all the materials for every geometry in the simulation state in cached frame. Though, it's possible to deduplicate this to some degree of course. Serializing materials would also involve serializing the node graph and potentially even more referenced data like images. At some point we most likely want things to stay referenced, so the problem is just moved to a different place. Another problem is that the materials are essentially recreated on every frame. Blender does not really have the ability to work with materials that are not in `Main` currently.\n\n### 2. Storing References\n\nStoring a reference to the material mainly means storing a material name and an optional library name in the simulation state. Then, when loading the simulation state, the materials available in the .blend file are mapped to the loaded geometry. Conceptually, this is also very straight forward. Materials can still be edited like they always have been. A potential problem is that if materials are renamed or removed, they can not be linked correctly anymore. However, that is somewhat expected with linking already. While this approach is easy design wise, there are some technical difficulties: The main problem is that we only know which materials are used by the baked data, once the data is loaded. And, to make matters more difficult, we might only know which baked data to load once depsgraph evaluation has started. That can happen when e.g. the file path to the data on disk is dynamically build/choosen during evaluation (this is not supported right now, but likely will be at some point).\n\nThe problem with knowing which materials will be used by the geometry is that materials are part of the dependency graph. As such, all materials we wish to use for rendering have to be added to the dependency graph *before* evaluation starts. As of right now, it's not possible to lazily add materials to the depsgraph once it becomes known that it is required.\n\nThere are a couple different possible solutions with different trade-offs:\n* A. Always add all materials to the depsgraph. This would be a simple solution, but it's obviously not scalable. Even less so if we wish to use the same solution for other kinds of referenced data like objects.\n* B. Only support linking baked data with materials that are referenced by material slots on the object or original geometry. This means that if the simulation state happens to contain materials used by e.g. other imported objects, those will not be linked correctly.\n* C. Detect all materials \"reachable\" from an object and always add those to the depsgraph. This might have noticeable overhead when potentially large parts of `Main` have to by scanned by many objects. It also wouldn't work in all cases. For example, if the simulation has been baked, and then the .blend file changes in ways that the material is not reachable from the object anymore. Then the material would not be linked correctly.\n* D. Store a name-to-material mapping on the modifier. This mapping could be created/updated automatically when baking or at other points in time. Only materials in this mapping can be linked when loading simulation state. If the simulation state contains a material name that is not in the list, we could show a warning and automatically add it to the list with the press of a button in many cases. With this approach, the user also has the ability to replace a material after baking easily. The mapping could also have per simulation zone overrides for more control.\n\n-----\n\nCurrently, my preferred solution is referencing the materials by name in the simulation state and use option D to do the linking at evaluation time.\n\n", "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)" ]

[ "Named Crease Attribute set to Edge Domain Crash\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0\n\nIf a named attribute node is setting the 'crease' attribute with the edge domain, a crash will occur.\n\n- In uploaded .blend file set domain to edge.\n\n\n[Crease Attribute Crash.blend](Crease_Attribute_Crash.blend)" ]

[ "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", "Bevel Tool cycling through percent mode locks numerical input\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.91.0 Alpha\n\nIn edit mode, if you input a precise value for a bevel (edge bevel tool), like lets say 0,5, and then cycle through the modes (M-key), after cycling past the percent mode, it resets your numerical input to 0, and you cannot change it anymore.\n\nDepending on what value you have input, and whether you have also moved your mouse or not, gives different results. Sometimes it resets to 0, sometimes to another number. In any case, it is then frozen, and you cannot change it.\n\n\nVersion 1, without mouse movement:\n- Add a cube\n- In edit mode, start the edge bevel tool (Ctrl + B)\n- Input a bevel value, like 0,1\n- Press M several times to cycles through modes.\n- The value has reset to 0.\n- Try deleting the input value (backspace) or writing any other number. It is locked. \n- Try moving the mouse. No effect.\n\nVersion 2, with mouse movement:\n- Add a cube\n- In edit mode, start the edge bevel tool (Ctrl + B)\n- Move your mouse around\n- Input a bevel value, like 0,1\n- Press M several times to cycles through modes.\n- The value has reset to some other value, probably based on the mouse position.\n- Try deleting the input value (backspace) or writing any other number. It is locked. \n- Try moving the mouse. No effect.\n", "GPencil: Hotkeys of Tools is not consistent when Draw Tool is active\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.76\n\nBroken: version: 2.81 (sub 11)\nWorked: (optional)\n\nI'm not sure whether this is intended or not.\nHotkeys (1 to 9) shift downward one by one depending on whether you are in a draw tool or not.\n\n1. Go to Draw Mode\n2. Select a draw tool by pressing Shift Spacebar, O (Not 1)\n3. Select a fill tool by pressing Shift Spacebar, 1\n4. Select a draw tool by pressing Shift Spacebar, 1 (Not O)\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: unable to change erase size while using the Draw tool\nOperating system: Linux-5.19.0-76051900-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.47, 5.19.0-76051900-generic) AMD 4.6 (Core Profile) Mesa 22.0.5\n\nBroken: version: 3.5.0 Alpha\nWorked: ???\n\nCan't change the size of the eraser brush while erasing while using the draw tool (`Ctrl + LMB`), I can do it with the scroll wheel on the mouse but not with the shortcuts assign for it `[]`\nAlso applies to annotation tool.\n\n- go to greasepencil draw mode\n- draw something\n- hold control to erase\n- try to change the size of the eraser brush while erasing (Either scroll wheel or brackets)", "Can't undo the keyframe change in edit mode\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.1.2\n\nWhile in edit mode, when you hit Undo in the graph editor after moving a keyframe, the graph doesn't change.\n\n- Animate anything using a couple of keyframes.\n- Change to edit mode in viewport\n- Switch timeline to the graph editor (not necessary, you can keep timeline as it is)\n- Select a keyframe and move it\n# Hit undo\n\nResult: The graph editor stays the same\n\nExpected: The move you just made in the graph editor should be the only thing being undone!\n\nTest file with first four steps included\n[#97700.blend](T97700.blend)", "UI: Cursor flickering when hovering over properties\nBroken: version: 3.0.0 Beta\n\nWhen hovering from one property to another in property area, sometimes cursor changes from <--> to standard cursor. There are no instances where you stop moving it and it stays as standard one - it always changes to <--> after a fraction of a second. UI scaling does not affect it.\n\nNote that when tried without recording problem was more apparent, almost always cursor was flickering.\n[UI Cursor flickering take 2 2021-11-27 10-58-42-112.mp4](UI_Cursor_flickering_take_2_2021-11-27_10-58-42-112.mp4)", "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", "Entering names in Object pointer parameter and confirming with the mouse in the right part of the button will clear user input immediately again\nWin 8.1x64, 3x gtx580\n\n2.79a\n\nIn a node's Object parameter, on entering the text manually, after pressing enter to confirm, if the mouse happened to be located where normally the \"X\" button to clear the parameter is, the field gets cleared.\nAlso applies to other object pointer fields.\n\nWhen entering names in Node Editor, (at least for me) it is common to move the mouse slightly sideways, so that the cursor is not over the field being typed in. As a result it happens to be over said clear button quite often. Given that it is currently impossible to undo a single name change #54580 , it turns into either loosing the name and having to search/type it again, or more often - by automatically pressing Undo - losing a whole row of changed fields.\n\n[rename.blend](rename.blend)\n - Click the Object parameter to type manually,\n - Move the mouse to the right side of the field, where the \"X\" was located before starting to type,\n - Enter a new object and press enter,\n - The Object parameter field is empty.", "Sculpting - Switching stroke method with a shortcut causes a freeze\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1\n\nWhen using E shortcut in sculpt mode to change stroke method of the brush, there is a ~5-10 second freeze every time.\nHowever, when you do the same thing from the brush UI, the switch is silky smooth. See the video for example\n\n1. Open attached file\n2. Switch to sculpt mode\n3. Do a few strokes, press E - blender will freeze for about 10 seconds\n4. Do a few strokes again, this time change stroke method from UI - no freezes here\n\nVideo:\n[blender_am0pkp0Cwy.mp4](blender_am0pkp0Cwy.mp4)\nExample File:\n[sculptbug.blend](sculptbug.blend)\n\n", "Move To Line Begin and Reset View operators in the console editor conflict when pressing Home key\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\n\nIn the python console editor, both the Move To Line Begin and the Reset View operators have the same shortcut \"Home\", so it is not possible to invoke the Move To Line Begin operator.", "Use toolbar for Clip Editor\nAs discussed with @Sergey, here's how we would like the Clip Editor to work:\n\n{[F6943021](Screenshot_2019-04-14_at_10.06.22.png), size=full}\n\nThis makes it compliant with the other editors in Blender 2.8.\n\n\n - - [x] {icon circle color=yellow} Add toolbar to the Clip Editor\n - - [x] {icon circle color=yellow} Add Marker tool to the toolbar\n - The Marker tool lets you add markers whenever you click. The tool settings for the next marker should then be added to the tool settings\n - - [x] {icon circle color=yellow} Add Selection tools to the toolbar\n - - [ ] {icon circle color=yellow} Add Cursor tool to the toolbar\n - - [ ] {icon circle color=yellow} Add transform tools (Move, Rotate, Scale, Transform) to the toolbar\n - - [x] {icon circle color=yellow} In Mask mode, add the masking tools to the toolbar", "Circle Select Tool improvements\n## Issue\n\nThe current problem with the Circle Select Tool is that it is very inconvenient to change the brush size. In the modal operator equivalent (Shortcut C) it's just about pressing + and - or using the scrollwheel but this is not an option for the Tool. Generally there are no shortcuts for Tools before they are initiated. If the settings need to be changed then this needs to happen in the Tool Settings in the header or sidebar.\nBut changing the radius via that slider in the settings is awkward and appears visually glitchy since it's intersecting with the UI itself.\n\n\n\n## Proposals\n\nSo how can this be fixed. Ideally the solution should be as straight forward as possible without reshuffling the keymap. But it is very important that this is a general solution that can also be used for other brush-like Tools in the future (like proposed retopology tools that also rely on a brush radius)\n\n**1. More integrated modal shortcuts**\n\nOnce a Tool is initiated (usually by click & dragging) it uses the modal operator. This means that when using the Circle Select Tool and click & dragging, the radius can be changed with the mouse wheel & the + and - keys. \nThe current issue with this is that the Gizmo drawing is conflicting with the Tool Radius and that any changes to the radius are not updated in the tool settings.\nKeeping these 2 more in sync would be one solution or at least a great added feature.\n\n\n\nIt should be updated to the way the annotate eraser tool works but with more accessible shortcuts for radius changes if the mouse wheel is not an option (pen users)\n\n**2. Include Brush Tools in more modes**\n\nAnother solution is to redesign the Circle Select Tool (and any tools, present or future, that work similarly) as a brush like in sculpt mode or the painting modes.\nThis means that when the Tool is active it does have a set of shortcuts that can change the tool settings before the tool is initiated.\n\n**Conflicts**\n\nAlmost all are already taken like the typical F for brush size changes. It's not clear what shortcut can be used. \nAlso any shortcut that would be available must then be exclusively used for those brush tools to avoid any conflicts. \n\n**Solutions**\n\n1. Find or make an available shortcut for brush tools radius. But this shortcut then needs to be left exclusive of those tools.\n2. Override needed shortcuts when brush tool is used (In this case F for the radius). This does introduce difficulties and extra tool switching in edit mode though. \n3. Reuse the shortcut C that is used for the Circle Select Tool to change the radius once the tool is active. This will be awkward and incompatible with future tools that will work similar though.\n\n## Open Topics\n\n- Can it be achieved to use both solutions to improve brush like tools?\n- Are there possibly other ways of solving the conflicts in proposal 2?\n- For proposal 1, what shortcuts could be better for adjusting the brush size? + & - are on the numpad and the brackets are too far to the right and on for example German keyboard layouts not very accessible.", "Texture Paint mode tools swap when exiting maximized area\nOperating system: Linux-5.17.5-76051705-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.68.02\n\nBroken: version: 3.3.0 Alpha\nWorked: unknown\n\n[texture_paint_tool_swapping-2022-05-10_12.52.16.mp4](texture_paint_tool_swapping-2022-05-10_12.52.16.mp4)\n\n- Go to texture paint mode\n- open second image editor\n- maximize the area of the 3D viewport\n- change the active tool\n- un-maximize the area\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" ]

[ "Using shortcuts to change tools: cursor doesn't change\nOperating system: Win 10\nGraphics card: 1080\n\nBroken: 2.81a\nWorked: (optional)\n\nAssign a shortcut to the tools - in my case I use the Function keys, e.g. F7 for the Edit Mode Grease Pencil. So F1 is the select tool, start in select, hit F7, it properly changes to the pencil but the cursor stays as cross hairs. When writing it does briefly switch to a pencil, then back when you lift off. Clicking the tools properly changes the cursor, but not using shortcuts. \n\n\n\n\nDetailed above, assign a shortcut to a tool, switch to it using the shortcut, the cursor stays as per the previous tool and only changes with a mouse click on the tool selection bar. ", "Cursor not updating when switching tools using shortcuts\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.16\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nWhen binding shortcuts to tools, the cursor does not correctly update.\n\nOpen Blender\nAssign shortcut to Annotate (B)\nAssign Shortcut to Select Box (V)\nAssign Shortcut to Annotate Erase (E)\nSwitch between the tool susing the shortcuts (B,V,E)\nThe Cursor does not update when you switch the tool, but as soon as you click, it updates, and when you release it goes back. if you hover over the tools, it switches correctly\n\n", "Cursor not updating when switching tools using shortcuts\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.16\n\n\nBroken: version: 2.80 (sub 73)\nWorked: (optional)\n\n\nCursor does not update when switching tools using shortcuts\n\nOpen new Blender file\nassign shortcut to annotaion tool (e.g. \"e\")\nclick on selection tool, you sould now see the default cursor\nnow press \"e\" and you are using the annotation too (it highlights in the t-panel)\nbut the cursor remains the default cursor\nwhen you click to draw an annotaion the brush cursor appears but also disappears when you release the mouse button\nthe cursor updates when you hover over the t-panel\nworks also teh other way around, if you are using the annotation tool and the switch to selection via shortcut the cursor remains the brush\n\n", "Cursor keeps brush appearence after leaves \"Annotate\" tool\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\nCursor keeps brush appearence after leaves \"Annotate\" tool\n\n\nWhen you leave the \"Annotate\" tool and press the \"W\" key for the \"Select\" tool, the cursor will remain the appearance of a brush.\nBut if you leave the \"Annotate\" tool by clicking on the selection tool icon, the icon will change to the shape of a cross.\nThe same thing happens with the \"Draw\" tool on the curve.\n\n\n" ]

[ "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.", "problem Blender 4.0 in a mac mini\nOperating system: macOS-13.4.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 4.0.0 Alpha\n\nI'm trying to get Blender 4.0 (Alpha) running on a Mac Mini running OS Ventura 13.14.1(c). When the cube appears (by default) it is not surrounded by the yellow paint and cannot be selected with the left mouse button or the pointer of the digital tablet either. It can only be selected in the outliner\n\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.", "Cursor jumping to edge of screen when lifting pen from tablet area (wintab)\nOperating system: Windows-10-10.0.19043-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 Beta\nWorked: 2.93\n\nTablet model: Huion h950p\nTablet api: Wintab\n\nWhen lifting the pen away from the tablet area, the cursor occasionally jumps to the edge of the screen, causing unexpected camera jumps or preventing hotkeys from being used in the 3d view.\n\nThe problem only happens with the Wintab api.\n\n\n - Set the tablet api to Wintab\n\n - Start creasing some edges and repeatedly lift and return the pen to the tablet area\n\n[cursorjump.mp4](cursorjump.mp4)\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", "UV Editor face select mode fails to select ngons reliably\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.98\n\nBroken: version: 3.4.1\nWorked: never? (2.83 fails too)\n\nUV Editor face selection mode fails to select ngons reliably, because it uses face dot based selection, which can not be turned off. I was told to report scenarios where face dot based selection fails to work as bugs, so I am doing so here.\n\n1. Open the attached file\n2. Select the mesh object, enter the edit mode, and in the UV editor, switch selection mode to face\n3. Attempt to select some of the larger ngon UV face\nResult: The selection of larger ngon UV faces fails in many cases\nExpected The UV faces under the mouse cursor are selected when clicked on\n\n[UVSelectBug.blend](UVSelectBug.blend)\n[2023-02-06 12-20-58.mp4](2023-02-06_12-20-58.mp4)", "The walk mode is stuck when it is enabled while using a tablet pen\nOperating system: Windows 10\n\n\nBroken: 3.0.0\n\n\nThe walk navigation mode goes does not trigger right away when it is used with a Wacom tablet in Windows Ink mode. The Win ink is set both in Blender and the Wacom properties.\n\nHere I enable the walk mode, but it does not move at all until I lightly move the mouse. After that it works.\n[ClvNCLQx0H.mp4](ClvNCLQx0H.mp4)\n\nUse a Wacom pen \nEnable Windows Ink in Wacom panel and in Blender\nEnable Walk navigation", "Shift+Spacebar shortcut for Tool Menu doesn't work correctly in sculpt mode\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.0\n\nPressing and holding Shift+Spacebar and selecting a tool works okay. But just pressing that shortcut quickly shows the menu and hide it.\n\nOpen sculpt layout or go to sculpt mode. Press and hold shortcut Shift+Spacebar. While holding you can move the cursor on some tool and release the buttons. Tool under cursor is selected. All is okay, it works like a Pie menu.\nBut there are also hotkeys in that menu and if I just press Shift+Spacebar (without holding), menu opens and closes quickly. And selected is tool that was under cursor at that moment. If you press (without holding) Shift+Spacebar again, the menu doesn't close now, because the selected tool has already selected. But again, if I move my cursor, just press the shortcut, the menu shows and closes. It's impossible to use the hotkeys on the right of the tools in that menu.\n\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", "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", "`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", "Exiting 'Start Editing Stached Action' mode with tab or selecting 'Stop Tweaking Strip Action' results in the channel mute button having no effect\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5600M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.22\n\nBroken: version: 2.93.5\n\n[Edit_Stashed Action_NLA_Bug.blend](Edit_Stashed_Action_NLA_Bug.blend)\nIf you either choose 'Start Editing Stashed action' or press Shift + tab, then you enter edit mode, but if you press tab or select 'Stop tweaking Strip action' it seems like you've returned to the NLA, but the strip mute button has no effect. Moving the strip behaves as expected. Going back into stash edit mode and exiting via the menu 'Stop editing stashed action' or Shift + Tab will get back to the NLA with the mute button behaving correctly\n\n\n\nOpen the attached blendfile, note that the NLA strip is muted and has no effect. Either right click on the NLA strip and select 'Start Editing Stashed action'. Press tab or right click on the strip and select 'Stop tweaking Strip action'. See that now the strip is active even though the channel is muted. \n\n\n", "VSE video strips with audio get packed into the .blend file when auto-packing enabled, leading to crashes with large amounts of videos\nOperating system: Windows 8.1\n\nBroken: 2.80, 2019-04-09\nWorked: 2.79\n\nBlender will try to pack all video/audio files in the vse into the .blend file if \"File>External Data>Automatically Pack Into .blend\" is enabled. This is terrible default behavior since it can very easily lead to blender attempting to save huge multi-gb files.\nIn addition to this, if you have more gb of files than you have ram, blender will crash when you enable auto-pack... really easy to do since a single video can easily be over 32gb.\n\nSome notes:\nBlender seems to only decide to do this for video files that have an audio track, even if the audio track is no longer loaded into the timeline.\nThere are no options to pack/unpack a video track. If the audio track is removed, the file will still attempt to be packed, but it cannot be unpacked.\n\nCreate a new 'Video Editing' file.\nLoad several gb of videos with audio into the vse timeline.\nSelect \"File>External Data>Automatically Pack Into .blend\"\nSave the file...\n", "Placement Tool for Objects and/or Collections\n### Motivation\n\nThe new drag & drop snapping helps easily & quickly placing objects in the scene. But it relies quite a bit on the asset and the scene it’s being dragged into (e.g. the size relative to the destination scene, the exact normal of the snapped to surface), etc. Users may want to adjust the rotation, the scale, the up-axis, use the origin for snapping rather than the bound-box (e.g. to place trees so they are partially covered by the ground plane), etc.\n\n### Basic Design Idea\n\nRather than setting these options before dragging (where you don’t get visual feedback) or while dragging (where it’s awkward to give input because you’re holding a mouse button), the Operate->Settings paradigm of Blender should be used: First the object/collection is dragged in and placed using basic snapping, then we provide a visual way to keep adjusting the transforms and parameters until the user is happy with the result.\n\nHowever, this placement method isn't just useful for dragging in assets. It is useful as a general transform tool and should be created as such. So this is a proposal for a general placement tool with bounding-box or origin based surface snapping, that gives access to most important transforms and properties for placing an object. In some way or another, it could be (temporarily and optionally?) activated after dragging an object or collection asset into the scene. If more advanced transforms are needed, the user can still access the proper transform tools & operators.\n\n### Temporary Activation\n\nHaving to activate a placement tool every time an asset is dragged in can be annoying. Blender could automatically activate it, at least in some temporary fashion. For example, the tool could temporarily override the active tool after dragging in an asset. Deselecting the dragged in object would bring back the real active tool. If the user wishes to go back to the placement tool, that can be explicitly enabled again in the toolbar.\n\n### Tool Design\n\nTODO", "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" ]

[ "Grab mode automatically enabled after selecting keyframe or VSE clip\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\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nWhen you select a keyframe, Blender will automatically enter the grab operator.\nThis is detrimental to workflow as you have to hit ESC after selecting if you did not want to activate the move operator.\nThis occurs when selecting in the Graph editor, Dope sheet or the VSE.\nThis is the same with left click select or right click select.\n\n\nSelect a single keyframe in the dope sheet and the grab operator will automatically be activated.\n\n\n", "Drag in empty space to box select does not work in animation editors\nOperating system: Ubuntu 18.10\nGraphics card: Radeon RX 560 Series (POLARIS11, DRM 3.31.0, 4.18.0-18-generic, LLVM 7.0.0)[example_vse_cache_invalidated.webm](example_vse_cache_invalidated.webm)\n\nBroken: 2.80, ebc44aae9897, master, 2018-05-11\n\nCached frames become invalidated as soon as another video strip is selected. \n\nAdd two video strips, one above the other. Select one of them and play, to get some frames cached. Then select the other strip and parts of the cache becomes invalidated. " ]

[ "TexBlendNode Python property tooltip incorrect\nBlender 2.8 \n\nI can not change the Progression or the Flip Axis for the Tex Blend Node with python. \n\nIt returns with an error that says \" no attribute use_flip_axis\". I thought this was my fault so I reached out for help on the Stack Exchange> [here ](how-do-i-change-the-blend-node-to-vertical?)\n\nThey think this is a bug or missing API?.. I checked online but could not see this bug reported so I thought I would let you guys know.\n\nI have used a rotate node to work around the problem but I am sure you guys would be able to fix this issue with ease.\n\n[#69973.blend](T69973.blend)", "Drivers not updating correctly when multiple drivers are relying on single property value change (viewport issue only)\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\nBroken: version: 2.81 (sub 10)\nAlso tested on 2.80 release version. Happened for me there for the first time so I've downloaded newest build to check if issue still occurs.\n\nWhen multiple drivers are linked into the same property, changing value of that property is not always propagated to all drivers. It looks like some sort of race condition, although I don't think it's caused by switching property back and forth and threads overlapping in that scenario, because even when doing this slowly, issue occurs. Issue also occurs when clicking arrows on a property instead of dragging left/right. \n\nSeems to be related to viewport displaying only. As presented at the end of linked video, rendering scene in such broken state is working correctly.\n\n1. Open provided blend file\n2. Select small cube at the bottom of the screen\n3. Cube has a property on it. Switch its value back and forth.\n4. When property is set to 0, only vertical bars should be visible. When property is set to 1, only horizontal bars should be visible.\n5. Not every time, but occasionally bar is visible when it shouldn't or the other way around.\n\nVideo of bug occurrence:\n\nwatch?v=5wrGXl3KnrQ&feature=youtu.be\n\n[bug-drivers.blend](bug-drivers.blend)", "Freestyle Lines Stopping Short of Vertices & Partially Failing\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 620 Intel 4.5.0 - Build 27.20.100.8682\n\nBroken: version: 2.92.0\n\nSee attached PNG file: Freestyle lines sometimes do not reach vertices - sometimes by a long way; and on some edges they are completely absent when they should be present.\n\n[The PNG file also shows a shadow problem which has been submitted separately: T88013 ]\n\nOpen the attached .blend file and press F12 ('Render').\n\n[BUG_FreestlyeLinesStoppingShort-of-Vertices-01.blend](BUG_FreestlyeLinesStoppingShort-of-Vertices-01.blend)\n\n\n\n", "State of hidden geometry not synced between edit mode and vertex paint/weight paint mode\nOperating system: Linux-5.8.0-7630-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.32.03\n\nBroken: version: 3.0.0 Alpha\n\nWhen vertex selection (or face selection) is used in either vertex paint or weightpaint mode the state of hidden geometry is not synchronized but overwritten by some specific state on this object. That makes it impossible to paint on using vertex selection. Joining the mesh into a new object did not fix the issue.\n[hidden_geo-2021-04-29_20.57.11.mp4](hidden_geo-2021-04-29_20.57.11.mp4)\n\nSee file:\n[hidden_geo.blend](hidden_geo.blend)\n\n", "Edges are selected in face mode when deselecting vertices from vertex group Panel\nBlender Version\nBroken: Current main.\nWorked: N/A.\n\nShort description of error\nDeselect Button in Vertex Groups Panel will deselect vertices that are not assigned to any groups. Edges become selected while in Face Mode as well. Also the Select Button will Select Faces that are not assigned too but those Edges that are active in face mode must be Selected for the Bug to work. Pay attention to the Edge around the triangle Fan at the top of the uv Sphere While in face mode.\n\nBlend File Incuded for simplicity\nJust Press the Deselect and notice the Faces that Get removed. and the Edges are actively Selected.\n\n", "Support Face color attributes for painting\nFace color attributes should be supported for sculpt painting and vertex paint mode.\n\nThey should also be listed under the Color Attributes UI List.\n\n", "Preferences window lags with add-ons preferences UI raises an exception\nOperating system: Windows 10 1903\nGraphics card: GTX970\n\nBroken: blender-2.80-9c5d54bfaf48-win64\nWorked:blender-2.80-8ac0fef4dfd1-win64\n\n\nWhen you click on a triangle in the addons list which is corresponds to an addon which contains VISIBLE_IPO_ON in code, it starts to incredibly lag. Seriously, one frame per second or two. Everything is quick and snappy until you press that goddam triangle. After that whole Preferences window behave like this till the restart of Blender. Other windows are unaffected.\nObserve: \nwatch?v=9fObpt0L8B0\n\nIn a log I can see a long and sad error: Traceback (most recent call last):\n```\nFile \"C:\\Users\\ostap\\AppData\\Roaming\\Blender Foundation\\Blender\\2.80\\scripts\\addons\\DECALmachine\\ui\\UILists.py\", line 16, in draw_item\n row.prop(item, \"isvisible\", text=\"\", icon=isvisibleicon, emboss=False)\n```\nTypeError: UILayout.prop(): error with keyword argument \"icon\" - enum \"VISIBLE_IPO_ON\" not found in ('NONE', 'QUESTION', 'ERROR', 'CANCEL', 'TRIA_RIGHT', 'TRIA_DOWN', 'TRIA_LEFT', 'TRIA_UP', 'ARROW_LEFTRIGHT', 'PLUS', 'DISCLOSURE_TRI_RIGHT', 'DISCLOSURE_TRI_DOWN', 'RADIOBUT_OFF', 'RADIOBUT_ON', 'MENU_PANEL', 'BLENDER', 'GRIP', 'DOT', 'COLLAPSEMENU', 'X', 'DUPLICATE', 'TRASH', 'COLLECTION_NEW', 'NODE', 'NODE_SEL', 'WINDOW', 'WORKSPACE', 'RIGHTARROW_THIN', 'BORDERMOVE', 'VIEWZOOM', 'ADD', 'REMOVE', 'PANEL_CLOSE', 'COPY_ID', 'EYEDROPPER', 'AUTO', 'CHECKBOX_DEHLT', 'CHECKBOX_HLT', 'UNLOCKED', 'LOCKED', 'UNPINNED', 'PINNED', 'SCREEN_BACK', 'RIGHTARROW', 'DOWNARROW_HLT', 'FCURVE_SNAPSHOT', 'OBJECT_HIDDEN', 'PLUGIN', 'HELP', 'GHOST_ENABLED', 'COLOR', 'UNLINKED', 'LINKED', 'HAND', 'ZOOM_ALL', 'ZOOM_SELECTED', 'ZOOM_PREVIOUS', 'ZOOM_IN', 'ZOOM_OUT', 'DRIVER_DISTANCE', 'DRIVER_ROTATIONAL_DIFFERENCE', 'DRIVER_TRANSFORM', 'FREEZE', 'STYLUS_PRESSURE', 'GHOST_DISABLED', 'FILE_NEW', 'FILE_TICK', 'QUIT', 'URL', 'RECOVER_LAST', 'THREE_DOTS', 'FULLSCREEN_ENTER', 'FULLSCREEN_EXIT', 'LIGHT', 'MATERIAL', 'TEXTURE', 'ANIM', 'WORLD', 'SCENE', 'OUTPUT', 'SCRIPT', 'PARTICLES', 'PHYSICS', 'SPEAKER', 'TOOL_SETTINGS', 'SHADERFX', 'MODIFIER', 'BLANK1', 'FAKE_USER_OFF', 'FAKE_USER_ON', 'VIEW3D', 'GRAPH', 'OUTLINER', 'PROPERTIES', 'FILEBROWSER', 'IMAGE', 'INFO', 'SEQUENCE', 'TEXT', 'SOUND', 'ACTION', 'NLA', 'PREFERENCES', 'TIME', 'NODETREE', 'CONSOLE', 'TRACKER', 'ASSET_MANAGER', 'NODE_COMPOSITING', 'NODE_TEXTURE', 'NODE_MATERIAL', 'UV', 'OBJECT_DATAMODE', 'EDITMODE_HLT', 'UV_DATA', 'VPAINT_HLT', 'TPAINT_HLT', 'WPAINT_HLT', 'SCULPTMODE_HLT', 'POSE_HLT', 'PARTICLEMODE', 'TRACKING', 'TRACKING_BACKWARDS', 'TRACKING_FORWARDS', 'TRACKING_BACKWARDS_SINGLE', 'TRACKING_FORWARDS_SINGLE', 'TRACKING_CLEAR_BACKWARDS', 'TRACKING_CLEAR_FORWARDS', 'TRACKING_REFINE_BACKWARDS', 'TRACKING_REFINE_FORWARDS', 'SCENE_DATA', 'RENDERLAYERS', 'WORLD_DATA', 'OBJECT_DATA', 'MESH_DATA', 'CURVE_DATA', 'META_DATA', 'LATTICE_DATA', 'LIGHT_DATA', 'MATERIAL_DATA', 'TEXTURE_DATA', 'ANIM_DATA', 'CAMERA_DATA', 'PARTICLE_DATA', 'LIBRARY_DATA_DIRECT', 'GROUP', 'ARMATURE_DATA', 'COMMUNITY', 'BONE_DATA', 'CONSTRAINT', 'SHAPEKEY_DATA', 'CONSTRAINT_BONE', 'CAMERA_STEREO', 'PACKAGE', 'UGLYPACKAGE', 'EXPERIMENTAL', 'BRUSH_DATA', 'IMAGE_DATA', 'FILE', 'FCURVE', 'FONT_DATA', 'RENDER_RESULT', 'SURFACE_DATA', 'EMPTY_DATA', 'PRESET', 'RENDER_ANIMATION', 'RENDER_STILL', 'LIBRARY_DATA_BROKEN', 'BOIDS', 'STRANDS', 'LIBRARY_DATA_INDIRECT', 'GREASEPENCIL', 'LINE_DATA', 'LIBRARY_DATA_OVERRIDE', 'GROUP_BONE', 'GROUP_VERTEX', 'GROUP_VCOL', 'GROUP_UVS', 'FACE_MAPS', 'RNA', 'RNA_ADD', 'MOUSE_LMB', 'MOUSE_MMB', 'MOUSE_RMB', 'MOUSE_MOVE', 'MOUSE_LMB_DRAG', 'MOUSE_MMB_DRAG', 'MOUSE_RMB_DRAG', 'PRESET_NEW', 'DECORATE', 'DECORATE_KEYFRAME', 'DECORATE_ANIMATE', 'DECORATE_DRIVER', 'DECORATE_LINKED', 'DECORATE_LIBRARY_OVERRIDE', 'DECORATE_UNLOCKED', 'DECORATE_LOCKED', 'DECORATE_OVERRIDE', 'TRACKER_DATA', 'HEART', 'ORPHAN_DATA', 'USER', 'SYSTEM', 'SETTINGS', 'OUTLINER_OB_EMPTY', 'OUTLINER_OB_MESH', 'OUTLINER_OB_CURVE', 'OUTLINER_OB_LATTICE', 'OUTLINER_OB_META', 'OUTLINER_OB_LIGHT', 'OUTLINER_OB_CAMERA', 'OUTLINER_OB_ARMATURE', 'OUTLINER_OB_FONT', 'OUTLINER_OB_SURFACE', 'OUTLINER_OB_SPEAKER', 'OUTLINER_OB_FORCE_FIELD', 'OUTLINER_OB_GROUP_INSTANCE', 'OUTLINER_OB_GREASEPENCIL', 'OUTLINER_OB_LIGHTPROBE', 'OUTLINER_OB_IMAGE', 'RESTRICT_COLOR_OFF', 'RESTRICT_COLOR_ON', 'HIDE_ON', 'HIDE_OFF', 'RESTRICT_SELECT_ON', 'RESTRICT_SELECT_OFF', 'RESTRICT_RENDER_ON', 'RESTRICT_RENDER_OFF', 'RESTRICT_INSTANCED_OFF', 'OUTLINER_DATA_EMPTY', 'OUTLINER_DATA_MESH', 'OUTLINER_DATA_CURVE', 'OUTLINER_DATA_LATTICE', 'OUTLINER_DATA_META', 'OUTLINER_DATA_LIGHT', 'OUTLINER_DATA_CAMERA', 'OUTLINER_DATA_ARMATURE', 'OUTLINER_DATA_FONT', 'OUTLINER_DATA_SURFACE', 'OUTLINER_DATA_SPEAKER', 'OUTLINER_DATA_LIGHTPROBE', 'OUTLINER_DATA_GP_LAYER', 'OUTLINER_DATA_GREASEPENCIL', 'GP_SELECT_POINTS', 'GP_SELECT_STROKES', 'GP_MULTIFRAME_EDITING', 'GP_ONLY_SELECTED', 'GP_SELECT_BETWEEN_STROKES', 'MODIFIER_OFF', 'MODIFIER_ON', 'ONIONSKIN_OFF', 'ONIONSKIN_ON', 'RESTRICT_VIEW_ON', 'RESTRICT_VIEW_OFF', 'RESTRICT_INSTANCED_ON', 'MESH_PLANE', 'MESH_CUBE', 'MESH_CIRCLE', 'MESH_UVSPHERE', 'MESH_ICOSPHERE', 'MESH_GRID', 'MESH_MONKEY', 'MESH_CYLINDER', 'MESH_TORUS', 'MESH_CONE', 'MESH_CAPSULE', 'EMPTY_SINGLE_ARROW', 'LIGHT_POINT', 'LIGHT_SUN', 'LIGHT_SPOT', 'LIGHT_HEMI', 'LIGHT_AREA', 'CUBE', 'SPHERE', 'CONE', 'META_PLANE', 'META_CUBE', 'META_BALL', 'META_ELLIPSOID', 'META_CAPSULE', 'SURFACE_NCURVE', 'SURFACE_NCIRCLE', 'SURFACE_NSURFACE', 'SURFACE_NCYLINDER', 'SURFACE_NSPHERE', 'SURFACE_NTORUS', 'EMPTY_AXIS', 'STROKE', 'EMPTY_ARROWS', 'CURVE_BEZCURVE', 'CURVE_BEZCIRCLE', 'CURVE_NCURVE', 'CURVE_NCIRCLE', 'CURVE_PATH', 'LIGHTPROBE_CUBEMAP', 'LIGHTPROBE_PLANAR', 'LIGHTPROBE_GRID', 'COLOR_RED', 'COLOR_GREEN', 'COLOR_BLUE', 'TRIA_RIGHT_BAR', 'TRIA_DOWN_BAR', 'TRIA_LEFT_BAR', 'TRIA_UP_BAR', 'FORCE_FORCE', 'FORCE_WIND', 'FORCE_VORTEX', 'FORCE_MAGNETIC', 'FORCE_HARMONIC', 'FORCE_CHARGE', 'FORCE_LENNARDJONES', 'FORCE_TEXTURE', 'FORCE_CURVE', 'FORCE_BOID', 'FORCE_TURBULENCE', 'FORCE_DRAG', 'FORCE_SMOKEFLOW', 'RIGID_BODY', 'RIGID_BODY_CONSTRAINT', 'IMAGE_PLANE', 'IMAGE_BACKGROUND', 'IMAGE_REFERENCE', 'NODE_INSERT_ON', 'NODE_INSERT_OFF', 'NODE_TOP', 'NODE_SIDE', 'NODE_CORNER', 'SELECT_SET', 'SELECT_EXTEND', 'SELECT_SUBTRACT', 'SELECT_INTERSECT', 'SELECT_DIFFERENCE', 'ALIGN_LEFT', 'ALIGN_CENTER', 'ALIGN_RIGHT', 'ALIGN_JUSTIFY', 'ALIGN_FLUSH', 'ALIGN_TOP', 'ALIGN_MIDDLE', 'ALIGN_BOTTOM', 'BOLD', 'ITALIC', 'UNDERLINE', 'SMALL_CAPS', 'HOLDOUT_OFF', 'HOLDOUT_ON', 'INDIRECT_ONLY_OFF', 'INDIRECT_ONLY_ON', 'CON_CAMERASOLVER', 'CON_FOLLOWTRACK', 'CON_OBJECTSOLVER', 'CON_LOCLIKE', 'CON_ROTLIKE', 'CON_SIZELIKE', 'CON_TRANSLIKE', 'CON_DISTLIMIT', 'CON_LOCLIMIT', 'CON_ROTLIMIT', 'CON_SIZELIMIT', 'CON_SAMEVOL', 'CON_TRANSFORM', 'CON_TRANSFORM_CACHE', 'CON_CLAMPTO', 'CON_KINEMATIC', 'CON_LOCKTRACK', 'CON_SPLINEIK', 'CON_STRETCHTO', 'CON_TRACKTO', 'CON_ARMATURE', 'CON_CHILDOF', 'CON_FLOOR', 'CON_FOLLOWPATH', 'CON_PIVOT', 'CON_SHRINKWRAP', 'MODIFIER_DATA', 'MOD_WAVE', 'MOD_BUILD', 'MOD_DECIM', 'MOD_MIRROR', 'MOD_SOFT', 'MOD_SUBSURF', 'HOOK', 'MOD_PHYSICS', 'MOD_PARTICLES', 'MOD_BOOLEAN', 'MOD_EDGESPLIT', 'MOD_ARRAY', 'MOD_UVPROJECT', 'MOD_DISPLACE', 'MOD_CURVE', 'MOD_LATTICE', 'MOD_TINT', 'MOD_ARMATURE', 'MOD_SHRINKWRAP', 'MOD_CAST', 'MOD_MESHDEFORM', 'MOD_BEVEL', 'MOD_SMOOTH', 'MOD_SIMPLEDEFORM', 'MOD_MASK', 'MOD_CLOTH', 'MOD_EXPLODE', 'MOD_FLUIDSIM', 'MOD_MULTIRES', 'MOD_SMOKE', 'MOD_SOLIDIFY', 'MOD_SCREW', 'MOD_VERTEX_WEIGHT', 'MOD_DYNAMICPAINT', 'MOD_REMESH', 'MOD_OCEAN', 'MOD_WARP', 'MOD_SKIN', 'MOD_TRIANGULATE', 'MOD_WIREFRAME', 'MOD_DATA_TRANSFER', 'MOD_NORMALEDIT', 'MOD_PARTICLE_INSTANCE', 'MOD_HUE_SATURATION', 'MOD_NOISE', 'MOD_OFFSET', 'MOD_SIMPLIFY', 'MOD_THICKNESS', 'MOD_INSTANCE', 'MOD_TIME', 'MOD_OPACITY', 'REC', 'PLAY', 'FF', 'REW', 'PAUSE', 'PREV_KEYFRAME', 'NEXT_KEYFRAME', 'PLAY_SOUND', 'PLAY_REVERSE', 'PREVIEW_RANGE', 'ACTION_TWEAK', 'PMARKER_ACT', 'PMARKER_SEL', 'PMARKER', 'MARKER_HLT', 'MARKER', 'KEYFRAME_HLT', 'KEYFRAME', 'KEYINGSET', 'KEY_DEHLT', 'KEY_HLT', 'MUTE_IPO_OFF', 'MUTE_IPO_ON', 'DRIVER', 'SOLO_OFF', 'SOLO_ON', 'FRAME_PREV', 'FRAME_NEXT', 'NLA_PUSHDOWN', 'IPO_CONSTANT', 'IPO_LINEAR', 'IPO_BEZIER', 'IPO_SINE', 'IPO_QUAD', 'IPO_CUBIC', 'IPO_QUART', 'IPO_QUINT', 'IPO_EXPO', 'IPO_CIRC', 'IPO_BOUNCE', 'IPO_ELASTIC', 'IPO_BACK', 'IPO_EASE_IN', 'IPO_EASE_OUT', 'IPO_EASE_IN_OUT', 'NORMALIZE_FCURVES', 'VERTEXSEL', 'EDGESEL', 'FACESEL', 'CURSOR', 'PIVOT_BOUNDBOX', 'PIVOT_CURSOR', 'PIVOT_INDIVIDUAL', 'PIVOT_MEDIAN', 'PIVOT_ACTIVE', 'CENTER_ONLY', 'ROOTCURVE', 'SMOOTHCURVE', 'SPHERECURVE', 'INVERSESQUARECURVE', 'SHARPCURVE', 'LINCURVE', 'NOCURVE', 'RNDCURVE', 'PROP_OFF', 'PROP_ON', 'PROP_CON', 'PROP_PROJECTED', 'PARTICLE_POINT', 'PARTICLE_TIP', 'PARTICLE_PATH', 'SNAP_OFF', 'SNAP_ON', 'SNAP_NORMAL', 'SNAP_GRID', 'SNAP_VERTEX', 'SNAP_EDGE', 'SNAP_FACE', 'SNAP_VOLUME', 'SNAP_INCREMENT', 'STICKY_UVS_LOC', 'STICKY_UVS_DISABLE', 'STICKY_UVS_VERT', 'CLIPUV_DEHLT', 'CLIPUV_HLT', 'SNAP_PEEL_OBJECT', 'GRID', 'OBJECT_ORIGIN', 'ORIENTATION_GLOBAL', 'ORIENTATION_GIMBAL', 'ORIENTATION_LOCAL', 'ORIENTATION_NORMAL', 'ORIENTATION_VIEW', 'COPYDOWN', 'PASTEDOWN', 'PASTEFLIPUP', 'PASTEFLIPDOWN', 'VIS_SEL_11', 'VIS_SEL_10', 'VIS_SEL_01', 'VIS_SEL_00', 'AUTOMERGE_OFF', 'AUTOMERGE_ON', 'UV_VERTEXSEL', 'UV_EDGESEL', 'UV_FACESEL', 'UV_ISLANDSEL', 'UV_SYNC_SELECT', 'GIZMO', 'ORIENTATION_CURSOR', 'NORMALS_VERTEX', 'NORMALS_FACE', 'NORMALS_VERTEX_FACE', 'SHADING_BBOX', 'SHADING_WIRE', 'SHADING_SOLID', 'SHADING_RENDERED', 'SHADING_TEXTURE', 'OVERLAY', 'XRAY', 'LOCKVIEW_OFF', 'LOCKVIEW_ON', 'AXIS_SIDE', 'AXIS_FRONT', 'AXIS_TOP', 'NDOF_DOM', 'NDOF_TURN', 'NDOF_FLY', 'NDOF_TRANS', 'LAYER_USED', 'LAYER_ACTIVE', 'SORTALPHA', 'SORTBYEXT', 'SORTTIME', 'SORTSIZE', 'SHORTDISPLAY', 'LONGDISPLAY', 'IMGDISPLAY', 'BOOKMARKS', 'FONTPREVIEW', 'FILTER', 'NEWFOLDER', 'FILE_PARENT', 'FILE_REFRESH', 'FILE_FOLDER', 'FILE_BLANK', 'FILE_BLEND', 'FILE_IMAGE', 'FILE_MOVIE', 'FILE_SCRIPT', 'FILE_SOUND', 'FILE_FONT', 'FILE_TEXT', 'SORT_DESC', 'SORT_ASC', 'LINK_BLEND', 'APPEND_BLEND', 'IMPORT', 'EXPORT', 'LOOP_BACK', 'LOOP_FORWARDS', 'BACK', 'FORWARD', 'FILE_CACHE', 'FILE_VOLUME', 'FILE_3D', 'FILE_HIDDEN', 'FILE_BACKUP', 'DISK_DRIVE', 'MATPLANE', 'MATSPHERE', 'MATCUBE', 'MONKEY', 'HAIR', 'ALIASED', 'ANTIALIASED', 'MAT_SPHERE_SKY', 'MATSHADERBALL', 'MATCLOTH', 'MATFLUID', 'WORDWRAP_OFF', 'WORDWRAP_ON', 'SYNTAX_OFF', 'SYNTAX_ON', 'LINENUMBERS_OFF', 'LINENUMBERS_ON', 'SCRIPTPLUGINS', 'SEQ_SEQUENCER', 'SEQ_PREVIEW', 'SEQ_LUMA_WAVEFORM', 'SEQ_CHROMA_SCOPE', 'SEQ_HISTOGRAM', 'SEQ_SPLITVIEW', 'IMAGE_RGB', 'IMAGE_RGB_ALPHA', 'IMAGE_ALPHA', 'IMAGE_ZDEPTH', 'VIEW_PERSPECTIVE', 'VIEW_ORTHO', 'VIEW_CAMERA', 'VIEW_PAN', 'VIEW_ZOOM', 'BRUSH_BLOB', 'BRUSH_BLUR', 'BRUSH_CLAY', 'BRUSH_CLAY_STRIPS', 'BRUSH_CLONE', 'BRUSH_CREASE', 'BRUSH_FILL', 'BRUSH_FLATTEN', 'BRUSH_GRAB', 'BRUSH_INFLATE', 'BRUSH_LAYER', 'BRUSH_MASK', 'BRUSH_MIX', 'BRUSH_NUDGE', 'BRUSH_PINCH', 'BRUSH_SCRAPE', 'BRUSH_SCULPT_DRAW', 'BRUSH_SMEAR', 'BRUSH_SMOOTH', 'BRUSH_SNAKE_HOOK', 'BRUSH_SOFTEN', 'BRUSH_TEXDRAW', 'BRUSH_TEXFILL', 'BRUSH_TEXMASK', 'BRUSH_THUMB', 'BRUSH_ROTATE', 'GPBRUSH_SMOOTH', 'GPBRUSH_THICKNESS', 'GPBRUSH_STRENGTH', 'GPBRUSH_GRAB', 'GPBRUSH_PUSH', 'GPBRUSH_TWIST', 'GPBRUSH_PINCH', 'GPBRUSH_RANDOMIZE', 'GPBRUSH_CLONE', 'GPBRUSH_WEIGHT', 'GPBRUSH_PENCIL', 'GPBRUSH_PEN', 'GPBRUSH_INK', 'GPBRUSH_INKNOISE', 'GPBRUSH_BLOCK', 'GPBRUSH_MARKER', 'GPBRUSH_FILL', 'GPBRUSH_ERASE_SOFT', 'GPBRUSH_ERASE_HARD', 'GPBRUSH_ERASE_STROKE', 'SMALL_TRI_RIGHT_VEC', 'KEYTYPE_KEYFRAME_VEC', 'KEYTYPE_BREAKDOWN_VEC', 'KEYTYPE_EXTREME_VEC', 'KEYTYPE_JITTER_VEC', 'KEYTYPE_MOVING_HOLD_VEC', 'HANDLETYPE_FREE_VEC', 'HANDLETYPE_ALIGNED_VEC', 'HANDLETYPE_VECTOR_VEC', 'HANDLETYPE_AUTO_VEC', 'HANDLETYPE_AUTO_CLAMP_VEC', 'COLORSET_01_VEC', 'COLORSET_02_VEC', 'COLORSET_03_VEC', 'COLORSET_04_VEC', 'COLORSET_05_VEC', 'COLORSET_06_VEC', 'COLORSET_07_VEC', 'COLORSET_08_VEC', 'COLORSET_09_VEC', 'COLORSET_10_VEC', 'COLORSET_11_VEC', 'COLORSET_12_VEC', 'COLORSET_13_VEC', 'COLORSET_14_VEC', 'COLORSET_15_VEC', 'COLORSET_16_VEC', 'COLORSET_17_VEC', 'COLORSET_18_VEC', 'COLORSET_19_VEC', 'COLORSET_20_VEC', 'EVENT_A', 'EVENT_B', 'EVENT_C', 'EVENT_D', 'EVENT_E', 'EVENT_F', 'EVENT_G', 'EVENT_H', 'EVENT_I', 'EVENT_J', 'EVENT_K', 'EVENT_L', 'EVENT_M', 'EVENT_N', 'EVENT_O', 'EVENT_P', 'EVENT_Q', 'EVENT_R', 'EVENT_S', 'EVENT_T', 'EVENT_U', 'EVENT_V', 'EVENT_W', 'EVENT_X', 'EVENT_Y', 'EVENT_Z', 'EVENT_SHIFT', 'EVENT_CTRL', 'EVENT_ALT', 'EVENT_OS', 'EVENT_F1', 'EVENT_F2', 'EVENT_F3', 'EVENT_F4', 'EVENT_F5', 'EVENT_F6', 'EVENT_F7', 'EVENT_F8', 'EVENT_F9', 'EVENT_F10', 'EVENT_F11', 'EVENT_F12', 'EVENT_ESC', 'EVENT_TAB', 'EVENT_PAGEUP', 'EVENT_PAGEDOWN', 'EVENT_RETURN')\n\nAnd after changing VISIBLE_IPO_ON/OFF to HIDE_OFF/ON in the mentioned file issue disappears. Of course you may say that it's the issue with an un-updated addons. but that's weird. when Blender starts to misbehave instead of showing error message about the issue, isn't it?\n\n1. Open any scroll of the addon with VISIBLE_IPO_ON in it. \n2. Enjoy the performance. ", "Spreadout enum in pie menu gives strange result\nWin7x64GTX660m\n\nBroken: 2.73\nWorked: (optional)\n\nIf \"select similar\" operator is launched from a pie, items are arranged in a weird fashion (happens only in vertex and edge mode), overlapping one another and showing index numbers such as 167.\n\nFrom file, just click run in text editor (replaced example operator in text editor's pie menu template with *pie.operator_enum(\"mesh.select_similar\", \"type\")*).\n\n[overlappingPies.blend](overlappingPies.blend)", "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.", "Collada exporter's triangulation option messes up custom vertex normals\nBroken: v3.4.1, v3.2.0, v3.1.2\nWorked: Never, as far as I can tell.\n\nWhen using the Collada exporter to export a mesh with custom vertex normals (with the exporter's triangulation option on), for each quad, one vertex of a split-off triangle will have an incorrect vertex normal.\n\n Figure 1: A grassy slope mesh in Blender.\n\n Figure 2: The same mesh in Unity. Note how the lighting produces a visible seam between the two triangles of each grass quad. (Apologies for the low color contrast in the screenshot)\n\n- In Blender, create a quad mesh and rotate it so that it's standing instead of laying down\n- Use \"point to target\" to point the quad's normals straight up\n- Export the quad with the Collada exporter, with the triangulate option on\n- Import the mesh into some other program to check the exported vertex normals. You should see that one of the vertex normals is wrong.\n\n**Workarounds**\nTriangulating with Ctrl+T does not suffer from this bug.", "GPencil: Average tool in Vertex Paint mode not working as expected\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\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\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", "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.", "Grease Pencil vertices selection is offset when Layers/Transform Location as set to a driver\nOperating system: Win10\nGraphics card: RTX3070\n\nBroken: 3.1.0 A\nWorked: N/A\n\n**Short Description of issue**\nMoving a Grease Pencil object's layer via Layers->Transform, by using a Driver, offsets where you have to click to select vertices from that layer.\n\nNOTE: Switching to Draw Mode and drawing a stroke fixes it temporarily, but once you move the controller of the driver again, the problem returns.\n\n**Steps to Reproduce**\n- Open .blend file\n- Select Suzanne and switch to edit mode\n- Try selecting vertices (Does not work)\n- Now attempt to select in circled area\n\n\n\n[#95902.blend](T95902.blend)\nVideo example: iZ_A2wOnAJQ", "Changing the geometry type in the Vertex Weight Proximity modifier disables \"Invert Falloff\" and \"Normalize Weights\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\nWorked: \n\nIn the **Vertex Weight Proximity** modifier if the proximity mode is set to *Geometry*, changing the geometry type between *vertex, edge and face* disables the options *Invert falloff* and/or *Normalize Weights*.\n[bug.mp4](bug.mp4)\n\nAdd an object, add the vertex weight proximity modifier, set the proximity mode to geometry, enable the options normalize weight and invert falloff and change the geometry type between vertex, edge or face.\n[Based on the default startup]\n\n" ]

[ "Vertex Slide - Correct UV Bug?\nOperating system and graphics card\nBlender 2.74 d33b564 Fedora 21 64Bit Ivybridge\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nI am using Blender 2.74 d33b564 on a Fedora 21 Linux 64Bit Box with Ivybridge GFX\n\nI noticed that when using Vertex Slide (SHIFT+V) that the operator panel Correct UVs\noption is very odd/risky because the edge that a vertex gets slid along is reset to the\nwrong location. It also act very differently depending on weather Correct UVs is\nalready active or not when Vertex Slide is executed.\n\nI have attached my system-info.txt file, a blend file showing the issue and a video\nalso showing what happens.\n\nI am posting this as a separate bug even though it could be related to bug:\n```\n \n T44608\n```\n\n[system-info.txt](system-info.txt)\n\n[VertexSlideCorrectUVBug.webm](VertexSlideCorrectUVBug.webm)\n\n[VertexSlide-CorrectUvsBug.blend](VertexSlide-CorrectUvsBug.blend)" ]

[ "Decals crash Eevee on AMD graphics card\nOperating system: Linux 6.2.7 Manjaro \nGraphics card: AMD 7900XT\n\nBroken: 3.3LTS, 3.4.1\n\nUsing decals will crash blender in Eevee. cycles works\n\nas an example file please see the .blend that was linked here by the decalmachine creator: 66438\n\nThe issue there is unrelated but the file can serve to show the issue I am having. The moment I switch to rendered view or materials preview blender will crash. I see no error message in console. The log files states just: \n\n```\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'BLENDER_EEVEE' # Property\n \n```\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 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", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Cycles freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)", "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", "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", "Viewport Rendering and Texture Baking freezes Blender\nOperating system: Windows 7 64bit\nGraphics card: GTX 1660 Super\n\nBroken: 2.90.1\nWorked: 2.83\nWorked: builds prior to b21ba5e579\n\n\nBlender freeze when baking ambiant occlusion\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nI prepared my scene to bake all objects, but almost every time I try to bake an object (especially the table under the tv), blender is often stuck at 0%, using high CPU usage and freeze.[CtUrban.blend](CtUrban.blend)\n\nUpdate: Viewport Rendering also crash Blender.\n\n", "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. ", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\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", "Blender 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\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)", "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", "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" ]

[ "Blender 2.80 won't open.\nWindows 7, Nvidia GeForce 8400 GS, 4 GB RAM.\n\nBroken: -\nWorked: -\n\n**Blender 2.80 won't open.**\n\n**When I open \"blender.exe\" console flashes on launching, then closes.**", "crash on blender start.\nwindows 7\nprocessor: pentium(R)dual core 2.30GHz\n4.GB ram\nno graphics card (all in one pc cant install one) \n\nBroken: (2.8)\nWorked: (2.78)\n\n**\n\n* *tries to launch blender 2.8 *\n\nAL lib: <EE> update device params: Failed to set 44100hz, got 48000 instead\n\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\nwarning!unable to find pixel format that supports WGL_SWAP_COPY_ARB.substituting ont that uses WGL_SWAP_UNDEFINED_ARB\n\nWin32 Error# <0>: the operation was completed successfully.\n\nfollowed by exit blender and the screen asking me if i want to quit even though changes werent saved (or made)**\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\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)", "Subdivision surface with circle curve issue. \nOperating system: Windows 11 Pro\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0\nWorked: (on 2.9 was working fine)\n\nCreating a mesh ring with curve circle and applying sub division serface, the modifier fails at two vertecies on the mesh. \n\nAdd curve -> circle -? edit mode -> select verticies -> E to extrude and S to apply size -> E to extrude on Z direction -> done\nObject Mode -> add modifier -> subdivision serface -> issue.\n[Issue with subdivision serface .blend](Issue_with_subdivision_serface_.blend)\n\n\n", "different Skin Modifier outputs for same mesh\nWindows 10\nNvidia Quadro 600\n\nBroken: 1422f0d\n\nThe skin modifier produces different meshes on the default cube.\n\n\nTrigger the skin modifier to update by doing the same thing I do in the .gif\n\n[skin_modifier_bug.blend](skin_modifier_bug.blend)\n\nNote: this only seems to happen when the edges are orthogonal. When I move one point, the problem doesn't appear on this and connected points.\n\n(Originially reported here: 576)\n", "Transfer data - vertex position by sampling UV\nAs we discussed on blender.chat, Blender would benefit from being able to transfer vertex positions from one object to another by sampling the UV's. Both the operator and the modifier\n\nHere is a mockup that might clarify what I mean\n\n\n\n", "Modifier changes to support sub-panels for Geometry Nodes\nThis is a follow up of #108649\n\n", "Add Primitive Tool in Mask Editing\n# Improve the Add Circle/Square tool for masking\nCurrently a mask primitive will always be added at the current cursor position. \nBut with the new tool system it would make more sense to be able to use the current mouse position to add primitives.\nIt should work very similar to the Add Object tool in 3D view. \nHere's how it could work in Mask mode in both Clip and Image editor:\n- Switch to Add Circle/Square tool\n- Click and hold mouse button pressed to add a primitive and scale it to the desired size. Release mouse button to finish. \n- While dragging, hold Alt key to scale from the center, hold Shift to draw perfect square/circle instead of freeform rectangle/ellipse\nOptional:\nIn 3d view the primitives are mostly parallel to the grid. For masking it could be interesting to be able to hold Ctrl while adding the mask to be able to rotate it.", "Mesh Bevel Node\nNOTE: Design outdated. See #98674 for current design and progress. It is a development task though, so please don't add comments like \"when will this be finished?\"", "Quadriflow remesh unwelds vertices on symmetry axis\nOperating system: Linux-5.7.9-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.91.0 Alpha\n\nQuadriflow remesh sever points at symmetry boundary.\n\n[quadriflow.mp4](quadriflow.mp4)\n\n[quadriflow_unweld.blend](quadriflow_unweld.blend)\n", "Blender development todo list -- Import/Export\nNOTE: this is a direct dump of Import_Export (without cherrypicking the [still] valid items)\n\n## Blender files and Library linking\n\n- [ ] Mixing \"direct\" and \"indirect\" data not well supported #26706\n- [ ] Making local data which is still used in libraries, causes problems #44321\n\n## All Formats\n\nCurrently negative scales will flip faces for formats which don't store object transformations (obj, ply, stl ... etc). #35892\n\n## FBX\nSee [[Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX]].\n\n## Alembic\n- [ ] While Alembic exports particles as points and supports ParticleInstance modifiers it could also support particle duplication (dupliobjects etc.), see #54703\n", "Node Group usability tasks for Node assets\n* Enum socket\n* Custom warnings and errors\n* Panels / Sub-panels\n* Dynamic UI changes\n* Surface choice for inputs in modifiers\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", "Circle select does not select all vertices within the same pixel\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.90.1\n\nSelecting closely-arranged vertices with circle select tool doesn't consistently select all vertices.\n\nCreate plane geometry with three vertices located close together (e.g., the end of a sword or a blade of grass). Type 'C' to use the circle select tool and select the vertices. Zoom in to verify that all vertices have been selected. De-select vertices. Change zoom level. Repeat selection. Repeat verification. See animated GIF, attached, using simple .blend file, attached.\n\n\n\n[C3DE_Ch4_L12a.blend](C3DE_Ch4_L12a.blend)\n\n", "Subdivide smooth is not symmetric\nWindows 8\nGeforce GTX 665 M\n\nBroken: Blender 2.96.0 r60995\n\n\nOn a 3 vertex line with the center vertex with greater y like that :\n\n\nIf I use subdividee smooth the result is not symmetric, I haven't set any random property.\n \n\n1./ Use subdivide smooth on the attached blend file, I have put the result that I get and the original\n[subdivide_smooth_bug.blend](subdivide_smooth_bug.blend)", "Viewport: anti-alising on normal lines\nNormals on faces/vertices are not antialiased:\n\n\n\nTo see them, enable them at the bottom of the 3D Viewport Overlay popover:\n\n\nThis issue is similar to what was covered in #107394", "Rim on objects when shadow catcher is in play\n开启阴影捕捉后边缘有硬边BUG \n\n\n\n" ]

[ "Asymmetric position vertices in circles primitives. Non-symmetrical edges in circles\nOperating system: Linux-5.11.16-2-MANJARO-x86_64-with-glibc2.33 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\nBroken: version: 2.93.0 Beta\n\nOperation which creation of circles such as `Add->Mesh->Circle`, `Add->Mesh->Cylinder` after applying have asymmetric position of vertices, which can give unexpected results such as Boolean operation with the selected Exact method.\n\nI created two circles - `A` and `B`. Circle `A` was created from menu `Add->Mesh->Circle` with radius equals 50 mm. You can see on image that parallel vertices top and bottom has asymmetric position. Also, the asymmetric arrangement of the vertices gives different lengths between the parallel vertices, which indicates that the circle has non-symmetrical edges. It shown on next image. \n\nAdditionally, for comparison I created second circle `B` from one quarter of circle and mirrored by `X` and `Y` axes for symmetric. Circle `B` has symmetric position of vertices and also symmetric edges and correct radius.\n\n\n[precission.blend](precission.blend)\n\nThis issue can affect in boolean operations with Exact option and give unexpected result when parts of meshes arrange symmetric, for example:\n\n\n\n[exact-boolean.blend](exact-boolean.blend)\n\nAlso I added to the file object created from correct circle primitives and I got expected result of Boolean operation:\n\n\n\nHowever, I noticed that the inaccuracy can see when use the millimeters system of measurement. If you switch to another system, asymmetric values you don't see but the issue will remain. What units use for calculates inside Blender?\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", "Rigid Body Constraints ignoring keyed rotation limits\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\n\n\nRigid Body Constraint limits seems to be only taking initial values, ignoring keyed values.\n\n\n1. Open attached blend file\n2. Verify that `Constraint.002` object has Rigid Body Constraint, Generic type, and Z upper angular limit keyed (from frame 1->40, 90->20 deg).\n3. Play animation.\n4. From frame 40 and on, that Z upper angular limit is keyed to be 20 deg, but the cube being hit will still rotate to 90 degrees (expecting limited to 20 deg).\n\nTested \"Generic\", \"Hinge\", \"Generic Spring\", none respects the keyed rotation limit.\n\n-----\n\nOriginal description:\n\n\nGeneric and Generic Spring constraints will ignore keyframed changes in their lower and upper limits.\n\n1. Create 4 Rigid body cubes and a passive ground plane under them.\n2. Line 3 of the cubes up on the X axis.\n3. Connect each of the 3 cubes with rigid body constraints set to generic.\n4. Set one of the cubes on the end to animated.\n5. Select the constraint between the animated cube you just made and the next one in line and set all limits to 0.\n6. Select the next constraint in the line and set all angular rotation limits to zero except the z angle upper limit, set that to 90.\n7. Set a keyframe on the upper limit Z axis of that same constraint on frame 1.\n8. Go to frame 40 and set the upper limit Z axis to 20 and keyframe it.\n9. Take the 4th cube you made and position it behind the cube on the end that is not set the animated.\n10. Take that same cube and make it animated and keyframe it on frame 40.\n11. Move that 4th cube to hit the none animated cube at the end of the line and keyframe it.\n12. Then hit play, the constraint will ignore the changed upper limit and rotate to 90 even though it shows as being only 20 in the properties panel.", "(Grease pencil) Blender freezes indefinitely when drawing using stabilize stroke function. \nOperating system: Windows 10 business 64bit\nGraphics card: Intel UHD 620/630\n\nBroken: both 3.2.2 and the experimental build 3.4.0 alpha\n\n\nWhile drawing using the stabilize stroke function (in blank grease pencil object), after some times blender freezes and stop responding, tested on both an HP prodesk g5 ( I5 8500, intel IGP UHD 630 and 8 GB of RAM) and asus zenbook (I5 7200U, UHD 620, 8GB RAM).\n\nThis only happened on both PCs equipped with intel IGP, I redid the same test on my home PC (I5 9400f, GTX 1060, 16GB RAM) and everything worked fine.\n\nIs this purely a performance issue ?\n\nJust create a blank grease pencil object and directly start drawing using the stabilize stroke function, test setup must be similar or close to the two PCs equipped with Intel IGP.", "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", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "FPS problem (movie import)\nOperating system: Windows 10\nGraphics card: rtx 2070\n\nBroken: \nWorked: Blender 3.5.1 \n\nWhen I import a 30 fps video in blender (in \"movie clip editor\"), this video will be interpreted as 120 fps per blender, making motion tracking impossible.\n\nimporting a 30fps video in movie clip editor\n\n", "Spin / Screw Adjust Last Operation: using the slider after having reset the axis will constantly pop up `Invalid/unset axis` [hard to escape]\nWindows 10\nNvidia mx 150\n\nBlender 2.9\n\nBlender starts to loose control in some functions when i press make some values to \"Zero\".\n\n1. Make a plane. goto edit mode and select face.\n2. Press \"Alt+E\" and select \"Spin\" option.\n3. Goto Last action menu, hover over the axis X value and press \"Backspace\" to make all values to zero. Error popup `Invalid/unset axis` comes up (which is correct)\n3. note here that Backspace seems broken [or intentionally disabled in recent builds], so it might be neccessary to set axis to zero \"by hand\"\n4. Now try to change the spin \"Steps\" using the slider (arrow keys are OK) and it will \"hang\" (as in: Error popup will follow the mouse) and you will have to hit ESC multiple times or force close blender.\n\n[#81042.webm](T81042.webm)", "Small improvements to 3D View Transform Manipulators\nAs per feedback from the Spring team, we would like to make some smaller improvements to the 3D View transform manipulators:\n\n\n - Increase the treshold for hiding the planar transform widgets, so that users don't accidentally drag the plane when they meant to drag the arrow\n - Increase arrow click threshold. Currently it's very unforgiving. Even if you click outside the arrow by one pixel, it doesn't register as an arrow click. Give it a few more pixels all the way around.\n - Separate the view-aligned rotation handle from the X, Y and Z rotation handles, so that users don't accidentally click the wrong one. We can make the view-aligned handle offset, like it was in 2.79\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", "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", "Particle Emitter - Particles collisions not accurate\nOperating system: Linux-5.11.0-40-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.82.00\n\nBroken: version: 3.1.0 Alpha\nWorked: This has been an ongoing problem since starting with Blender from 2.8\n\n\nParticles are not respecting collision system in every case.\n\n- Create plane and add particle system\n- Give emitted particles a positive or zero gravity value in field weights\n- Add wind force field running roughly parallel to plane.\n- Add turbulence.\n- Add collision system to plane\n\nExpected behaviour is for the particles to bounce off the plane as they are emitted in a positive Z direction and blown by turbulence against the plane. Instead they often break through. In the past this has meant that particles are bypassing the collision system such that emitted bubbles break through the hull of a submarine, and in my current case, half my sand particles to be hidden from view in a desert scene.\n\nNote attached file which shows the behaviour. Watch the simulation side on and particles can clear be seen breaking through the mesh.\n\n[Sand Wind Test.zip](Sand_Wind_Test.zip)\n\n\n\n", "Cycles GPU/CPU render difference with more than 64 transparent bounces and coplanar faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\n\n\nWhen using particle plane with transparency ( to fake volume scatter ), we have a color mismatch between CPU and GPU rendering. \n\n\n see attach file\n\n\n\n[cpu_gpu_issue.blend](cpu_gpu_issue.blend)\n \n", "bpy.ops.object.transform_apply no working after physics simulation\nOperating system: Windows 10 Pro\nGraphics card: 2x Nvidia 1080 GTX\n\nBroken: 2.8, b46245470f79, 2018-04-18\nWorked: 2.7x\n\nWhen running a rigid body simulation, it is not currently possible to apply transformation to freeze a specific frame. If you start scrubbing in the timeline, the object either goes back to original position or jumps to random position that was generated during the simulation.\n\n - add a plane and add a passive rigid body\n - add a suzanne and add an active rigid body\n - run the simulation\n - choose a frame\n - select the suzanne object\n - apply transformation/apply visual transformation\n # scrub in the timeline\n\n\n\n\nBased on the default startup or an attached .blend file (as simple as possible).", "Particle instance modifier can crash when create from Children is checked and Normal is not\nOSX 10.11.6, xeon w3680 6core 12thread \n[system-info.txt](system-info.txt)\n2.69.7 5bd8ac9\nalso Nightly 2.79 34fe3f9c069\n\n\nUsing a particle instance modifier with Children checked and Normal not checked and then attempting to change certain parameters of the particle system such as in the velocity or children tabs causes a crash. Enabling Normal in the particle instance modifier prevents this from happening.\nCreate a Plane with a hair type particle system.\nCreate a cube with a particle instance modifier and set the object to the Plane with the particle system.\nCheck the box for Children and uncheck the box for Normal.\nGo to the particle system on the Plane and check Advanced. \nDrag any of the values in Velocity or Children and soon it will crash.\n[Crash_ParticleInstance.zip](Crash_ParticleInstance.zip)", "Particle system bug with texture influence\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.95\n\nBroken: version: 3.6.0\nWorked: N/A.\n\nParticle system caching issue. \n\n1. Make a particle system with collider that kills particle. Add a cloud texture to influence it's density.\n2. Now bake.\n3. Now later when you increase or decrease size of the particle. the cache breaks. \n4. Some particle is starting to stay on collide serve instead of killing . And some particle floats around." ]

[ "Rigid body simulation behaves wildly on OSX\nMac os X 64-bit , NVIDIA GeForce 320M 256 MB\n\nBroken: Blender 2.69.11/ which is the 2.70 test build.\n\n\nWell there is something wrong with the rigid body simulator. When I add a object and make it active and add a plane which is passive. The object does drop to the plane as it should but once the active object touches the passive plane it starts to slide and move around. Physics are not properly simulated.\n\nI uploaded a video of a screen recording to show the problem/bug on my youtube page.\nSjN8_sZcngM" ]

[ "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 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", "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", "Blender sometimes crashes when loading a file with unregistered nodes\nOperating system: Windows 10 64 Bit\nGraphics card: Nvidia Geforce GTX 750 Ti\n\nBroken: 2.83.7 release\n\nSometimes when opening a file with unregistered custom nodes, Blender will crash with an `EXCEPTION_ACCESS_VIOLATION` error.\n\n**Stack trace from Visual Studio:**\n```\nblender.exe!node_free_node(bNodeTree * ntree, bNode * node) Zeile 2033\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (2033)\nblender.exe!ntree_free_data(ID * id) Zeile 227\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\node.c (227)\nblender.exe!BKE_libblock_free_datablock(ID * id, const int UNUSED_flag) Zeile 136\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\lib_id_delete.c (136)\nblender.exe!DEG::deg_free_copy_on_write_datablock(ID * id_cow) Zeile 1073\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1073)\nblender.exe!DEG::deg_update_copy_on_write_datablock(const DEG::Depsgraph * depsgraph, const DEG::IDNode * id_node) Zeile 952\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (952)\nblender.exe!DEG::deg_evaluate_copy_on_write(Depsgraph * graph, const DEG::IDNode * id_node) Zeile 1088\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval_copy_on_write.cc (1088)\nblender.exe!std::invoke<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, Depsgraph * && _Arg1, DEG::IDNode * & <_Args2_0>) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<std::_Unforced,0>::_Call<void (__cdecl*&)(Depsgraph *,DEG::IDNode const *),Depsgraph *,DEG::IDNode * &>(void(*)(Depsgraph *, const DEG::IDNode *) & <_Vals_0>, Depsgraph * && <_Vals_1>, DEG::IDNode * & <_Vals_2>) Zeile 1658\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1658)\nblender.exe!std::_Call_binder<std::_Unforced,0,1,void (__cdecl*)(Depsgraph *,DEG::IDNode const *),std::tuple<std::_Ph<1>,DEG::IDNode *>,std::tuple<Depsgraph * &&>>(std::_Invoker_ret<std::_Unforced,0> __formal, std::integer_sequence<unsigned __int64,0,1> __formal, void(*)(Depsgraph *, const DEG::IDNode *) & _Obj, std::tuple<std::_Ph<1>,DEG::IDNode *> & _Tpl, std::tuple<Depsgraph * &&> && _Ut) Zeile 1388\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1388)\nblender.exe!std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>::operator()<Depsgraph *>(Depsgraph * && <_Unbargs_0>) Zeile 1427\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (1427)\nblender.exe!std::invoke<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & _Obj, Depsgraph * && _Arg1) Zeile 1626\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1626)\nblender.exe!std::_Invoker_ret<void,1>::_Call<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> &,Depsgraph *>(std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &> & <_Vals_0>, Depsgraph * && <_Vals_1>) Zeile 1641\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\type_traits (1641)\nblender.exe!std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl&)(Depsgraph *,DEG::IDNode const *),std::_Ph<1> const &,DEG::IDNode * &>,void,Depsgraph *>::_Do_call(Depsgraph * && <_Args_0>) Zeile 904\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (904)\nblender.exe!std::_Func_class<void,Depsgraph *>::operator()(Depsgraph * <_Args_0>) Zeile 952\n\tunter A:\\Programs\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.27.29110\\include\\functional (952)\nblender.exe!DEG::`anonymous namespace'::evaluate_node(const DEG::`anonymous-namespace'::DepsgraphEvalState * state, DEG::OperationNode * operation_node) Zeile 117\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (117)\nblender.exe!DEG::`anonymous namespace'::deg_task_run_func(TaskPool * pool, void * taskdata, int thread_id) Zeile 129\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (129)\nblender.exe!BLI_task_pool_work_and_wait(TaskPool * pool) Zeile 939\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (939)\nblender.exe!BLI_task_pool_work_wait_and_reset(TaskPool * pool) Zeile 970\n\tunter C:\\blender-git\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc (970)\nblender.exe!DEG::deg_evaluate_on_refresh(DEG::Depsgraph * graph) Zeile 403\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc (403)\nblender.exe!DEG_evaluate_on_refresh(Main * bmain, Depsgraph * graph) Zeile 65\n\tunter C:\\blender-git\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc (65)\nblender.exe!scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain, bool only_if_tagged) Zeile 1329\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1329)\nblender.exe!BKE_scene_graph_update_tagged(Depsgraph * depsgraph, Main * bmain) Zeile 1367\n\tunter C:\\blender-git\\blender\\source\\blender\\blenkernel\\intern\\scene.c (1367)\nblender.exe!wm_event_do_depsgraph(bContext * C, bool is_after_open_file) Zeile 360\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (360)\nblender.exe!wm_event_do_refresh_wm_and_depsgraph(bContext * C) Zeile 387\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (387)\nblender.exe!wm_event_do_notifiers(bContext * C) Zeile 552\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.c (552)\nblender.exe!WM_main(bContext * C) Zeile 456\n\tunter C:\\blender-git\\blender\\source\\blender\\windowmanager\\intern\\wm.c (456)\nblender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Zeile 530\n\tunter C:\\blender-git\\blender\\source\\creator\\creator.c (530)\nblender.exe!invoke_main() Zeile 79\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (79)\nblender.exe!__scrt_common_main_seh() Zeile 288\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (288)\nblender.exe!__scrt_common_main() Zeile 331\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl (331)\nblender.exe!mainCRTStartup() Zeile 17\n\tunter D:\\agent\\_work\\9\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp (17)\nkernel32.dll!00007ffca1667bd4()\nntdll.dll!00007ffca1e0ce51()\n```\n\nThe exception in line 2033 of node.c says that there is an access violation when reading at position `0xFFFFFFFFFFFFFFFF`. `node->typeinfo` does exist (is not null), but `freefunc` (and actually most of the other attributes) point to `0xdddd...`. Because of that, I think that this bug might be caused by a similar issue as described in #72833.\n\nI'm not sure if a core dump helps you, it's quite large (1GB + another GB for the .pdb file) so if you need it I can look for a way to make it available to you. I'm not a C or C++ dev so I don't know what is helpful.\n\n**EDIT**: I think this crash is caused by opening files files with nodes that were registered while the file was originaly saved but not anymore.\n\nIt's a bit complicated because it doesn't happen all the time. The particular file(s) where I observed this issue use nodes from an addon (Armory3D) which supports per-project custom nodes which get registered via a `on_load_post()` handler (so there is a delay between opening the file and registering the nodes). I'm not entirely sure, but it seems like the crash occurs when the nodes are registered again. The crash even occurs when unregistering the nodes before saving the file.\n\nBecause of that complicated setup (addon required + project setup + custom node package) I will go without an example file. If you aren't able to find the cause without one, please tell me so that I can prepare a minimal project setup for you.\n\nThank you very much!\n\n*Original issue*: 1890", "Blender crashes when computing normals of a particular mesh\nOperating system: macOS (Monterey) 12.1 (21C52)\nGraphics card: AMD Radeon Pro 5300M 4 GB\nGraphics card: Intel UHD Graphics 630 1536 MB\n\nBroken: 3.0.0 (3.0.0 2021-12-03)\nWorked: Was not observed to work\n\nCrashes on opening file attached. Crashes on other files. Randomly crashes when editing using models exported from Roblox (.obj files).\n\nOpen attached blend file. You get the crash report (crashes with different stacks for other files and when editing):\n\n[hacker_revenge.blend](hacker_revenge.blend)\n\n```\nlines=12, name=Translated Report\nProcess: Blender [2869]\nPath: /Applications/Blender.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.0.0 (3.0.0 2021-12-03)\nCode Type: X86-64 (Native)\nParent Process: zsh [1661]\nResponsible: Terminal [1596]\nUser ID: 501\n\nDate/Time: 2021-12-21 10:11:52.0228 +0100\nOS Version: macOS 12.1 (21C52)\nReport Version: 12\nBridge OS Version: 6.1 (19P647)\nAnonymous UUID: BAF76297-0E65-F3CC-0672-23E0B08EE74B\n\n\nTime Awake Since Boot: 28000 seconds\n\nSystem Integrity Protection: enabled\n\nCrashed Thread: 1\n\nException Type: EXC_CRASH (SIGSEGV)\nException Codes: 0x0000000000000000, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11\nTerminating Process: Blender [2869]\n\nThread 0:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bf80451 loop_split_worker_do(LoopSplitTaskDataCommon*, LoopSplitTaskData*, BLI_Stack*) + 209\n1 Blender \t 0x10bf7f289 loop_split_generator(TaskPool*, LoopSplitTaskDataCommon*) + 361\n2 Blender \t 0x10bf7efa6 BKE_mesh_normals_loop_split + 502\n3 Blender \t 0x10bf685aa BKE_mesh_calc_normals_split_ex + 426\n4 Blender \t 0x10bde8e75 mesh_calc_modifier_final_normals(Mesh const*, CustomData_MeshMasks const*, bool, Mesh*) + 165\n5 Blender \t 0x10bde8f42 tbb::interface7::internal::delegated_function<mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)::$_0 const, void>::operator()() const + 66\n6 Blender \t 0x10c355b7b tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long) + 75\n7 Blender \t 0x10bde7482 mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**) + 1602\n8 Blender \t 0x10bde6b45 mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool) + 133\n9 Blender \t 0x10bde5cc5 makeDerivedMesh + 133\n10 Blender \t 0x10bfe1bb8 BKE_object_handle_data_update + 1016\n11 Blender \t 0x10bfe1ff4 BKE_object_eval_uber_data + 52\n12 Blender \t 0x10c491b76 blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*) + 134\n13 Blender \t 0x115d6f092 tbb::internal::function_task<Task>::execute() + 18\n14 Blender \t 0x10c362679 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long) + 393\n15 Blender \t 0x10c361cc1 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*) + 225\n16 Blender \t 0x10dff0f58 tbb::internal::task_group_base::wait() + 24\n17 Blender \t 0x115d6ed02 BLI_task_pool_work_and_wait + 482\n18 Blender \t 0x10c491941 blender::deg::deg_evaluate_on_refresh(blender::deg::Depsgraph*) + 673\n19 Blender \t 0x10c02d868 scene_graph_update_tagged + 424\n20 Blender \t 0x10c36bab3 wm_event_do_depsgraph + 179\n21 Blender \t 0x10c376068 wm_file_read_post + 312\n22 Blender \t 0x10c3752fd WM_file_read + 749\n23 Blender \t 0x10c37adb6 wm_open_mainfile__open + 342\n24 Blender \t 0x10c372de9 wm_operator_invoke + 521\n25 Blender \t 0x10c36cde9 wm_operator_call_internal + 329\n26 Blender \t 0x10c36d5d4 WM_operator_name_call_ptr_with_depends_on_cursor + 164\n27 Blender \t 0x10ce91b76 ui_apply_but_funcs_after + 310\n28 Blender \t 0x10ce8e023 ui_handler_region_menu + 387\n29 Blender \t 0x10c373706 wm_handlers_do_intern + 950\n30 Blender \t 0x10c36f0b4 wm_handlers_do + 52\n31 Blender \t 0x10c36e4e3 wm_event_do_handlers + 1539\n32 Blender \t 0x10c3665d0 WM_main + 32\n33 Blender \t 0x10bdd54eb main + 907\n34 dyld \t 0x1254f84fe start + 462\n\nThread 1 Crashed:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 6:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 7:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff808049178 _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff808049647 _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x113f9d26f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x113f9bcfe 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 13:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 caulk \t 0x7ff810c831c0 caulk::mach::semaphore::wait_or_error() + 16\n2 caulk \t 0x7ff810c6a08a caulk::concurrent::details::worker_thread::run() + 36\n3 caulk \t 0x7ff810c69d4e 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*) + 41\n4 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n5 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 14:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 15:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x7ff8081c2aba mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff8081c2e2b mach_msg + 59\n2 CoreAudio \t 0x7ff809e4695b HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 CoreAudio \t 0x7ff809cd50ff HALC_ProxyIOContext::IOWorkLoop() + 3937\n4 CoreAudio \t 0x7ff809cd3bc1 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63\n5 CoreAudio \t 0x7ff809e9c76c HALB_IOThread::Entry(void*) + 72\n6 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 16:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 18:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 21:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 22:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 23:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 24:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 25:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 26:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 27:\n0 libsystem_kernel.dylib \t 0x7ff8081c2af6 semaphore_wait_trap + 10\n1 Blender \t 0x10c35d378 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x10c35d219 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\nThread 28:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 29:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 30:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 31:\n0 libsystem_pthread.dylib \t 0x7ff8081fafec start_wqthread + 0\n\nThread 32:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x7ff8081c2aba mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff8081c2e2b mach_msg + 59\n2 CoreFoundation \t 0x7ff8082c6af2 __CFRunLoopServiceMachPort + 319\n3 CoreFoundation \t 0x7ff8082c51cb __CFRunLoopRun + 1325\n4 CoreFoundation \t 0x7ff8082c45dd CFRunLoopRunSpecific + 563\n5 AppKit \t 0x7ff80ae61d98 _NSEventThread + 132\n6 libsystem_pthread.dylib \t 0x7ff8081ff4f4 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff8081fb00f thread_start + 15\n\n\nThread 1 crashed with X86 Thread State (64-bit):\n rax: 0x000000000000000e rbx: 0x0000600003c40090 rcx: 0x000070000d0a5f08 rdx: 0x0000000000000028\n rdi: 0x0000000000002403 rsi: 0x0000000000000003 rbp: 0x000070000d0a5f20 rsp: 0x000070000d0a5f08\n r8: 0x0000000000002503 r9: 0x0000000000000000 r10: 0x0000000000002403 r11: 0x0000000000000246\n r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000600003c40090 r15: 0xffffffffffffffff\n rip: 0x00007ff8081c2af6 rfl: 0x0000000000000246 cr2: 0x000070000d0a5ff8\n \nLogical CPU: 0\nError Code: 0x01000024 \nTrap Number: 133\n\n\nBinary Images:\n 0x10bc58000 - 0x118253fff org.blenderfoundation.blender (3.0.0) <8acf8f8a-1a0b-37b4-a45b-75aaca58c182> /Applications/Blender.app/Contents/MacOS/Blender\n 0x1254f3000 - 0x12555efff dyld (*) <cef5a27a-d50b-3020-af03-1734b19bc8c5> /usr/lib/dyld\n 0x7ff8081c2000 - 0x7ff8081f8fff libsystem_kernel.dylib (*) <5aa1e5be-b5b8-3a02-9885-a8c99e0ca378> /usr/lib/system/libsystem_kernel.dylib\n 0x7ff808046000 - 0x7ff80808cfff libdispatch.dylib (*) <c8f7bfb6-4b1a-37cd-a32d-cd5069c916df> /usr/lib/system/libdispatch.dylib\n 0x7ff8081f9000 - 0x7ff808204fff libsystem_pthread.dylib (*) <6c7561b4-4b92-3f45-921e-abe669299844> /usr/lib/system/libsystem_pthread.dylib\n 0x7ff810c68000 - 0x7ff810c8afff com.apple.audio.caulk (1.0) <e76d1ab3-89c2-3a93-990b-30827fcf89b0> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7ff809b1e000 - 0x7ff80a245fff com.apple.audio.CoreAudio (5.0) <33f55d9c-eaef-3fbd-add5-ed3e54925762> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x7ff808246000 - 0x7ff808748fff com.apple.CoreFoundation (6.9) <eab0e216-2a9e-31ce-9164-fdf3ebcf7bd3> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7ff80acb5000 - 0x7ff80bb43fff com.apple.AppKit (6.9) <d23b9681-3764-3298-a716-fbb511dd5a7c> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 0\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: 0\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\nWritable regions: Total=2.3G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.3G(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 384K 3 \nActivity Tracing 256K 1 \nCG backing stores 2688K 4 \nCG image 76K 4 \nColorSync 224K 25 \nCoreAnimation 116K 9 \nCoreGraphics 12K 2 \nCoreUI image data 972K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 436.3M 85 \nMALLOC guard page 48K 10 \nMALLOC_MEDIUM (reserved) 1.4G 12 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 132K 33 \nStack 55.8M 33 \nVM_ALLOCATE 34.1M 147 \nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\n__DATA 98.7M 349 \n__DATA_CONST 17.0M 205 \n__DATA_DIRTY 774K 118 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 698.8M 17 \n__OBJC_RO 81.8M 1 \n__OBJC_RW 3136K 2 \n__TEXT 479.1M 361 \n__UNICODE 588K 1 \ndyld private memory 1088K 3 \nmapped file 163.7M 24 \nshared memory 808K 22 \n=========== ======= ======= \nTOTAL 3.8G 1487 \nTOTAL, minus reserved VM space 2.0G 1487 \n```\n\n```\nlines=12, name=Full Report\n{\"app_name\":\"Blender\",\"timestamp\":\"2021-12-21 10:11:52.00 +0100\",\"app_version\":\"3.0.0\",\"slice_uuid\":\"8acf8f8a-1a0b-37b4-a45b-75aaca58c182\",\"build_version\":\"3.0.0 2021-12-03\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 12.1 (21C52)\",\"incident_id\":\"9B83A860-E322-4D03-B0CE-187C62682666\",\"name\":\"Blender\"}\n{\n \"uptime\" : 28000,\n \"procLaunch\" : \"2021-12-21 10:11:31.6855 +0100\",\n \"procRole\" : \"Foreground\",\n \"version\" : 2,\n \"userID\" : 501,\n \"deployVersion\" : 210,\n \"modelCode\" : \"MacBookPro16,1\",\n \"procStartAbsTime\" : 28935533255199,\n \"coalitionID\" : 1696,\n \"osVersion\" : {\n \"train\" : \"macOS 12.1\",\n \"build\" : \"21C52\",\n \"releaseType\" : \"User\"\n },\n \"captureTime\" : \"2021-12-21 10:11:52.0228 +0100\",\n \"incident\" : \"9B83A860-E322-4D03-B0CE-187C62682666\",\n \"bug_type\" : \"309\",\n \"pid\" : 2869,\n \"procExitAbsTime\" : 28955868010950,\n \"cpuType\" : \"X86-64\",\n \"procName\" : \"Blender\",\n \"procPath\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.0.0\",\"CFBundleVersion\":\"3.0.0 2021-12-03\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n \"storeInfo\" : {\"deviceIdentifierForVendor\":\"39CB2ACC-1148-5821-AB90-8D6F120CC508\",\"thirdParty\":true},\n \"parentProc\" : \"zsh\",\n \"parentPid\" : 1661,\n \"coalitionName\" : \"com.apple.Terminal\",\n \"crashReporterKey\" : \"BAF76297-0E65-F3CC-0672-23E0B08EE74B\",\n \"responsiblePid\" : 1596,\n \"responsibleProc\" : \"Terminal\",\n \"bridgeVersion\" : {\"build\":\"19P647\",\"train\":\"6.1\"},\n \"sip\" : \"enabled\",\n \"isCorpse\" : 1,\n \"exception\" : {\"codes\":\"0x0000000000000000, 0x0000000000000000\",\"rawCodes\":[0,0],\"type\":\"EXC_CRASH\",\"signal\":\"SIGSEGV\"},\n \"termination\" : {\"flags\":0,\"code\":11,\"namespace\":\"SIGNAL\",\"indicator\":\"Segmentation fault: 11\",\"byProc\":\"Blender\",\"byPid\":2869},\n \"extMods\" : {\"caller\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"system\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"targeted\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"warnings\":0},\n \"faultingThread\" : 1,\n \"threads\" : [{\"id\":1319763,\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":3310673,\"symbol\":\"loop_split_worker_do(LoopSplitTaskDataCommon*, LoopSplitTaskData*, BLI_Stack*)\",\"symbolLocation\":209,\"imageIndex\":0},{\"imageOffset\":3306121,\"symbol\":\"loop_split_generator(TaskPool*, LoopSplitTaskDataCommon*)\",\"symbolLocation\":361,\"imageIndex\":0},{\"imageOffset\":3305382,\"symbol\":\"BKE_mesh_normals_loop_split\",\"symbolLocation\":502,\"imageIndex\":0},{\"imageOffset\":3212714,\"symbol\":\"BKE_mesh_calc_normals_split_ex\",\"symbolLocation\":426,\"imageIndex\":0},{\"imageOffset\":1642101,\"symbol\":\"mesh_calc_modifier_final_normals(Mesh const*, CustomData_MeshMasks const*, bool, Mesh*)\",\"symbolLocation\":165,\"imageIndex\":0},{\"imageOffset\":1642306,\"symbol\":\"tbb::interface7::internal::delegated_function<mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)::$_0 const, void>::operator()() const\",\"symbolLocation\":66,\"imageIndex\":0},{\"imageOffset\":7330683,\"symbol\":\"tbb::interface7::internal::isolate_within_arena(tbb::interface7::internal::delegate_base&, long)\",\"symbolLocation\":75,\"imageIndex\":0},{\"imageOffset\":1635458,\"symbol\":\"mesh_calc_modifiers(Depsgraph*, Scene*, Object*, bool, bool, CustomData_MeshMasks const*, int, bool, bool, Mesh**, Mesh**, GeometrySet**)\",\"symbolLocation\":1602,\"imageIndex\":0},{\"imageOffset\":1633093,\"symbol\":\"mesh_build_data(Depsgraph*, Scene*, Object*, CustomData_MeshMasks const*, bool)\",\"symbolLocation\":133,\"imageIndex\":0},{\"imageOffset\":1629381,\"symbol\":\"makeDerivedMesh\",\"symbolLocation\":133,\"imageIndex\":0},{\"imageOffset\":3709880,\"symbol\":\"BKE_object_handle_data_update\",\"symbolLocation\":1016,\"imageIndex\":0},{\"imageOffset\":3710964,\"symbol\":\"BKE_object_eval_uber_data\",\"symbolLocation\":52,\"imageIndex\":0},{\"imageOffset\":8625014,\"symbol\":\"blender::deg::(anonymous namespace)::deg_task_run_func(TaskPool*, void*)\",\"symbolLocation\":134,\"imageIndex\":0},{\"imageOffset\":168915090,\"symbol\":\"tbb::internal::function_task<Task>::execute()\",\"symbolLocation\":18,\"imageIndex\":0},{\"imageOffset\":7382649,\"symbol\":\"tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::process_bypass_loop(tbb::internal::context_guard_helper<false>&, tbb::task*, long)\",\"symbolLocation\":393,\"imageIndex\":0},{\"imageOffset\":7380161,\"symbol\":\"tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all(tbb::task&, tbb::task*)\",\"symbolLocation\":225,\"imageIndex\":0},{\"imageOffset\":37326680,\"symbol\":\"tbb::internal::task_group_base::wait()\",\"symbolLocation\":24,\"imageIndex\":0},{\"imageOffset\":168914178,\"symbol\":\"BLI_task_pool_work_and_wait\",\"symbolLocation\":482,\"imageIndex\":0},{\"imageOffset\":8624449,\"symbol\":\"blender::deg::deg_evaluate_on_refresh(blender::deg::Depsgraph*)\",\"symbolLocation\":673,\"imageIndex\":0},{\"imageOffset\":4020328,\"symbol\":\"scene_graph_update_tagged\",\"symbolLocation\":424,\"imageIndex\":0},{\"imageOffset\":7420595,\"symbol\":\"wm_event_do_depsgraph\",\"symbolLocation\":179,\"imageIndex\":0},{\"imageOffset\":7463016,\"symbol\":\"wm_file_read_post\",\"symbolLocation\":312,\"imageIndex\":0},{\"imageOffset\":7459581,\"symbol\":\"WM_file_read\",\"symbolLocation\":749,\"imageIndex\":0},{\"imageOffset\":7482806,\"symbol\":\"wm_open_mainfile__open\",\"symbolLocation\":342,\"imageIndex\":0},{\"imageOffset\":7450089,\"symbol\":\"wm_operator_invoke\",\"symbolLocation\":521,\"imageIndex\":0},{\"imageOffset\":7425513,\"symbol\":\"wm_operator_call_internal\",\"symbolLocation\":329,\"imageIndex\":0},{\"imageOffset\":7427540,\"symbol\":\"WM_operator_name_call_ptr_with_depends_on_cursor\",\"symbolLocation\":164,\"imageIndex\":0},{\"imageOffset\":19110774,\"symbol\":\"ui_apply_but_funcs_after\",\"symbolLocation\":310,\"imageIndex\":0},{\"imageOffset\":19095587,\"symbol\":\"ui_handler_region_menu\",\"symbolLocation\":387,\"imageIndex\":0},{\"imageOffset\":7452422,\"symbol\":\"wm_handlers_do_intern\",\"symbolLocation\":950,\"imageIndex\":0},{\"imageOffset\":7434420,\"symbol\":\"wm_handlers_do\",\"symbolLocation\":52,\"imageIndex\":0},{\"imageOffset\":7431395,\"symbol\":\"wm_event_do_handlers\",\"symbolLocation\":1539,\"imageIndex\":0},{\"imageOffset\":7398864,\"symbol\":\"WM_main\",\"symbolLocation\":32,\"imageIndex\":0},{\"imageOffset\":1561835,\"symbol\":\"main\",\"symbolLocation\":907,\"imageIndex\":0},{\"imageOffset\":21758,\"symbol\":\"start\",\"symbolLocation\":462,\"imageIndex\":1}]},{\"triggered\":true,\"id\":1319769,\"threadState\":{\"r13\":{\"value\":0},\"rax\":{\"value\":14},\"rflags\":{\"value\":582},\"cpu\":{\"value\":0},\"r14\":{\"value\":105553179443344},\"rsi\":{\"value\":3},\"r8\":{\"value\":9475},\"cr2\":{\"value\":123145521094648},\"rdx\":{\"value\":40},\"r10\":{\"value\":9219},\"r9\":{\"value\":0},\"r15\":{\"value\":18446744073709551615},\"rbx\":{\"value\":105553179443344},\"trap\":{\"value\":133},\"err\":{\"value\":16777252},\"r11\":{\"value\":582},\"rip\":{\"value\":140703264680694,\"matchesCrashFrame\":1},\"rbp\":{\"value\":123145521094432},\"rsp\":{\"value\":123145521094408},\"r12\":{\"value\":0},\"rcx\":{\"value\":123145521094408},\"flavor\":\"x86_THREAD_STATE\",\"rdi\":{\"value\":9219}},\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319770,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319771,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319772,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319773,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319774,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319775,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319776,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319777,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319778,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319779,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319780,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":12664,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":13895,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":137646703,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":137641214,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319784,\"name\":\"AMCP Logging Spool\",\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":111040,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":16,\"imageIndex\":5},{\"imageOffset\":8330,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":36,\"imageIndex\":5},{\"imageOffset\":7502,\"symbol\":\"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*)\",\"symbolLocation\":41,\"imageIndex\":5},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319824,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319830,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":2746,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":3627,\"symbol\":\"mach_msg\",\"symbolLocation\":59,\"imageIndex\":2},{\"imageOffset\":3311963,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":111,\"imageIndex\":6},{\"imageOffset\":1798399,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3937,\"imageIndex\":6},{\"imageOffset\":1792961,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":63,\"imageIndex\":6},{\"imageOffset\":3663724,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":72,\"imageIndex\":6},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319965,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319975,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319976,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319977,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319978,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319979,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319980,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319981,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319982,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319983,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319984,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319985,\"frames\":[{\"imageOffset\":2806,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7361400,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7361049,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":1319991,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1319993,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320011,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320012,\"frames\":[{\"imageOffset\":8172,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":1320013,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":2746,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":3627,\"symbol\":\"mach_msg\",\"symbolLocation\":59,\"imageIndex\":2},{\"imageOffset\":527090,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":319,\"imageIndex\":7},{\"imageOffset\":520651,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1325,\"imageIndex\":7},{\"imageOffset\":517597,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":563,\"imageIndex\":7},{\"imageOffset\":1756568,\"symbol\":\"_NSEventThread\",\"symbolLocation\":132,\"imageIndex\":8},{\"imageOffset\":25844,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8207,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]}],\n \"usedImages\" : [\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4492460032,\n \"CFBundleShortVersionString\" : \"3.0.0\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 207601664,\n \"uuid\" : \"8acf8f8a-1a0b-37b4-a45b-75aaca58c182\",\n \"path\" : \"\\/Applications\\/Blender.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.0.0 2021-12-03\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4920913920,\n \"size\" : 442368,\n \"uuid\" : \"cef5a27a-d50b-3020-af03-1734b19bc8c5\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703264677888,\n \"size\" : 225280,\n \"uuid\" : \"5aa1e5be-b5b8-3a02-9885-a8c99e0ca378\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703263121408,\n \"size\" : 290816,\n \"uuid\" : \"c8f7bfb6-4b1a-37cd-a32d-cd5069c916df\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703264903168,\n \"size\" : 49152,\n \"uuid\" : \"6c7561b4-4b92-3f45-921e-abe669299844\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703410061312,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 143360,\n \"uuid\" : \"e76d1ab3-89c2-3a93-990b-30827fcf89b0\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703291269120,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7503872,\n \"uuid\" : \"33f55d9c-eaef-3fbd-add5-ed3e54925762\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64h\",\n \"base\" : 140703265218560,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 5255168,\n \"uuid\" : \"eab0e216-2a9e-31ce-9164-fdf3ebcf7bd3\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1856.105\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703309713408,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 15265792,\n \"uuid\" : \"d23b9681-3764-3298-a716-fbb511dd5a7c\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2113.20.111\"\n }\n],\n \"sharedCache\" : {\n \"base\" : 140703261675520,\n \"size\" : 15216738304,\n \"uuid\" : \"40432a03-88d3-305f-9c0c-e7549e71d927\"\n},\n \"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.2G resident=0K(0%) swapped_out_or_unallocated=1.2G(100%)\\nWritable regions: Total=2.3G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=2.3G(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 384K 3 \\nActivity Tracing 256K 1 \\nCG backing stores 2688K 4 \\nCG image 76K 4 \\nColorSync 224K 25 \\nCoreAnimation 116K 9 \\nCoreGraphics 12K 2 \\nCoreUI image data 972K 7 \\nFoundation 16K 1 \\nKernel Alloc Once 8K 1 \\nMALLOC 436.3M 85 \\nMALLOC guard page 48K 10 \\nMALLOC_MEDIUM (reserved) 1.4G 12 reserved VM address space (unallocated)\\nMALLOC_NANO (reserved) 384.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 132K 33 \\nStack 55.8M 33 \\nVM_ALLOCATE 34.1M 147 \\nVM_ALLOCATE (reserved) 32K 1 reserved VM address space (unallocated)\\n__DATA 98.7M 349 \\n__DATA_CONST 17.0M 205 \\n__DATA_DIRTY 774K 118 \\n__FONT_DATA 4K 1 \\n__GLSLBUILTINS 5176K 1 \\n__LINKEDIT 698.8M 17 \\n__OBJC_RO 81.8M 1 \\n__OBJC_RW 3136K 2 \\n__TEXT 479.1M 361 \\n__UNICODE 588K 1 \\ndyld private memory 1088K 3 \\nmapped file 163.7M 24 \\nshared memory 808K 22 \\n=========== ======= ======= \\nTOTAL 3.8G 1487 \\nTOTAL, minus reserved VM space 2.0G 1487 \\n\",\n \"legacyInfo\" : {\n \"threadTriggered\" : {\n\n }\n},\n \"trialInfo\" : {\n \"rollouts\" : [\n {\n \"rolloutId\" : \"601d9415f79519000ccd4b69\",\n \"factorPackIds\" : {\n \"SIRI_TEXT_TO_SPEECH\" : \"6194416f2171a2330e561f05\"\n },\n \"deploymentId\" : 240000355\n },\n {\n \"rolloutId\" : \"5fc94383418129005b4e9ae0\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000192\n },\n {\n \"rolloutId\" : \"607844aa04477260f58a8077\",\n \"factorPackIds\" : {\n \"SIRI_MORPHUN_ASSETS\" : \"6103050cbfe6dc472e1c982a\"\n },\n \"deploymentId\" : 240000066\n },\n {\n \"rolloutId\" : \"5ffde50ce2aacd000d47a95f\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000090\n },\n {\n \"rolloutId\" : \"602ad4dac86151000cf27e46\",\n \"factorPackIds\" : {\n \"SIRI_DICTATION_ASSETS\" : \"6193d03f2171a2330e561dfc\"\n },\n \"deploymentId\" : 240000290\n },\n {\n \"rolloutId\" : \"60da5e84ab0ca017dace9abf\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000008\n }\n ],\n \"experiments\" : [\n\n ]\n}\n}\n\nModel: MacBookPro16,1, BootROM 1715.60.5.0.0 (iBridge: 19.16.10647.0.0,0), 6 processors, 6-Core Intel Core i7, 2,6 GHz, 32 GB, SMC \nGraphics: Intel UHD Graphics 630, Intel UHD Graphics 630, Built-In\nGraphics: AMD Radeon Pro 5300M, AMD Radeon Pro 5300M, PCIe, 4 GB\nDisplay: Color LCD, 3072 x 1920 Retina, Main, MirrorOff, Online\nMemory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J\nMemory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, Micron, MT40A2G8NEA-062E:J\nAirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Jul 12 2021 18:02:56 version 9.30.464.0.32.5.76 FWID 01-c081cfed\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: Wi-Fi, AirPort, en0\nUSB Device: USB31Bus\nUSB Device: T2Bus\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```", "Crash after linked object is edited then switched to another scene (object origin scene)\nOperating system: Window10\nGraphics card:\n\n\nBroken: 2.90.1 ( hash: 3e85bb34d0d7 )\nWorked: unknown\n\n\nBlender simply crash and close the window directly after editing the \"linked\" object from 2nd screen and switched back to 1st screen.\n\n\n\nThis error can be reproduced with 2 scenes setup.\n\n- First scene contains a simple mesh object. Let's say a \"Cube\" object\n- Create a second scene.\n- In the first scene, select the \"Cube\" object then \"Make Links\" {key Ctrl L} to 2nd scene.\n- Now, we switch to 2nd scene. The 2nd scene now should contains the same \"linked\" Cube object from 1st scene.\n- Okay, this is important step. In this 2nd scene, we select this \"linked\" Cube object and set the Relations to: *Object > Relations > Make Single User > Object*\n- After that, we go to \"Edit Mode\" for this \"linked\" Cube object.\n- In \"Edit mode\", make a simple change to this \"linked\" Cube object.\n- Once simple change is done, don't do anything else. You just directly switch back to \"First scene\". CRASH here.\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", "Outliner crash/assert when deleting an override on a mesh\nOperating system: Linux-6.1.18-200.fc37.x86_64-x86_64-with-glibc2.36 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon Graphics (renoir, LLVM 15.0.7, DRM 3.49, 6.1.18-200.fc37.x86_64) AMD 4.6 (Core Profile) Mesa 22.3.7\n\nBroken: version: 4.0.0 Alpha\nWorked: never\n\nOutliner crash/assert when deleting an override on a mesh\n\nIn a debug build:\n- open `main.blend`\n- clear the override on the mesh in the Outliner\n\n\nThere seems to be something wrong with updating the tree, it still wants to draw the mesh override?\n(tried some additional stuff with `DEG_relations_tag_update`, `outliner_cleanup_tree`, `BKE_view_layer_synced_ensure` in `id_override_library_clear_single_process` to no avail...)\n\n```\n==1574045==ERROR: AddressSanitizer: heap-use-after-free on address 0x61c00030490c at pc 0x00000b189b87 bp 0x7ffe8b70fea0 sp 0x7ffe8b70fe98\nREAD of size 4 at 0x61c00030490c thread T0\n #0 0xb189b86 in outliner_but_identity_cmp_context_id_fn /blender/source/blender/editors/space_outliner/outliner_draw.cc:1973\n #1 0xa1946d9 in ui_but_equals_old /blender/source/blender/editors/interface/interface.cc:732\n #2 0xa19822c in ui_but_update_from_old_block /blender/source/blender/editors/interface/interface.cc:967\n #3 0xa1a07ab in UI_block_update_from_old(bContext const*, uiBlock*) /blender/source/blender/editors/interface/interface.cc:1869\n #4 0xa1a1cea in UI_block_end_ex(bContext const*, uiBlock*, int const*, int*) /blender/source/blender/editors/interface/interface.cc:1964\n #5 0xa1a2cd5 in UI_block_end(bContext const*, uiBlock*) /blender/source/blender/editors/interface/interface.cc:2058\n #6 0xb1a58dc in blender::ed::outliner::draw_outliner(bContext const*) /blender/source/blender/editors/space_outliner/outliner_draw.cc:4097\n #7 0xb210d95 in outliner_main_region_draw /blender/source/blender/editors/space_outliner/space_outliner.cc:88\n #8 0x7025c43 in ED_region_do_draw(bContext*, ARegion*) /blender/source/blender/editors/screen/area.cc:539\n #9 0x42a3126 in wm_draw_window_offscreen /blender/source/blender/windowmanager/intern/wm_draw.cc:1000\n #10 0x42a482a in wm_draw_window /blender/source/blender/windowmanager/intern/wm_draw.cc:1166\n #11 0x42a78e4 in wm_draw_update(bContext*) /blender/source/blender/windowmanager/intern/wm_draw.cc:1564\n #12 0x428bfd8 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:645\n #13 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #14 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n #15 0x7f56eb04a5c8 in __libc_start_main@GLIBC_2.2.5 (/lib64/libc.so.6+0x275c8)\n #16 0x8ee494 in _start (/build_linux_debug/bin/blender+0x8ee494)\n\n0x61c00030490c is located 140 bytes inside of 1712-byte region [0x61c000304880,0x61c000304f30)\nfreed by thread T0 here:\n #0 0x7f56f4cb9388 in __interceptor_free.part.0 (/lib64/libasan.so.8+0xb9388)\n #1 0x4278fad in MEM_lockfree_freeN /blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:104\n #2 0xdd817a in BKE_id_free_ex /blender/source/blender/blenkernel/intern/lib_id_delete.cc:170\n #3 0xdd9f4d in id_delete /blender/source/blender/blenkernel/intern/lib_id_delete.cc:366\n #4 0xdda2a9 in BKE_id_delete_ex /blender/source/blender/blenkernel/intern/lib_id_delete.cc:384\n #5 0xdda304 in BKE_id_delete /blender/source/blender/blenkernel/intern/lib_id_delete.cc:389\n #6 0xb1d5a80 in id_override_library_clear_single_process /blender/source/blender/editors/space_outliner/outliner_tools.cc:1489\n #7 0xb1da009 in outliner_liboverride_operation_exec /blender/source/blender/editors/space_outliner/outliner_tools.cc:1959\n #8 0x43624d5 in WM_menu_invoke_ex(bContext*, wmOperator*, wmOperatorCallContext) /blender/source/blender/windowmanager/intern/wm_operators.cc:1046\n #9 0x4362a0b in WM_menu_invoke(bContext*, wmOperator*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_operators.cc:1071\n #10 0x42b76d9 in wm_operator_invoke /blender/source/blender/windowmanager/intern/wm_event_system.cc:1530\n #11 0x42b943e in wm_operator_call_internal /blender/source/blender/windowmanager/intern/wm_event_system.cc:1731\n #12 0x42b96a7 in WM_operator_name_call_ptr(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1779\n #13 0x42babf9 in WM_operator_name_call_ptr_with_depends_on_cursor(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*, char const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1972\n #14 0xa2348a7 in ui_apply_but_funcs_after /blender/source/blender/editors/interface/interface_handlers.cc:1038\n #15 0xa2c8f30 in ui_popup_handler /blender/source/blender/editors/interface/interface_handlers.cc:11657\n #16 0x42b0485 in wm_handler_ui_call /blender/source/blender/windowmanager/intern/wm_event_system.cc:818\n #17 0x42d0410 in wm_handlers_do_intern /blender/source/blender/windowmanager/intern/wm_event_system.cc:3319\n #18 0x42d17cf in wm_handlers_do /blender/source/blender/windowmanager/intern/wm_event_system.cc:3436\n #19 0x42dbd54 in wm_event_do_handlers(bContext*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:4063\n #20 0x428bfc0 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:639\n #21 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #22 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n\npreviously allocated by thread T0 here:\n #0 0x7f56f4cba097 in calloc (/lib64/libasan.so.8+0xba097)\n #1 0x42796e2 in MEM_lockfree_callocN /blender/intern/guardedalloc/intern/mallocn_lockfree_impl.c:210\n #2 0x42646c0 in DNA_struct_reconstruct /blender/source/blender/makesdna/intern/dna_genfile.cc:1236\n #3 0x44e9d47 in read_struct /blender/source/blender/blenloader/intern/readfile.cc:1810\n #4 0x44f74ff in read_libblock /blender/source/blender/blenloader/intern/readfile.cc:2955\n #5 0x450125d in blo_read_file_internal /blender/source/blender/blenloader/intern/readfile.cc:3624\n #6 0x44d538b in BLO_read_from_file /blender/source/blender/blenloader/intern/readblenentry.cc:414\n #7 0x913295 in BKE_blendfile_read /blender/source/blender/blenkernel/intern/blendfile.cc:1014\n #8 0x4301733 in WM_file_read(bContext*, char const*, ReportList*) /blender/source/blender/windowmanager/intern/wm_files.cc:1024\n #9 0x430e599 in wm_file_read_opwrap /blender/source/blender/windowmanager/intern/wm_files.cc:2718\n #10 0x430f626 in wm_open_mainfile__open /blender/source/blender/windowmanager/intern/wm_files.cc:2841\n #11 0x430e957 in operator_state_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2754\n #12 0x430f889 in wm_open_mainfile_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2865\n #13 0x430ec2d in wm_open_mainfile__discard_changes /blender/source/blender/windowmanager/intern/wm_files.cc:2793\n #14 0x430e957 in operator_state_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2754\n #15 0x430f889 in wm_open_mainfile_dispatch /blender/source/blender/windowmanager/intern/wm_files.cc:2865\n #16 0x430f8b6 in wm_open_mainfile_invoke /blender/source/blender/windowmanager/intern/wm_files.cc:2870\n #17 0x42b76d9 in wm_operator_invoke /blender/source/blender/windowmanager/intern/wm_event_system.cc:1530\n #18 0x42b959e in wm_operator_call_internal /blender/source/blender/windowmanager/intern/wm_event_system.cc:1765\n #19 0x42b96a7 in WM_operator_name_call_ptr(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1779\n #20 0x42babf9 in WM_operator_name_call_ptr_with_depends_on_cursor(bContext*, wmOperatorType*, wmOperatorCallContext, PointerRNA*, wmEvent const*, char const*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:1972\n #21 0xa2348a7 in ui_apply_but_funcs_after /blender/source/blender/editors/interface/interface_handlers.cc:1038\n #22 0xa2c8f30 in ui_popup_handler /blender/source/blender/editors/interface/interface_handlers.cc:11657\n #23 0x42b0485 in wm_handler_ui_call /blender/source/blender/windowmanager/intern/wm_event_system.cc:818\n #24 0x42d0410 in wm_handlers_do_intern /blender/source/blender/windowmanager/intern/wm_event_system.cc:3319\n #25 0x42d17cf in wm_handlers_do /blender/source/blender/windowmanager/intern/wm_event_system.cc:3436\n #26 0x42dbd54 in wm_event_do_handlers(bContext*) /blender/source/blender/windowmanager/intern/wm_event_system.cc:4063\n #27 0x428bfc0 in WM_main(bContext*) /blender/source/blender/windowmanager/intern/wm.cc:639\n #28 0x8ef1a5 in main /blender/source/creator/creator.cc:593\n #29 0x7f56eb04a50f in __libc_start_call_main (/lib64/libc.so.6+0x2750f)\n\nSUMMARY: AddressSanitizer: heap-use-after-free /blender/source/blender/editors/space_outliner/outliner_draw.cc:1973 in outliner_but_identity_cmp_context_id_fn\nShadow bytes around the buggy address:\n 0x0c38800588d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n 0x0c38800588e0: 00 00 00 00 00 00 00 00 fa fa fa fa fa fa fa fa\n 0x0c38800588f0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c3880058900: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa\n 0x0c3880058910: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n=>0x0c3880058920: fd[fd]fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058930: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058940: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058950: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058960: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd\n 0x0c3880058970: 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 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==1574045==ABORTING\n```\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.", "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)", "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", "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```", "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", "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "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```" ]

[ "Adding a mesh to a hidden object and undo the operation causes Blender to crash\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\nBroken: version: 2.81 (sub 16)\n\nAdding a mesh to an object in edit mode while it's hidden and undo this operation makes Blender crash.\n\n1. Start from the default scene\n2. Select the cube and go in edit mode\n3. Hide the cube by clicking the little eye in the \"outliner\" tab (editor tab)\n4. Add a mesh (Shift + A) to the object (es. circle)\n\nIf you unhide the cube you can see that the circle mesh is correctly added to the cube and you can continue working on the scene,\nbut if you undo the step 4 Blender crashes\n\nI also noticed that, after step 4 (when you still have the circle selected after unhiding the cube), if you do operations on the circle (like scaling, moving, extruding...) and undo these operations Blender also crashes, BUT if after these operations you select something else in the cube object (like a vertex of the cube) and start undoing only the \"adding of the circle\" (step 4) make Blender crashes, other operations (scaling...) are undone correctly.\n\nThanks have a nice day", "Undo Crashes Blender\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nUndo after adding one 3d object to a hidden in viewport object closes Blender without bug report.\n\n\n1 - Add a 3d object to the scene\n2 - Enter edit mode\n3- Make the object hidden in the viewport options (eye button)\n4- Add a new 3d object inside that hidden object (without making them visible in viewport)\n5 - press Ctl+z and Blender closes\n\nI hope this helps\n\nWith my best regards\n\n", "Using undo after adding an object in edit mode to an object hidden in viewport causes a crash\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 399.24\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nAdding a mesh to a hidden object in edit mode, followed by an undo causes Blender to crash.\n\n 1. Select an object and switch to the edit mode\n 2. Hide or disable the currently edited object in the viewport through the outliner (eye icon or monitor icon)\n 3. Add a new geometry to the mesh, e.g. by adding a vertex\n 4. Undo the previous step (CTRL + Z)\n\n" ]

[ "Working sliders are faded in the overlays panel\nBroken: 3.0\n\n**Short description of error** \nthe wireframe and wireframe opacity sliders are faded in the overlays panel even when they're working.\n\nFor better visibility, delete the cube, add a suzanne, press ctrl+3 to subdivide it, then apply the modifier.\nIn the Object Properties, under viewport display, turn on \"show edges\" OR set the object to \"Display As: Wire\".\nIn the viewport's Overlays panel, drag the wireframe threshold and wireframe opacity sliders. Make sure that you are in solid shading and the wireframe option is off in the overlays panel. \nThe sliders are faded even though they are working.", "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", "EEVEE: Mixing between a fully transparent and holdout shader yields a half transparent result\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.2.0 Release Candidate\nWorked: I thinck the issue is for \"all\" versions of blender\n\nHoldout shader having issue with alpha (semi transparency).\n\nPut a image plane with exr image that contain alpha. When using a holdout shader mixed with another shader (transparency shader for exemple) the alpha of the image sequence is used for the mix of the 2 shaders. It should have a complete transparent image with the holdout of other object in the scene. The issue is that there is a dark outline for the semi transparent. Holdout have issue dealing with semi tranparency ? or maybe something else.\nSee the attached image to understand the issue.\n\n\n", "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", "environment pass is occluded by geometry making it unusuable with a shadowcatcher\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.83 (sub 1)\nWorked: unsure if ever\n\nenvironment pass is occluded by geometry making it unusuable with a shadowcatcher\n\n\nopen attached .blend, go to compositing workspace, hit f12, when finished use the split viewer factor to slide between the image and the environment pass. \n\nPerhaps the transparency section needs an additional 'shadow catchers are transparent'.......although that wouldn't make much sense as shadow catchers should always be transparent. Regardless, the environment pass definitely shouldn't contain any geometry information. Is there ever a scenario where you'd want the environment AOV to be jet black where the 3d objects are located?\n\n[environment alpha bug.blend](environment_alpha_bug.blend)", "Blender 3.0 Denoising on Transparency Creates Artifacting (Blend included)\nOperating system: Win 10 (latest update)\nGraphics card: RTX 3090\n\nBroken: (3.0.0 and 3.0.1 dc2d18018171 Branch: Master)\nWorked: (2.9.0)\n\nWhen enabling transparency under \"Film\" settings, artifacts occurs in the transparency channel\n\nOpen attached .blend in 2.9.0 and 3.0.0 and hit render to see. I've set-up a compositor node setup to highlight and visualize the artificating found in 3.0.0. Try rendering with both Denoising methods to see variations in artifacts.\n\n**Other notes**\nI've played with as many render settings as possible and found that the denoiser is responsible. OptiX is worst, OpenImage is not as bad in artifacting.\n\n[alpha-transparency-denoising-issue-sample.blend](alpha-transparency-denoising-issue-sample.blend)\n\nNotice the clean colors in the greys (background composited in Compositor to help see issue)\n\n\nNotice the vertical and horizontal line noise\n\n\n[system-info.txt](system-info.txt)", "MetalRT: Rendering being unresponsive with AO node\nOperating system: Ventura 13.4.1\nGraphics card: Apple M1 Max 32 Core\n\nBroken: Blender 3.6 LTS\nWorked: Blender 3.5.1\n\nAfter downloading the newest Version of Blender it seems that using the Ambient Occlusion Node need leads to Blender being unresponsive. Sample count stays on 0 and neither Viewport nor F12 Render is starting as expected. Trying to quit, Blender crashes completely.\n\n- Add new material\n- Add Ambient Occlusion Node\n- Select cycles and GPU\n- Enable MetalRT\n- Start Viewport Rendering.\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", "weird unremovable noise which looks like white or semitransparent squares\nWindows GTX NVIDIA 860M Lenovo Y50 laptop 16GB RAM and 2GB VRAM\n\nBroken: (2.77, weird unremovable noise which looks like white or semitransparent squares)\n\n\n**I have horrible flickering noise during my animation and it flickers like a sparks. What causes this noice is alpha images with holes or models of the grids with holes + method of reducing it by using Z and normal passes combined with bilaterural blur (advised by Barteck Skorupa). But i still wanna use it since it still better and only way to properly reduce other types of noice presented in my scene. So this noice looks like SQUARE PIXELS which are flickering during animation. Change of iterations of bilatural blur helps a bit but not completely and not on all frames. \n\nI will give you more info now about this strange things -\n\n\n1- At most frames there is no such noise (because i removed it by using bilateral blur and determinator) but at other frames they are still appear and not despeckle not bilatural blur helps and the weird thing - THEY BECOME MORE VISIBLE AT HIGHER SAMPLES!!!!\n\n\n2 - At some frames this squares are transparent at others - semitransparent or completly white like you can see on the screenshot\n\n\n3 - If i render same image at small samples - like 125 for example - i may not see them at all. But if i change to 150 - they become very visible!!!. \n\n4 - They mostly appear around grids holes models or grids holes alpha images.\n\n\n5- Even if camera not moving they may still appear and look at different frames - differently (white or semitransparent )\n**\n\n\n\n\n\n\n\n\n\n**To reproduce the error you whould probably need to render scene when camera moves and looks directly on grids png images with holes or even models of grids with a holes and also try to use bilatural blur node with determinator + z pass and normal pass combined ro remove noise - since most of the issues appearing when you using this nodes combinations (but its necessarily to use them)**\n\n\nIf you will need a blend file please leave me a comment on [email protected]. Thanks\n", "Non animatable properties\nBroken: version: 3.3.0 Alpha\n\nWorking on refreshing the in-built AnimAll addon by adding the latest properties supported in Blender.\n@ideasman42 asked me to file a task\n\nCertain properties are missing animation capabilities:\n\n - Lattice Vertex Groups\n - Mesh Vertex Creases", "Improve Palette management in Paint Modes (Meshes and Grease Pencil)\nThis is not a task only related to Grease Pencil, but also to any Paint mode.\n\nAs part of the Vertex Paint development in Grease Pencil, we have detected some missing features in Palettes and we have decided to fix it, because Palettes look a little outdate and without improvements for several versions.\n\nMissing features/ WishList:\n\n* There is no default palette.\n* Swatches cannot be re-arranged\n* Colors cannot be sorted\n* Colors can't be named\n* Palettes cannot be merged\n* templatePalette control UI is outdated\n* No ability to import palettes from other software\n* No ability to export palettes to other software\n* Missing easy way to create palettes from images\n\nAbout default palette, in grease pencil we have implemented a default palette similar to Krita/GImp palette. This palette is required by GPencil, but it would be good idea to set this default palette in Texture Paint and Vertex Paint for meshes too.\n\n\nCurrently, I have solved the Sorting, Moving, Join and some Import modules in Grease Pencil branch, but the list above is the initial ideas.", "Cycles: Baking to an externally loaded image fails to update the image buffer results in Cycle's Rendered Viewport Shading\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.3.0, 2.93\nWorked: probably never\n\nBaking to an externally loaded image will not changed the baked image as displayed in the Viewport Shading's Rendered Mode.\nThe newly baked image buffer is shown correctly in the image editor and (EEVEE's) Material Preview, but wrong in Cycles's render view.\n\n- Open the attached .blend file.\n- Open the attached baked image in the image texture node.\n- Use it to bake any type of pass to the loaded image.\n- Observe that the image looks unchanged in the Rendered View by connecting the image texture node to the material output.\n[#98063.blend](T98063.blend)\n\n[2022-05-12 09-12-20.mp4](2022-05-12_09-12-20.mp4)", "World aov output nodes dont work unless background node's colour is >= 0.0001\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: Unknown\n\nWorld aov output nodes dont work unless background node's colour is >= 0.0001\n\n\n1. Open attached file\n2. go to the compositor of 'scene' and render still image\n3. the custom world aov is blank\n4. go to scene.001 and render\n5. the world aov now outputs correctly\n\nBoth scene's are identical, the only difference is scene.001's world background node's colour is set to 0.0001. The custom AOV is of type Value rather than colour. This is problematic because it breaks compositor setups that check for values > 0 etc.\n\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", "Geometry Nodes: Mismatching data types connections work differently from other node editors\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.5.0\n\nFloat math node overrides color data, even though it is muted. Same setup works in shader editor without problems.\n\nOpen file and activate *Viewer* in GN. Expected result: colored output (judging by shader area behavior)\n\n" ]

[ "Bake to vertex colors completely broken in 3.1 & 3.2\nOperating system: Win 10\nGraphics card: 980 Ti\n\nBroken: 3.1 beta & 3.2 alpha\nWorked: 3.0.1\n\nCaused by 74afc86d4b\n\nBaking to vertex colors (for example ambient occlusion) seems to be completely broken since 3.1 beta, as it is producing randomly looking artifacts, nowhere near to expected results.\nThe same scene & baking / rendering settings works better in 3.0.1 (with smaller bugs).\n\n\nWhen rendering to texture, the same setup works correctly even in 3.1 beta & 3.2 alpha.\n\nOpen the attached .blend file in 3.0.1 and 3.1 beta / 3.2 alpha, hit Bake and compare results.\n[bake-to-vcols_3.1-3.2_bug.blend](bake-to-vcols_3.1-3.2_bug.blend)\n\n" ]

[ "Define How to Deal With Different Preview Sizes and DPIs\nChoosing a size to generate a preview/thumbnail for is not trivial. Users may want to show thumbnails in different sizes (e.g. relatively small in the asset list, bigger in the sidebar). But also, the previews are stored with the assets in .blends - how to deal with different DPIs the asset previews may be shown in?\n\nE.g. a user creates an asset inside a .blend with a non-hiDPI screen and installs that .blend as asset repository on a hiDPI machine. Or the other way around: Create asset on hiDPI screen, install .blend as repository for a non-hiDPI setup.", "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", "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", "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", "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. -----------------------------------------------------------", "Asset Manager: Support preview thumbnails for more data-block types\n## Motivation\n\nFor the asset manager, good previews are important. They are needed to tell assets apart visually, names are more like the secondary way to select them. We need to think about how to capture different data-blocks in a good way, to get the best possible previews.\nWe need that for multiple data-block types.\n\n## Design\n\nWe should try to come up with simple solutions, that work in the majority of cases. Just because there are some cases where a simple solution doesn't work, doesn't mean we can't use it in the majority of cases where it would. So we could have a simple, one-click way to create an asset and one that allows setting further options for when it's needed.\n\nMaterials, objects, poses, textures, images, screen-layouts, worlds and lights already support previews. We could of course improve them.\n\n### Collections\n\nDesign needed. [TODO]\n\n### Brushes\n\n *From #56744, we'll probably use the same previews here.*\n\n### Simulations\n\nDesign needed.\n\n### Rigs\n\nDesign needed.\n\n### Movie Clips\n\nIdea: Display some frame, but allow \"scrubbing\" through frames with horizontal mouse movements over the preview.\n\n### Object Types\n\n* Curves (Viewport/OpenGL render?)\n* Empties\n* Cameras\n* Volumes\n* Force Fields\n* ...\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", "Brushes Assets Viewport User Interface\n{[F13331829](image.png), size=full}\n\nAdditional Notes:\n\n{[F13331831](image.png), size=full}", "Breaking UI API changes for 4.0\n- [ ] Remove grid display for UI lists - Never worked well and is badly maintained. May have been added for an oudated asset UI design even?\n- [ ] Remove asset-view UI template - Should be replaced by the [asset shelf](102879).\n- [ ] Replace/deprecate UI lists? - Probably too much work, would require UI views to be exposed to Python. But can at least be converted to use UI views internally and benefit from its features.\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", "Add size of IDs on disk to Outliner info\nIn complex files/production context, it can be very useful to be able to quickly see the size used by data-blocks, which ones are very heavy, etc.\n\nThis could be done e.g. by checking the last undo step, size is stored in memory chunks, so by doing a quick loop over all BHeads we should be able to get the size of each ID on disk? Or maybe even more efficient, storing that info in IDs after each undo step is written, generating it would then be almost for free.\n\nOutliner could then have a optional column to display that info.", "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", "ID Management: Sanitize and clarify our ID creation/copy tags\nSome of our ID creation/copying code and flags are currently still fuzzy and not really correct, especially when changes proposed in #88555 (ID Management: Sanitize and clarify our ID tags) become real. This concerns 'out of `G_MAIN`' IDs mostly.\n\nIMPORTANT: This task is a sister of #88555 (ID Management: Sanitize and clarify our ID tags), both will be worked on together.\n\n## `LIB_ID_CREATE_LOCALIZE`\nThis ID creation flag is only used in two places, and its name is extremely confusing since it actually sets `NO_MAIN` flag, not `LOCALIZED` one. It should simply be removed.\n\n## `LIB_ID_COPY_LOCALIZE`\nShould be updated to set `LOCALIZED` flag instead of `NO_MAIN` one: `LIB_ID_CREATE_LOCAL | LIB_ID_CREATE_NO_USER_REFCOUNT | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_NO_LIB_OVERRIDE`\n\nA new `LIB_ID_COPY_NO_MAIN` set of flags should be added with default behavior to create a `NO_MAIN` ID, probably `LIB_ID_CREATE_NO_MAIN | LIB_ID_CREATE_NO_DEG_TAG | LIB_ID_COPY_NO_PREVIEW | LIB_ID_COPY_CACHES | LIB_ID_COPY_NO_LIB_OVERRIDE` (would leave `NO_REF_COUNT` out of the default set of flags).\n\n## `ntreeLocalize`\nThis special function needs to be removed, this specific behavior should be strictly handled through calls to generic `BKE_id_copy_ex` and dedicated code in `ntree_copy_data` IDType callback.\n\nNot sure where the recursive copying of sub-trees should be handled though, either in `BKE_id_copy_ex` or `BKE_libblock_copy_ex`, in a similar way to how we deal with animation data currently, or from `ntree_copy_data`, as done e.g. for shapekeys for meshes and other obdata?\n*Would rather keep this 'localize' behavior in the `ntree_copy_data` i think, at least for now. We need a full rethink of how we handle recursive 'deep' copying of IDs anyway, current code is dodgy at best here, and often fully broken (ref. #72659 (Making 'singleuser' for a group with too smart NodeCustomGroup breaks user counters of both source and target nodes) and similar).*", "Placement Tool for Objects and/or Collections\n### Motivation\n\nThe new drag & drop snapping helps easily & quickly placing objects in the scene. But it relies quite a bit on the asset and the scene it’s being dragged into (e.g. the size relative to the destination scene, the exact normal of the snapped to surface), etc. Users may want to adjust the rotation, the scale, the up-axis, use the origin for snapping rather than the bound-box (e.g. to place trees so they are partially covered by the ground plane), etc.\n\n### Basic Design Idea\n\nRather than setting these options before dragging (where you don’t get visual feedback) or while dragging (where it’s awkward to give input because you’re holding a mouse button), the Operate->Settings paradigm of Blender should be used: First the object/collection is dragged in and placed using basic snapping, then we provide a visual way to keep adjusting the transforms and parameters until the user is happy with the result.\n\nHowever, this placement method isn't just useful for dragging in assets. It is useful as a general transform tool and should be created as such. So this is a proposal for a general placement tool with bounding-box or origin based surface snapping, that gives access to most important transforms and properties for placing an object. In some way or another, it could be (temporarily and optionally?) activated after dragging an object or collection asset into the scene. If more advanced transforms are needed, the user can still access the proper transform tools & operators.\n\n### Temporary Activation\n\nHaving to activate a placement tool every time an asset is dragged in can be annoying. Blender could automatically activate it, at least in some temporary fashion. For example, the tool could temporarily override the active tool after dragging in an asset. Deselecting the dragged in object would bring back the real active tool. If the user wishes to go back to the placement tool, that can be explicitly enabled again in the toolbar.\n\n### Tool Design\n\nTODO", "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)." ]

[ "Show \"Orphaned\" assets in \"Unassigned\" catalog\nIf there are assets with catalog IDs that are not recognized, the Asset Browser can show these in the *Unassigned* item in the catalog tree.\n\nOptionally (probably not a Blender 3.0 target) these could be grouped by the catalog's *simple name* as stored on the asset." ]

[ "Sculpt crash in certain scenario (PBVH vert number does not match)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.6\n\nCrash upon altering the model in any way.\n\n1. Open file\n2. Use a tool/brush to alter the model.\n3. Instant Crash\n\nI have updated GPU drivers and the latest Blender version as of today, still crashes.\n\nCould not find any duplicate bugs of crashes when interacting with models, only crash on startup and others. \n\nI expect my GPU is just too trash.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Goblin.crash.txt](Goblin.crash.txt)\n\n[Goblin.blend](Goblin.blend)\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 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", "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)", "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", "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)", "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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "segfault on f3 when mouse hover focus off foreground window\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.6.1\nAlready broken: 3.0\nWorked: 2.93.18\n\nThe application crashes upon using the Search Menu keyboard shortcut, under the condition that the mouse hover focus is not over the foreground window.\n\nUPDATE: must enable Developer Extras for crash to occur!\nNew file.\nMake the window not fullscreen so you can see some desktop.\nHover mouse over desktop.\nPress F3 key to open Search Menu.\nObserve notification of segmentation fault.\n\nAlternatively, open a preferences window or secondary blender window and mouse over the main window and press F3, that's how I found it.\n\nBefore 3.0 the same steps will cause the menu to appear in the foreground window as close as it can get itself to the mouse outside.\nUPDATE: checked Developer Extras and it was on, yet no crash prior to 3.0\n", "blender 4.0 shutdown immediately after launching\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\nblender 4.0 latest build shutdown immediately after launching . and i think its cant overwrite the file showing in the image .when i deleted that file and try to launch blender its work just fine . after doing some stuff blender got crashed 🙃 and the same thing happen again (can`t launch) and so i have to do the same method to get it to work again 🙂👌\n\n----\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", "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\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", "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", "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)" ]

[ "cmd+z crash\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.1.2\n\n\ncmd+z serveal times，it always crashed\n\n\n\napple report below\n\n```lines=18\n-------------------------------------\nTranslated Report (Full Report Below)\n-------------------------------------\n\nProcess: Blender [65686]\nPath: /Applications/Blender 3.1.2.app/Contents/MacOS/Blender\nIdentifier: org.blenderfoundation.blender\nVersion: 3.1.2 (3.1.2 2022-04-01)\nCode Type: X86-64 (Native)\nParent Process: launchd [1]\nUser ID: 501\n\nDate/Time: 2022-05-10 11:10:46.5481 +0800\nOS Version: macOS 12.3 (21E230)\nReport Version: 12\nAnonymous UUID: 35B468B4-3456-9C66-AF92-6373F96C1165\n\n\nTime Awake Since Boot: 150000 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: UNKNOWN_0xD at 0x0000000000000000\nException Codes: 0x000000000000000d, 0x0000000000000000\nException Note: EXC_CORPSE_NOTIFY\n\nTermination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11\nTerminating Process: exc handler [65686]\n\nVM Region Info: 0 is not in any region. Bytes before following region: 4405927936\n REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL\n UNUSED SPACE AT START\n---> \n __TEXT 1069d2000-11331e000 [201.3M] r-x/r-x SM=COW ...MacOS/Blender\n\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x107c0dd98 ui_but_equals_old + 8\n1 Blender \t 0x107c0e931 UI_block_update_from_old + 1089\n2 Blender \t 0x107c0eb38 UI_block_end_ex + 152\n3 Blender \t 0x107d766d6 draw_outliner + 2774\n4 Blender \t 0x107d89e40 outliner_main_region_draw(bContext const*, ARegion*) + 32\n5 Blender \t 0x1076745b1 ED_region_do_draw + 337\n6 Blender \t 0x1070f82ed wm_draw_update + 1757\n7 Blender \t 0x1070f5810 WM_main + 48\n8 Blender \t 0x106b50f89 main + 873\n9 dyld \t 0x12990651e start + 462\n\nThread 1:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff81f43b7ce _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff81f43bc9d _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x10eeccc1f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x10eecb6ae 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 2:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff81f43b7ce _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff81f43bc9d _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x10eeccc1f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x10eecb6ae 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 3:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff81f43b7ce _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff81f43bc9d _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x10eeccc1f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x10eecb6ae 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 4:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff81f43b7ce _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff81f43bc9d _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x10eeccc1f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x10eecb6ae 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 5:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 libdispatch.dylib \t 0x7ff81f43b7ce _dispatch_sema4_wait + 16\n2 libdispatch.dylib \t 0x7ff81f43bc9d _dispatch_semaphore_wait_slow + 98\n3 Blender \t 0x10eeccc1f IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run() + 79\n4 Blender \t 0x10eecb6ae 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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*) + 62\n5 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n6 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 6:: AMCP Logging Spool\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 caulk \t 0x7ff8280cc2e0 caulk::mach::semaphore::wait_or_error() + 16\n2 caulk \t 0x7ff8280b4102 caulk::concurrent::details::worker_thread::run() + 36\n3 caulk \t 0x7ff8280b3dc6 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*) + 41\n4 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n5 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 7:: com.apple.audio.IOThread.client\n0 libsystem_kernel.dylib \t 0x7ff81f5b997a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81f5b9ce8 mach_msg + 56\n2 CoreAudio \t 0x7ff82122cd71 HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int) + 111\n3 CoreAudio \t 0x7ff8210b7e63 HALC_ProxyIOContext::IOWorkLoop() + 3909\n4 CoreAudio \t 0x7ff8210b6959 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 63\n5 CoreAudio \t 0x7ff8212827a8 HALB_IOThread::Entry(void*) + 72\n6 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 8:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 9:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 10:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 11:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 12:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 13:\n0 libsystem_kernel.dylib \t 0x7ff81f5c0092 __accept + 10\n1 _socket.cpython-310-darwin.so \t 0x12f763388 sock_accept_impl + 24\n2 _socket.cpython-310-darwin.so \t 0x12f7637e2 sock_call_ex + 402\n3 _socket.cpython-310-darwin.so \t 0x12f761080 sock_accept + 144\n4 Blender \t 0x10f58f857 method_vectorcall_NOARGS + 135\n5 Blender \t 0x10f67abef call_function + 431\n6 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n7 Blender \t 0x10f670311 _PyEval_Vector + 145\n8 Blender \t 0x10f67abef call_function + 431\n9 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n10 Blender \t 0x10f670311 _PyEval_Vector + 145\n11 Blender \t 0x10f67abef call_function + 431\n12 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n13 Blender \t 0x10f670311 _PyEval_Vector + 145\n14 Blender \t 0x10f67abef call_function + 431\n15 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n16 Blender \t 0x10f670311 _PyEval_Vector + 145\n17 Blender \t 0x10f5886cf method_vectorcall + 367\n18 Blender \t 0x10f7243b6 thread_run + 70\n19 Blender \t 0x10f6d4839 pythread_wrapper + 25\n20 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n21 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 14:\n0 libsystem_kernel.dylib \t 0x7ff81f5c1d5a __select + 10\n1 Blender \t 0x10f72291c time_sleep + 140\n2 Blender \t 0x10f5cc495 cfunction_vectorcall_O + 277\n3 Blender \t 0x10f67abef call_function + 431\n4 Blender \t 0x10f677b8a _PyEval_EvalFrameDefault + 30538\n5 Blender \t 0x10f670311 _PyEval_Vector + 145\n6 Blender \t 0x10f67abef call_function + 431\n7 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n8 Blender \t 0x10f670311 _PyEval_Vector + 145\n9 Blender \t 0x10f67abef call_function + 431\n10 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n11 Blender \t 0x10f670311 _PyEval_Vector + 145\n12 Blender \t 0x10f5886cf method_vectorcall + 367\n13 Blender \t 0x10f7243b6 thread_run + 70\n14 Blender \t 0x10f6d4839 pythread_wrapper + 25\n15 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n16 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 15:\n0 libsystem_kernel.dylib \t 0x7ff81f5c00aa poll + 10\n1 select.cpython-310-darwin.so \t 0x121bbdd63 select_poll_poll + 291\n2 Blender \t 0x10f58f66c method_vectorcall_FASTCALL + 140\n3 Blender \t 0x10f67abef call_function + 431\n4 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n5 Blender \t 0x10f670311 _PyEval_Vector + 145\n6 Blender \t 0x10f67abef call_function + 431\n7 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n8 Blender \t 0x10f670311 _PyEval_Vector + 145\n9 Blender \t 0x10f67abef call_function + 431\n10 Blender \t 0x10f677c2c _PyEval_EvalFrameDefault + 30700\n11 Blender \t 0x10f670311 _PyEval_Vector + 145\n12 Blender \t 0x10f67abef call_function + 431\n13 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n14 Blender \t 0x10f670311 _PyEval_Vector + 145\n15 Blender \t 0x10f58862c method_vectorcall + 204\n16 Blender \t 0x10f67abef call_function + 431\n17 Blender \t 0x10f677cd3 _PyEval_EvalFrameDefault + 30867\n18 Blender \t 0x10f670311 _PyEval_Vector + 145\n19 Blender \t 0x10f67abef call_function + 431\n20 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n21 Blender \t 0x10f670311 _PyEval_Vector + 145\n22 Blender \t 0x10f67abef call_function + 431\n23 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n24 Blender \t 0x10f670311 _PyEval_Vector + 145\n25 Blender \t 0x10f5886cf method_vectorcall + 367\n26 Blender \t 0x10f7243b6 thread_run + 70\n27 Blender \t 0x10f6d4839 pythread_wrapper + 25\n28 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n29 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 16:: com.apple.NSEventThread\n0 libsystem_kernel.dylib \t 0x7ff81f5b997a mach_msg_trap + 10\n1 libsystem_kernel.dylib \t 0x7ff81f5b9ce8 mach_msg + 56\n2 CoreFoundation \t 0x7ff81f6bccdd __CFRunLoopServiceMachPort + 319\n3 CoreFoundation \t 0x7ff81f6bb368 __CFRunLoopRun + 1276\n4 CoreFoundation \t 0x7ff81f6ba7ac CFRunLoopRunSpecific + 562\n5 AppKit \t 0x7ff82224efee _NSEventThread + 132\n6 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n7 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 17:\n0 libsystem_kernel.dylib \t 0x7ff81f5c1d5a __select + 10\n1 Blender \t 0x10f72291c time_sleep + 140\n2 Blender \t 0x10f5cc495 cfunction_vectorcall_O + 277\n3 Blender \t 0x10f67abef call_function + 431\n4 Blender \t 0x10f677b8a _PyEval_EvalFrameDefault + 30538\n5 Blender \t 0x10f670311 _PyEval_Vector + 145\n6 Blender \t 0x10f67abef call_function + 431\n7 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n8 Blender \t 0x10f670311 _PyEval_Vector + 145\n9 Blender \t 0x10f67abef call_function + 431\n10 Blender \t 0x10f677b65 _PyEval_EvalFrameDefault + 30501\n11 Blender \t 0x10f670311 _PyEval_Vector + 145\n12 Blender \t 0x10f5886cf method_vectorcall + 367\n13 Blender \t 0x10f7243b6 thread_run + 70\n14 Blender \t 0x10f6d4839 pythread_wrapper + 25\n15 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n16 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 18:\n0 libsystem_pthread.dylib \t 0x7ff81f5f1f48 start_wqthread + 0\n\nThread 19:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 20:\n0 libsystem_kernel.dylib \t 0x7ff81f5b99b6 semaphore_wait_trap + 10\n1 Blender \t 0x1070ec0e8 tbb::internal::rml::private_worker::run() + 344\n2 Blender \t 0x1070ebf89 tbb::internal::rml::private_worker::thread_routine(void*) + 9\n3 libsystem_pthread.dylib \t 0x7ff81f5f64e1 _pthread_start + 125\n4 libsystem_pthread.dylib \t 0x7ff81f5f1f6b thread_start + 15\n\nThread 21:\n0 libsystem_pthread.dylib \t 0x7ff81f5f1f48 start_wqthread + 0\n\nThread 22:\n0 libsystem_pthread.dylib \t 0x7ff81f5f1f48 start_wqthread + 0\n\nThread 23:\n0 libsystem_pthread.dylib \t 0x7ff81f5f1f48 start_wqthread + 0\n\n\nThread 0 crashed with X86 Thread State (64-bit):\n rax: 0x0000000000000000 rbx: 0xff2c2c2cff2c2c2c rcx: 0x0000000000000000 rdx: 0x00000000006a6200\n rdi: 0x00007f8b4350ce08 rsi: 0xff2c2c2cff2c2c2c rbp: 0x00007ff7b952d520 rsp: 0x00007ff7b952d520\n r8: 0x0000000000000000 r9: 0x0000000000002800 r10: 0x0000000000008014 r11: 0x0000000000003fff\n r12: 0x00007f8b424e4088 r13: 0x00007f8b4350ce08 r14: 0x00006000003a4148 r15: 0x00007f8b4517c118\n rip: 0x0000000107c0dd98 rfl: 0x0000000000010282 cr2: 0x0000000129990383\n \nLogical CPU: 0\nError Code: 0x00000000 \nTrap Number: 13\n\nThread 0 instruction stream:\n c3 0f 1f 80 00 00 00 00-55 48 89 e5 41 56 53 48 ........UH..AVSH\n 8b 5f 10 48 85 db 74 27-49 89 f6 66 2e 0f 1f 84 ._.H..t'I..f....\n 00 00 00 00 00 0f 1f 00-4c 89 f7 48 89 de e8 25 ........L..H...%\n 00 00 00 84 c0 75 0a 48-8b 1b 48 85 db 75 e9 31 .....u.H..H..u.1\n db 48 89 d8 5b 41 5e 5d-c3 66 2e 0f 1f 84 00 00 .H..[A^].f......\n 00 00 00 0f 1f 44 00 00-55 48 89 e5 0f b7 47 2c .....D..UH....G,\n [66]3b 46 2c 75 4e 48 8b-87 58 03 00 00 48 3b 86 f;F,uNH..X...H;.\t<==\n 58 03 00 00 75 3e 48 8b-87 60 03 00 00 48 3b 86 X...u>H..`...H;.\n 60 03 00 00 75 2e 8b 86-68 03 00 00 39 87 68 03 `...u...h...9.h.\n 00 00 75 20 48 8b 87 90-02 00 00 48 3b 86 90 02 ..u H......H;...\n 00 00 75 10 48 8b 87 a8-02 00 00 48 3b 86 a8 02 ..u.H......H;...\n 00 00 74 04 31 c0 5d c3-48 8b 8e 98 02 00 00 48 ..t.1.].H......H\n\nBinary Images:\n 0x1069d2000 - 0x11331dfff org.blenderfoundation.blender (3.1.2) <886d906a-93f0-3952-a46f-144e5205f719> /Applications/Blender 3.1.2.app/Contents/MacOS/Blender\n 0x129901000 - 0x12996cfff dyld (*) <dd9e80de-fb3b-349b-96a4-46874ad34d11> /usr/lib/dyld\n 0x7ff81f5b8000 - 0x7ff81f5effff libsystem_kernel.dylib (*) <26a59789-b846-3ed4-96dc-8dbef3c0c8e7> /usr/lib/system/libsystem_kernel.dylib\n 0x7ff81f438000 - 0x7ff81f47efff libdispatch.dylib (*) <31d69d55-9895-326c-ad61-621c5ca87314> /usr/lib/system/libdispatch.dylib\n 0x7ff81f5f0000 - 0x7ff81f5fbfff libsystem_pthread.dylib (*) <2f6c275d-7e14-3d31-a924-e1bb41d2415f> /usr/lib/system/libsystem_pthread.dylib\n 0x7ff8280b2000 - 0x7ff8280d3fff com.apple.audio.caulk (1.0) <0b849791-3a62-33d1-8cf1-9c612a9d8e18> /System/Library/PrivateFrameworks/caulk.framework/Versions/A/caulk\n 0x7ff820efe000 - 0x7ff821631fff com.apple.audio.CoreAudio (5.0) <e432684f-546f-3931-af3e-a0281c23a244> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio\n 0x12f75f000 - 0x12f76cfff _socket.cpython-310-darwin.so (*) <099583aa-a77b-35dd-b414-f30dbc3a62c2> /Applications/Blender 3.1.2.app/Contents/Resources/3.1/python/lib/python3.10/lib-dynload/_socket.cpython-310-darwin.so\n 0x121bbc000 - 0x121bc0fff select.cpython-310-darwin.so (*) <16f40aa0-5cbc-3ea0-92f2-cca27bea0643> /Applications/Blender 3.1.2.app/Contents/Resources/3.1/python/lib/python3.10/lib-dynload/select.cpython-310-darwin.so\n 0x7ff81f63d000 - 0x7ff81fb3efff com.apple.CoreFoundation (6.9) <743f0cb7-e962-3e42-8653-7bd141129561> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation\n 0x7ff8220a3000 - 0x7ff822f30fff com.apple.AppKit (6.9) <36ec7e1b-ab12-377b-b3eb-ffc5baabee9f> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit\n\nExternal Modification Summary:\n Calls made by other processes targeting this process:\n task_for_pid: 0\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: 23\n thread_create: 0\n thread_set_state: 0\n\nVM Region Summary:\nReadOnly portion of Libraries: Total=1.5G resident=0K(0%) swapped_out_or_unallocated=1.5G(100%)\nWritable regions: Total=1.7G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.7G(100%)\n\n VIRTUAL REGION \nREGION TYPE SIZE COUNT (non-coalesced) \n=========== ======= ======= \nAccelerate framework 128K 1 \nActivity Tracing 256K 1 \nCG backing stores 3840K 4 \nCG image 96K 8 \nColorSync 100K 9 \nCoreAnimation 124K 7 \nCoreGraphics 12K 2 \nCoreImage 4K 1 \nCoreUI image data 1036K 7 \nFoundation 16K 1 \nKernel Alloc Once 8K 1 \nMALLOC 1.0G 593 \nMALLOC guard page 32K 8 \nMALLOC_LARGE (reserved) 256K 2 reserved VM address space (unallocated)\nMALLOC_NANO (reserved) 256.0M 1 reserved VM address space (unallocated)\nOpenGL GLSL 256K 3 \nSTACK GUARD 96K 24 \nStack 99.7M 26 \nStack Guard 4K 1 \nVM_ALLOCATE 186.9M 329 \nVM_ALLOCATE (reserved) 96.0M 2 reserved VM address space (unallocated)\n__DATA 110.4M 572 \n__DATA_CONST 29.2M 324 \n__DATA_DIRTY 1542K 195 \n__FONT_DATA 4K 1 \n__GLSLBUILTINS 5176K 1 \n__LINKEDIT 719.8M 77 \n__OBJC_RO 82.6M 1 \n__OBJC_RW 3200K 2 \n__TEXT 776.4M 573 \n__UNICODE 592K 1 \ndyld private memory 1152K 3 \nmapped file 172.9M 28 \nshared memory 1284K 17 \n=========== ======= ======= \nTOTAL 3.5G 2826 \nTOTAL, minus reserved VM space 3.2G 2826 \n\n\n\n-----------\nFull Report\n-----------\n\n{\"app_name\":\"Blender\",\"timestamp\":\"2022-05-10 11:10:47.00 +0800\",\"app_version\":\"3.1.2\",\"slice_uuid\":\"886d906a-93f0-3952-a46f-144e5205f719\",\"build_version\":\"3.1.2 2022-04-01\",\"platform\":1,\"bundleID\":\"org.blenderfoundation.blender\",\"share_with_app_devs\":0,\"is_first_party\":0,\"bug_type\":\"309\",\"os_version\":\"macOS 12.3 (21E230)\",\"incident_id\":\"7A2BCA27-CB0A-4A92-9289-BB4B4B1706AF\",\"name\":\"Blender\"}\n{\n \"uptime\" : 150000,\n \"procLaunch\" : \"2022-05-10 10:18:01.5772 +0800\",\n \"procRole\" : \"Foreground\",\n \"version\" : 2,\n \"userID\" : 501,\n \"deployVersion\" : 210,\n \"modelCode\" : \"iMac19,1\",\n \"procStartAbsTime\" : 149882388505649,\n \"coalitionID\" : 175391,\n \"osVersion\" : {\n \"train\" : \"macOS 12.3\",\n \"build\" : \"21E230\",\n \"releaseType\" : \"User\"\n },\n \"captureTime\" : \"2022-05-10 11:10:46.5481 +0800\",\n \"incident\" : \"7A2BCA27-CB0A-4A92-9289-BB4B4B1706AF\",\n \"bug_type\" : \"309\",\n \"pid\" : 65686,\n \"procExitAbsTime\" : 153047215997583,\n \"cpuType\" : \"X86-64\",\n \"procName\" : \"Blender\",\n \"procPath\" : \"\\/Applications\\/Blender 3.1.2.app\\/Contents\\/MacOS\\/Blender\",\n \"bundleInfo\" : {\"CFBundleShortVersionString\":\"3.1.2\",\"CFBundleVersion\":\"3.1.2 2022-04-01\",\"CFBundleIdentifier\":\"org.blenderfoundation.blender\"},\n \"storeInfo\" : {\"deviceIdentifierForVendor\":\"B46F7F0D-AA84-5DB1-84CE-820DB151F71E\",\"thirdParty\":true},\n \"parentProc\" : \"launchd\",\n \"parentPid\" : 1,\n \"coalitionName\" : \"org.blenderfoundation.blender\",\n \"crashReporterKey\" : \"35B468B4-3456-9C66-AF92-6373F96C1165\",\n \"sip\" : \"enabled\",\n \"vmRegionInfo\" : \"0 is not in any region. Bytes before following region: 4405927936\\n REGION TYPE START - END [ VSIZE] PRT\\/MAX SHRMOD REGION DETAIL\\n UNUSED SPACE AT START\\n---> \\n __TEXT 1069d2000-11331e000 [201.3M] r-x\\/r-x SM=COW ...MacOS\\/Blender\",\n \"isCorpse\" : 1,\n \"exception\" : {\"codes\":\"0x000000000000000d, 0x0000000000000000\",\"rawCodes\":[13,0],\"type\":\"EXC_BAD_ACCESS\",\"signal\":\"SIGSEGV\",\"subtype\":\"UNKNOWN_0xD at 0x0000000000000000\"},\n \"termination\" : {\"flags\":0,\"code\":11,\"namespace\":\"SIGNAL\",\"indicator\":\"Segmentation fault: 11\",\"byProc\":\"exc handler\",\"byPid\":65686},\n \"vmregioninfo\" : \"0 is not in any region. Bytes before following region: 4405927936\\n REGION TYPE START - END [ VSIZE] PRT\\/MAX SHRMOD REGION DETAIL\\n UNUSED SPACE AT START\\n---> \\n __TEXT 1069d2000-11331e000 [201.3M] r-x\\/r-x SM=COW ...MacOS\\/Blender\",\n \"extMods\" : {\"caller\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"system\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":23},\"targeted\":{\"thread_create\":0,\"thread_set_state\":0,\"task_for_pid\":0},\"warnings\":0},\n \"faultingThread\" : 0,\n \"threads\" : [{\"triggered\":true,\"id\":2088165,\"instructionState\":{\"instructionStream\":{\"bytes\":[195,15,31,128,0,0,0,0,85,72,137,229,65,86,83,72,139,95,16,72,133,219,116,39,73,137,246,102,46,15,31,132,0,0,0,0,0,15,31,0,76,137,247,72,137,222,232,37,0,0,0,132,192,117,10,72,139,27,72,133,219,117,233,49,219,72,137,216,91,65,94,93,195,102,46,15,31,132,0,0,0,0,0,15,31,68,0,0,85,72,137,229,15,183,71,44,102,59,70,44,117,78,72,139,135,88,3,0,0,72,59,134,88,3,0,0,117,62,72,139,135,96,3,0,0,72,59,134,96,3,0,0,117,46,139,134,104,3,0,0,57,135,104,3,0,0,117,32,72,139,135,144,2,0,0,72,59,134,144,2,0,0,117,16,72,139,135,168,2,0,0,72,59,134,168,2,0,0,116,4,49,192,93,195,72,139,142,152,2,0,0,72],\"offset\":96}},\"threadState\":{\"r13\":{\"value\":140236106550792},\"rax\":{\"value\":0},\"rflags\":{\"value\":66178},\"cpu\":{\"value\":0},\"r14\":{\"value\":105553120084296},\"rsi\":{\"value\":18387119950418160684},\"r8\":{\"value\":0},\"cr2\":{\"value\":4992861059},\"rdx\":{\"value\":6971904},\"r10\":{\"value\":32788},\"r9\":{\"value\":10240},\"r15\":{\"value\":140236136366360},\"rbx\":{\"value\":18387119950418160684},\"trap\":{\"value\":13},\"err\":{\"value\":0},\"r11\":{\"value\":16383},\"rip\":{\"value\":4425047448,\"matchesCrashFrame\":1},\"rbp\":{\"value\":140701942863136},\"rsp\":{\"value\":140701942863136},\"r12\":{\"value\":140236089606280},\"rcx\":{\"value\":0},\"flavor\":\"x86_THREAD_STATE\",\"rdi\":{\"value\":140236106550792}},\"queue\":\"com.apple.main-thread\",\"frames\":[{\"imageOffset\":19119512,\"symbol\":\"ui_but_equals_old\",\"symbolLocation\":8,\"imageIndex\":0},{\"imageOffset\":19122481,\"symbol\":\"UI_block_update_from_old\",\"symbolLocation\":1089,\"imageIndex\":0},{\"imageOffset\":19123000,\"symbol\":\"UI_block_end_ex\",\"symbolLocation\":152,\"imageIndex\":0},{\"imageOffset\":20596438,\"symbol\":\"draw_outliner\",\"symbolLocation\":2774,\"imageIndex\":0},{\"imageOffset\":20676160,\"symbol\":\"outliner_main_region_draw(bContext const*, ARegion*)\",\"symbolLocation\":32,\"imageIndex\":0},{\"imageOffset\":13247921,\"symbol\":\"ED_region_do_draw\",\"symbolLocation\":337,\"imageIndex\":0},{\"imageOffset\":7496429,\"symbol\":\"wm_draw_update\",\"symbolLocation\":1757,\"imageIndex\":0},{\"imageOffset\":7485456,\"symbol\":\"WM_main\",\"symbolLocation\":48,\"imageIndex\":0},{\"imageOffset\":1568649,\"symbol\":\"main\",\"symbolLocation\":873,\"imageIndex\":0},{\"imageOffset\":21790,\"symbol\":\"start\",\"symbolLocation\":462,\"imageIndex\":1}]},{\"id\":2088179,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":14286,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":15517,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":139439135,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":139433646,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088180,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":14286,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":15517,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":139439135,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":139433646,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088181,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":14286,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":15517,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":139439135,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":139433646,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088182,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":14286,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":15517,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":139439135,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":139433646,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088183,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":14286,\"symbol\":\"_dispatch_sema4_wait\",\"symbolLocation\":16,\"imageIndex\":3},{\"imageOffset\":15517,\"symbol\":\"_dispatch_semaphore_wait_slow\",\"symbolLocation\":98,\"imageIndex\":3},{\"imageOffset\":139439135,\"symbol\":\"IlmThread_2_5::(anonymous namespace)::DefaultWorkerThread::run()\",\"symbolLocation\":79,\"imageIndex\":0},{\"imageOffset\":139433646,\"symbol\":\"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_5::Thread::*)(), IlmThread_2_5::Thread*> >(void*)\",\"symbolLocation\":62,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088186,\"name\":\"AMCP Logging Spool\",\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":107232,\"symbol\":\"caulk::mach::semaphore::wait_or_error()\",\"symbolLocation\":16,\"imageIndex\":5},{\"imageOffset\":8450,\"symbol\":\"caulk::concurrent::details::worker_thread::run()\",\"symbolLocation\":36,\"imageIndex\":5},{\"imageOffset\":7622,\"symbol\":\"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*)\",\"symbolLocation\":41,\"imageIndex\":5},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088190,\"name\":\"com.apple.audio.IOThread.client\",\"frames\":[{\"imageOffset\":6522,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7400,\"symbol\":\"mach_msg\",\"symbolLocation\":56,\"imageIndex\":2},{\"imageOffset\":3337585,\"symbol\":\"HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, bool, unsigned int)\",\"symbolLocation\":111,\"imageIndex\":6},{\"imageOffset\":1810019,\"symbol\":\"HALC_ProxyIOContext::IOWorkLoop()\",\"symbolLocation\":3909,\"imageIndex\":6},{\"imageOffset\":1804633,\"symbol\":\"invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int)\",\"symbolLocation\":63,\"imageIndex\":6},{\"imageOffset\":3688360,\"symbol\":\"HALB_IOThread::Entry(void*)\",\"symbolLocation\":72,\"imageIndex\":6},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088250,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088251,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088252,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088253,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088254,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088256,\"frames\":[{\"imageOffset\":32914,\"symbol\":\"__accept\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":17288,\"symbol\":\"sock_accept_impl\",\"symbolLocation\":24,\"imageIndex\":7},{\"imageOffset\":18402,\"symbol\":\"sock_call_ex\",\"symbolLocation\":402,\"imageIndex\":7},{\"imageOffset\":8320,\"symbol\":\"sock_accept\",\"symbolLocation\":144,\"imageIndex\":7},{\"imageOffset\":146528343,\"symbol\":\"method_vectorcall_NOARGS\",\"symbolLocation\":135,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":146499279,\"symbol\":\"method_vectorcall\",\"symbolLocation\":367,\"imageIndex\":0},{\"imageOffset\":148186038,\"symbol\":\"thread_run\",\"symbolLocation\":70,\"imageIndex\":0},{\"imageOffset\":147859513,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":25,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088257,\"frames\":[{\"imageOffset\":40282,\"symbol\":\"__select\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":148179228,\"symbol\":\"time_sleep\",\"symbolLocation\":140,\"imageIndex\":0},{\"imageOffset\":146777237,\"symbol\":\"cfunction_vectorcall_O\",\"symbolLocation\":277,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479434,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30538,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":146499279,\"symbol\":\"method_vectorcall\",\"symbolLocation\":367,\"imageIndex\":0},{\"imageOffset\":148186038,\"symbol\":\"thread_run\",\"symbolLocation\":70,\"imageIndex\":0},{\"imageOffset\":147859513,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":25,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088265,\"frames\":[{\"imageOffset\":32938,\"symbol\":\"poll\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7523,\"symbol\":\"select_poll_poll\",\"symbolLocation\":291,\"imageIndex\":8},{\"imageOffset\":146527852,\"symbol\":\"method_vectorcall_FASTCALL\",\"symbolLocation\":140,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479596,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30700,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":146499116,\"symbol\":\"method_vectorcall\",\"symbolLocation\":204,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479763,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30867,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":146499279,\"symbol\":\"method_vectorcall\",\"symbolLocation\":367,\"imageIndex\":0},{\"imageOffset\":148186038,\"symbol\":\"thread_run\",\"symbolLocation\":70,\"imageIndex\":0},{\"imageOffset\":147859513,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":25,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088294,\"name\":\"com.apple.NSEventThread\",\"frames\":[{\"imageOffset\":6522,\"symbol\":\"mach_msg_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7400,\"symbol\":\"mach_msg\",\"symbolLocation\":56,\"imageIndex\":2},{\"imageOffset\":523485,\"symbol\":\"__CFRunLoopServiceMachPort\",\"symbolLocation\":319,\"imageIndex\":9},{\"imageOffset\":516968,\"symbol\":\"__CFRunLoopRun\",\"symbolLocation\":1276,\"imageIndex\":9},{\"imageOffset\":513964,\"symbol\":\"CFRunLoopRunSpecific\",\"symbolLocation\":562,\"imageIndex\":9},{\"imageOffset\":1753070,\"symbol\":\"_NSEventThread\",\"symbolLocation\":132,\"imageIndex\":10},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2088416,\"frames\":[{\"imageOffset\":40282,\"symbol\":\"__select\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":148179228,\"symbol\":\"time_sleep\",\"symbolLocation\":140,\"imageIndex\":0},{\"imageOffset\":146777237,\"symbol\":\"cfunction_vectorcall_O\",\"symbolLocation\":277,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479434,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30538,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":147491823,\"symbol\":\"call_function\",\"symbolLocation\":431,\"imageIndex\":0},{\"imageOffset\":147479397,\"symbol\":\"_PyEval_EvalFrameDefault\",\"symbolLocation\":30501,\"imageIndex\":0},{\"imageOffset\":147448593,\"symbol\":\"_PyEval_Vector\",\"symbolLocation\":145,\"imageIndex\":0},{\"imageOffset\":146499279,\"symbol\":\"method_vectorcall\",\"symbolLocation\":367,\"imageIndex\":0},{\"imageOffset\":148186038,\"symbol\":\"thread_run\",\"symbolLocation\":70,\"imageIndex\":0},{\"imageOffset\":147859513,\"symbol\":\"pythread_wrapper\",\"symbolLocation\":25,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2126869,\"frames\":[{\"imageOffset\":8008,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":2126949,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2126950,\"frames\":[{\"imageOffset\":6582,\"symbol\":\"semaphore_wait_trap\",\"symbolLocation\":10,\"imageIndex\":2},{\"imageOffset\":7446760,\"symbol\":\"tbb::internal::rml::private_worker::run()\",\"symbolLocation\":344,\"imageIndex\":0},{\"imageOffset\":7446409,\"symbol\":\"tbb::internal::rml::private_worker::thread_routine(void*)\",\"symbolLocation\":9,\"imageIndex\":0},{\"imageOffset\":25825,\"symbol\":\"_pthread_start\",\"symbolLocation\":125,\"imageIndex\":4},{\"imageOffset\":8043,\"symbol\":\"thread_start\",\"symbolLocation\":15,\"imageIndex\":4}]},{\"id\":2127636,\"frames\":[{\"imageOffset\":8008,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":2127637,\"frames\":[{\"imageOffset\":8008,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]},{\"id\":2127646,\"frames\":[{\"imageOffset\":8008,\"symbol\":\"start_wqthread\",\"symbolLocation\":0,\"imageIndex\":4}]}],\n \"usedImages\" : [\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4405927936,\n \"CFBundleShortVersionString\" : \"3.1.2\",\n \"CFBundleIdentifier\" : \"org.blenderfoundation.blender\",\n \"size\" : 211075072,\n \"uuid\" : \"886d906a-93f0-3952-a46f-144e5205f719\",\n \"path\" : \"\\/Applications\\/Blender 3.1.2.app\\/Contents\\/MacOS\\/Blender\",\n \"name\" : \"Blender\",\n \"CFBundleVersion\" : \"3.1.2 2022-04-01\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4992274432,\n \"size\" : 442368,\n \"uuid\" : \"dd9e80de-fb3b-349b-96a4-46874ad34d11\",\n \"path\" : \"\\/usr\\/lib\\/dyld\",\n \"name\" : \"dyld\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703654707200,\n \"size\" : 229376,\n \"uuid\" : \"26a59789-b846-3ed4-96dc-8dbef3c0c8e7\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_kernel.dylib\",\n \"name\" : \"libsystem_kernel.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703653134336,\n \"size\" : 290816,\n \"uuid\" : \"31d69d55-9895-326c-ad61-621c5ca87314\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libdispatch.dylib\",\n \"name\" : \"libdispatch.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703654936576,\n \"size\" : 49152,\n \"uuid\" : \"2f6c275d-7e14-3d31-a924-e1bb41d2415f\",\n \"path\" : \"\\/usr\\/lib\\/system\\/libsystem_pthread.dylib\",\n \"name\" : \"libsystem_pthread.dylib\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703800434688,\n \"CFBundleShortVersionString\" : \"1.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.caulk\",\n \"size\" : 139264,\n \"uuid\" : \"0b849791-3a62-33d1-8cf1-9c612a9d8e18\",\n \"path\" : \"\\/System\\/Library\\/PrivateFrameworks\\/caulk.framework\\/Versions\\/A\\/caulk\",\n \"name\" : \"caulk\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703681208320,\n \"CFBundleShortVersionString\" : \"5.0\",\n \"CFBundleIdentifier\" : \"com.apple.audio.CoreAudio\",\n \"size\" : 7553024,\n \"uuid\" : \"e432684f-546f-3931-af3e-a0281c23a244\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreAudio.framework\\/Versions\\/A\\/CoreAudio\",\n \"name\" : \"CoreAudio\",\n \"CFBundleVersion\" : \"5.0\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 5091225600,\n \"size\" : 57344,\n \"uuid\" : \"099583aa-a77b-35dd-b414-f30dbc3a62c2\",\n \"path\" : \"\\/Applications\\/Blender 3.1.2.app\\/Contents\\/Resources\\/3.1\\/python\\/lib\\/python3.10\\/lib-dynload\\/_socket.cpython-310-darwin.so\",\n \"name\" : \"_socket.cpython-310-darwin.so\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 4860919808,\n \"size\" : 20480,\n \"uuid\" : \"16f40aa0-5cbc-3ea0-92f2-cca27bea0643\",\n \"path\" : \"\\/Applications\\/Blender 3.1.2.app\\/Contents\\/Resources\\/3.1\\/python\\/lib\\/python3.10\\/lib-dynload\\/select.cpython-310-darwin.so\",\n \"name\" : \"select.cpython-310-darwin.so\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64h\",\n \"base\" : 140703655251968,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.CoreFoundation\",\n \"size\" : 5251072,\n \"uuid\" : \"743f0cb7-e962-3e42-8653-7bd141129561\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/CoreFoundation.framework\\/Versions\\/A\\/CoreFoundation\",\n \"name\" : \"CoreFoundation\",\n \"CFBundleVersion\" : \"1858.112\"\n },\n {\n \"source\" : \"P\",\n \"arch\" : \"x86_64\",\n \"base\" : 140703699709952,\n \"CFBundleShortVersionString\" : \"6.9\",\n \"CFBundleIdentifier\" : \"com.apple.AppKit\",\n \"size\" : 15261696,\n \"uuid\" : \"36ec7e1b-ab12-377b-b3eb-ffc5baabee9f\",\n \"path\" : \"\\/System\\/Library\\/Frameworks\\/AppKit.framework\\/Versions\\/C\\/AppKit\",\n \"name\" : \"AppKit\",\n \"CFBundleVersion\" : \"2113.40.126\"\n }\n],\n \"sharedCache\" : {\n \"base\" : 140703651663872,\n \"size\" : 15224815616,\n \"uuid\" : \"341ea950-3974-372a-a140-92d2252fd87c\"\n},\n \"vmSummary\" : \"ReadOnly portion of Libraries: Total=1.5G resident=0K(0%) swapped_out_or_unallocated=1.5G(100%)\\nWritable regions: Total=1.7G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=1.7G(100%)\\n\\n VIRTUAL REGION \\nREGION TYPE SIZE COUNT (non-coalesced) \\n=========== ======= ======= \\nAccelerate framework 128K 1 \\nActivity Tracing 256K 1 \\nCG backing stores 3840K 4 \\nCG image 96K 8 \\nColorSync 100K 9 \\nCoreAnimation 124K 7 \\nCoreGraphics 12K 2 \\nCoreImage 4K 1 \\nCoreUI image data 1036K 7 \\nFoundation 16K 1 \\nKernel Alloc Once 8K 1 \\nMALLOC 1.0G 593 \\nMALLOC guard page 32K 8 \\nMALLOC_LARGE (reserved) 256K 2 reserved VM address space (unallocated)\\nMALLOC_NANO (reserved) 256.0M 1 reserved VM address space (unallocated)\\nOpenGL GLSL 256K 3 \\nSTACK GUARD 96K 24 \\nStack 99.7M 26 \\nStack Guard 4K 1 \\nVM_ALLOCATE 186.9M 329 \\nVM_ALLOCATE (reserved) 96.0M 2 reserved VM address space (unallocated)\\n__DATA 110.4M 572 \\n__DATA_CONST 29.2M 324 \\n__DATA_DIRTY 1542K 195 \\n__FONT_DATA 4K 1 \\n__GLSLBUILTINS 5176K 1 \\n__LINKEDIT 719.8M 77 \\n__OBJC_RO 82.6M 1 \\n__OBJC_RW 3200K 2 \\n__TEXT 776.4M 573 \\n__UNICODE 592K 1 \\ndyld private memory 1152K 3 \\nmapped file 172.9M 28 \\nshared memory 1284K 17 \\n=========== ======= ======= \\nTOTAL 3.5G 2826 \\nTOTAL, minus reserved VM space 3.2G 2826 \\n\",\n \"legacyInfo\" : {\n \"threadTriggered\" : {\n \"queue\" : \"com.apple.main-thread\"\n }\n},\n \"trialInfo\" : {\n \"rollouts\" : [\n {\n \"rolloutId\" : \"5fc94383418129005b4e9ae0\",\n \"factorPackIds\" : {\n\n },\n \"deploymentId\" : 240000370\n },\n {\n \"rolloutId\" : \"607844aa04477260f58a8077\",\n \"factorPackIds\" : {\n \"SIRI_MORPHUN_ASSETS\" : \"6103050cbfe6dc472e1c982a\"\n },\n \"deploymentId\" : 240000066\n }\n ],\n \"experiments\" : [\n\n ]\n}\n}\n\nModel: iMac19,1, BootROM 1731.100.125.0.0, 6 processors, 6-Core Intel Core i5, 3 GHz, 16 GB, SMC 2.46f12\nGraphics: Radeon Pro 570X, Radeon Pro 570X, PCIe, 4 GB\nDisplay: iMac, Retina 5K (5120 x 2880), Main, MirrorOff, Online\nMemory Module: BANK 0/ChannelA-DIMM0, 8 GB, DDR4, 2667 MHz, Micron, 8ATF1G64HZ-2G6E3\nMemory Module: BANK 2/ChannelB-DIMM0, 8 GB, DDR4, 2667 MHz, Micron, 8ATF1G64HZ-2G6E3\nAirPort: spairport_wireless_card_type_wifi (0x14E4, 0x7BF), wl0: Jul 12 2021 19:26:30 version 9.30.464.0.32.5.76 FWID 01-45ccefcd\nBluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports\nNetwork Service: Ethernet, Ethernet, en0\nUSB Device: USB31Bus\nUSB Device: FaceTime HD Camera (Built-in)\nUSB Device: lenovo USB Optical Mouse\nThunderbolt Bus: iMac, Apple Inc., 47.5\n```" ]

[ "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", "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 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)", "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", "High Resolution Render support\nSome fields needs to be able to output really high resolution renders out of EEVEE.\n\nFor now, we just try to allocate the asked buffer size and live with the consequence.\n\nMost GPU have a limit of 16K² texture resolution and some really high renders could not fit GPU memory in some cases.\n\nTo workaround this issue, we need to implement a multipass rendering.\n\nThe issue with this approach is that Screen Space effects (GTAO, SSR, SSRefract, SSSubSurfaceScattering) cannot take the whole picture into account.\n\nWe can split the rendering into tiles, scanlines, checkerboard pattern but the artifacts of SS effects will likely to be different for each", "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", "EEVEE and Workbench missing animatable properties\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n\nWorking-ish*:\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release) \nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release) and later\n\n\nEEVEE and Workbench's render properties (`Properties Editor --> Render Properties`) are, for the most part, not animatable.\nThis is in contrast to Cycles which, *for the most part*, has all settings set to be animatable.\nBack in 2.79b the OpenGL \"Workbench\" Render options were supported:\n\n\n\nSome of the panels like Film, Simplify and Colour Management (which exist in all render engines) work as expected from 2.7X to 2.8X.", "Node Group Sliders Slow Performance using Packed Textures\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 2.83.6, also tested in the 2.91 daily build, and 2.90.1. Same performance.\n\nUsing custom nodes groups sliders with packed textures make them very slow using Cycles, on EEVEE it seems working fine. \nIf i unpack the textures the sliders acts normally.\nI also notice every time i use any slider in the top left corner shows \"Updating images\" and the freeze occurs. \nI also discover if i change the values of all the sliders that are using the packed textures it comes back to normality and the lag disapears.\nIm not a tech but it seems it has something to do with loading the textures.\nSize and image formts seems that are not the problem i tried changing them.\n{[F9090399](Packed_textures_performance.gif), size=full}\n\n- Append node group with textures unpacked.\n- Sliders working good and fast with textures unpacked.\n- Pack the textures.\n- Sliders and load times freezing.\n- Unpack the textures again.\n- Sliders come back to normality.\nor\n- Open attached .blend file\n- Play with the custom node sliders\n- Unpack the textures again.\n- Sliders come back to normality.\n\n[Packed _Performance_new.blend](Packed__Performance_new.blend)\n\n", "Cycles motion blur does not interpolate correctly\nOperating system: Fedora Linux (Wayland)\nGraphics card: AMD GPU (but Cycles renders on AMD CPU)\n\nBroken: 3.5.0\nWorked: never? (same results till 2.83)\n\nCycles motion blur interpolation is strange.\nIt's very noticeable when an object or the camera is bound to a constraint and the motion blur shutter is set very high (like 60 frames). Cycles motion blur will interpolate it wrong. I will include pictures and .blend files\n\n- Open attached .blend file\n- Render the first frame with EEVEE and Cycles and compare the motion blur.\n\n", "Viewport animation renders take progressively longer if there is a split in the scene!\nOperating system: macOS-13.5.2-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Ultra 1.2\n\nBroken: version: 3.6.2\nWorked: Never\n\nWhen animating a render from the viewport, if a spline is present in the scene each frame takes progressively longer and longer to render until it takes a painfully long time per frame. Once the spline is deleted from the scene, each frame takes the same amount of time to render!\n\nMake an animation of approx 1000 frames\nInclude a spline in the scene - you don't have to render it, it just needs to be in the scene!\nViewport Render Animation\nYou should quickly notice that each frame is taking longer and longer to render\nBy the time you get to frame 800 (if you care to wait that long) you will be pulling your hair out!\n...now delete the spline\nViewport Render Animation\nEach Frame now takes the same time to render and you can smile once more.\n\n....I'm already guessing that whoever is gracious enough to try this will magically not have the problem - if so, please reply and I will supply files... I just would rather not at this time as I am interested to see if it is indeed reproducible? I can confidently say that I have experienced this issue for at least 5 years, but it's only now that it has come to bite me again and I have finally proven (to myself, at least) that the issue is spline related - my scene had one single 'Annotation' spline that I wasn't even aware of hanging around in it and deleting it sped up render times by an order of magnitude!\n\nThanks\nWayne\n\n", "Regression: 3.1 & 3.2 Image/UV Editor poor performance (Byte textures, window dragging, maximizing area)\nOperating system: Win 10\nGraphics card: 980 Ti, recent drivers\n\nBroken: 3.1 beta v31.f420118335e4 and 3.2 alpha master.95005bbe02cf\nWorked: 3.0.x\n\n**Short Description**\nTest 1: \nWhen interacting with UV / Image editor my fps drops from 144 to ~20 - depending on how large is the Image Editor window.\nThe actual image size or format doesn't affect the performance at all, but Image Editor without any image loaded (just with grid) is completely smooth when moving it around.\n\nTest 2: \nThe performance is also significantly lower when dragging any window border\nWas completely smooth in 3.0.x\nCould be specific for this GPU / architecture, since my coworker with AMD can't reproduce the issue.\nnote this also has its own report, see #97272 (Regression: Blender 3.1 UI editor resize /border dragging performance), so maybe this could be removed from this report...\n\n**Steps to Reproduce**\nTest 1:\n\nopen UV / Image Editor\nload any image\npan the view around, move UVs etc\nshould be noticeably slower than in 3.0.x\n[2022-02-02 11-03-10.mp4](2022-02-02_11-03-10.mp4)\n\nTest 2:\nopen the default scene\ndrag any window border\nshould be noticeably slower than in 3.0.x\n[2022-02-02 11-00-05.mp4](2022-02-02_11-00-05.mp4)\n", "Scene Proxies in the Video Sequence Editor\nWindows 7 Ultimate, 64-bit, 32GB, 5960x, Nvidia Quadro FX 1800 (Primary) & GeForce 9800 GTX+ (Secondary)\n\nBroken: (2.79a) Official builds\nWorked: (2.79) Official builds\n\n\nTo cut a long story short @ideasman42 disabled Scene proxies in the Video Sequence Editor because:\n\n> In #54048#485268, @ideasman42 wrote:\n> Looked into this and for now **building proxies doesn't support anything besides movie, so disabling support for this.**\n> \n> 6535f668b4\n\n\n*This shocked me, have I been using Blender wrong?* Because I've been happily doing this for months.\n\nI don't quite understand the rationale behind the removal of is.\n\nThe main problem for me is that I have projects (made in 2.79 and earlier) that rely on scene proxies and when opening them up in 2.79a viewing or creating them doesn't work.\n\nNow there *are* issues with Scene Proxies most notably the aforementioned (#54048) one and it can be really bad:\n\n[0001-2565.mkv](0001-2565.mkv)\nand\n**Other proxy issues**\n - Skipping frames whilst rendering.\n - Properties side panel scrolls up after changing proxy location in the File Explorer.\n - Overwrite don't have the same behaviour as Overwrite does in the render setting (in the properties editor)\n - and [inconsistent functionality ](F2418236).\n\nBut I've always treated this as an incomplete feature, (same way I treat NetRender, it's somewhat stable but is inconsistent. e.g. blender/blender-addons#52502) throwing in a bug report due to just crashing (#53792) and have been fine.\n\nBut now with the update, the [Proxy/Timecode Panel ](proxy.html) is still there and does nothing. and as I said in my query to @ideasman42's decision to disable this:\n\n> In #54048#485618, @ChristopherAnderssarian wrote:\n> So, @ideasman42 does this invalidate my bug report? #53792\n> Also, is it a good idea to disable this considering the Proxy/Timecode Panel option still there (or are you still working on this)?\n> \n> With no information or feedback in the Blender Manual or when trying to create proxies (nothing happens), `you are going to get users confused on a essential feature that worked` (works fine in cycles for me (not the file names the crashing)) in 2.79 `and now doesn't with no apparent reason why. `\n\n___\n\n> In 6535f668b4, @ideasman42 wrote:\n>>...generating proxies currently only works for movies...\n\n*No... they don't. They worked for Scenes before. (and they work for images for that matter)*\n>>...cancel until other types of sequence strips are supported...\n\n*What do you mean by this? That it's officially 'supported', documented?* \n___\n\nNow that I've been trying to research around a bit, is this an incomplete feature or has it slowly gotten broken in time?\nThere's #43857 which uses a scene proxy. So there must be other uses who uses this right? Or was this just an example?\nI would love to use this with Eevee; having the proxies rendered in no time and my GPU not getting taxed.\n___\n\nWhat I think to be good next steps:\n\n - Having the functionality back as it was before.\n - An open task to deal with the *Other proxy issues.*\n___\n\nZipped folder with a working Blender file and proxy:\nTested in Ubuntu VM both 2.79 and 2.79a with reproducible behaviour.^\nTested on a separate laptop with both 2.79 and 2.79a with reproducible behaviour.^\n(Note: In my Ubuntu VM I had to toggle Textured Solid button in the Scene Preview/Render Panel to get the proxy showing in 2.79.)\n(^ Reproducible behaviour being: fully working in 2.79 and not working at all in 2.79a)\n[Blender_VSE_Testing_Scene_Proxy.zip](Blender_VSE_Testing_Scene_Proxy.zip)\n\n\nI'm sure this was just a misunderstanding.\nYours,\nA passionate Blender user", "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", "Eevee preview nodes with drivers performance drop Round 2\n[NodesPerformanceDropRound2.blend](NodesPerformanceDropRound2.blend) this is extend of previos task #71214\nSystem Information\nOperating system:Windows 10\nGraphics card: GeForce GTX 1060\n\nBlender Version\nBroken: Blender 2.81 Beta aff6446e064f and 2.82 Beta 092deb88b074\nWorked: 2.8\n\nShort description of error\nComplex shader with large amount of math nodes and with drivers slow down performance\nin 2.8 60 fps\nin 2.82 30 fps\n\nExact steps for others to reproduce the error\nCreate material with 30 node groups contains 30 math nodes, add driver to shader. Set viewport to material preview and watch performance droping", "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" ]

[ "Scene strips in the VSE are excessively slow to playback.\nOperating system: Windows 8.1\nGraphics card: Geforce 860m, Geforce 980\n\nBroken: 2.80, 2019-03-10\nWorked: 2.79\n\nScene strips in the vse will play back very slowly. This seems to happen regardless of render engine, or scene preview type in the vse preview settings, tho some settings and engines do provide better performance than others, even the best combination is still terribly slow.\nFor example: an eevee scene with only a camera and no special effects enabled will play back at 1-2fps in the vse, but animation playback in the 3d viewport will of course be over 30fps.\nNote that this is not the same as the slow playback/rendering due to the color transforms, this still happens when the color is set to 'Default' transform and 'None' look.\n\n\nCreate a second Scene\nAdd that scene to the vse of the first scene\nstart playback\n\n\nI have attached a simple .blend file where I have tried to make the playback as efficient as possible... still only get about 2fps. [eevee vse test.blend](eevee_vse_test.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```", "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 becomes unstable/crashes after using \"Reload Scripts\" if using any \"ShaderNodeCustomGroup\" nodes.\nOperating system: Windows 10\nGraphics card: NVIDIA\n\nBroken: 2.81\n\nIf you manipulate a \"ShaderNodeCustomGroup\" node after having used the \"Reload Scripts\" operator (F8) Blender will become unstable.\n\nAttached is a small addon that implements a minimal custom node group.\n1. Enable the addon and switch to the shader editor.\n2. Create the custom node (Add->Test Category->TestNodeCustomGroup)\n3. Trigger 'Reload Scripts' (F8 key).\n4. Adjust the color input of the custom node.\n5. Repeat steps 3/4 until you crash (usually crashes on first or second try for me)\n[node_custom_test.py](node_custom_test.py)", "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", "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?", "Blender 3.5 and 3.5.1 are crashing while using Metal as backend\nOperating system: macOS 12.6.3\nGraphics card: Radeon Pro 580 8GB\n\nBroken: 3.50, 3.51 (Metall Backend)\nWorked: 3.50, 3.51 (OpenGL Backend)\n\nBlender simply hang. I use eevee, if you switch to rendered viewport shading it crashed complete system. I use Metall as backend, if I choose OpenGL it works fine. \n\n \nI attached an .blend file for example.\n\n", "Crash when trying to delete particle system or undo CTRL+Z\nBroken: version: 2.82 (sub 7)\nWorked: 2.79\n\nAfter updating from 2.79 to 2.8 this file file crashes when I try to delete the Plane. When I go to Edit mode, trying to rotate, grab or do anything it crashes. Plane has a particle system on it. When i try to delete it crashes too. Basically if i touch the Plane in any way it will crash and there is no way to get rid off it. Cannot delete the particle system either. Also, when i try to undo the last step CTRL it also makes it crash.\n\n- Open the attached file\n- Try to delete the plane or its particle system \nCrash.\n\n[T74786_2-83.blend](T74786_2-83.blend)\n\n\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)", "Latest Blender 4.0 not opening\nOperating system: Linux-5.15.0-83-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: blender-4.0.0-alpha+main.b5c89822ac40-linux.x86_64-release\nWorked: 3.6.3 Release Candidate\n\nAfter double-clicking on the \"blender\" starter-folder, it shows what you can see on the picture, before canceling the session\n\nJust try to start 4.0. I guess it's my drivers and noone can confirm, right?\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```", "Open Blender\nHello\n\nI can't open the app, i dowload all versión windows, windows store and portable.\n\nsxstrace.exe\n\nI have windows 10, but i can open the app,\n\nI hope you can help me\nThanks\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.", "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", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "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" ]

[ "Blender crashes when I exit\nWindows 8.1 x64\n\nBroken: 2.71 and Version blender-2.71-4b4ae83-win64\nWorked: 2.70\n\n\nHi when I quit out of blender it cases the blender process to crash. Where it says \"Blender has stop working\". And widows gives me a change to debug the process or close the program.\n\nMy graphics card is an ATI Radeon HD 4550 with the WDDM v.1.1 Driver \nversion 8.97.10.6\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\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```", "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", "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.", "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)", "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", "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", "Regression: Crash when animation is playing\nOperating system: Windows 10\nGraphics card: 2x RTX3080\n\nBroken: 3.6 and 3.6.1 release canditate\n\nPress the space bar, the animation starts and Blender closes. The console says : EXCEPTION_ACCESS_VIOLATION\nI also test the file with an independent portable version of Blender, but the crash still occurs.\n\nPress space bar to play the animation and wait the frame 48.\n\n[Fluent_Testing_7_for_blend_dev.blend](https://projects.blender.orgattachment)", "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", "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) ", "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", "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)", "Crash When Adding Hair Subdivision upon Viewer node\nOperating system: Windows-10-10.0.17134-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\n\n\nAdding hair subdivision will cause crash immediately when you are using viewer node to visualize field values in the viewport.\nNote no crash will occur if the viewer node is inactive.\n\n[Hair Crash.crash.txt](Hair_Crash.crash.txt)\n\n1. select default cube\n2. shift+A to add empty hair\n3. in the node tree add viewer node.\n4. Crash if adding subdivision\n[Hair Crash.blend](Hair_Crash.blend)", "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", "Baking dynamic paint to image sequence is cancelled without user interaction\nOperating system: Window 10, 64 Bit, 128GB RAM\nGraphics card: RTX 3090 with the newest studio driver.\n\nBroken: 2.93.5\nWorked: ./.\n\nI am following the cggeek tutorial on creating rain effects (watch?v=35bbyAJodEQ). Like said in 06:30 of the tutorial I wanted to bake the image sequence.\nIt happened some times that the Blender status line said that the bake had started, it sopped announcing that the bake had been cancelled without user interaction.\nI installed 2.93.5 and isolated the 3 concerned objects: The emitter plane, the plane I want to create the baking for and the drop. I started Blender via the debugging command file, clicked on bake and Blender crashed. \nThese are the produced files:\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\nPreviously I have tried to find out if the modifier sequence has an effect, but it does not have one. The position of the Dynamic Paint modifier can be arbitrary, and it is not essential if the plan includes particle systems or not.\n\nAfter more trials I could not reproduce the crash, only the indication of cancelling appeared - furthermore withour interacton:\n\n\n\nThanks\n\n- Open attached file (This is a minimum .blend file, which crashed on the first try after installing 2.93.5 and led to the production of the debug files above)\n- With the object \"aBodenFriedhof.002\" selected, go to {nav Physics Properties > Dynamic Paint > Output} and press `Bake Image Sequence`\nAfter a short time, the process will be canceled without an explanation.\n\n[dpSplit.blend](dpSplit.blend)\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" ]

[ "Add texture paint slot crash\nOperating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.8.38\n\n\nBroken: version: 2.80 (sub 64)\nWorked: (optional)\n\n\nBlender crashes when I try to add a texture paint slot (any kind, base color, specular etc, and in any mode )\n\nSwitch to Texture Paint workspace\nTexture Slots > Add a texture paint slot\n\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", "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", "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.", "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", "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", "GPencil: Low hardness values always draws yellow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.91.0 Alpha\n\nGrease Pencil creates yellow transparency with lower hardness values on brush.\n\n - Open in 2D Animation mode\n - Set to a \"Dots\" brush (eg. Dots Brush) its most noticeably shown there. It happens for the other ones too but this one is most noticeable\n - Set the Radius to something largish so we can see whats happening (eg 2000px), or zoom in \n - Draw a circle and you'll be able to see it\n\nIt looks like there's a faint yellow tinge transparency which builds up when putting the grease pencil strokes on top of each other.\nWhat it looks like:\n\n\nExample blend\n[yellowtransparency.blend](yellowtransparency.blend)\n\nBasic repro gif\n\n\nMe shading a ball\n\n\n\n\n\n", "CPU + GPU render precision differences for small, far away area light\nOperating system: Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.74\n\nBroken: version: 2.81 (sub 8)\nWorked: (optional)\n\nThis was recently reported in this thread : \n2\n\n I can at least say, that when using small area lights below a size of 1 (e.g. meter), and it’s getting darker (the light source is far away from the object) you can clearly see this problem: CPU renders the tiles darker than the CUDA GPU.\n\n\n\nCreate a new scene with the cube, remove the default light, create an area light, resize it to lets say 10% (or 1%… the smaller the bigger the effect) and rotate it that it lights the default cube.\nHere is a .blend that reproduce the issue :\n[TileProblem.blend.blend](TileProblem.blend.blend)\n\n", "Grease Pencil eraser acts as though full pressure was applied when tablet stylus is released\nGraphics card: GTX 980\nReproduced on these operating systems:\n- Windows 10\n- Arch Linux 6.3.1 (KDE Plasma 5.27)\n\nReproduced using these drawing tablets:\n- HUION H610PRO V2\n- HUION Q11K\n\nBroken: Reproduced in 3.5.1 and 4.0 (locally compiled 7372b3bdda350)\nWorked: Before 74f291cdea979 (2016-01-11)\n\nErasing lightly with a pressure-sensitive tablet is made difficult by a bug that erases a large area (as if the stylus was pressed down with maximum pressure) whenever the stylus is released:\n\n<video src=\"attachment\" title=\"pen_pressure_release_bug.mp4\" controls></video>\n\nThis is the code that introduced this issue (added in 74f291cdea979 for #47101)\nRemoving it completely resolves this issue:\n```cpp\n /* Hack for pressure sensitive eraser on D+RMB when using a tablet:\n * The pen has to float over the tablet surface, resulting in\n * zero pressure (#47101). Ignore pressure values if floating\n * (i.e. \"effectively zero\" pressure), and only when the \"active\"\n * end is the stylus (i.e. the default when not eraser)\n */\n if (p->paintmode == GP_PAINTMODE_ERASER) {\n if ((event->tablet.active != EVT_TABLET_ERASER) && (p->pressure < 0.001f)) {\n p->pressure = 1.0f;\n }\n }\n```\n\nA sample of what I observed by logging pen pressure events while reproducing the issue:\n```\ntablet.active: 1, p->pressure: 0.399948\ntablet.active: 1, p->pressure: 0.326324\ntablet.active: 1, p->pressure: 0.246231\ntablet.active: 1, p->pressure: 0.168350\ntablet.active: 1, p->pressure: 0.097900\ntablet.active: 1, p->pressure: 0.038330\ntablet.active: 1, p->pressure: 0.000000\n```\nWhen I **release** my stylus, an event of type `EVT_TABLET_STYLUS` (`1`) with a pressure value at (or very close to) `0.0f` is sent. This triggers the above conditional that sets `p->pressure` to `1.0f` (full pressure), causing the issue.\n\nIn the attached .blend file:\nUsing a pressure sensitive drawing tablet, lightly use the Grease Pencil eraser tool to erase the strokes, then release your stylus.\n(If your drawing tablet sends an event with a pressure value lighter than `0.001`, the issue will occur)\n\n## Question: Is #47101 still relevant and applicable?\nI'm not sure I fully understand the use-case that was effected by #47101 or whether it is even still applicable to Blender today, 8 years later.\nIf someone can shed some light on what the intended behavior of 74f291cdea979 is and whether it is still needed, I will happily work on a pull request to reconcile this issue (or simply remove the conditional if it is no longer applicable)\n\n", "Grease Pencil problem in drawing short lines\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.83 (sub 10)\n\nThere is a problem with drawing short lines in this version\n\nDraw a very short line and then zoom in on it\n", "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", "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", "GPencil: Stroke not working with Holdout\nOperating system: Windows 10\nGraphics card: GeForce GTX 970\n\nBroken: 2.82a, as found on the splash screen\nWorked: Never\n\nSetting a collection as holdout in view layer options in cycles works as expected on grease pencil objects in the viewport render preview, but does not work on grease pencil objects when rendering. The entire grease pencil object is visible in the renders, whereas in the viewport render preview the parts of the grease pencil obscured by foreground objects set to holdout is alpha. \n\nCreate a grease pencil empty behind the startup cube. \nDraw some stuff. \nPut the startup cube in a collection and set the engine to cycles. \nFrom the view layers options for the new collection containing the startup cube, set it to holdout. \nTurn on render preview from the viewport shading options. Notice that the cube is invisible, along with the parts of the grease pencil that had been obscured by the cube.\nPress F12\nNotice in the rendered image that all of the grease pencil is visible, even the parts we had expected to be alpha masked from the startup cube holdout.\n\nSee the attached blend file.\n[HoldoutTrouble.blend](HoldoutTrouble.blend)\n", "Wireframes aren't displayed in Edit Mode when Overlays are off. \nBroken: 2.82a, 2.83, 2.90 alpha\nWorked: 2.81a\n\nWireframes aren't displayed in Edit Mode if Overlays are turned off, but they're only shown in object mode, or if there's a modifier with \"display in edit mode\" option. \n\nOpen default file.\nChange to wireframe mode.\nturn off overlays.\nchange to edit mode. Wireframe won't be shown.\n", "GP kills bloom\nOperating system: Linux-5.15.0-83-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: GeForce GT 630/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.157\n\nBroken: version: 3.6.3 Release Candidate\nWorked: \n\nWhen you have mesh objects emitting in front of grease pencil objects, bloom doesn't work there.\n\n\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)" ]

[ "Grease Pencil objects not reacting to lights \nOperating system: OSX High Sierra\nGraphics card: AMD Radeon R9 M370X 2 GB / Intel Iris Pro 1536 MB\n\n2.83 Alpha\nDate 2020-03-12 19:47\nHash: fa823f0af867\n\nWhen adding a light to the scene, the grease pencil objects don't react to it.\n\n1. Open new 2D Animation file\n2. Select the Grey \"Solid Fill\" material.\n3. Draw a shape.\n4. exit into Object mode\n5. Add a Light. (and orient it to object depending on light selected)\n" ]

[ "Color management is broken in the Sequencer\nOperating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1\n\n\nBroken: version: 2.80 (sub 74)\nWorked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79\n\nWeird things happens when changing the color management settings in the VSE:\n- wrong color display\n- make sound\n\nWith a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.\nAlso, changing this setting does not apply the change directly, the VSE has to be refreshed.\n\nAnother issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.\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", "viewport shading > color > texture, textures not affected by transformation\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99\n\nBroken: version: 4.0.0 Alpha\n\n\nViewport solid mode color option \"Texture\" does not take mapping nodes into account.\n\n---------\n\nOriginal description:\n\nwhen switching to texture in viewport shading color properties, the image textures are only affected by UV editor and not by texture coordinates node, in My opinion this texture preview is much more faster and better than EEVEE, if only you can ditch EEVEE and make the workbench preview the main material preview that support all nodes, If you notice Cinema 4D ,Max and Maya, they all use a material preview similar to this Blender Workbench preview, I don't know if you noticed these days almost everyone is saying that they prefer previewing and editing their material in cycles rather than EEvee because its way more faster to load, I tested in a 2k scene cycles took a couple of seconds switching to render view on CPU, Eevee took 12 Mins to load all textures, I hope Eevee next solves this issue if not, I would really hope that you consider developing the workbench preview \n\n?\n\n", "Drag-to-toggle visible/selectable/renderable in the Group view.\nWindows 64\n\nBroken: 2.70a\n\nThe drag-to-toggle visible/selectable/renderable in the Outliner does not work in the Groups view.\n", "GPencil: Average tool in Vertex Paint mode not working as expected\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\nThe tool paints colors that exist in points far from the brush's area of influence and sometimes paints unexisting colors.\n\n1. Draw simple strokes with the Solid Stroke material.\n2. In VP mode paint half of it orange and half blue.\n3. try the the Average tool in the half blue area then in the other half.\n4. Now do Paint > Reset Vertex Color.\n5. Try the Average tool again.\n\n<video src=\"attachment\" title=\"Vertex Paint Bug-1.mp4\" controls></video>\n\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)", "Smear tool painting vertex colors corrupts color info: part 2\nvertex colors get corrupted under certain blend mode combinations. 3.0.1 master.\n\nusing the smear tool over blue colors introduce green, magenta, yellow, gray and orange not present inside the blue ranges.\n\npainting with blue results in grays instead. \n\ni had this problem in 3.2 alpha using sculpt vertex colors, but when i got back to a project in 3.0.1 it happened with vanilla vertex colors tool. \n\nincluded a file this time\n\n[vertex colors bug.blend](vertex_colors_bug.blend)\n\n\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.0.1\nWorked: (newest version of Blender that worked as expected) 2.93\n\nSmear tool painting vertex colors corrupts color info\n\nuse paint brush with blue color. paints gray instead.\nuse smear brush. it should smear blues and not oranges and greens.\n", "Color of header-bar of Graph and Drivers Editors is darker than that of the other editors.\nOperating system: Linux-4.19.69-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40\n\n\nBroken: version: 2.80 (sub 75)\n\n\nColor of header-bar of Graph and Drivers Editors is darker than that of the other editors. This looks a bit inconsistent.\nI feel that the color should be lighter as in Timeline and other editors.\nI'm using the default Blender Dark theme, and haven't changed any of the theme settings.\n\n\n[Based on the default startup .blend file]\n\n{[F7723159](Graph_Editor_header_color_darker.png), size=full}\n\nThanks!", "View Pan not working for smaller clip start value\nOperating system: win 10 pro\nGraphics card: rtx 2060\n\nBroken: 3.5, 2.83\nWorked: never?\n\nFor smaller `clip start` value when we zoom out, `View pan` does not work\n\n- Open .blend file\n- Pan around by any method\nIncrease `clip start` value, this will fix panning problem\n[Sand_003.blend](Sand_003.blend)", "The alpha channel set in Viewport Display settings for an object's material appears as if it's set to 0 when a background image is behind it\nOperating system: Linux x64 (Debian-based)\nGraphics card: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a)\nNvidia drivers, version: 440.31\nKernel: 4.19.0-6-amd64\n\nBroken: v2.81a and v2.80, downloaded from blender.org as a tar.gz\n\nWhen you change the Viewport Display color for an object to have an alpha channel < 1.0 but > 0.0, then manipulate the scene so that there's a reference or background image behind that geometry, the overlapping area will appear completely transparent (alpha 0.0).\n\n\n1. New scene\n2. Add a cube: Shift a -> Mesh -> Cube\n3. Add an image: Shift a -> Image -> Reference (or background)\n4. Select an image\n5. Position the image behind the cube in the viewport. Select the cube.\n6. In the properties panel, select Material Properties\n7. In the Material Properties panel, select Viewport Display\n8. Change the Color to have an alpha between 0.0 and 1.0, exclusive\n\n**Observed behavior**\nLike the screenshots, the overlapping area allows the background image to completely shine through.\n\nQQxLCpv\n\n**Expected behavior**\nThe object will become uniformly translucent and allow the background/reference image to be partially visible, not make the image fully transparent in the overlap.\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", "EEVEE: Mixing between a fully transparent and holdout shader yields a half transparent result\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.2.0 Release Candidate\nWorked: I thinck the issue is for \"all\" versions of blender\n\nHoldout shader having issue with alpha (semi transparency).\n\nPut a image plane with exr image that contain alpha. When using a holdout shader mixed with another shader (transparency shader for exemple) the alpha of the image sequence is used for the mix of the 2 shaders. It should have a complete transparent image with the holdout of other object in the scene. The issue is that there is a dark outline for the semi transparent. Holdout have issue dealing with semi tranparency ? or maybe something else.\nSee the attached image to understand the issue.\n\n\n", "GPencil: Fill tool Ignore Transparent strokes setting broken\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 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\n", "2.83lts Regression: Viewport render image ignores colormanagement, and appears to be hardcoded to use sRGB.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBisect points to 190fd795a9\nBroken: version: 2.83.0\nWorked: 2.82a\n\n`Viewport Render Image` ignores color management. The image produced is clamped to 1.0 according to the color sampler. It appears to be hard coded to sRGB.\n\nCreate a Scene that has scene linear color values above 1.0. Render with Filmic. Then do `viewport render image` and see how it produces an image with blown out highlights.\n\n2.82a:\n\n\n2.83:\n\n\n\n[test.blend](test.blend)\n\n", "Theme: Inconsistent solid color for the background in the 3D viewport\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75\n\nBroken: version: 2.90 (sub 0)\nWorked: 2.79b\n\nThe color of the 3D viewport background set to theme seems to not match with the color set in the theme setting.\n\nCheck the examples below with the color #36393F\n\n2.79b: color is exactly like in the theme setting.\n\n\n2.80 to 2.82: color looks good but seems grainy.\n\n\n2.83 to 2.90: color is slightly changed, when sampled not the expected theme color.\n\n\n- Open blender\n- In the initial layout change the Outliner editor to Preferences\n- Go to background color option\n- Use the colorpicker to get a sample of the background color\nThe color shouldn't change, but it does" ]

[ "3d view's header no longer transparent (with Tool Settings hidden)\nOperating system: Linux-4.15.0-159-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.0.0 Beta\nWorked: 2.93 and earlier\nThe 3D view's header at the top or bottom of the screen is no longer transparent in 3.0, when the `Show Tool Settings` is disabled, as it used to be in earlier versions. I really liked the additional amount of screen space you could gain by disabling the tool settings. \n\nSee screenshot and compare green(before) with orange(now).\n\n\nWhatever you do, there's now always the thick double bar at the top/bottom of the screen with plenty unused space.\nIn the 3D view's theme space, the header transparency only affects the tool settings, not the header itself.\n\n\n* disable `Show Tool Settings` in 2.93 and 3.0 \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)", "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", "Error baking particles in OSX\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.135\n\nBroken: version: 2.83.1\n\nI have two particle emisor and when I try to bake it crash.\nI try it in Linux and work perfectly!\n[TEST_ERROR.crash.txt](TEST_ERROR.crash.txt)\n\n[TEST_ERROR1.blend](TEST_ERROR1.blend)\n\n- Open file\n- Bake particles\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.", "Crash after Disk Cache Particle bake while set to render as path\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.0.1\nsame results on daily 3.1 build\n\nBlender crashes after finishing baking the particles to disk.\nThen proceeds to delete the baked files upon reopening the file. \n(don't know if the deletion is intended behaviour or not, but it stops you from being able to salvage the bake unless you rename / duplicate the cache folder beforehand)\n\nSeems to only happen with disk cache bake and not baking to memory. \nChanging the 'render as' setting to anything but 'path' seems to stop the crashing.\n\nOpen file, bake the particle system\n[Particle Bake to DiskCache Crash.blend](Particle_Bake_to_DiskCache_Crash.blend)", "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)", "Mouse movement causes crash during particle bake\nOperating system: Win10\nGraphics card: GTX2060\n\nBroken: 2.90, 0330d1af29c0, master, 2020-08-31\n\nReproducible crash when baking particle animation and moving mouse\n\nSadly, I was not able to reproduce the crash in a simpler file, so I assume it has to be related to the current boid setup with lots of drivers.\n\n1. Load the attached blend file\n2. Make sure Workspace is set to layout\n3. Select one of the two particle-emitters\n4. Click bake\n5. During bake move the mouse over Render or Graph views\n- > Crash\n\nAlso see this video capture: VIUy6r9S-Hk (It ends in the moment of the crash)\n\n[swarm-test1.crash.txt](swarm-test1.crash.txt)\n\n[swarm-test2-crash.blend](swarm-test2-crash.blend)", "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)", "crash while setting vertices positions using foreach_set\nOperating system: macOS-12.6.6-x86_64-i386-64bit 64 Bits\nGraphics card: Intel(R) Iris(TM) Graphics 6100 Intel Inc. 4.1 INTEL-18.8.6\n\nBroken: version: 3.6.0\n\ncrash while setting vertices positions using foreach_set\n\nstart blender, run script\n\n```python\nimport bpy\nimport numpy as np\n\nl = 2 ** 28\nme = bpy.data.meshes.new('mesh')\nme.vertices.add(l)\na = np.random.random((l, 3))\nme.vertices.foreach_set('co', a.ravel())\no = bpy.data.objects.new('mesh', me, )\nbpy.context.view_layer.active_layer_collection.collection.objects.link(o)\n```\n\noutput:\n```\nWriting: /tmp/blender.crash.txt\n[1] 13339 segmentation fault /Applications/Blender/blender-3.6.0.app/Contents/MacOS/Blender\n```\n\nin blender 3.4 while using 2**27 length output is this\n```\nError: Array length mismatch (expected -402653184, got 402653184)\nError: Python: Traceback (most recent call last):\n File \"/Text\", line 8, in <module>\nRuntimeError: internal error setting the array\n```\n\ncontents of `/tmp/blender.crash.txt` is just me running script, nothing interesting\n\ninteresting bit from crash report (i can provide in full)\n\n```\nThread 0 Crashed:: Dispatch queue: com.apple.main-thread\n0 Blender \t 0x10bbaef04 foreach_getset + 1124\n1 Blender \t 0x112f45046 cfunction_call + 134\n2 Blender \t 0x112f01015 _PyObject_MakeTpCall + 373\n3 Blender \t 0x112fdf95b call_function + 971\n4 Blender \t 0x112fdbc41 _PyEval_EvalFrameDefault + 24817\n5 Blender \t 0x112fd5a22 _PyEval_Vector + 146\n6 Blender \t 0x112fd5978 PyEval_EvalCode + 120\n7 Blender \t 0x10bb9cd2a python_script_exec + 506\n8 Blender \t 0x10c6754b0 text_run_script + 64\n9 Blender \t 0x10b600ce6 wm_operator_invoke(bContext*, wmOperatorType*, wmEvent const*, PointerRNA*, ReportList*, bool, bool) + 582\n10 Blender \t 0x10b600a03 wm_operator_call_internal(bContext*, wmOperatorType*, PointerRNA*, ReportList*, wmOperatorCallContext, bool, wmEvent const*) + 515\n11 Blender \t 0x10b602025 WM_operator_name_call_ptr_with_depends_on_cursor + 165\n12 Blender \t 0x10c36bffd ui_apply_but_funcs_after(bContext*) + 285\n13 Blender \t 0x10c366fc2 ui_handler_region_menu(bContext*, wmEvent const*, void*) + 434\n14 Blender \t 0x10b604a4f wm_handlers_do_intern(bContext*, wmWindow*, wmEvent*, ListBase*) + 1007\n15 Blender \t 0x10b604020 wm_handlers_do(bContext*, wmEvent*, ListBase*) + 48\n16 Blender \t 0x10b6033ba wm_event_do_handlers + 2554\n17 Blender \t 0x10b5f91b0 WM_main + 32\n18 Blender \t 0x10adea41e main + 878\n19 dyld \t 0x12788152e start + 462\n```\n\n", "GPencil: Selecting textured brushes will crash Blender\nOperating system: Linux-5.8.0-7642-generic-x86_64-with-glibc2.32 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.39\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92.0\n\nWhen appending the textured brushes from the [Blender Cloud](5ccfe64353b85e279cf72acd) into a file, Blender will crash when trying to preview the brushes in the tool settings.\n\n\n - Open Blender 2.93 and select the \"2D Animation\" template.\n - Go to *File*>*Append* and browse to the `pepeland_GP_brush_pack_V1.blend` file. Go into the *Brush* folder and append the brushes `GBrush_001` through `GBrush_010`.\n # Click the brush icon in the tool settings. Blender crashes.\n\n\n\n", "GPencil: Blender crash when GP3 enabled & you open the default 2D animation file\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\n\nBlender crash when GP3 enabled & you open the default 2D animation file & use the Draw tool\n\n- enable GP3 under the experimental features\n- save preferences and restart Blender\n- do File > New > 2D Animation\n- try to draw something.\n\nSince my 2D animation file is customized, I included it below.\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", "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", "Hair display error in blender 3.0.1\nHello, when I add new hair in the Particle Edit mode. Then the hair does not come from the mesh itself, but as if it weighs above it. What's the problem, maybe I'm doing something wrong?\n\n{[F12865495](Безымянный.png)}Operating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: AMD Radeon R7 200 Series ATI Technologies Inc. 4.5.148202 Core Profile Context 21.3.1 27.20.15003.1004\n\nBroken: version: 3.0.1\n\n\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 crashes when adding Particle system (Hair/Interpolated Children)\nOperating system: Mac OS Monterey 12.6 / MacBook Pro 16 (2019) \nGraphics card: AMD Radeon Pro 5500M 4 GB\nIntel UHD Graphics 630 1536 MB\n\nBroken: Blender 3.3.0\nWorked: Blender 2.83.9\n\nShort description of the error:\nAfter adding in Particle system, Blender 3.3.0 freezes, and after 1-2 min computer rebuts itself. \n\nFor compressing, Blender 2.83.9 works fine even with a high number of Interpolated Children.\n\nExact steps for others to reproduce the error:\n- Open a new project\n- Select default cube\n- Select Particle system\n- Add a new Particle system\n- Change Particle system to Hair\n- Add Interpolated children\n- Increase Display amount to \"16\"\n\n[Crash Blender.mp4](Crash_Blender.mp4)", "Increase the emitter number of hair particles causes the program to freeze and crash\nOperating system: macOS-10.14.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.25\n\nBroken: version: 3.2.2 Release Candidate\nWorked: 3.0.1\n\nIncrease the emitter number of hair particles causes the program to freeze and crash.\n\nOperation steps：\n\n - Select a mesh object, activate the particle, select hair type.\n - Activate the hair children and select simple or interpolated type.\n - Adjust the number of hair particles emitter number to 5000 or higher.\n - Blender program freezes, wait a few seconds and then the program crashes and quits.\n\nThe problem can be reproduced on iMacs with both macOS Mojave and macOS Monterey operating systems. After testing, I found that the problem is related to the graphics card model. No similar problem was found on older MacBook Pro with intel graphics cards.\n[macOS Crash Report_macOS Mojave.rtf](macOS_Crash_Report_macOS_Mojave.rtf)\n[macOS Crash Report_macOS Monterey.rtf](macOS_Crash_Report_macOS_Monterey.rtf)\n", "Blender 3.3 particle hair issue\nImac MacOs Moterey 12.6\nImac 27\" 5K\n3.6 GHz 10-core Intel i9\n128GB memory 2667 MHz DDR4\nRadeon Pro 5500 XT 8GB\n\nBlender 3.3.0{[F13624001](Ric-Hair-01a3-HairCard_01.blend)}\n\nBlender 3.3.0\nUsing Particle Hair\nWhile there are 2 Hair groups created in the window\nI am in camera view\nI go to the VIEW sidebar tool - turn off \"camera to view\"\nand attempt to realign the items in the camera view\nThe program and then the computer locks up completely, I cannot move the cursor in the progam window or any other window. I have to force a reboot - has happened 2 times in a row.\n\nI am using cycles CPU enabled\n\nfile attached", "Blender 3.1 MacOS 12.3 crash on viewport display\nOperating system: MacOS 12.3\nGraphics card: Radeon RX480\n\nBroken: 3.1.2\nWorked: 3.0\n\nAs of the 3.1 update, some of my heavier projects and compositions are crashing when moving around on the viewport, I doubt this is related to the new Metal integration added on 3.1 because I tested this with the metal hardware disabled and enabled, I was even able to do cycles previews on gpu and cpu with no crash as long as the viewport isn't moved or rotated.\nDoes not matter if I switch to wireframe view or any preview, switching to eevee, etc. My entire Mac freezes and it takes about 20 seconds before blender crashes and the whole computer starts responding again. The freezing can happen whenever something that changes the viewport happens, such as hiding meshes, rotating, etc, even once it crashed when I switched to the modifier menu and hovering the mouse on the viewport.\n\nAfter finishing calculation, anything that does a change on the viewport.\n[CrashReport.txt](CrashReport.txt)", "Regression: Hair Particles Freeze Entire MacOS!\n\n\n\n| Operating system: | Graphics card: | Owner: | Note: |\n| -------- | -------- | -------- | -------- |\n| macOS-12.3-x86_64-i386-64bit 64 Bits | AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13 | @dr_formalyst | |\n| macOS-11.6.5-x86_64-i386-64bit 64 Bits | AMD Radeon R9 M290X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.6.21 | @jennyp | fixed |\n| macOS-10.14.6-x86_64-i386-64bit 64 Bits | AMD Radeon Pro 570 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.25 | @didi404 | |\n| Mac OS Monterey 12.6 / MacBook Pro 16 (2019) | AMD Radeon Pro 5500M 4 GB | @MaxSonicUA | fixed in Ventura 13.2 and Blender 3.4.1 |\n| Imac MacOs Monterey 12.6 3.6 GHz 10-core Intel i9 | Radeon Pro 5500 XT 8GB | @r189 | |\n| MacOS 12.3 | Radeon RX480 | @CharmanDrigo | |\n\n\n\nBroken: version: 3.1.0\nWorked: 3.0\nCaused by 5b299e5999 (@RoyTheKoi found this)\n\nUsing hair particles freezes entire MacOS, the entire laptop becomes unresponsive and hard reset is required.\nThe problem occurs when hair needs to be displayed in a viewport (if it's hidden in viewport, the system does NOT crash when rendering hair in Cycles. \n\n- Open attached .blend file and turn on the particle in viewport\nor\n- Add ParticleSystem, Hair.\n- Increase the number of particles (over 10 000 will always break it).\nThe computer will freeze (please note the system info).\n\n[bug-hair-report.blend](bug-hair-report.blend)\n[system-info.txt](system-info.txt)\n" ]

[ "Create geometry nodes modifier when selecting an existing one in the editor\nSelecting an already existing geometry nodes tree in the editor on an object without a modifier should automatically create a nodes modifier. This is in parallel to the behaviour of selecting a material without a material slot.\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.", "Regression: Particle mirror broken for particular mirrored mesh.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.1.2. also version: 3.3.0 hash: `8d9d5da13706`\nWorked: 3.0.0, commit hash: `8b44b756d850db38ab4d83513682f2012d88a3f4` from branch 3.0.1 to be exact.\n\nCaused by 02ab4ad991\n\nParticle hair x-mirror results in hair going in all directions instead of being properly mirrored, see the following screenshot: \n\n1. Start from the attached blend file which has an emitter sourced from a base model and mirrored by applying a mirror modifier. I could not reproduce the issue from scratch with simpler geometry and I might have reconnected the hair at some point .\n2. Go into particle edit mode on the `Eyebrows_Particle` object.\n3. Enable x-mirror in the top-right `Options` menu.\n4. Observe that the particles change directions.\n\nHere is what it looks like when it's working in the same particle edit mode with x-mirror enabled. The exact commit that introduced the issue is: `77694b571f5bd297ea7228b30f591ebbd333e0ea`.\n\n\n\n[mirror_bug.blend](mirror_bug.blend)\n\n[repro.blend](repro.blend)\n- open file\n- `Particle` > `Mirror`\n- observe wrong mirroring", "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)", "Hair dynamics stopped working after editing and combing in \"Particle Edit\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.1.0 Alpha\n\nHair dynamics stopped working after editing and combing in \"Particle Edit\"\nPossible duplicates: #91258, #56818\n\n[#93344.blend](T93344.blend)\n\n- Open file\n- Cut hair with Cut brush\n# Comb hair with Comb brush with disabled Preserve Strand Lengths option\n\nSimulation no longer works", "Wrong property changing `matrix_world` and destructive undo via RMB.\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23\n\nBroken:\nversion: 3.6.1\nversion: 4.0.0 Alpha\nWorked: never\n\nReturning to the original state during editing (or canceling) does not give the result that was when editing was started.\n<video src=\"attachment\" title=\"2023-08-16 21-40-53.mp4\" controls></video>\n\n1. Copy script and run\n```python\nimport bpy\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Test Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n col = self.layout.column()\n ob = context.object\n col.prop(ob,'name')\n col.prop(ob,'matrix_world')\n\nif __name__==\"__main__\":\n bpy.utils.register_class(Panel)\n```\n2. Quickly change the scale value for the object matrix.\n3. Press Right mouse button.\n\n", "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", "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.", "Undo unavailable for Remove Vertex Group in edit mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.01\n\nBroken: version: 2.82 (sub 1)\n\n**Bug description**\nAfter remove a vertex group from a mesh while in edit mode, the undo operator still works, but undo buffer does not seem to contain the remove vertex group operation, so using undo undoes whatever was done *before* the removal of vertex group. On entering object mode, using undo will undo the vertex group removal operation *before* any mesh editing, leading to confusing out-of-order undo operations\n\n**Repro steps:**\nCreate new mesh\nCreate vertex group\nSwitch to edit mode\nMove a vertex to make an obvious visible change\nRemove vertex group\nMove another vertex visibly\nSwitch to object mode\nUse 'undo' operator multiple times\n'undo' operator will undo vertex transforms, and appear to do nothing when it reaches the point in the undo buffer where it ought to undo 'remove vertex group'\nSwitch to object mode\nUse 'undo' operator\nRemoved vertex group is back, and edit mode is active\n\nI won't lay out all of the variations, but for more complicated failure modes with weirder out-of-order undo operations, try:\n\n* move vertex, remove group, move other vertex, switch to object mode, use undo function\n\n* create two vertex groups before entering edit mode, move vertex, delete first vertex group, move another vertex, delete second vertex group, move a third vertex. Enter object mode and use 'undo' operator\n\n\n\n\n\n\n\n[system-info.txt](system-info.txt)", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n", "\"Repeat History\" unavailable after \"Undo\"\nCurrently undo clears the operator history,\nideally this should instead keep these actions in sync with the undo history.\n", "Undo, Sculpt mode options reverts back with wrong order and simultaneously\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\n\nTo reproduce:\nWith sphere\n1. Go to sculpt mode\n2. Make a stroke\n3. Change an option (remesh/options)\n4. Make another stroke\n5. Press Undo or {key Ctrl+Z} twice \n\nExpected: one stroke and one option change will be rolled back.\nActually: option wasn`t reverted, but both strokes do.\n\n6. change few options\n7. Press Undo: you will go back to object mode and all options from the Remesh panel will be reverted.\n\n[2021-07-29_11-11-37.mp4](2021-07-29_11-11-37.mp4)\n\n\n", "Missing undo push for Paint Mask and Vertex Selection in weight paint\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 466.77\n\nBroken: version: 3.0.0 Alpha\n\nEnabling or disabling of the Paint Mask and Vertex Selection modes is missing an undo push\n\n\n\n[Weight.blend](Weight.blend)\nEnable Paint Mask\n\nPaint on the model\nUndo\nResult: Both the paint and the paint mask mode are undone", "'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", "Link-drag-search unsupported in texture node editor\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\nWorked: 3.0.0, since there is no such feature.\n\n\"Auto-completion/search\" is not working as intended with Texture Node Editor. For some reason, only reroutes are being displayed. [2022-11-23 22-42-21_1.mp4](2022-11-23_22-42-21_1.mp4)\n\nOpen Texture Node Editor -> Drag from any socket.\n\nNote: sorry for the incorrect spelling of word \"reroute\"\n" ]

[ "Problem Undoing in geometry nodes while using Edit mode\nBlender Version:\nI'm using 3.4, but it always had this issue even in other versions \n\nDescription:\nIf you are working in the geometry nodes editor and enter in edit mode on that object or another object. if you try undoing [ctrl z] it will take you back to the state the node tree was in when you changed modes, after pressing undo [ctrl z] the amount of times as actions you did since you changed modes.\n\nthis is a long standing problem and I never remember it ever working properly. \n\n[2022-08-17 20-08-42.mp4](2022-08-17_20-08-42.mp4)", "Undo doesn't consider changes in nodetree when object is in edit and texture paint mode\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.79-3.4\n\nFor reference: this is due to this commit 4a08b974f4\nFrom the commit message:\n\"don't store undo steps for property changes in paint & edit modes.\"\n\nWhen in edit and texture paint mode, I can't undo changes, that I made in the shader editor. \n\n\n - Open .blend\n - Move some verts.\n - Change a shader node setting.\n - Press {key Ctrl Z}.\n # The verts move back, but the node setting remains.\n[#71895-undo-not-undoing-shader-nodes.blend](T71895-undo-not-undoing-shader-nodes.blend)", "Shader editor: no Undo in Edit mode or Texture Paint mode\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.1\n\nBroken: 3.0.1, version: 3.3.0 Alpha\n\nIn Edit or Texture Paint mode, undo does not work in the Shader editor. Sometimes, undo stops having any effect on the nodes, sometimes it just takes multiple undos to undo a single change (no reproducible example for that at the moment). I'm using global undo.\n\nIn the default scene,\n- enter edit mode\n- open a shader editor\n- select the Principled BSDF node and either\n - Alt-drag to disconnect it from the Material Output node \n - or add a label to the node\n - or add a brick texture node and connect it to the Principled BSDF color input\n - or deleting the Principled BSDF\n- 4x Ctrl-Z takes you out of edit mode (2x undo in case of the changed label) but does not reconnect the Principled BSDF to the Material output (if you are in Object mode, pressing once will reconnect the nodes) or return the label to its prior state\n\nIn Texture Paint mode, undo will not take you back to object mode.", " \"undo\" and \"redo\" do not work\nOperating system: Arch Linux\nGraphics card: Nvidia 3070Ti\n\nDescription:\nSometimes \"undo\" and \"redo\" do not work. I haven't noticed any pattern to the error. This happens when I work with anything, such as a mash. I do something, press Ctrl+z, then Ctrl+Shift+z and \"redo\" does not work. Even though I'm doing everything right.\n\nAlso, very often when working with materials I press Ctrl+z and \"undo\" does not work. Sometimes it is necessary to press Ctrl+z several times, and it cancels only one action.\n\nSometimes, when working with materials, I press Ctrl+z and instead of materials starts undoing the actions I did with the mesh.\n\nI specify that I am not a beginner and I do all the actions correctly.\n\nAdditional info:\nThe problem occurs in all versions I have tried since 2.8.", "Editing a curve node in edit mode breaks undos\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 516.59\n\nBroken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash: `a2d59b2dac\n\nIf a \"curve\" node is edited while the viewport is on edit mode, undos don't do anything until edit mode is left.\n\n- Go in edit mode\n- Modify a curve node in any way (RGB Curve, Float Curve and Vector Curve node all share this issue), this is shown in the undo history as \"Unknown action\"\n- Without leaving edit mode, press the undo button (or Ctrl+Z)\n\nNow, undo won't do anything until you reach the point where you switched to edit mode (anything past that can't be undone), and moving through the undo history won't work at all. Going out of edit mode fixes this. \n\nEditing the curve in object mode doesn't break undos, but it still is shown as \"Unknown action\" in the undo history.\n\nTested in old versions up to 2.8 (I don't know how to access shader nodes in 2.7 and before), couldn't find a single version that didn't have this bug.", "Undo not working in the shader editor when in Edit Mode\nOperating system: Linux-6.2.0-20-generic-x86_64-with-glibc2.37 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 525.105.17\n\nBroken: version: 3.5.1\n\nWhen in Edit mode, the undo function does not work in the Shader Editor. I can see the undos happening in the undo history list, but they are not reflected in the Shader Editor \n\n- Have a material open in the Shader Editor\n- Set viewport to Edit Mode,\n- Make some changes in the shader editor\n- Try and undo those changes. \n- The undos aren't occuring in the shader editor, despite the undos happening in the undo history\n\n", "Undo after removing a node in Edit mode doesn't get it back\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.59\n\nBroken: version: 3.3.0\n\nIn [object_mode.blend](object_mode.blend) remove the Mix node with X or Delete key, CTRL+Z to undo -> Mix node gets back\nIn [edit_mode.blend](edit_mode.blend) do the same -> Mix node doesn't get back. Btw. if you repeat undo 3x times, cube switches back to Object mode\n\n", "Undo doesn't work properly in Node Editor\nOperating system: Windows 7\nGraphics card: 'GeForce GTX 1050 Ti/PCIe/SSE2'\n```\n \t 'NVIDIA Corporation'\n '4.5.0 NVIDIA 384.94'\n```\n\nversion: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f54494e, type: \nbuild date: 2019-07-29, 09:41 AM\n\n\nMaking a cut and undoing works fine.\n\nBut any of steps below results in problems with undo:\nMake a cut and move a node requires 3 undo's.\nMake a cut and move a node and move a node again requires 5 undo's. One more move and it requires 7 undos. \nIf I make a cut and move a node 9 times it takes 19 times to undo.\n\nUsing a group node : Cutting a link and undoing in Edit Mode doesn't work at all. \n\n\n- Default Cube : Click use Nodes.\n- Try any of the steps described above\n\n[Node Editor Undo Cube.blend](Node_Editor_Undo_Cube.blend)\n\n[Node Editor Undo on Group Node.blend](Node_Editor_Undo_on_Group_Node.blend)" ]

[ "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", "Accessed thru Parsec software, with left hand mouse, some operations need a right click instead of a left click to confirm\nOperating system: ?\nGraphics card: ?\n\nBroken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: edc1a09966a7, type: release\nbuild date: 2023-07-16, 23:35:12\n\n\n\nI m using parsec to acces to my workstation, but through parsec I have issues,\n\nI m left hand so my left click is a right one. I notice some operations needs a right click instead of a left click to confirm. For validating a scale I need to right click, for validating a rotation too.\nfor grab it's ok.\n\n\n- Access Blender through Parsec\n- I'mm a left hand guy I set my mouse with the master click as the right button instead of the left one, \nso everything should work with a right click instead of a left one...\n- Select an object with right click and grab, and can confirm grabbing with right click.\n- Repeat for Rotate/Scale, but have to confirm with left click.\n\n", "Unable to select multiple Grease Pencil layers with Python\nOperating system:\nGraphics card:\n\nBroken: 3.4\nWorked: \n\nSetting the Grease Pencil Layer property \"select\" with Python doesn't seem to work. Tried various update tags with no luck. Similar layer properties, such as the booleans \"lock\" and \"hide\", work as expected with the same code as below.\n\n[select_bug.blend](select_bug.blend)\nOpen Blender from a console/terminal and keep that window in view, open the attached .blend, click the play button in the Text Editor header to run the example script (which sets all layers' select property to True), then hover the mouse cursor over the Python console and press Enter to run the command: print([gpl for gpl in bpy.context.object.data.layers if gpl.select])", "Cannot sculpt under masked geometry 2.92\nOperating system: windows 10\nGraphics card: nvidia 1050ti\n\nBroken: 2.92.0, also 5ec6c8d267\n\nWorked: (optional)\n2.83.12lts\n\nLast report on the same issue #80980 (Cannot sculpt behind Hidden geometry)\nCannot sculpt under maked geometry. I reported this bug in a previous version and it was fixed. the bug is now back.\n\n| ||\n| -- | -- |\n\n- Add a UV sphere.\n- Assign some vertices to a vertex group, \"del\".\n- Add mask modifier, mode = vertex group, select \"del\", check \"invert\"\n- Go to sculpt mode, notice the vertices highlighted under the brush or the geometry modified while sculpting. In 2.83.12, they're on the back side of the hole. In 3.0, they're part of the \"del\" group.\n\n\n\n\n", "Blender 2.8 UI designs (parent task)\nThis is a parent task for all the confirmed UI tasks for Blender 2.8. We are targeting these changes for Blender 2.80. Other UI and tools updates can be added for future releases.\n\nThis list serves as a reference for developers, and is especially important for after the Code Quest has ended. These items are grouped by topic here:\n\n### Tools\n - #55036 Tool System Todo\n - #54858 Command Settings Cleanup\n - #55043 Tool Settings Editor\n - #54885 2.8 UI Tools: Toolbar Ordering\n - #54582 2.8 UI Tools: Tools Design\n - #55039 2.8 UI Tools: Tool Tweaking UI\n - #55027 2.8 UI Tools: Favourites Bar / Specials Menu Design\n - #54950 3D Cursor Design\n - #55386 2.8 UI Tools: Top Bar, Tool Properties & Toolbar Update\n - #54661 Tools Manipulators design\n\n### Asset Manager\n - #54642 Asset Manager UI\n\n### Keymaps\n - (Todo) Input Device-Agnostic Keymap\n - #55162 Blender Default Keymap Changes\n - #54963 Industry Compatible Keymap\n\n### Viewport\n - #54723 Viewport Manipulator Design\n - #54908 Workbench & Shading UI design\n\n### Addons\n - #55407 2.8: Addons UI\n\n### Outliner & Collections\n - #54707 Outliner Collections Interaction Design\n\n### Status Bar\n - #54861 Status Bar Design\n\n### Properties Editor\n - #54951 Properties Editor Design\n - #54862 Multi-Object Properties Editing\n\n### Top Bar & Workspaces\n - (Todo) Workspaces & Mode design\n\n### Default User Experience\n - #54943 Blender 2.8 Defaults\n - #54943 Default Theme\n\n### Other\n - #55353 Multi-Object Edit Mode/Pose Mode/Sculpt Mode UI\n - #54989 FaceMaps Phase 1: bone selection & bone display", "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", "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: Set Pivot to Mask Border doesn't work with the initial mask generated by the Box/Lasso mask tools\nWin 10\n\nBroken: blender-2.81-382e7ce9ecfb-windows64\nWorked: ?\n\nThe Set Pivot to Mask Border function doesn't work with the initial mask generated by the Box/Lasso mask tools.\n\nLaunch Blender\nOpen the Sculpting template (File ➞ New ➞ Sculpting)\nChoose the Box or Lasso mask tool\nMask a part of the mesh\nSelect one of the Transform tools (just to see the pivot)\nRun the Set Pivot to Mask Border (Sculpt menu ➞ Set Pivot ➞ Pivot to Mask Border)\n*And nothing happens* \n\n[2019-10-18_18-09-13.mp4](2019-10-18_18-09-13.mp4)\n\n**Note**, if I \"blur\" the mask **(Mask menu ➞ Smooth Mask)** then the \"Pivot to Mask Border\" will start working.\n\nAlso, masks generated with the regular mask brush don't have this problem...", "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.", "Grease Pencil Arrange Stroke operator does not function with Curve Editing\nOperating system: Linux 64-bit\nGraphics card: GTX 1080 ti\n\n2.93.5 and 3.0.0 alpha\n\nIn edit mode, \"Arrange Stroke\" operator does not work when use_curve_edit is enabled.\n\n[GP_arrange_bug.blend](GP_arrange_bug.blend)\n\n - Open attached file\n - Use any of the Arrange Stroke operators on the selected stroke\n # Disable Curve Editing and try again to see that it otherwise works as intended\n\n", "Grease Pencil - A corrupt Sculpt > Push brush is created when undoing a mode change\nOperating system: Darwin-19.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 2.90.0 Alpha\n\nA corrupt Push brush is created when I undo a Draw -> Sculpt mode change.\n\n* File > New > 2D animation\n* Change from draw to sculpt mode\n\n* Edit > Undo (the mode changes back to draw mode)\n* Change again to sculpt mode as before\n* A new corrupt Push brush has appeared called F Push (instead of F Push Stroke), and is selected. It has no thumbnail. It is missing the usual UI elements of the Push brush, like strength. See screenshot.\n \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)", "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", "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?", "Grease Pencil Shear Tool Todo\n## Grease Pencil Shear Tool Todo\n * - [x] {icon circle color=red} The tool should execute on release, so when you click and drag, it stops. Currently you need to click an extra time, which is inconsistent and annoying.\n * - [ ] {icon circle color=green} Add Tool Setting to switch between horizontal and vertical shearing\n * - [ ] {icon circle color=green} Shear should have a manipulator to shear in any direction, the orientation on which is controlled by the Orientation setting, just like the Transform manipulators. Dragging any of the handles shears in that direction." ]

[ "Grease Pencil default interaction overrides Left click mouse select\nWindows x64, i7 4930k, Titan X graphic card\n\nBroken: 2.8 alpha 9b817bc1689\nWorked: Branch greasepencil-object 2.8.5 ebadf391e33 (June 2018 from graphicall)\n\nIf the user has \"left click\" as selection method, using GreasePencil tools will not allow manipulation (edit, sculpt). Default grease pencil manipulation doesn´t obey the \"left click\" selection from the user preferences menu.\n\n1. Open Blender. Go to edit - User preferences. \n2. Go to Input - Select with - Left click select\n3. Go to a 3D view. Shift+A: Add a grease pencil monkey\n4. Enter Draw mode. Then switch to sculpt (sculpt strokes)\n- Information palette announces that you can manipulate the tool with right mouse (which is selection by blender default)\n5. If you try to sculpt with LEFT mouse click (user preferences) it will not work.\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)", "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", "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", "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", "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", "Geometry Nodes: simulation crashes when \"Cache\" option is disabled\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14802 Core Profile Context 21.40.64.06 30.0.14064.6002\n\nBroken: version: 4.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\n\nDisabled \"Cache\" option causes a crash when jumping back to start frame.\n\nAdd a simulation zone, output the geometry result.\n\nGo to the Physics tab and disable the __Cache__ option in the Simulation Nodes\n\nSimulation a few frames, then jump back to the start frame.\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", "Support Alembic export/import of curve objects\nI created this issue as requested [here ](T51195#430327).\n\nWhile the export of animated mesh objects works quite well, exporting and importing curve objects does not work as expected at the moment.\n\nWhen exporting curves there are two main options:\n- Export as curve\n- Export as mesh\n\nBoth of these are very useful. Depending on the specific setup it might not be useful to export a curve as curve but rather as mesh. Being able to export as mesh should always be an option.\n\nI created a little test file that includes a curve object with multiple animated properties and modifiers: [curve_export_test.blend](curve_export_test.blend)\nSome modifiers implicitly convert the curve into a mesh, so when the user wants to export as a curve, it should (if possible) evaluate all modifiers until the curve is converted. If it is not possible to apply only some modifiers, it should still be possible to only export the curve before any modifier is applied (next to the option to export the whole thing as a mesh).\n\nAlso, keep in mind:\n- Curves can consist of multiple splines.\n- The amount of splines per curve object can change over time.\n- The amount of points in a spline can change over time.\n- Curves and spline points have quite properties have quite a few attributes that need to be considered when exporting as curve (bevel radius, ...).\n\nIf I had to choose what to develop first, mesh or curve export of curve objects, I'd vote for mesh, as it allows for more flexibility. Additionally I imagine it to be easier to develop.", "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", "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```", "Sculpt crash in certain scenario (PBVH vert number does not match)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.76\n\nBroken: version: 2.93.6\n\nCrash upon altering the model in any way.\n\n1. Open file\n2. Use a tool/brush to alter the model.\n3. Instant Crash\n\nI have updated GPU drivers and the latest Blender version as of today, still crashes.\n\nCould not find any duplicate bugs of crashes when interacting with models, only crash on startup and others. \n\nI expect my GPU is just too trash.\n\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[Goblin.crash.txt](Goblin.crash.txt)\n\n[Goblin.blend](Goblin.blend)\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", "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", "Crash - \"Freestyle SVG Export\" addon and output path to a folder that does not exist on the disk\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 531.18\n\nBroken: version: 3.4.1\nWorked: Unknown\n\nBlender crashes when the \"Freestyle SVG Export\" addon is activated and the \"Output\" field contains an incorrect path to a folder that does not exist on the disk.\n\n\n1. In empty scene create some object, for example a default cube\n2. Enable the \"Freestyle SVG Export\" addon\n4. Enable \"Freestyle\" Layer Propertie\n3. In the \"Output\" field on the \"Output Properties\" tab, enter some invalid path to a folder that does not exist on the disk\n4. After pressing F12 \"Render Image\" blender crashes\n\nCrash will not occur when we disable \"Freestyle SVG Export\" checkbox, or if we specify the correct path to save the file.\n\nRegards.\n\n", "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 !" ]

[ "Converting edge to Curve Crash \nwindows 7 \nGeForce GTX 960\n\nand\n\nwindows 10\nGeforce GTX 970M\n\n\nBroken: 2.8 hash: 034a45c54e00 \ndate: 2018-07-19-2:02\n\n\nReport: \n\n\n**Whenever I try \"curve fom mesh/text\" Blender crash \n\nbut\n\nConverting mesh from curve/meta/surf/text/ everything works fine.**\n\n\n\n\n", "Blender 2.8 crashes when converting to Curve from Mesh\nSystem info:\n[system-info.txt](system-info.txt)\n\nHi, when converting the Mesh in the attached blend file to a Curve, Blender crashes.\n\n[Crash example.blend](Crash_example.blend)\n\nAgain tried with this version and got same result:\nversion: 2.80 (sub 20), branch: blender2.8, commit date: 2018-07-10 23:21, hash: 17bc056, type: Release\n", "Crash on Convert to Curve \nWin 7 Pro, NVIDIA GeForce GTX 680\n\n2.80 Alpha\n\nBlender Crashe when convert a edged mesh to curve\n\nConverting an object with just edges in object mode, will be crashes the Blender\nand shortcut for this command in Blender 2.79 was Alt + C but it's still not implemented in 2.80 Alpha\n", "Convert to - Curve from Mesh/Text\nOperating system and graphics card\nLinux Mint 19, GTX 1080Ti, GTX 1070\n\nBroken: \nWorked: blender-2.80-46bdbc6c78b-linux-glibc219-x86_64\n\nBlender crashes when I apply Convert to - Curve from Mesh/Text - to a curve. \n\nIn the startup scene, delete the cube, create a Mesh Circle and apply Convert to - Curve from Mesh/Text, it crashes every time.\n" ]

[ "Outliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.5, 2.90, 2.91 ce0bcd5fb\nWorked: Never (2.79 has the same problem)\n\nOutliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\n\n[T79961_repro.blend](T79961_repro.blend)\n- Open file\n- Cube should be in editmode\n- In the Outliner (should be in Data API mode):\n - navigate to Meshes > Cube > Skin Vertices > expand the dot as well\n - crash", "\"No Render\" volume of space with motion blur and GPU render\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.27\n\nBroken: version: 3.4.1\nWorked: N/A\n\nThere appears to be a volume of virtual space where objects do not render.\n\nLoad attached file. Set render frame to 110 and render the scene. Note the progress it makes as the large cube slowly vanishes with each render pass, while the smaller thin cube only partially renders. Set the frame to 50 and it renders fine. The problem starts with frame 106 and gets progressively worse for the large cube, while it seems to somewhat recover for the thin cube in later frames.\n\nThe problem does not repro with CPU rendering, and did not repro with my older graphics card way back when I first made this scene (GeForce 1080Ti). It repros with GPU rendering on both 3.4.1 and 3.1.0. It does not repro with motion blur disabled (hence the viewport render is also fine).\n[GPU Motion Blur Bug.blend](GPU_Motion_Blur_Bug.blend)\n", "Color management is broken in the Sequencer\nOperating system: Linux-5.0.21-1-MANJARO-x86_64-with-arch-Manjaro-Linux 64 Bits\nGraphics card: Mesa DRI Intel(R) Sandybridge Mobile Intel Open Source Technology Center 3.3 (Core Profile) Mesa 19.1.1\n\n\nBroken: version: 2.80 (sub 74)\nWorked: earlier build of 2.80 (hash: d62a749fcf48) and 2.79\n\nWeird things happens when changing the color management settings in the VSE:\n- wrong color display\n- make sound\n\nWith a movie strip displayed on the sequencer, changing the sequencer_colorspace_settings property in the Color Management changes the look of the image even when there is no color correction modifier on the strip. Example: using filmic log instead or sRGB will change the look which it should not.\nAlso, changing this setting does not apply the change directly, the VSE has to be refreshed.\n\nAnother issue with the color management is the change of exposure and gamma setting is way slower than it was on earlier build and it also makes the sound of the current strip/frame do some noise.\n", "Principled shader clearcoat roughness inconsistent change from 0.0177 to 0.0178.\nCPU: AMD 860K\nRAM: 8GB\nGFX: nVidia 960 GTX, 4 GB\nOS: Xubuntu 16.04\nDrivers: 375.82 from nvidia-375 (open source), installed from \"Additional Drivers\" section of settings window.\nBlender: 2.79 2017-09-11 10:43, Hash = 5bd8ac9abfa\n\nOn the left, the plane has a principled shader. It only has a clear coat on it. No SSS, diffuse is RGB 0,0,0, no sheen, and no normal/bump mapping. The \"Clearcoat Roughness\" setting is at 0.0177 (and of course displays it at 0.018 unless you click on it).\n\n\nHowever, the right plane is exactly the same, except the \"Clearcoat Roughness\" setting is at 0.0178, 0.0001 more. As you can see in the above picture, it's completely different, not just slightly different.\n\nHere is the blend file:\n[cleacoat_rough_bug.blend](cleacoat_rough_bug.blend)\n\nAny questions, I'll respond as quickly as I can.", "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", "The bridge tool fails in a situation with multiple rows of faces facing each other\nWin10 Pro 64 bit; AMD Ryzen 2700X; Nvidia GTX 1060 6GB; 32 gigs RAM\n\nBroken: hash d1be30f (buildbot build May 4).\nWorked: never\n\nIn a situation where you have multiple rows of faces that face each other across empty space (with other areas where they face away from each other). The bridge tool (even with*loop pairs* checked) is unable to give priority to the direction the normals are facing. The result of this is that instead of getting nice bridges among the multiple rows of cubes, the tool produces faces that overlap and have zero area. As hinted, the*loop pairs* checkbox in this case does not do anything and the result is the same.\n\nOpen the .blend, invoke the bridge operator (the result is the same whether or not \"loop pairs\" is selected.\n\n**blend**\n[IffyBridge.blend](IffyBridge.blend)\n\n[IffyBridge.blend](IffyBridge.blend) (updated blend)\n\nAn additional note; I submitted this issue years ago, but it was never fixed and I couldn't find my old report. If the bug is not going to be fixed, then just close this as a todo item or with a \"won't fix\" tag.\n", "Cycles: ray & shader counters\n[D4204: Ray and Shader counters for Cycles](D4204)", "Theme > Shader Editor, Sidebar > Alpha value does not work\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A3000 12GB Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 537.13\n\nBroken: version: 3.6.1\n\nIn side of the Shader editor, if you want to change the color works correctly, but if you want to change the Alpha value, is not working.\n\nGo to Preferences > Themes > Node editor > Theme space > Region Background\n\n", "Filter color 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.5.1\n\n\nHue color and color bar doesn't sinchronize\n\n1) change object in sculpt mode\n2) use colore filter\n3) option fill\n4) try to change hue color\n\n", "Cycles: Caustics don't work when volume boundary between casting and receiving surfaces\nOperating system: MacOS, Windows\nGraphics card: Apple Silicon, Nvidia RTX3090\n\nBroken: 3.5.1, 3.6 Alpha\nWorked: -\n\nWhen there is a volume boundary between a caustic casting and receiving surface, the caustics vanish. \n\nOpen the attached .blend file. There is a sun, an ocean surface, and a sea floor. There are 4 sections: \n- On the right, there is no volume and the caustics appear\n- the two middle sections contain volumes where either the top or bottom boundary of the volume is between ocean and floor, and no caustics appear\n- on the left the volume boundaries are above the ocean, and below the floor, and caustics are visible\n\n", "Mantaflow: emit smoke from particles can't inherit velocity.\nOperating system: windows 10\nGraphics card:\n\nBroken: 2.92\nWorked: 2.83\n\nEmit smoke from particles can't inherit velocity.\n[volume speed bug.blend](volume_speed_bug.blend)\n\n\n2.90.0\n\n\n2.91\n", "Resetting singular values in the Themes disables them\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: 2.93.5\n\nInstead of globally resetting the default themes, if I use the \"Reset to default\" for a color or a value, it simply puts it to black/0.0.\n[2021-10-27 14-12-52.mp4](2021-10-27_14-12-52.mp4)\n\nGo to themes and right click a color or value.\n[Based on the default startup]\n\n", "VSE Channel headers TODO\nImprovements for channel headers in general:\n- - [ ] 2-way `v2d` scroll synchronization\n- - [ ] Investigate why changing RNA property doesn't update timeline region\n- - [ ] Cleanup loading code for `SeqTimelineChannel`, looks like it could be optimized a bit more.\n- - [ ] Use better integrated drawing engine like list-views\n\nOther related tasks:\n - Decide on [D14263: VSE: Limit timeline view height](D14263)", "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", "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" ]

[ "Principle Volume in World Shader is not working\nEdit by @Alaska \nBisecting points to 6f502136c7 as the cause.\n\n---\n\n**System Information:**\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\n**Blender Version:**\nBroken: version: 2.90.0\nWorked: 2.83.4\n\n**Short description of error:**\nThe principaled volume shader is not rendered by EEVEE when it is used in the world shader.\n\n\n|||\n| -- | -- |\n|2.83|2.90|\n\n**Exact steps for others to reproduce the error:**\n1. Start a new scene and change the render engine to EEVEE.\n2. In the world shader, add a principaled volume node and attach it to the volume socket of the material output node.\n3. In 2.90, notice how the volume is not rendered by EEVEE while in 2.83 the volume is.\n\nHere's a .blend file with steps 1 and 2 done:\n[#80332 - EEVEE missing world volume shader.blend](T80332_-_EEVEE_missing_world_volume_shader.blend)", "Volumetrics not working in 2.9 eevee\nOperating system: win10\nGraphics card: Titan rtx\n\nBroken: (example: 2.90.0, edbf15d3c044, master, 2020-09-03, as found on the splash screen)\nWorked: works in 2.83.5\n\nVolumetrics through Principled volume material aren't appearing in Eevee. \n\nBased on the default startup or an attached .blend file (as simple as possible).\nHead to shader editor and switch the mode to world. Add principled volume material and plug it into world output. This should normally render volumetrics i.e fog etc, but it stays the same. Plesae refer the attached image to see the problem . \n\nThank you", "Principled volume node not working for world output volume\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.90.0\n\nSaw a tutorial by [Grant Abbitt ](g8683RF1COo?t=827) where he created a light fog effect by adding principled volume node to the world output volume. Apparently, this did not work even when the density was set to max.\n\n\n\n**Blender file**\n[test.blend](test.blend)\n\n" ]

[ "Mesh Bevel Node\nNOTE: Design outdated. See #98674 for current design and progress. It is a development task though, so please don't add comments like \"when will this be finished?\"", "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", "Fullscreen doesn't activate if the 3d Viewport is maximized \nTested on :\n\n2.73 a\n\nGooseberry 2.73 # d92f591\n\nWhen the viewport is maximized ( Ctrl + Up Arrow). Switching to 3d view fullscreen mode wont work. ( Alt+F10 nor from the view menu button ). ", "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)", "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)", "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", "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", "2.90 Not opening on Linux\nOperating system: Linux Mint 18.1\nGraphics card: Intel HD 620\n\nBroken: \nBlender 2.90 won't open up fully, it appears to open up and immediately closes\nWorked: \n\nTried a few different ways to open, won't open.\n\nOne of the methods I tried opening with was through the Terminal and this was the message I had returned back:\n\nRead prefs: /home/john/.config/blender/2.90/config/userpref.blend\nfound bundled python: /home/john/Desktop/3D Related/1BlenderVersions/blender-2.90.0-linux64/2.90/python\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nGPUShader: linking error:\nerror: Input block `ShaderStageInterface' is not an output of the previous stage\n\nWriting: /tmp/blender.crash.txt\nSegmentation fault", "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", "EEVEE & Viewport Module\nThis page is in the process of being fully replaced by #eevee_viewport.\n\n---\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- `(straightforward)` - *Task which is straightforward to implement, which don't rely on larger API changes or refactoring.* \n\n# Long Term Projects\n\nDevelopment may span multiple release cycles.\n\n- {icon circle color=yellow} #68989 ( Selection future-proof design)\n- {icon circle color=yellow} #68990 (Vulkan support)\n- {icon circle color=yellow} [D5442: LANPR line rendering (summer of code)](D5442)\n- {icon circle color=yellow} #68991 (Fisheye / panorama in EEVEE)\n- {icon circle color=yellow} #68993 (Stereo Panorama in EEVEE)\n- {icon circle color=yellow} #68994 (VR design / usability)\n- {icon circle color=yellow} #68995 (VR input integration and mapping)\n- {icon circle color=yellow} #68464 (Better Motion Blur)\n- {icon circle color=green} #68996 (OpenSubdiv GPU acceleration)\n- {icon circle color=green} #68997 (Panorama selection support in viewport)\n- {icon circle color=green} #68463 (Dynamic Indirect light cache)\n- `?` #68998 (Virtual Reality (XR/VR/AR/MR))\n\n\n# Medium Term Projects\n\nDevelopment should be possible in a single release cycle.\n- {icon circle color=red} #71347 (Virtual Reality - Milestone 1 - Scene Inspection)\n- {icon circle color=yellow} #68478 (World Light Extraction)\n- {icon circle color=yellow} #68453 (Anisotropic BSDF)\n- {icon circle color=yellow} #68456 (Shadow catchers)\n- {icon circle color=yellow} #68474 (Clustered Light Culing)\n- {icon circle color=green} #67579 (Improve NDOF navigation)\n- {icon circle color=green} #54638 (OpenGL headless rendering)\n- {icon circle color=green} #68479 (Pointiness support)\n- {icon circle color=green} #68460 (Multiscatter Glossy BSDF)\n- {icon circle color=green} #68459 (Hair BSDF)\n- {icon circle color=green} #68458 (Velvet BSDF)\n- {icon circle color=green} #68477 (Parallax Occlusion Mapping)\n- {icon circle color=green} #68468 (Depth of Field Refactor)\n- {icon circle color=green} #68472 (Light Nodetree support)\n- {icon circle color=green} #68470 (Shadow buffers)\n- {icon circle color=green} #60779 (3D Viewport clipping support)\n\n# Paper Cuts\n\nSmall improvements and polish.\n\n- {icon circle color=green} #64281 (Option to lasso-select using geometry instead of object centers.)\n- {icon circle color=green} #69282 (Ability to cancel viewport operations (rotate/pan/zoom))\n- {icon circle color=green} #68206 (Lag reading viewport depth buffer in LookDev mode)\n- {icon circle color=green} #70803 (Support Viewport roll - around the cursor position) `(straightforward)`\n- {icon circle color=green} #73214 (Armature Object's \"Display As\" does nothing)\n- {icon circle color=green} #73732 (Grid-lines vanish in perspective view, when viewed from the side)\n", "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", "(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", "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", "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", "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 with the node editor\nWin7\nIntel(R) Core(TM)2 Duo CPU\nE8400 @ 3.00 GHz 3.00 GHz\nRAM 2,00 GB 32 Bit\nGraphic card Intel(R) Q45/Q43 Express Chipset\n\n(no other computer for testing available, the crash is reproducible)\n\n\nBlender 2.75a c27589e\n\nNode-editor. Insert a mix shader direct in the existing line. \nThat's it.\n\nNode editor, shift A, select Shader->mix Shader, drop it on the line.\n(Blender crashes even when using the \"Add Shader\".)\n\nThe reduced file:\n[Bug-Report2.blend](Bug-Report2.blend)" ]

[ "Regression: Boolean Modifier Distorts UVs\nBroken: Blender 3.2.2 Official\nBroken: 2.93\nWorked: 2.92\n\nBroke with a3f091d7ce\n\n\nBoolean modifier distorts UVs of cutter object. In the attached screenshot and blend file. There are two cutters objects of roughly the same shape, one of them works correctly and the other doesn't.\n\n\n\n[tmp_2.blend](tmp_2.blend)", "Line art modifier clips with object on (MBP 16\")\nOperating system: macOS Big Sur\nGraphics card: 5500M \n\nBroken: 2.93.0 LTS\nWorked: -\n\nLine art modifier (grease pencil) seems to clip into / z-fighting the object. \n\n\nJust add a new line art modifier, possibly a mac problem?\n\nTest File:\n[line_sample.blend](line_sample.blend)", "Annotation tool in Image Editor does not switched off when mode is changed\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86\n\nBroken: version:\n- 2.93.0 Alpha\n- 2.91.2\n- 2.90.1\n- 2.83.10\n- 2.81a\n- 2.80\nWorked: Never\n\n\nWhen annotation tool is selected in View Mode, and then changed to the Paint Mode,\nthe annotation tool remains \"ON\" even if Draw tool is active in Paint Mode. \n\n\n\nI uploaded a snapshot.\nThe active tool is Draw tool, as shown in tool panel.\nBut the annotation line is drawn when the mouse is dragged.\n\n- Open the Image Editor and create a new image.\n- Switch to *Paint* mode in the *Image Editor* and select the *Draw* tool.\n- Switch to *View* mode in the *Image Editor* and select the *Annotation* tool.\n- Switch to *Paint* mode and notice that the *Draw* tool is indicated as active tool in the toolbar\n# Try to use the *Draw* tool.\nAn annotation line is drawn instead of a brush stroke with the *Draw* tool. It only starts to work once the tool is reselected in the toolbar.", "With enabled Modifier On Cage option crashes on entering Edit Mode if in Render Viewport Shading\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 522.30\n\nBroken: version: 3.3.0\n\nIn Eevee, in Render Viewport Shading, an object having a Geometry Nodes modifier with enabled On Cage Modifier Result, that affects a UV Attribute which is used in Shader, crashes upon entering Edit Mode.\n\n - Set Viewport Shading Mode to Render\n - Enter Edit Mode ->Crash\n[displace-preview.blend](displace-preview.blend)", "Paint Mode: Alpha Auto-Masking\nNOTE: This design still needs to be further discussed and decided upon.\n\n# Goal\n\nThe very common brush setting in Blender to \"Affect Alpha\" should be revamped for the upcoming Paint Mode.\nThe main issue with the setting is that it is local to the brush. But in typical painting workflows you'd expect to have this be a more universal toggle that affects all tools!\nToggling this per brush is not a reasonable solution.\n\nThere are multiple approaches to fix this.\n\n## Proposal: Alpha Auto-Masking\n\nThere is already a design in place for sculpt and paint mode. There we use auto-masking to easily target specific areas as a mode setting.\nThese are meant to be instantly accessible with a pie menu on `Alt + A` and would affect all tools and brushes.\nThis would likely be the most intuitive and fastest option.\n\n## Image Editor Inclusion\n\nIf we decide to replace the brush option with an auto-masking option this puts further pressure on implementing the same options for the image editor.\nThis might be reason enough to lower the priority for now, until the image editor can be properly prioritised to mirror the 3D viewport paint mode features.\n\n## Long Term Alternative\n\nOther image painting applications such as Krita implemented this as a toggle for any individual layer to paint on.\nWhile this is not likely to implement this way right now, it could be kept in mind for the UI of the [layered textures design]().", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "mask visibility in sculpt mode using shape keys or generative modifiers\nOperating system: Windows 10\nGraphics card: nvidia 1060 Ti\n\n2.8 RC2\n\nIf you have a mesh with a mask and create a shape key, the mask will be no longer visible, still active but not visible.\n\n\n- Add UV Sphere\n- Sculpt mode\n- Paint a mask\n- Create shape keys\n\n\nOr from the default startup:\n- in sculptmode, `Mask` > `Invert Mask` (default cube should turn dark)\n- strokes dont have an effect now (this is expected)\n- add **any** generative modifier to the default cube (e.g. triangulate)\n- back in objectmode, save the file\n- reload the file\n- enter sculptmode\n- no mask is visible\n- strokes dont have an effect now (this is confusing since you are not aware masks prevent an effect since you dont even see the masks)\n\n(note we have the option `Use Deform Only` in sculptmode which might be exactly for that purpose, still not being able to use masks with generative modifiers should be more clear)", "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", "Generated texture coordinates missing when switching from solid to rendered mode\nOperating system: Windows 10 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.80.0-git.14884cda1ff5-windows64\nWorked: 2.79b f4dc9f9d68b\n\nThe \"Generated\" texture coordinates make textures \"stick\" to the surface, even if the object is being deformed.\nHowever, this does not work as expected in 2.80 with the Armature Modifier, neither in Eevee nor Cycles.\nIn 2.79 in works correctly.\n\nPossibly related: #59275.\nHowever, this bug affects both Cycles and Eevee, while that report only concerns Eevee (and Cycles works correctly).\nThe difference is that here an Armature is used, while that report uses Shape Keys.\n\n[generated.blend](generated.blend)\nThe scene contains a cube with an armature modifier.\n- Open in both 2.79 and 2.80.\n- Press F12 to render.\n- See how the texture mapping differs.", "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 eliminates brush texture\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\nI think it shouldn`t be undoable as other brush settings now.\nIt is much easier to delete texture manually, than restore it and tune it again.\n\n[2021-05-26_14-00-22.mp4](2021-05-26_14-00-22.mp4)\n\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", "Texture paint undo sometimes changes texture slot\nOperating system: Windows 10\nGraphics card: GTX 1060\n\nBroken: 2.80 (sub 48), 2019-03-12 13:53, hash: 936014ea8c74\n\nWhen texture painting on a particular texture slot, then undoing that painting, sometimes the selected paint slot will change.\n\nI couldn't reproduce from the default startup file, so I've stripped down the file that's having problems as much as I can.\n\n1. Open attached file\n2. Select paint slot \"Skin mask\" from either topbar or properties panel.\n3. Paint some strokes on the model or image editor\n4. Press Ctrl-Z\n5. Notice the paint slot is no longer set to \"Skin mask\"\n\n- - -\n\n- Change to the Skin Mask slot.\n- Paint a single stroke in the image editor.\n- Undo two times.\n- Paint another single stroke in the image editor.\n- Undo one time.\n- Notice that the slot changed.\n[texturepaintbug.blend](texturepaintbug.blend)", "Lag on moving mesh elements in edit mode with skin modifier\nOperating system: Windows 11\nGraphics card: NVIDIA GeForce RTX 2060\n\nBroken: 3.4.0\nWorked: nothing\n\nIn edit mode if object has a skin modifier and visibility of modifier is set for edit mode, a performance drop is seen on moving mesh elements in edit mode\n\n- Open attached file\n- Switch to edit mode\n- Select all vertices and move them\n[untitled.blend](untitled.blend)", "Edit mode. Wire become non-selectable dependent on resolution (regression)\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 75)\nWorked: 2.79\n\n\nWithout multisampling wire just disappear and with multisampling it is still visible but not selectable.\n\n[2019-09-14_23-07-53.mp4](2019-09-14_23-07-53.mp4)\n[2019-09-14_23-09-58.mp4](2019-09-14_23-09-58.mp4)\n\n\n\nTry to select loop and zoom in-out with and without viewport multisampling. Here the file, but bug will appear even with UV-sphere.\n[b.blend](b.blend)\n\n" ]

[ "Missing UV Islands / Image Editor / Some generative modifiers (bevel, skin, triangulate, wireframe)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Quadro M2200/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIf geometry has the Bevel Modifier applied and the Realtime Display is on, the UV islands do no display in the Image Editor.\nIf you turn off the Realtime display (Display in Viewport) and then adjust the view in the Image Editor, the UV Islands will appear.\nIf you turn On the Realtime display and then adjust the view in the Image Editor, the UV Islands will vanish.\nYou can still paint in the Texture paint on the geometry and it will appear in the Image Editor.\n\nCreate a Cube\nAssign a Bevel Modifier - turn Realtime display ON (for me it is on by default)\nSet interface to Texture Paint mode.\nThere will by no UV Islands displayed in the Image editor\n\n[UV_Island_Bevel.blend](UV_Island_Bevel.blend)\n\n\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", "Mesh to Volume crash on small geometry\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 3.4.1\n\nIn some cases with small geometries, the `Mesh to Volume` node ends up consuming a lot of memory and resulting in a crash.\n\nThis was identified when running the background rendering script for the attached production file.\n\nWith the production file, on the 23rd frame (Every time), I got the crash. It does it from the command line OR from the software itself. From the command line, it shows me the information for the last frame (23), then goes into the error message. I copied it below, and the .crash.txt file is attached.\n\n```\nCurrent Frame= 23  Axon Length um=60,  n Soma Mito=15,  n Proximal Mito=3,  n MidNeurite Mito=1,  n Distal Mito=3,  Mito Avg LW Ratio=1.33,  Mito Size=0.36,\nError   : UNKNOWN EXCEPTION\nAddress : 0x00007FFF45F2FE7C\nModule  : KERNELBASE.dll\nThread  : 00003638\nWriting: C:\\Users\\Owner\\AppData\\Local\\Temp\\NeuroMito 823 03b.crash.txt\n```\n\n- Open attached file [mesh_to_volume_crash.blend](https://projects.blender.orgattachment)\n- Reduce the size of primitive geometry to `0.8`\n\n---\n**Steps for the production file**\nThe .Blend file refers to the attached .CSV file. To run it, you just have to change the folder in the script to wherever you saved the .csv file. I used this command to run it from command line, or just run the script to start the rendering.\n\n\"c:\\Program Files\\Blender Foundation\\Blender 3.4\\blender.exe\" -b \"S:\\Phys\\NeuroMito 823 03b.blend\" --python-exit-code 1 --python-text \"Render01\"\n\nThank you as always for your work on this amazing program. I am sure it is something about the way I am using geometry nodes or scripting that is causing this.\n\n", "Unexpected behavior when applying Geometry Nodes modifier on top of the Multires.\nThis is a more comprehensive report on a bug that was recently posted and closed [HERE ](T97603)\n\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84\n\nBroken: version: 3.0.1+\n\nApplying Geometry Nodes on top of the Multires modifier does not give expected results. Multires is an exception from the \"Applying a modifier will apply it as if it was first in the stack\" rule, when a modifier is applied on top of the Multires, the mesh changes will be applied to the currently visible subdivision level. Quick video below.\n[Multires GNodes Bug.mp4](Multires_GNodes_Bug.mp4)\nAnd the Example .blend file > [Multires GN Bug.blend](Multires_GN_Bug.blend)\n\nHow should applying the Geometry Nodes behave ? When the Geometry Nodes modifier doesn't change the vertex count and simply deforms the mesh, it should behave just like any other modifier, see example video with the Shrinkwrap modifier. \nSo what when Geometry Nodes does change the vertex count ? I say we keep the same behavior that solidify modifier has, it skips Multires and applies it as it would be first in the stack. While of course this will bring broken results, this is a already an existing behavior so i think it would be completely fine.\n\nSeries of images presenting how applying a Solidify modifier on top of Multires behaves. (Intended behavior)\n\n\n\n\n\n\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", "Geometry Nodes: Support materials in simulation state.\nCurrently, the simulation state in geometry nodes cannot contain materials. The main reason is that those separate IDs which are not serialized as part of simulation baking. Ideally, baking materials would just work, at least in the most common circumstances.\n\nWhile this task is about materials, the same thoughts also apply to other referenced IDs like object/collection instances.\n\nThere are two main possible solutions:\n1. Serialize materials as part of the simulation state.\n2. Only store a reference to the material in the simulation state.\n\n### 1. Serializing Materials\n\nSerializing materials has the benefit that it could just work. We'd have to store all the materials for every geometry in the simulation state in cached frame. Though, it's possible to deduplicate this to some degree of course. Serializing materials would also involve serializing the node graph and potentially even more referenced data like images. At some point we most likely want things to stay referenced, so the problem is just moved to a different place. Another problem is that the materials are essentially recreated on every frame. Blender does not really have the ability to work with materials that are not in `Main` currently.\n\n### 2. Storing References\n\nStoring a reference to the material mainly means storing a material name and an optional library name in the simulation state. Then, when loading the simulation state, the materials available in the .blend file are mapped to the loaded geometry. Conceptually, this is also very straight forward. Materials can still be edited like they always have been. A potential problem is that if materials are renamed or removed, they can not be linked correctly anymore. However, that is somewhat expected with linking already. While this approach is easy design wise, there are some technical difficulties: The main problem is that we only know which materials are used by the baked data, once the data is loaded. And, to make matters more difficult, we might only know which baked data to load once depsgraph evaluation has started. That can happen when e.g. the file path to the data on disk is dynamically build/choosen during evaluation (this is not supported right now, but likely will be at some point).\n\nThe problem with knowing which materials will be used by the geometry is that materials are part of the dependency graph. As such, all materials we wish to use for rendering have to be added to the dependency graph *before* evaluation starts. As of right now, it's not possible to lazily add materials to the depsgraph once it becomes known that it is required.\n\nThere are a couple different possible solutions with different trade-offs:\n* A. Always add all materials to the depsgraph. This would be a simple solution, but it's obviously not scalable. Even less so if we wish to use the same solution for other kinds of referenced data like objects.\n* B. Only support linking baked data with materials that are referenced by material slots on the object or original geometry. This means that if the simulation state happens to contain materials used by e.g. other imported objects, those will not be linked correctly.\n* C. Detect all materials \"reachable\" from an object and always add those to the depsgraph. This might have noticeable overhead when potentially large parts of `Main` have to by scanned by many objects. It also wouldn't work in all cases. For example, if the simulation has been baked, and then the .blend file changes in ways that the material is not reachable from the object anymore. Then the material would not be linked correctly.\n* D. Store a name-to-material mapping on the modifier. This mapping could be created/updated automatically when baking or at other points in time. Only materials in this mapping can be linked when loading simulation state. If the simulation state contains a material name that is not in the list, we could show a warning and automatically add it to the list with the press of a button in many cases. With this approach, the user also has the ability to replace a material after baking easily. The mapping could also have per simulation zone overrides for more control.\n\n-----\n\nCurrently, my preferred solution is referencing the materials by name in the simulation state and use option D to do the linking at evaluation time.\n\n", "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)", "Add modifier error message for attribute name clashes\nIf user has a UV and a vertex color groups with the same name things behave in non predictable ways.\n\nThe nodes modifier should check for this and add an error message when this happens.", "bump node ignores height input (with certain inouts used as mapping vectors in the tree, seems to require `SOCKET_OUT_POINT`as opposed to `SOCKET_OUT_NORMAL`)\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\n\n\nbump node does not react to data.\n\n[bump bug.blend](bump_bug.blend)\n\n\n\n\n\n\n\n\nFor Cylces, the following seem to be the working inputs (the ones that trigger the availability of requirements for the bump node):\n- Geometry node\n - Position\n - Parametric\n - all others dont trigger the requirements (derrivatives?)\n- Texture Coordinate node\n - Generated\n - UV\n - Object\n - Camera\n - Window\n - all others dont trigger the requirements (derrivatives?)", "Alembic is exporting objects with geometry nodes as empty objects.\nOperating system: Windows 10\nGraphics card: 2070\n\nBroken: blender-3.0.0-alpha+master.b73dc36859e0-windows.amd64-release\n\n\n\nAlembic export does not seem to understand objects with the geometry nodes modifier properly. The resulting .abc file does not seem to contain the intended object when imported back. Basically it is not evaluating the mesh during export.\n\n\n\n\n- Open the attached .blend\n\n- Select the \"GeometryNode\" objects from the outliner.\n\n- Open File/Export/Alembic \n\n- Make sure you only have \"Selected Objects\" selected in the options so it only exports the selected objects.\n\n- Bear in mind we are only exporting the object with the geometry nodes mod, the resulting import should be a single combined mesh\n\n- Export it\n\n- Import the .alembic file back\n\n- You should have an empty \"GeometryNode.001\" shell object. If the resulting import has more multiple objects then you exported other objects in the scene too, which goes against the basic premise of this test.\n\n[_04072021_1929_51.blend](_04072021_1929_51.blend)\n\n\n\n\n\n", "Mesh Bevel Node\nNOTE: Design outdated. See #98674 for current design and progress. It is a development task though, so please don't add comments like \"when will this be finished?\"", "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", "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", "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)", "Geometry Nodes/Curve to Mesh: BLI_ASSERT_UNIT_V3 failure for curve normals in `math_rotation.cc#rotate_direction_around_axis` when using Minimum Twist \nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\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: 3.5.0 Alpha, branch: master, commit date: 2022-12-14, hash: `rBUnknown`\nWorked:?\n\nWhile debugging and testing changes in `curve_to_mesh_convert.cc`, I came across a `BLI_ASSERT_UNIT_V3` failure for curve normals in `math_rotation.cc#rotate_direction_around_axis`.\n\n```\nRead blend: /tmp/rotate_direction_around_axis_normalize_bug.blend\nBLI_assert failed: source/blender/blenlib/intern/math_rotation.cc:16, rotate_direction_around_axis(), at '!(fabsf(_test_unit - 1.0f) >= 0.0002f) || !(fabsf(_test_unit) >= 0.0002f)'\nAbort trap: 6\n```\n\n`rotate_direction_around_axis` is called from `CurvesGeometry::evaluated_normals()... curves::poly::calculate_normals_minimum()` when using `Minimum Twist` (no assert failure in `Z-up` mode). No apparent negative effect when tested with non debug release. It seems to be due to the fact that `curve_geometry.cc#rotate_direction_around_axis()` does not normalize its returned value. It happens on a fairly big curve with ~200k control points that I created to test curve_to_mesh performance. \n\nFull backtrace:\n[rotate_direction_around_axis_normal_assertion_failure.txt](rotate_direction_around_axis_normal_assertion_failure.txt)\n\n**How to reproduce:**\nStart Blender (compiled in debug mode) from command line to see standard output, open the test file and switch the Set Curve Normal to \"Minimum Twist\". `BLI_assert` message should appear on the standard output.\n\ntest file:\n[rotate_direction_around_axis_normalize_bug.blend](rotate_direction_around_axis_normalize_bug.blend)\n\n**Suggested change:**\n\nNormalize the result of `rotate_direction_around_axis`:\n\n```\nlang=diff\ndiff --git a/source/blender/blenlib/intern/math_rotation.cc b/source/blender/blenlib/intern/math_rotation.cc\nindex 454862c8d18..92eb7832eb8 100644\n--- a/source/blender/blenlib/intern/math_rotation.cc\n+++ b/source/blender/blenlib/intern/math_rotation.cc\n@@ -20,7 +20,7 @@ float3 rotate_direction_around_axis(const float3 &direction, const float3 &axis,\n const float3 diff = direction - axis_scaled;\n const float3 cross = math::cross(axis, diff);\n \n- return axis_scaled + diff * std::cos(angle) + cross * std::sin(angle);\n+ return math::normalize(axis_scaled + diff * std::cos(angle) + cross * std::sin(angle));\n }\n \n float3 rotate_around_axis(const float3 &vector,\n```\n", "Simulation Nodes Reset Behavior\nCurrently, the simulation range for geometry nodes is the scene range. So whenever the cache becomes invalid and we go back to frame 1 (or whatever the scene range start is), the cache is reset. \n\nNow, we want to add support for giving individual simulations separate frame ranges. Those might not match the scene range anymore. The simulation start might be before the scene start frame to support preroll (potentially even at a negative frame). Therefore, using the scene start frame as the reset point, does not make sense anymore.\n\nThe new behavior should/could work like this:\n* Invalidated simulations reset whenever the current frame is at or before the simulation start frame.\n* There is a new \"Play with Preroll\" button in the timeline that starts playback at the first simulation start frame in the scene. \n * Since this frame is at or before all simulation start frames, all invalidated simulations are reset.\n\nOpen Questions:\n * Are all or only invalidated simulations taken into account when determining the first frame for the \"Play with Preroll\" operator.\n * Where to put the new \"Play with Preroll\" button exactly, what should it be called and what should it look like?\n\n" ]

[ "Geometry nodes crash\nOperating system: Windows 10\nGraphics card: nVidia 2060\n\n3.0.0 Alpha\n\nThe error occurs with a couple of simple steps.\n\nCreate a Geometry node layout on the default cube. **Input > Line > Output**\nIf you disconnect the Line node, then reconnect to the Lines *Count* input. Blender will close.\n" ]

[ "Black render artifact with CPU+GPU rendering in viewport\nWindows 7 Pro\nNvidia Quadro P6000\nIntel Xeon E5-2690 v4\n\nBroken: daily builds 2.79 since at least 25.10.2017.\nWorked: -\n\nIf I enable combined CPU+GPU rendering, a black rectangle shows up on one of my objects. It shows up in viewport rendering, and also in the final render. This seems to be independent of the material used. I have provided a stripped down version of the scene where it is still visible. This time only in the viewport, the final render works for this simplified scene. \n\nThe artifact seems to be \"locked in space\", I can move or rotate the object away, so that it disappears. In some rotation angles it is not a black rectangle, but dense black lines. \nWhat is also interesting is that the surface of the object in not only black, but partly transparent. I have put a lamp and a cube inside the object in the demo scene, these should not be visible from outside, but they are.\n\n- Open file. In the render settings GPU compute should be turned on, and in the user preferences CUDA should have both the CPU and GPU selected.\n- Turn on viewport rendering. --> black box visible.\n- Then switch to CPU rendering. No more black box.\n\n[black_artifact_bug3.blend](black_artifact_bug3.blend)\n\n", "Regression: Extrude Tool XYZ Handles overlap on orthographic view and small world scale\nOperating system: Linux-5.15.0-43-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro GP100/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.85.02\n\nBroken: version: 3.4.0, 3.3 , 3.2\nWorked: 3.1\nCaused by 5045968f24\n\nThis bug might be related to #99670.\nWhen using the Extrude Tool, the handle type can be changed to show XYZ axes. When the object is way smaller than 1 Blender Unit, it becomes impossible to grab the Y and X handles in orthographic view.\n\n- Scale down the cube to 0.01 percent\n- Enter edit mode\n- Make the Extrude Tool active and switch the tool settings to XYZ\n- Try dragging the Z or Y handles\n\nFirst 3 steps are included in file\n[#100321.blend](T100321.blend)", "Render Artifacts with SSS + Motion Blur + Use Spacial Splits\nWhen you have the \"perfect storm\" of Subsurface Scattering, Motion Blur, and \"Use Spacial Splits\" (Render>Performance) all applied to an animated mesh, the rendered image will exhibit some pretty severe artifacts and mesh cracking on certain frames of an animation.\n\nThe main issue appears to be related to \"Use Spacial Splits\"\n\nOpen the attached zip - watch the comparison video. Open the .blend file, hit F12 to render (frame 34 is a good example)[Spacial Splits +Motion Blur Artifact Bug.zip](Spacial_Splits__Motion_Blur_Artifact_Bug.zip)\n\n[Render Bug - Spacial Splits + Motion Blur + Sss-1.m4v](Render_Bug_-_Spacial_Splits___Motion_Blur___Sss-1.m4v)", "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)", "Redo causes pointy mesh artifacts in Multires\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.90 (sub 0)\n\nIn the new multires, if I sculpt on a level, then subdivide, sculpt on that layer again, then undo to the base level and redo back to the higher levels, it creates a pointy mess in the place of where I'd sculpted.\n[bad undo redo multires.blend](bad_undo_redo_multires.blend)\n[2020-05-02 01-39-06.mp4](2020-05-02_01-39-06.mp4)\n1. Remove default cube, add UV sphere. Go to sculpting workspace. \n2. Add a multires modifier and create a few subdivision levels.\n3. Sculpt on those levels and undo back to the lowest level.\n4. Redo back to the higher levels. Some of those steps would have pointy shapes.\n", "Improved way to display weight painting colors\nWeight group colors in vertices blend between their neighbors by going through the entire range of values between the 2 points\n\n\nFor example if a vertex has a 1.0 (red) value and one of it's neighbors has a 0.0 (blue) value, the face will show a rainbow interpolation going trough orange, yellow, green, cyan and finally blue\n\n\nIn certain situations where each of the vertices of a face have different values (like 1.0, 0.5, 0.75, 0.0) it will create weird intersections in the middle that look like there is a vertex there that doesn't exist\n\n\nThe problem is even worst when the wireframe is not displayed and we only see gradients of colors indicating vertex values that do not exist\n\n\nThe solution is to fix the color blending mode to simply **mix** between the 2 neighboring colors. This way it is very clear that vertices have values of 1.0, 0.75 and 0.5 and nothing in between.\n", "Sculpting a mesh from Blender 3.6 causes corruption\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) Arc(TM) A770 Graphics Intel 4.5.0 - Build 31.0.101.4644\n\nBroken: version: 3.6.2\nWorked: none, tested as far back as 3.3\n\nSculpting this mesh causes hilarious corruption and I don't know why. Note the huge Dimension coordinates.\n\nThis mesh was duplicated off a body mesh which also intermittently had the same issue. I've flipped between 3.5 and 3.6 a lot to edit that mesh because of #109432 (it's a furry character, I needed my rest position when working with hair systems). I'm wondering if something is corrupted in the mesh data itself. \n\nsculpt\n\n", "Denoise + Pixel Size + Render Region = Artifacts in Viewport\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: \nNVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.84, \nNVIDIA GTX 1080.\nOptix is used.\n\nBroken: version: 3.2.0 Alpha\nWorked: Don't know.\n\nWhen the pixel size for render preview is increased, (2X, or 4X), Render region is set, and viewport denoiser is turned on, the viewport render gives weird artifacts.\n\n\nTurn on render preview, and zoom in this file:\n[Pixl Size Denoise Render region.blend](Pixl_Size_Denoise_Render_region.blend)\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)", "Mesh support mirror (symmetry) on all axes\nCurrently symmetry is hard coded to X axis in many places.\n\nSymmetry on any other axis isn't possible, this task proposes to support symmetry on all 3 axis.\n\nThis impacts:\n\n- Transform\n- Weight Pain (see #65872 for why sculpt symmetry isn't appropriate).\n- Edit mode smooth.\n- Particle editing.\n- Armature/Rigging (need to look into this)\n", "Clipping Region in blender v3.2 and up is causing a werid artifact\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon RX 6600M ATI Technologies Inc. 4.5.0 Core Profile Context 22.10.1.221003\n\nBroken: version: 3.3.1\n\nweird colorful noise when using Clipping region ALT+B\n\nit happens by simply using the clipping region, it happens in both object mode and edit mode\n\n**Diagnosis that I tried** (USEFUL NOTES{[F13703419](Untitled.png)} FOR FIXING THE PROBLEM)\nwhat is causing it?: \n- I noticed that the bug is only on the Viewport Overlays it seems like it's smth related to the graphical smoothing done by \"viewport overlay smooth wires\" from blender preferences -> viewport -> Quality -> Smooth Wires. I can turn of that for Overlay and for Edit mode, but it's just hiding the problem not fixing it, also the selected objects highlight (active element and not active element) are both still showing the same artifact and I don't know how to turn off smoothing for this part.\n\nis it gpu driver problem?\n- it most likely is a conflict between blender and my gpu, I don't think it's a driver problem tho because I tried the latest two gpu drivers available from amd, and both of them are showing the same problem. I tried running blender using my integrated gpu and tried my RX6600M gpu and in both cases it happend, I don't know if the smoothing is done on the gpu level or cpu level tho so it could be not related to which gpu I use\n\nWhat versions of blender does it happen in?\n- I mainly use blender from steam with auto updates, I noticed the problem when I was using v3.3.1 then I tried few older versions by manually installing them from the offical blender website, the bug doesn't show up in v3.1.2 and v2.79b however it's in showing up in v3.2.0 and v3.3.0 and v3.3.1 -not steam version- I didn't test more versions tho\n\nP.S. my device -Legion 5- has a mux switch, when I did the bug report the mux switch is turned off which means the integrated GPU is disconnected thus it's not showing up in the bug report, however when I tried to check the bug \n\n\n\n\n\n\n\n[untitled.blend](untitled.blend)", "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", "clay strip brush (and probably any brush) create some strange shading and geometry artifacts...\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\n\nclay strip brush (and probably any brush) create some strange shading and geometry artifacts...\n\n1. open blender, subdivide the default cube in edit mode a few times,\n2. add subdiv modifier with 3 levels (25,1 million in total) and apply modifier.\n3. go to sculpt mode and start playing with the clay strip brush and brush settings a little bit...\n4. change the sculpt plane to view plane, and add a stroke continuously in the edge of the cube, and some transparent shading bug appears when i go to check the back side of the stroke made, but this get fixed when i use the smooth brush a little bit in those boundary edges...\n\n\n5. change the sculpt plane to area plane again, and try on other edge the same again, and some grid topology starts to appear suddenly in the first stroke when drawing, but when i keep drawing it was less noticeable the artifact but was still there...\n\n\n\n", "Sculpt mode transform tools. Weirdness with 3d cursor.\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007\n\nBroken: version: 2.81 (sub 11)\n\n1. In sculpt mode transform tools strange behavior with 3d cursor. Trying rotate part of the mesh, first rotation might be ok and second sometimes ok, but then rotation is going crazy. Exit to object mode then again enter sculpt mode, rotation is ok, but only for 1-2 times then again it acts weird (watch the video 1).\n\n2. Scaling in sculpt mode with 3d cursor not like in edit mode, it is very strange (watch the video 2).\n\n1. Open attached *.blend file, rotate several times, (do not cancel rotation with rmb!).\n\n2. Open attached *.blend file, select scale tool, try to scale, go to edit mode try to scale, see the difference?[video_1.mp4](video_1.mp4)\n\n[video_2.mp4](video_2.mp4)\n\n[bug_rot_scale.blend](bug_rot_scale.blend)", "Noise artefacts when lacunarity is near 1\nFor all noises that have fractal detail and lacunarity set close to 1 this outputs a zoom type effect.\n\n\n\nThis is caused by the noise origin occurring in the same place. \n\nIt is possible to mitigate this by offsetting the fractal layers but fixing this would be a breaking change.\n\n```Diff\n+#define FRACTAL_OFFSET 1259.0\n+\n /* The fractal_noise functions are all exactly the same except for the input type. */\n float fractal_noise(\n vec3 p, float octaves, float roughness, float lacunarity, bool normalize)\n@@ -78,7 +80,7 @@ float fractal_noise(\n octaves = clamp(octaves, 0.0, 15.0);\n int n = int(octaves);\n for (int i = 0; i <= n; i++) {\n- float t = snoise(fscale * p);\n+ float t = snoise(fscale * p + i * FRACTAL_OFFSET);\n sum += t * amp;\n maxamp += amp;\n@@ -87,7 +89,7 @@ float fractal_noise(\n }\n float rmd = octaves - floor(octaves);\n if (rmd != 0.0) {\n- float t = snoise(fscale * p);\n+ float t = snoise(fscale * p + (n + 1) * FRACTAL_OFFSET);\n float sum2 = sum + t * amp;\n return normalize ? mix(0.5 * sum / maxamp + 0.5, 0.5 * sum2 / (maxamp + amp) + 0.5, rmd) :\n\n```\n\n" ]

[ "QuadriFlow with the new symmetry option creates holes at the center\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)\n\n\nQuadriFlow creates hole artifacts like these when remeshing. Usually occurs after using Voxel Remesher and/or Dyntopo which can break symmetry at the center very often.\n\n\n1) Sculpt something in Sculpt Mode and use Voxel Remesher/Dyntopo.\n2) Start QuadriFlow. It doesn't always produce these holes in the mesh, but keep repeating part one and two and you will eventually get these holes where each side hasn't been properly merged together." ]

[ "The Principled (transparency=1)/Glass BSDF converge incorrectly when using Multiscatter GGX on non manifold meshes.\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\nThe Principled (transparency=1)/Glass BSDF converge incorrectly when using Multiscatter GGX on non manifold meshes. This issue is only present with Multiscatter GGX and does not occur with other microfacet distribution models. It also seems to only affect transmission as the Glossy BSDF does not have this issue. Additionally it also seems to only occur in combination with non manifold meshes.\n\nNon manifold mesh:\nGGX+non manifold mesh\n\nMultiscatter GGX+non manifold mesh\n\nThe problem is the sudden incorrect apperance of light in within the red circle in the case of Multiscatter GGX.\n\nManifold mesh:\nGGX+manifold mesh\n\nMultiscatter GGX+manifold mesh\n\nNo problem here.\n\n[Multitest4.blend](Multitest4.blend)\n\nIn this test file the gradient going into the roughness input goes from 0 at the top to 1 at the bottom. There is another hidden manifold cylinder. Unhiding the manifold cylinder shows that this issue does not occur with manifold meshes.\n\nThank you and have a great day!\n", "Cloth simulation of Ngons are broken with Angular Bending Springs\nOperating system:Win\nGraphics card:RTX 3060 Ti\n\nBroken: 2.83, 3.2.2, 3.4\n\n\nThe attached file includes two similar meshes, one of which has an Ngon. A cloth simulation with the default settings was added except for some pinned vertices.\nThe mesh with the Ngon doesn't simulate correctly as shown in this video:\n\n[20220829-125207.mp4](20220829-125207.mp4)\n\n\nPlay animation:\n\n[cloth bug.blend](cloth_bug.blend)\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", "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", "Hiding faces on a specific mesh causes random hidden edges to display in place of non-hidden ones\nOperating system: macOS-13.5.1-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Pro 1.2\n\nBroken: version: 3.6.2\nWorked: unknown, but same bug occurs in 3.5\n\nWhen selecting certain faces on this mesh (see attached STL file), pressing H or shift-H to hide faces will cause a random set of floating edges to display in the hidden regions, and the visible region will display with no edges (making it impossible to see your selection in edge select mode). The set of edges is truly random, as undo / redo will show a different set of edges each time.\n\n| Here is the full mesh with an example selection | Here is the result of pressing shift-H |\n| -- | -- |\n|  |  |\n\n1. Open the attached blend file bugball.blend, and enter edit mode on the ball to see the random floating ghost edges.\n2. Press 2 and try selecting things (selections on the un-hidden faces are invisible, and the ghost edges can't be selected).\n3. Press Alt-H and Shift-H to see that a different set of floating edges appears every time.\n\nIf the blend file doesn't work, try and import the attached STL file using file -> import -> stl and observe the same behavior.\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", "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", "Cycles does not render geo with Multires modifier while in Sculpt mode\nOperating system: Windows 10, Linux\nGraphics card: Nvidia GTX 960\n\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nAdding a Multires modifier with the Sculpt parameter > 0 (to further develop the model I'm working on) makes the geo disappear when using Cycles in the viewport, while in Sculpt Mode. As a first time Blender user, I'm not sure if this is the expected behaviour for this. I have checked with other users and they can reproduce the error. \n\nIt would be useful to render in viewport without leaving Sculpt Mode.\n\nCreate a geometry. Add a Multires modifier. Set Sculpt to a value greater than 0. Enter Sculpt Mode. Change the viewport render from Eevee to Cycles. The geometry disappears on rendering. I have a sample of the problem in this tweet I published several hours ago: 1150657198374080512\n\nThanks!", "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", "Multres disabled in Sculpt Mode when under another modifier\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06\n\nBroken: version: 2.92.0 Alpha\n\nWhen stacking another modifer like Solidify or Mirror over (listed below in the modifier stack) the multires modifier it will disable you from sculpting on the subdivision levels when entering sculpt mode.\nInstead it will show the base resolution. If any modifier visibility is toggled or sculpt level is switched it will be fixed.\nSometimes when sculpting on an object with this bug it also crashes but I couldn't reliably reproduce this.\n\nI assume the intended effect would be that the modfiers other than the multire get disabled, but not the multires itself.\n\n- Add a multires modifier on the default cube\n- Subdivide 2 times\n- Add solidifiy modifier \n- Enter sculpt mode\nNow instead of showing subdivision 2 it will show the base mesh\n- Toggle any modifier visibility, subdivision level or the sculpt mode option \"Use Deform only\"\nNow it will be fixed. Toggle out and into sculpt mode again and it will show the bug again.\n\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", "Using LineArt modifier , line behind object will appear unexpectedly.\nSystem Information\nOperating system: Windows-10 64bit ver.20H2 os build 19042.1052{[F10208498](2021-07-02__3_.png)}\n\nGraphics card: NVIDIA Quadro [P2000](P2000.txt) driver ver.R470 U1 (471.11) WHQL\n\nBlender Version\nBroken: version: 3.0.0 Alpha\n\n**Short description of error:**\nUsing LineArt modifier , line behind object will appear unexpectedly.\n\n[2021-07-09 10-22-31.mp4](2021-07-09_10-22-31.mp4)\n\n**Exact steps for others to reproduce the error:**\n[lineartTest.blend](lineartTest.blend)\n\n- Open file \n- Tweak camera shift X property from min to max\n\nLines won't be drawn for some objects. \nBug looks a bit different in `7489427e4d` than what's shown in video\n\nAny way ,I’m excited new features.Thank you all to a great work.\nHave a nice days.", "Applying Subdivision/Multires Modifier De-merges UV's\n### Update\n\nThe issue of custom-data (UV's specifically) becoming detached remains, this problem existed before b88dd3b8e7, it was just less obvious since selection connected near-by UV's. Now UV's are merged by default at a very low threshold when applying modifiers to mitigate the problem. Keeping this report open as it would be good if subdivision-surface didn't separate UV's, replies to this report contain some notes that could lead to a solution. In practice users should not experience problems caused by this behavior, so marking low priority. ~ @campbellbarton.\n\n----\n\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.91.0 Alpha \nWorked: working in 2.90 \n\nCaused by b88dd3b8e7\n\nWhen applying a subdivision modifier, certain UV's points disconnect from their neighbors. This does not seem to occur with the F3 menu subdivide operation.\n\n- Open default blender scene.\n- Subdivide cube - 1 level and apply it. Do this step 4x\n- In the UV editor use \"Alt select\" to select face loops at random.\n- Alt click around until a face loop is not fully completed, this will reveal unmerged vertices.\n- Check area that did not complete by moving faces, vertices, edges etc to confirm unmerged UV's.\nThis does not seem to be an issue with the newly added 9a52b30cc0 in my eyes, rather an issue with subdividing.\n[UV Disconnect.blend](UV_Disconnect.blend)\n\n", "Regression: Damaged normals in sculpting with Multires modifier\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nWhen sculpting, sometimes breaks normals. Switching between modes fixes this.\n| Edited sculpture | Object mode |\n| -- | -- |\n|  |  |\n\n1. Open attached file.\n2. Go to Sculpt mode.\n3. Do something.\nLook at the fact that in some places the normals are damaged.", "UV map inconsistency after bevel modifier\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nMesh position in edit mode affects how bevel processes UV map\n\nIn attached file translate selected part of mesh along world Z axis -> UV is changing position\n[bevel_uv_issue.blend](bevel_uv_issue.blend)" ]

[ "Multires Subdivide Randomly Creates Spikes\nOperating system: Windows 64 bit\nGraphics card: Nvidia GTX 750 Ti\n\nBroken: 2.83.8, 2.90 release, 2.91 beta dca36a8ec922, 2.92.0 Alpha 7bab87c119\nWorked: 2.82a (no issues in 4 attempts)\n\nRandom spikes appear when clicking \"Subdivide\" in the Multiresolution Modifier.\nThis seems to happen around ngons.\n\n1. Add a cylinder.\n[multires_spikes.blend](multires_spikes.blend)\n[T829005_2.83_example.blend](T829005_2.83_example.blend)\n2. Press \"Subdivide\" in the Multires-Modifier multiple times.\nThis happens randomly, so you may need multiple attempts.\n\nOne possible outcome:\n\n\nThe expectation is, that it should look exactly like the Subdivision Surface Modifier.", "Multiresolution modifier creates spikes when subdividing ngon meshes. \nOperating system: Linux-5.6.14-300.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits, Windows\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.82\n\nBroken: version: Bisected to 4542b50afc \nWorked: version: Before 4542b50afc\nMultiresolution modifier creates spikes when CC subdividing ngon meshes.\n\nAdd cylinder or cone mesh, add multiresolution modifier on it, and subdivide with the default Catmull Clark (level 2-3 is enough to show the mess-up). See attached.\nOccurs in both Object and Sculpt modes.\n\n\n[multires.blend](multires.blend)\n\n---\n2.83.8 .blend\n[T829005_2.83_example.blend](T829005_2.83_example.blend)\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", "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.", "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", "Sculpting produces weird shading artifacts\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\nWhen sculpting a low poly mesh, weird shading artifacts appear. \nIf you remove them with a modifier, then over time they reappear when sculpting\n[X9Tkiufd2w.mp4](X9Tkiufd2w.mp4)\n\n|.blend file showing in the video:|[test.blend](test.blend)\n| -- | -- |\n\n- In a clean scene with no objects, Add a cylinder (or any low poly object, preferably with N-gons)\n- Enable Shade Smooth on the object. {nav Object > Shade Smooth}\n- Go to Sculpt Mode\n- Use a brush anywhere - the affected vertices will have their normals updated and change their look\n\n||\n| -- | -- |\nIf you undo or do any operation that affects the entire mesh it will change the shading everywhere\n|\n| -- |\n", "Blender renders wrong in viewport\nOperating system: macOS-11.2.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.15\n\nBroken: version: 2.93.0 Alpha\n\n\n\n1) steps to reproduce:\n\nopen blend file [circular_circles_wave_emission.blend](circular_circles_wave_emission.blend)\n\n2) in viewport change to rendered view\n\n3) you will see:\n\n\n\n4) select the circles\n\n5) press tab and tab again\n\n6) you will see:\n\n\n\nwhich is correct\n\n", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "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", "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", "Vulkan: Better handling of GPU debug when not having vulkan SDK installed.\nBlender libraries only contain a subset of the vulkan SDK. Most important is\nthat validation layers aren't added. These validation layers will be enabled\nwhen starting blender with `--debug-gpu` (or test cases).\n\nIn this case there is an error printed to the console. This should not be an\nerror, but we could add a log line when not found.\n\n", "Multires spikes\nOperating system:\nGraphics card:\n\nBroken: Blender 3.00\nWorked:\n\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n1. Sculpt while having multires modifier on\n2. Move \"sculpt\" level up and down\n3. Go into edit mode? I am not sure if I did do this, but I read that some people did do it to cause the artifact to appear. \n4. Artifact appear\n5. Unable to fix, without restarting [Handle safeguard v2.blend](Handle_safeguard_v2.blend)\n\nI can read online that this seems to have been a bug for long, but I couldn't find a fix. \n\nCan I use multires on my objects? What exactly caused this, and how can I fix it? \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", "Rendering in cycles causes objects with materials to go black and shiny when using the GPU\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 7900 XT ATI Technologies Inc. 4.5.0 Core Profile Context 23.7.1.230626\n\nBroken: version: 3.6.1\nWorked: N/a\n\nWhen my render engine is set to cycles and device is set to GPU Computer (with HIP and my 7900 XT selected), if I look at an object with a material applied in either viewport shading or as a rendered image the model will appear black and shiny or occasionally will just show as a flat blue colour. \n\nThis issue does not occur when using the CPU as the device instead and also did not begin to occur until a few days ago (prior to which it was working fine).\n\nI've checked the same blender file on a laptop with a 3060 GPU which worked correctly so I don't think the file itself is corrupted.\n\nI have also checked multiple blend files, some of which work fine, others do not, one file has some things working and other things broken (I will attach it to this bug report)\n\n\n1. Load the attached blend file \"ArkenV1R1_Interior.blend\".\n2. Go to edit > preferences > system > cycles render devices, set it to HIP with RX 7900 XT selected.\n3. Under scene settings, change the render engine to cycles and device to GPU compute.\n4. Switch to Viewport shading.\n5. Observe that the bullets and floor panel are shown as black and shiny while the table renders correctly (grey and blue).\n6. Press F12 and observe that the rendered image also shows the bullets and floor panel as black and shiny.\n\n\n**Additional**\nIncorrectRender.png was rendered using GPU\nCorrectRender.png was rendered using CPU\n\nI will be happy to provide anything else needed to figure this out, thanks!\n\n", "Black artefact when mixing transparency and glass at a certain ratio\nOperating system: WIn 10\nGraphics card: GTX 1080\n\n2.92\n\nBlack artefact appear on flatter surfaces when mixing 99.9% transparent and 0.1% glass shaders. Glass should be rough. \n\nMake a cube, switch to Cycles, add material, add Glass and Transparent Shaders, Mix them together, put factor on 0.999, increase Glass roughness, depending on roughness a entirely black circle will appear on the cube when viewed straight on. \n\n[TransBug.blend](TransBug.blend)", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Blender stops updating display after GPU spike\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.8681\n\nBroken: version: 2.92.0 Beta\nWorked: I have not found a version that works as expected on this computer. I have tried 2.79, 2.8, 2.91\n\nI was premature in saying the problem is gone for [#85061 ](T85061).\n>After a few minutes of using Blender, the window freezes. Windows does not detect that it is not responding, but Blender does not respond to any input, including clicking on the close button. All elements that are drawn by Blender remain as they were at the moment of the crash except if I resize the window smaller.\n\nIf I watch the performance tab on Windows Task Manager, the freeze coincides with a 100% spike on the GPU.\nAs long as that spike doesn't happen, there is no problem, but once it does, Blender stops responding to any input, but it does not crash.\nI have updated my graphics drivers.\n[blender_debug_output.txt](blender_debug_output.txt)\n\nI have not determined exact steps. It has occurred on multiple files doing multiple different tasks. As far as I can tell, there is no correlation between what I am working on or what task I am performing, and the error occurring.\n" ]

[ "Cycles renders artifacts on CPU but not on GPU\nDuring a project I noticed this strange shading effect which I wasn't able to \"fix\" by just tweaking settings. What's interesting about this is that it only occurs for CPU rendering and not for GPU (usually I would expect it the other way around).\n\n\n\nJust load the blend file and render it with CPU and GPU to see the effect.\n\n[cycles-cpu-artifacts.blend](cycles-cpu-artifacts.blend)\n\nTested with the official Blender build on Windows 7 64." ]

[ "Compositor refresh on every 3D view edit and blocks UI\nOperating system: Windows-10-10.0.16299 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBroken: version: 2.80 (sub 74)\n\nAdjust operator panel for selection operations is greyed out after every operation. When you move cursor out of the input field it's active again. It happens only when compositor is opened and \"Use Nodes\" is selected. See video:\n[Desktop 2019.06.19 - 12.22.31.02.avi](Desktop_2019.06.19_-_12.22.31.02.avi)\n\n - Open attached file: [select_compositor_bug.blend](select_compositor_bug.blend)\n - Use Select > Checker deselect\n # Go to adjust operator panel and change one value. Menu will be greyed out until you move cursor out of input field.\nIt's the same with other selection operations like \"Select Similar\" or \"Select Sharp Edges\".", "Playback locks to frame with Sync-to-Audo, when changing Sound Settings\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 466.11\n\nBroken: version: 3.0.0 Alpha\n\nWhen playing the animation, while using Sync to audio, changing the Sound Settings will lock the playback. \nThe UI will show the fps etc but will not move beyond one frame.\n\n- Start Blender, set playback sync to Sync to Audio.\n- Press play.\n- Change anything in the Sound Settings of the User Preferences. \n- The UI will appear to as though animation is playing but the frame won't change: fps would be visible. (Inserting keyframes shows that scene doesn't actually change.)\n- If you move the timeline frame manually, when you stop it will only move forward one frame.\n\n[T88679_m.blend](T88679_m.blend)\n|Device|If fps shows with frame paused|\n| -- | -- |\n|CoreAudio|No, frame is set to 0, fps disappears, playback stops|\n|SDL on mac| yes |\n|SDL on windows| no|\n|OpenAL| yes|\n|OpenAl built-in input|yes|\n|SDL|yes|\n|pulseaudio|?|\n|WASAPI|?|\n", "Local Camera doesn't allow animation of camera from excluded collection\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\n Local Camera in N-panel not playing camera action, if this camera is in excluded collection. For comparison Cube is parented to rotating Empty from the same excluded collection and it is working fine.\n\n\nIn default scene:\n - Give Camera an animation and put it in a new excluded collection\n - Select this Camera as Local Camera in N-panel\n - Remove Active Camera (or replace with another camera) from Scene Properties tab and play animation -> not working\n - Include collection back and play again -> working ok\n\nIn attached file:\n - Play animation with excluded/included New Collection\n\n[camera_problem.blend](camera_problem.blend)\n", "Render cloth animation does not resets cache\nBroken: 2.82.7\nWorked: 2.79b\n\nWhen modifier Subdivision is before the cloth physics modifier,but with different subdivision settings for rendering and viewport, the cache remains active even when rendering.\nPossibly related to #74523.\n\n- Open attached file\n- Run animation (without baking)\n- Render animation\nNotice that the cloth is deformed with each rendered frame.\nThis is because rendering reuses the cache.\n\n[bug.blend](bug.blend)", "Displacement Animation works only with keyframed node present\nOperating system: Linux-5.4.0-107-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.60.02\n\nBroken: version: 3.1.2\nBroken: version: 3.2.0 Alpha\nWorked: unkown\n\nDisplacement Animation works only with a keyframed node present, even if it is not connected!\nI was trying to animate displacement using the object color, finding that it doesn't work.\nWhen trying a keyframed mapping node instead I found that it works but even if the node is not connected!\n\n - Open the attached blender file, switch to render mode and play the animation\n - The displacement will be animated.\n - Now delete the not connected mapping node or clear its keyframes.\n - The displacement will not be animated anymore. Even though I would expect it to be animated by the object color.\n\n[displace-test-1-1.blend](displace-test-1-1.blend) \n\n[displace-test-1-1.mp4](displace-test-1-1.mp4)\n", "VSE Scene strip's color profile is overridden by sequencer settings\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nThere are two scenes:\n1. **Scene.001** is VSE sequencer with *RGB* profile in color management\n2. **Scene** is used as *Scene Strip* and has *XYZ* color profile\n\nWhen rendering **Scene** strip from **Scene.001** sequencer, it overrides original *XYZ* with its *RGB*, but OpenGL preview shows correct mode.\n\nIn attached file render separately **Scene** 3d view and **Scene.001** VSE sequencer to see the difference\n\n", "Inconsistent Grease Pencil auto-keying behavior\nOperating system: Linux 64-bit\nGraphics card: GTX 1080\n\n3.1 and prior\n\nWhen auto-keying is enabled and you're transforming a GP stroke in edit mode on a new frame, a keyframe is added at the beginning of the operation before it is confirmed. If you right-click to cancel the operation, the redundant keyframe remains. This is inconsistent with auto-keying in every other area, in which Blender waits for the user to confirm the operation before adding the keyframe. \n\nAlso, deleting a stroke fails to add a new keyframe. I apologize if these are two different bugs but they seem related.\n[GP_autokey_bug.blend](GP_autokey_bug.blend)\n - Open the attached file.\n - Grab (G) a stroke, then right-click to cancel moving it. The keyframe was inserted, even though no change was made.\n # Go to another frame, then delete a stroke. No keyframe was inserted this time, even though the GP drawing has definitely changed!\n\n", "VSE: Transform settings doesn't get copied across scenes\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\nTransform settings doesn't get copied across scenes\n\nCopy a strip, which doesn't match the render resolution, across scenes:\n{[F10121941](copy_missing_transform.gif),size=full}\n\n", "`action.frame_range` span always >=1 when there's only 1 key frame in it.\nOperating system: Mint\nGraphics card: Nvidia\n\nBroken: 3.5 & main branch\n\n\nframe_range wrong value when only 1 keyframe\n\n- with default cube, go to frame 6\n- Insert a keyframe (for example, on location)\n- bpy.context.object.animation_data.action.frame_range returns (6.0, 7.0)\n\nMy expectation was it returns (6.0, 6.0)\n\nIf you then insert a keyframe at frame 7, it still returns (6.0, 7.0)\n\n", "VSE unkeyed transforms in preview persist in cache\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\nVSE unkeyed transforms in preview persist in cache.\nIf transforms occur on a property that has an fcurve already (but no keyframe is actually created on that frame), this transform will remain in the cache for that frame.\nThis does not get invalidated on timeline scrubbing / frame change.\n\n(this report was split from #98015 (VSE strip transforms do not animate correctly and persist after clearing the animation) since multiple issues came up in that report)\n\n[VSE_keyframing.blend](VSE_keyframing.blend)\n\n- open .blend\n- create a keyframes for rotation on frame 1\n- go to frame 10\n- rotate in the `Preview` again and confirm the rotation (but dont create a keyframe)\n- scrub the timeline\n- since this change on frame 10 was not keyed, it should vanish, but it doesnt, it remains in the cache\n- note: when the strip in the `Sequencer` view gets moved, the issue goes away (assume the whole cache gets invalidated then)\n\n\n", "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.", "VSE: Frame Rate Base Rounding Leads To Vid / Audio Strips Out Of Sync by 1 Frame\nOperating system: Windows 10\nGraphics card: RTX 3090\n\nBroken: since 3.0 until now in 3.6.1 hash 8bda729ef4dc\nWorked: 2.93.18\n\nIt looks like the same bug #21138 is reappearing in the 3.x series and since the bug report is 14 years old, I created a new one.\nOld bug report: 21138\n\nMy description:\nI have a lot of projects with 29.97fps (30000/1001) and those work correctly with Blender 2.9x but since Blender 3.0 all video clips are 1 frame shorter and my projects are a mess, because the frames in all clips are also shifted 1 frame !!\nIf I set the base to 1.0009 instead of 1.001 its all fine in the Timeline, but if I set 29.97 from the drop-down menu, all clips are 1 frame shorter and shifted.\nI have this also tested with videos without any audio and that makes no difference.\nThe audio length btw is alway correct.\nI also noticed that the trick with 1.0009 is not good, because this value is then transferred to the exported video and thats wrong!\n\nI think the problems in the following posts also have the same cause?\n[audio-is-1-frame-off](https://blender.stackexchange.com/questions/51650/audio-is-1-frame-off)\n[blender-3-0-vse-audio-and-video-out-of-sync-bug](https://blender.stackexchange.com/questions/250718/blender-3-0-vse-audio-and-video-out-of-sync-bug)\n\n", "Next/Previous Keyframe breaks when \"Show Only Selected\" is disabled\nOperating system: Linux-5.4.0-91-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.91.03\n\nBroken: version: 3.1.0 Alpha, branch: master, hash: `60a9703de8`\nWorked: never, 2.79 also had this problem in a way (but slightly different due to limitations of its dope sheet). 2.83 has the exact same problem described here.\n\nNext/Previous Keyframe ( {key up} and {key down} in the dope sheet) do not jump to the next/previous key **shown**, but to the next/previous key of the **active object**.\n\nIn other words, it sort of works as if \"Show Only Selected\" is always enabled, but then even more strict, only responding to the keys of the active object. This can probably be tracked down to the dope sheet only showing animation data of the active object back in the old ≤2.79 days.\n\n1. Open the attached blend file.\n2. See that the current frame is set to frame 1.\n3. While hovering with the mouse over the dope sheet, press the up arrow {key up}.\n4. See the message \"No more keyframes to jump to in this direction\". *Expected behaviour:* it would jump to the next keyframe shown, which is at frame 5.\n5. Click on the Cube to make it active + selected.\n6. While hovering with the mouse over the dope sheet, press the up arrow {key up}.\n7. See that it jumps to frame 10, which is the next keyframe in the Cube's animation. *Expected behaviour:* it would jump to the next keyframe shown, which is at frame 5.\n\n\n\n[next-prev-keyframe-selection-issue.blend](next-prev-keyframe-selection-issue.blend)", "Action editor key frames not displaying sometimes\nSometimes when working with multiply animations and switching through them in the action editor. The Keyframes stop displaying for certain action. \nWhen the Panel with the action editor View is removed and added again, the displaying is working again.\nThis bug was seen in Version 2.76 and daily Build from 10/30/2015.\n\nError:\n\nFixed after closing and opening action editor view\n\n\nMy Project without Mesh. Bug is seen in walk_back_cycle action.\n[animation_editor_error_project.blend](animation_editor_error_project.blend)\n\nThis bug is very annoying in my workflow.\n\nGreetings and thank you for your work!", "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" ]

[ "Blender video editing: Moving video / audio strips doesn't move keyframes\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.35\n\n\nBroken: version: 2.80 (sub 59)\nWorked: (optional)\n\n\nAfter moving a video / audio strip, keyframes in the strip are off or corrupted. They do not seem to follow the translation of the strip, but stay in place. This behavior is different from the one in Blender 2.79.\n\n(1. Optional. Change into Video editing workspace)\n2. Make sure the video sequencer is open.\n3. Add a movie (movie strip).\n4. Select the movie strip.\n5. In the movie strip's \"edit strip\" properties, add a keyframe (I) to the Opacity property.\n6. Place the cursor a few seconds further into the strip.\n7. Change the value of Opacity to 0, add a new keyframe (I).\n(8. Make sure the keyframes were set properly by watching the movie playback.)\n9. Select the movie strip (box-select).\n10. Move the movie strip forward a few seconds (G key).\n11. Note that as you move the strip, the keyframes shown in the timeline windows do not move with the strip.\n12. After the strip is moved, the keyframes are not placed in the same spots relative to the beginning and end of the strip anymore. Rather, they have stayed in the same absolute position in the timeline.\n\nExpected behavior is that the movie / audio strips move with the strip as the strip is moved, like it was in Blender 2.79.\n\nThank you for all your hard work." ]

[ "Industry Compatible keymap uses Ctrl + H for two separate actions resulting in only one action working\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.2.1\n\nThere's a keymap conflict here when using the Industry Compatible map:\n\n\nUnfortunately instead of resulting in both actions being done, this results in the \"hide unused\" shortcut not working at all by default.\n\n- switch to Industry Compatible keymap\n- create a material\n- select a node and try to use keyboard shortcuts for \"hide unused\" and \"collapse\"\n- note they're both Ctrl + H resulting in only \"collapse\" ever doing anything.\n\nEither should by default both actions happen upon that shortcut or there should not be a conflict by default.\n", "Connected child bone's nominal location values affected when transformed about 3D cursor\nBroken: 2.79, 2.90.1\nWorked: N/a\n\nAs expected, when moving a single connected child bone, its location is not affected, only the rotation.\nBut it is still possible to affect them accidentally if transforming about the 3D cursor.\nThis is a minor bug, but it's a definite inconsistency.\n\n - Open attached file.\n - Move/Rotate/Scale the child bone about the 3D cursor.\nNote the bone's nominal location values in the side panel.\n\n[Connected Bone Pose Bug.blend](Connected_Bone_Pose_Bug.blend)", "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", "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", "Select key in dopesheet deselect bone in the viewport\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.48\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nIf you select key in Dopesheet without Only selected, it deselect your bone in viewport\n\n1) open [deselectBone.blend](deselectBone.blend)\n2) select bone in Pose mode\n3) select any key in dopesheet without \"Only selected\"\n4) bone is now deselected in viewport\n\n", "Fade Inactive Geometry: Objects with the same stored mode are not 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\nIt is possible to keep objects in a certain mode even if they are not active. \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.\nUnfortunately if any object in the scene is also in the same mode, even if it is not active or affected by the currently active object, it will not be greyed out.\n\n In this example image 2 quad-spheres are not greyed out. The left one is active and can be sculpted on. The right one is not active or selected but is also currently in sculpt mode. \n\n- Disable \"Lock Object Modes\" in Topbar -> Edit\n- Duplicate an object multiple times to have more than 1\n- Select one and switch to (for example) vertex paint mode\n- Select another object in the 3D viewport or via the outliner without exiting the mode of the active object\n- Switch into the vertex paint mode\n- The other object is not greyed out \n\n", "Collection don't change text color\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\nActive object's text is not visible if the selected object is collection (in the outliner).\n \n\n**Steps to Reproduce**\n- Open the directory where blender.exe is\n- Place the `test.xml` file inside `\\blender_version\\scripts\\presets\\interface_theme\\`\n- Run Blender\n- Change the theme to `test` from preferences tab\n- Select the collection in outliner (Collection name is not clearly visible because of changed `active Highlight` color)\n\n[test.xml](test.xml)", "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", "Simulation Nodes: show bakes in outliner\n_No response_\n\n", "Auto IK pose for FK chains moves the entire bone chain\nOperating system: Linux-5.13.0-39-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01\n\nBroken: 2.79 - 3.2.0 Alpha\nWorked: Not found\n\nChanging the position of the first bone change the position of the last bone's tail. \n[Peek 2022-04-01 11-50.mp4](Peek_2022-04-01_11-50.mp4)\n\n[bugautoik.blend](bugautoik.blend)\n1-Select the bone \"Bone\"\n2-Start moving the bone (G)\n3-Apply the new position by pressing left click or space bar\nThe last tail should move as in the video. \n\nNOTE: in the video im using a stylus wacom4 and the bug its trigger every single time clicking or using space bar, more or less intense but its there, using a regular mouse its not that consistent but it happened one of ten tries randomly. \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.", "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. ", "Auto keying not keying for child bones and not transformed\nOperating system: Windows 10\nGraphics card: RTX 3060 Ti\n\nBroken: (3.1.0 c77597cd0e15 master 2022-03-08 18:16)\n\nWhen I tried to auto key multiple bones by select these and hit G > Mouse1 only the top of parented bone is keyed and nothing for anything else \n\n・Add armature\n・In edit mode -> extrude bone\n・Enable Auto keying\n・In pose mode -> Select All (A) ->Move/Rotate/Scale(but not make any transform, just apply) to add a keyframe\n\nTest file with first 3 steps included:\n[#96473.blend](T96473.blend)", "Stronger binding of Active and Selected\n**Context**\n\nFor many things that can be *Selected*, there is also a state called *Active*. There can be 0..∞ *Selected* things, and 0..1 *Active* things. This applies to objects, bones, fcurves, fcurve keys, mesh elements, and more. These will just be referred to as *thing* in this task to avoid having to repeat that entire list.\n\nThe *Selected* and *Active* states are independent, so there are four states a thing can be in:\n\n| | Not Selected | Selected |\n| -- | -- | -- |\n| Not Active | x | x |\n| Active | x | x |\n\n**Problem**\n\nThere are two states possible that can cause issues:\n1. **There are *Selected* things, but none of them is *Active*:** a sidebar/numerical/properties panel will not show information, and generally be empty without explanation why.\n2. **There is an *Active* thing, but it is not *Selected*:** this is not shown in the UI, as there is no separate color for this situation; all *Active* things are shown the same way regardless of them being *Selected* or not. This causes confusion and unexpected behaviour, and also doesn't allow for an actual clear use of this possibility.\n\n**Related Reports**\n\nThese reports are examples of confusing situations where the disconnect between *Active* and *Selected*. The list is not exhaustive, and may be expanded later.\n\n- #14429 (selected bone is not active)\n- #65219 (Objects don't become active object if they are selected by a box)\n- #68647 (objects selected using box select cannot be moved to collection if there is no active object)\n- #81922 (The Graph Editor doesn't show any curve of the Armature (if in Pose mode, but armature unselected, with box/circle/lasso tools))\n\n**Proposal**\n\nThis design task proposes linking *Active* and *Selected* such that:\n1. If there are *Selected* things, there is always one of those that is the *Active* thing.\n2. If a thing is *Active*, it is also always *Selected*.\n\n**Hurdles to Overcome**\n\nRule 1. above requires that one of the selected things is marked active. There is not always a unique, obvious choice here, for example when box-selecting multiple things at the same time. In this case the choice should at least be consistent so that users know what to expect after a while. The thing closest to the mouse cursor (when using the mouse to select) could be a reasonable choice.\n\nRule 2. above can be dealt with in various ways:\n- Create a function that returns the *Active* thing, and make it return nil when that thing is not also *Selected*. This is what was implemented for the Active Keyframe (983ad4210b). This has the downside that now nothing is active, breaking rule 1 and forcing the selection-changing code to pick another thing to become *Active*.\n- Refuse deselection of the *Active* thing.\n- ... something more elegant.\n\n**Goal of this Design Task**\n\nThe goal of this design task is to answer the following questions:\n- Is there an agreement that the current situation causes issues, and that having a stronger correlation between *Active* and *Selected* is a good thing?\n- Is there an agreement that the proposed two rules are the way to go?\n- How do we implement these rules in a way that makes sense to artists?\n- Can we implement this in a way that can be reused by all the affected parts? Some unified selection/activation API that can be implemented for different data types?\n", "Cyclic Strip Time not work with non-zero Action Clip Start Frame\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.92\n\nBroken: version: 2.93.3\nWorked: ???\n\nCyclic Strip Time not work with Action Clip\n\nI attached .blend to show this bug.\nThe track called \"Ok\" works with the \"Cyclic Strip Time\" check mark correctly.\nThe track called \"Bug\" works with the \"Cyclic Strip Time\" check mark incorrectly.\n\nIn the track \"Ok\", there are two keys, at 0 and 10 frames.\nIn the track \"Bug\", the same two keys, but for 43 and 53 frames. In the Action Clip, I set the values Frame Start =43 and End = 53.\nI expect that the \"Bug\" track will perform the same actions as the \"Ok\" track, but this does not happen.\nI think this is a mistake.\n[BugCST.blend](BugCST.blend)\n" ]

[ "Outliner: show_active doesn't expand armature to show active bone\nBroken: 2.81, 2.82 (ba1e9ae4733a)\nWorked: 2.80\n\nWhen the Armature is collapsed in outliner, pressing numpad . to show active doesn't expand armature data block, so doesn't show active. In edit mode, it will expand the Armature object, but only the object. In pose mode, it doesn't expand even that.\n\n\n1. Create an armature\n2. Switch to edit mode and add a few bones, select one of them\n3. Hover over the Outliner, make sure the Armature is collapsed, and press numpad period.\n\nArmature object will expand, but not armature data.\n\n4. Collapse Armature object\n5. Switch to Pose mode\n6. Hover over the Outliner and press numpad period.\n\nNothing will be expanded at all." ]

[ "different Skin Modifier outputs for same mesh\nWindows 10\nNvidia Quadro 600\n\nBroken: 1422f0d\n\nThe skin modifier produces different meshes on the default cube.\n\n\nTrigger the skin modifier to update by doing the same thing I do in the .gif\n\n[skin_modifier_bug.blend](skin_modifier_bug.blend)\n\nNote: this only seems to happen when the edges are orthogonal. When I move one point, the problem doesn't appear on this and connected points.\n\n(Originially reported here: 576)\n", "Changing the geometry type in the Vertex Weight Proximity modifier disables \"Invert Falloff\" and \"Normalize Weights\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.91.0\nWorked: \n\nIn the **Vertex Weight Proximity** modifier if the proximity mode is set to *Geometry*, changing the geometry type between *vertex, edge and face* disables the options *Invert falloff* and/or *Normalize Weights*.\n[bug.mp4](bug.mp4)\n\nAdd an object, add the vertex weight proximity modifier, set the proximity mode to geometry, enable the options normalize weight and invert falloff and change the geometry type between vertex, edge or face.\n[Based on the default startup]\n\n", "Crash on Python API bpy.ops.mesh.rip_move()\nOperating system: Windows 10\nGraphics card: RTX3080\n\nBroken: 3.3.2, 3.4.0, 3.5.0-alpha\n\nCrash on calling `bpy.ops.mesh.rip_move()` from Python API.\n\n - Open new Blender file\n - Switch to Scripting workspace\n - Create file with\n```\nimport bpy\nbpy.context.area.ui_type = 'VIEW_3D'\nbpy.ops.mesh.rip_move()\nbpy.context.area.ui_type = \"TEXT_EDITOR\"\n```\n - Delete all objects\n - `Shift-A` to add cylinder\n - Tab` to edit mode\n - Click edge or vertex selection mode\n - Select an edge or vertex\n - Run script\n - Crash\n\nManually doing a `V` rip move and then using the \"reports\" list to copy over the exact command to line #3, also results in a crash\n[blender.crash.txt](blender.crash.txt)", "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)", "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", "Modifiers after physics ones shouldn't invalidate cache\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\n\nIn current Blender, any change on modifiers invalidates.\nModifiers *after* physics modifiers won't affect the result of physical simulation, therefore they shouldn't invalidate the cache. \n\n\n1. Create a plane\n2. Give it Cloth and Subdivision modifiers, in this order\n3. Set the end frame to 10\n4. Play animation until the end\n5. Stop animation\n\nNow the simulation is cached.\n\n6. Change the viewport division level on Subdivision modifier\n\nNow the cache is invalidated.\n\n", "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", "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", "Transfer shape key is only working for meshes\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\nWorked: Never\n\nTransfering shape keys is option in panel menu, but it only works for meshes. This is not mentioned in documentation and only evident after running the operator.\n\n\nDuplicate object in provided file and try to transfer shape keys.\n", " EXCEPTION_ACCESS_VIOLATION when entering Edit Mode\nOperating system: Windows 10 1903 (18362.239)\nGraphics card: Intel HD Graphics 4000\n\n***Broken:***\nBlender 2.80 (sub 75) / 2019-07-29 09:44 AM Windows / Stable\nBlender 2.81 (sub 1), branch: master, commit date: 2019-08-13 11:31, hash: 6f9cbbc8ec4f\n***Worked:***\nBlender 2.79 (copied mesh over through copybuffer.blend)\n\n\nWhen entering edit mode of a specific object Blender crashes with EXCEPTION_ACCESS_VIOLATION. Logs and example .blend provided.\n\nThe issue shouldn't be in my GPU, since the same issue persists even with Software Rendering.\n\n1. Open up example file\n[window_broken.blend](window_broken.blend)\n\n2. Select `window_panes` and enter Edit Mode\n3. Get EXCEPTION_ACCESS_VIOLATION\n\n**Logs (2.80 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n[blender_debug_output.txt](blender_debug_output.txt)\n\n**Logs (2.81 `blender_factory_startup`)**\n[blender_system_info.txt](blender_system_info.txt)\n\n[blender_debug_output.txt](blender_debug_output.txt)", "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", "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", "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", "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", "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)" ]

[ "Regression: Vertex Weight Mix crash on apply/undo when mesh has shape keys\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: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nI'm getting a crash in a community addon when it applies a Vertex Weight Mix modifier to a mesh with shape keys.\n\nNo crash occurs with the addon when running Blender with `--debug-memory`, instead a lot of `Memoryblock add_shapekey_layers: double free` and `Memoryblock free: pointer not in memlist` are printed to the system console.\n\nI have been unable to reproduce the exact scenario present in the addon in isolation, whereby a crash occurs when applying the modifier, but does not crash when `--debug-memory` is used. However, I have managed to produce similar crashes with Vertex Weight Mix that I'm guessing are related.\n\n\nCrash applying modifier (seems to always crash even with `--debug-memory`)\n1. Start with a default cube\n1. Add two shape keys (so there is the 'Basis' and one other shape key)\n1. Add a Vertex Group\n1. Add a Vertex Weight Mix modifier\n1. Set the Vertex Group you created as both the A and B vertex group (it's not necessary for both A and B to be the same, the crash still occurs if you were to have added two vertex groups and set one as A and the other as B)\n1. Apply the modifier\n1. Crash with the following printed to the System Console:\n```\nMalloc returns null: len=2096855700656 in dupli_malloc, total 19523832\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FFB94071470\nModule : VCRUNTIME140.dll\nThread : 000059d8\n```\n\nCrash on undo unless `--debug-memory` is used:\n1. Open the attached .blend\n1. Apply the Vertex Weight Mix modifier on the cube\n 1. When using `--debug-memory`, this also seems to make the mesh invisible unless the shape keys are removed\n1. Undo\n1. Crash occurs if not using `--debug-memory`, otherwise `Memoryblock free: pointer not in memlist` is printed once to the System Console. Nothing is printed to the System console if not using `--debug-memory`.\n\n\nCrash on entering Edit mode after applying modifier (sometimes doesn't crash with `--debug-memory`):\n1. Open the attached .blend\n1. Apply the Vertex Weight Mix modifier on the cube\n 1. When using `--debug-memory`, this also seems to make the mesh invisible unless the shape keys are removed\n1. Enter edit mode\n1. Crash with the following printed to the System Console:\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF664FA2674\nModule : blender.exe\nThread : 00005840\n```\n\n" ]

[ "Crash with GPU Render\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.02\n\nBroken: version: 3.4.0\nWorked: unknown\n\nOn cycles, using the GPU renderer blender crashes. This only happens when I am using Optix with GPU and CPU. If I disable my CPU, Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, then the render works, using only CPU rendering also works.\n\nMy Memory is not fully used, both GPU and ram, and I have the newest GPU driver, GameReady version 528.02\nHope the blend file works without the video files.\nThanks for helping\n[obj_tracking_test_2.crash.txt](obj_tracking_test_2.crash.txt)\n\n[obj_tracking_test_2.blend](obj_tracking_test_2.blend)\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)", "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", "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", "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", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "2022.1.21 30x24k crash after finisx1.6\n[2022.1.21_HK_tree.crash.txt](2022.1.21_HK_tree.crash.txt)\n\n{[F12814049](2022.1.21_blender_debug_output.txt)}Operating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA RTX A6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.47\n\nBroken: version: 3.1.0 Alpha\n\n超过20K高分辨 仍旧在GPU渲染完成后崩溃\nMore than 20K high resolution，Still crashes after GPU rendering is complete\n但当分辨率降至 20k 以下，比如 19 x 16 k 则不会发生崩溃\nBut when the resolution drops below 20k, such as 1.9 x 1.6k, the crash will not occur.\n\n\n", "Memory leak while rendering with particle hair?\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49\nSystem Memory: 32 GB\n\nBroken: version: 3.4.0\nWorked: Could not find any which made a difference (tried 3.4.1, 3.3, 3.2, and 2.83)\n\nHi\nI've been having a problem where, while rendering in cycles, a blend file appears to be causing system memory usage to increase every frame. It does seem to plateau eventually, but the memory committed remains high even after the rendering is finished or stopped.\n\nI tried to simplify things down as much as possible, it's just the mesh and the object with several particle hair systems.\n\nRender the sample blend file.\nOriginal (240 MB)\nSample.blend?dl=0\nCompressed (54 MB)\nSample.zip?dl=0\nOr\n-Create new blend file\n-Set to render using cycles (gpu using optix)\n-Append \"Sample\" collection from attached blend file\n-Render", "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", "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```", "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 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", "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.", "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)" ]

[ "Blender crashes when using particles properties.\nOperating system: Windows 10\nGraphics card: Intel(R) HD Graphics 4600\n\nBroken: 3.0.0\n\nCrashing when using particles properties. Hair.\n\nYou don't need a blend file to see that. It crashes just when you work with a simple cube." ]

[ "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 freeze on render and texture baking (with packed textures)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1660 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.92.0\nWorked: 2.83\n\nThis broke somewhere between b21ba5e579 and f2b5f731d5\nAssume 99436acde8\n\nBlender freezes on render\nBlender also freezes on texture bake and rendered viewport\nTried on 3 different PCs, all the same\n\nIf textures are unpacked, rendering is fine.\n\nSimply open attached .blend file and hit F12\n\n[render_test2b_delmesh3_simplified.blend](render_test2b_delmesh3_simplified.blend)", "Using another Mesh for Texture Indices (Texture Space / Generated Texture Coordinates)\nOperating system: Windows 10\nGraphics card: Geforce GTX1060\n\nBroken: 2.80.74 and 2.91.0 Beta\nWorked: Blender 2.79b Date: 2018-03-22 14:10 Hash: `f4dc9f9d68b`\n\n\nThe option \"Texture Mesh\" in the \"Texture Space Panel\" of the \"Object Data Properties Tab\" has no effect if the mesh does not have a deform type modifier.\n\n|\n| -- |\n|File is [here ](GeneratedTextureCoordinates4.blend?dl=0).\n\n\n- Open attached file - (Note that the geometry of one mesh affects the texture coordinates of the other)\n- Go to the modifiers tab and disable or delete the modifier\nTexture Mesh has no effect.\n[texspace_texture_mesh_bug.blend](texspace_texture_mesh_bug.blend)", "Particle Texture influence broken when using two particle system on the same object\nOperating system: Ubuntu 18.04\nGraphics card: GeForce 970GTX\n\nBroken: 2.90.1\nWorked: Never (2.8+)\n\n\nWhen using two particles system on the same object with an influencing texture, one particle system has a wrong influence (e.g. Particle System shrink to quickly)\n\nBlend File: [particle_texture_bug.blend](particle_texture_bug.blend)\n\n0. Set the animation start and end to 100 - 200\n1. Create an Emitter and a Particle Object\n2. Add a Particle System to the Emitter and use the Particle Object for rendering\n3. Set the Start and End to 100 - 200\n4. Give the Particle System a Blend Texture that influences the size with \"Strand/Particle\" as Coordinates\n5. Add another System and Duplicate the previous one to get the exact same setting\n6. Change the Start and End of the new System to 0 - 100\n7. Bake all Dynamics\n8. Render Frame 199 and compare to rendering of 101. The particles in 199 are tiny in comparison (or invisible). They should look near identical\n\nOptional: \n9. Remove the 0-100 Particle and Redo Baking\n10. Frame 199 now has normal sized particles\n", "Huge memory consumption by studio HDRIs previews\nOperating system: MacOS 10.14.5\nGraphics card: Intel UHD Graphics 630 1536 MB\n\nBroken: 2.91 d8585e184a\n\nGrab a texture file of 10-20 MB size. \nPut it in \"~/Library/Application Support/Blender/2.91/datafiles/studiolights/world\". Duplicate the texture file around 10 times.\nOpen Blender, open preferences, lights tab. \nSee memory increase.\n\n\n", "\"Texture properties\" tab hidden after creating \"New Scene\"\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\nGraphics card: GeForce 1080 Ti\n\nAfter adding a New Scene in Blender, the Texture properties tab in the Properties window is missing.\n\nSee my attched image to reproduce the error in detail, please.\n\n1. Start with empty scene\n2. Add a New Scene inside your scene by creating a \"Scene.001\"\n3. Texture properties are hidden in \"Scene.001\"\n\nThis happens in v2.82 too.\n\nIs this a bug or do I miss something, please?\n", "AutoDepth ignores texture transparency\nOperating system: Win 10 64-bit\nGraphics card: 980 Ti\n\nBroken: 2.93.4 LTS, 3.0 alpha (including current latest build)\nWorked: 2.79\n\nWhen navigating using mouse with auto-depth enabled, the full-transparent parts of textures should be ignored when picking the depth.\nThis worked correctly in 2.79, but 2.93 and the latest 3.0 alpha seem to ignore this.\n\n\nEnable Auto-Depth, create an object, assign it a material with some full-transparent texture, then try to zoom / pan using mouse with the cursor on it.\n[autodepth-transparent-issue.blend](autodepth-transparent-issue.blend)", "Implement drag and drop in ID text fields (ID name and/or paths)\nWindows 7 x64\n\nBroken: 705c43b\n\nwhen drag dropping images in the texture node's path field, it should replace the current texture name with the dragged and dropped one, but instead it does like if you dropped in empty space and adds a new texture node.\n\nOpen attached file, replace one of the windows with a file browser in a location where you have some images. Then drag that image over the texture name filed of the texture node. Tooltip shows that the field is recognised correctly by changing from 'add new node' to 'paste name'. But if you drop, it will do as if you dropped in empty space and add a new node.[bug drag and drop tex node.blend](bug_drag_and_drop_tex_node.blend)\n\n", "Cycles does not respect the texture alpha mode\nOperating system: Gentoo Linux \nGraphics card: AMD 290x\n\nBroken:\n2.79b\n2.80 f15205b93f56e454b76d5a222fdb9a9665b99907 2018-01-02\n\nEevee respect the alpha mode in the texture settings, however cycles does not.\n\n[alpha_test_pack.blend](alpha_test_pack.blend)\n\n1. Load the attached .blend file\n2. Change the texture settings for the `Alpha:` setting for the image texture node (with use alpha on).\n3. Notice that in cycles the `Alpha:` setting has not effect, the texture alpha is always premultilied.", "Grease Pencil: unable to change erase size while using the Draw tool\nOperating system: Linux-5.19.0-76051900-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.47, 5.19.0-76051900-generic) AMD 4.6 (Core Profile) Mesa 22.0.5\n\nBroken: version: 3.5.0 Alpha\nWorked: ???\n\nCan't change the size of the eraser brush while erasing while using the draw tool (`Ctrl + LMB`), I can do it with the scroll wheel on the mouse but not with the shortcuts assign for it `[]`\nAlso applies to annotation tool.\n\n- go to greasepencil draw mode\n- draw something\n- hold control to erase\n- try to change the size of the eraser brush while erasing (Either scroll wheel or brackets)", "Remove normalization from original coordinate attribute (CD_ORCO)\nFrom #95776:\n\n> The internal CD_ORCO attribute is normalized to 0..1 which is not really helpful, not even as default texture coordinates. It would be good to do some refactoring so these are stored unnormalized and then applying any additional texture space scaling for rendering only.", "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?", "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", "Rendering with F12 does not consider the different resolutions in each scene\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: ATI Radeon HD 5750 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.4.0 Alpha\nWorked: I don't know, but even it never worked, it doesn't mean it is correct :)\n\nRender (F12) does not respect **Render Layer** node dimension\n\nI have two scenes with different dimension\n- Scene 1080 px - for rendering scene\n- Scene 2160 px - for compositing scene 1080 px\n\nScene 1080 rendered by pressing render icon at **Render Layer** node result correct with expected mix in compositor of Scene 2160 ...\n\n\n\n... but rendering by pressing **F12** in Scene 2160 renders Scene 1080 also in 2160 px (so compositor fails in result).\n\n\n\nFor more info or sample file see 2214\n\nI hope it is would be something small to fix. \nThank you for your time.\n\n- Open attached file\n- Compare rendering with F12 (which should render the two scenes at different sizes) with rendering using the render button on node\n[bse275864_OneScene.blend](bse275864_OneScene.blend)", "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" ]

[ "Texture limit size not working\nOSX 10.11.6\nIntel Iris 1536\n\nBroken: 2.80.0 #26d5a3625ed\nWorked: 2.79b\nChanging texture limit in the preferences doesnt have any effect in the viewport.\n\nunwrap model and add material with image texture. Open settings > general > change texture limit enum has no effect." ]

[ "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", "Error in Message of Linked data is Missing\nOperating system: Ubuntu 20.04\nGraphics card: Geforce MX230\n\nBroken: 3.6 beta\n\nThe message about the lost linked data mentions Proxies that have been removed since 3.0. Perhaps it should be replaced with \"Library Overrides\"? The error is not only in the pop-up window, but also in the Info editor\n\n\n\nOpen this file\n[bandit_anim_2.blend](attachment)\n\n", "Performance issues when moving bones of an armature when the Outliner is set to Blender file\nBroken: 2.93\n\nThis happens on heavy scenes and with many linked files, if you have an Outliner opened and set to \"Blender file\".\nThe fps drops dramatically only when trying to move a bone of an armature. It doesn't matter the complexity of said armature.\nThe problem stops happening after closing the Blender file Outliner.\nCould it be related to this other fix? T87842", "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", "Object Info Random - inconsistent result\nOperating system: Win10 64\nGraphics card: gtx1050ti\n\nBroken: 2.79, 2.8\n\n*Random* output from **Object Info** depends on every object in scene, even *Empties*!\nThere are two identical scene sets with linked objects, but *Empty* belongs to *Scene.001* only. *Cube* is instanced via duplifaces and *Random* produces different result if *Empty* isn't linked in both scenes.\n\nOpen file, viewport render Scene and Scene.001\n[Obj_info_Random_out.blend](Obj_info_Random_out.blend)", "Can't edit new driver on an overriden property on a linked object with no animation data\n## Simplified Report\n\n- The following file contains an object with no animation data.\n- Link the object to a new file and make a library override from it.\n- Add a new driver on one of its location channels.\n- Notice that driver options are grayed out and can't be edited.\n- One expects to be able to edit the driver since the object has no animation data. \n\n[libraryFileWithNoAnimationData.blend](libraryFileWithNoAnimationData.blend)\n\n## Original Report\n\n\nOperating system: Linux-5.15.60-1-MANJARO-x86_64-with-glibc2.36 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.65.01\n\nBroken: version: 3.3.0\nWorked: ??? I could have sworn this worked in 3.2 but it seems to have the same behavior. Same in 2.93.\n\nUsing drivers with overridden properties is not really usable. I can add a driver, but then I cannot edit it.\n\nLink a collection into a file and make a library override. Right-click on a property and choose \"Add Driver\".\nRight click on the property (which should turn purple) and then choose \"Edit Driver\" Notice that the\ndriver's controls are all blurred out! You can't edit them in the UI.\nIt gets worse!\nOpen a driver-editor window so you can watch what happens in the next step, and select the driver you\njust created- open the \"Drivers\" tab in the window. Look at the expression.\nIn the main window (not the driver window), click on the driven property and type ~~\"#1\" - when you\nprepend a hash symbol, that tells Blender to edit the expression of a driver (it's a handy way to make\nnew drivers with simple expressions. Try it at home!)~~ **edit: it looks like you don't need the hash when it is already driven.**\nNow, notice the expression change in the driver window that you aren't normally able to edit!\nI have also confirmed that you can edit some properties with the Python API that you cannot edit in\nthe user interface.\n\n**My Thoughts** (If you're interested)\nI do not know if the design for overrides is intended to support using drivers like this. It feels a little squishy\nbecause I don't know if Blender will keep the driver around when I resync the override. On the other hand, it's\nreally handy when doing animation that is easier to do programmatically, such as causing a bone to oscillate\nwith sine-waves (e.g. a plant waving with the wind). Sometimes I use a driver to bake keyframes - so I set up the\ndriver and then bake its motion to an action, and get rid of the driver. It is my opinion that driver support is\nnecessary for overrides, because it's something I expect to be able to use, as an animator. I don't know if the\nold Proxy system supported drivers, though.\nAt any rate, if it is blocked from editing in one place, it should be blocked from editing through the API, too.\n\nI apologize if this is a known issue. I don't see any similar bug reports but it appears things have been like this\nfor a while.", "Wrong result mixing 2 nodes of an image texture\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.3, 2.93\nWorked: unsure\n\nWhen using 2 nodes of the same texture and connecting the Color output from one and the Alpha from another, the result looks different in comparison when using both outputs from one node. Broken in EEVEE\n\n1) Open the file, switch to material preview/rendered\n2) Reconnect the color (or the alpha) link to another texture\n[Bug1.blend](Bug1.blend)", "Having too much hair particles creates visual glitches\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: not really sure, but it may have been in blender for some time\n\nHair strips gets a really bad distortion once they reach a certain threshold of number, children and \"additional subdivisions\"\n\n\nUsing a ball with 2 subdivisions:\n\n| 1 | Furball with hair strips, 0 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| -- | -- | -- |\n| 2 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 80 interpolated children |  |\n| 3 | Furball with hair strips, 1 additional Subdivisions, 20000 particles and 60 interpolated children |  |\n| 4 | Furball with hair strips, 1 additional Subdivisions, 18000 particles and 60 interpolated children |  |\n| 5 | Furball with hair strands, 1 additional Subdivisions, 18000 particles and 60 interpolated children (hair gets scrambled where the glitch is happening) |  |\n| 6 | Furball with the exact same configuration as the first glitchless one, but with 3 Strand steps on Viewport Display instead of 2 |  |\n\nSo it seems like a mix of a lot of segments and a lot of particles create those glitches.\n\nThe file bellow contains the furball with the second configuration\n[furball.blend](furball.blend)\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", "Cycles does not generate the exact same images when a scene is rendered twice\nOperating system: Ubuntu 20.04\nGraphics card: Nvidia 2070 Super\n\nBroken: master\nWorked:\n\n\nThe results generated by Cycles are not 100% deterministic.\nAs a consequence path guiding ( #92571 ) can not be implemented deterministically.\n\n\n1. Start Blender and open a scene like `monster`\n2. Render the scene with 64spp and store the result as exr image (e.g., monster-run-0.exr).\n3. Repeat 1. and 2. and save the result as exr again (e.g., monster-run-1.exr).\n\n4. Use an image comparison tool such as tev (tev) and compute the difference. \n\nYou will see that, even if both renderings were performed on the same machine, the resulting images have minor differences.\nNote: It might be necessary to scale the diff-images to see the errors.\n\nRun 0:\n\nRun 1:\n\nDiff:\n\n\n\n\n\n\n \n\n\n \n\n \n\nBased on the default startup or an attached .blend file (as simple as possible).", "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", "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.", "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", "Curve \"solidify\" modifier glitch\nOperating system: Windows 7\nGraphics card: GT750M\n\nBroken: 2.80, 2019-02-28\nWorked:\n\nWhen applying a \"Solidify\" modifier to a bezier curve shape (or imported SVG), it creates random height vector points, creating strange triangles. This can be fixed by simply selecting the errored vector point then selecting one of the transform value (in my case it was Y) in the panel and either pushing enter (keeping the same value) or unselecting the vector point.\n\n\nAttached blend file with imported SVG.\n\n", "Grease pencil object in some cases look like low poly.\nOperating system: Linux-4.4.0-176-lowlatency-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 435.21\n\nBroken: version: 2.83 (sub 11)\nWorked: 2.82 (sub 7)\n\nIn some cases GP objects looks blocky, like a low poly objects.\n\nOpen attached file and render it.\nCompare render result with previous worked blender version.\n\n\n[2.83_bug.blend](2.83_bug.blend)\n" ]

[ "Collection instances controlled by proxy armatures sometimes have the instancing empties transformation applied\nOperating system: Linux-5.3.0-29-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.81 (sub 16)\nWorked: Works fine in 2.80\n\nA rigged object is linked into a scene, and a proxy armature is created and animated. When rendered, there are glitches in some random frames, where the object moves out of position.\n\nSee the attached production/scenes/scene02 .blend file. The cow is rendered with glitches. [bug_render_glitches.zip](bug_render_glitches.zip)\n\n----\n\nEdit: updated test file: [production.zip](production.zip)\n\n" ]

[ "Outline of plane in Object mode does not Render after applying transforms\nBroken: Current main.\nWorked: N/A.\n\nOutline of plane in Object mode does not Render after applying transforms and looking Down the plane in top down view or any view.\n\n1. Delete the default cube.\n2. Add a Plane.\n3. Numpad 7 for top down view.\n4. selct the plane and rotate on x axis 90 degrees\n5. Apply all transforms.\n\nFrom Blend File Just Select the plane and press numpad 7 to go to Topdown view and Out line should stop rendering.", "Rigid body : the animation of the angle constraint parameters does not work with an animated object\nOperating system: windows 10\nGraphics card: gtx 1070\n\nBroken: 2.92\nWorked: don't know \n\n\nRigid body : A rigid body \"animated\" object + a another rigid body object connected with hinge rigid constraint. The animation of the angle constraint parameters does not work with an animated object. I have bugs sometimes also with other parameters like breakable . (see the blend)\n\n[rigidconstraint.blend](rigidconstraint.blend)\n\n", "Rolling the viewport always use last selection as pivot point\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 496.49\n\nBroken: version: 3.1.0\n\nWhen using the navigation setting Orbit Around Selection and Auto Depth, rolling the viewport always use the last selection as the pivot point, even when nothing is selected.\n\nThe expected behavior should be the same as having the orbit around selection disabled, when nothing is selected the rolling should pivot around the center of the screen.\n[blender_roll_bug.mp4](blender_roll_bug.mp4)\n\n1. Activate orbit around selection and auto depth in the navigation preferences\n2. Bind view3d.view_roll in the keymap using roll angle\n\n3. Select an object and roll the viewport\n4. De-select the object and roll the viewport again, the pivot remains in the same place\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.", "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)", "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", "Delete Geometry node face mode behaves unexpectedly when used after Join Geometry\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.2.1\nWorked: N/A (problem exists on 3.1.2)\n\n\nNot sure if this is by design, but I find that the following behaviour unexpected:\n\n- By itself, a Mesh Line output connected to Delete Geometry + Geometry Proximity node using Face mode won't delete anything.\n- However, when such a Mesh Line is joined with a Grid primitive, then Delete Geometry + Geometry Proximity in Face mode will cause all of Mesh Line to be deleted, regardless of distances.\n\n\n\n\n\n\n\n\n- Download the blend and observe Mesh Line is preserved.\n- Unmute Grid node link to Join Geometry, and observe Mesh Line is now gone.\n\n[line-deletion.blend](line-deletion.blend)\n", "context override for bpy.ops.view3d.view_selected doesn't work\nBlender 3.6\n\nTried to override currently selected items and run `bpy.ops.view3d.view_selected` (default blender operator binded on \"Numpad .\" by default) and it doesn't work. If I select objects manually with `obj.select_set(True)` it works.\n\nI've compared context's dict produced by `bpy.context.copy()` - the only difference between the context after `.select_set` were `selected_objects`, `selected_ids`, `selected_editable_objects` and I've overidden them.\n\nWay to reprodiuce:\n1) Open default blender scene.\n2) Make sure nothing is selected and move camera away.\n3) Run the code below - nothing happens\n4) Uncomment first two lines of code - operator works.\n\n```python\nimport bpy\n\n#for obj in bpy.data.objects:\n# obj.select_set(True)\n \nfor area in bpy.context.screen.areas:\n if area.type == 'VIEW_3D':\n for region in area.regions:\n if region.type == 'WINDOW':\n override = {\n 'area': area, \n 'region': region\n }\n override['selected_objects'] = bpy.context.view_layer.objects[:]\n override['selected_ids'] = bpy.context.view_layer.objects[:]\n override['selected_editable_objects'] = bpy.context.view_layer.objects[:]\n with bpy.context.temp_override(**override):\n bpy.ops.view3d.view_selected()\n # print(bpy.context.copy())\n```\n\n", "Viewport Z-Bias & retopology overlay related issues\nSince this is being reported frequently and retopology overly has caused some weird issue with mask display as well previously, it's best we keep track of them in a central place so we could check if any particular fix is working for all situations:\n\n------\n\nProblem still presents:\n\n- Retopology overlay affecting other parts of the drawing/picking operation: #109115 #107768 ~~#109277~~ ~~#107411~~\n- (Potentially related) Selecting when X-Ray turned on is not visually effective and then switching to face mode crashes: #110136\n\n------\n\nFixed:\n\n- ~~Wireframe visible in close distances: #110048 #109040 #109514 #109499 #109685~~\n- ~~Retopology overlay 0 z offset problem: #109662~~\n\n-------\n\nProbable cause:\n\nAs suggested in 107768#issuecomment-937545 , I believe the problem here is that\n\n1. `DRW_object_is_in_edit_mode` does not exclusively check if object is in edit mode, but it combines other logics that affects drawing and stuff.\n2. `XRAY_ENABLED` marco is not always accompanied with `RETOPOLOGY_ENABLED`, this leads to inconsistencies in the user interaction and the display.", "Geometry based lights do not generate shadow on a shadow catcher surface\nOperating system: Windows 10\nGraphics card: RTX 3060\n\nBroken: 3.0.0 and further versions\nWorked: (2.93.10 LTS)\n\nGeometry based lights do not generate shadow on a shadow catcher surface.\n\n- Open attached file\n- Switched to viewport rendering\n[#103795-3.blend](T103795-3.blend)\n\nBlender 2.93 LTS:\n\n\nBlender 3.x:\n", "Lattices don't display selected vertices with modifier \"Edit Mode\" enabled\nSince 2.8x, lattices have not been displaying selected vertices when the modifier option \"Edit Mode\" id enabled.\n\nThis is easy to test:\n\n- add a new lattice object\n- add a wave deform modifier.\n- enter edit-mode.\n- enable \"Edit Mode\" toggle for the modifier.\n\nThis test file shows the problem too, open it and toggle the \"Edit Mode\" modifier button.\n\n[#77184.blend](T77184.blend)\n\n----\n\nReporting this to keep track of the issue: `BKE_lattice_modifiers_calc` is making a copy of the lattice `lt_eval` which doesn't contain an edit-lattice, which is then used for drawing.", "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", "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).", "Geometry nodes preview, clipping Region in the viewport its not working\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nTo be compleatly honest i don't remember if this was a limitation of the preview node or not and i was unable to find the answer. \nSo as the title says viewport clip in viewport doesn't work in the geonodes overlay preveiw\n\n\n- Try to preview any data from geometry nodes. \n- alt+b to do a viewport clip\nshould look like in the left side of the image above, but it seems that a second geometry with the info from geo nodes in alpha blend mode its not being clipped \n\n", "Subdivided surface preserves mesh UVs and vertex colors when not needed\nThis code causes UVs and vertex colors to always be preserved through the modifier stack.\n\n```\n /* this wasn't in 2.63 and is disabled for 2.64 because it gives problems with\n * weight paint mode when there are modifiers applied, needs further investigation,\n * see replies to r50969, Campbell */\n#if 0\n CustomData_set_only_copy(&dm->loopData, mask->lmask);\n CustomData_set_only_copy(&dm->polyData, mask->pmask);\n#endif\n```\n\nFor simple solid shading these are not needed, and `ED_view3d_datamask` should take care of requesting them when needed, taking up memory and CPU time.\n\nHowever, there is currently an issue where switching shading modes does not reevaluate the dependency graph to add these data layers, so just re-enabling this code is not enough to fix this. See also #63595 (Generated texture coordinates missing when switching from solid to rendered mode)." ]

[ "Fade Geometry state changes selectability\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86\n\nBroken: version: 2.83 (sub 10)\n\nWith Fade Geometry enabled, other objects can not be selected while in pose mode.\nWith Fade Geometry disabled, other objects can be selected while in pose mode.\n\n[#70907.blend](T70907.blend)\n\n- Open file\n- Try clicking on bone and cube - selected item and interaction mode should be changed\n- With the bone selected and in pose mode: in Viewport Overlays, check Fade Geometry\n- Repeat step 2 - once in pose mode, cube can not be selected\n\n\n" ]

[ "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", "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", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Eevee: Unknown bug when just create first shader \nStep to reproduce an issue (or bug?):\n1. Run latest Blender v3.4alpha (Experimental build) with Eevee Next integrated.\n2. Create scene with just one Cube.\n3. Go to Properties > Material panel > Create New material.\n4. Boom! Blender shut down imidetily.", "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", "Blender Crash when deleting images too fast\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: AMD Radeon(TM) Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.44 30.0.13044.0\n\nBroken: version: 3.2.0\n\nBlender crashes when deleting images in the Layer blend file libery\n(3.3 alpha is crashing also and i didnt found any report about this issue)\n\n\n* go to outliner -> select blend file\n* make sure to be in the material preview mode\n* delete the first image by right click and then click on delete image\n* (now u only need to rightclick and leftclick to delete next images, because u dont need to aim for the delete anymore)\n* delete images while blender tries to preview the last change after deleting one of the images\n blender crashes\nwhen deleting images too fast, my blender just crashes (happens on my bad pc often, because i download models and rework them)\nIf you wait for the new material preview of the model after deleting nothing happens, but if you dont blender crashes when continuing to delete images\n\nVideo: CvO9nw4qilc\n\n[pharaoh x suite.blend](pharaoh_x_suite.blend)\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)", "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)", "\"RENDER_OT_render\" called with \"EXEC_DEFAULT\" freezes Blender with Eevee motion blur enabled\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.67\n\nBroken: version: 2.90.0 Beta\n\nbpy.ops.render.render() called without 'INVOKE_DEFAULT' from the Python Console or script freezes Blender when Eevee motion blur is enabled.\nAnd the same issue is in the 2.91 Alpha version.\n\n----\n\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Open Python console\n- type in bpy.ops.render.render() and hit enter\n\n----\n\n*Edit* (added method that doesn't activate via Python).\n\n**Exact steps to reproduce the error without activating from Python.**\n- Open Blender\n- Make sure context scene render engine is Eevee\n- Turn on motion blur\n- Run this script in the text editor\n\n\n```\nimport bpy\ndef menu_func_import(self, context):\n layout = self.layout\n layout.operator_context = 'EXEC_DEFAULT'\n layout.operator(\"render.render\", text=\"Blocking Render\")\nbpy.types.TOPBAR_MT_render.append(menu_func_import)\n```\n\n- Run \"Render -> Blocking Render\" from the top-bar.", "EEVEE: Crash if computation is too heavy for the system (TDR issue)\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\n\n\nBroken: version: 2.80 (sub 72)\nWorked: (optional)\n\n\nAny time I try to render an image sequence in any format in Eevee, it constantly crashes the whole program on the first frame. I was able to render before until I changed some camera location animations and adding a focusing animation. As well as changing the camera sensor size. I am rendering in 4K I have attached the log file.\n[blender_debug_output.txt](blender_debug_output.txt)\n\n[blender_system_info.txt](blender_system_info.txt)\n\n[NebulaV2.blend](NebulaV2.blend)", "Blender 3.2.1 / 3.4 - Cycles - Persistant Data and Motion Blur artifacts on GPU\nOperating system: Windows 10, Ubuntu 21.04\nGraphics card: GTX 1080, RTX 3080\n\nBroken: 3.2.1, b5e92c3dfe\nWorked: 2.79\n\nPersistant data is bugs out during renders sometimes.\n\n1. Open attached blend file in Blender 3.2.1\n2. Press f12\n3. Press right on the keyboard (frame 771)\n4. Press f12\n5. Press right on the keyboard (frame 772)\n6. Press f12\n7. Notice how its not as expected.\n8. Press f12 without framing forward\n9. Notice how it is fine\n\ngood\n\nbad\n\n\nThis means when rendering animations, it can produce frames which bad, which then require more re-renders.\n\nWindows and Linux have both been tested and results are the same.\n\nTested CUDA, Optix and both have issues. CPU renders fine. \n\nDisabling Persistant Data renders fine.\n[bug.blend](bug.blend)\n\nNOTE: We had #95475, #96822 already for Persistent Data and Motion Blur issues (these should be fixed), I can repro this case though.\n\nEDIT:\nAs another task #100729 has been merged into this file, there is another test file [BUG.blend](BUG.blend)\n", "Burned Out Screen Space Reflections in Eevee Viewport - Nvidia GT 750M\nOperating system: macOS 10.14.3\nGraphics card: NVIDIA GeForce GT 750M 1024 MB\n\nBroken: 2.90.0\nWorked: 2.79\n\nIn some cases I detected that the Screen Space Reflections in Eevee Viewport gets out of control.\nA few seconds after switching to the viewport (even when viewport samples are set to 1) the issue kicks in and – as the sampling continues – an increasing percentage of the reflections get totally white.\n\n\n\nThe renders are correct.\nSurfaces affected by reflection planes are correct.\nHiding the chandeliers meshes solves the problem. Switch tab and back for this to work.\n\nI was able to strip down the scene and identify the source of the problem: Originally I set up the glass material with \"multiply\" blending. This was converted (when opened with belnder 2.82 alpha) to a \"Shader to RGB\" and a \"Transparent BSDF\" node. [1]\n\nThe \"Shader to RGB\" causes the problem in 2.82.\nThe \"multiply\" blending of the material causes it in 2.8.\n\nOpen the attached file.\nSwitch to LookDev or Rendered viewport.\nWait.\n\n[Chandelier.blend](Chandelier.blend)", "Regression: Screen Space Reflections on EEVEE render shaders with roughness a minimum regardless the value or map in the shader\nOperating system: Linux Manjaro \nGraphics card: Geforce 590\n\nBroken: 3.2 and succeeding versions\nWorked: 3.1\n@Tyson-Marchuk found the first bad commit: 80859a6cb2\nAlso mentioned the potential fix: #102423#1459379\n\nScreen Space Reflections on EEVEE render materials incorrectly\nThe shaders roughness valuue or map are ignored and all shaders are render \n| 3.3.1 (SSR off) | Broken: 3.3.1 (SSR on) | Worked: 3.1.0 (SSR on) |\n| -- | -- | -- |\n|  |  |  |\n\nThe problem became evident in a scene with medium or high roughness by enabling the Screen Space Reflactions\n\n[SSR.blend](SSR.blend)", "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", "Eevee: Occasional render glitches when using attribute node\nOperating system: Linux, specifically KUbuntu with X11\nGraphics card: RTX 3080 (Driver Version: 530.30.02, CUDA Version: 12.1)\n\nBroken: 2.93 - 4.0.0 Alpha, 2023-06-29, f47eed749eaf\nWorked: 2.92 (as available on Steam)\n\nUsing an attribute in an Eevee material causes occasional but severe render glitches. This does not happen consistently on any particular frame. It does not happen when rendering from the command line with `--background`.\n\nTo reproduce, render an animation with the attached Blender file. One in every 50 frames or so are corrupted. Occasionally it gets most of the way through the animation before ever producing a bad frame.\n\nThis file is basically the startup file with two changes:\n1. An attribute node with the name set to \"Color\" is plugged into the base color on the default material.\n2. The sample count is lowered to one. (The issue persists without this, but with a higher sample count, some samples glitch and others do not. The final image is a mix of the glitched and regular samples.)\n\nI have ensured that this is not a problem with my particular Blender settings by deleting everything in `~/.config/blender/4.0/config` and selecting \"Save New Settings\" in the splash screen before opening and rendering the file in the 4.0.0 alpha.\n\nNormal frame:\n\n\nCorrupted frame (as rendered in 2.93, some other versions simply display a transparent hole where the cube was without affecting the background):\n\n\n" ]

[ "2.90 : Crash on minimize window while rendering sequence w/motion blur (EEVEE)\nOperating system: Windows 10 \nGraphics card: RTX 2060 Notebook\n\nBroken: 2.90.0 alpha\nWorked: 2.83 LTS\n\nMinimizing Blender's window while rendering a sequence in EEVEE crashes in 2.90 and motion blur is on. Seems to perhaps only crash if each frame takes beyond a certain amount of time to render. Sometimes minimizing is not even necessary, and it just crashes in place on frame 2.\n\nStart Blender.\nCheck \"Motion Blur\" and increase the \"motion blur steps\" to 16+.\nRender Sequence as MPEG-4 output.\nMinimize both windows/show desktop at any point during rendering for crash. If no crash, restore Blender workspace window for crash.\n\nSorry if this isn't enough information to reproduce it properly, this is my first bug report and it's mostly motivated by primal rage. This is very dependable on my end and I've gotten it to go off every time by following these steps.\n\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF899C4404D\nModule : python37.dll\nThread : 00000b1c\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF899B76424\nModule : python37.dll\nThread : 00002a48\n\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF899B76424\nModule : python37.dll\nThread : 00000e1c\n", "Render crash with EEVEE on extreme motion blur values\nOperating system: Windows 10 1909 18363.900\nGraphics card: AMD Radeon R5 M330 with Radeon Software 20.5.1\n\nBroken: 2.90.0 Alpha, branch: master, commit date: 2020-07-02 07:29, hash: 22197d7f8a26\n\nWhen rendering with really high values of shutter, max blur and steps, blender occasionally crashes.\n\nPress \"render image\" a few times in the given file. This occurs rather occasionally, usually taking between 3-5 images rendered. \nI have tried reproducing it on linux (Ubuntu 20.04), and the crash does occur, but much more occasionally - taking between 15-20 images instead.\n\nI think this could be related to #78483\n\n[2020-07-02 15-05-42.mp4](2020-07-02_15-05-42.mp4)\n[blender_debug_output.txt](blender_debug_output.txt)\n[blender_system_info.txt](blender_system_info.txt)\n[test.blend](test.blend)", "(Blender 2.9 Alpha bug) Blender keeps closing when rendering (not so big) animation! (Object Motion Blur Issue)\n**System Information** \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.12\n\nBroken: version: 2.90.0 Alpha\nWorked: (2.83 worked! its not a newer version, but older.)\n\n**Short description of error** (wont be so short, sorry!)\nI am rendering an animation for an animation collab i've been doing with a friend, and i have been using Blender 2.9 for object motion blur and i've been loving it so far! However when i render the animation, blender crashes without anything, just instant close in the middle of the rendering. Had only two successful renders so far. And i've been rendering an 89 frame animation today and it has been crashing since morning. I've tried soo many times. I've tried freeing up my Windows (C:) if that had anything with it, nope. Deleted some programs, nope. I got super stressed about it maybe being something with my PC, but then just to make sure i went back to Blender 2.83 and render the same animation, and it didnt crash once! I rendered the animation multiple times to make sure and still didnt crash.. \n*(I have just checked to make sure you guys get more information, it seems to work when i disable motion blur! Tried without it and it worked, but then tried it with opening the motion blur again afterwards and it crashed)*\n\nI made an animation. I opened motion blur on 2.9 since it has object motion blur, and it keeps crashing non-stop :( Thought it was about my computer, doesnt seem to be so far. More about the motion blur.\n\nBlend File: [miiski2das2.blend](miiski2das2.blend)\n\nIf you need any more info let me know! \n", "Crash when rendering animation with new Eevee Object Motion blur\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\nWorked: Blender 2.83 with old motion blur\n\nWhen rendering all frames in a scene in Eevee with the new object motion blur Blender consistently seems to crash somewhere during the render with the number of steps set to two or more.\n\n1. Open startup file\n2. Enable Motion Blur with the number of steps set to 2 or more\n3. Render the full animation\n4. Blender crashes\n\n[blender.crash.txt](blender.crash.txt)\n", "EEVEE animation render crashes periodically \nOperating system: Linux-4.15.0-108-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 440.100\n\nBroken: version: 2.90.0 Alpha\n\nWhile rendering an EEVEE scene with fog and motion blur, blender keeps crashing every 100 frames or so. \n\nOpen the file and render animation\n\nBacktrace produce\n# Blender 2.90.0, Commit date: 2020-06-30 20:02, Hash a3e6b7c2ce06\nbpy.context.scene.frame_start = 1378 # Property\nSaved \"fatest.blend\" # Info\n\n# backtrace\n/home/ashehata/Applications/blender-2.80-dev/blender(BLI_system_backtrace+0x33) [0x69d1103]\n/home/ashehata/Applications/blender-2.80-dev/blender() [0xc10236]\n/lib/x86_64-linux-gnu/libc.so.6(+0x3ef20) [0x7fa4298dbf20]\n/home/ashehata/Applications/blender-2.80-dev/blender(_PyFrame_New_NoTrack+0x17) [0xc02397]\n/home/ashehata/Applications/blender-2.80-dev/blender() [0xc02010]\n/home/ashehata/Applications/blender-2.80-dev/blender(_PyEval_EvalFrameDefault+0x88dc) [0xc0b9dc]\n/home/ashehata/Applications/blender-2.80-dev/blender() [0xc02050]\n/home/ashehata/Applications/blender-2.80-dev/blender(_PyFunction_FastCallDict+0x2a6) [0x56b7d46]\n/home/ashehata/Applications/blender-2.80-dev/blender() [0x12455f4]\n/home/ashehata/Applications/blender-2.80-dev/blender() [0x12034d7]\n/home/ashehata/Applications/blender-2.80-dev/blender(ED_region_header_layout+0x13d) [0x126693d]\n/home/ashehata/Applications/blender-2.80-dev/blender(wm_draw_update+0x35d) [0xec74cd]\n/home/ashehata/Applications/blender-2.80-dev/blender(WM_main+0x30) [0xec5430]\n/home/ashehata/Applications/blender-2.80-dev/blender(main+0x33c) [0xb49a3c]\n/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7fa4298beb97]\n/home/ashehata/Applications/blender-2.80-dev/blender(_start+0x2a) [0xc0c63a]\n\n[fatest.blend](fatest.blend)", "Eevee Motion blur crash rendering animation with steps set to higher value\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.90.0 Alpha\n\n\nBlender crashes while trying to render an animation with Motion Blur enabled and wildly spinning cube in it. Apparently Steps value playing a role in it, since crash happens when I set Steps to anything above 4 increasingly faster - if on 5 it will render ~40 frames, on 16 steps it's rarely passing father than 15th frame. \n\n1. Open a file:\n\n [cube2.blend](cube2.blend)\n\n2. Press CTRL+F12\n", "Blender crashes when rendering EEVEE animation with motion blur\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0 Alpha\nWorked: Since 2.90 just added motion blur for EEVEE, I don't know if this applies)\n\n[Blender crashes when rendering this simple camera move when rendered in EEVEE with motion blur turned on. When turned off, it renders fine. Also renders fine in Cycles. I adjusted a couple of settings under Motion Blur, but it crashed regardless.]\n\n[1. set start and stop frame; 2. select EEVEE; 3. Check \"Motion Blur\"; 4. click Ctrl-F12.{[F8648726](montage_bug.blend)}]\n\n" ]

[ "Dynamic Paint With UNDO [Control Z] Crash Blender\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen Press Control Z While In Weight Paint (EDIT MODE), Blender Crash\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[weight-paint-v1.blend](weight-paint-v1.blend)\n1. Open the provided .blend file\n2. Start playback and enter Weight Paint mode\n3. Paint and then undo (Control + Z)\n4. Blender crashes after a while,\n\nHere is video to show case KUUbxSnwmbE", "Blender crashed in edit mode with material index creazy and strange normal\nOperating system: Linux pop-os 5.17.5-76051705-generic\nGraphics card: NVIDIA GeForce RTX 3060 Ti\n\nBroken: 3.1.0 / blender-3.2.0-stable+v32.e05e1e369187-linux.x86_64-release\n\nAn object imported from I don't know where, with crazy material_index : (-30086) in spreadsheet editor, and with strange normal, makes blender sik.\n\nIn edit mode, if I try to move the concerned geometry blender crashes systematically.\n\n[2022-06-16_bug-normal.crash.txt](2022-06-16_bug-normal.crash.txt)\n\n[2022-06-16_bug_system-info.txt](2022-06-16_bug_system-info.txt)\n\n[2022-06-16_bug-normal.blend](2022-06-16_bug-normal.blend)\n\nthank you,\n - Thomas", "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", "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", "Remove and re-add the rigid body world causes Blender to crash.\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\nWorked: I dont know.\n\nWhen the physical world is removed and added again, playback will cause the program to crash.\n\n\n1. Download the 2.blend and open it.\n2. Play 5 frame.\n3. Click the Remove Rigid Body World button.\n4. Click the Add Rigid Body World button.\n5. Click the rigid body world setting Collection. Then select RigidBodyWorld .\n6. Click the rigid body world setting Constraints. Then select RigidBodyConstraints .\n7. Move to 1 frame.\n8. Play 5 frame. Blender will crash immediately.\n\n[2.blend](2.blend)", "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", "Error reporting in modifiers\n[D11591: Alembic: import arbitrary attributes](D11591) adds some error reporting for attribute reading. It would be nice to formalize this, and extend it to be applicable in other areas, Alembic I/O or otherwise.\n\nOne area of improvement would be to stop outputting to the console while telling users to look it: on some platform, or depending on how Blender was started, there may not be a console readily available, and Blender would need to be restarted with a console.\n\nThis can fixed by using `ReportLists` where applicable.\n\nFurther, modifiers should have the ability to carry multiple error messages as multiple things can go wrong (e.g. if multiple attributes could not be imported, we should have one error per attribute). This would be the responsability of modifier type. [D15492: Modifiers: add a callback to copy the error message](D15492) introduces some API for modifiers to manage their own errors.\n\n----------------\n\n**Discussion summary**\n\nRather than [D15492](D15492), extend `ModifierData` with an optional `ReportList*` which would help differentiate between info/warning/error, and have it all displayed in the UI generically.\n\nSee [P3197](P3197.txt) for a quick implementation. Here is an example, based on [D11591: Alembic: import arbitrary attributes](D11591):\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 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", "Crash probability opening .blend with imported USDs\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 512.15\n\nBroken: version: 3.3.0\n\nOpening files with imported USDs (animated high poly) causes a crash, on some files, with probability of crash, depending on file 25-80%, on some - 100%.\nWhat possibly leads to increased chances of crash is replacing materials or multiple USDs.\nIdentical geometry via Alembic works fine.\n\n - Opening the file should lead to a crash\n[usd_crash.zip](usd_crash.zip)\n\n\n", "Crashes when Switching to Material Viewport / Rendered Viewport / Rendering\nOperating system: Windows 10\nGraphics card: 2 Nvidia GTX 1660 Super's\n\n[blender_system_info.txt](blender_system_info.txt)\n\nBroken: blender 2.8 / 3.4\n\n\nBlender runs completely fine when editing and building a model but once rendering is involved, even in preview, it immediately closes with no explanation. This crash will also happen with the default cube. This had not happened before and have tried Updating blender, reinstalling, simplifying, etc but no change and can reproduce the issue on my computer. i can have it in material mode if i have 0 assets in the scene but once i add something it crashes, i am suspecting a bad pathing issue as i had recently refreshed my computer but do not know how to fix it or give blender a hard reset.\n\n{[F14170509](blender.crash.txt)}[blender_debug_output.txt](https://archive.blender.org/developer/F14170500/blender_debug_output.txt)\nOpen Blender, have any Physical asset inside the scene, switch to rendered / Material Viewport, Crash\n\nI have included the project I was working on and the default cube as they create the same issue.\nPlease note that I have installed the most recent Blender program onto my laptop and opened the files attached and did not have any crash happen so it seems the issue is solely between my computer and the blender program.\n\n[Default Cube.blend](Default_Cube.blend) [Skell Rig base.blend](Skell_Rig_base.blend)", "Alembic design notes\n# Terminology\n\n* ABC = Alembic file (because extension is .abc)\n* DNA = Blender’s data structure\n\n# Current Functionality\n\nImporting meshes from ABC can result in multiple cases. For each imported object:\n* No object animation, no mesh deformation: mesh is imported into DNA as regular mesh object, after that no more link with ABC.\n* With object animation: as above, but with constraint that streams transformations from ABC to DNA.\n* With mesh deformation: as first case, but with modifier that streams mesh data from ABC to DNA, possibly even removing and reconstructing the entire mesh.\n\n\nOther functionality:\n* Materials are buggy (materials should be mapped by name, but we don’t seem to save those to ABC).\n* Curves are supported and loaded as Blender curves (but miss certain properties such as extrustion, etc.).\n* Particles in ABC are loaded as vertex-only mesh.\n* Camera animation is partially supported (transforms, but not camera properties such as zoom/DoF)\n\n\nCurrently easy to do:\n* Static mesh exchange between other software and Blender (because of point 1 above)\n* Adding constraints/modifiers on top of ABC import.\n* Removing extraneous objects.\n* Assigning and editing materials (but on data level may be troublesome).\n* Adding hair/particle systems (it may not work well, but it’s easy to add).\n\n\nCurrently hard or impossible to do:\n* Keeping Blender in sync with ABC (automatically importing added objects, etc.)\n* Knowing (from user perspective) which objects are from ABC and which are from Blender.\n* Performing actions for all imported objects (such as setting a consistent time offset)\n* Offsetting objects in space.\n* Flipping between “real” objects and cached versions.\n* Reliably add hair/particle system, groom, and bake to ABC again.\n\n\n# Tech meeting with Sybren, Sergey, and Campbell\nFeatures discussed:\n* Data streaming can be implemented in same way as dupli-lists / dupli-groups:\n * Loaded ABC is represented as dupli-object. This allows us to generate the meshes / curves from ABC without saving them to the blend file. It also allows the artist to spatially offset the ABC.\n * Dupli-object has option to indicate which sub-hierarchy is loaded. This allows artists to select a subset of objects in the ABC, for example loading an animated character but not the environment or cameras.\n * Dupli-object is stored as `DNAAlembicHierarchy` struct in DNA.\n * Objects from ABC are shown in outliner as collection, similar as currently done with dupli-group.\n * Besides being able to disable the entire collection (currently possible), it should be possible to disable individual objects (not yet possible). This allows, for example, to load an animated Agent 327 from ABC and remove/hide his watch.\n * The collection could contain options to indicate which sub-hierarchy it represents, and a time offset for animations.\n * Alembic XForm hierarchies are loaded as hierarchy of Empties, possibly as their own subgraph in the depsgraph.\n * Open question: how to interact with the objects, how to create static overrides or otherwise “make local”.\n* [Material](abcm.html) names are loaded from ABC\n * Currently Blender doesn’t even properly store material names to ABC at all.\n * The creator of the ABC is responsible for assigning materials to objects / data. The name of these materials should be saved to the ABC.\n * When loading an ABC the materials are looked up by name (if there are duplicates from different libraries, pick arbitrary one).\n * An artist should be able to choose which material names in the ABC map to which Blender materials.\n * It might be nice to have a button “Generate Missing Materials”, which automatically creates correctly-named materials and assigns them to the meshes/objects.\n* Objects loaded from ABC should be handled as “linked from library”, with the ABC as “virtual library”. Interaction between objects from ABC and Blender should be discussed (for example when merging two meshes, one from ABC and one from Blender).\n* Hair: It may be possible to load an animated mesh from ABC, add a hair system, groom it, and save to another ABC. This poses problems with ABC allowing meshes to arbitrarily change topology (and thus also vertex and face order) from one frame to the next. Possible solutions lie in reconnecting the hair system after loading the ABC (for example by using UV coordinates instead of vertex/face indices) or disallowing mesh changes completely after adding hair (this option won’t be liked by artists). We should check with artists in the industry to see which workflows are actually in use.\n* Motion blur: object motion blur is already there. Deformation motion blur should work when the mesh doesn’t change topology. Otherwise it can work if we save & load velocities.\n\n\n# Interface Mockup\n\n\n\n\n\n# Future Work\nPossible directions that we may implement in the future, and may be nice to know about in advance to at least not make completely impossible with current design choices. The basic idea behind this feature is *fixups on top of cached data*.\n\n\n## Sculpt on top of ABC mesh\nHere Hjalti takes the role of the animator, and Andy that of the shader/lighter/look developer.\n1. Hjalti animates character, exports to ABC.\n2. Andy loads ABC, tweaks materials and environment.\n3. Andy locally changes the ABC-streamed mesh (e.g. not changing topology, but for a number of frames change, say, the position of the hand).\n4. Andy saves those changes to another ABC file that acts as a 2nd layer of mesh data.\nSteps 2-4 can be repeated, generating multiple layers of ABC files that eventually are all merged into a single animated character in Blender (this merging of data from different ABC files is supported by ABC itself).\n\n\n# Open Questions\n\n- How to interact with instanced objects from ABC.\n- How to allow modifiers to be stacked on top of imported ABC meshes/curves.\n\n\n# Development Targets\nTBD which is part of Code Quest, or postponed to later. Should be discussed with artists for final decision on what to build & how.\n\n\n1. Rework ABC importer to produce `DNAAlembicHierarchy` structs instead of directly creating new objects/meshes/curves/cameras.\n2. Allow enable/disable of individual objects in ABC dupli-group.\n3. Create & link Collection for ABC.\n4. Fix material name saving.\n5. Create system for material linking.\n6. Implement switching collection between ‘cached’ and ‘live’.\n7. User Interaction between ABC-backed and non-ABC-backed objects (for example trying to join two of those, or trying to parent a Blender object to an ABC object or vice versa)\n8. Make the hair system work.\n9. Test motion blur to clarify what works and what doesn’t (and implement/fix the latter if desired).", "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", "The range of the edge crease values exported in Alembic is incompatible with other software\nBlender exports edge crease values in the range [0, 1], while other software seems to expect it in the range [0, 10] similar to OpenSubDiv, making the exported alembic file incompatible with other software.\n\n### Original Report\n\nOperating system: Windows 10\nGraphics card: Nvidia GeForce RTX 2080\n\nBroken: 3.2.1\nWorked: 3.1\n\n\nwhen exporting Alembic file the crease value doesn't get read properly by other softwares. (it works when importing back to Blender though) the creased edges get recognised but not their values (they all have the same value). (I tried this with Modo Maya and 3DsMax).\n\nI think this was also a problem of the version 2.9 and when I reported the bug it was fixed after, the problem at that time was that the values didn't correspond to the values that other softwares use. They all use a values that correspond, like for example 0.3 in Modo is 3 in Maya or 3 in 3Ds Max but in Blender for some reason is 0.6. - it would be also nice that this problem is addressed and we can have the same type of creasing values so the files get exported properly. \n\nBut right now the problem is that the values don't even get recognised by other softwares. Please let me know if you need any help to fix this problem I can run some tests. I think it is very important that the edge creasing workflow is aligned with the one that other softwares use. \n", "Blender (2.91) crashes on change frame with handler set to render scene\n\nOperating system: Catalina (10.15.7)\nGraphics card: \n\n\n2.91.0\n\nI want to have the scene rendered automatically every time the frame changes.. so I set a post frame change handler do just that (according to blender documentation: bpy.app.handlers.html#bpy.app.handlers.frame_change_post)\n\nPaste this in the Blender console to setup the handler: \n\n```\nimport bpy\n\ndef my_handler(scene):\n bpy.ops.render.render(use_viewport=True)\n \nbpy.app.handlers.frame_change_post.append(my_handler)\n```\n\nHowever, blender crashes as soon as I change the frame.\n\n- Open attached file\n- Run script\n- Change frame\n[handler_ops_render_crash.blend](handler_ops_render_crash.blend)\n\n\n" ]

[ "Crash when replacing an Alembic file while blender is open.\nWindows - Asus GTX 1060 6Gb\n\nBroken: 2.78.4 7ae9d09\nWorked: didn't ever to my knowledge.\n\nWhen you're doing an alembic pipeline say from maya, you usually will endup replacing alembic files with updated ones, though you might not want to have to close blender, and reopen it so if you have blender open and happen to update the Alembic file with a new one, that IE differs only in animation that will crash blender, i'm attaching 2 ABC files that are similar, will just have a minor difference for you to try.\n\nOpen blender 2 blender instances\nmake an animation on one of them\nexport ABC\nOn the second blender instance import ABC file.\nthen in the first blender instance do some changes, reexport and replace the ABC file you made before.\nwhen you go to the second blender instance\nmove the timeline\nit'll crash.\n\nso for making the process quicker I created 2 alembic files from the same project:\n\n[norman_dosposes.abc](norman_dosposes.abc)\n\n[norman_dosposesB.abc](norman_dosposesB.abc)\n\n\nlet me know if you need anything else!\nCheers!\n\n\n" ]

[ "Node editor: exposing node attributes in node group\n**Current situation**\nWhen currently creating a node group the node setup and the settings of the nodes are persistent in the node group. Only by the use input sockets can our users tweak the usage of the node group. As those input sockets can only connect to other input sockets the freedom of tweaking is limited.\n\n**Proposed situation**\nIn the proposed situation I want to have an option where the users can ‘expose’ attributes of a node to the nodegroup level. My proposal will be similar to “Insert key-frames” in workflow.\n\nExample:\n\nWhen the user wants the Filter type of the Blur node to be exposed, the user can open the attribute menu and will be ample to select “Expose to node group”.\n\n\nNote: this menu needs will hold a new operation when in the editing a node group: “Expose to group” and “Dispose from group”. We can also add a key to these operations (“E” is not assigned yet in node editor when hovering over a node attribute as far as I can see.)\n\nWhen the node group is closed all exposed attributes will be rendered in the node group.\nBy this the user will still be able to tweak this setting and make changes per instance of the same node group.\n\n**Open issues**\nIt should also be clear to users which attributes are exposed. We can use a Color, but it won’t be clear when an attribute is keyframed and exposed. We could also solve this by having a gradient or checker fill for color, or something else.\n\n**Technical stuff**\nStore references of exposed Node/RNA attributes in the nodegroup.\n\nThe main usages of node systems are cycles and compositor. Both of them flatten the node tree so all instance specific settings can be handled during the flattening process. For texture nodes we can use a reference to the nodegroup instance when executing (haven’t looked into the current state of the code yet). \n\nChanges to addons needs to be done by the addon developers themselve. There might be a breakage or at least new blender feature that needs to be supported. \n\nAs the current node system is not changed in Blender2.8 I think it is very plausible to implement this in 2.79 and merge it in Blender 2.8 when finished.\n\n\n\n", "Nodes: Changing Input position with a Driver\nBroken: 3.1 and 3.2 Alpha\n\nIn Geometry Nodes editor, shift an input socket above a socket having a Driver and it will switch the Driver.\n[2022-03-12 15-58-02.mp4](2022-03-12_15-58-02.mp4)\n\n- Enter Group Node\n- Shift \"Vertices Y\" input above\n[Test.blend](Test.blend)", "Eevee Group Node ignores socket type conversion (eg. Vector to Float)\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 527.56\n\nBroken: version: 3.5.0 Alpha, branch: main\nWorked: N/A\n\nIf the input of a group node is `Float`, but you connect a `Vector`, the group will read the input as a vector instead of a float.\n\n1. Download the Blender file below\n[test.blend](test.blend)\n2. Switch to Eevee, it looks like this:\n\n3. Switch to Cycles, it looks like this:\n\n\nIt seems to be node group evaluation. When ungrouped it looks identical.", "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", "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)", "Viewer Node does not initialize from within Compositor node group\nOperating system: Windows 10 x64\nGraphics card: RTX 8000\n\nBroken: 10/26/2022 build\n\n\nViewer node does not work if used for the very first time inside a compositor node group. Once the user goes back to the top level composite and connects a Viewer Node, it works, and then updates normally when going back into node groups.\n\n**Reproduce from a file**\n\n[viewerNodeNotWorkingInNodeGroup.blend](viewerNodeNotWorkingInNodeGroup.blend)\n\n- Add a viewer node for the Image node output.\n- Notice how the backdrop and the Viewer image doesn't get initialize with the viewer content.\n- Go back to the top level node tree and add a viewer node.\n- Notice how the viewer is initialized.\n- Go back inside the node group.\n- Notice how it updates correctly, so it is only for the first time.\n\n**Reproduce from scratch**\n - New General file\n - Hit 0 and F12 to render one frame of the default cube\n - Change to Composite tab\n - Change top view to Image Editor\n - Pick dropdown and select Viewer Node\n - In compositor panel Shift-A to add a greenscreen image\n - Shift-A to add a Keyer node\n - PIck a green color to key it\n - Add Scale node, set to Fit and Render Size\n - Connect Keyer Image output to Scale node\n - Add Alpha Over node. Connect Render Layers to Alpha Over Background input and Scale node to Foreground input\n - Select Image, Keying, Scale, and Alpha Over nodes. \n - Ctrl-G to Group\n - Make sure Node Wrangler is enabled.\n - Inside the group. select the Image node.\n - Ctrl-Shift-LMB to add a Viewer and connect it\n - Note that Viewer Node display in Image Editor does not update.\n - Press Tab to go up one level.\n - Highlight Render Layers and press Ctrl-Shift-LMB. Now render layer is shown in Viewer Node.\n - Highlight Node Group and press Tab to go in.\n - Now image viewer is working and active.\n\n", "Geometry-node object-info rotation&scale outputs values are False if scale is negative \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 512.59\n\nBroken: version: 3.3.0\n\nthe object info rotation & scale values are false if the scale of the sampled object is negative \nsee video, where i compare with simple drivers of the object transforms\n\n[dffdsdfdsfsfd.mp4](dffdsdfdsfsfd.mp4)\n[buggy transforms.blend](buggy_transforms.blend)\n\n", "Breaking change? Curve point tilt default orientation rotated by 90°\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.40\n\nBroken: version: 3.6.0\nWorked: 2.80\n\nThe default orientation (0°) of curve points has changed by 90°. If the curve is used for another object's curve modifier, the result between Blender 2.80 is different to newer versions (reproduced with 2.81...3.6). This is a change that I did not find listed in the release notes, so this is either a bug or by design. In any case, it's a breaking change.\n\n2.80 vs 3.6:\n\n\n\n1. Open the attached project in Blender 2.80 and in 3.6\n2. If you compare the two, you see that the normal orientation is different, consequently the result of the curve modifier affecting the mesh is different.\n\nAfter migrating a bigger project this causes several issues that would need to be fixed. Or Blender needs to be fixed.\nThis is an old issue, so I hope it's not a duplicate. Didn't find it.\nThank you.\n\n", "Geometry nodes preview, clipping Region in the viewport its not working\nOperating system: Linux-5.15.0-58-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03\n\nBroken: version: 3.4.0 Alpha\nWorked: Never\n\nCaused by: c55d38f00b\n\nTo be compleatly honest i don't remember if this was a limitation of the preview node or not and i was unable to find the answer. \nSo as the title says viewport clip in viewport doesn't work in the geonodes overlay preveiw\n\n\n- Try to preview any data from geometry nodes. \n- alt+b to do a viewport clip\nshould look like in the left side of the image above, but it seems that a second geometry with the info from geo nodes in alpha blend mode its not being clipped \n\n", "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", "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.", "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", "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.", "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)", "Changing outputs from Separate RGB node into Displacement (using microdisplacement) does not trigger geometry update.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\n\nChanging outputs from Separate RGB node into Displacement (using microdisplacement) does not trigger geometry update. Have to tab into edit mode to force mesh update.\n[rgb_disp_bug.blend](rgb_disp_bug.blend)\n\nAdd plane with microdisplacement enabled.\nConnect Image node to Separate RGB node and one of the channels into Displacement node.\nChange view to Rendered mode.\nChange channels from R to G to B to R and notice no geometry updates happen in the view port. (Make sure to use an image with different channels)" ]

[ "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" ]

[ "Applying Skin Modifier to square loop object and in edit mode braking the loop makes prob\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0\n\n\nBroken: version: 2.80 (sub 74)\nWorked: (optional)\n\n\n\nSkin modifier disturbs the geometry form one corner on braking the loop form one corner of closed loop (of square shape). Although in this case the angles are 90% but it's will make prob...\n\n\n\n\n", "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", "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)", "Copy/Paste object operator copies collections specified somewhere in that object (e.g. Geometry Node Collection Info node, particle system instance collection, ...)\nBroken: Current master.\nWorked: Never.\n\nThe copy operator treats the `Collection Info` node as the fact that the object belongs to the collection.\n\n| Ctrl+C | Ctrl+V | Expected |\n| -- | -- | -- |\n|  |  |  |\n\n1. Create collections `Collection_1`, `Collection_2`.\n2. Add Cube in `Collection_1`.\n3. Add Cone in `Collection_2`.\n4. Create geometry node modifier on Cube. Go in node tree:\n a. Create `Collection Info` node.\n b. Choose a `Collection_2`.\n5. Select `Collection_1`, Cube.\n6. Copy object in 3d view.\nExpected: Cube object will copied.\nBug: Copyring object, collection and attach that in collection that chosen in `Collection Info` node.\n\nThe same happens when you:\n\n- Create collections Collection_1, Collection_2.\n-- Add Cube in Collection_1.\n-- Add Cone in Collection_2.\n- Create a particle system on the Cube\n-- Render As Collection\n-- specify Collection_2 as the Instance Collection\n- Select Collection_1, Cube.\n-- Copy object in 3d view.\n-- Expected: Cube object will copied.\n-- Bug: Copying object, collection and attach that in collection that chosen in the Particle Instance Collection.", "Can't get vertex color in index layer of \"Particle Instance\" modifier\nOperating system: Mac OS ventura 13.1 \nGraphics card: Apple M1\n\n\nBroken: version: 3.5.1. 3.6.1\nWorked: 2.80.75\n\n\nI define a vertex color named \"test color\" in \"Object data properties\"-\"color attributes\"-\"+\"-\"domain: vertex\"-\"data type: color\" for a general plane mesh. Then I add a \"Particle Instance\" modifier for the mesh. In the \"layers\" section of the modifier, I want to assign the previous \"test color\" to the \"index\" field. However, I get an empty list prompted when tapping the field area. And I can't enter the name manually either.\n\n1. build a plane mesh\n2. Create a vertex color. \"Object data properties\"-\"color attributes\"-\"+\"-\"domain: vertex\"-\"data type: color\" for the plane\n3. Add a \"Particle Instance\" modifier for the plane\n4. Go to \"index\" field in \"layers\" section of the modifier.\n\n", "unwanted uv-gap created by bevel modifier\nOperating system and graphics card\nwindows 7\nNVIDIA GeForce GTX 660\n\nBroken: 3d243eb\nWorked: same error on offical release 2.78\n\nbevel modifier (bevel by weight) creates an unwanted UV-gap at a vertex with 5 edges connected. 2 edges has bevel weight. Error visible if bevel modifier is applied of if subdiv modifier is active. The UV-gap disappears if 4 out of 5 edges has a 90 degree angle to one another.\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\nHard to explain how to model. Easiest for you is to open the .blend and test it. I put a shape key on the \"error mesh\". Turn the shapekey on/off to show the error.[bevel modifier error.blend](bevel_modifier_error.blend)", "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", "Geometry node - setting lacunarity to 0 crashes Blender (musgrave texture)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.93\n\nBroken: version: 3.2.2\n\nIn a fairly simple geonode tree, trying to set lacunarity to 0 will crash Blender instantly.\n\n- Use attached Blend.file\n- In the 'set position' branch, try to set 'musgrave texture' lacunarity to 0\n- Crashes everytime for me\n\n[Geonode attribute.blend](Geonode_attribute.blend)", "Geometry Nodes fouling up motion blur\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA RTX A5000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.86\n\nBroken: version: 3.1.0\nWorked: N/A\n\nGeometry Nodes applied to a spline which affect its shape over time do not blur when Motion Blur is enabled.\n\nLoad attached simple file. Render frame zero. There is no blur at all. Render frame 1, *everything* is blurred, despite only part of the spline is in motion. It would appear the entire spline is blurred according to how the base object is moving, not how the spline is deformed as a result of the applied Geometry Nodes.\n\nNote that same file loaded into 3.3.1 causes Blender to crash (GPU rendering only - it's a stack corruption bug in the nVidia driver, but 3.1 doesn't cause a problem). I previously reported that crash but it was rejected due to possibly being related to the Photographer add-on, which I have uninstalled. It still crashes.[Motion Blur Bug.blend](Motion_Blur_Bug.blend)", "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)", "Bevel modifier disconnects vertices in the UV map\n{[F8713789](2KmuzHs.png)}Operating system: Windows 10 x64\nGraphics card: GTX 970\n\nBroken: 2.83.1, 47b6c332587ca45eddc98e75b3f563e2f17a0d47, probably all 2.8+ versions\n[SM_UVTest.blend](SM_UVTest.blend)\n\nWhen using an angle or weight limit on the Bevel modifier, vertices connecting beveled and unbeveled edges are split in the UV map, producing distorsions.\n\nAdded a blend file. To reproduce the issue, apply the Bevel modifier, and select all faces to see the problematic vertex in the UV editor. \n\nSome context is here : 1241831", "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.", "Refactor: Replace socket declaration system for (Geometry) Nodes Panels\nThis is an internal refactor, follow up of #108897\n\n", "Grease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\n\n\nBroken: version: 3.3.0 Alpha\n\n\nWorked: Blender 3.2 \n\n\n\n\nGrease Pencil modifier \"line art\" won't draw objects with Geometry Nodes Instances.\n\n\n\n\n - New scene.\n - Keep the cube.\n - Don't delete it.\n - Add an empty Grease Pencil Object.\n - Don't delete the cube.\n - Add a Line Art Modifier to the Grease Pencil Object,\n - Switch Source to Object, and select the cube.\n - Assign the default layer and material.\n - You should be seeing something like this\n\n\n\n - Add geometry nodes nodes to the cube.\n - yes keep the damn cube.\n - here is the simplest setup that involves instances that I could think of\n\n\n\n - as you can see in the viewport the grease pencil line art has dissapeared completely.\n\n\nThanks for looking into it.\n\n", "Geometry Node: Changing modifier input values with python no cause update\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0 Alpha\n\n\nChanging modifier input values with python no cause update.\nBy code:\n\n```\nbpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_1\"][0] = 13.8\n```\n\nValue in modifier property was changed. User interface no updated before modifiers panel are not redrawn. Result of modifier didn't updated.\n\n\n\n- Open attached file\n- Run the code `bpy.data.objects[\"Cube\"].modifiers[\"GeometryNodes\"][\"Input_7\"] = 1.0` in the python console\nThe modifier UI may change, but the Viewport does not.\n[geom_node_py_bug.blend](geom_node_py_bug.blend)\n\n" ]

[ "Instances lose their material upon applying geometry nodes modifier\nOperating system: macOS-11.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.4.17\n\nBroken: version: 2.93.0 Beta\nWorked: unknown\n\nWhen applying a geometry nodes modifier, all instances lose their original material and take on the material of the object which had the modifier on it (they do retain the correct material-index). I would expect them to retain their original material.\n\nIn geometry nodes, instance an object with a different material\nApply the geometry nodes modifier", "Instanced object (in GN) not textured.\nOperating system: Linux-5.4.0-72-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.102.04\n\nBroken: version: 2.93.0 Beta\nWorked:2.92\n\n\nTexture or material not conserved when instancing object in geometry nodes.\n\nOpen the attached .blend. The source object (leaf) is textured, but the instanced plant leaves are not.\n\n[texture-bug-v2.93.blend](texture-bug-v2.93.blend)", "GeoNodes: material shader ignored when generated primitive ist connect first in join geometry node\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 465.89\n\nBroken: version: 2.93.0 Beta\n\nWhen a generated mesh primitive is connected above the original geometry (train) in the join geometry node multi input their is no material shading for any mesh in the object. Is the original geometry connected first to the join, both meshes get shaded. Probably it is more a design thing than a bug, but I wanted to report anyway, because it took me 2 hours to figure out the reason for getting no shading. Probably because of material id setting or something for the generated mesh, but i also couldn't figure that out. At least its confusing as default behaviour :-) \nBTW. using geo nodes attributes in cycles so much more often don't give any information (despite type, ranges), than they do that I'm not sure where to start a bug report. Are there restrictions I'm not aware of or do I handle the data wrongly? \n\n- add material to start cube\n- add geometry node\n- in node tree add join geometry node to only noodle\n- add mesh primitive (line, cylinder,...) and connect to join node \n\nwhen primitive is connected above the first noodle the shading disappears. \n\nScreenshot and test file: \nAAA1bPsX4JzqdgHR_MhaIsopa?dl=0\n\n\nit's awesome anyway. Thanks for looking into it. Enjoy. \n\n\n" ]

[ "Mirror Uv\nThere already exists an operator called Copy Mirrored UV Coords. This could be extended to support the features described below\n\n\n- From +X to -X for example (source can be positive or negative X, Y or Z) \n- Options:\n - By object space\n - By world space\n - By topology \n\n\n\n**Starting point**\n\n\n**Desired result**\n\n", "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", "Missing Face Set Operators\nThis task is a todo list for missing face set operators. - [x] means operator works on either a user-picked face set or all of them. A single arrow means conversion operator in one direction already exist (so, Mask to Face Set already exists).\n\n- Face Set- [x] `<->` Vertex Groups\n- Face Set- [x] `<->` Face Maps\n- Face Set- [x] `->` UV Seams\n- Face Set- [x] `->` Mask\n- Make Disconnected Face Sets Unique\n- Separate By Face Sets\n- Face Set- [x] `<->` Material Slots\n- Face Maps `<->` Face Sets", "PBVH Pixels should check on center uv coordinate.\nCurrently it checks on bottom left corner, but the painting is half a pixel shifted. By adding an offset of half a pixel this should reduce some artifacts.", "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", "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}", "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\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", "Adjust last operation: can't reset properties to default value\nBroken: 2.8x\n\nIn the Adjust Last Operation panel, the context menu for any property has the Reset to Default Value options disabled, although they are enabled in the operator panel.\n\n\n1. Load the default scene\n2. Enter edit mode on the cube\n3. Bevel an edge\n4. Expand the operator panel in the bottom left\n5. Right click any property, note that Reset to Default Value option is enabled and works\n6. Go Edit -> Adjust Last Operation\n7. Right click the same property in that panel, note that Reset to Default Value option is disabled", "UV map inconsistency after bevel modifier\nOperating system: win10\nGraphics card: 1050ti\n\nBroken: 3.4.1\n\nMesh position in edit mode affects how bevel processes UV map\n\nIn attached file translate selected part of mesh along world Z axis -> UV is changing position\n[bevel_uv_issue.blend](bevel_uv_issue.blend)", "Hair particles roots moving when using curl kink type and simple children\nOperating system:Windows 10\nGraphics card: Nvidia RTX\n\nBroken: 3.0+\n\n\n\nWhen you use particle hair with simple children and you try to add the curl kink. The roots move with the amplitude. The only thing that keeps the roots in their place is to turn on the clumping. This doesn't happen when you use the interpolated children\n\nI don't know if it's a bug (most likely) but it is extremely frustrating\n\n Take a look at the video.I've added the file just in case\n \n Thanks\n\n", "Constraint with custom space not limiting transformation\nOperating system: Windows 11\nGraphics card: RTX 3060\n\nBroken: Blender 3.6.2\nWorked: Never\n\nAffect transform conflict with custom space\n\nAccording to documentation, Affect Transform option will limit manual rotation, but it doesn't with custom space. It works with local space.\n\n**Steps To Reproduce**\n\nOpen [file](https://projects.blender.orgattachment) and rotate contrained bone. Check bone transformaton - it is not limited.\n", "Regression: Strange crease when using proportional editing with the \"connected only\" option turned on (edge selected)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.72\n\nBroken: version: 2.93.0\n\nPretty sure this is caused by 21b9231d7f\n\nWhen using proportional editing, there is a strange pinching/creasing that is going on where it should be smooth. It seems to only happen when \"Connected Only,\" is turned on\n\n1. Open new file\n2. Add plane\n3. Add a whole bunch of edge loops\n4. Enable proportional editing + \"Connected Only,\" option\n5. Grab one edge and move it up || down\n\n\n\nTest File:\n[#89968.blend](T89968.blend)", "pressing z key to switch between extrusion \n intel i5 ,win ,amd radeon \nblender 2.8 \n490a385c8124\n\n\n\n\nThis happens when transform orientation set to Global \nCreate a sphere , select a face and extrude \nBy default it will extrude along the normal , when pressing z it will now extrude along the global but it won't go back to normal when pressing the 'z'key again \n \n\n\n ", "Blender development todo list -- Import/Export\nNOTE: this is a direct dump of Import_Export (without cherrypicking the [still] valid items)\n\n## Blender files and Library linking\n\n- [ ] Mixing \"direct\" and \"indirect\" data not well supported #26706\n- [ ] Making local data which is still used in libraries, causes problems #44321\n\n## All Formats\n\nCurrently negative scales will flip faces for formats which don't store object transformations (obj, ply, stl ... etc). #35892\n\n## FBX\nSee [[Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX]].\n\n## Alembic\n- [ ] While Alembic exports particles as points and supports ParticleInstance modifiers it could also support particle duplication (dupliobjects etc.), see #54703\n" ]

[ "UV Editor Individual Origins not working for Edges, Vertices and Faces\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.41\n\nBroken: version: 2.81 (sub 16)\nWorked: (optional)\n\nIn the UV Editor the option to transform based on individual origins is not working for Edges, Vertices and Faces of the UV mesh, only for whole Islands.\n\nAdd an Object (either something more complicated than a cube or alternatively a subdivided cube.\nUnwrap\nSelect some connected vertices at one part of the UV mesh\nSelect some connected vertices at another part of the UV mesh which are not connected to the previously selected ones\nSet the Pivot to \"Individual Origins\"\nRotate or scale to see that the rotation or scale uses the median point of the selected vertices rather than the individual origins of each vertex collection.\n" ]

[ "Skin modifier can produce undesirable geometry\nBroken: blender-2.74-65328fa-win32\nWorked: never as the skin modifier always had problems like that\n\nThe skin modifier sometime fail and generate very bad geometry\n\n[skinbug.blend](skinbug.blend)\nload the attached blend, and see the problem as shown in the screenshot {[F177512](screenshotbug01.jpg)}(the underlying vertices are all symmetrical, as that base was done with the mirror modifier) \nTest with the various x/y/z options in the skin modifier and see how that buggy geometry can move in other place of the generated mesh\n\nOnly way to fix is to try to either move around the vertices or to rescale them (CTRL+A with the skin modifier) , not real solutions if you need all the branches to be +/- the same diameter and at exact locations.", "mantaflow instability on high timesteps\nmacOS 10.14\nIntel HD 6000\n\nBroken ce64cfd6edc2a0ec0aabfd4daaa5f655763cc74b, 2.83.12\n\n**error**\n\n[11110001-0070.mp4](11110001-0070.mp4)\n\n- Add quick liquid to default cube.\n- Set minimum and maximum timesteps to 100.\n- Bake up to frame 70 and watch the liquid explode.", "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).", "Measure Tool Todo's\n\n- #69660 (Measure tool thickness option exposed in the UI)", "GPencil: Inconsistent brush profile using Line/Shape tool\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.0\n\n- When certain brushes with unique characteristics like \"Ink Pen\" or \"Marker Chisel\" brush is selected, and *Draw tool* is used, the brush characteristics (thickness, frequency of effect) are appealing (image: green). \n- But when those brushes are selected, and any *Line/Curve/Shape* tool is used, the brush characteristics have undesired effect (image: red). The peaks are extreme, and the frequency of the extremes along the stroke is high (not as smooth as drawing).\n- (A) The Thickness Profile can reduce the maximum peaks, but not even-out the minimum valleys. (B) The frequency of the brush effect can't be distributed evenly across the stroke. It seems the only way to edit it is through manual sculpting. \n- The number of points (few/many) also doesn't smooth out the effect. \n\n*Also just an additional suggestion, when using line/shape tool in its edit mode (before confirmed with Enter) it would be helpful to be able to adjust its settings (Subdivision, Radius, Strength, Thickness Profile) in real-time to preview the changes - without having to confirm the stroke, undo, change settings, and apply stroke again. Only mouse-wheel scrolling, that controls subdivisions, allows preview of settings changes in real-time.\n\n\n\n", " 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.", "GPencil: Shortcuts in Draw Mode are hardcoded\nMultiple keys in the `gpencil_draw_modal` function are hardcoded and (some) don't show up in the info bar. This makes it impossible for the user to know what certain keys do as well as impossible to change them in the keymap. All of those keys should be in the keymap with the default keys set as they are now.\n\nHere is a list of these (hardcoded) shortcuts:\n\n - {key Enter}, {key Pad_Enter}, {key Esc}, {key Space}, {key Ctrl Z} (?): Confirm\n - {key Mousewheel_Up}, {key Pad_Plus}: Increase size of eraser\n - {key Mousewheel_Down}, {key Pad_Minus}: Decrease size of eraser\n - {key O}: Set center of guide\n - {key V}: Turn off speed guide\n - {key M}: Alternate or flip guide direction\n - {key L}: Turn on line guide; {key Ctrl L}: Turn on line guide with angle = 0; {key Alt L}: Turn on line guide with last angle\n - {key C}: Turn on circular guide\n - {key K}: Turn line guide clockwise\n - {key J}: Turn line guide anti-clockwise\n", "Workbench: Shadow Bug\nOperating system: MacOS Catalina\nGraphics card: Intel Iris Pro 1536 MB\n\nBroken: 2.83\n\nWhen trying to add a shadow, all screen \"cracks\" into different-shadow pieces\n\n\n\nViewport Shading> \"checkbox\" Shadow ", "Enable Python library optimizations for macOS\nTo match the same change in Linux: f222fe6a3a0750d1dfdb74f8db817c8f9f5b7236\n\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...)", "Sculpt Paint: Smoothing Strength\nNOTE: This design is still under discussion and potentially incomplete.\n\n# Issues\n\n### Hard to access smoothing strength\n\nIn sculpt mode it is possible to smooth geometry or colors (blurring) directly by holding `Shift`.\nAdjusting the smoothing strength should be very accessible.\nUnfortunately the current design in sculpt mode is less than ideal.\n\nFor sculpting brushes the strength of the smooth brush is used as the global smoothing strength.\nSo the workflow has been to switch to the smooth brush and adjust the brush strength there.\nThis is not as intuitive as changing the strength of the currently active brush.\n\n### Bloating keymap & toolbar\n\nSince Blender 3.2 we also have a paint brush within the same mode. The issue here is that the paint brush smoothing strength is hard-coded. We must add a way to control the color smoothing strength.\nWe could change that wit the same solution as the regular sculpting brushes, but that would mean adding another smoothing brush and another shortcut. \nThis unnecessarily bloats the keymap and toolbar further. We shouldn't add any more smoothing brushes unless really necessary.\n\n# Proposal:\n\nA possible solution for this would be to make the smoothing strength a brush setting for every brush.\nThis would have the following advantages:\n\n- We could add a shortcut operator on `Alt F` to control the smoothing strength of the currently active brush. This makes the setting much more accessible.\n- Depending on if you are using a sculpting or a smoothing brush, the shortcut operator would control the related smoothing strength\n- The smoothing strength can have a \"Use Unified Strength\" toggle (enabled by default), to optionally give each brush the smoothing strength it needs (This would need further investigation into the toggle behaviour)", "Grease Pencil Fill Tool Breaks After Scroll-Wheel Zooming Window\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 980/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.30\n\nBroken: version: 2.91.0 Beta\nAlso tested in 2.83.9 & 2.92 Alpha on Windows, and 2.91 Beta on Mac with same results.\n\nIf an 'unclosed' area made with grease pencil lines on its own layer overlaps and is 'closed' with grease pencil lines on a second layer, zooming the 2d workspace in and out will cause the fill tool to 'break' and fill the whole screen; even when the fill tool is set to: Advanced-Layers-Visible. \n\nCreate closed shape on one layer. Create 'open' shape on second layer that overlaps and is closed by grease pencil lines from the first layer. Zoom in and out in workspace while using the fill tool in a separate 'fill' layer. \nPlease see attached .blend file and screen capture: \n\n[FillTest.blend](FillTest.blend)\n\n[FillTest.mp4](FillTest.mp4)\n\n\nI really hope this isn't just user error. Thank you for taking a look!\n", "Cycles GPU Compute 5000 x 5000 pixels render F12 crashes\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0 Alpha\n\nCycles GPU Compute 5000 x 5000 pixels render F12 crashes\n\nMacOS 13.5\nSee youtube about Blender crash guide during 5000 x 5000 pixels.\n\nNot matter both same crash Blender 3.6.3 and 4.0\n\n", "Shrink/Fatten \"Offset Even\" can not be used as default\nThe \"Offset Even\" option is turned on by default for the Shrink/Fatten (Alt-S) tool. You can see this by opening user preferences, selecting the input tab and opening the Shrink/Fatten menu under the Mesh menu. However, if you use the tool, you'll see checking or unchecking this default option makes no difference. The tool always defaults to off.\n\nIt doesn't seem currently possible, even with custom coding, to have this option on by default. I disabled all transform modal map keys just to be sure they weren't interfering. They are not. I also tried changing the default key to something else (Ctrl-K). It seems nothing can be done to have this tool use \"Offset Even\" (i.e. even thickness) by default. ", "Sculpt Mode: Occlusion blurring steps\nFor View and Area auto-masking we implemented Limit and Falloff sliders for controlling the extend and softness of the mask.\nThese are disabled when \"Occlusion\" is used.\n\n\n\nWe need to implement a setting to blur the edge of the Occlusion mask.\nThe easiest solution would be to add additional \"Blur\" steps, similar to the Cavity masking." ]

[ "Annotate and TimeLine too thin for Mac.\nOperating system: Darwin-18.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.11.20\n\nBroken: version: 2.81 (sub 2)\nWorked: (optional)\n\nToo thin need to fix everything on TimeLine and Annotate\n\n\n\n\n" ]

[ "Weight paint vertex select difficult to see (depends on surface color)\nThis is an issue since 3.2x\n\n**Short description of the issue**\nVertex selection is difficult to see in some cases, depending on the surface color.\n\nChanging the view-port shading \"Color\" can make the unselected vertex color match the selected vertices color.\n\n<video src=\"attachment\" title=\"screenshot.webm\"></video>\n\n**Exact steps for others to reproduce the issue**\n- Open attached .blend file.\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. ", "Changes the cursor from an arrow to a prohibition sign when working with floating windows.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40\n\nBroken: all versions\n\nThe bug only affects the visual change of the cursor from an arrow to a prohibition sign. The error occurs when dragging resources from the resource browser, which is a floating window. The functionality is not broken and you can drag resources without any problem, but it is confusing for the user.\n\n1. open the resource browser in a floating window.\n2. drag any asset into the 3d view\n3. drag another asset (the cursor is already changed to a prohibition mark)\n\n", "In Face-select Mode, Hiding unselected doesn't hide loose edges\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 400 Intel 4.4.0 - Build 20.19.15.5070\n\nBroken: version: 2.83 (sub 0)\nWorked: (optional)\n\nI don't really know if it is a bug or a limitation but Loose edges are not hidden when hiding unselected in face select mode.\n\nOpen the attached blend file and hit Shift+H with the selected face. It doesn't hide the loose edges.\n[Bug test.blend](Bug_test.blend)", "Applying screw modifier doesn't respect hide status of edges from edit mode.\n\n\nUPDATE: If the Unhide hotkey is used, despite no parts actaully being \"unhidden\", the uneditable parts become editable.\n\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.61\n\nBroken: version: 3.5.0\n\n\nApplying a screw modifier with parts of mesh hidden in edit mode will result in those generated mesh from hidden parts to:\n\n1. only show as edges,\n2. be still selectable in edge select mode,\n3. and becoming uneditable.\n\nwhen going back to edit mode.\n\nOriginal description:\n\nIf certain parts of a mesh with a screw modifier are hidden in edit mode (though still visible with the screw modifier, just not selectable), and then the modifier is applied to the mesh in object mode, the previously hidden parts will become uneditable, though still selectable in edit mode.\n\n\n- Add a screw modifier to an object\n- Hide parts of the object in edit mode\n- Apply the screw modifier in object mode\n- Go to edit mode, the parts that's hidden supposedly has edges on display.\n - If use edge select mode, you can actually select those ghost edges, but not editable.\n - If use alt-h, then everything is shown and behaving normal again.\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.", "Drawing size of particles not matching DPI\nOperating system: MacOS\nGraphics card: AMD Radeon Pro 450\n\nBroken: 2.83\nWorked: N/A\n\nWhen moving the blender window to the external monitor, the halo size of the particles changes, which can cause them to disappear.\nBest way to see what I mean is to watch this short clip of me moving the window, and also zooming in and out to show that not all colors are lost: Vu6MSHVxEUwYLvob8\n> In #82238#1283352, @jenkm wrote:\n> The problem here is with the `U.pixelsize` or something like that, as usual.\n> \n> When you move a window between Low and High DPI screens, the size of the spheres does not change correctly.\n> It seems that the size changes twice, like the UI scale plus the size of the spheres additionally.\n> \n> | Low DPI Screen | Moved to High DPI | Low DPI with Thick \"Line Width\" |\n> |  |  |  |\n> \n> And further, depending on the size, these spheres can be hidden by a mesh.\n> \n> | Thick | Default | Thin |\n> |  |  |  |\n> \n> The size of the spheres should not depend on `U.pixelsize`, first of all.\n> The visibility of these spheres also depends on the viewing angle, what is also not clear whether this is intentional or not.\n\n\n- Open attached file\n- Update the particles if needed\n- Move the window to another monitor with different DPI\n||\n| -- | -- |\n[particles.blend](particles.blend)\n\n---\n**Complex file:**\n[rain.blend](rain.blend)", "Show small preview image even in non-Thumbnail Display Modes\nAs mentioned in #89729 (Add toggle for Vertical and Horizontal Display Mode) we should support the Vertical and Horizontal List Display Modes as well. But rather than showing the data-block type icon there (which is rather useless), show the preview, which is much more important typically.\n\nThis may actually be nice for the regular File Browsing as well, but there it may be more important to have an icon to quickly differentiate the different file types.", "Cursor's icon doesn't update correctly when going from panel to scene\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.2.0 Alpha\nWorked: Never (introduced/discovered with new design for 2.8 series)\n\nThe cursor icon doesn't update properly when returning it to the scene fast enough after tweaking in panels, and on it's way passing over text panels.\n\n- Go edit mode and select a vertice/edge/face to activate the transform panel\n- Place the cursor in the panel where its icon displays the OS default one\n- Move the cursor fast enough onto the scene. On its way pass over text panels.\n- The cursor icon is the default's one, not the cross as it should.\nSee the .gif for visual explanation:\n", "Cycles X: Camera-visible lamps are not affected by holdout\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.96\n\nBroken: version: 3.0.0 Alpha\n\nBlender 3.0 adds a feature where camera ray visibility can be enabled on lamps, making them directly visible. However, if this option is enabled simultaneously with the holdout option, the lamp will remain visible. Holdout should override camera visibility, as holdout can be changed per-view layer. With the current behavior, a directly-visible lamp will appear again on holdout layers, copying it's direct brightness for every layer it appears as a holdout in.\n\nSee attached .blend file, which contains a point lamp with holdout and camera visibility both enabled. Note that the lamp remains visible. In fact, the holdout option seems to have no affect at all.\n\n[holdout_lamp_bug.blend](holdout_lamp_bug.blend)\n\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)", "Improved Mask icon with disabled state\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 @joeedh and @JulienKaspar.\n\n# Context\n\nWe discussed the need to update the icon for Masks.\nThere is no \"disabled\" version of the icon, which is very needed for [auto-masking in sculpt mode](T101593), and masked layers in grease pencil.\nApart from that the current icon is also way too similar to other icons like Overlays.\n\nCurrent masking icon:\n\n\nProposed icons:\n\n\nThese are the `CLIPUV_DEHLT` and `CLIPUV_HLT` and are currently used in the 2D curve UI and grease pencil layer masks.\nThey work much better as a recognizable industry standard masking icon.\n\n# Goal\n\n`CLIPUV_DEHLT` will be the new universal masking icon for various areas of Blender:\n- Auto-Masking\n- Mask modifier\n- Mask editing (Image Editor)\n- Mask Data-Block\n- Grease Pencil Masks\n\nIn the case of Auto-Masking, the header icon needs to be switched with `CLIPUV_HLT` if all auto-masking options are disabled.\nFor the implementation the `View3D_PT_object_type_visibility` is a good reference.\n\nThe icons of `GPencilLayerMask.invert` also need change.\nFor now we should use the `select_intersect` and `select_subtract` icons as a more accurate depiction: \n\nLater on the grease pencil module can change or create new icons for this part of the UI.\n\n", "Weight paint: front face falloff checkbox looks inactive (dimmed)\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\nBroken in 2.93.7 too\n\nFront face falloff checkbox Looks dimmed, but it is active\n\n\nAlso in the n-panel there is correct variant. And another one incorrect.\n\n\n[2021-12-19_04-11-58.mp4](2021-12-19_04-11-58.mp4)\n", "Custom Properties Improved UI\nCurrent UI:\n\n\n\n- [ ] Allow reordering of custom properties in ways that make the most sense to an artist\n- [ ] Allow editing from the sidebar\n- [ ] Decrease the space between properties\n- [ ] Using an 'X' icon to delete\n- [ ] User and edit icon instead of \"Edit\"\n- [ ] Better location of icons\n- [ ] Group properties by the selected object/bone (see image)\n- [ ] Add a drop-down to select the data type\n- [ ] Allow the use of checkboxes to represent booleans\n\n", "Sculpt Mode Border Mask Tool Todo\n## Sculpt Mode Border Mask Tool Todo\n * - [x] {icon circle color=red} When this tool is selected, it currently shows the wrong tool settings which affect the brushes, not this tool. These should not be visible when this tool is active.\n * - [ ] {icon circle color=yellow} We should add a tool setting to add/remove the mask as you drag. Currently, the only way to remove from mask, is very hidden: You drag with RMB. This could become more consistent and more discoverable if we added the same Add/Remove buttons as with other Sculpt tools" ]

[ "Grayed out UI layout makes custom icons brighter\nOperating system: Windows-10-10.0.17134 64 Bits\nGraphics card: GeForce GTX 860M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35\n\n\nBroken: version: 2.80 (sub 64)\n\n\nGrayed out UI layout makes custom icons brighter instead of dimmed.\n\n\n - Open attached blend file: [icon_brightness.zip](icon_brightness.zip)\n - Text Editor → Run Script.\n - 3D View → Sidebar → TEST tab.\n - Toggle Enable Layout property and look at the icons.\n\n[2019-05-15_00-43-24.mp4](2019-05-15_00-43-24.mp4)\n\n\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", "Normal map node worked is not correct\nOperating system: win10 x64\nGraphics card: gtx 1650\n\nBroken: 3.5.0, 1be25cfff18b, 2023-03-29\nBroken: 2.93\nWorked: 2.92\n\nCaused by 1c22b551d0\n\n\nI do not think that this is an error or a bug, rather it is not a refinement. \nIn some cases, the normal map node does not display them as you would like. \n\n\nI created a Hight poly model and bake it into a plane. Then I applied the resulting texture to the Low poly base mesh. It didn't display correctly there, only part of it smoothed out, but the other part showed sharp edges, very similar to the Fresnel effect\n\n", "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", "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", "Bug - Refraction BSDF in Eevee interferes with Render properties > Film > Transparency - it blocks the transparency so to speak.\nBest demonstrated with a video (please note that the refraction bsdf is transparent, so objects can se seen through, so can the world background - when the world is not transparent that is) :\n\n[DE3VFV8aIO.mp4](DE3VFV8aIO.mp4)\n\n", "EEVEE & Viewport Module\nThis page is in the process of being fully replaced by #eevee_viewport.\n\n---\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- `(straightforward)` - *Task which is straightforward to implement, which don't rely on larger API changes or refactoring.* \n\n# Long Term Projects\n\nDevelopment may span multiple release cycles.\n\n- {icon circle color=yellow} #68989 ( Selection future-proof design)\n- {icon circle color=yellow} #68990 (Vulkan support)\n- {icon circle color=yellow} [D5442: LANPR line rendering (summer of code)](D5442)\n- {icon circle color=yellow} #68991 (Fisheye / panorama in EEVEE)\n- {icon circle color=yellow} #68993 (Stereo Panorama in EEVEE)\n- {icon circle color=yellow} #68994 (VR design / usability)\n- {icon circle color=yellow} #68995 (VR input integration and mapping)\n- {icon circle color=yellow} #68464 (Better Motion Blur)\n- {icon circle color=green} #68996 (OpenSubdiv GPU acceleration)\n- {icon circle color=green} #68997 (Panorama selection support in viewport)\n- {icon circle color=green} #68463 (Dynamic Indirect light cache)\n- `?` #68998 (Virtual Reality (XR/VR/AR/MR))\n\n\n# Medium Term Projects\n\nDevelopment should be possible in a single release cycle.\n- {icon circle color=red} #71347 (Virtual Reality - Milestone 1 - Scene Inspection)\n- {icon circle color=yellow} #68478 (World Light Extraction)\n- {icon circle color=yellow} #68453 (Anisotropic BSDF)\n- {icon circle color=yellow} #68456 (Shadow catchers)\n- {icon circle color=yellow} #68474 (Clustered Light Culing)\n- {icon circle color=green} #67579 (Improve NDOF navigation)\n- {icon circle color=green} #54638 (OpenGL headless rendering)\n- {icon circle color=green} #68479 (Pointiness support)\n- {icon circle color=green} #68460 (Multiscatter Glossy BSDF)\n- {icon circle color=green} #68459 (Hair BSDF)\n- {icon circle color=green} #68458 (Velvet BSDF)\n- {icon circle color=green} #68477 (Parallax Occlusion Mapping)\n- {icon circle color=green} #68468 (Depth of Field Refactor)\n- {icon circle color=green} #68472 (Light Nodetree support)\n- {icon circle color=green} #68470 (Shadow buffers)\n- {icon circle color=green} #60779 (3D Viewport clipping support)\n\n# Paper Cuts\n\nSmall improvements and polish.\n\n- {icon circle color=green} #64281 (Option to lasso-select using geometry instead of object centers.)\n- {icon circle color=green} #69282 (Ability to cancel viewport operations (rotate/pan/zoom))\n- {icon circle color=green} #68206 (Lag reading viewport depth buffer in LookDev mode)\n- {icon circle color=green} #70803 (Support Viewport roll - around the cursor position) `(straightforward)`\n- {icon circle color=green} #73214 (Armature Object's \"Display As\" does nothing)\n- {icon circle color=green} #73732 (Grid-lines vanish in perspective view, when viewed from the side)\n", "EEVEE: Blender Crashes when rendering specific File\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00\n\nBroken: version: 2.93.0\nWorked: (N/A)\n\nBlender crashes when rendering specific file. It only seems to happen with this file - when I render other (even larger) files with the same inputs it works fine, but with this one it crashes every time. The error message is EXCEPTION_ACCESS_VIOLATION, but I received the data from an open source website and it is placed in a folder on my computer that I have full access to. Debug report: [blender_debug_output.txt](blender_debug_output.txt)\n\nSave NZ_Compressed40pc.jpg to desktop \nOpen Dev.blend\nIn the shader editor for the plane, ensure the image texture has NZ_Compressed40pc.jpg linked as input.\nRender>render image\n\nTest File:\n[Dev.blend](Dev.blend)\n", "Cycles does not respect the texture alpha mode\nOperating system: Gentoo Linux \nGraphics card: AMD 290x\n\nBroken:\n2.79b\n2.80 f15205b93f56e454b76d5a222fdb9a9665b99907 2018-01-02\n\nEevee respect the alpha mode in the texture settings, however cycles does not.\n\n[alpha_test_pack.blend](alpha_test_pack.blend)\n\n1. Load the attached .blend file\n2. Change the texture settings for the `Alpha:` setting for the image texture node (with use alpha on).\n3. Notice that in cycles the `Alpha:` setting has not effect, the texture alpha is always premultilied.", "Cycles shading glitch\nOperating system: Windows 10\nGraphics card: AMD\n\nBroken: 3.4.1\nWorked: ?\n\nCycles shows incorrect shading, also different from Eevee. (The file is very simplified just to showcase the problem)\nI'm thinking it is a variation of T99933 bug but not sure so tell if that's the case\n\n[bug.blend](bug.blend)\n1) Open the file, switch to rendered view. Normals should look like this\n\n2) In the material disconnect the alpha socket, now it should look different.\n\nIs alpha supposed to affect normals at all?\n3) Repeat the same in Eevee, results look consistent", "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", "Burned Out Screen Space Reflections in Eevee Viewport - Nvidia GT 750M\nOperating system: macOS 10.14.3\nGraphics card: NVIDIA GeForce GT 750M 1024 MB\n\nBroken: 2.90.0\nWorked: 2.79\n\nIn some cases I detected that the Screen Space Reflections in Eevee Viewport gets out of control.\nA few seconds after switching to the viewport (even when viewport samples are set to 1) the issue kicks in and – as the sampling continues – an increasing percentage of the reflections get totally white.\n\n\n\nThe renders are correct.\nSurfaces affected by reflection planes are correct.\nHiding the chandeliers meshes solves the problem. Switch tab and back for this to work.\n\nI was able to strip down the scene and identify the source of the problem: Originally I set up the glass material with \"multiply\" blending. This was converted (when opened with belnder 2.82 alpha) to a \"Shader to RGB\" and a \"Transparent BSDF\" node. [1]\n\nThe \"Shader to RGB\" causes the problem in 2.82.\nThe \"multiply\" blending of the material causes it in 2.8.\n\nOpen the attached file.\nSwitch to LookDev or Rendered viewport.\nWait.\n\n[Chandelier.blend](Chandelier.blend)", "Command Line Rendering with EEVEE is slow\nWin 7 Pro 64Bit \nGTX 1070\nDriver: 417.22\n\nBroken:\nblender-2.80-606223f6a61-win64\n\n\nIf I render with EEVEE via Command Line, the GPU Load is around 40-50% (4min 33sec).\nRendered the same scene in a normal way via Gui, the GPU Load is around 90-98% (3min 20sec).\n\nIf I render the same scene with Cycles via Command Line, the GPU Load is around 90-98%\n\nblender -b PathToBlend -a\n\n\nI've tried several scenes with the same result all the time.\n\n[cube-eevee.blend](cube-eevee.blend)\n\n[cube-cycles.blend](cube-cycles.blend)\n", "Alpha hashed material produces shifting artifacts when animated in EEVEE\nWhen an object with material that has alpha hashed transparency is animated in EEVEE, the noise pattern may look either unstable or shifting as shown below: \n[alpha-hashed-transparency-problem.mp4](alpha-hashed-transparency-problem.mp4)\n\n\n\nYou can observe that the artifacts on top staying in place rather than rotating with the cube while those on the sides keep flickering, thus producing shifting and unstable appearance.\n\nThe symptom is also noticeable when changing the camera position in rendered viewport mode in Blender. And it's particularly problematic in UPBGE (a fork of the old BGE based on the latest Blender source) because a game engine must animate objects in realtime with relatively small number of samples per frame.\n\nUpon an examination from the developers of UPBGE, it is found that the problem is due to the fact that the current implementation of alpha hashed transparency uses the world coordinate instead of the object space, as it is often recommended (e.g. [2017 ACM SIGGRAPH Symposium on Interactive 3D Graphics and Games](p4TYf5DDpbQ)).\n\nIt appears that a simple change from the world to object coordinate fixes the problem as shown in this [test commit (see line 80) ](e0a8638d0b255f2fc6ce778d10dd0d12a467b4d3#diff-2b8bf4f9e10009510d02c14e3659ee032c73f829de5453d6abcdf6a3f884fdfdR80), which produces the following result:\n[alpha-hashed-problem-solved.mp4](alpha-hashed-problem-solved.mp4)\n\nIt's my understanding that the [original author ]() decided to use the world matrix to avoid the difficulties with certain corner cases, like when the object is scaled by an extreme factor. However, while such a problem may be circumvented relatively easily (e.g. discard the scale information from the matrix) such a problem described above may pose more substantial issues with making an animation or rendering in realtime.\n\nSo, I hope this problem and the suggested fix may be evaluated again since we have more people interested in using Blender for such purposes now, thanks to the gaining popularity of EEVEE.", "Eevee clamping color values when viewport rendering and using viewport HDRI\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 466.11\n[system-info.txt](system-info.txt)\n\nBroken: version: 3.0.0 Alpha\nWorked: (never)\n\nWhen doing a viewport render, color values are being clamped. In 2.92 a workaround for this was introduced - if you disable overlays, color is being processed as it should.\nHowever, if you use a viewport HDRI, even with the overlays turned off, values are still clamped.\nAs these two are often used together to get some quick snaps, it is a little inconvenient\n\n\n\n[#88288.blend](T88288.blend)\n\n- Open file\n- Switch to rendered view\n# Viewport render image\n\nColors are clamped even though overlays are disabled\n", "Textures mapped on UVs with very high location values appear emissive when rendering on CPU\nTextures mapped on UVs that have vertices with very high location values appear emissive or black with CPU rendering. The UV vertex location values are around the range -3960966. \n\n### Original Report\n\nOperating system: macOS Monterey 12.4\nGraphics card: Apple M1 Max\n\nBroken: In every version I can find but for example in 3.2.1 2022-07-06 and 2.80 2019-07-29 as well as the nightly alpha 3.3.0 2022-07-17\nWorked: Cannot find a version in which it works.\n[system-info.txt](system-info.txt)\n\n**Background**\n\nI'm generating images in python using a script and I load objects from a dataset called SceneNet. Some of these objects have poor UV mapping, which is not a big deal, but it's causing rendering artifacts which are a problem.\n\n**The Bug**\n\nWhen a surface has incorrect UV mapping and has a stretched out texture, it leads to the surface becoming extremely bright. It does not *emit* light, the issue only occurs when there is a light source, emissive surface, or world background in the scene. The surfaces with stretched textures seem to multiply the reflected light by a high factor.\n\n**In the viewport** the issue only occurs when rendering on CPU. When rendering on GPU, the texture looks stretched out but with the correct color and not bright.\nExample 1:\nGPU ONLY  CPU \nExample 2:\nGPU ONLY  CPU \nExample 3, the same scene but with UV mapping fixed for part of the wall:\nCPU \nExample 4, blender 3.3.0 2022-07-17:\nGPU  CPU  Replaced problem faces with 100% white diffuse material \n\n**When rendering to file**, I have seen two cases:\n - The image looks like in the viewport while rendering, but when finishing the render the image becomes black.\n - When rendering with mixed CPU+GPU in Blender 3.1.0, the upper part of the image has the lighting issue from the CPU, and the rest of the image looks fine. \n\n**Desired behavior:**\nThe result from pure GPU rendering is the desired behavior.\n\nOpen attached .blend file, change viewport to render, switch between GPU and CPU rendering to see the difference. Try render to file using CPU/GPU/Mixed.\n[bug-textures.blend](bug-textures.blend)" ]

[ "Texture node in EEVEE makes shader pink in lookDev and render view mode\nOperating system: Ubuntu 18.04\nGraphics card: AMD Radeon 580 RX\n\nBroken: blender-2.80 e2d04229c38b\nWorked: blender-2.80 2c0da4a3db96\n\nTexture coordinates node turns material color to pink in EEVEE. Works fine in Cycles.\n\n[broken shader.blend](broken_shader.blend)", "Pink result in lookDev and Render mode (Eevee) with TextureCoordinate node NOT with UVMap node.\nOperating system: Linux-4.8.0-53-generic-x86_64-with-debian-stretch-sid 64 Bits\nGraphics card: GeForce GTX 780/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 384.130\n\n\nBroken: version: 2.80 (sub 60)\nWorked: version about a week ago?....sorry not 100%\n\n\nGot consistent pink result when using the TextureCoordinate node but not with the UVMap node. Tested on all outputs of the TextureCoordinate node not just the uv output. They all fail. Regardless of simplicity or complexity of the network i have the same issue. As long as a TextureCoordinate node is used (even if it is \"mix\"d out of the final result) i get this problem.\n\n- Create a geo object,\n- put material on it\n- Add texture (image or procedural)\n- plug to colour\n- control vector of texture with TextureCoordinate - PINK!!\n- control vector of texture with UVMap - NO PINK!\n\nNOTE: This issue doesn't exist with cycles.\n\nFile:\n[test_pinky.blend](test_pinky.blend)\n\nSample Images:\n\n\n", "Pink placeholders in Eevee instead of textures that point in the right path\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 416.94\n\n\nBroken: version: 2.80 (sub 60)\nWorked: (optional)\n\n\nI have a scene created in an older version of 2.8. I reopened it in the latest build and when I switch to Eevee, every texture that I used shows as pink placeholders. I checked and double checked and the texture paths are all correct. The textures are correctly applied and displayed when I switch the renderer to Cycles." ]

[ "Crash with lineArt modifier and Armature\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: version: 3.0.0 Alpha\nExperienced with 2.93.2\n\nHaving a line art object in the scene applied to an object 'A' when there is an armature on object 'B' makes blender very unstable. A simple scroll in the timeline will crash instantly.\n\n\nIn the attached file, what I did : \n- Create a cube, subdivided along Y, add a simple armature, keyframe it with a simple motion.\n- Duplicate the cube, apply the armature.\n- Select the second cube, shift-a -> Object Line Art\nFrom there : \n- Scroll the timeline... Crash.\n\nIf I delete the animated cube, scrolling works fine. Disabling it in viewport as well.\n\n\nI also tried adding a simple cube, instead of duplicating the initial \"armatured\" cube, and adding the Object Line Art to it, but the same crash occurs.\n\n[LineArtCrash.blend](LineArtCrash.blend)\n\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", "Collections (parent task)\nPossible improvements for collections user interface:\n* G-key group operators in the 3D viewport and object properties should become more clear.\n* Creating a new collection in the outliner could put all the selected objects (and collections?) in it.\n* Shortcut keys to improve usability, as in #54707.", "Irradiance volume visibility collection not working properly\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.5\nWorked: Unknown\n\nThe irradiance volume visibility collection is not working as intended. File is included.\n\nDownload [this example. ](view?usp=sharing)\nWhen you open the file you'll notice immediately that the IV is already set to Collection, which means in theory it should NOT be affecting anything in \"Collection 2\". Even if you delete the light cache and rebake it, no matter what happens, it affects everything outside \"Collection\" regardless. The way I see it, visibility collection is meant to affect whom it collects lights from and meshes to light up, but so far it only seems to care about gathering lights alone.\n\nThis ALSO affects rendering it out. For that, just change the view layer to V1, and turn on Collection 2 to replicate.\n\nWorse still, disabling the visibility/renders of the irradance volume still lights up other objects no matter what. This, in my opinion, is a huge issue. It means I have to delete the light cache whenever I need it off, and rebake it, wasting a TON of time just to render it and only have it affect a singular object.", "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", "Replace object-linked materials feature\nMaterials linked to objects have some issues:\n- They cause problems for geometry nodes, which can arbitrarily change material slots during evaluation.\n- They tend to be confusing, partially due to relying on consistent indices between two different lists\n- They cause large performance issues for reference counting in the main data-base, since geometry-level operations also have to be aware of objects\n- Object-linking is theoretically redundant now that materials can be changed during evaluation.\n\nBecause of that, it would be best to remove the feature and replace it with something more generic.\nMost workflows are already possible with nodes like the \"Replace Material\" node, but we have to be able to replicate the behavior exactly in order to version the feature away. There are a few options:\n1. Add a modifier with a UI-list interface that sets materials at specific slots.\n2. Add the necessary features to geometry nodes (loop? lists?) necessary to make the behavior completely generic\n3. Just add a geometry node group with enough nodes to handle whatever list of object linked materials the object had.\n", "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.*", "`Object().users_collection` and `Object() in Collection().objects.values()` don't work in drivers.\nOperating system: Linux\nGraphics card: Intel\n\nBroken: 2.92\n\n\n`self.id_data.users_collection` always reads out to an empty `tuple` in drivers.\n\n`self.id_data in bpy.data.collections- [x].objects.values()` always evaluates out to `False` in drivers, even when the equivalent expression evaluates as `True` in the interactive terminal.\n\n* Add a driver to any property of the default cube.\n* Enable \"Use self\" on the driver.\n* Set the driver code as follows: `[print(self.id_data.users_collection),0][-1]`\n\nThe empty `tuple` will be printed out to the console.\n\n* Set the driver code as follows: `[print(next(iter(c for c in bpy.data.collections if self.id_data in c.objects.values()))),0][-1]`\n\nA `StopIteration` exception will be raised.", "Unable to fix broken linked IDs when renamed in libfile\nWindows 10\nWindows 7 x64\n\nWorked: 2.82\nBroken: 2.83.0\n\nCant rename linked collection. Error: Cannot edit external library data\n\nDefault Blender setup (first file lets call it assets.blend)\nCreate a collection and name it \"Test\" \nCreate a cube and move it to \"Test\" collection\nSave the file\n\nCreate another file (lets call it level.blend)\nLink the \"test\" collection from the assets.blend\nCheck all linking options before hiting link\nSave the file\n\nNow open assets.blend again and rename \"Test\" collection to \"Cube\"\nAnd save it again.\n\nOpen level.blend\nA message appears that link is broken\nGo to Outliner and change Display mode to Blender File\nNow go down to the linked collection\nDouble click broken collection to rename it\nError message appears \"Cannot edit external library data\"\n\nRenaming linked collections works fine in 2.82\n", "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)", "Collection instance set to Display As Wire doesn't show in Solid mode when not selected\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.94\n\nBroken: version: 3.3.1\n\nCollection instanced to scene display options are probably wrongly addressed in code. I'm attaching screenshots with descriptions (JPEGs).\n\n\n\n\n\nCreate an object inside a *Collection*. Instance *Collection*to scene and change its *display as* options to *Wire* and/or *Bounds*. You'll see that *display as bounds* shows wireframe while *display as wire* doesn't show anything. I'm attaching my file to help you investigate.\n\n[displayAsBug.blend](displayAsBug.blend)\n\n(Why hunting bugs feels so good?! Glad I can help with developing Blender 💘)\n\n", "Copying scene unhides hidden collections\nWindows-10-10.0.16299 64 Bits\nGeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.67\n\nBlender 2.80 (sub 53)\n\n[hidden_collections_copy_scene_bug.blend](hidden_collections_copy_scene_bug.blend)\n\nOpen attached file. There are two hidden collections.\nMake a copy of the scene using either \"Link Object Data\" or \"Full Copy\".\nCollections in the newly created scene will be set to visible.", "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", "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", "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" ]

[ "Outliner: Collection dragging tooltip is not updating\nBroken: e8027ec2a0ca (3.0)\nWorked: e8027ec2a0ca~ (2.93)\n\nWhen you drag a collection the tooltip about linking is missing.\n\n* Drag `Collection` inside the `Scene Collection`.\n* The tooltip should say \"Move inside collection (Ctrl to link)\".\n\nNote: The linking itself works, the problem is only the tooltip." ]

[ "Stereoscopic - right side has incorrect render (Eevee)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.93.4\nWorked: unknown\n\nStereoscopic creates an incorrect image for the rendered Right side (Eevee).\nThe right side seems to be a mix of the correct render and a render with low samples (1?). This is clear on the soft shadows and AO.\n \nIt can only be resolved by enabling Screen Space Reflections, which isn't always desirable obviously. \n\nOpen attached blend file and render. \nCompare left and right render.\n\n[stereoscopic_rightSide_difference.blend](stereoscopic_rightSide_difference.blend)\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.", "Eevee's AO shades even outside of the distance\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.0\n\nEevee's AO creates certain amount of gradients and shading even outside the Distance area. I'm not refering to the typical screen space oclussion problems. \n\nFor example, if you turn Distance to 0, instead of getting the same result as having AO turned off, you get a gradient. Here's how it looks with a flat lit, diffuse scene:\n\nDistance 0, Factor 0:\n\nDistance 0, with a Factor of 10 to exagerate the effect:\n\n\nEven if the gradient is subtle with Factor 1, it can be very visible in certain workflows. Example: There are no other screen space effects in this image, other than AO, which has small distance anyway but this gradient spans the entire image (I'm aware that 360 is not officially supported but still, the gradient itself is not a fault of the 360 stitching and can be a problem for regular images too \n\nIf this is a limitation of the method, may I suggest a clamping slider of some sort for very light values? Thank you❤\n\nOpen the file and turn AO on and off\n[AOBUG.blend](AOBUG.blend)\n\n", "EEVEE: Material update does not trigger shadowmap update\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nModify procedural does not update real time in view port shading in EEVEE \n\nJust a cookie with procedural noise in front of a point light in EEVEE (remove hdri if it's missing), I could not see changes while modify noise texture, also with viewer\n\nAttached blend file and video\n[studio-light-v1.blend](studio-light-v1.blend)\n[studio-procedural-gobo.mp4](studio-procedural-gobo.mp4)\n", "File thumbnails don't always show rendered result\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.81 (sub 16)\n\nBlender doesn't save previews that look as the eevee (or cycles) render when using a camera.\n\nUse a file with a camera, save while rendered mode is on, and it will look like workbench mode.\nDelete the camera, it will save as the mode is displayed and will do as rendered if that's what you have.", "Subdivision modifier artifacts in Blender 2.80\nOperating system: Windows 10\nGraphics card: 1080ti\n\nBroken: \n2.80 downloaded on the 3rd of Feb, 2019 as found on the download beta section\nWorked: (optional)\n\n\nSome artifacts around the out circle in the blend file, this is not present in Blender 2.79\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\nload attached file, doesn't matter if it is Cycles or Blender the artifact is present.\n\n[ukelele.blend](ukelele.blend)", "Alpha mode 'Straight' on Image Texture node behaves differently between Cycles and Eevee\nOperating system: Windows 10 Pro x64\nGraphics card: GTX 1080Ti for display, RTX 3090 for render\n\nBroken: 3.3.1\nWorked: I don't know\n\nWhen the `Alpha` property is set to `Straight`, the result is different between Eevee and Cycles.\n\n\n- Open the .blend file provided\n- Set one of the viewports to Material Preview and the other to Rendered\nNote that the results of the images are different\n[alpha_mode_eevee_vs_cycles.blend](alpha_mode_eevee_vs_cycles.blend)\n\nOriginal file\n[test leaking_ori.blend](test_leaking_ori.blend)\n", "Aliased wireframes + modifier edit mode display issue\nOperating system: Linux-4.15.0-51-generic-x86_64-with-glibc2.27 64 Bits\nGraphics card: GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.143\n\nBroken: version: 3.4.1\n2.90\nWorked: 2.79, 2.81\n\nEdit mode aliased wireframes (selected/unselected) of a mesh with modifiers looks broken for both ortho and perspective views, even with reasonable clipping range.\n\n**Steps to reproduce**\n\n* Open file\n* Disable all anti-aliasing and smoothing in preferences > Viewport > Quality\n\nSelection looks bad, but also other edges are bit fuzzy. Disable mirror modifier visibility in edit mode and edges looks better.", "EEVEE: Contact shadows problem on layered hashed materials\nOperating system: linux open source drivers\nGraphics card: rx 6800\n\nBroken: 2.93\nWorked: Never (2.83+)\n\ncontact shadows dont look correct on certain angles for layered alpha hashed materials(hair cards for example). iissue is more noticable in viewport then in final render, but it is noticable in both.\n\nmake a sphere make it alpha hashed and slightly transparent then duplicate and scale geometry with slight offset to make layers then rotate around object with contact shadows enabled on the lamp\n\n\n[contact shadows problem.blend](contact_shadows_problem.blend)", "Workbench: Strange anti-shadow when clipping cuts landscape\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 473.04\n\nBroken: version: 3.1.2\n\n\nAs title says. This shadow looks like this:\n\n\nDemo:\n[2022-05-06_01-02-27.mp4](2022-05-06_01-02-27.mp4)\n\nYou can test it by your own with my file\n[WB shadowbug.blend](WB_shadowbug.blend)\n\n", "Holdout doesn't work with Mix Shader correctly in Eevee\nOperating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13\n\nBroken: version: \n- 2.92.0 Alpha\n- 2.91.0\n- 2.90.1\nWorked: 2.83.x\n\nHoldout doesn't work with Mix Shader correctly in Eevee. \n\nWhat I expect when mixing with 100% Holdout:\n\n\n\nWhat I get instead:\n\n\n\n\n\n - Open the simple blend below\n - Move the timeline from 0-100, which moves the Mix Shader Fac from 0-1.\n - When at frame 1, it should be a 100% Holdout, but notice that this isn't the case\n - Switch to Cycles and verify that it indeed handles this case correctly\n\n[holdout_eevee_bug.blend](holdout_eevee_bug.blend)\n\n", "Caustics not work as expected\nHi,\nI'm going crazy with shadow caustics.\nOddly they work when they turn off.\nIn the attached scene [caustics_not_work.blend](caustics_not_work.blend), if you disabled caustics on lights or objects, they will be displayed, otherwise no caustics will be displayed.", "Command Line Rendering with EEVEE is slow\nWin 7 Pro 64Bit \nGTX 1070\nDriver: 417.22\n\nBroken:\nblender-2.80-606223f6a61-win64\n\n\nIf I render with EEVEE via Command Line, the GPU Load is around 40-50% (4min 33sec).\nRendered the same scene in a normal way via Gui, the GPU Load is around 90-98% (3min 20sec).\n\nIf I render the same scene with Cycles via Command Line, the GPU Load is around 90-98%\n\nblender -b PathToBlend -a\n\n\nI've tried several scenes with the same result all the time.\n\n[cube-eevee.blend](cube-eevee.blend)\n\n[cube-cycles.blend](cube-cycles.blend)\n", "CPU render will look different to GPU render and fails randomly\nWin 10, GTX 880M, GTX 1080TI Founders Edition\n\nBroken: blender-2.79.0-git.2ca1f29-windows64\nWorked: na\n\nAttached you'll finde a scene what has issues with GPU rendering. The scene is using the old shaders with a bevel shader (OSL).\n\nThe preview will not start or maybe it takes a very long time. Here nothing happened.\nIn GPU mode the preview starts as expected.\n\nWhen I try to render with F12 in CPU mode it doesn't start or maybe it will start after a long time. Here nothing happened after 10 minutes.\nWhen I render a small region with CPU it takes a long time till it starts to render.\nWhen I start rendering in GPU mode it starts fast as expected ignoring OSL of course.\n\nIn the ZIP and attached you'll see a picture with a split screen. Left side is GPU. Right CPU. The results are different. Transparent parts with DOF will have extreme noise.\n\nLoad the scene and press F12. Here CPU render will not start as expected.\nSwitch to GPU and press F12. Rendering will start.\nDefine a small region where the transparent parts are. Press F12. It will take really long but start. Result has noise at the transparent parts.\nThis might be a bug in the Cycles render engine or an issue with the shader tree.\n\n[170902_Blender_279_Cycles_CPU_Issue.zip](170902_Blender_279_Cycles_CPU_Issue.zip)\n\n\n\n", "Artifacts around shadow catcher object\nOperating system: Win 10 PRO 19041.1348\nGraphics card: GTX 1080\n\nBroken: Official 3.0\nWorked: 2.9 lts\n\n{[F12718649](image.png),size = full}\n[头图制作B.blend](头图制作B.blend)\n\nLine is faintly visible at Y=472px height.\n\nThis doesn't happen when Denoise node Prefilter is set to Accurate, but when opening older files, Fast option is used by default.\n" ]

[ "Blender 2.82 EEVEE Sun Shadows look terrible in viewport\n{[F7833569](untitled.blend)}Operating system: Windows-10-10.0.17763 64 Bits\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.30\n\nBroken: version: 2.82 (sub 0)\nWorked: (optional)\n\n[Blender 2.82 EEVEE Sun Shadows look terrible in viewport, pixelated even at the highest shadow maps setting. Shadows from other lights looks ok at high shadow maps but sun shadows in EEVEE look terrible. it used to look good in version 2.81]\n\n[ In EEVEE render view change the light to sun and look at the shadow of any object]\n\n" ]

[ "GPencil: Tint modifier in Fill mode, don't get restricted by vertex group influence\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nTint modifer in Fill mode, don't get restricted by vertex group as influence. in other hand, it works well on stroke mode,i really need this to be fixed really soon as possible please, see video\n\n", "Texture painting with mirroring and viewport clipping does not mirror\nOperating system: Linux-5.8.4-200.fc32.x86_64-x86_64-with-fedora-32-Thirty_Two 64 Bits\nGraphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 450.66\n\nBroken: version: 2.91.0 Alpha\nWorked: never, 2.79 also did not do this\n\nTexture painting with mirroring and viewport clipping does not mirror\n\n[texturepaint_mirror_clipping.blend](texturepaint_mirror_clipping.blend)\n- Open .blend\n- Do a stroke on the right side --> updates on the left as well because x-mirroring is turned ON\n- (Undo)\n- {key Alt B} a clipping region in the viewport\n- Do a stroke again on the right side --> updates on the right side\n- {key Alt B} to clear the clipping region in the viewport, see no updates have taken place on the clipped left side\n\nExpected: stroke should update the clipped area as well [as we do for vertexpaint, weightpaint and sculpting], everything else would be inconsistent\n\n", "overlay.show_paint_wire doesn't work in vertex paint modes depending on edit mode selection\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.80?\n\nThis overlay option seems to take into account edit-mode selection\n\n\nHere's what it's supposed to do:\n[viIeK7Tkv0.mp4](viIeK7Tkv0.mp4)\n\nBut on 2.93 and 3.0 it appears to do nothing in Weight/Vertex Paint mode if the geometry is selected in edit mode. This seems like a bug, unless it's some odd design choice?\n\n- Create a cube and select all its verts in edit mode.\n- Enter weight paint mode\n- Toggle the Show Wire setting under Viewport Overlays->Weight Paint (NOT \"Wireframe\" under Viewport Overlays->Geometry)\n- Nothing happens\n- Switch to edit mode\n- Deselect all with Alt+A\n- Go back to weight paint mode\n- Wireframe display now works as expected.\n\n\nNote: This now changed again in 44d2479dc3 (now it does not draw **at all** -- reported separately in #89880 (overlay.show_paint_wire doesn't work anymore))", "Backface culling setting applies in Material Preview shading and affects selectability\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 (sub 3)\nBroken: version: 2.83 (sub 17)\nWorked only if face orientation on in 2.82a release\n\nBackface culling setting applies in Material Preview shading and affects selectability.\nExpected: if it is visible and selectable, I should be able to select it.\n[2020-05-26_00-02-02.mp4](2020-05-26_00-02-02.mp4)\n\n**Steps to reproduce**\n[nonselectable.blend](nonselectable.blend)\n\n- Open file\n- Try to select octagon", "Support Face color attributes for painting\nFace color attributes should be supported for sculpt painting and vertex paint mode.\n\nThey should also be listed under the Color Attributes UI List.\n\n", "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", "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)", "Mirror Uv\nThere already exists an operator called Copy Mirrored UV Coords. This could be extended to support the features described below\n\n\n- From +X to -X for example (source can be positive or negative X, Y or Z) \n- Options:\n - By object space\n - By world space\n - By topology \n\n\n\n**Starting point**\n\n\n**Desired result**\n\n", "Reflection plane significantly reduces intensity of normal maps on affected surfaces\nOperating system: Windows 10\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU\n\nBroken: Currenct main.\nWorked: Never.\n\nWhen a reflection plane capture is added to any scene in EEVEE, the resulting reflections on surfaces affected by said capture will be significantly less affected by shader-based normal maps.\n\nComparison:\n| Without a Reflection Plane | With a Reflection Plane |\n| -- | -- |\n|  |  |\n\nThis is unexpected behavior, and although I do not fully know the intricacies of how the reflection plane capture functions, it would ideally not affect surfaces in this way.\n\nOpen the included demo file and switch to rendered view.", "Curve / Geometry / Bevel Objects don't accept Mirror Curve\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\n[i try to use a curve with mirror modifier, to use it as Bevel Object in ObjectDataProperties Curve. Now i see the half , it miss the modifier]\n\nCreate curve with mirror modifier, add it to new curve inside ObjectDataProperties Bevel Objet\n[CurveBevelMirror.blend](CurveBevelMirror.blend)\n\n", "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)", "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", "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)", "Grease pencil: unstable offset height (surface drawing)\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\n\nWhen I use perspective camera, and try to drad on surface with GP, offset is unstable and depends on distance from camera.\n\nTest File:\n[#94735.blend](T94735.blend)\n[2022-01-08_10-23-37.mp4](2022-01-08_10-23-37.mp4)\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 :)" ]

[ "weight paint gradient is broken when mirror modifier is enabled\nOperating system: Windows-10-10.0.17763 64 Bits\nGraphics card: 67EF:CF ATI Technologies Inc. 4.5.13474 Core Profile Context 22.19.162.4\n\n\nBroken: version: 2.80 (sub 75)\nWorked: (optional)\n\n\nGradaient tool in weight paint mode is broken when mirror modifier is enabled. In particular, drag to start from out of mesh is not working.\nRelated task : T65872\n\n1. Move the default cube in Edit mode for don't overlap the mirror\n2. Add mirror modifier to the cube\n3. Use Gradient tool in weight paint mode\n" ]

[ "Found material bindings on prim at path <path> but MaterialBindingAPI is not applied on the prim\nOperating system: Linux-6.1.0-7-amd64-x86_64-with-glibc2.36 64 Bits\nGraphics card: Mesa Intel(R) UHD Graphics (CML GT2) Intel 4.6 (Core Profile) Mesa 22.3.6\n\nBroken: version: 3.5.1\nWorked: ?\n\nTextures/material are not getting imported from .usd files.\n\nDownload and extract USD dataset: island-usd-v2.0.tgz\nFile -> Import -> USD -> import island/usd/island.usda \n\nThe imported file will not have any materials assigned, the terminal log will include: \n Found material bindings on prim at path <path> but MaterialBindingAPI is not applied on the prim.\n\nIt also happens with the NVidia Omniverse industrial pack assets.\n\n", "shadow catcher appearing in vector pass\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: 4.0.0 Alpha\n\nvector data is present for the shadow catcher objects. This needs to be omitted otherwise the vector blur node can't be used to add motion blur to the 3d elements, because unwanted motion blur will be added to the environment pass. If it a backplate was used then it wouldn't be a problem, transparent film could be set, and the blur would only affect the geometry. This also has an issue though, because the vector blur pass modifies the alpha too, so the shadow catcher vector could still affect the blur of the 3d geometry even if it's hidden by transparency.\n\n\n1. open attached file\n2. go to frame 10\n3. open the compositor\n4. render still frame\n5. check the compositor backdrop (shows vector data for the shadow catcher).\n\nSame result if film is set to transparent.\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.", "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", "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", "Compositor in start up file does not show specific passes\nBroken: version: 3.1.0 Alpha\nWorked: Prior to 7e712b2d6a\n\nWhen loading the startup file, some passes will be missing from the compositor. For example the denoiser.\n\nHere is a video showing off the issue: [F12781327](Missing_Passes_in_Compositor.mp4)\n\nWatch the video above or follow the steps below:\n\n1. Start up Blender and change the render engine to Cycles.\n2. Go to the `Viewlayer Properties` tab and enable Denoising Data.\n3. Change one of the areas to the `Compositor` and tick the `Use Nodes` box.\n4. Take note of the passes that are available on the `Render layer` node.\n5. Select from the top of Blender `File -> Defaults -> Save Startup File`\n6. Close Blender\n7. Open a new instance of Blender 3.1 and notice that the `Render Layer` node is missing some of the inputs that should be there.\n\nHow it looks before you re-open Blender:\n{[F13081662](image.png), size=full}\n\nHow it looks afterwards:\n{[F13081667](image.png), size=full}\n\n\nExample of startup.blend:\n[startup.blend](startup.blend)", "No preview icon in the material list\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 536.40\n\nBroken: version: 3.6.1\nWorked: (unknown)\n\nI noticed that for this material in the list it is not previewed, but in the \"Preview\" panel the preview is correct.\nThis is a simple setup of mixing 2 shaders using the \"Alpha\" attribute as a factor.\nThis situation makes it difficult to work when only using the drop-down list of materials in various situations..\n\nThx.\n\n", "4090 has problem with texture in render preview\nOperating system: Windows 11\nGraphics card: Nvidia Geforce 4090\n\nBroken: (3.4 and 3.5.1)\nWorked: none.\n\n**Short description of error** \nThis only started recently, has been fine up till today. My preferences are set to use both the CPU (AMD Threadripper 32) and the GPU (geforce 4090) in OptiX (or CUDA, doesnt seem to matter). Once the file opens, material preview works fine. (refer to \"materialpreview.png\") but when i click render preview (refer to renderprevier.png) all i see is my rig. Anything with a texture is a similar dark grey as the default blender background. I can move the camera around fine, but no textures are visible. If i click material preview again to switch back, blender freezes and must \"end task\" in task manager. If i turn off the GPU assistance and only have the CPU enabled, everything works as it should. \n\nYesterday i updated to latest windows 11 update. I also updated my gameready drivers for my 4090. When the issue started, i thought it might have something to do with gameready drivers so switched to Studio drivers. This did not fix it. \nAssuming that these updates may have broken my file, i rolled back windows 11 drivers to most recent previous version, and did the same with the nvidia studio drivers (uninstalled 5.35.... installed 5.31). This fixed nothing.\n\nI would love to know why my GPU can't be used with Blender suddenly. Games work fine. Furmark 3d app works fine, no issues. Heat is fine. Very frustrating to have such expensive gear suddenly stop working.\n\n", "VSE prefetch not showing clip's keyframe changes\nOperating system: Ubuntu Linux 18.04.5 amd64\nGraphics card: Nvidia GTX 1070\n\nBroken: blender-2.90.1, blender-2.92.0-9d6d5b9bebd1-linux64\nWorked: unknown\n\nWhen VSE \"Prefetch Frames\" is turned on and you edit a clip's keyframes, the prefetch will continue rendering frames into the cache without your changes.\n\n\n1. Launch Blender\n2. Choose \"Video Editing\" under New File\n3. Drag a still image (any PNG should do) into the timeline.\n4. Drag clip extents so that it starts from frame 0 and goes to frame 2000.\n5. In video preview, enable \"Prefetch Frames\"\n6. Go to frame 20 in the timeline and select the clip.\n7. Create an Opacity keyframe by clicking the dot next to Opacity.\n8. Go to frame 80 in the timeline.\n9. Change the clip Opacity to 0.4 and click the dot to create a new keyframe.\n10. Start playback and see that the clip shows 100% opacity, even though the timeline shows that it should be 40%. Changing the proxy render size will clear the cache and show correct results.\n\nIf you clear the cache and do steps 8-10 quickly enough (i.e. before the prefetch finishes), you will also see that even though you modify the clip while prefetch is not done, the prefetching will continue to render incorrect frames. E.g. if you create the opacity keyframe while the prefetching is at frame 500, prefetched frames after 500 will still show as 100% opaque.", "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)", "Transform Node Messes Up Alpha Channel Manipulation\nArch Linux\nNvidia 750ti\n\nBroken: 2.79 (Tried 2.8 as well and I have the same issue)\n\nAs referenced here:\n4\n\nWhen I take an image in the compositor and scale it up 2x or whatever and then separate the RGBA and dilate/erode the alpha and use that to set the alpha on the image, it only works within the size of the original image and not the scaled up image. Also even if I use the R, G, or B, it still only uses the size of the original image and not that of the scaled up one.\n\n\n\nCropped if I try to mess with the alpha after a transform.\n\n\nUncropped if I mute my changes to the alpha.\n\n\nAlso I believe that if you scale down\n\n[dilatecropissue.blend](dilatecropissue.blend)\n", "GPencil: Fill tool Ignore Transparent strokes setting broken\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 516.94\n\nBroken: version: 3.5.0 Beta\n\nFill tool not ignoring transparent strokes when the settings is enabled. When you enable Show boundary lines, it shows that transparent strokes are not a boundary but the fill still uses them as boundaries.\n\n- Open attached file and try the fill tool. Under the Advanced menu 'Ignore Transparent' and 'Show Lines' are enabled.\n\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?", "EEVEE: Mixing between a fully transparent and holdout shader yields a half transparent result\nOperating system: macOS-10.13.6-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 580 OpenGL Engine ATI Technologies Inc. 4.1 ATI-1.68.25\n\nBroken: version: 3.2.0 Release Candidate\nWorked: I thinck the issue is for \"all\" versions of blender\n\nHoldout shader having issue with alpha (semi transparency).\n\nPut a image plane with exr image that contain alpha. When using a holdout shader mixed with another shader (transparency shader for exemple) the alpha of the image sequence is used for the mix of the 2 shaders. It should have a complete transparent image with the holdout of other object in the scene. The issue is that there is a dark outline for the semi transparent. Holdout have issue dealing with semi tranparency ? or maybe something else.\nSee the attached image to understand the issue.\n\n\n", "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." ]

[ "RGBA movie rendering: WebM/VP9 codec missing alpha channel\nOperating system: Linux-5.8.6-1-MANJARO-x86_64-with-glibc2.32 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 5.8.6-1-MANJARO, LLVM 10.0.1) X.Org 4.5 (Core Profile) Mesa 20.1.7\n\nBroken: version: 2.91.0 Alpha, also broken in 2.82a\n\nRendering a movie with alpha channel works for\n- ffmpeg video codec #1\n- png codec\n- HuffYUV codec\nBut choosing WebM/VP9 does not include an alpha channel, so either the RGBA option should not be there or something is wrong in the encoding step.\n\n**Edit**\nExported movie looks like it has proper alpha, but Blender (next to other software cannot import that properly)\n\nIn the default scene:\nrender properties: Film transparent\noutput properties: File Format: FFmpeg video, Color RGBA, Video Codec: WebM/VP9\nRender Animation and open the file: black background is still there, no checkerboard like with the working codecs, also putting it over a solid color in the sequencer using Alpha Over clearly shows that there is no alpha channel." ]

[ "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 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", "Crash when renaming a world in a timer and dragging a world in the asset browser\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.4.0 Alpha\nWorked: Don't know, tested back to 3.1, and still got the crash\n\nWhen a python timer renames a world, and the user is dragging a world *from another file* in the asset browser, blender will crash. (doesn't happen if the world is from the current file)\n\nI also tested this on materials, and it didn't cause a crash, so I assume that it's limited to just worlds.\n\n[world renaming crash.blend](world_renaming_crash.blend)\n* Open the attached blend file, and run the script in the text editor.\n* That will start a timer that will run once a second for ten seconds, and will rename a world data-block each time.\n* During those ten seconds, in the asset browser window, start dragging a world asset that originates from another file.\n* Blender should crash.\n\n[2022-10-23 15-49-18.mp4](2022-10-23_15-49-18.mp4)\n\nThanks a lot!", "Blender (2.91) crashes on change frame with handler set to render scene\n\nOperating system: Catalina (10.15.7)\nGraphics card: \n\n\n2.91.0\n\nI want to have the scene rendered automatically every time the frame changes.. so I set a post frame change handler do just that (according to blender documentation: bpy.app.handlers.html#bpy.app.handlers.frame_change_post)\n\nPaste this in the Blender console to setup the handler: \n\n```\nimport bpy\n\ndef my_handler(scene):\n bpy.ops.render.render(use_viewport=True)\n \nbpy.app.handlers.frame_change_post.append(my_handler)\n```\n\nHowever, blender crashes as soon as I change the frame.\n\n- Open attached file\n- Run script\n- Change frame\n[handler_ops_render_crash.blend](handler_ops_render_crash.blend)\n\n\n", "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```", "Crash without warning when opening material properties panel.\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: AMD Radeon RX 540 Series, ATI Technologies Inc., OpenGL, 4.5.0 Core Profile Context 22.20.16.03.220829\n\nBroken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379f7\nBroken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3\nWorked: no newer version works.\n\nWe get a hard crash without warning when opening the material properties panel in the \"Layout\" workspace right after startup (i.e. with a clean \"General\" new file). Opening the material properties panel in other workspaces causes the same crash.\n\nI suspect that this is an EEVEE problem since opening other properties panels (which do not have the material preview) works fine and opening the material properties panel after having selected the Cycles engine in the \"Render properties\" panel also works fine. Somehow, it feels like being a hardware problem, but I cannot explain why. Interestingly, the device for rendering in the [Preferences][System] is set to \"\"None\" and no GPU's are available in the Cuda, OptiX, HIP, and oneAPI sections.\n\nWhen switching the viewport in the \"Layout\" workspace to \"Viewport Shading\" (i.e. rendered by EEVEE), Blender crashes. When Cycles is selected as rendering engine, then \"Viewport Shading\" works fine.\n\nThe crash happens on my colleague's computer in India to which I have no direct access. Updating graphics drivers is not easily possible due to company constraints. My colleague now uses the Cycles rendering engine by default. Some current file of her was saved with the default EEVEE setting, so she cannot load the file without crashing Blender; I have now modified the file on my computer by switching it to Cycles rendering which bypasses that problem for now.\n\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Open the \"Material properties\" panel in the \"Layout\" workspace.\n- Blender crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Select \"General\" new file\n- Select \"Viewport Shading\" in the \"Layout\" workspace.\n- Blender Crashes.\n\n[Based on the default startup]:\n- Open Blender.\n- Load a previously stored blend file with EEVEE set as the renderer (and I suspect showing the \"Materials properties panel\" or the viewport in \"Viewport Shading\" mode).\n- Blender Crashes.\n\n", "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 3.6.1 crashes when switching to Viewport Shading to Rendered on MacBook Pro M1\nOperating system: macOS-13.5-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 Max 1.2\n\nBroken: version: 3.6.1\n\nEnabling objects in the scene causes blender to no longer render. It just says: Sample 0/32 (Using optimized kernels) and if i try and change the Viewport Shading back to something else it crashes. This issue seems to only happen on a specific file.\n\nOpen file, switch Viewport Shading to Rendered, try and switch it back to anything else.\n\n", "Crash while switching to edit mode with EEVEE + Geometry Nodes\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.0.0\n\nWhen switching to edit mode in while the viewport's set to render it crashes (see attached video)\n[blender crash 2021-12-17 21-54-00.mp4](blender_crash_2021-12-17_21-54-00.mp4)\n\n1 load the attached file\n2 switch to rendered view in the viewport\n3 switch to edit vertex mode\n4 that's a crash!\n\n[transitions_001_blender3.blend](transitions_001_blender3.blend)", "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 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.", "Closing System Console can lead to loss of work\nOperating system: Windows\n\nAny\n\n* Start Blender\n* Toggle the System Console (2.83 and newer `Windows > Toggle System Console`\n* Press the - [x] button on the system console", "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)", "Blender crash on pose library N-panel\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 850M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.68\n\nBroken: version: 3.5.1\n\nEvery time I click on invert button (which invert filtering) inside pose library N-panel blender crashes under this condition that your active asset library set to all.\n\n1. First be sure animation pose library add-on is enable.\n2. Create new scene.\n3. Create an armature.\n4. Go to pose mode.\n5. Click on Animation tab on side bar(N-panel).\n6. Change active pose library from \"Current File\" to \"All\".\n7. Click on double arrow icon which indicate invert filtering one or two times.\n8. Blender will crash.\n\nI also tested on blender 3.6 Beta , It still exist but in v 3.6 beta you should click on view port shading options after step 6 to perform crash.\n\nAnyway I upload crash log.\nThanks a lot.", "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" ]

[ "Crash by switching between environment properties and material properties \nplatform: Windows\n\trenderer:\t'Intel(R) HD Graphics 620'\nvendor:\t\t'Intel'\nversion:\t'4.5.0 - Build 25.20.100.6446'\n\nversion: 2.90.0 Alpha, branch: master, commit date: 2020-06-23 21:54, hash: 49234c15e299, type: Release\n\n**Brief description of the error**\nExact steps for others to reproduce the error:\n\n1- Open Blender\n2- Leave it as the default in the video (in Eevee)\n3- Put the cursor and click on \"Environment properties\"\n4- Then click on \"Material Properties\"\n5- Re-enter \"Environment Properties\" and the program automatically closes completely.\n\n\nIMPORTANT NOTE: Before doing this, experience that if I leave it in \"CYCLES\" and do the same procedure it does not close and then I pass it to \"EEVEE\" it does not close either, the program closes when it is the first time if not I pass it to CYCLES, otherwise the program closes me.\n\n\nThank you very much for your help and great work, also a thousand apologies for English since it is very regular, I am from the country of Colombia. Blessings.[Blender 2020-06-24.mp4](Blender_2020-06-24.mp4)" ]

[ "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", "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)", "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.", "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)", "Cycles: GPU Optix kernel loading with Bevel/Ambient Node.\nXMGNEO17 Laptop AMD Ryzen9 5900HK Radion.\nOperating system: Windows 11 Home. 21H2\nGraphics card: Nvidia Geforce RTX 3080 Laptop GPU. 16 GB VRAM.\n\nBlender 3.2-3.4 show the error. Blender 3.1 and before not.\n\nThe error happens when ever an Ambient Occlusion or Bevel Node is used and connected in a shader and GPU option OPTIX is enabled for rendering in Cycles. It does not happen with CUDA or CPU.\nBlender will start render process and stops with the line: Preparing for rendering, this can take time.. etc. At that point the UI is still working, but will freeze after trying to cancel rendering. Blender can only be forced to shut down. Scene changes are lost. \n\nThe but is very simple to reproduce:\n1. Open Blender and apply a shader to the cube. \n2. Add a bevel/Ambient node to the shader and connect it to any input. Doesn't really matter which.\n3. Enable Optix in the preferences and set cycles as render. Make sure its set to use GPU.\n4. Switch viewport to preview render.\n5. Blende will stop preparing the scene and won't move further. Its UI is still reacting until trying to stop the process.", "Cycles crashes on viewport rendering in CUDA driver\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: 3.2\n\nThe crash happens while navigating the viewport in shading mode, using Cycles.\n\nThis crash reappeared in the latest 3.3 release. It happened in older releases, then it got stable, but now it's back again.\nApparently, it has to do with Cuda.\nIt's not happening in one particular scene only, but rather randomly regardless of the complexity of the scene.\n\n[Cave-CloseUp-v006.crash.txt](Cave-CloseUp-v006.crash.txt)\n\n[Cave-CloseUp-v005.crash.txt](Cave-CloseUp-v005.crash.txt)\n\n[blender.crash.txt](blender.crash.txt)", "Closing System Console can lead to loss of work\nOperating system: Windows\n\nAny\n\n* Start Blender\n* Toggle the System Console (2.83 and newer `Windows > Toggle System Console`\n* Press the - [x] button on the system console", "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", "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", "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", "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", "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", "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)", "Non animatable properties\nBroken: version: 3.3.0 Alpha\n\nWorking on refreshing the in-built AnimAll addon by adding the latest properties supported in Blender.\n@ideasman42 asked me to file a task\n\nCertain properties are missing animation capabilities:\n\n - Lattice Vertex Groups\n - Mesh Vertex Creases", "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" ]

[ "Blender crashes by toggling between object and environment properties rapidly\n**Operating system:** Windows 10\n**Graphics card:** Intel / Intel (R) HD Graphics 620 Core 5\n**Broken Blender Version:** blender-2.90.0-6899cb3c073e-windows64\n\n\n**Error** \nBlender crashes by switching between object and environment properties rapidly.\n\n**Steps**\n\n1-Open the program and leave it as default (Cube, Camera, Light Light)\n2-Create a circle curve (Although it is not necessary, it can be like this in the image)\n3-Select the cube\n4-Click on \"environment properties\" only and immediately go to \"object properties\" and without modifying anything, go back to environment properties and the program closes instantly (Even just by having the mere cube and switching several times in a row between those two options, the program closes), (Note: Repeat several times in a row to close the program)\n\nWith OFFICIAL version of Blender 2.83.0 It does not happen, it is only with Alpha version 2.90.0 (blender-2.90.0-6899cb3c073e-windows64)\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", "Extra face dots in UV Layout editor (GPU subdivision OFF, On Cage OFF in Subdivision modifier make a difference)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: Intel(R) HD Graphics 4600 Intel 4.3.0 - Build 20.19.15.4835\n\nBroken: version: 3.4.1\nBroken: version: 3.1\nWorked: not since GPU subdivision was introduced (so in a way, it was working in 3.0)\n\nExtra random faces appear in the UV Layout editor\n\n- I can mosty repro this if GPU Subdivision in Preferences > Viewport > Subdivision is OFF\n- It does not happen at all if I turn off `On Cage - Adjust edit cage to modifier result` on the SubSurf modifier.\n\nIn the attached file, toggle from face select mode to vertex select mode and back to face select mode. (Might have to repeat 5-6 times) Extra faces appear in the UV Layout editor. Also see here: [1457172]\n\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}", "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", "Surface Deform Modifier invokes \"Invalid surface UVs\" error when applied to Hair\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: Intel(R) UHD Graphics 770 Intel 4.5.0 - Build 31.0.101.3959\n\nBroken: version: 3.5.1\n\nWhen adding Fur to the mesh in the example file, the Surface Deform modifier produces the error message \"Invalid surface UVs on x curves\". This also appears related the rippling visibility of the hair an animation (see also [#109285](109285#issuecomment-965921))\n\n\n1. Load the attached file and press play\n2. Note the \"Invalid surface UVs on x curves\" error in the Surface Deform modifier\n3. Stop the playback, and note that the figure in the error corresponds with the appearance of hairs on the surface\n4. Select the Body object and Add > Curve > Fur\n5. Observe the same error in the newly added Surface Deform modifier\n\n", "Custom split normals & sharp edge edge behavior seems incorrect\nOperating system: Mac\nGraphics card:\n\nBroken: 3.6.1\nWorked: 3.2\n\nHi,\n\nI've noticed several changes to Blender custom (split) normal behavior between 3.2 and 3.6, using both the Python API and the user interface. I apologize if none of these are bugs, but some of this behavior seems possibly unintended to me.\n\nFirst, \n\nmesh.normals_split_custom_set(custom_normals)\n\nNow automatically marks edges as sharp when the normals differ (or differ past a certain threshold?). This behavior is not in 3.2 and I'm not sure if it is correct or desirable. Is it supposed to be impossible to have split normals without (marked) sharp edges?\n\nSecond,\n\nIf a mesh has split normals around a sharp edge, removing the sharpness attribute on the edge (in the user interface or the api) throws away the split normal data. I'm attaching a picture:\n\nThird,\n\nMerge by distance in 3.2 used to preserve split normals if it joined two faces with distinct corner normals (but vertices within threshold). It now appears to average them or something. \n\nI've attached a picture of issue #2 and a .blend file with before/afters of issue 2 and 3\n\n", "Cycles: improve subsurface scattering for some meshes shapes\nIn cycles-x, the Christensen-Burley dipole approximation was fully replaced by random walk.\n\nHowever for some mesh shapes results are not as good, or could be improved regardless.\n* Self-intersection meshes give dark borders. Counting back/front facing intersections could help determine inside/outside better to avoid such artifacts.\n* Sharp corners \"glow\", which may be physically correct but is not necessarily desired. It may be possible to add user control with an option somehow, using some minimum throughput\n\nIf these can't be solved, we may consider adding back the dipole approximation, but since path splitting and the memory usage is a difficult fit for the new kernels we'd really like to avoid it.", "Booleans are completely breaking on my object\nOperating system: macOS Monterey (ARM64)\nGraphics card: Apple Silicon `M1`\n\nBroken: 3.2.0 Alpha & others\nWorked: *2.83.X*? (reported in comment)\n\nBooleans can often be very touchy and may require positioning them just right for them to do operations properly. It seems that it really depends on where the vertices line up. I've been cutting window slots out of ridged galvanized steel plates using boolean cubes and it's worked for every other object. However, this one particular piece in my scene has been causing endless trouble for me despite being the exact same procedure. Seems as though I need to put my boolean objects in the EXACT RIGHT place for them to work right. I found that adding a ludicrous number of subdivisions w/ the subsurface modifier can somewhat help, but it greatly depends on whether or not I position my cubes in the right spot. It is preventing me from placing my windows where they need to go on my scale accurate historic building recreation. I don't know why this object is being so temperamental but it is blocking me from making any progress on this side of the building and I'm afraid I'll keep running into the problem later on.\n\nI may post additional demo files that showcase more boolean issues as I frequently run into problems of faces not being filled properly, crappy vertex extrusions, objects being weirdly combined instead of differenced, and many more annoyances. I hope booleans can get a lot more love from the developers so that they work as intended.\n\n\n\nI'm not entirely sure how to reproduce an issue like this. It mostly plagues more detailed models but can happen anywhere and depends on object positions, alignment, topology, and so on. Attached is a problematic file.\n\n**Attached file information**\n[F12870489](brokenBooleans.blend.zip) There are several issues present. For one thing, the boolean modifier is struggling to cut a simple rectangle out of a plane. It is adding geometry to certain parts, cutting out geometry that shouldn't be cut out, and is not accurate at all. I've noticed that using the \"fast\" option usually yields better results than using the \"exact\" option. However, in the case of this object, it actually breaks it EVEN MORE! Try selecting the \"cutoutGalvanizedSteel\" (planar object) and setting the booleans to \"fast\" to see a new problem emerge. Adding a solidify modifier to the very top of the stack will fix the issue. However, booleans should work on planes, too.\n\n[F12871474](BorkedBooleans.blend.zip) Many different problems. Boolean objects are displayed as wireframes. If you see a boolean as having geometry, it's because it is being added by the Boolean modifier. The boolean modifier likes to add the boolean's geometry to the source mesh sometimes, even when it is set to difference or intersection. In issue 2, there is a mesh problem in the boolean. If you enter edit mode, you can see that the problematic vertices are selected. They crash the boolean operation altogether. Merging these vertices will solve the issue, but for more complex boolean objects, this may not always be an option.\n\n[brokenBooleans.blend.zip](brokenBooleans.blend.zip)\n[BorkedBooleans.blend.zip](BorkedBooleans.blend.zip)", "Texture distortions near a seam WITH some Mean Bevel Weight applied\nOperating system: Windows 10 64-bit\nGraphics card: GTX 1080Ti\n\nBroken: 2.93.3\nWorked: \n\nOn a concave surface, texture distorts near a seam edge with a bit of Mean Bevel Weight applied.\n\n1) Create a curvy concave vessel/cup/pot with thickness. \n2) Add Bevel modifier 0.1m amount, segments 2, Weight method\n3) Make the mouth rim edges to be seams, and apply about 0.10 - 0.25 mean bevel weight\n4) you can do the same on the base outer edge \n5) UV unwrap, create image, better with 2048 and with UV Grid to see effect, apply to mesh\n\nNotice the texture distorts near the outer seam edge of the concave surface (the outer skin of the pot/cup)\nSetting the Mean Bevel Weight back to 0 removes this phenomenon but defeats the bevel purpose.\nI made 3 blender files and all exhibit same \"problem\".\n\n[bugreport2.blend](bugreport2.blend)\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)", "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)", "Bevel modifier creates zero area faces with unexpected normals when clamping to an unbeveled edge.\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79\n\nBroken: version: 2.92.0\nWorked: I cannot find a working version, I've checked 2.83 and 2.81. (I tried to use 2.79, but I've forgotten how to use it.)\n\n\n\n\nEdit (Baardaap): When the bevel modifier is clamped to an unbeveled edge, it creates a zero area face. This in itself it to be expected and not really a problem though it might be nice to prevent. When you bevel with the bevel operator the same happens. The problem is that the bevel modifier causes a recalculation of all normals, which generates random normals for the zero area faces. These random normals lead to strong shading artifacts when the shading is set to shade smooth.\n\noriginal report follows:\n----------------------------------------\n\n\n\n\n\n\nInconsistent normal behaviour when using a bevel modifier with\n(a) amount exactly matching the face dimension (or is clamped), and\n(b) auto smooth off\nWhen compared with auto smooth on, or just bevelling an edge directly.\n\nIn the sample file attached, I've created an L shape by creating a plane, then extruding 3 additional edges.\nI've added a reflective material to see how the normal affects the reflections.\nFor each L shape, I've then added a bevel modifier, only changing amount/segments. Or alternatively I've done bevel edge, and only set amount/segments.\nThen I've either set to smooth or flat shading, and/or turned-on auto-smooth.\n\nIn the attached file, I've prepared the different test scenarios.\nFrom bottom to top:\n - Modifier/Flat,\n - Modifier/Smooth, // This is the row where I see inconsistencies (highlighted in red)\n - Modifier/Smooth/AutoSmooth,\n - BevelEdge/Flat,\n - BevelEdge/Smooth,\n - BevelEdge/Smooth/AutoSmooth,\n\nFrom left to right:\n - Amount=2, Segments=10, // obvious difference for the flat plane above the bevel, plus weird anomaly for top segment of bevel\n - Amount=2, Segments=3, // obvious difference for the flat plane above the bevel\n # Amount=1, Segments=3, // this row has no apparent differences\n\n\n\nWhen viewing the file, I find it best to use material preview mode, then orbit up/down, and compare the reflections of the different rows.\n\n\nMy analysis.\nWhen performing a bevel, the faces being bevelled shrink to make space for the bevel, but retain their original normal.\n \n\nWhen the bevel amount matches the face size, then those faces still exist, however they have zero size - represented by the red lines.\n\n\nUsing the spreadsheet in 2.93, I can see inconsistencies with the normal vector for these faces.\n\nHere I've set the bevel modifier segments=1, and amount=2.\n\n\nAnd the corresponding spreadsheet (annotated).\n\n\nYou'll note that the two empty faces do have valid unit normals, though both a pointing at Z=1.\nYou would expect the vertical face - [x] to have a normal with X=1.\n\nHowever if you compare with the reference scenarios like having auto-smooth=on, or applying a bevel edge directly, this is what you see.\n\n\nIn this case, rows 0 and 4 actually have the normal vector set to 0, 0, 0. (I.e. technically an invalid unit vector.)\n\n\nSo, what I believe is happening is that when there is an invalid normal vector, then blender refuses to perform smoothing across from one face to another. The smoothing ends at the bevel edge and the adjacent face in this case is shaded flat.\n\nGetting back to the bevel modifier when auto-smooth is off, while this has valid unit vectors, one of those vectors has the wrong orientation.\nThis is why there is a reflection anomaly on the vertical face, but not on the horizontal face.\n", "Bevel/Crease lost after joining geometries in the Geo-Node\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.41\n\nBroken: version: 3.0.0 Alpha\n\nJoining the geometry in the node tree removes the bevel weight and crease data.\n\n\n\n\n\n[Geo-Node Bevel_Crease.blend](Geo-Node_Bevel_Crease.blend)\nOpen the given file and try toggling the modifiers.\n\n\n", "Inconsistency of some tools/operators (e.g. Subdivide) in regards to hidden geometry\nBroken: all or none\n\nI'm not really sure this is even an issue, though it feels like it. As far as I understand it, mesh editing tools are not supposed to affect hidden geometry. But the Subdivide tool does. Consider this mesh:\n\n\nIf you hide the middle face...\n\n\n...and then Subdivide the two remaining faces...\n\n\n...Subdivide will create new edges cutting through the hidden face, also creating inconsistent selection (i.e. selected edges in face select mode). Shouldn't the operator check that that face is hidden and not create edges through it?", "Freestyle - marked freestyle edges do not work on objects with the boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: Unknown\n\nEdges marked as freestyle do not work on objects with the boolean modifier\n\n\n1. Create cube object, add some edge loops and mark any edge as **\"Freestyle Edge\"**2. Create a second cube, and use it as a \"cutter\" using the**\"Boolean\"** modifier\n3. Activate **\"Freestyle\"**and check the**\"Edge Markt\"** in the \"Line Set\" area\n4. Make a render - the edge marked as **\"Freestyle Edge\"** will not be visible\n\n\nFile in attachment.\nThank you\n\n[Boolean Freestyle bug.blend](Boolean_Freestyle_bug.blend)\n\n" ]

[ "Bevel modifier disconnects vertices in the UV map\n{[F8713789](2KmuzHs.png)}Operating system: Windows 10 x64\nGraphics card: GTX 970\n\nBroken: 2.83.1, 47b6c332587ca45eddc98e75b3f563e2f17a0d47, probably all 2.8+ versions\n[SM_UVTest.blend](SM_UVTest.blend)\n\nWhen using an angle or weight limit on the Bevel modifier, vertices connecting beveled and unbeveled edges are split in the UV map, producing distorsions.\n\nAdded a blend file. To reproduce the issue, apply the Bevel modifier, and select all faces to see the problematic vertex in the UV editor. \n\nSome context is here : 1241831" ]

[ "OpenEXR can't be used to save results during the render process\nOperating system: XUbuntu 20.04\nGraphics card: Not applicable\n\nBroken: Blender 3.0.0, Commit date: 2021-12-02 18:35, Hash f1cca3055776\nWorked: Blender 2.93.7\n\nSeems OpenEXR now can't be used to save intermediate results during rendering using Cycles. The other formats (like PNG) seems works just fine. Blender starting v3 just crashing if you trying to save as single or multi-layer EXR. When the render is completed the `save_render` function is working correctly.\n\nThis bug doesn't allow to prepare the proper distributed preview for user outside of Blender UI (EXR needed to merge multiple preview samples from the remote workers).\n\nThe default cube blender scene is just enough to reproduce. Please switch to script console and paste the next code:\n```\nbpy.context.scene.render.engine = 'CYCLES'\nbpy.context.scene.render.image_settings.file_format = 'OPEN_EXR' # OPEN_EXR_MULTILAYER here will fail too, but PNG for example will work just fine.\nbpy.context.scene.cycles.use_adaptive_sampling = False\nbpy.context.scene.cycles.samples = 512\n\nbpy.ops.render.render('INVOKE_DEFAULT', use_viewport=True)\n\nimport time\ntime.sleep(2)\nbpy.data.images['Render Result'].save_render('_preview.exr')\n\n### Crash will be right here ###\n\nimport os\nprint(\"Preview file exists:\", os.path.exists('_preview.exr'))\n```\n\nCrash report: [blender.crash.txt](blender.crash.txt)\n", "Calling operator from handler that saves bmesh freezes blender forever\nBlender version: 3.5.1\n\nI setup some shader to run on top of blender viewport and connected it’s update to `SpaceView3D.draw_handler_add`. The idea was that shader will only work in EDIT mode and if user exists it then it will automatically trigger some operator.\nLine that freezes Blender is `bm.to_mesh(context.object.data)` although it doens’t freeze right away.\n\nWhat I’ve found that if I call operator that edits mesh from bmesh then it freezes Blender entirely.\nCurrently as a workaround I moved operator’s code to some function and call it instead of because `bm.to_mesh(context.object.data)` doesn’t seem to freeze Blender when it’s called from handler without operator.\n\n\nEasy way to reproduce (create default scene, make sure cube is selected, run the script):\n\n```python\nimport bpy\nfrom bpy.types import SpaceView3D\nimport bmesh\n\nclass TestHandler:\n installed = None\n\n @classmethod\n def install(cls, context):\n handler = cls()\n cls.installed = SpaceView3D.draw_handler_add(\n handler, (context, ), \"WINDOW\", \"POST_VIEW\"\n )\n\n @classmethod\n def uninstall(cls):\n try:\n SpaceView3D.draw_handler_remove(cls.installed, \"WINDOW\")\n except ValueError:\n pass\n cls.installed = None\n\n def __call__(self, context):\n obj = context.object\n if obj.mode != \"EDIT\":\n TestHandler.uninstall()\n bpy.ops.test.test()\n print('HANDLER CALL FINISHED') # never printed\n return\n \n print('HANDLER FINISHED')\n\nclass TestOperator(bpy.types.Operator):\n bl_idname = \"test.test\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST OPERATOR CALLED')\n bm = bmesh.new()\n\n # WITHOUT THIS LINE IT DOESN'T FREEZE\n bm.to_mesh(context.object.data)\n\n # still printed\n print('TEST OPERATOR FINISHED')\n return {\"FINISHED\"}\n \nclass TestSetupOperator(bpy.types.Operator):\n bl_idname = \"test.test_setup\"\n bl_label = \"test\"\n\n def execute(self, context):\n print('TEST SETUP OPERATOR CALLED')\n TestHandler.install(context)\n return {\"FINISHED\"}\n\n\nbpy.utils.register_class(TestOperator)\nbpy.utils.register_class(TestSetupOperator)\nbpy.ops.object.mode_set(mode=\"EDIT\")\nbpy.ops.test.test_setup()\n# freezes on the next step\nbpy.ops.object.mode_set(mode=\"OBJECT\")\n```\n\n", "\"Loop Cut and Slide\" requires to click anywhere first (different from loop cut)\nOperating system: Windows 10 64bits\nGraphics card: RTX 3070\n\nBroken: Blender 3.1\nWorked: Blender 2.93.6\n\nBehavior changed in f8b51f702c\n\n\nCalling for \"Loop Cut and Slide\" won't start previewing the possible cuts until a first left click is made anywhere on the viewport. This behavior is different from the \"Loop Cut\". It is a very small thing, but it is getting anoying.\n\n - Enter edit mode on the default cube.\n - Search and activate the operator \"Loop Cut\". It will show possible cuts immediately.\n - Search and activate the operator \"Loop Cut and Slide\". It won't show any possible cut until a left click.\n\n[2022-03-21 16-25-50.mkv](2022-03-21_16-25-50.mkv)", "Auto Render doesnt work with scene animations\n{[F8575831](autorender.gif)}Operating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\n\nBroken: version: 2.83.0 Beta\n\nIt should render when the scene animation updates. In general auto render also seems a bit unreliable. eg. Sometimes I turn it off and it keeps rendering, and it doesn't render even if some changes are made to the scene. Anyway in this case it doesn't update when there're scene animations.\n\nFrom startup:\n1. Set \"Use nodes\" in compositor\n2. Turn on \"Auto render\"\n3. Animate default cube (I used rotate here)\n4. Scrub timeline\nIt doesn't auto render with new changes.\n\nWith attached blend:\n- Scrub timeline\n\n[autorender_animation.blend](autorender_animation.blend)\n\n\n", "(Unneccessarily) restricted execution in scripted expression drivers (using e.g. \"self\", \"bpy.data\")\nOperating system: Linux-5.15.0-69-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Mesa Intel(R) HD Graphics 4600 (HSW GT2) Intel 4.6 (Core Profile) Mesa 22.2.5\n\nBroken: version: 3.5.0\n\nself causes error in scripted expression drivers\n\nIn scripted expression drivers using expression \"self.location.x\" from Blenders manual and \"self.location[0]\" from online examples both fail with \"ERROR: Invalid Pythpn expression\".\nI have enabled \"Use Self\" in driver and \"Auto Run Python Scripts\" in preferences\n\n", "popup window call operator will crash blender\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.96\n\nBroken: version: 3.2.0 Beta\n\nThis script is use to check the active material, it can be run correct in the main window, but not popup window(change the pref window to node editor)\n```\nimport bpy\n\nbpy.ops.screen.userpref_show(\"INVOKE_AREA\")\narea = bpy.context.window_manager.windows[-1].screen.areas[0]\n\n\narea.type = 'NODE_EDITOR'\nflip_header = True\narea.ui_type = 'ShaderNodeTree'\narea.spaces[0].node_tree = bpy.data.materials['Material'].node_tree\n\nfor region in area.regions:\n if region.type == 'HEADER':\n with bpy.context.temp_override(area=area, region=region):\n if flip_header: bpy.ops.screen.region_flip('INVOKE_DEFAULT') # this line will not\n\n if region.type == 'WINDOW':\n with bpy.context.temp_override(area=area, region=region):\n bpy.ops.node.view_all(\"INVOKE_AREA\") # this line will report context error\n```\n\n- Open .blend file\n- Execute script\n[#98491.blend](T98491.blend)\n\n\n\n", "Workbench render engine does not update the Material Slots panel preview\nOperating system: Linux Fedora 35\nGraphics card: Intel\n\nBroken: 3.2.0 Beta, branch: master, commit date: 2022-05-10 06:30, hash: 11aa237858d4, type: release\n\n\nThe aspect of the preview sphere in the Material Slots panel is not updated.\n\n\n1 - In a factory default startup file, select \"Workbench\" as render engine\n2 - Select the \"Cube\" Object\n3 - Open the Material Property Panel, in Viewport Display set a different color (diffuse_color)\n4 - The aspect of the preview sphere in the Material Slots panel is not updated.\n\nThe users of my BlenderFDS (www.blenderfds.org) addon keep asking me: why?\nA correct UI feedback is important especially for new users, and I presume this should be quite easy to fix. \n\nThank you very much, I am grateful for your work.\n\n[system-info.txt](system-info.txt)", "Image of the viewport can no longer be obtained via glReadPixels in Python. Gives strange results since 2.83\nOperating system: Arch Linux 5.8.5-arch1-1\nGraphics card: Intel i7-8665U\n\nBroken: since 2.83\nWorked: till 2.82\n\nIn Python, we get an image of the viewport from within an registered draw handler routine using:\n\nviewport = bgl.Buffer(bgl.GL_INT, 4)\nbgl.glGetIntegerv(bgl.GL_VIEWPORT, viewport)\nwidth = int(viewport[2])\nheight = int(viewport[3])\nimage = np.zeros([height, width, 4],dtype=np.uint8)\nbuffer = bgl.Buffer(bgl.GL_BYTE, image.shape, image)\nbgl.glReadPixels(0, 0, width, height, bgl.GL_RGBA, bgl.GL_UNSIGNED_BYTE, buffer)\n\nIt worked fine till 2.82, as shown here\n\n\nHowever, it gives blackish colors of the objects in the viewport since 2.83:\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", "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", "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", "AVI Raw index corrupted\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.90.0\nWorked: Never\n\nRendering AVI RAW file will create file with invalid or corrupted index. This seems to happen only with 3840x2160 resolution.\n\n\n[#80482.blend](T80482.blend)\n\n- Open file\n- Render animation\n- Open rendered file in VLC\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", "Current value 0 matches no enum in error with creating a new keymap from Industry Compatible or Blender 27x keymap\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.1.0 Alpha\n\nWhen you create a new keymap from the industry compatible keymap or the Blender 2.7x keymap, then you get errors in the console about this and that operator does not match current value 0 in enum ...\n\nRelated task: T92754\n\n\n\n- Open Blender\n- Open Preferences\n- Switch to Industry compatible Keymap\n- Create a new keymap\n- Watch the console\n- Repeat with the Blender 27x keymap as the base ...\n\n\n\n\n\n\n\nEDIT, the params.action_mouse parameter could be the cause.\n\n\n\n\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" ]

[ "Batch Generate-Previews doesn't work anymore\nOperating system: Windows 10\nGraphics card: MSI GTX 1080\n\nBroken: 2.83.2\nWorked: 2.80\n\nThe \"Batch Generate-Previews\" does not work anymore. The little processing black square just pop out and disappears after a second. I tried on an old version of Blender (2.80) and it works just fine. The processing square stays way longer on the old version. With the new one, it seems that the process doesn't succeed.\n\nSave a file with a basic cube.\nClick on the \"Batch Generate-Previews\" tool\nTry to append with another file -> no preview has been exported" ]

[ "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", "Python API for Tools\nGoals of this task:\n1. Create an API to create new tools.\n2. Create an API to register tools in the toolbar.\n\n## Create new Tool\n\nEvery tool is a `namedtuple` called `ToolDef` currently. That is a nice internal format but does not work well in an API due to the amount of attributes.\nThere is a wrapper called `ToolDef.from_fn` that makes it easier to create new tools. This function is used can be used as a decorator. Every decorated function then turns into a tool definition.\n\nThe advantage of that approach is that it makes tool definitions very compact. However, personally I think that this does not work well in an API because \"why should I define a function to create a tool\". \nA better approach could be to use concepts that are used in other parts of the API already: classes.\n\nUnfortunately the concept of a class does not fit exactly, because there aren't really instances of a tool. The tool would be the class itself.\nA combination of the current tool syntax and classes could fit best. Below is an example of how that API might look like.\n\n```\nlang=python\nfrom bpy. tools import ToolDefinition\n\n@ToolDefinition\nclass CursorTool:\n label = \"Cursor\"\n description = \"Set the cursor location\"\n icon = \"ops.generic.cursor\"\n keymap = ... # to be discussed\n\n def draw_settings(self, context, layout):\n props = self.operator_properties(\"view3d.cursor3d\") \n layout.prop(props, \"use_depth\")\n layout.prop(props, \"orientation\")\n```\nThis approach also allows individual attributes to be normal values or functions (e.g. there can be a function to generate the description dynamically).\nWe could also change it so that `CursorTool` has to inherit `ToolDefinition`. However I prefer to use a decorator here because of the following reasons.\n- It differentiates it from Panels, Menus, etc. which work quite differently.\n- Allows us to run code when the new tool is created. This code can check if everything is setup correctly and can add missing attributes. Although this can probably be done with `__init_subclass__` as well, haven't tried it yet. \n- A decorator can transform the class completely, potentially even convert it into a `namedtuple` if necessary.\n\nSince tools are (currently?) very lightweight, tools don't have to be registered. The \"registration\" happens when it is added to the toolbar.\n\n## Add Tool to Toolbar\n\nI use the following terminology, not sure if other terminology is established already.\n- **Toolbar**: The toolbar (I know, recursive definition) within one specific mode. E.g. the toolbar in curve edit and mesh edit mode are completely separate toolbars.\n- **Toolbar Entry**: A single icon in the toolbar. A toolbar entry can contain an arbitrary amound of tools. If it has 0, it will be hidden. If it has more than 1, a submenu will be displayed.\n- **Entry Block**: Can contain an arbitrary amount toolbar entries. A toolbar can have multiple entry blocks. Entry blocks are separated in the UI.\n\nFor users to be able to use a tool, it has to be in a toolbar. The goal is to allow addon developers to do the following.\n- Add a new entry block to a toolbar.\n- Add a toolbar entry to an existing or new entry block.\n- Add a tool to an existing or new toolbar entry.\nWe do not support creating a new toolbar. Only existing toolbars can be extended (for now).\n\nIn the current design it is difficult to allow all these operations because toolbars are mainly tuples, which means they are immutable. Changing this is not too difficult but then we face the bigger problem: How can we identify toolbars, entry blocks and entries? Also, should the identifier be just a string or some python object? I guess we will use strings, because they are used in many other areas in Blender already.\n- Toolbar: This is mostly a solved problem because there is already the tool mode. The main question is whether the space type should become part of the identifier. E.g. is the identifier just `EDIT_ARMATURE` or `VIEW3D.EDIT_ARMATURE`?\n- Entry Block: Currently there is no concept of an identifier for entry blocks. This would have to be added to support the second kind of operation. An example block identifier could be `EDIT_MESH.ADD_MESH` which contains the Add Cube and possibly other tools.\n- Entry: An entry also does not have an identifier currently. However these identifiers are easier to come up with because the scope is much smaller. In most cases the identifier could just be the name/label of the tool. A full entry identifier could look like `EDIT_MESH.MANIPULATE.SPIN`. We might also want to flatten the namespace out a little so that entry blocks and entries themselves are in the same namespace. Then `EDIT_MESH.SPIN` would be an entry while `EDIT_MESH.ADD_MESH` is a block. Don't know how likely name collisions are.\n\nOnce the identifier issue is solved, the API could look like so:\n```\nlang=python\nimport bpy\n\nbpy.tools.register(BLOCK_OR_ENTRY_IDENTIFIER, tool)\nbpy.tools.unregister(BLOCK_OR_ENTRY_IDENTIFIER, tool)\n```\nThe same API could be used by Blender itself to setup the default toolbars.\nThe order of tools within an entry and the order of entries within a block depends entirely on the registration order and cannot be changed using the API for now. This could be added later if it proofs to be useful, however it would be better to implement support for custom reordering. Panels are handled similarly; the order of panels can be changed by the user but not by an addon (afaik).", "Image Sequence data disappears after certain properties are set\nOperating system:\nGraphics card:\n\nBroken: 2.83.6 (and all previous 2.8x versions)\n\n\nCannot access image sequence pixel data from 'Image Sequence' editor after certain properties are set.\n\nBased on the following startup file and bundled image sequence:\n\n\n1. Open the 'image_sequence_issue.blend' file from the following zip folder:\n[image_sequence_issue.zip](image_sequence_issue.zip)\n2. Run the active script in the text editor area\n3. Notice that an error is thrown - the image sequence has no data.\n4. Now comment out lines 8 & 9 (or line 12), and re-run the script. Notice that no error is thrown and the image has data.\n\nFor reference; the script bundled in the above file is copied below:\n\n```\nimport bpy\n\n# get the image editor space in the current screen\nviewer_area = next(area for area in bpy.context.screen.areas if area.type == \"IMAGE_EDITOR\")\nviewer_space = next(space for space in viewer_area.spaces if space.type == \"IMAGE_EDITOR\")\n\n# set properties on the image user\nviewer_space.image_user.frame_offset = 1\nviewer_space.image_user.use_cyclic = True\n\n# set the display channels to 'color'\nviewer_space.display_channels = \"COLOR\"\n\n# viewer_space.image.reload() # this line does not fix the issue\nprint(\"Before update:\", viewer_space.image.has_data)\nviewer_space.image.update()\nprint(\"After update: \", viewer_space.image.has_data)\n```", "Show error messages in the info editor\nFollowup task to #83237", "Lots of animation-related operators do not check if the data is editable or not\nMany animation-related operators do not do any check whether the data-block they operate on is linked, liboverride or fully local data. This seems to affect in particular operations from the 3DView (like key insertions), and in the NLA (like adding new tracks, duplicating strips, etc.).\n\nE.g. one can insert keyframes on a linked object (ie create animdata for that linked object, a new local action, and assign that local action to the linked object!).\n\nRelated to issue reported in #98686 (Cant rename local NLA tracks within a local library override data-block.).", "Unable to add drivers to bone collections visibility\nOperating system: Windows 11\nGraphics card: RTX 4060ti\n\nBroken: 4.0.0 Alpha 2023-09-06\nWorked: Before bone collections were merged\n\nThis kinda leans into feature requests, but it is a regression nonetheless. Drivers also weren't acknowledged from what i could see.\nBefore bone collections were recently introduced, you could add a driver to each layer to influence it's visibility, and i know many people liked to use that in order to influence the visibility of a group of bones. Currently you cannot influence the visibility of a bone collection through drivers, the only option to do it now being controling the visibility of individual bones.\n\nN/A\n\n", "Keymap changes are not reflected for the local view setting\nOperating system: Linux-5.18.10-arch1-1-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.57\n\nBroken: version: 3.3.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown`\nWorked:\n\nWhen I turn off frame selected in keymap -> local view and restore it to its default it keeps the old behavior until blender is restarted.\n\nI tested changing delete in object mode (x) key to disable confirm and when I restored it it worked as expected so I think it is related to local view specifically.\n\n- Open default scene\n- In Preferences > Keymap: search for local view and uncheck `Frame selected` checkbox\n- use the shortcut in viewport. Notice frame select operation is not performed (which is expected)\n- In keymap, restore changes\n- Again use shortcut to switch to local view (frame selected operation is expected to execute but it doesn't)\n\n\n", "Python Operator.report does not show in status bar when overriding context\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.2.0 Alpha\nAlso broken all the way back to 2.79.\n\nAn operator's `report()` call does not show a message in the status bar or info editor when the operator is not invoked by the user. This is expected.\nHowever, overriding the execution context to `'INVOKE_DEFAULT'` or even a specific area does not make it work either. This part seems like a bug.\n\n**Simple reproduction file**\n[no_reports.blend](no_reports.blend)\n- Run the script and notice Warning reports in the stdout but not in the status bar\n- Same when saving the .blend file\n- As expected, running the operator manually (F3 search) works as intended\n - Alternatively, modify the `invoke` function to require user input (such as via `context.window_manager.invoke_confirm`), then the timer/save handler calls also work\n- The override_context makes no difference here\n\n**Reproducing from a blank startup file**\n- Create an operator that calls `self.report` on execute\n- Call the operator from e.g. a timer or application handler\n- Even when overriding the context, the report only shows in stdout, but not in the user interface\n\n", "Missing modal keymap settings for operators such as `Inset Faces`\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79\n\nBroken: version: 3.5.1\nWorked: unknown\n\nHi. Today I noticed that in the preferences there is no panel to customize hotkeys in modal mode for the \"Inset Faces\" operator.\n\n", "Clipped text labels intermittently missing ellipses by Float properties\nBroken: 3.4\nWorked: -\n\nThere are no ellipses by node group parameters in all editors by unhidden values \n\n[2022-09-02 16-57-07.mp4](2022-09-02_16-57-07.mp4) \n\n- Open attached file\n[missing_ellipsis_bug.blend](missing_ellipsis_bug.blend)", "Evaluate \"Add to Collection\" in Object > Collections panel\nIn the Properies {nav Object tab > Collections}, the '+' icon invokes the *Add to Collection* operator (the button next to it shows the same name, but actually invokes *Link to Collection* - this task is about the '+' button next to it!). \n\n\n\nWhen clicking it a new collection is created (which the name doesn't suggest) and the object moved to it. Problem is, the collection is not linked into the current scene. The user thinks nothing happened. You have to check the Data API or Blender File Outliner display mode to see that a collection was added. There actually is a way to link it to the scene, but it's pretty much hidden (can you find it? :) )\nA fake user is set, so this seems to be deliberate behavior. I assume it was more intended to be used for collection instances, where you might not want to link a collection, only an instance. And it's probably a left over from the old group system.\n\nCould we avoid this confusion?\nWe could just link the collection into the scene. Users can still unlink it. And the operator name could be *Add to New Collection*.", "Crash. Script changing values of a prop attached to object by an operator popup crashes the app\nOperating system: Windows 10 Pro\nGraphics card: NVidia GTX 1070 Ti\n\nBroken:\n(example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen used from a plugin, operator that uses wm.invoke_props_popup(self, event) to draw(and change) properties from a property group attached to an object (constantly) crashes the app.\nWhen same code is used from the blender scripting area, the app does not crash, but after initial change of the param, the property is grayed out(seems like a bug as well).\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF7DDBEA080\nModule : c:\\Blender28\\program\\blender.exe\nThe terminal process terminated with exit code: 11\n\n1) Create a testing_grounds.py file\n2) Fill it with code provided below\n3) Install as an addon\n4) Select an object\n5) Launch the operator(through space, typing \"TEZZT\")\n6) Change the value of the property by clicking and dragging the value;\n7) Repeat step (6) a few times if the app hasn't crashed yet\n\n```\nbl_info = {\n \"name\" : \"TestingGrounds\",\n \"author\" : \"ChieVFX\",\n \"description\" : \"\",\n \"blender\" : (2, 80, 0),\n \"location\" : \"\",\n \"warning\" : \"\",\n \"category\" : \"Generic\"\n}\n\nimport bpy\n\nclass SomeParams(bpy.types.PropertyGroup):\n float_value : bpy.props.FloatProperty()\n\nclass TestOp(bpy.types.Operator):\n bl_idname=\"testing_ground.tezzt\"\n bl_label=\"TEZZT\"\n bl_options={'REGISTER', 'UNDO'}\n\n def invoke(self, context, event):\n wm = context.window_manager\n return wm.invoke_props_popup(self, event)\n \n def execute(self, context):\n print(\"Im fine\")\n return {'FINISHED'}\n \n def draw(self, context):\n layout : bpy.types.UILayout = self.layout\n obj = context.object\n some_params = obj.some_params\n layout.prop(some_params, \"float_value\", text=\"Prop popup test\")\n \nclasses = [\n SomeParams,\n TestOp\n]\n\ndef register():\n for cls in classes:\n bpy.utils.register_class(cls)\n \n bpy.types.Object.some_params = bpy.props.PointerProperty(type=SomeParams)\n\n\ndef unregister():\n for cls in classes:\n bpy.utils.unregister_class(cls)\n \nif __name__ == \"__main__\":\n register()\n bpy.ops.testing_ground.tezzt('INVOKE_DEFAULT')\n```\n", "Running a script that registers an operator from the same operator crashes\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.5.1\n\nIf you execute an `bpy.ops.text.run_script()` through the operator through the panel in a Text editor, then blender crashes.\n\nP.s. maybe it's my fault and I did something wrong, but is blender supposed to crash?\n\nCopy the script or download the file:\n```Py\nimport bpy\n\nclass Op(bpy.types.Operator):\n bl_idname = 'op.op'\n bl_label = \"Op\"\n def modal(self, context, event):\n bpy.ops.text.run_script() # <------- here -------\n return {'FINISHED'}\n def invoke(self, context, event):\n context.window_manager.modal_handler_add(self)\n return {'RUNNING_MODAL'}\n\nclass Panel(bpy.types.Panel):\n bl_idname = 'Panel_PT_Panel'\n bl_label = \"Panel\"\n bl_space_type = 'TEXT_EDITOR'\n bl_region_type = 'UI'\n bl_category = 'Text'\n def draw(self, context):\n self.layout.operator(Op.bl_idname, text='Click me')\n\n\nclasses = (Op, Panel)\n\ndef register():\n for c in classes:\n bpy.utils.register_class(c)\ndef unregister():\n for c in reversed(classes):\n bpy.utils.unregister_class(c)\n\nif __name__==\"__main__\": register()\n```\n\n", "Batch Rename: Preset support\nThe batch rename operator supports chaining operations, allowing for setup actions which users may want to re-use.\n\nThis is a convenience feature.\n\nExample use cases (which may be possible in the future):\n\n- *Bones*\n - Add a prefix.\n - Number the object/bone based on it's level in the hierarchy.\n - Add a L/R suffix based on it's side.\n- *Objects*\n - Rename them to match their object data.\n - Number them, ordering based on their Z locaiton.\n", "Select Interior Faces is not working\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.24\n\nBroken: version: 4.0.0 Alpha\nWorked: \n\nthe operator \"select > select all by trait > interior faces\" is not working at all. Honestly I've never used this operator, so I'm not sure of how it should behave, but it doesn't do anything even with the simplest geometry. I tested it in 3.5 and 4.0 Alpha; I can't test it on other releases at the moment because of company installation restriction\n\nthe file attached is just a cube inside another cube in the same object\n\n" ]

[ "Operator Presets doesn't display name correctly\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.83.0\n\nOperator Presets name doesn't update when you choose a custom preset\n\n- Use default .blend file, Select the default cube, choose to Export fbx.\n- On the Export options, create a custom Operator Preset and name it whatever you like\n- Note that the settings are remembered, however the Operator Preset name doesn't update when you select you're custom preset.\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.", "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)", "\"Paste Objects\" doesn't copy source objects' collection heirarchy\nStarting to switch over to Blender 2.8 / 2.9, copy pasting still isnt working as intended. Please see #58190 as a reference of the previous bug.\n\nSystem Information\nOperating system: Ubuntu 17.10\nGraphics card: GTX 1080\n\nBlender Version\nBroken: blender2.9 55a2682348\nWorked: master Oct 2018 786870e26f\n\nShort description of error\nCopy pasting between blend files, it does not honor the collection hierarchy, Previously with blender 2.7 we could disable 'Active Layer' and the objects would go to their correct respective layers from the original blend file. Now with Blender 2.8 the only option is to have the copy paste on to the active collection, ruining any sort of collection hierarchy that was previously setup.\n\nExact steps for others to reproduce the error\n\n - Open Blender 2.8\n - create a new collection called 'test'\n - move the cube into this the collection 'test'\n - copy collection 'test'\n - create new blend file\n - delete everything apart from the default collection 'Collection'\n - create new collection 'test'\n - make the active collection the default collection 'Collection'\n - Paste\n - in the 'Paste Selection from Buffer' dialogue box, disable active collection\n - notice how the cube just created a new collection altogether, rather than creating the correct collection name / merging into it.", "[Python API] PointerProperty to type Collection slows down animation after open Preferences with excluded collections\nOperating system: macOS-12.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M1 1.2\n\nBroken: version: 2.93, 3.6.1, 4.0.1\nWorked: seems to be never working properly\n\nPointerProperty to type Collection slows down animation after open Preferences with excluded collections\n\nPossible [related to this](87468)\n\n1. Download [Zen2.blend](view?usp=sharing)\n2. Press play to convince that FPS is high\n\n3. Open Preferences window and also convince that FPS is still the same\n\n4. Run script that will create property group with PointerProperty to collections\n5. Press play\n6. While running, open and close preferences\n\n**Result:**\n\nFPS is dropped down and 'using fallback' message is written in console\n\n\n\nP.S. It seems like after opening Preferences window excluded collection is starting to take part during animation as if they are not excluded\n\n\n\n", "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", "Outliner Sorting and Dragdrop\nCurrently, the way you sort items in the Outliner is rather unclear.\n\nWe include this option in the Filter popover:\n\n\nBut when you disable this, you cannot re-order objects manually - instead they are displayed in the order of creation. \n\nAdditionally, this toggle only affects objects, not Collections, which are always manually sorted.\n\nWe can make this a lot clearer and more consistent, like so.\n\n - Replace the Sort Alphabetically toggle with an enum for with different sorting methods:\n\n - Make it apply to everything: Objects, Bones & Collections.\n - When set to Free, you can then freely re-organize both Collections and objects manually. \n\n---\n\nDragdrop is also closely related to sorting once we add custom sorting. We draw small black bars between items to indicate a sort dragdrop, and we shade the line dark when dropping into an item. We could improve on this.\n\nAlso, it would be good to allow object parenting without the shift modifier key.", "Different results for select_all option in local view\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 465.89\n\nBroken: version: 2.93.0\n\nWhen having one of two object in local view the {key A} works different than the command\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\neven though the output in the bottom left window in the scripting tab is the same.\n\n[Based on the attached .blend file]\n1. Select *Cube*\n2. Go in local view\n3. Press {key A} to select **only**the *Cube* because of the local view\n4. Deselect everything\n5. Run the command:\n\n```\nimport bpy\nbpy.ops.object.select_all(action='SELECT')\n```\nBut now you have the *Cube***and** *Cube.001* selected even though you used the same command. The output in the bottom left window in the scripting tab is the same. Shouldn't you select in both times the exact same objects?\n\n[selectAll.blend](selectAll.blend)\n\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 :)", "Pick Shortest path interferes with Ring select - Regression\nWindows 10\nNvidia GTX 1070\n\nBroken: Blender 3.0, 2.93LTS\nWorked: Blender 2.92.0\n\n In Blender 3.0 shortest path selection interferes with ring selection on my custom keymap where both operators share the same button layout, the difference being a single and double mouse click respectively. When selecting two edge rings, shortest path interferes and adds additional edges to connect the two edges from which a ring selection is produced. Instead, I expect it to only perform two ring selections.\n\n1. Map \"mesh.shortest_path_pick\" to Shift + LMB click\n2. Map \"mesh.edgering_select\" to Shift + LMB double click\n3. Create a cube or monkey\n4. Perform two edge ring selections that do not touch each other, preferably one or two edges apart from each other.\n5. Notice the additional edges selected in between the edges used to pick the ring selection with. \n\n[Bugreport - Shortest path & edgering selection.mp4](Bugreport_-_Shortest_path___edgering_selection.mp4)\nI also confirmed this on a factory reset 3.0.", "Object Action Workflow Polishing\n", "Delayed update of outliner ui on change of active collection\nBlender 3.6\n\nWhen you change active collection outliner UI updates only after you leave the outliner.\nAttached short demo gif.\n\nWay to reproduce the issue:\n1) Start default blender scene.\n2) Add new collection \"Example\"\n3) Run the script below in the text editor.\n4) Note that above the outliner you can see currently active collection, by default it's \"Collection\"\n5) Try to select \"Example\" instead of \"Collection\" - it won't update in the ui above.\n6) If you leave the outliner it will update the active collection.\n7) You can also try to choose some other collection and run operator to `.tag_redraw()` - F3 - Update Outliner. Note that info message that says that active collection didn't changed, it's just that outliner area wasn't updated.\n\nWhat expected - outliner ui to update as you change active collection.\n\n```python\nimport bpy\n\ndef get_outliner_area(context):\n screen = context.screen\n for area in screen.areas:\n if area.type == \"OUTLINER\":\n return area\n\nclass EXAMPLE_OT_custom_collection_new(bpy.types.Operator):\n bl_idname = \"example.redraw_outliner\"\n bl_label = \"Update outliner\"\n def execute(self, context):\n before = context.collection.name\n area = get_outliner_area(context)\n area.tag_redraw()\n self.report({\"INFO\"}, f\"{before} -> {context.collection.name}\")\n\n return {'FINISHED'}\n\ndef context_draw_outliner_foobar_buttons(self, context):\n layout = self.layout\n layout.label(text=context.collection.name)\n layout.label(text=context.view_layer.active_layer_collection.name)\n layout.operator(\"example.redraw_outliner\")\n\ndef register():\n bpy.utils.register_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.append(context_draw_outliner_foobar_buttons)\n\ndef unregister():\n bpy.utils.unregister_class(EXAMPLE_OT_custom_collection_new)\n bpy.types.OUTLINER_HT_header.remove(context_draw_outliner_foobar_buttons)\n\nif __name__ == \"__main__\":\n register()\n```\n\n", "Outliner Sync Selection: Use general update method\nCurrently there is a callback to flag the `wmWindowManager` as needing selection to sync to the outliner `ED_outliner_select_sync_from_object_tag`.\n\nUsing this requires us to explicitly tag on any selection change. See: [D5572: Outliner synced selection refinements](D5572).\n\nWe currently have 2x function calls used when objects have been selected.\n\n```\nDEG_id_tag_update(&scene->id, ID_RECALC_SELECT);\nWM_event_add_notifier(C, NC_SCENE | ND_OB_SELECT, scene);\n```\n\nThis task is to solve selection tagging in a more general way. \n\nPossible solutions could be:\n\n- Use the depsgraph tag or notifier to tag the outliner for selection syncing.\n- Add a function that calls `DEG_id_tag_update`, `WM_event_add_notifier` & `ED_outliner_select_sync_from_object_tag` so we don't need to duplicate the same lines of code in many places.\n\n\n----\n\n*Note, object selection is used for the purpose of discussion. Selection of other types may use a similar method.*\n\n", "Boolean modifier: Self Intersection fails when mesh object is same for both operand types\nOperating system: Win10 (21H1 19043.1348)\nGraphics card: GeForce 1080Ti (496.76)\n\nLatest 3.0 (December 02, 02:20:21 - 9cec9b4d6e33)\n\nOperand type `collection` did not consider `self intersection` with certain condition.\nIt fails when mesh object is same for both operand types\n\n- Open .blend file\n- Change operand type to `Object`\n- Uncheck `Self Intersection`\n- Switch back to `Collection\n\nTest File:\n[boolean.blend](boolean.blend)\n[2021-12-03 13-50-41.mp4](2021-12-03_13-50-41.mp4)", "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", "Edit-Mesh \"Select Next Active\" doesn't handle a wire edge loop (vertex mode)\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 works with loop ,that surrounden by others, but can`t deal with single circle, when I am trying to select one per one.\nPlease watch video:\n[2020-01-17_19-06-34.mp4](2020-01-17_19-06-34.mp4)\n\n[untitled.blend](untitled.blend)" ]

[ "Layer Switching Shortcut Inconsistency\nThere is some improvement concept for collections shortcuts.\nCurrently, 1234 buttons shows a collection, but sending objects requires name in menu (M - \"Collection 1\" - \"Collection 3\" for example)\nThat would be nice if moving to collection will also support their number.\n\nFor example, \"5\" button shows collection called \"Lighting Collection\", so pressing \"M5\" will send selected objects to it.\n\n----\n\n*See: #55162#619317 - originally from @1D_Inc*" ]

[ "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", "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", "Linked collection with smoke simulation cached doesn't work\nOperating system: Windows 10\nGraphics card: RTX 2070 laptop\n\nBroken: 2.82\nWorked: IDK\n\n Linked collection with smoke doesn't seems to load the cache properly or something.\n\n- Create a scene with a quick effect smoke,\n- Save the file,\n- Bake the simulation.\n- Save the file again,\n- File -> New -> General\n- File -> Link the collection of the another file\nThe domain doesn't load the cache", "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)", "Animation: Replacing bone layers + groups with bone collections\nThis design describes the replacement of armature _bone layers_ & _bone groups_ with a new _bone collections_ system.\n\nImplementation is in #109976 and #112271.\n\n## Goals\n\n- Named collections, instead of numbered layers, should give a better indication as to what the collection contains / is for.\n- Increased flexibility in number of collections.\n- More similarity to the scene object collections, including features like 'not selectable' which can increase clarity of how to use a rig by animators.\n- Compatibility with library overrides, so that new shot-specific bone collections can be added.\n- Unification of numbered bone layers (for organisation) and named bone groups (for coloring).\n\n## Properties of the System\n\n- Armatures have one or more bone collections.\n - If there is only one collection it cannot be removed.\n- Every bone is in zero or more bone collections.\n- Bone collections **cannot be nested**. At least not for 4.0, can be added later.\n- Bone collections must have a **unique name** within the armature.\n- Library Overrides:\n - New bone collections can be added.\n - Existing ones cannot be reordered / removed.\n- Bone collections have the following properties:\n - Name\n - Selectable: 'set' wins over 'cleared'\n - Visible: 'set' wins over 'cleared'\n - `IDProperties` (aka Custom Properties) for use by add-ons.\n- Bones will get individual color properties.\n - The color system of bone groups will be used, which allows selection of 'default', 20 theme-defined colors, and a custom RGB value.\n - Bones have a color defined as part of the armature data. Here 'default' is the default grey color.\n - Pose Bones have a color defined as part of the object/pose data. Here 'default' means 'uncolored', and will thus show the edit bone color.\n\n## Operations\n\nThese operations can be performed on/with bone collections:\n\n- (De)select one or more collections themselves\n- (De)select all bones in active collection\n- (De)select all bones in collections containing the currently selected bones\n- Create a new collection\n- Delete a collection. Bones in the collection that are now 'orphaned' are assigned to the 'default' collection.\n- Move collection up/down in the list.\n- Move selected bone(s) to a collection.\n- Select Bones of Same Color.\n\n## User Interface\n\nFor Blender 4.0 the UI is kept intentionally simple. I'm thinking of reusing the Bone Groups interface, with the addition of a few per-collection icons (visible, selectable, color palette) as well as an indicator of which collection(s) contain the selected bone(s).\n\n## Conversion from Old to New\n\n- Layers converted to `Layer {NUM}` collections.\n- Bone groups converted to `{name}` collections.\n- Selection Sets converted to `SelSet {name}` collections.\n- Maybe even automatically merge these when they contain the same bones?\n\n## Uses of the Current System\n\n### Bone Layers\n\n- Visibility\n- Logical grouping\n\n### Bone Groups\n\n- Coloring of logical groups\n- Set by rigger\n\n### Edit Mode vs. Pose Mode\n\nThis describes Blender's **current** behavior:\n\n| Property / Action | Edit | Pose |\n|---------------------------------------|------|------|\n| Name Bone | ✅ | ✅ |\n| Set Bone Layers | ✅ | ✅ |\n| See Bone in Group Color | ❌ ¹⁾ | ✅ |\n| Create / Assign Bone Group | ❌ ¹⁾ | ✅ |\n| Select Bones in Group | ❌ ¹⁾ | ✅ |\n| Set Bone Group Color | ✅ | ✅ |\n| Set Armature Viewport Display options | ✅ | ✅ |\n| Set Bone Viewport Display options | ❌ ²⁾ | ✅ |\n\n¹⁾ The new system should allow these in Edit mode too.\n²⁾ Bones can only be hidden, which is separated between edit mode & pose mode.\n\n## Future Work\n\nThese are ideas for future improvements / extensions:\n\n- Nestable bone collections.\n- Integration with the Outliner.\n- Per-collection option whether bones are deforming or not (rather than setting that per bone)\n- Per-collection viewport display mode (octo, line, bbone, etc)\n- Possibly unification of Selection Sets as well.\n\n## Code Location\n\nThis work will kickstart a new module in `source/blender/animrig`. This will become the place for new animation/rigging related code. The intention is that also a subset of the already-existing animation-related code from both `blenkernel` and `editors` is going to move there, to help clean up the API and make it more consistent.\n\n-------------------------\n\n## Ongoing Work\n\n**Targets for 4.0-bcon1: tracked in #109976**\n\n**Targets that could be pushed back to 4.0-bcon2:**\n\n- [x] Add ID Properties support to bone collections, including a UI.\n- [x] Removal of bone group RNA access & UI\n- [x] Ensure that library overrides can add new bone collections & assign bones to them (#112271)\n- [x] Removal of bone groups from the UI, including the Ctrl+G menu\n- [x] Add bone collections to the outliner (replacing the current list of bone groups)\n- [x] Operators to move/add selected bones to a collection:\n - [x] move to collection (similar to 'm' for objects & collections, from viewport)\n - [x] add to collection (similar to 'shift+m' for objects & collections, from viewport)\n- [x] Select Similar operator (by collection, by color) / Shift+G menu\n- [ ] Fixing the Collada I/O, as that also handles bone layers.\n- [x] Make bone collections on linked-but-not-overridden armatures usable. The object itself may be overridden, so changing the active bone collection should work (even when it cannot be saved), and then 'Select Bones' and 'Deselect Bones' operators should work.\n\n**Potential push back to later:**\n\n- [ ] Add selectability toggles to bone collections (only for pose mode)\n- [ ] Add armature-global override to selectability, so that a rigger can still opt to select all the bones, then lock them down for animators.\n- [ ] Managing bone assignments to collections from the outliner.\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", "Don't show catalog path when dragging assets over root level catalogs\nWe show the name, and the full path of a catalog in parentheses, when dragging assets over it. For root level items this will just result in showing the catalog name twice. This is confusing and should be avoided.\n\n", "\"Make Single User\" does not unlink object from other scenes when creating Scene using \"Linked Copy\"\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12\n\nBroken: version: 2.93.6 Release Candidate\nWorked: 2.90.1 (according to [description by user DAG here ]], who lists his software version in a [[ https:*blender.stackexchange.com/questions/74460/how-to-unlink-remove-an-object-from-a-scene/227238#comment383264_74486 | comment higher in the same question, here ](https:*blender.stackexchange.com/questions/74460/how-to-unlink-remove-an-object-from-a-scene/227238#227238).\n\nScenes created using the \"Linked Copy\" option do not allow objects to be unlinked via \"Make Single User\".\nAdditionally, in my testing, I have not found any way to make single user objects in a scene created using the \"Linked Copy\" option or in the original scene (i.e. creating a new object in either scene always creates a **linked** object). Objects deleted from one scene are also deleted in the other. Because of this, I have not been able to find a way to change a Scene created via \"Linked Copy\" independently of the original scene, making the \"Linked Copy\" option functionally useless.\n\n\n - Open a new default file\n - Create a new scene using the \"Linked Copy\" option\n - Select the default cube in the new scene (will likely be already selected)\n - \"Option\" menu -> \"Relations\" -> \"Make Single User\"\n - Delete the cube in this Scene\n - Switch to the first Scene\n\nExpected Result: The default cube is still in the first Scene\nObserved Result: The default cube has been deleted from the first Scene\n\n\n\n", "Source Collection visbility will affect the final render of the links object(geo nodes) in eevee/cycles\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15\n\nBroken: version: 3.2.0 Alpha\n\nWhen collection is used in GN tree and it is disabled for final render (camera icon in outliner). Then the new object is not visible in final render\nWhich is not the case when object is used instead of collection in GN tree\n\n1. create a simple object\n2. move it to a new collection\n3. turn off the collection's visibility\n4. new object with geo mod, use the collection as output\n5. render, the new object didn't show in the final render(but viewport)\n\nor \n- Open test file\n- Do final render i.e. F12 (object is not visible in final render)\n- Now connect `object info` node to group output and render (object is visible)\nTest File\n[#97535.blend](T97535.blend)\n[2022-04-22 12-55-10.mp4](2022-04-22_12-55-10.mp4)", "Add Asset Browser to Animation Workspace?\nShould the Asset Browser, or at least the 3D View Sidebar with the pose library asset view be added to the default *Animation* workspace?", "Outliner: Unexpected behavior when duplicating object hierarchies\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.4.1\n\n**may not be a bug** - duplicate a parent object (i.e. an object that has child objects). The duplication automatically selects the new object in the 3D viewport but this selection differs from that shown in the outliner. This means dragging to, say, a new collection does not work as expected (only the parent object is moved leaving the child behind).\n\nThe set up (this is the attached blend file):-\n1. Create two cubes (or any meshes) and parent one to the other to form a hierarchy.\n2. Add the object(s) to a collection.\n3. Create another top level collection which is empty.\n\nThe aim:-\nTo duplicate the object(s) (not the collection) and copy the duplicate to the second (currently empty) collection.\n\nThe steps:-\n1. Right click the parent object in the outliner and choose \"Select Hierarchy\". Note that the outliner shows the selected objects with a blue background bar (as expected).\n\n2. In the 3D viewport, use Shift or Alt D (doesn't matter which) to create new duplicate objects. Note that the 3D viewport shows the duplicate parent and child selected. The outliner shows a new object selected (with blue bar) but the tree is collapsed so we can't see the child.\n\n3. In the outliner, click and drag the selected parent object to the empty collection. Note that only the parent moves, the child is left behind. This child has then to be dragged separately.\n\nAfter step 2, every visual cue leads the user to believe that the duplicate hierarchy is selected. And this is the intuitive behaviour expected. But expanding the outliner tree shows the child object is not, in fact, selected (no blue bar). So an additional step of having to reselect the hierarchy is required before step 3.\n\nThe main issue is that with lots of objects and detailed hierarchies, just forgetting that additional \"select hierarchy\" step before dragging means that child objects can be scattered all over the place away from their parent and the user is left picking through the large list trying to sort it out.\n\nThis may not be a bug, it may be working as designed. But I cannot think of a use case where the current functionality would be useful so I'm assuming it's a small selection bug.\n\n", "Objects with volume material is included in render even when it's inside HOLDOUT collection\nOperating system: Windows 10\nGraphics card: NVIDIA RTX 2070 Super\n\nBroken: 2.91\nWorked: (Nothing since collection system was presented)\n\nObjects with volume material is included in render even when it's inside HOLDOUT collection.\n\nApart from the question whether volume material should mask the other collections, it should not be rendered like it normally would. It should at least be excluded from the render.\n(Volume material object inside INDIRECT ONLY collection works fine)\n\nIt's very simple. Based on the default new file...\n\n1. Make a new collection and enable holdout.\n2. Make a new icosphere object inside the new collection.\n3. Give the icoshpere a volume material(Simple principled volume is fine).\n4. Move the icosphere in front of the camera, making the default cube go behind the icosphere inside the camera view.\n5. Render the image. You'll see that the holdout is not working properly for volume material objects.\n\n[volume_holdout.blend](volume_holdout.blend)", "Add object redo: exits local view if there are no other objects in local view\nBroken: 2.80 to 2.92 master\nWorked: 2.79b\n\n\nIf you're in local view and there are no objects, add an object and attempt to adjust any property in the redo panel, Blender drops out of local view. However, if you don't touch the redo panel and instead e.g. transform the object, local view is retained.\n\n\nIn the default scene with cube selected:\n\n- enter local view\n- delete the cube\n- add a new object\n- attempt to adjust any property in the redo panel", "Changes to the asset catalog UI\n- - [x] Nest real catalogs under \"All\" item. (e38532773b)\n- - [x] Remove `'HOME'` icon. (fca6a9fe3f)\n- - [ ] Improve layout to make relationships more clear.\n- - [x] Expand the selected item on click. (56ff954030)\n- - [x] Don't expand all top-level catalogs. (c0122cc888)\n- - [ ] Add hierarchy lines.\n- - [ ] Asset catalog icon for each row?", "Wrong add selection to active collection operator description\nOperating system: Arch Linux\nGraphics card: GTX 970\n\nBroken: 036e95bb21fa\n\n\nWhen left-clicking on a collection in the outliner it is highlighted in white and its name is also shown in the 3D viewport and status bar. This to me indicates it is the \"active collection\", analogous to the active object. \n\nHowever, the tooltip (and collections in the list) for Add selection to active collection (Ctrl-Shift-G) says \"Add the object to the collection **that contains the active object**\". This indicates a different meaning of \"active collection\". \n\nSo two questions:\n- Which is the correct definition of active collection?\n- What is the use of the highlighted collection in the outliner?\n\n\n" ]

[ "Asset Browser - Current File doesn't place objects in active collection\nOperating system: Windows 11\nGraphics card: RTX 4070ti\n\nBroken: 3.5.0\nWorked: Supposedly never (tested 3.0-3.6)\n\nWhen adding an object into the scene from the Current File category in the Asset Browser, objects are placed into the same collection as the assets they originate from instead of the collection you are currently working in.\n\n- Move default cube into a new collection\n- Mark as asset\n- Ensure the scene collection is active, not the cube collection\n- Drag cube asset from Asset Browser Current File category into the scene\n- It will appear in the same collection as the asset reference object\n" ]

[ "Geo Nodes lose instances during a Cycles animation render\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 472.84\n\nBroken: version: 3.0.1\nWorked: 3.0.1 is the oldest version of Blender that can use the nodes needed for the project to take place.\n\nGeo Nodes lose instances during a Cycles animation render\n\nFollow the tutorial detailed in this video: watch?v=rRGq4C1KPOE \n\nThe following are a screenshot of my Geo Nodes group and blend file of the offending Geo Node group.\n\n\n\n[Bridge run.blend](Bridge_run.blend)\n\n", "Breaking shader node changes for 4.0\nThere are a number of proposed changes to shader nodes that break the Python API, mainly for add-ons that import and export shaders.\n\nWe need to make a decision to either:\n* Make these breaking changes in 3.2 or 3.3, and then do them all together with good communication so scripts only need to be updated once.\n* Postpone all breaking changes to 4.0, and see which parts of these patches can be non-breaking. For example we could have new general Mix/Combine/Separate nodes in addition to the existing ones.\n\nPatches:\n* [x] [D14034: Geometry/Compositor/Shader/Texture Nodes: Add general Combine/Separate Color nodes](D14034)\n* [ ] [D14257: Shader Nodes: Changes to node UI and default values to improve consistency](D14257)\n* [ ] [D14202: UI (Shader/Compositor): Rename \"RGB\" input to \"Color\" input](D14202)\n* [ ] [D13749: Node: Mix node](D13749)\n* [ ] [D13359: Rename \"fac\" to \"factor\" across all nodes](D13359)\n* [ ] Use proper \"Brightness\" word in names", "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", "GPU Subdivision: Crash on applying Subdivision Surface Modifier\nOperating system: Win 10 22H2 10.0.19041\nGraphics card: Intel® HD Graphics 5500 Driver version: 20.19.15.5171\n\nBroken: All versions after 2.93.11\nWorked: 2.93.11\n\nBlender crashes when applying the Subdivision Surfaces modifier. Tested with various different geometries (meshes, NURBS)\nCrash probably occurs with old intel GPUs\n\n- Start Blender\n- Apply SS modifier to cube OR delete cube, add another object (cube? lol), add modifier to that", "Point Instance node doesn't instance meta objects.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GT 710/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.65\n\nBroken: version: 2.93.0 Alpha\n\nFor Geo Nodes, Point Instance node doesn't work (doesn't copy) meta objects (like metaball). \n\nI used a very basic setup. The original input and output nodes plus one point instance node. I selected the object to be a meatball. Nothing happens! I selected any other object (non-meta). The object is instanced. Geo nodes were added to the default cube. \n", "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", "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.", "node editor: Texture preview refresh with cursor selection\nOperating system: 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux\nGraphics card: RTX 2070\n\nBroken: Blender 2.93.0, Commit date: 2021-02-17 06:07, Hash 17dddc941714\n\nwhen selecting things in geonodes space the texture preview refresh anomaly.\n\n- Open blender default file.\n- Open the geometry nodes editor\n- Add a geometry node group\n- Open the texture tab ( property panel )\n- Add a texture for the current brush\n- Change to cloud texture\n- Try to select things with cursor select ( Key : C ) in the geometry nodes area.\n- It will refresh the texture preview\n\n[untitled.blend](untitled.blend)\n[Kazam_screencast_00003.mp4](Kazam_screencast_00003.mp4)", "Weird Motion Blur with Simulation Nodes\nBroken: 3.6.2\n\nMotion Blur doesn't work properly with Geometry Nodes instances.\nAs shown in the rendered video, the motion blur seems to give weird results, the motion trails of the instanced particles from the Geometry Nodes (and Simulation Nodes) setup don't seem to follow their direction properly.\n\n<video src=\"attachment\" title=\"animation.mp4\" controls></video>\n\n[Test.blend](attachment)\n- Open file\n- Hit play to bake simulation until let's say frame 45\n- Render frame 45\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", "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", "Hotkeys conflict between Shader Nodes, Compositing Nodes, GeoNodes and Texture Node Editor.\nOperating system: Windows-10-10.0.17763-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.6\n\nI have hotkeys on frequently used nodes in shader editor. When I switch to Compositing, first of all I have hotkeys already assigned to similar nodes (I did it in shader editor, but they are automatically assigned in compositing). Secondly, I get an error in Compositing - Not a shader or geometry node tree.\n\n1) Apply the \"I\" button to the \"Invert\" node in the shader editor\n2) Switch to Compositing or Texture Node Editor\n3) Call the invert node with the I button\n\nYou get the following error \n```\nPython: Traceback (most recent call last):\n\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 138, in invoke\n result = self.execute(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 129, in execute\n self.create_node(context)\nFile \"D:\\BF_daily_build\\2.93.0\\blender-2.93.7-candidate+v293.4ec6cc412d7f-windows.amd64-release\\2.93\\scripts\\startup\\bl_operators\\node.py\", line 92, in create_node\n node = tree.nodes.new(type=node_type)\n\nRuntimeError: Error: Cannot add node of type ShaderNodeInvert to node tree 'Geometry Nodes'\n\nNot a shader node tree\n\nlocation: <unknown location>:-1\n```\nbandicam_2021-11-26_16-53-56-020.mp4\nNode_Conflict.blend\n\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", "Segfault with gdb debugger in PointsToVolume node\nOperating system: Linux-6.4.3-gentoo-x86_64-AMD_Ryzen_9_7950X_16-Core_Processor-with-glibc2.37 64 Bits, WAYLAND UI\nGraphics card: AMD Radeon RX 7900 XT (gfx1100, LLVM 15.0.7, DRM 3.52, 6.4.3-gentoo) AMD 4.6 (Core Profile) Mesa 23.1.3\n\nBroken: version: 4.0.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `Unknown`\n\nGCC builds with a gdb debugger attached crash in the Points-to-Volume node.\nThis does not happen if no debugger is attached, or when using msbuild.\n\nUse a GCC Debug build, run Blender with a GDB debugger attached.\nCreate a point cloud and convert it to a volume.\n\n\nOpenVDB will throw a lot of warnings about missing RTTI on the [`ParticlesToLevelSet::Raster`](ParticlesToLevelSet.h#L468) class.\n```\nRTTI symbol not found for class 'tbb::interface9::internal::finish_reduce<openvdb::v10_0::tools::ParticlesToLevelSet<openvdb::v10_0::Grid<openvdb::v10_0::tree::Tree<openvdb::v10_0::tree::RootNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::LeafNode<float, 3u>, 4u>, 5u> > > >, void, openvdb::v10_0::util::NullInterrupter>::Raster<blender::geometry::OpenVDBParticleList, openvdb::v10_0::Grid<openvdb::v10_0::tree::Tree<openvdb::v10_0::tree::RootNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::InternalNode<openvdb::v10_0::tree::LeafNode<float, 3u>, 4u>, 5u> > > > > >'\n```\n\n~~This appears to be a long-standing gcc bug:\nshow_bug.cgi?id=81932\nThe nested `Raster` class is virtual due to its destructor, which seems to be the condition triggering this problem.~~\nEDIT: The same problem occurs with the _Volume Cube_ node, the gdb warning might be a red herring. Removing the `virtual` keyword from the `Raster` class also silences the warning, not sure if this class really must be virtual at all.\n\nThe effect is that debugging any file containing a Points-to-Volume node with gdb becomes impossible. I'm not sure if there is anything we can do on the Blender side to work around the problem.\n\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" ]

[ "Crash in GN when severing a connection before a 'Reroute' node going to a 'Join Geometry' node.\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.79\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.3.1 Stable\n\nBlender crashes in GN workspace when trying to sever a connection with 'Ctrl+RMB drag'. The connection severed needs to be before a 'Reroute' going into a 'Join Geometry'. When the connection before the 'Reroute' is severed, the crash occurs.\n\n1. Place a 'Join Geometry' between 'Group Input' and 'Group Output'.\n2. Create a 'Reroute' between 'Group Input' and 'Join Geometry'.\n3. Using 'Ctrl+RMB drag', sever the connection between 'Group Input' and 'Reroute'.\n\n\n[GN Join Geometry crash.blend](GN_Join_Geometry_crash.blend)\n\n\n\n", "Regression: assert and crash on Connecting empty reroute node to multi socket\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 496.49\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nCaused by: db0ef8b00d3c\n\nIf you plug a reroute node into a multisocket with no data entered into it, blender will crash.\n\n```lines=10\nStack trace:\nblender.exe :0x00007FF7711E3DC0 bli_windows_system_backtrace_stack_thread F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:219\nblender.exe :0x00007FF7711E2EC0 BLI_windows_system_backtrace_stack F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:306\nblender.exe :0x00007FF7711E28C0 BLI_system_backtrace F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:372\nblender.exe :0x00007FF7711E7F80 _BLI_assert_print_backtrace F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:36\nblender.exe :0x00007FF770E186D0 <lambda_96a7f9c242f31bac247b4262dc0c3ff6>::operator() F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:654\nblender.exe :0x00007FF770E0FBB0 blender::FunctionRef<void __cdecl(blender::fn::lazy_function::LockedNode &)>::callback_fn<<lambda_9 F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\BLI_function_ref.hh:95\nblender.exe :0x00007FF770E19950 blender::FunctionRef<void __cdecl(blender::fn::lazy_function::LockedNode &)>::operator() F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\BLI_function_ref.hh:132\nblender.exe :0x00007FF770E248A0 blender::fn::lazy_function::Executor::with_locked_node F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:584\nblender.exe :0x00007FF770E22480 blender::fn::lazy_function::Executor::run_node_task F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:693\nblender.exe :0x00007FF770E22700 blender::fn::lazy_function::Executor::run_task F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:612\nblender.exe :0x00007FF770E1C5E0 blender::fn::lazy_function::Executor::execute F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:317\nblender.exe :0x00007FF770E1C850 blender::fn::lazy_function::GraphExecutor::execute_impl F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:1185\nblender.exe :0x00007FF76F028AB0 blender::fn::lazy_function::LazyFunction::execute F:\\Blender_build\\first\\blender\\source\\blender\\functions\\FN_lazy_function.hh:327\nblender.exe :0x00007FF76F025790 compute_geometry F:\\Blender_build\\first\\blender\\source\\blender\\modifiers\\intern\\MOD_nodes.cc:1184\nblender.exe :0x00007FF76F02E960 modifyGeometry F:\\Blender_build\\first\\blender\\source\\blender\\modifiers\\intern\\MOD_nodes.cc:1305\nblender.exe :0x00007FF76F00BA50 modifyGeometrySet F:\\Blender_build\\first\\blender\\source\\blender\\modifiers\\intern\\MOD_nodes.cc:1343\nblender.exe :0x00007FF76E5ABC50 modifier_modify_mesh_and_geometry_set F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\DerivedMesh.cc:629\nblender.exe :0x00007FF76E5A9730 mesh_calc_modifiers F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\DerivedMesh.cc:972\nblender.exe :0x00007FF76E5A9150 mesh_build_data F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\DerivedMesh.cc:1585\nblender.exe :0x00007FF76E5AF0A0 makeDerivedMesh F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\DerivedMesh.cc:1744\nblender.exe :0x00007FF76E5F6DA0 BKE_object_handle_data_update F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\object_update.cc:165\nblender.exe :0x00007FF76E5F6C50 BKE_object_eval_uber_data F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\object_update.cc:329\nblender.exe :0x00007FF76ED41CF0 <lambda_dfec21a1fb9cbd0068712bf807655c50>::operator() F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\builder\\deg_builder_nodes.cc:1513\nblender.exe :0x00007FF76ED3C930 std::invoke<<lambda_dfec21a1fb9cbd0068712bf807655c50> &,Depsgraph *> C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.30.30705\\include\\type_traits:1503\nblender.exe :0x00007FF76ED36100 std::_Invoker_ret<void,1>::_Call<<lambda_dfec21a1fb9cbd0068712bf807655c50> &,Depsgraph *> C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.30.30705\\include\\functional:652\nblender.exe :0x00007FF76ED45410 std::_Func_impl_no_alloc<<lambda_dfec21a1fb9cbd0068712bf807655c50>,void,Depsgraph *>::_Do_call C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.30.30705\\include\\functional:823\nblender.exe :0x00007FF76ED097D0 std::_Func_class<void,Depsgraph *>::operator() C:\\Program Files\\Microsoft Visual Studio\\2022\\Community\\VC\\Tools\\MSVC\\14.30.30705\\include\\functional:870\nblender.exe :0x00007FF76ED0A2F0 blender::deg::`anonymous namespace'::evaluate_node F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:114\nblender.exe :0x00007FF76ED09F60 blender::deg::`anonymous namespace'::deg_task_run_func F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:128\nblender.exe :0x00007FF771283950 Task::operator() F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc:165\nblender.exe :0x00007FF771284160 tbb_task_pool_run F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc:215\nblender.exe :0x00007FF7712847A0 BLI_task_pool_push F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\task_pool.cc:472\nblender.exe :0x00007FF76ED0A8A0 blender::deg::`anonymous namespace'::schedule_node_to_pool F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:64\nblender.exe :0x00007FF76ED092D0 blender::deg::`anonymous namespace'::schedule_node<void __cdecl(blender::deg::OperationNode *,int,T F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:287\nblender.exe :0x00007FF76ED08DB0 blender::deg::`anonymous namespace'::schedule_children<void __cdecl(blender::deg::OperationNode *,i F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:304\nblender.exe :0x00007FF76ED092D0 blender::deg::`anonymous namespace'::schedule_node<void __cdecl(blender::deg::OperationNode *,int,T F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:281\nblender.exe :0x00007FF76ED08DB0 blender::deg::`anonymous namespace'::schedule_children<void __cdecl(blender::deg::OperationNode *,i F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:304\nblender.exe :0x00007FF76ED092D0 blender::deg::`anonymous namespace'::schedule_node<void __cdecl(blender::deg::OperationNode *,int,T F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:281\nblender.exe :0x00007FF76ED08DB0 blender::deg::`anonymous namespace'::schedule_children<void __cdecl(blender::deg::OperationNode *,i F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:304\nblender.exe :0x00007FF76ED092D0 blender::deg::`anonymous namespace'::schedule_node<void __cdecl(blender::deg::OperationNode *,int,T F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:281\nblender.exe :0x00007FF76ED08DB0 blender::deg::`anonymous namespace'::schedule_children<void __cdecl(blender::deg::OperationNode *,i F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:304\nblender.exe :0x00007FF76ED092D0 blender::deg::`anonymous namespace'::schedule_node<void __cdecl(blender::deg::OperationNode *,int,T F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:281\nblender.exe :0x00007FF76ED09110 blender::deg::`anonymous namespace'::schedule_graph<void __cdecl(blender::deg::OperationNode *,int, F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:293\nblender.exe :0x00007FF76ED0A250 blender::deg::`anonymous namespace'::evaluate_graph_threaded_stage F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:339\nblender.exe :0x00007FF76ED09CC0 blender::deg::deg_evaluate_on_refresh F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\eval\\deg_eval.cc:459\nblender.exe :0x00007FF76ECB5C10 deg_flush_updates_and_refresh F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc:45\nblender.exe :0x00007FF76ECB5D70 DEG_evaluate_on_refresh F:\\Blender_build\\first\\blender\\source\\blender\\depsgraph\\intern\\depsgraph_eval.cc:69\nblender.exe :0x00007FF76E098BD0 scene_graph_update_tagged F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\scene.cc:2680\nblender.exe :0x00007FF76E09C900 BKE_scene_graph_update_tagged F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\scene.cc:2728\nblender.exe :0x00007FF76DD58D60 wm_event_do_depsgraph F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:446\nblender.exe :0x00007FF76DD5AFD0 wm_event_do_refresh_wm_and_depsgraph F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:469\nblender.exe :0x00007FF76DD5A2D0 wm_event_do_notifiers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:692\nblender.exe :0x00007FF76DD21ED0 WM_main F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm.c:646\nblender.exe :0x00007FF76DD19C30 main F:\\Blender_build\\first\\blender\\source\\creator\\creator.c:579\nblender.exe :0x00007FF77162B830 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF77162B5E0 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF77162B5C0 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF77162B8F0 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThreads:\nThread : 000003ac\nntdll.dll :0x00007FFA763D0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA76382680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00002be0\nntdll.dll :0x00007FFA763D0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA76382680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00000e60\nntdll.dll :0x00007FFA763D0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA76382680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 0000324c\nntdll.dll :0x00007FFA763CCFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA73DB1A40 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFA1BC71C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFA1B9FF73C Symbols not available\n\n\nThread : 0000429c\nntdll.dll :0x00007FFA763CDA80 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFA73DDCAD0 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFA73DDCAB0 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFA1BCA7770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFA1BCA7770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00003550\nwin32u.dll :0x00007FFA741AA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFA74B606F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFA1BC71C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00002f18\nntdll.dll :0x00007FFA763D0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA76382680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 000006a0\nntdll.dll :0x00007FFA763D0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFA76382680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00003a7c\nntdll.dll :0x00007FFA763CDA80 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFA73DDCAD0 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFA7550A260 CoRevokeInitializeSpy\ncombase.dll :0x00007FFA7550A260 CoRevokeInitializeSpy\ncombase.dll :0x00007FFA7550A260 CoRevokeInitializeSpy\ncombase.dll :0x00007FFA7550A260 CoRevokeInitializeSpy\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 00003120\nntdll.dll :0x00007FFA763CCFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFA73DB1A40 WaitForSingleObjectEx\nWintab32.dll :0x00007FFA6A072050 hn_wintab_OnTimeout\nWintab32.dll :0x00007FFA6A072050 hn_wintab_OnTimeout\nWintab32.dll :0x00007FFA6A072050 hn_wintab_OnTimeout\nKERNEL32.DLL :0x00007FFA76217020 BaseThreadInitThunk\nntdll.dll :0x00007FFA76382630 RtlUserThreadStart\n\n\nThread : 0000092c\nwin32u.dll :0x00007FFA741AA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFA74B606F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFA6095458B Symbols not available\n\n\nLoaded Modules :\n0x00007FF76BE30000 3.4.0.0 blender.exe F:\\Blender_build\\first\\ninja_lite_debug\\source\\creator\\Debug\\blender_private.pdb\n0x00007FFA76330000 10.0.19041.1806 ntdll.dll\n0x00007FFA76200000 10.0.19041.1806 KERNEL32.DLL\n0x00007FFA73D90000 10.0.19041.1826 KERNELBASE.dll\n0x00007FFA74390000 10.0.19041.1806 SHELL32.dll\n0x00007FFA74060000 10.0.19041.789 msvcp_win.dll\n0x00007FFA73C90000 10.0.19041.789 ucrtbase.dll\n0x00007FFA74B40000 10.0.19041.1503 USER32.dll\n0x00007FFA741A0000 10.0.19041.1826 win32u.dll\n0x00007FFA75DF0000 10.0.19041.1620 GDI32.dll\n0x00007FFA73B80000 10.0.19041.1706 gdi32full.dll\n0x00007FFA74EE0000 10.0.19041.1682 ADVAPI32.dll\n0x00007FFA64770000 epoxy-0.dll\n0x00007FFA75E20000 7.0.19041.546 msvcrt.dll\n0x00007FFA388C0000 3.10.2150.1013 python310_d.dll\n0x00007FFA75EC0000 10.0.19041.1586 sechost.dll\n0x00007FFA64200000 14.30.30708.0 MSVCP140D.dll\n0x00007FFA75BD0000 10.0.19041.1806 RPCRT4.dll\n0x00007FFA6D510000 14.30.30708.0 VCRUNTIME140D.dll\n0x00007FFA711A0000 14.30.30708.0 VCRUNTIME140_1D.dll\n0x00007FFA74D90000 10.0.19041.1202 ole32.dll\n0x00007FFA754D0000 10.0.19041.1741 combase.dll\n0x00007FFA616F0000 6.10.19041.1110 COMCTL32.dll\n0x00007FFA59F30000 10.0.19041.685 ucrtbased.dll\n0x00007FFA75AE0000 10.0.19041.546 WS2_32.dll\n0x00007FFA75470000 10.0.19041.1706 SHLWAPI.dll\n0x00007FFA74CE0000 10.0.19041.1741 shcore.dll\n0x00007FFA6ED30000 10.0.19041.546 VERSION.dll\n0x00007FFA70980000 14.30.30708.0 VCRUNTIME140.dll\n0x00007FFA74360000 10.0.19041.546 IMM32.dll\n0x00007FFA62D10000 10.0.19041.867 dbghelp.dll\n0x00007FFA717F0000 10.0.19041.746 dwmapi.dll\n0x00007FFA71B00000 10.0.19041.1806 windows.storage.dll\n0x00007FFA732D0000 10.0.19041.1806 Wldp.dll\n0x00007FFA73960000 10.0.19041.844 profapi.dll\n0x00007FFA70B20000 10.0.19041.1620 uxtheme.dll\n0x00007FFA71820000 10.0.19041.546 kernel.appcore.dll\n0x00007FFA741D0000 10.0.19041.1415 bcryptPrimitives.dll\n0x00007FFA75830000 10.0.19041.1806 MSCTF.dll\n0x00007FFA75D00000 10.0.19041.985 OLEAUT32.dll\n0x00007FFA63F10000 10.0.19041.1806 OPENGL32.DLL\n0x00007FFA6A0B0000 10.0.19041.1806 GLU32.dll\n0x00007FFA75A30000 2001.12.10941.16384 clbcatq.dll\n0x00007FFA6E560000 10.0.19041.1620 AppXDeploymentClient.dll\n0x00007FFA1AF40000 30.0.14.9649 nvoglv64.dll\n0x00007FFA74F90000 10.0.19041.1741 SETUPAPI.dll\n0x00007FFA74260000 10.0.19041.1620 cfgmgr32.dll\n0x00007FFA74170000 10.0.19041.1023 bcrypt.dll\n0x00007FFA70210000 10.0.19041.546 WTSAPI32.dll\n0x00007FFA73240000 10.0.19041.546 CRYPTBASE.DLL\n0x00007FFA734E0000 10.0.19041.546 msasn1.dll\n0x00007FFA6E480000 10.0.19041.906 cryptnet.dll\n0x00007FFA73A20000 10.0.19041.1320 CRYPT32.dll\n0x00007FFA6AF70000 10.0.19041.1566 drvstore.dll\n0x00007FFA73710000 10.0.19041.1620 devobj.dll\n0x00007FFA74100000 10.0.19041.1806 WINTRUST.dll\n0x00007FFA727A0000 10.0.19041.546 ntmarta.dll\n0x00007FFA6DE70000 10.0.19041.546 dxcore.dll\n0x00007FFA73890000 10.0.19041.546 powrprof.dll\n0x00007FFA73870000 UMPDC.dll\n0x00007FFA73810000 10.0.19041.546 WINSTA.dll\n0x00007FFA63C20000 10.0.19041.1387 dataexchange.dll\n0x00007FFA6F3D0000 10.0.19041.1741 d3d11.dll\n0x00007FFA702F0000 10.0.19041.1741 dcomp.dll\n0x00007FFA72400000 10.0.19041.1806 dxgi.dll\n0x00007FFA6CE80000 10.0.19041.1806 twinapi.appcore.dll\n0x00007FFA65F30000 10.0.19041.1806 textinputframework.dll\n0x00007FFA71060000 10.0.19041.746 CoreMessaging.dll\n0x00007FFA70D00000 10.0.19041.546 CoreUIComponents.dll\n0x00007FFA705E0000 10.0.19041.1682 wintypes.dll\n0x00007FFA66C60000 7.2.19041.746 Oleacc.dll\n0x00007FFA6A070000 1.0.0.1 Wintab32.dll\n0x00007FFA53C40000 10.0.19041.1023 explorerframe.dll\n0x00007FFA60940000 10.0.19041.1566 directmanipulation.dll\n0x00007FFA73470000 10.0.19041.546 CRYPTSP.dll\n0x00007FFA72A50000 10.0.19041.1052 rsaenh.dll\nBLI_assert failed: F:\\Blender_build\\first\\blender\\source\\blender\\functions\\intern\\lazy_function_graph_executor.cc:654, operator ()(), at 'default_value != nullptr'\n```\n\n1. Create new geometry node modifier\n2. Add `Join Geometry` / `To Instances` and connect to group input and output\n3. Create new reroute node\n4. Connect reroute to multi input socket\n\n[2022-10-09 04-39-29.mp4](2022-10-09_04-39-29.mp4)" ]

[ "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", "Slow camera view navigation in Cycles rendered shading mode with many instances\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.0.0 Alpha\nWorked: 2.93\n\nWhen looking through camera and navigating the viewport (with Lock Camera to View for example), the movement is much slower than a regular perspective view. This happens in rendered shading mode with Cycles, when many object instances are in the scene. Instances can be generated with Geometry Nodes or the old particle system. Also they don't even have to be visible on screen, you could be looking at a single cube somewhere to the side, and the camera navigation will still be slow.\n[camera navigation bug.blend](camera_navigation_bug.blend)\n\n\n - Use the provided file\n - Switch to rendered mode and disable overlays\n - Try looking around\n - Switch to camera view\n # Navigation should be much slower and unresponsive\n\n\n\n", "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)", "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", "heap-use-after-free when cancelling animation playback from frame change handler\nOperating system: macOS-13.4-arm64-arm-64bit 64 Bits\nGraphics card: Metal API Apple M2 Max 1.2\n\nBroken: version: 4.0.0 Alpha\nWorked: Don't know. Only managed to reproduce using ASAN builds, which is time consuming to do for the previous releases\n\n\nExecuting `bpy.ops.screen.animation_cancel()` from a `frame_change_post` would lead to `heap-use-after-free` ASAN error with the following stacktrace: [stacktrace.txt](attachment)\n\nThis is one of the minimalistic ASAN errors which I've found while looking into updates in the #107248 (107248#issuecomment-962171).\n\n\n- Start blender with ASAN (to give it the best possible chance of success)\n- Open attached .blend file\n- Run the script\n- Hit spacebar to start playback\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)", "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", "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\n\n", "Crash on Mac when starting with `--debug-gpu` flag\nOperating system: Mac OS Ventura 13.1\nGraphics card: Apple M1 Max\n[system-info.txt](system-info.txt)\n\nBroken: 3.4.1\nWorked: 3.3.2\n\nBlender won't start on a Mac when starting with `--debug-gpu` flag.\nThe terminal output is this:\n\n```\n/Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\nRead prefs: /Users/vollstock/Library/Application Support/Blender/3.4/config/userpref.blend\nWARN (gpu.debug): source/blender/gpu/opengl/gl_debug.cc:165 init_gl_callbacks: Failed to hook OpenGL debug callback. Use fallback debug layer.\nzsh: segmentation fault /Applications/Blender\\ 3.4.1.app/Contents/MacOS/Blender --debug-gpu\n```\n\n\nStart with the flag\n\n```\n/Applications/Blender.app/Contents/MacOS/Blender --debug-gpu\n```", "Metal: selection with GPU depth picking is broken in wireframe mode\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\nWhen working in the 3D viewport, when in Wireframe mode and Xray mode is OFF, clicks to select an object are passed through and select objects behind the object. It's very difficult to select the object whose intention it is to select.\nview?usp=sharing\n\nThe video link above demonstrates this.\n\n\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)", "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", "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", "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", "Render animation cycles-x bug March 11, 2022\nOperating system: macOS-12.3-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13\n\nBroken: version: 3.2.0 Alpha\n\nRender count from 1 to 1200 frames\n\n\nBlender 3.2.0 Alpha within Cycles-x\nPush the 'Command + F12\" and render animation cause bug between start to end (855 - 1200 frames)\n\nBlender and video file: [Blender 3-2-0 by Kent Davis March 11 2022.zip](Blender_3-2-0_by_Kent_Davis_March_11_2022.zip)\n\n\n\n\n\n\n\nRadeon Pro 575:\n\n```\nChipset Model:\tRadeon Pro 575\nType:\tGPU\nBus:\tPCIe\nPCIe Lane Width:\tx16\nVRAM (Total):\t4 GB\nVendor:\tAMD (0x1002)\nDevice ID:\t0x67df\nRevision ID:\t0x00c4\nROM Revision:\t113-D000AA-931\nVBIOS Version:\t113-D0001A1P-025\nEFI Driver Version:\t01.00.931\nMetal Family:\tSupported, Metal GPUFamily macOS 2\nDisplays:\n```\niMac:\n```\nDisplay Type:\tBuilt-In Retina LCD\nResolution:\tRetina 5K (5120 x 2880)\nFramebuffer Depth:\t30-Bit Color (ARGB2101010)\nMain Display:\tYes\nMirror:\tOff\nOnline:\tYes\nAutomatically Adjust Brightness:\tNo\nConnection Type:\tInternal\n```\n\n" ]

[ "MacOS crash when opening a second rendered 3dview window --MacOS 13.0.1--\nOperating system: macOS-13.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.9.48\n\nBroken: version: 3.5.0 Alpha\n\n\nWhen in rendered 3dview and open a second window also in rendered 3d view, blender hangs for 20 sec. and then MacOS becomes unresponsive and finally crashes.\nNo way to 'force quit' or any other trick to stop blender. or the MacOS crash.\nThis happened now 5 times in a row, always when opening a second new window also in rendered 3dview.\n\nOpen blender 3.4 /3.5 in MacOS 13.01 & switch to rendered 3dview. Then after a minute open another rendered 3dview window.\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) ", "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", "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", "NLA Visual Bake of Actions (with Rigify character) Gives broken results.\nOperating system: Windows 10 Home 64bit\nGraphics card: GeForce RTX 2080\n\nBroken: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: c77597cd0e15, type: release, build date: 2022-03-09, 00:44:13\nWorked: 3.0 and later - All that can open this file correctly.\n\n**Description**\n(Files provided for testing)\nyou'll find a stack of NLA Action strips resulting in desired animation.\nBaking those actions into a single Action using visual keying results in Broken looking animation (baked action is set to Replace).\nAdditionally even though the resulting strip is set to replace and placed as the top layer. Turning Layers on/off below it affects the resulting pose on the character.\nOne would expect once the top layer is set to Replace, anything happening in the lower layers should have no apparent effect and could safely be removed from the NLA.\n\nAttached Viewport Renders of Pre and Post Bakes for reference.\nAttached Character rig used as a Library override (save and relocate the library override from the outliner in the Animation file)\nAttached The Animation File in which I am attempting to Bake.\n\n[MomoDebug_A_rig.blend](MomoDebug_A_rig.blend)\n\n[BadBakeNLAActions.blend](BadBakeNLAActions.blend)\n\n- Open file BadBakeNLAActions.blend. MomoDebug_A_rig.blend is linked, so may need relocating\n- Delete The top NLA track - it is my failed bake.\n# Turn on all other tracks below\n\n- Run Object > Animation > Bake Action. Use Visual keying option.\n- Turn off all the layers below (EXCEPT for the WORLD PLACER, that one doesn't get baked because it affects the rig Object itself rather than the bones)\n\nResult:\nI couldn't remove the layers below without breaking the animation.\n\n", "Smoke artefacts when baking smoke simulation based on particles\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.59\n\nBroken: version: 3.2.2\nWorked: none\n\nI have a baked particle simulation that is propelled by a wind force field. Next, I have a smoke simulation whose flow source is set to particle system.\nWhen I run the simulation it takes much longer than usual and ends up creating lines of smoke in random directions.\n\nI add that all the sliders in the field weights tab of the domain object are at 0 (gravity, all...) so no force field can be the cause of this scattering\n\nHere are some pictures of the problem :\n\n\n\nWith higher resolution :\n\n\n- Open the blend file\n- Bake Particles\n- Bake Smoke\n\n[SceneProblem2.blend](SceneProblem2.blend)\n\n", "Crash while switching to edit mode with EEVEE + Geometry Nodes\nOperating system: macOS-10.15.7-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 650M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-14.0.32 355.11.11.10.10.143\n\nBroken: version: 3.0.0\n\nWhen switching to edit mode in while the viewport's set to render it crashes (see attached video)\n[blender crash 2021-12-17 21-54-00.mp4](blender_crash_2021-12-17_21-54-00.mp4)\n\n1 load the attached file\n2 switch to rendered view in the viewport\n3 switch to edit vertex mode\n4 that's a crash!\n\n[transitions_001_blender3.blend](transitions_001_blender3.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", "Selected Objects render state (hidden in renders) causes baking of black images (also these are visible in renders after baking, setting is not as it was before)\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.09\n\nBroken: version: 3.1.0\nWorked: Cannot find any - tested back to 2.81\n\nIf rendering of the selected object is not enabled, then the baking will fail with a black image created.\nStrangely the rendering icon for this object will be automatically turned-on in the outliner - if you hover your mouse over.\nBaking will still fail - even though the icon now shows that rendering is enabled.\nTurning off render, then turning it back on again will fix the problem so that baking will now work.\n\nLoad the blend file attached (or use your own scene set-up for baking).\n[Bake selected to active has black image.blend](Bake_selected_to_active_has_black_image.blend)\nClick on Bake to confirm that the baking is successful.\n\nDisable render for the Selected object.\n\nClick on Bake again, and a black image will be created.\n\nNote that the Selected object still has rendering disabled.. Move your mouse into the Outliner above the render icon, and observe that rendering for the Selected object automatically becomes enabled.\n\nClick on Bake again and observe a black image is still created.\nDisable rendering for the Selected object, then enable it again.\nClick on Bake again and the baking will be successful.\n\n\nObservations:\n1) If rendering is disabled for the active object, then this error is shown.\n\n2) The bake duration is the same whether the rendering is enabled for the selected object or not. (Mine was taking a 2.5 minutes, and it took a long time to figure out what the problem was.)\n3) Saving the blend file and reloading fixes the problem - the state is persisted as render==enabled.", "Material Properties Button\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: AMD Radeon RX 6700 XT ATI Technologies Inc. 4.5.0 Core Profile Context 22.20.18.220726\n\nBroken: version: 3.5.0\n\nevery time i click on the materials properties button on the right, blender shut down.\n\nit happens when you start or anytime what you are doing. Just start program, click materials properties button.\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", "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", "Particle system with collision modifier hangs on baking\nOperating system: Linux-5.8.0-55-generic-x86_64-with-glibc2.31 64 Bits\nGraphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.80\n\nBroken: version: 2.93.0\nWorked: 2.81a\n\n[#88965.blend](T88965.blend)\n\n- Open file\n- Bake particles on LRG_Submarine_Propeller object\n\nIt fails. When you disable collision modifier on LRG_Submarine_Hull object or simplify it considerably, it works.", "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", "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", "Clicking \"Bake All Dynamics\" causing various crashes.\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 536.99\n\nBroken: version: 3.6.2\n\nUsing \"Bake All Dynamics\" is beyond finicky and crashes Blender in many different use cases. Many little \"tricks\" are needed to make it work. I am using Disk Cache for all below situations, but I believe the crashes happen with or without this.\n\nSituations where it crashes:\nClicking \"Bake All Dynamics\" within the Cloth cache settings. It seems it's required to click \"Bake All Dynamics\" button within the context of the Rigid Body system, or else it crashes instantly.\n\nClicking \"Bake All Dynamics\" in the context of hair dynamics seems to do nothing. Same goes for \"Update All to Frame\"\n\nIf a rigid body simulation has been baked, clicking \"Delete All Bakes\", then clicking \"Bake All Dynamics\" immediately will also crash blender. The only workaround for this is to \"move\" an object even if using a zero value, before clicking \"Bake All Dynamics\" again. This prevents the crash. \n\n\nCreate a Rigid Body Sim, create a Cloth Sim. Check \"Disk Cache\" as an option. Try the various methods listed above.\n\n" ]

[ "Crashing after baking ( or clearing and baking ) simple smoke sim\nWindows 10, GTX 1070\n\nBroken: Blender 2.8 Alpha 2, 74737091c00\n\n\nBlender crashes either the first time baking, or after a few bake, clear and re-bakes.\n\n1) Start a new Scene\n2) Select the default cube ( probably already selected )\n3) Open the Physics Tab\n4) Select \"Smoke\" and Type \"Domain\"\n\n5) Shift A and add a UV Sphere\n6) In the Physics Tab, select \"Smoke\" and \"Flow\"\n\n7) Reselect the Cube, and go to the Cache tab in the Physics section\n\nNote that the buttons for caching can't be selected until you save.\n\n8) Save the scene\n9) Select \"Bake\"\n\nIf Blender doesn't crash...\n\n10) Select \"Free All Bakes\"\n11) GOTO 9 :)\n\nI've attached the simple .blend file, start at 9) if you're using it.[Smoke_Baking_Crash.blend](Smoke_Baking_Crash.blend)\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", "Cycles shaders show up in EEVEE list (Properties > Material tab > Surface panel)\nOperating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.60\n\nBroken: version: 2.80 (sub 75)\nAlso confirmed broken in 2.80 release candidates 2 and 3\nWorked: ----\n\nSome shaders not yet available in EEVEE, such as the Toon shader, are included in the list of shaders in the materials tab of the properties window even when EEVEE is selected as the render engine. When such shaders are selected, adjusting most of their parameters has no effect on the viewport/render. Currently, the only way to know which shaders are supported is either by trial and error or by using the node editor.\n\n1. With a fresh blender scene, check that EEVEE is the selected render engine, and go to materials tab in the properties window\n2. You should already have a material if it's the default cube scene. In the surface panel, click on the shader selector (set to principled BSDF by default)\n3. The menu that shows up includes Toon shader among other unsupported ones.\n\n[Based on the default startup]\n\n**Screenshot**\n\n\n", "Exaggerated Ambient Occlusion Effect with Subsurface Scattering Materials in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.2\n\nWhen rendering with Cycles, whenever meshes with materials that have subsurface scattering intersect, a very obvious ambient occlusion effect is generated around the intersections. It functions as expected with Eevee, but in Cycles, there's always a very unattractive dark seam line.\n\nApply any subsurface scattering materials to any two intersecting meshes, and render out with Cycles.\n\nHere are my results, I used a procedural snow shader, but I get similar results with any subsurface scattering materials.\n[subsurface scattering.blend](subsurface_scattering.blend)\nResults with Subsurface Scattering in Cycles\n\nSame shader in Cycles with Subsurface scattering turned off\n\nSame shader in Eevee with baked indirect lighting and subsurface scattering turned on\n\n\n", "Cycles: principled BSDF volume scattering\nThe idea is to add another \"subsurface scattering\" method, to specify the inside of the object.\n\nThe parameters for SSS are designed to specify an average color at the surface, and then absorption and scattering parameters are derived from that. Such parameters make less sense for thinner volumes, like absorption and scattering inside glass, ice or ocean water. Further, SSS uses a diffuse BSDF at the entry point which is not suitable for such effects.\n\nThe parameters for this would be similar to principled volume, likely:\n* Density\n* Scattering Color\n* Absorption Color\n* Anisotropy\n\nThe scattering implementation could be shared with random walk, for efficient handling of many scattering events. However this does mean no handling of internal objects, so potentially there could be an option for both, or some automatic optimization to handle both cases efficiently.\n\nFor handling refraction the entry point, in general this is tricky as there will be volume caustics with a glossy refraction. A possibility would be to make the surface transparent and ignore any refraction, or to use some blurring through filter glossy.", "Toon shader glossy removes direct and indirect light of diffuse shaders at low sizes with path tracing integrator\nOperating system: Ubuntu 18.04.1\nGraphics card: RX 480\n\nBroken: blender-2.80-a1ae04d15a9f\nEither CPU or GPU as rendering device\n\nWorked: set integrator to Branched Path Tracing\n\n\nToon BSDF glossy component at pretty low sizes nullifies(or removes) diffuse shader and toon shader diffuse direct lighting, at low or medium sizes it removes indirect lighting. This only occurs when the integrator is set to Path Tracing\n\nIn Cycles render engine\n1) subdivide initial cube, then set to smooth shading, set light to 1000 strength\n2) add a plane (to cast indirect light)\n3) add material to the cube, add mix shader with a fac of 0.1, in the first slot use a diffuse shader (or toon shader with diffuse component) with a color, now for the second slot set a toon shader with glossy component, set its size to 0.001\n4) set to render mode, the sphere should be colored but is dark with only the glossy component, when you change the glossy toon size to 0.003 the diffuse part appears but pretty dark, at 0.010 only the direct part of the diffuse shader is fully illuminated, at 0.030 the indirect part is still dark and at around 0.400 the indirect part is fully illuminated, all these were compared to branched path tracing\n[Glossy_toon_shader_bug.blend](Glossy_toon_shader_bug.blend)\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)", "simply moving the render window is terribly slow\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: AMD Radeon HD 7600M Series ATI Technologies Inc. 4.5.13422 Core Profile Context 0\n\nBroken: version: 2.82 (sub 6)\nWorked: (optional)\n\nwith more complex scenes (such as for example blenderman file 57e5084f0fcf294119c5055c) once you render an image and you have eevee in render preview mode, moving the render window becomes very slow, probably because eevee returns to refreshing the previw render without needing it.\n\nsee the video\n\n[GRAbwindow.mp4](GRAbwindow.mp4)\n", "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.", "Different padding between eevee and cycle properties\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: GeForce GT 630M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35\n\nBroken: version: 3.0.0 Beta\nWorked: ???\n\ndifferent padding see image below:\n\n\n\ni dont know is this because new ui design or not.\n\n\n", "Shading turns pink if combining UDIM + AOV\nOperating system: Windows 10\nGraphics card: GTX 1070 Ti\n\nBroken: 3.6.1 and 4.0 (963c0ed5e7b0)\nWorked: 3.5.0\n\nShading renders pink (viewport, eevee, cycles) when the material has an UDIM image texture and a AOV Output.\n\n\n\n- In the default's cube material, add an image texture node.\n- Click on \"new\" to create a new texture with \"Tiled\" enabled.\n- Connect the texture to the Principled BSDF node.\n- Add a AOV Output node.\n\nCube turns pink.\n\n", "EEVEE and Workbench missing animatable properties\nOperating system:\tWindows 7\nGPU:\t\t\tRadeon Vega 64, Divider version: 19.12.2\nCPU:\t\t\tIntel Core i7-5960X\n\n\nWorking-ish*:\t\t`blender-2.79b-f4dc9f9d68b-windows64` (official release) \nBroken:\t\t\t`blender-2.80-f6cb5f54494e-windows64` (official release) and later\n\n\nEEVEE and Workbench's render properties (`Properties Editor --> Render Properties`) are, for the most part, not animatable.\nThis is in contrast to Cycles which, *for the most part*, has all settings set to be animatable.\nBack in 2.79b the OpenGL \"Workbench\" Render options were supported:\n\n\n\nSome of the panels like Film, Simplify and Colour Management (which exist in all render engines) work as expected from 2.7X to 2.8X.", "Add interference effects to glossy and glass shaders\nAs a response to patch [D2003](D2003) and my own work in OSL ([interference script](showthread.php?403299-UPDATE-v1-6-Cycles-PBR-thin-film-interference-and-metals)), I suggest to add the option of interference effects to the glossy and glass shaders natively in cycles. Please note that I'm not familiar with the source code of Cycles, so this task description is based on cursory glancing through the code.\n\nThe OSL script suffers from the limitation that the effect of roughness on the surface normal does not influence the reflectance and transmittance factors calculated with the generalized Fresnel equations. Only the macroscale normal is used for the reflectance and transmittance. Patch [D2003](D2003) handles this in a more appropriate way for metals by applying the correct reflectance to each sample from a distribution of angles in case of rough surfaces. \n\nI propose to build on top of patch [D2003](D2003), which I expect to have pretty much laid out all the ground work, and to extend it to include one or two additional layers of an arbitrary material that can be described with a complex refractive index. \n\nThings to discuss:\n\n - Implementation: multiple glossy shaders, or a single shader that can handle substrate-only, substrate+1 layer, substrate+2 layers?\n - The phase of the reflectance is required for physically-correct behavior (no approximation). I implemented a complex math library in OSL just for this. Is it acceptable to do the same for cycles?\n - If for substrate-only the approximate Fresnel reflectances are used, then for 1 or two layers with zero thickness a small color change can occur as in that case the exact solution is used. Is that acceptable? (disregarding a check for zero thickness of course)\n - What to show the user? My OSL script has 3 n,k pairs (RGB) for each material (substrate, layer 1, layer 2). Then two thicknesses, one for each layer. I think this is the minimum. I optionally have the wavelengths of the RGB triplet and the refractive index of the outside medium as input via conditional compilation. The latter is perhaps the least useful, but the wavelengths determine the spacing between the interference fringes and therefore have an artistic value.\n\nThere are probably more things that I didn't think of, but this is a start. I am familiar with the physics and the equations that calculate such a feature and have experience with coding in C++. I would volunteer to implement interference effects in cycles and am thinking along the lines of co-development with a more senior Cycles developer.\n\n\n\n\n\n", "EEVEE renders black when no normal NODES connected to mix node --> normal input.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.92.0 Release Candidate\n\n\nEEVEE renders black when no normal NODES connected to mix node --> normal input. Works fine with Cycles. \n\nOpen below file and click on each material output to see the issue. Switch to cycles and all fine.\n\n[empty normal bug.blend](empty_normal_bug.blend)\n\n\n\n\n", "Cycles fully transparent shader is brighter when a Clear Coat shader is behind it\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 3.3.0 Alpha\nWorked: Never Worked\n\nWhen doing Decals, we often use alpha channel to define transparent area. However, I found when the Object's base color is above hsl(h,s,0.01), who's under the Decal, then the decal's transparent area will affect the underneath object's shading.\nMy test configuration is that 2048 viewport samples alongwith light bounces param all been set to 64.\nThe BUG is easier to notice when the background object is light grey, and the light is quite dimmed(or just turn down the exposure in colormangement to observe.)\n\n\n\n\n\nPlease open the attached Blend file to test.\n[Transparent shading BUG.blend](Transparent_shading_BUG.blend)\n\n", "EEVEE & Viewport Module\nThis page is in the process of being fully replaced by #eevee_viewport.\n\n---\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- `(straightforward)` - *Task which is straightforward to implement, which don't rely on larger API changes or refactoring.* \n\n# Long Term Projects\n\nDevelopment may span multiple release cycles.\n\n- {icon circle color=yellow} #68989 ( Selection future-proof design)\n- {icon circle color=yellow} #68990 (Vulkan support)\n- {icon circle color=yellow} [D5442: LANPR line rendering (summer of code)](D5442)\n- {icon circle color=yellow} #68991 (Fisheye / panorama in EEVEE)\n- {icon circle color=yellow} #68993 (Stereo Panorama in EEVEE)\n- {icon circle color=yellow} #68994 (VR design / usability)\n- {icon circle color=yellow} #68995 (VR input integration and mapping)\n- {icon circle color=yellow} #68464 (Better Motion Blur)\n- {icon circle color=green} #68996 (OpenSubdiv GPU acceleration)\n- {icon circle color=green} #68997 (Panorama selection support in viewport)\n- {icon circle color=green} #68463 (Dynamic Indirect light cache)\n- `?` #68998 (Virtual Reality (XR/VR/AR/MR))\n\n\n# Medium Term Projects\n\nDevelopment should be possible in a single release cycle.\n- {icon circle color=red} #71347 (Virtual Reality - Milestone 1 - Scene Inspection)\n- {icon circle color=yellow} #68478 (World Light Extraction)\n- {icon circle color=yellow} #68453 (Anisotropic BSDF)\n- {icon circle color=yellow} #68456 (Shadow catchers)\n- {icon circle color=yellow} #68474 (Clustered Light Culing)\n- {icon circle color=green} #67579 (Improve NDOF navigation)\n- {icon circle color=green} #54638 (OpenGL headless rendering)\n- {icon circle color=green} #68479 (Pointiness support)\n- {icon circle color=green} #68460 (Multiscatter Glossy BSDF)\n- {icon circle color=green} #68459 (Hair BSDF)\n- {icon circle color=green} #68458 (Velvet BSDF)\n- {icon circle color=green} #68477 (Parallax Occlusion Mapping)\n- {icon circle color=green} #68468 (Depth of Field Refactor)\n- {icon circle color=green} #68472 (Light Nodetree support)\n- {icon circle color=green} #68470 (Shadow buffers)\n- {icon circle color=green} #60779 (3D Viewport clipping support)\n\n# Paper Cuts\n\nSmall improvements and polish.\n\n- {icon circle color=green} #64281 (Option to lasso-select using geometry instead of object centers.)\n- {icon circle color=green} #69282 (Ability to cancel viewport operations (rotate/pan/zoom))\n- {icon circle color=green} #68206 (Lag reading viewport depth buffer in LookDev mode)\n- {icon circle color=green} #70803 (Support Viewport roll - around the cursor position) `(straightforward)`\n- {icon circle color=green} #73214 (Armature Object's \"Display As\" does nothing)\n- {icon circle color=green} #73732 (Grid-lines vanish in perspective view, when viewed from the side)\n" ]

[ "EEVEE roughness 0 results in bright white material\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.89\n\nBroken: version: 2.93.0 Alpha\nWorked: 2.92\n[faceting on bump.blend](faceting_on_bump.blend)\n\n\n\n\n", "Eevee: Transparent material goes superbright with clearcoat-/roughness set to zero\nOperating system: GENTOO Linux, updated regulary once a day\nGraphics card: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)\nGraphics driver: x11-drivers/nvidia-drivers-460.56\n\nBroken: since blender-2.93.0-f117ea262463-linux64\nWorked: until blender-2.93.0-8f2c3c63e970-linux64\n\nTransparent materials appear in pure white (like cut out of screen) when certain parameters are set to zero. Observed with roughness/clearcoat.roughness/subsurface - sometimes\nit looks like, this happens when a \"value\"-node is attached to that parameter input.\n\nLoad attached blend file and render with Eevee: The Sphere appears in pure white. Change the above mentioned parametes to x>0 and re-render: Everything looks fine.\n[MaterialError.blend](MaterialError.blend)", "Eevee: material transparency show up as a white glow in preview and render\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71\n\nBroken: 2.93.0 Alpha\nWorked: 2.93.0 Alpha\n\nThe transparent shader setup looks like \"white emission\" in material and render preview, it also appears in the final render\n\n\nAlso some funky things going on with Ambient occlusion and bloom settings:\n[2021-03-15 11-18-33.mkv](2021-03-15_11-18-33.mkv)\n\n\nIn the older version the file is okay:\n\n\n- Open attached .blend file\n- hit material preview or render preview\n[shader_test.blend](shader_test.blend)\n\n---\nPerhaps this not a bug but a setting that I need to enable or change? But this is not documented anywhere (maybe related to this other issue: #86558 (Eevee render / preview artifact))\n\nThanks,\n\nLawrence\n\n\n\n" ]

[ "Can't uninstall completely and clean\nwindows 7 SP1 64 bit\n\nBroken: 2.75a c27589e\n\nCan't uninstall completely when used \"Uninstall blender\" from Start menu, and need to manually delete\n\n\nthe old version (with .exe packed ) has an option that let's you select \"leave user setting\" or \"remove all things\" when you uninstall, but the new version (with .msi packed) no this option for uninstall, and will leave some files on your computer, by the way, it's have't choice for your install, e.g. create a desktop shortcut, use blender for .blend flies, and create start menu, all blender default at install, and I can't custom setting for this, although this no affect for our used, but i'm a little OCD :D\n\nsorry for my bad English :)\n", "Font rendered incorrectly with text object\nOperating system: Windows-10-10.0.22000-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.4.1\n\nThe font is displayed incorrectly when added to 3d text object\n\nFont and blend file in attachment\n[untitled.blend](untitled.blend)\n\n[roadrage.ttf](roadrage.ttf)\n\n", "Gizmo position is wrong for meshes with modifiers\nWin10, Win7, Mac OS Sierra\nGTX970, GTX750\n\nBroken: 2.78a e8299c8 , 2.66.0 r54697\n\n\nWhen a joint (for example, an arm) is bent, paint weight is not enough to express deformation around the joint. So it's a common practice to add a shape key for the bent shape and edit it.\nBut when you enter edit mode and select polygons to edit it, the manipulator is on wrong position. \n\nJust select faces. Manipulator is supposed to sit on the selected faces but it's not.\n\n[manipulator bug.blend](manipulator_bug.blend)", "Blending Factor Slider in Image Editors not working\nOperating system: Linux-5.15.0-50-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: NVIDIA GeForce RTX 2070 Super/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.61.05\n\nBroken: version: 3.4.0 Alpha\n\nThe \"Blending Factor\" slider in the Mask Display options doesn't work (= the image outside the masked area stays black).\n\n\n\nThe same display option works as expected in the Movie Clip Editor's mask mode.\n\n- Open Blender\n- Press F11 to open an Image Editor\n- Open an existing image or create a new e.g. a Color Grid\n- Switch the Image Editor to mask mode and draw a closed shape.\n- Go to the Mask Display menu and select the \"Overlay\" option and set it to \"Combined\"\n- Move the Blending Factor slider -> Nothing happens.", "Fonts with self-intersections not displayed correctly\nSome fonts downloaded from Google Fonts like `Quicksand`, `Raleway`, `Comfortaa`, `Jura`, have editable properties (width and others) and therefore have geometry full of intersections.\n\nThe `scanfill` in Blender has a limitation that does not consider the direction of the contours (clockwise with counterclockwise) to define a hole.\nHere is a **GIF** showing how the direction of the contour should influence the result:\n\n\nHere are some examples of fonts showing the problem:\n||||\n| -- | -- | -- | -- |\n|Roboto Flex|Quicksand|KG Broken Vessels Sketch|Comfortaa\n\n- Download any of the mentioned fonts.\n- Open simple .blend file with fonts implemented.\n[fontissues.blend](fontissues.blend)\n[KG_Broken_Vessels_Sketch.blend](KG_Broken_Vessels_Sketch.blend)\n[KGBrokenVesselsSketch.ttf](KGBrokenVesselsSketch.ttf)\n\n[Comfortaa-New.zip](Comfortaa-New.zip)\n[Quicksand-New.zip](Quicksand-New.zip)", "Reports & Warnings UI\n\n\nIn Blender, we want to improve how the app communicates to the user, for things like warnings, info, reports and progress bars.\n\nWe already have several separate systems for this:\n\n - We have a message popup in the status bar\n\n\n- We also have a separate 'Info' editor\n\n\nWe can make this nicer by tying things together more. Here's how.\n\n\n## Info editor improvements\n\nFirst, we need to add support for displaying messages, warnings and errors inside the Info Editor. We can do this by adding a switch at the top:\n\n{[F7655925](Screenshot_2019-08-09_at_11.33.10.png), size=full}\n\nWhen set to Messages, you'll see a list of messages and reports over time.\n\nCurrently we have two categories of messages: errors and info, but we can add a third:\n\n\nThis makes it clearer to the user if a message is positive (success), neutral (information) or negative (error):\n\n\nEach message type has an associated color. In the Info Editor Filter popover we could filter by type.\n\n\n\n**Readability**\nThe current Info Editor is impossibly difficult to read, visually. Everything is unseparated with text-wrap. The contents just become a wall of text that is very hard to read:\n\n\n[D6491](D6491) already implements some large benefits to readability by separating each notification and adding a header icon: {[F8253216](InfoEditor4.png), size=full}\n\nWe can do even more, by using progressive disclosure to let users open or close notifications, like so:\n{[F8253348](Screenshot_2019-12-31_at_12.24.31.png), size=full}\n\n## Status Bar\nWe can make a few improvements to the Status Bar also:\n\n**Click on message to open Info Editor window**\n\nBy clicking on the message or warning, you could be taken to the Info Editor. Simplest way is to spawn it as a new window.\n\n**Persistent error symbol**\n\nIf an error is unresolved, we can keep an error symbol in the Status Bar, so that the user knows the error still lingers.\n\n\n**Remove file info from Status Bar**\n\nCurrently there isn't much space to display full info messages and warnings in the Status Bar, because the file info is in the way.\n\nWe have received many requests to move the file info elsewhere:\n\n\n\nIn a vertical list, there would be a lot more space to communicate this kind of information, and we could add a lot more. This could be moved to the viewport, or in a Stats panel in the Scene Properties, for example.\n\nWith this out of the way, we have a lot more room for nicer messages and warnings.\n", "Action editor key frames not displaying sometimes\nSometimes when working with multiply animations and switching through them in the action editor. The Keyframes stop displaying for certain action. \nWhen the Panel with the action editor View is removed and added again, the displaying is working again.\nThis bug was seen in Version 2.76 and daily Build from 10/30/2015.\n\nError:\n\nFixed after closing and opening action editor view\n\n\nMy Project without Mesh. Bug is seen in walk_back_cycle action.\n[animation_editor_error_project.blend](animation_editor_error_project.blend)\n\nThis bug is very annoying in my workflow.\n\nGreetings and thank you for your work!", "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", "Some Overlays are not rendered in Viewport Render (Text Info incl object name, Statistics, 3D Cursor)\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 2.93.1\nAlso 3.1.0 Alpha\n\nUsing viewport render (or workbench) I'm unable to view object or empty names \n```\n(bpy.data.objects[\"NAME\"].show_name)\n```\n\nEnable show name on a visible object, and make a viewport render (bpy-ops-render-opengl)\nThe text isn't rendered in the image like it is in the viewport.\n\n", "GPencil: Hardlight blend issue\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce GTX 960M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.83.0\n\nThe semi-transparent textures of Grease Pencil material turn black when their layer is in HardLight blend mode.\n\n- open the provided blend file\n- see, wrong alpha blending\n- NB: change the blend mode and it works as expected\n\n[GP-hardlight-blend-issue.blend](GP-hardlight-blend-issue.blend)\n\n", "Do Not Allow The Image Resolution To Go Below 1 (or .8 at lowest)\nOperating system:\nGraphics card:\n\n2.8.3\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\n\nI have very poor vision. Before I realized the font text box also had little arrow sizers or something, I thought you had to type in the value only.\n\nWhen trying to type 1.4, I accidentally typed .1 somehow (I couldn't see the screen with 1.0 Resolution Scale).\n\nI almost uninstalled the software, but with 15 minutes and WIndows Magnifier I got lucky and found Edit Preferences again, and another 5 or 10 minutes to find the Resolution Scale textbox.\n\nA minimum resolution scale would easily solve this, to where it cannot go below 1 in my opinion, but maybe an 18 year old with eagle eyes and a 99 inch monitor might want smaller, like .8.\n\n\nEdit - Preferences - Type .1 in Resolution Scale and hit ok.\n\nLet me know if you can solve it from there without uninstalling. Its like a pinatta game, but should never happen in the best menu font system I have ever used (I made a video giving you an A++ today, until I found this bug, I crossed off an A.\n\nThe file attached is from a Resolution Scale of .6, which I can't risk setting it any lower or I can't get it back.\n\nHere is a video link of the problem if you care to watch:\nrstH-msnuuw\n\nPlease tell me you agree Resolution Scale has no business ever being so low the software is unreadable.\n\nNew users, especially those with visual impairments worse than mine may not be aware of the little slider arrows. I noticed them on my 5th attempt at learning Blender, and uninstalled / installed each time before I found the font setting today, \n\nFive minutes later I found the font bug.\n\n\nThank you,\n\nCorby / Data Juggler", "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", "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", "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", "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" ]

[ "Letters are missing in Blender Interface Texts\n{[F81894](bug.jpg)}Operating system and graphics card\nWindows 7 Ultimate 64bit , ATI Radeon HD 5450\n\nBroken: 2.70 official release\nWorked: 2.69\n\nAll of the Interface texts are missing letters. Tried every new version types ( 64 bit , 32 bit, .zip packages ). still problem exists.\n\nJust started blender. That's all I did.\n" ]

[ "EEVEE Holdout missing screen space reflections\nOperating system: windows 10\nGraphics card: rtx 2070 super\n\nBroken: 2.8.5\n\nscreen space reflections are not applied to an object from environment that has been held out using holdout button on collection. since the stuff is still there when holdout is applied to background, screen space should still be applied to objects that are not held out.\n\nhere is an example:\n\n\n\n[holdout ssr.blend](holdout_ssr.blend)", "Regression: broken normal shading, sharp edges appear on smooth surfaces.\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: 2.93, version: 3.0.0 Alpha\nWorked: 2.83.9, 2,92\n\nCaused by 1c22b551d0\nTo fix this, 5c4d24e1fd got reverted\nProblem still persists though...\n\n\nIn newer versions normal mapping looks broken, sharp edges appear.\nEevee and Cycles have same bug.\n\nupdated: [untitled.blend](untitled.blend)\n\ndifference in shading\n**2.93 on top, 2.8 down below:**\n\n\nThis effect appears even with very small angle of clean surface (without normal maps)\n\n\n\n<video src=\"2021-05-18_16-17-05.mp4\" title=\"F10122604/2021-05-18_16-17-05.mp4\" controls></video>", "Cycles: improve subsurface scattering for some meshes shapes\nIn cycles-x, the Christensen-Burley dipole approximation was fully replaced by random walk.\n\nHowever for some mesh shapes results are not as good, or could be improved regardless.\n* Self-intersection meshes give dark borders. Counting back/front facing intersections could help determine inside/outside better to avoid such artifacts.\n* Sharp corners \"glow\", which may be physically correct but is not necessarily desired. It may be possible to add user control with an option somehow, using some minimum throughput\n\nIf these can't be solved, we may consider adding back the dipole approximation, but since path splitting and the memory usage is a difficult fit for the new kernels we'd really like to avoid it.", "EEVEE: Alpha Blend + Show Backface material is out of focus.\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nIn EEVEE when the DOF is on, and the focus is on the glass object, it is blurred.\nOnly when you set the focus on an object that can be seen through the glass, it becomes sharp.\n\nI set up a simple animation in the blender file, where the camera's DOF is fixed on the glass ball, and the background moves forward and backward.\nFocus is only caught when the background overlaps with the ball.\n\n- Open Attached File\n- disable and enable`Show Backface`\n[focus bug.blend](focus_bug.blend)\n\n", "EEVEE-Next: Improve refraction denoising\nAs of now, the refraction rays reuse the same denoising pipeline as reflection rays. However this overblurs the results for low roughness.\n\nThis is because refraction lobe is dependent on IOR and roughness. So we need a way to compute the effective roughness of the glass based on its IOR and roughness.\n\nOne way to do that would be to fit a cone to the refracted lobe and try to match the reflective GGX roughness associated with a cone of the same angle.\n\n", "Strange background grid pattern appears on the compositor panel\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: Intel(R) Iris(R) Plus Graphics Intel 4.5.0 - Build 27.20.100.9079\n\nBroken: version: 2.93.5\nWorked: 2.91.2\n\nStrange grid pattern appears on the compositor background when zooming in (when backdrop is on).\n\nThis is what it should looks like:\n\n\nThis is what it actually looks like:\n\n\nAnd this only happens when I zoom in. At a very far-away view the background gradually becomes normal:\n\n\n\n\nThis does not happen on my other devices, so I think it might be a hardware compatibility problem. Also, I had the latest graphic driver installed and the graphic card supports OpenGL 4.6:\n\n\n- Open blender\n- Switch to the compositor workspace,\n- Enable backdrop\n- zoom in.\n\n", "Transparent Object intersecting shows artefacts in Render, but not in VP preview render\nOperating system: Win10\nGraphics card: GeForce980\n\n\nBroken: 2.93, 2.93, only in Cycles\nNote this was always visible, but there seems to be a change between 0f61b27e93 (where this was a lot less noticable) and then e14894aad2 (which already shows the current behavior).\n\n2 Objects imported from a CAD via .PLY, they intersect slightly. Gave one of them a fully transparent material, it shows up in render in the form of shadows (or dark reflections?) on the other one. Solving the intersection, disabling ray visibility for camera both solves this, but it still feels like a bug.\n\n\nOpen .blend, press render. Move up solid2_solid2, disable its ray visibility or use vp preview render for comparison.\nNormal Render (object is fully transparent)\n\nobject hidden for camera (still some artefacts)\n\nobject excluded from render - no artefacts\n\n\n[OverlapBug.blend](OverlapBug.blend)", "Render: Option to use fullscreen depthbuffer for tracing\nAdd an option to allow the use of a more precise depth buffer when doing screen space effects.\n\nThat may solve some issue regarding noise or self intersection.", "Black Artifacts While Using Adaptive Subdivision\n{[F7718097](bug.png)}Operating system: Windows-10-10.0.18362 64 Bits\nGraphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15\n\n\nBroken: version: 2.80 (sub 75)\n\n\nBlack artifacts on edges of geometry while using adaptive subdivision. I was trying to duplicate my workflow from other 3d software. Extruding geometry from 2d curves creates extra edges on the model. And extra edges create weird shadows on displacement.\n\nImport curve from dxf file. Use extrude Object Data > Geometry. Fill mode: Both. Use subdivision and displacement.\n\n[1.blend](1.blend)\n", "Bevel Modifier: Odd amount of segments causes UV propagation issues at seams\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 2.83, 3.4.0 Alpha\nWorked: unknown\n\nAny odd number of bevel segments greater than 1 fails to preserve seams in the propagated UV data on intersections. Instead UV data is interpolated, which can for example cause nasty artefacts when baking.\n[bug_bevel_uv_seams_interpolation-2022-09-01_15.26.11.mp4](bug_bevel_uv_seams_interpolation-2022-09-01_15.26.11.mp4)\n\nFile:\n[baking_artefacts.blend](baking_artefacts.blend)\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", "Flicker Volume Artifacts in EEVEE on RTX Cards by increasing samples\nOperating system: Windows-10-10.0.18362-SP0 64 Bits + Linux\nGraphics card: GeForce RTX 2060 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92\nIt seems to be only on RTX Cards\n\nBroken: version: 2.83 - 3.1 (Seems to be worse since 3.0)\n\nWierd colorful artifacts every frame in volume in rendered footage from EEVEE (Not in viewport)\nBloom makes out of this artifacts a big glowing colorfull mess. \nWithout bloom you can see little white artifacts random generated around in Volume (like in old Films)\nif you have less Objects in your Scene. less Artifacts are their (Video 2).\nWhen you increase the sample rate more artifacts show up. You can use a sample rate like 1000 and you have Disco.\n\nIt is in every big volume scene (this isnt the only scene where these artifacts are. All of my scenes ,that have volume in it, have these artifacts (with bloom on, you can realy see the lightflashes)\n\nBug Report from Nvidia:\n3233904\n\nBlend file:[Scene Volume Moinster.blend](Scene_Volume_Moinster.blend)\n\n**Video much Stones (100 samples) :** [Bug wierd flikkering40000-0150.mp4](Bug_wierd_flikkering40000-0150.mp4)\n\n\n**Video less Stones (100 samples) :** [Bug wierd flikkering50000-0150.mp4](Bug_wierd_flikkering50000-0150.mp4)\n\n**Video less Stones (1000 samples) :** [Bug wierd flikkering6 1000samples0000-0150.mp4](Bug_wierd_flikkering6_1000samples0000-0150.mp4)\n \n**Other Examples:** [S1 new Exp0800-0950.mp4](S1_new_Exp0800-0950.mp4)\nI hope you can find the Problem\nThank you for your Time to make Blender better.\n**Thank you very much**", "Exaggerated Ambient Occlusion Effect with Subsurface Scattering Materials in Cycles\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68\n\nBroken: version: 2.93.2\n\nWhen rendering with Cycles, whenever meshes with materials that have subsurface scattering intersect, a very obvious ambient occlusion effect is generated around the intersections. It functions as expected with Eevee, but in Cycles, there's always a very unattractive dark seam line.\n\nApply any subsurface scattering materials to any two intersecting meshes, and render out with Cycles.\n\nHere are my results, I used a procedural snow shader, but I get similar results with any subsurface scattering materials.\n[subsurface scattering.blend](subsurface_scattering.blend)\nResults with Subsurface Scattering in Cycles\n\nSame shader in Cycles with Subsurface scattering turned off\n\nSame shader in Eevee with baked indirect lighting and subsurface scattering turned on\n\n\n", "Denoiser creating artefacts\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\nGraphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14\n\nBroken: version: 2.83.0\nWorked: ー\n\nStrange artefacts are being created by the denoiser, firefly like bright and dark pixels where there were no such artefacts in the 'Noisy Image'. Looking into the 'Denoising Depth' pass reveals negated depth values around the artefacts. In the supplied .blend it seems to be caused by some weird interaction between the sun lamp and the water material with a black diffuse.\n\nDenoised Image: \nNoisy Image: \nDenoising Depth: \n(White values are ~90 black are ~-90)\n\nRender frames from supplied .blend\n[DenoiseBug.blend](DenoiseBug.blend)\n", "Decals crash Eevee on AMD graphics card\nOperating system: Linux 6.2.7 Manjaro \nGraphics card: AMD 7900XT\n\nBroken: 3.3LTS, 3.4.1\n\nUsing decals will crash blender in Eevee. cycles works\n\nas an example file please see the .blend that was linked here by the decalmachine creator: 66438\n\nThe issue there is unrelated but the file can serve to show the issue I am having. The moment I switch to rendered view or materials preview blender will crash. I see no error message in console. The log files states just: \n\n```\nbpy.context.space_data.shading.type = 'RENDERED' # Property\nbpy.context.space_data.context = 'RENDER' # Property\nbpy.context.scene.render.engine = 'BLENDER_EEVEE' # Property\n \n```\n\n" ]

[ "Eevee SSR quality regression in 2.91 alpha\nGraphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.66\n\nBroken: version: 2.91.0 Alpha\nWorked: 2.90\nBehavior changed in da741013a1\n\nScreen space reflections have visible banding noise pattern, especially noticable on high roughness materials that's not apparent in 2.90.\n\n\n\nOpen the added blend file in 2.90 and 2.91 and switch to rendered mode. \n\n[2.91_SSR.blend](2.91_SSR.blend)\n\n" ]

[ "Crash/Assert with two modifiers that require normals data [e.g. DataTransfer]\nOperating system: Windows-10-10.0.16299-SP0 64 Bits\nGraphics card: GeForce MX150/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.87\n\nBroken: version: 2.90.0\n\nCrash/Assert with two modifiers that require custom normals data [e.g. DataTransfer]\n\nIn a Debug build:\n\n[#84664.blend](T84664.blend)\n- Open File\n- add another modifier that requires normal data (e.g. Displace), or just duplicate the existing modifier\n\n[un2.blend](un2.blend)\n- Try to go to edit mode of \"Vert.011\"\n- Blender will crash.\n\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", "Cycles dupli object baking issues\nnvidia g880m\n\nBroken: blender-2.73-d56c9fb-win64\nWorked: (optional) probably never\n\nwhen assigning object as duplis to some mesh, and then trying to bake these duplis to another mesh, duplis appear black. But in normals mode, it works, so they are there, just without material or something.\nAlso, you can see that the duplis are there actually twice, one offset quite strongly. In some other file, I got them also four times...\n\n\n[bakebug.blend](bakebug.blend)\nopen the file, hit bake. \nthe group of objects in the ceter bakes to the cube.\n\nalso, you can see another group of objects, where duplis have been made \"real\" and it works well, it's group of objects called \"fine\", baking to the cube works well with seemingly same meshes.\n", "Click selecting a keyframe in the Dope Sheet deselects all channels\nOperating system: Linux Mint\nGraphics card: RTX 3070\n\nBroken: latest master\nWorked: checked until 2.93 and it still was broken\n\nWhen click selecting a keyframe on a summary channel in the Dopesheet (and the Timeline which is basically a Dopesheet),\nit deselects all channels.\nIf you drag select it, all channels of the keys are selected.\n\nClick selecting a keyframe that is not on a summary channel does select the channel as well.\n\nI would expect click and drag select to behave the same on summary channels.\n\nBased on the default startup or an attached .blend file (as simple as possible).\n\n* open the provided blend file (channels are already selected)\n* click select a keyframe on a summary channel in either the Timeline or the Dope Sheet\n* note the channels are all deselected\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)]", "Regression: Crash on deleting shape key from Blender File view.\nOperating system: macOS-13.5-x86_64-i386-64bit 64 Bits\nGraphics card: Metal API AMD Radeon Pro 575 1.2\n\nBroken: version: 4.0.0, 3.2\nWorked: 3.1\n\nCaused by a71a513def202b119328035dbd68e86c2c47f7ac\n\nOutliner on Blender File when delete cause crash guide.\n\n- Open attached file\n- Add shape key\n- Switch outliner to Blender file display mode\n- Expand Shape key\n- select `key` then delete it from context menu\n\nr2jrCca\n\nYoutube:\nOlegeJrBbmE\n\nMy Dropbox file:\nLola%20Bunny.zip?dl=0\n\n- - -\nFirst create new ticket I unable to paste picture this here.\nI did drag there 250MB and (Remove) cause appear <html><head></head><body></body><html> please fix without <html> k5RFuuy\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", "Entire system freezing while using NLA in Blender 2.91 and newer (Mesa only?)\nOperating system: Fedora 33\nGraphics card: Intel HD Graphics 520 (Mesa 20.2.4)\n\nBroken: 2.91\nWorked: 2.90.1\n\nBlender randomly freeze entire graphics system. After freezing, last 2 frames is flickering if you move mouse. I can even save my work with CTRL+S, but after that i need to restart my computer. Setting INTEL_DEBUG=reemit environment variable fixes the issue.\n\nMethod 1\nAdd a few keyframes.\nScroll up and down in the NLA editor.\n[blender-freeze-2.mp4](blender-freeze-2.mp4)\n\nMethod 2\n\nJust do something, even in Solid view, even in Video Sequence editor. I don't know how to reproduce, it happens after 10 minutes of work. Also i notice some glitches in VSE with image strips. Also bug with Depth of Field was fixed in this version, probably this fix relate to this bug.\n\nBug with depth of view that was fixed:\nT77828\n\nIssue with VSE\n[blender-vse-artifacts-1.webm](blender-vse-artifacts-1.webm)", "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", "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...", "Crash after executing the script\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: 3.6.1 Release Candidate\n\nApplication crashes when clicking on the script run button\n\n1/ launch Blender\n2/ click on \"Scripting\" tab; click \"New\"\n3/ paste the following chatgpt generated script and run it: \n```\nimport bpy\nfrom math import sqrt, sin, cos\n\n# Define the vertices of the tetrahedrons\nvertices1 = [\n (1, 1, 1),\n (-1, -1, 1),\n (-1, 1, -1),\n (1, -1, -1)\n]\n\nvertices2 = [\n (1, -1, -1),\n (-1, 1, -1),\n (-1, -1, 1),\n (1, 1, 1)\n]\n\n# Define the faces of the tetrahedrons\nfaces1 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\nfaces2 = [\n (0, 1, 2),\n (0, 2, 3),\n (0, 3, 1),\n (1, 3, 2)\n]\n\n# Create new meshes and objects\nmesh1 = bpy.data.meshes.new(\"Tetrahedron1\")\nobj1 = bpy.data.objects.new(\"Tetrahedron1\", mesh1)\n\nmesh2 = bpy.data.meshes.new(\"Tetrahedron2\")\nobj2 = bpy.data.objects.new(\"Tetrahedron2\", mesh2)\n\n# Set the object locations and scene context\nobj1.location = (-2, 0, 0)\nbpy.context.scene.collection.objects.link(obj1)\n\nobj2.location = (2, 0, 0)\nbpy.context.scene.collection.objects.link(obj2)\n\n# Create the vertices and faces of the meshes\nmesh1.from_pydata(vertices1, [], faces1)\nmesh1.update(calc_edges=True)\n\nmesh2.from_pydata(vertices2, [], faces2)\nmesh2.update(calc_edges=True)\n\n# Hinge the tetrahedrons together by one edge\nedge1 = mesh1.edges[0]\nedge2 = mesh2.edges[2]\n\nbpy.ops.object.select_all(action='DESELECT')\nobj1.select_set(True)\nobj2.select_set(True)\n\nbpy.context.view_layer.objects.active = obj2\nbpy.ops.object.mode_set(mode='EDIT')\nbpy.ops.mesh.select_all(action='DESELECT')\nedge2.select = True\nbpy.ops.mesh.edge_face_add()\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Add an armature to the tetrahedrons\nbpy.ops.object.armature_add()\narmature = bpy.context.object\narmature.name = \"HingeArmature\"\narmature.location = (0, 0, 0)\n\n# Add bones to the armature\nbpy.ops.object.mode_set(mode='EDIT')\nbone1 = armature.data.edit_bones.new('Bone1')\nbone1.head = (0, 0, 0)\nbone1.tail = (-2, 0, 0)\nbone1.use_deform = False\n\nbone2 = armature.data.edit_bones.new('Bone2')\nbone2.head = (0, 0, 0)\nbone2.tail = (2, 0, 0)\nbone2.use_deform = False\n\nbpy.ops.object.mode_set(mode='OBJECT')\n\n# Parent the tetrahedrons to the armature\nobj1.parent = armature\nobj1.parent_type = 'BONE'\nobj1.parent_bone = 'Bone1'\n\nobj2.parent = armature\nobj2.parent_type = 'BONE'\nobj2.parent_bone = 'Bone2'\n\n# Animate the hinge\nframes = 30\n\nfor frame in range(frames):\n bpy.context.scene.frame_set(frame)\n\n angle = frame / frames * 2 * 3.14159265\n\n bone1.tail = (-2 * cos(angle), 0, -2 * sin(angle))\n bone2.tail = (2 * cos(angle), 0, 2 * sin(angle))\n\n bone1.keyframe_insert(data_path='tail')\n bone2.keyframe_insert(data_path='tail')\n```", "ID Deduplication on Append - UX \nThis task is about which behavior should be default when linking/appending IDs, and assets, and how much/how users should be able to customize those behaviors.\n\nNOTE: Currently this is mostly listing topics to be discussed. This is also a first pass, there are likely many more use cases/topics to be discussed.\n\n# Problem\nCurrently, when appending a data-block, Blender appends (i.e. link and make local) the ID and all of its dependencies.\n\nThis means that if a single object in appended ten times, you will get ten copies of the object, but also of its meshes, materials, animations, etc.\n\nThis behavior may be fine in some cases, but not in others.\n\n# Default Behaviors\n## Generic Considerations\nTo avoid having many copies of the same ID, the first appended copy needs to be re-used for the subsequent appends.\n# Do we always re-use that ID, even if it has already been modified by the user locally?\n *Think first appended ID should always be re-used, reliably detecting modified IDs compared to linked one is possible, but tricky and not very efficient (RNA diffing)... There could be a mechanism though to break that reference such that next append creates a new copy of it.* **No diffing.** User has ways to make an existing local ID not re-usable anymore, and to force not re-using an ID when appending again. \n# ~~Could we use the UserPreferences settings for data copying, to decide which ID types we systematically create new copies for, and which ID types we try to re-use previously appended ID?~~\n\n## Specific Cases\nHere is a list of different use cases, possible behaviors being:\n* Link.\n* Append (Link + Make Local, aka new copy).\n* Re-use of previously appended local ID.\n\n### Append Material\n| Data type | DEFAULT | Alternative Behavior 1 |\n| --- | --- | --- |\n| Material itself: | re-use | *duplicate* |\n| Image: | NA | re-use |\n| Node groups: | NA | *duplicate* |\n| Actions: | NA | *duplicate* |\n\n### Append Object\n| Data type | DEFAULT | Alternative Behavior 1 |\n| --- | --- | --- |\n| Object itself: | *duplicate* | *duplicate* |\n| Obdata: | re-use | *duplicate* |\n| Actions: | re-use | *duplicate* |\n| Materials: | re-use | Apply Materials Rules ? |\n\n### Append Collection\n**Collection itself:*** In case of Empty-based instantiation:\n***In case of ViewLayer-based instantiation:** Object: *same as above for Object case?*\n\n# User Customization\n## Change behavior in UserSettings\nShould user be able to change default behavior in user settings, or only on a case-by-case basis when actually linking/appending IDs or assets?\n\n## Change Behavior in Asset/File browsers\nShould user be able to toggle options like \"Link everything\", or \"Never deduplicate\" ? etc.\n", "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", "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", "Graph Editor - Multiple Windows Problem\nOperating system: Windows 10 - 64\nGraphics card: Radeon RX 5500 XT\n\nBroken: 2.93.0\n\nI split my single Blender window to two Graph Editor/Node Editor & 3D Viewport for my multiple screens. If my mouse hovering anything but node editor(Include Graph editor or 3D Viewport) and I press play that timeline cursor like starts twitching.\n\nCreate two different windows. Graph Editor and 3D Viewport. Than press play on 3D Viewport window selected.\n\nTest file:\n[Bugfile.blend](Bugfile.blend)\n\nVideo:\n[2021-06-10 15-35-41.mp4](2021-06-10_15-35-41.mp4)" ]

[ "2.83: Unable to move, grab, or duplicate keyframes in any editor without a Crash \nOperating system: Linux, Win7, MacOS\n\n\nBroken: version: 2.83 (sub 0), branch: master, commit date: 2020-01-10 10:40, hash: befc082736\nWorked: c3d6929e4f\n\nMoving keyframes on any keyframe editors (DopeSheet, action, timeline or curve) crashes blender.\n\nJust keyframe default cube on the first frame and another for example on frame 20. In the timeline try to move the keyframes. The blender immediately closes... at least for me here...\nYou can try on \"animation\" workspace on the dopesheet editor and the crash will happen also.\nIn my tests, I was not able to move a keyframe on any editor...\n\n", "Crash inserting keyframes for shapekeys\nOperating system: Linux-4.19.91-1-MANJARO-x86_64-with-glibc2.29 64 Bits\nGraphics card: AMD VERDE (DRM 2.50.0, 4.19.91-1-MANJARO, LLVM 9.0.0) X.Org 4.5 (Core Profile) Mesa 19.2.7\n\nBroken: version: 2.83 (sub 0)\nWorked: 2.81a\n\nInserting keyframes for multiple shapekeys crashes blender 2.83\nIn the default scene, go to Object Data properties\ncreate 8 shapekeys with the plus button\ninsert keyframes for the value slider of each shapekey with the I key\nit will crash somewhere between inserting the 3rd and 7th keyframe" ]

[ "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)", "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", "Error baking particles in OSX\nOperating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GTX TITAN X OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.33.0 387.10.10.10.40.135\n\nBroken: version: 2.83.1\n\nI have two particle emisor and when I try to bake it crash.\nI try it in Linux and work perfectly!\n[TEST_ERROR.crash.txt](TEST_ERROR.crash.txt)\n\n[TEST_ERROR1.blend](TEST_ERROR1.blend)\n\n- Open file\n- Bake particles\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)", "Dynamic Paint With UNDO [Control Z] Crash Blender\nOperating system: Windows-7-6.1.7601-SP1 64 Bits\nGraphics card: GeForce GTX TITAN X/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.64\nBroken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)\nWorked: (optional)\n\nWhen Press Control Z While In Weight Paint (EDIT MODE), Blender Crash\n\nBased on the default startup or an attached .blend file (as simple as possible).\n[weight-paint-v1.blend](weight-paint-v1.blend)\n1. Open the provided .blend file\n2. Start playback and enter Weight Paint mode\n3. Paint and then undo (Control + Z)\n4. Blender crashes after a while,\n\nHere is video to show case KUUbxSnwmbE", "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)", "Crash after linked object is edited then switched to another scene (object origin scene)\nOperating system: Window10\nGraphics card:\n\n\nBroken: 2.90.1 ( hash: 3e85bb34d0d7 )\nWorked: unknown\n\n\nBlender simply crash and close the window directly after editing the \"linked\" object from 2nd screen and switched back to 1st screen.\n\n\n\nThis error can be reproduced with 2 scenes setup.\n\n- First scene contains a simple mesh object. Let's say a \"Cube\" object\n- Create a second scene.\n- In the first scene, select the \"Cube\" object then \"Make Links\" {key Ctrl L} to 2nd scene.\n- Now, we switch to 2nd scene. The 2nd scene now should contains the same \"linked\" Cube object from 1st scene.\n- Okay, this is important step. In this 2nd scene, we select this \"linked\" Cube object and set the Relations to: *Object > Relations > Make Single User > Object*\n- After that, we go to \"Edit Mode\" for this \"linked\" Cube object.\n- In \"Edit mode\", make a simple change to this \"linked\" Cube object.\n- Once simple change is done, don't do anything else. You just directly switch back to \"First scene\". CRASH here.\n\n", "Crash with Boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.13\n\nBroken: version: 3.4.0 Alpha\nWorked: 3.1.2 (appears to have been broken since 3.2.0)\n\nBlender crashes when performing an Intersection Boolean between a cube and a bunch of loose faces. (Granted, this is probably not something you should do in the first place, but at least it should be limited to producing a bad result, not a crash.)\n\nI didn't find a crash log, but it's easy to reproduce.\n\n* Load the attached .blend file.\n* Scrub the timeline to frame 209. Blender crashes.\n\n[crash.blend](crash.blend)\n", "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", "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)", "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", "Clicking \"Bake All Dynamics\" causing various crashes.\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 536.99\n\nBroken: version: 3.6.2\n\nUsing \"Bake All Dynamics\" is beyond finicky and crashes Blender in many different use cases. Many little \"tricks\" are needed to make it work. I am using Disk Cache for all below situations, but I believe the crashes happen with or without this.\n\nSituations where it crashes:\nClicking \"Bake All Dynamics\" within the Cloth cache settings. It seems it's required to click \"Bake All Dynamics\" button within the context of the Rigid Body system, or else it crashes instantly.\n\nClicking \"Bake All Dynamics\" in the context of hair dynamics seems to do nothing. Same goes for \"Update All to Frame\"\n\nIf a rigid body simulation has been baked, clicking \"Delete All Bakes\", then clicking \"Bake All Dynamics\" immediately will also crash blender. The only workaround for this is to \"move\" an object even if using a zero value, before clicking \"Bake All Dynamics\" again. This prevents the crash. \n\n\nCreate a Rigid Body Sim, create a Cloth Sim. Check \"Disk Cache\" as an option. Try the various methods listed above.\n\n", "Crashes when working with pose mode (rigidbodies involved)\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23\n\nBroken: version: 3.0.1\nWorked: 2.8\n\nFrequent random crashes.\n\nJust animate bones. It may even crash at undo. One day it's okay, another it crashes 20 times a day.\n[debug_logs.zip](debug_logs.zip)\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", "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" ]

[ "Switching between edit mode, and particle edit mode consistently crashes.\n- Windows 10 Home, 64bit-bit\n- Nvidia GTX 970 driver: 388.13\n\n2.8 alpha 2 efa3389b83e\n\nAfter grooming, switching from `particle edit mode` to `edit mode` causes blender to crash\n\n- open blend file\n- enter particle edit mode using tab menu\n- brush hair strands ( If this is not done the bug does not appear )\n- press tab a few times to toggle between particle edit mode and edit mode.\n- crash to desktop\n\n\nI get the following error from stderr\n```\nError : EXCEPTION_ACCESS_VIOLATION\nAddress : 0x00007FF6AC5470A8\nModule : C:\\Users\\robert\\Downloads\\blender-2.80.0-git.efa3389b83e-windows64\\blender.exe\n```\n\n[example.blend](example.blend)\n\n\nThanks :)\n", "Crash when quickly pressing tab in particle edit\nHardware:\n - CPU: Intel Core i7-7700\n - GPU: ASUS Nvidia GeForce GTX 1070 dual\n - RAM: HyperX Fury Black, DDR4 2400MHz (2x8GB)\n - No hardware overclocked\n\nSoftware:\n - Windows 10 1803 Home 64-Bit\n - Screen Resolution 2560x1440@144Hz (Gsync enabled)\n - Nvidia driver version: 416.34\n\nBroken: 2.80.0 b4dfe00fd60\n\nBlender should not crash when quickly switching to edit mode from particle edit mode. This bug works in all previous versions of blender 2.8 (well the ones I have used).\n\n - Create new blender project (keep cube)\n - Select Cube\n - Go to particle system tab on the right\n - Create new particle system\n - Set particle system as hair\n - On left side of window go to particle edit mode\n - Use \"comb\" tool to distort hairs\n - use middle mouse button to rotate view\n - Quickly press \"TAB\" several times to go to edit mode and back\n - Blender crashes\n" ]

[ "Cloning materials with too smart ShaderNodeCustomGroup breaks user counters of both source and target nodes\nOperating system: Linux-5.0.0-37-generic-x86_64-with-debian-buster-sid 64 Bits\nGraphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.56\n\nBroken: version: 2.82 (sub 4)\nWorked: (optional)\n\nSome of my shader nodes need to have separate node trees for each their copies.\n\nIt seems quite legal to do like this:\n```\n def copy(self, node):\n self.node_tree = bpy.data.node_groups.new('newtree', 'ShaderNodeTree')\n```\nWhen the material is cloned (via `ops.material.new`), it makes the original tree.users == 0, and new tree.users == 2\nSource node becomes zombie and dies after reloading or orphan cleaning.\nTarget node becomes undead and cannot die because of zero users.\n\n\n1. run attached script from command line: `blender --factory-startup --background --python test_op_mat_clone.py`\n2. observe output: all trees are expected to have 1 users\n\n[test_op_mat_clone.py](test_op_mat_clone.py)", "Material Preview (EEVEE) can cause access violations when switching to edit mode\nOperating system: Windows-10-10.0.19045-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.65\n\nBroken: version: 3.6.3\nWorked: N/A\n\nSwitching to edit mode with material preview (EEVEE) enabled results in a crash \n(Log from my machine produced with the joined blender file also joined to this report)\n\nusing the file joined in this report:\n- Open the scene\n- Select \"Circle.039\"\n- Switch to material preview\n- Attempt to enter edit mode on \"Circle.039\"\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", "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", "Custom properties without a name cannot be edited/deleted\nOperating system: macOS-12.0.1-x86_64-i386-64bit 64 Bits\nGraphics card: AMD Radeon Pro 560X OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.7.29\n\nBroken: version: 3.1.0 Alpha\nWorked: 2.93.6 Release Candidate\n\nA custom property without a name cannot be edited or deleted (gives an error), however in the worked version as stated above, the unnamed property can still be manipulated without triggering an error.\n\n1. In the default scene, create a new custom property for the cube and remove its name completely.\n\n2. Press OK\n3. Blender gives an error, as shown below:\n\n4. Dismiss the pop up and click on either the gear/cross icons:\n\n\n[unnamed_prop.blend](unnamed_prop.blend)\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.", "Shader Nodetree Error: Invalid implicit socket conversion: Shader -> Color\nOperating system: Windows-10-10.0.19044-SP0 64 Bits\nGraphics card: GeForce GTX 1660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.33\n\nBroken: version: 3.3.1\nWorked: I don't know but the problem is also present in the version 3.0.0\n\n\n```lang=glsl\nRead prefs: C:\\Users\\rfnei\\AppData\\Roaming\\Blender Foundation\\Blender\\3.3\\config\\userpref.blend\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(float_from_Closure(tmp34), node_tree.u36, tmp37);\n |\n | Error: C1503: undefined variable \"float_from_Closure\"\n\n\nShader Nodetree Error: Invalid implicit socket conversion\nERROR (gpu.shader): GPU_material_compile FragShader:\n |\n\n 7164 | invert(node_tree.u35, vec4_from_Closure(tmp34), tmp37);\n |\n | Error: C1503: undefined variable \"vec4_from_Closure\"\n\nShader Nodetree Error: Invalid implicit socket conversion\nShader Nodetree Error: Invalid implicit socket conversion\n```\n\n\n1. EEVEE render\n2. Shader editor: put some shader socket to color socket\n3. Check the console", "`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", "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)", "Select Interior Faces causes assertion failure with zero-area faces in certain situations\nOperating system: Windows-10-10.0.19041-SP0 64 Bits\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-06-23 17:19 , hash: `8f4d991594`\nWorked: Unsure\n\nA specific mesh, which includes a zero-area face, causes an assertion failure when running the *Select All By Trait > Interior Faces* operator\n\n1. Open the attached .blend file\n2. In edit mode, hit F3, type \"select interior faces\", hit enter\n3. Assertion failure\n\n[interior-face-assert.blend](interior-face-assert.blend)\n\nThe bug appears to be benign outside of debug mode.\n\nThe assertion is:\n\n`BLI_assert failed: D:\\blender-git\\blender\\source\\blender\\editors\\mesh\\editmesh_select.c:2944, EDBM_select_interior_faces(), at '-BLI_heap_node_value(node_min) >= cost'`\n\nBoth `-BLI_heap_node_value(node_min)` and `cost` are NaN (I just stuck in a `printf`).\n\nThe exact positioning of of the edges, save for those around the zero-area face, seems to be irrelevant. I can't recreate the problematic mesh by hand, however.\n\n\n\nI believe this is a minimal example: I can't delete any more faces without the problem going away.\n\nStack trace: [P2206](P2206.txt)", "Erratic behaviour of materials/material slots for text objects\nOperating system: Linux-5.19.0-45-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: NVIDIA GeForce GTX 980M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 510.108.03\n\nBroken: version: 3.6.0\n\nMaterial assignment for text objects doesn't behave as expected. Removing an unused material slot will cause changes to the materials used by the object. The same happens if you rearrange the material slots.\n\n1. Add a new text object. Leave the default string \"Text\".\n2. Add 3 new material slots with different materials to the object. Use different viewport display colors to be able to see changes.\n(You will now have Material.001, Material.002 and Material.003)\n3. In edit mode, select the last two letters and assign Material.002.\n(You should now have \"Te\" using Material.001 and \"xt\" using Material.002)\n4. In object mode, remove the last material slot containing Material.003.\n(This material was not assigned to any character, and removing it should not cause any change.)\n5. All 4 letters are now using Material.001. \"xt\" should still be using Material.002.\n\nAlternatively, execute step 1-3 above and then.\n4. Move the last material slot up to the first place.\n(This should not cause any change. Normally in blender, the materials used by the geometry will not change if you rearrange the material slots.)\n5. You will now have \"Te\" using Material.004 and \"xt\" using Material.002. \"Te\" should still be using Material.001.\n\nI have attached a blend file where you just need to remove the last (unused) material slot to see the problem, or move the last material slot up to first position.\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", "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", "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", "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)" ]

[ "Node editor: Assert on changing node values ntreeFromID(ntree->owner_id) == ntree\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 496.49\n\nBroken: version: 3.4.0 Alpha\n\nassert hit when changing any value of newly added nodetree: `BLI_assert failed: node_owner_pointer_get(), at 'ntreeFromID(ntree->owner_id) == ntree'`\n\n**Playback Steps**\n- Open default scene\n- Switch to shading workspace -> delete default material node tree\n- Add new node tree\n- Change any property\n\n[2022-10-01 16-59-32.mp4](2022-10-01_16-59-32.mp4)\n\n```lines=10\nVendor: NVIDIA Corporation\nRenderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2\nVersion: 4.5.0 NVIDIA 496.49\nContext Version: 4.5\nVendor: NVIDIA Corporation\nRenderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2\nVersion: 4.5.0 NVIDIA 496.49\nContext Version: 4.5\nStack trace:\nblender.exe :0x00007FF6F6310E60 bli_windows_system_backtrace_stack_thread F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:219\nblender.exe :0x00007FF6F630FF60 BLI_windows_system_backtrace_stack F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:306\nblender.exe :0x00007FF6F630F960 BLI_system_backtrace F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\system_win32.c:372\nblender.exe :0x00007FF6F63156C0 _BLI_assert_print_backtrace F:\\Blender_build\\first\\blender\\source\\blender\\blenlib\\intern\\BLI_assert.c:36\nblender.exe :0x00007FF6E8F24370 node_owner_pointer_get F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\node.cc:417\nblender.exe :0x00007FF6E96578C0 BKE_id_owner_get F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\lib_id.c:1972\nblender.exe :0x00007FF6EA9893D0 RNA_find_real_ID_and_path F:\\Blender_build\\first\\blender\\source\\blender\\makesrna\\intern\\rna_path.cc:943\nblender.exe :0x00007FF6EA98A370 RNA_path_full_ID_py F:\\Blender_build\\first\\blender\\source\\blender\\makesrna\\intern\\rna_path.cc:1184\nblender.exe :0x00007FF6EA98A6A0 RNA_path_full_property_py_ex F:\\Blender_build\\first\\blender\\source\\blender\\makesrna\\intern\\rna_path.cc:1261\nblender.exe :0x00007FF6EA98A630 RNA_path_full_property_py F:\\Blender_build\\first\\blender\\source\\blender\\makesrna\\intern\\rna_path.cc:1297\nblender.exe :0x00007FF6EA03B640 WM_prop_pystring_assign F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_operators.c:642\nblender.exe :0x00007FF6EC16F090 ui_apply_but_autokey F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:983\nblender.exe :0x00007FF6EC169280 button_activate_exit F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:8567\nblender.exe :0x00007FF6EC182DB0 ui_handle_button_event F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:9345\nblender.exe :0x00007FF6EC187A10 ui_handler_region_menu F:\\Blender_build\\first\\blender\\source\\blender\\editors\\interface\\interface_handlers.c:11388\nblender.exe :0x00007FF6EA025B20 wm_handler_ui_call F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:786\nblender.exe :0x00007FF6EA0279A0 wm_handlers_do_intern F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3217\nblender.exe :0x00007FF6EA025EB0 wm_handlers_do F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3334\nblender.exe :0x00007FF6EA0330B0 wm_event_do_handlers F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm_event_system.cc:3925\nblender.exe :0x00007FF6E9FFB190 WM_main F:\\Blender_build\\first\\blender\\source\\blender\\windowmanager\\intern\\wm.c:643\nblender.exe :0x00007FF6E706E5F0 main F:\\Blender_build\\first\\blender\\source\\creator\\creator.c:579\nblender.exe :0x00007FF6F69626A0 invoke_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:79\nblender.exe :0x00007FF6F6962490 __scrt_common_main_seh d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:288\nblender.exe :0x00007FF6F6962470 __scrt_common_main d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_common.inl:331\nblender.exe :0x00007FF6F6962760 mainCRTStartup d:\\a01\\_work\\20\\s\\src\\vctools\\crt\\vcstartup\\src\\startup\\exe_main.cpp:17\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThreads:\nThread : 00004f60\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 000049b4\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004acc\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001634\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004c78\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004e2c\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00002dfc\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00000894\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00000728\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003138\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00000a14\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004d98\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004b88\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001e78\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003d40\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003ae4\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nblender.exe :0x00007FF6F89B30F0 IlmThread_3_1::Semaphore::wait\nblender.exe :0x00007FF6F89B2390 IlmThread_3_1::TaskGroup::Data::removeTask\nblender.exe :0x00007FF6F89B31F0 std::thread::_Invoke<std::tuple<void (__cdecl IlmThread_3_1::Thread::*)(void) __ptr64,IlmThread_3_1\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 0000515c\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 0000528c\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001654\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001510\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001620\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 0000517c\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00000d04\nntdll.dll :0x00007FFB90CF0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFB90CA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003694\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nnvoglv64.dll :0x00007FFB23BB1C00 DrvValidateVersion\nnvoglv64.dll :0x00007FFB2393F73C Symbols not available\n\n\nThread : 00002758\nntdll.dll :0x00007FFB90CEDA80 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFB8E50CAD0 WaitForMultipleObjectsEx\nKERNELBASE.dll :0x00007FFB8E50CAB0 WaitForMultipleObjects\nnvoglv64.dll :0x00007FFB23BE7770 DrvPresentBuffers\nnvoglv64.dll :0x00007FFB23BE7770 DrvPresentBuffers\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004404\nwin32u.dll :0x00007FFB8E3EA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFB905306F0 MsgWaitForMultipleObjectsEx\nnvoglv64.dll :0x00007FFB23BB1C00 DrvValidateVersion\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003458\nntdll.dll :0x00007FFB90CF0980 ZwWaitForWorkViaWorkerFactory\nntdll.dll :0x00007FFB90CA2680 TpReleaseCleanupGroupMembers\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 000038a8\nntdll.dll :0x00007FFB90CEDA80 ZwWaitForMultipleObjects\nKERNELBASE.dll :0x00007FFB8E50CAD0 WaitForMultipleObjectsEx\ncombase.dll :0x00007FFB9012A260 CoRevokeInitializeSpy\ncombase.dll :0x00007FFB9012A260 CoRevokeInitializeSpy\ncombase.dll :0x00007FFB9012A260 CoRevokeInitializeSpy\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00002c48\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\nWintab32.dll :0x00007FFB5ED62050 hn_wintab_OnTimeout\nWintab32.dll :0x00007FFB5ED62050 hn_wintab_OnTimeout\nWintab32.dll :0x00007FFB5ED62050 hn_wintab_OnTimeout\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00001bc0\nwin32u.dll :0x00007FFB8E3EA0F0 NtUserMsgWaitForMultipleObjectsEx\nUSER32.dll :0x00007FFB905306F0 MsgWaitForMultipleObjectsEx\ndirectmanipulation.dll:0x00007FFB727A458B Symbols not available\n\n\nThread : 000044a0\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 000007a8\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00003a60\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00002100\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004790\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00000678\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 00004c88\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 000011d8\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nThread : 000036a0\nntdll.dll :0x00007FFB90CECFB0 NtWaitForSingleObject\nKERNELBASE.dll :0x00007FFB8E4E1A40 WaitForSingleObjectEx\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\ntbb_debug.dll :0x00007FFB5F462176 tbb::spin_rw_mutex_v3::internal_release_writer\nucrtbased.dll :0x00007FFB568C4B90 register_onexit_function\nKERNEL32.DLL :0x00007FFB8FFD7020 BaseThreadInitThunk\nntdll.dll :0x00007FFB90CA2630 RtlUserThreadStart\n\n\nLoaded Modules :\n0x00007FF6DD760000 3.4.0.0 blender.exe F:\\Blender_build\\first\\ninja_build_debug\\source\\creator\\Debug\\blender_private.pdb\n0x00007FFB90C50000 10.0.19041.1806 ntdll.dll\n0x00007FFB8FFC0000 10.0.19041.1806 KERNEL32.DLL\n0x00007FFB8E4C0000 10.0.19041.1826 KERNELBASE.dll\n0x00007FFB90080000 10.0.19041.546 WS2_32.dll\n0x00007FFB8F480000 10.0.19041.1806 RPCRT4.dll\n0x00007FFB5F460000 tbb_debug.dll\n0x00007FFB90510000 10.0.19041.1503 USER32.dll\n0x00007FFB8E3E0000 10.0.19041.1826 win32u.dll\n0x00007FFB90940000 10.0.19041.1620 GDI32.dll\n0x00007FFB8E890000 10.0.19041.1706 gdi32full.dll\n0x00007FFB8E340000 10.0.19041.789 msvcp_win.dll\n0x00007FFB8E790000 10.0.19041.789 ucrtbase.dll\n0x00007FFB90A80000 10.0.19041.1682 ADVAPI32.dll\n0x00007FFB75E00000 14.30.30708.0 VCRUNTIME140_1D.dll\n0x00007FFB63090000 14.30.30708.0 VCRUNTIME140D.dll\n0x00007FFB585C0000 14.30.30708.0 MSVCP140D.dll\n0x00007FFB8EDC0000 7.0.19041.546 msvcrt.dll\n0x00007FFB90840000 10.0.19041.1586 sechost.dll\n0x00007FFB8F7A0000 10.0.19041.1806 SHELL32.dll\n0x00007FFB56850000 10.0.19041.685 ucrtbased.dll\n0x00007FFB908E0000 10.0.19041.1706 SHLWAPI.dll\n0x00007FFB8EC50000 10.0.19041.1023 bcrypt.dll\n0x00007FFB82690000 10.0.19041.867 dbghelp.dll\n0x00007FFB8F670000 10.0.19041.1202 ole32.dll\n0x00007FFB900F0000 10.0.19041.1741 combase.dll\n0x00007FFB557F0000 epoxy-0.dll\n0x00007FFB90830000 10.0.19041.546 PSAPI.DLL\n0x00007FFB90B30000 10.0.19041.1741 shcore.dll\n0x00007FFB90450000 10.0.19041.546 IMM32.dll\n0x00007FFB4DC10000 59.16.100.0 avformat-59.dll\n0x00007FFB26C50000 59.18.100.0 avcodec-59.dll\n0x00007FFB8FEF0000 10.0.19041.985 OLEAUT32.dll\n0x00007FFB29150000 9.0.0.0 openvdb_d.dll\n0x00007FFB63060000 59.4.100.0 avdevice-59.dll\n0x00007FFB52EF0000 57.17.100.0 avutil-57.dll\n0x00007FFB5C2C0000 6.4.100.0 swscale-6.dll\n0x0000000070440000 1.0.28.0 libsndfile-1.dll\n0x000000006ACC0000 libgmp-10.dll\n0x00007FFB4E3D0000 1.21.1.0 OpenAL32.dll\n0x00007FFB66F10000 libgmpxx_d.dll\n0x00007FFB4D830000 2.0.20.0 SDL2.dll\n0x00007FFB8EE60000 10.0.19041.1741 SETUPAPI.dll\n0x00007FFB7A730000 10.0.19041.1503 dbgeng.dll\n0x00007FFB8E9A0000 10.0.19041.1620 cfgmgr32.dll\n0x00007FFB61870000 10.0.19041.1 AVIFIL32.dll\n0x00007FFB84750000 6.10.19041.1110 COMCTL32.dll\n0x00007FFB87580000 10.0.19041.546 VERSION.dll\n0x00007FFB4CDF0000 3.10.2150.1013 python310_d.dll\n0x00007FFB63360000 14.30.30708.0 VCRUNTIME140.dll\n0x00007FFB8BF30000 10.0.19041.746 dwmapi.dll\n0x00007FFB7C370000 10.0.19041.546 Secur32.dll\n0x0000000070680000 libfftw3-3.dll\n0x00007FFB60330000 4.3.100.0 swresample-4.dll\n0x00007FFB6CB00000 10.0.19041.1 AVICAP32.dll\n0x00007FFB84720000 10.0.19041.546 WINMM.dll\n0x00007FFB75DB0000 14.30.30708.0 VCRUNTIME140_1.dll\n0x00007FFB5BB70000 14.30.30708.0 MSVCP140.dll\n0x00007FFB83B30000 10.0.19041.1503 dbgmodel.dll\n0x00007FFB68460000 10.0.19041.1 MSVFW32.dll\n0x00007FFB89BB0000 10.0.19041.546 XmlLite.dll\n0x00007FFB6A310000 10.0.19041.1 MSACM32.dll\n0x00007FFB8E1C0000 10.0.19041.1586 SSPICLI.DLL\n0x00007FFB81B10000 10.0.19041.1 winmmbase.dll\n0x00007FFB5E400000 tbbmalloc_debug.dll\n0x00007FFB8C220000 10.0.19041.546 kernel.appcore.dll\n0x00007FFB8C420000 10.0.19041.1806 windows.storage.dll\n0x00007FFB8DBF0000 10.0.19041.1806 Wldp.dll\n0x00007FFB8BCC0000 10.0.19041.1620 uxtheme.dll\n0x00007FFB8E9F0000 10.0.19041.1415 bcryptPrimitives.dll\n0x00007FFB8E210000 10.0.19041.844 profapi.dll\n0x00007FFB8F5B0000 2001.12.10941.16384 clbcatq.dll\n0x00007FFB88C60000 10.0.19041.1503 MMDevApi.dll\n0x00007FFB8E080000 10.0.19041.1620 DEVOBJ.dll\n0x00007FFB88CF0000 10.0.19041.1741 AUDIOSES.DLL\n0x00007FFB8E250000 10.0.19041.546 powrprof.dll\n0x00007FFB8E230000 UMPDC.dll\n0x00007FFB90710000 10.0.19041.1806 MSCTF.dll\n0x00007FFB4DAE0000 10.0.19041.1806 OPENGL32.DLL\n0x00007FFB5EFC0000 10.0.19041.1806 GLU32.dll\n0x00007FFB88F50000 10.0.19041.1620 AppXDeploymentClient.dll\n0x00007FFB22E80000 30.0.14.9649 nvoglv64.dll\n0x00007FFB8A030000 10.0.19041.546 WTSAPI32.dll\n0x00007FFB8DB60000 10.0.19041.546 CRYPTBASE.DLL\n0x00007FFB8DF80000 10.0.19041.546 msasn1.dll\n0x00007FFB87740000 10.0.19041.906 cryptnet.dll\n0x00007FFB8EAF0000 10.0.19041.1320 CRYPT32.dll\n0x00007FFB85FD0000 10.0.19041.1566 drvstore.dll\n0x00007FFB8EA80000 10.0.19041.1806 WINTRUST.dll\n0x00007FFB8D000000 10.0.19041.546 ntmarta.dll\n0x00007FFB878A0000 10.0.19041.546 dxcore.dll\n0x00007FFB8E020000 10.0.19041.546 WINSTA.dll\n0x00007FFB7B960000 10.0.19041.1387 dataexchange.dll\n0x00007FFB8AF80000 10.0.19041.1741 dcomp.dll\n0x00007FFB8A750000 10.0.19041.1741 d3d11.dll\n0x00007FFB8CC00000 10.0.19041.1806 dxgi.dll\n0x00007FFB885C0000 10.0.19041.1806 twinapi.appcore.dll\n0x00007FFB82BA0000 10.0.19041.1806 textinputframework.dll\n0x00007FFB8B930000 10.0.19041.746 CoreMessaging.dll\n0x00007FFB8B250000 10.0.19041.546 CoreUIComponents.dll\n0x00007FFB8A190000 10.0.19041.1682 wintypes.dll\n0x00007FFB81AA0000 7.2.19041.746 Oleacc.dll\n0x00007FFB5ED60000 1.0.0.1 Wintab32.dll\n0x00007FFB6B370000 10.0.19041.1023 explorerframe.dll\n0x00007FFB72790000 10.0.19041.1566 directmanipulation.dll\n0x00007FFB8DF30000 10.0.19041.546 CRYPTSP.dll\n0x00007FFB8D370000 10.0.19041.1052 rsaenh.dll\nBLI_assert failed: F:\\Blender_build\\first\\blender\\source\\blender\\blenkernel\\intern\\node.cc:417, node_owner_pointer_get(), at 'ntreeFromID(ntree->owner_id) == ntree'\n```" ]

[ "Particle edit select linked not working from menus\nOperating system: Windows-7-6.1.7601-SP1 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)\n\n\nHi, I noticed that the select linked option in hair \"Particle edit\" mode/Select/ select linked doesn't work\n\nPlease open the file press W then select linked\n\nthankyou\n\n[hair.blend](hair.blend)\n\n\n", "Bevel Vertex selection stops after for planar geometry\nOperating system: Windows 10\nGraphics card: NVIDIA Geforce GTX 1060 3 GB\n\n2.83.2\nBevel Vertex does not maintain the selection for planar objects. For other objects the selection is transferred onto the verts created from the Bevel.\n\nCreate a plane, circle, or any planar object/ \nIn edit mode, Bevel any amount of vertices (ctrl+shift+B) on a plane, circle, or any other type of planar geometry and try to bevel any number of the corners.", "Grease Pencil vertex paint select is using sculpt mode selection mode\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\nWhen selecting with mouse clicks the selection mode in the header determines which component is selected.\nIn Grease Pencil sculpt mode this behaves as expected. If it's set to \"points\", selecting will select points. If it's set to \"stroke\" it will select entire strokes.\n\nWhen switching to vertex paint mode this is not the case. Instead it will select components based on the selection mode that is set in sculpt mode.\n\nThe ideal behavior imo would be to have all grease pencil modes share the active selection mode.\nThis makes it easier to manage and simpler to use.\n\n- Change the keymap preferences to right click select (Selection shortcuts in left click select are partially broken atm)\n- Add a Gpencil Monkey\n- Switch to Sculpt Mode\n- Enable point selection mode\n- Select some points with `RMB` and `Shift RMB`\n- Switch to Vertex Paint mode\n- Make sure to use stroke selection mode\n- Select some strokes with `RMB` and `Shift RMB` (Notice how it will instead select points)\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)", "Edit-Mesh \"Select Next Active\" doesn't handle a wire edge loop (vertex mode)\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 works with loop ,that surrounden by others, but can`t deal with single circle, when I am trying to select one per one.\nPlease watch video:\n[2020-01-17_19-06-34.mp4](2020-01-17_19-06-34.mp4)\n\n[untitled.blend](untitled.blend)", "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", "bpy.ops.object.vertex_weight_copy() fails in multi edit mode\nOperating system: windows 10 amd ryzen 9 5950x 2 x 3090 (not in nvlink)\nGraphics card:\n\nBroken: 3.12\nWorked: don't think it ever has\n\nin multi edit copy vertex to selected fails and does not create new groups or copy the weights, you have to join the mesh first then do copy to selected then separate the mesh again which is problematic in more complex rigging scenarios with shape keys etc. \n\nincluded example blend file with both meshes selected tab into edit mode highlight 1 vertex on the cylinder and then select all the verts on the ico sphere and select copy, the copy fails. If you join the ico sphere to the cylinder mesh and do the same it works as expected.\n\ngoing to write a script as a workaround but I think it's really a bug ? (all be it a small one :-) )\n\n\n[copyfail.blend](copyfail.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", "Solidify cause wrong vertex selection in edit mode\nLinux-4.19.0-12-amd64-x86_64-with-debian-10.6 64 Bits\nMesa DRI Intel(R) UHD Graphics 630 (Coffeelake 3x8 GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 18.3.6\n\nWindows 10-10.0.19041 SP0 64Bit\nGeForce 9600 GT PCIe SSE2 Nvidia Corporation\nRadeon RX550/550 Series ATI Technologies Inc. 4.5.14736 Core Profile Context 20.8.3 27.20.12027.1001\n\nBroken: version: 2.80 (sub 75)\nBroken: version: 2.83.2\nBroken: version: 2.90.1\nBroken: version: 2.91.0 Beta\nWorked: unknown\n\nIn 3d viewport, vertex selection, solid mode, X-Ray off, you cannot predict what you are selecting when using solidify:\nBlender is ignoring the X-Ray (\"Allow selecting through the items\") and is selecting, randomly, occluded items.\nHaving a very narrow clipping does not mitigate the issue.\n\nExplanation video [SelectLight.mp4](SelectLight.mp4)\n\n[#82182.blend](T82182.blend)\n\n- Open file\n- Click inside blue circle\nOccluded vertex will be selected\n", "Transform cursor (patch included)\nRecently LMB-Drag was made to move the cursor *(edit, this has since been reverted)*.\n\nHowever this just moves the cursor under the mouse,\n\nit _could_ be useful to use transform here, it allows.\n\n- Drag, XKey to lock to an axis\n- ... Shift+Y to constrain to a plane.\n- ... Hold Ctrl to snap (snap to verts for example is handy)\n- ... Shift for more precise placement...\n... most other transform keys.\n\n\nOne reservation I have about this, is that you probably would often want to be able to snap to vertices and edges, and not have to depend on the current snap options in the 3d view header.\n\nSo we could override the snap options that transform uses.... but this seems a bit crappy too, since you may want to snap to faces in some cases, or even snap to grid.\n\nAs an alternative, we could just not bother attempting to integrate this with transform, and add snapping to the current modal operator (similar to how we have with the Ruler operator, which shares low level code with transform snapping)\nBut in that case we miss the axis constraints which seem like they would be nice to support.\n\n\nHere is a test patch to show how it works: [P87](P87.txt)\nNote, it crashes if you try to scale and its hard coded to LMB for cursor place, so its mostly a proof of concept.", "Outliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\nOperating system: Windows-10-10.0.18362-SP0 64 Bits\nGraphics card: GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 451.48\n\nBroken: version: 2.83.5, 2.90, 2.91 ce0bcd5fb\nWorked: Never (2.79 has the same problem)\n\nOutliner (Data API mode) crash trying to display a MeshSkinVertex in editmode\n\n[T79961_repro.blend](T79961_repro.blend)\n- Open file\n- Cube should be in editmode\n- In the Outliner (should be in Data API mode):\n - navigate to Meshes > Cube > Skin Vertices > expand the dot as well\n - crash", "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", "Rigid body doesn't work when collision is set to mesh, deform and deforming\nOperating system: Windows-10-10.0.19042-SP0 64 Bits\nGraphics card: Radeon RX Vega M GH Graphics ATI Technologies Inc. 4.5.14761 Core Profile Context 21.30.37.04 30.0.13037.4001\n\nBroken: version: 3.2.1\n\nThe rigid body simulation doesn't work with objects using collision with mesh, deform and deforming.\n\n* Make a plane, subdivided\n* Give it a wave modifier\n* Set up the rigid body type: dynamic, active, animated; collision: mesh, deform and deforming.\n* Use another object make it rigid body active\n* Run simulation\n* Sometimes works and when changing rigid body substeps per frame doesn't work at all (well sometimes works but when it does things jump out of control not like in Blender 2.79)\n\nIn Blender 2.79 works perfectly\n\n\n[Wave simulation 3.2.blend](Wave_simulation_3.2.blend)\n\n[Wave simulation 2.79.blend](Wave_simulation_2.79.blend)\n\nBlender 3.2\n\n\n\nBlender 2.79\n\n\n", "Snapping to vertex for Rotation doesnt work for Empty and Pivot Point\nBroken: 2.92, 3.1.2\nWorked: -\n\nSnapping with Rotation enabled doesnt work for Empty and Pivot Point (In Affect Only Origin mode)\nIn attached file,\ncube was properly aligned during rotation with snapping to vertex on the plane (marked)\nbut rotation of Empty produce unexpected results\n\nPlace any type of Emply object or try to edit Pivot Point and rotate it with snapping to certain object vertex to match rotation. Rotation will always produce unexpected results.\n\nVideo demonstration: watch?v=zB9ElkiEG7U\n\n[snapping_issue_T99279.blend](snapping_issue_T99279.blend)", "Lattices don't display selected vertices with modifier \"Edit Mode\" enabled\nSince 2.8x, lattices have not been displaying selected vertices when the modifier option \"Edit Mode\" id enabled.\n\nThis is easy to test:\n\n- add a new lattice object\n- add a wave deform modifier.\n- enter edit-mode.\n- enable \"Edit Mode\" toggle for the modifier.\n\nThis test file shows the problem too, open it and toggle the \"Edit Mode\" modifier button.\n\n[#77184.blend](T77184.blend)\n\n----\n\nReporting this to keep track of the issue: `BKE_lattice_modifiers_calc` is making a copy of the lattice `lt_eval` which doesn't contain an edit-lattice, which is then used for drawing." ]

[ "Vertex Slide crippled functionality\n\nSystem: Mac OS X 10.6.8 (10K549)\nGraphics card: ATI Radeon HD 5670\n\n\n\nBroken: Blender 2.70 Test build 1 (v2.69.11)\nDate: 2014-02-20 - 20.05:32\nHash: 4789793\n\nWorks: Blender 2.69.0 v60991 (The Official Release) Oct 31, 2013\n\n\n\nThe Vertex Slide functionality (called from menu, or GG, or Shift V) will slide vertex along one edge only (or the extension of one edge) from its original position.\n\n\n\nOpen the attached .blend{[F78474](Vertex_Slide_Bug_Or_Feature.blend)} file (Vertex Slide Bug or Feature). Slide the selected vertex along positive Y axis.\nThen try to slide the vertex along negative X axis or negative Z axis *without entering the Vertex Slide command again.* The sliding vertex is stuck at the original junction, and will not move along any other axes than the initial one (or the extension of it by unclamping).\n\nIn the official Blender 2.69.0 release the vertex can be freely moved along any connected edge without having to call the Vertex Slide command several times.", "GG is broken\nGuys, hitting GG while in edit mode use to lock a vertex to a selected/pointed to edge, and user was free to change that selection at any point. Now it seems that the choice of the edge to follow have to be made upfront and if I change my mind I have to do all the procedure all over again. This is not as good as it was in previous versions. More work for the same result.\n\nOperating system and graphics card\n\nBroken: (example: 2.69.7 4b206af, see splash screen)\nWorked: (optional)\n\n\nBased on a (as simple as possible) attached .blend file with minimum amount of steps\n" ]

[ "Geometry Nodes: Store Named Attribute does not propagate existing data when the domain changes\nOperating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits, X11 UI\nGraphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07\n\nBroken: version: 3.6.0 Beta\nWorked: Never.\n\nWhen using `Store Named Attribute` using a selection to store data on a subset of the geometry, the remaining elements keep their data that is already stored in that attribute. Because the name space of all attributes is shared, regardless of the domain, storing under the same name on a different domain will overwrite the attribute data. However, this will not implicitly propagate the existing attribute data for elements outside of the selection. That would be the expected behavior, as without a change of domain this is what happens and implicit domain conversions happen regularly in geometry nodes as necessary.\n\n| On a top face | On bottom vertex |\n| -- | -- |\n|  |  |\n\n[store_attribute_propagation.blend](attachment)\n\n", "Bone drivers do not copy when duplicated\nMac OSX 10.9.5 and NVIDIA GeForce GTX 470\n\nBroken: 2.77 (sub 3)\nWorked: ?\n\nIf a bone has any driver (on constraint or property) and it is duplicated (shift D in edit mode or \"symmetrize\") the drivers are not copied.\n\nBone constraints, however, copy perfectly and also try to find the correct .L or .R target if applicable.\nThis would save a lot of time if the drivers worked in the same way.\n", "Meshes that are generated with the screw modifier cant use the box projection type\nOperating system:\nGraphics card:\n\nBroken: 83f9218801d4\n\nThe meshes that are modified or extended by the screw modifier can't use the box projection of an image map. All the objects in the screenshot use the same material and the texture projection. As you can see the box and the plane has no problem with the projection type.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nLoad the attached .blend\n\nEnable the material preview and check the object named \"Screw\"\n\nCtrl-A -> \"visual geometry to mesh\" to see that the texture would normally work on the mesh, except ehwn the modifier is enabled.\n\n[_23012023_1655_00.zip](_23012023_1655_00.zip)", "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.", "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.", "Multires the Apply Base add to Quick Favorites can't change mesh.\nOperating system:Windows-10-2004 64 Bits\nGraphics card:GeForce RTX 2080 Ti/NVIDIA 462.59\n\nBroken: version: 3.0.0 Alpha, branch: master, commit date: 2021-07-21 18:41, hash: 64bb49fa4e3c, type: release\n\nMultires the Apply Base add to Quick Favorites can't change mesh.\n[0000-2931.mp4](0000-2931.mp4)\n\n\n- Add multires to cube, subdivide few times\n- Go to sculpt mode, sculpt mes a bit\n- Add Apply Base to Quick Favourites\n- Use Apply Base invoked from Quick Favourites\n\nOperator doesn't work this way", "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.", "Freestyle - marked freestyle edges do not work on objects with the boolean modifier\nOperating system: Windows-10-10.0.19043-SP0 64 Bits\nGraphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94\n\nBroken: version: 3.3.0\nWorked: Unknown\n\nEdges marked as freestyle do not work on objects with the boolean modifier\n\n\n1. Create cube object, add some edge loops and mark any edge as **\"Freestyle Edge\"**2. Create a second cube, and use it as a \"cutter\" using the**\"Boolean\"** modifier\n3. Activate **\"Freestyle\"**and check the**\"Edge Markt\"** in the \"Line Set\" area\n4. Make a render - the edge marked as **\"Freestyle Edge\"** will not be visible\n\n\nFile in attachment.\nThank you\n\n[Boolean Freestyle bug.blend](Boolean_Freestyle_bug.blend)\n\n", "Formalize Default Selection Behavior and Key-map\nSelection should behave as consistent as possible throughout Blender. There should be a formal description for that to help avoiding inconsistencies.\n\nNOTE: This task is WIP, all content is tentative.\n\nWe *may* have to draw distinctions between right-click vs. left-click and 2D vs. 3D editors. For the latter, there are rather different requirements.\n\n### 2D Editors\n\n| Key-map item | Action\n| ---------------- | --------\n| {key Click} | Select item (and activate) an item. Deselect others.\n| {key Shift Click} | Toggle selection (and activate):\n| | * Select (and activate) if item was *not* selected\n| | * (Activate it item was selected)\n| | * Deselect item (if already active, or) if selected.\n| ... | ...\n\n\n[TODO make table per-tool?]", "Blender development todo list -- Tools (migrated from wiki)\nNOTE: this is a direct dump of Tools (without cherrypicking the valid items)\n\n\n# Scene\n\n**New scene - Full Copy**\nSeveral things are still not copied or reassigned when using this tool:\n- [ ] Particles - Not even the particle systems themselves, not to mention re-assigning 'objects' pointers to copied IDs too, see #40891.\n- [ ] Textures when they are only used by e.g. modifiers (i.e. not by a material, world or lamp).\n- [ ] Textures used by modifiers are not re-assigned to new copies when possible either (only objects are handled).\n\n# Library System\n- [x] Hard (or even impossible) to relocate libraries that have been moved (#44958). Addressed in id-remap branch, hopefully merged in 2.78.\n- [ ] 'Find Missing Files' does not work with .blend lib files (impossible with current master, easy to do once id-remap is merged, see #47774).\n\n# Transform\n- [ ] API and draw code for manipulator needs to be redone still. For this reason no manipulator drawing happens during transform.\n- [ ] Manipulator click behavior (left-click-release a manipulator axis to enable a transform on that axis -> perform transform and wait for another left-click to confirm. Expected behavior from 2.4x)\n- [ ] Operator parameters in toolbar don't have to be drawn all always, needs cleanup.\n- [x] Transform redo fails when you change mode during transform (use R S G keys).\n- [x] Mirror of rotated objects doesn't always work correct #37928\n- [ ] Numeric input for rotational transform resolves to modulo 360. Should it? #40167 - ''possible fix included''.\n- [ ] Transform along the axis does incorrect axis projection in certain circumstances #40893\n- [ ] Scaling from zero is not possible with 'S' shortcut (#44551).\n- [ ] Transform redo fails when mouse move is required (#50419).\n- [ ] Apply Scale: Option not to scale all object properties (curve radius, empty scale, text scale... etc). \"Scale Properties\" toggle.\n- [ ] Cursor input to calculate rotation can accumulate a small amount of error (impacts bend and rotate) #53590\n- [ ] Armature edit-mode transform proportional editing doesn't work (#53992).\n\n**Transform Snap**\n- [x] Snapping to vertex slide (Taking into account multiple selections)(#48927).\n- [x] Snapping to face local axis doesn't snap the vertex to the face surface (#38438).\n- [ ] Snapping to self doesn't work with proportional edit-mode (#44793).\n- [ ] Snapping doesn't work for Boolean modifier (#35023).\n- [x] Snapping in object mode rotates object around their origin, instead of rotating them around their snapped point (#42362).\n- [ ] Snapping doesn't behave as expected when having several parented objects (#41199).\n- [ ] Snapping between multiple objects can give some working-as-intended, but in practice quite undesirable behavior (using bounding box) (#47171).\n- [ ] Snapping falls back to using a grid, however this isn't clearly communicated<br>(advanced snapping on faces, vertices, etc. only works on move/rot/scale, see #42798).\n- [ ] Snap to cursor and snap to grid could be made to work more consistently: See (#34441)\n- [ ] snap_project individual element on surface of other objects - watch?v=XrEPpHGoKlk&feature=youtu.be&t=1m10s;\n- [ ] Snap does not work for NURB surfaces (#78434);\n\n# DupliObject\n- [ ] There is no good way to control the rotation of objects in DupliFaces option (rotation is computed from face normal (which is good) and first three vertices of the polygon (which is weak, epic fail with e.g. Mirror modifier). See #37365.\n- [ ] Duplifaces don't work well with the mirror modifier, see #37820.\n\n# Curves\n- [ ] Capping front / back -ends of beveled curve doesn't work, see #26136\n- [ ] Constructive modifier kills generated UV mapping on bevelled curves, see #27411\n- [ ] Surfaces Make Segment rotates U/V even when it's not actually needed, see #31480\n- [ ] Couldn't cycle through vertices with the same location using mouse selection, see #36760\n- [ ] Curve tessellation might work not as it's expected to, see #37386, #40171\n- [ ] Curve deform doesn't work if curve is zero-scaled #38907\n- [ ] Nurbs clamp order by total number of points, this should be clamped at runtime #40378\n- [ ] Handling of non-smooth control points with (Bézier/poly) curves in general, and their rotation in particular, could be improved when generating BevelList & Path, see #44393.\n- [ ] In some cases Bevel should prefer \"clip\" behavior over trying to keep constant shape across the path #50720.\n\n# Text objects\n\n- [ ] Font formatting interface should be improved (#49599)\n- [ ] Default Bfont doesn't support russian characters (or any other non-european charset) in text object, while UI does show Russian characters (#53744)\n\n# Metas\n\n- [ ] Some shapes (Cube) for eg. draw far outside the tessellation bounds making them hard to select. see #47455\n\n# Meshes\n\n**Mesh Editing**\n- [ ] Knife & loopcut\n - [ ] Knife/loop cut need to work properly with operator properties/redo\n - [ ] Restore Quad Corner Cut Methods (Innervert, Fan and Path) for Subdivisions and Knifecut\n - [ ] Knife cuts side-on, intersecting the entire face, could be detected and ignored #43816\n- [ ] Mirror edit mesh operator (Ctrl M) fails to flip normals leaving an incorrectly mirrored mesh (turns normals inside)\n- [ ] Add option to disable n-gons usage for tools (might be useful for some usages) (see #31268)\n- [ ] 'Checker deselect' could be modified to work in some cases where it currently fails, (see #34544)\n- [ ] Merge meshes: add option to join UVs (and other CD layers!) by names rather than index (see #36749).\n- [ ] toolbar mesh Extrude operator inconsistency (see #36977).\n- [ ] Shape keys: Enhance memory usage (not storing vcos for unchanged vertices? See blender/blender-addons#39287).\n\n- [ ] Bevel\n - [ ] Better handling of profile=1, profile=0.25, and implement profile=0 cases (see #39132 and #38458 and #40278).\n - [ ] Generalize to handle several manifold sheets touching at a point (see #34678).\n - [ ] Improve clamping code (see #38871).\n - [ ] More options, e.g., spline spec for profile shape (see #40722) and vertex blends with setbacks.\n - [ ] Treat more cases like \"pipe\" to avoid bulges (see #40258)\n - [ ] Option to have bevel not create n-gons (see bf-funboard thread)\n - [ ] Sometimes leaves degenerated geometry (#48174)\n\n- [ ] DataTransfer/Geometry Matching\n - [ ] Add 'matching' algorithms based on 'similar shape' rather than simple items proximity/raycasting (see #46762 for a usecase) - WARNING: most likely advanced, mathy project!\n - [ ] A review of islands handling could also be useful, current code is rather complex and not so efficient.\n\n- [ ] Discussion\n - [ ] Extrude behaviour on cancel, see (#23492).\n\n**Text Editing (3D)**\n- [ ] When converting beveled text into a mesh - there are many doubles.\n- [ ] Text object requires better integration with the system clipboard, #38556, #46330\n- [ ] Support font kerning (#47725).\n\n**UV Unwrapping**\n- [ ] Settings for pack margin in different operators behaves inconsistently, see detailed description: 039547.html\n- [ ] Remove doubles has an option to Merge with unselected verts, This would be very handy for welding also.\n- [ ] Detect convex mesh without seams on unwrap and print warning.\n- [ ] Unwrapping fails on a particular strange topology (#31145)\n- [ ] Unwrapping for concave polygons is badly supported #41810\n- [ ] Face/edge selection in UV Editor does not work same as in 3DView (#52276).\n\n; Not ported from 2.4x\n- [ ] Click Project from face\n- [ ] Consolidate into one image\n- [ ] Billboard render on active\n- [ ] Unwrapping could run out of stack size for tricky geometry #42524\n\n**Vertex Paint**\n\n- [ ] Undo in vertex (and weight paint) behave differently to sculpt/project-paint modes regarding undo steps #52993\n\n### Sculpt & Paint\n\n**Sculpting**\n- [ ] Check documentation and fix hotkeys which could be useful for artists (or remove redundant hotkeys and update documentation), see #26017\n- [ ] Grab + symmetry can make things shoot off more quickly than they should (strength of movement is being double counted), see #25370\n- [ ] Not all drawing modes supports PBVH drawing, see #32454, #38608, #38609\n- [ ] Not all shading modes are supported for dyntopo, see #34010\n- [ ] Hidden faces are treated as hidden by sculpt tools but when PBVH drawing isn't used, the hidden faces display (and cant be edited), see #33078\n- [ ] Multires modifiers: makes mesh invisible after leaving sculpting mode, see #36591\n- [ ] Multires sculpt: artifacts grabbing between different levels #40465\n- [ ] Dyntopo does not support restoration when aborting a stroke, see #46456.\n\n**Painting (3D)**\n- [ ] Solve projection paint issue when one vertex in a face in behind the view in perspective mode<br>index.php?func=detail&aid=26393&group_id=9&atid=498\n- [ ] Continue to unify paint modes\n - [ ] Consistent brush texture mapping across paint modes (sculpt/tex paint/proj paint).\n - [ ] Consistent brush options, eg. 'Rake' or 'Anchored' in texture paint.\n- [ ] Make paint of displacement texture apply real time on model (optional). (#24657)\n- [ ] Allow view center to work for selected/active face in WPaint mode.\n- [ ] Viewport navigation for painting modes can be improved #48113\n- [ ] Users can perform strokes which apply to a huge number of pixels (by accident) - this could be handled gracefully #52351\n\n**Painting (2D)**\n- [ ] Clone image painting should support the same translation/rotation/scale tools as stencil texture mapping.\n- [ ] Stepped lines in image editor painting, blending should use float coordinates and interpolate (#52610)\n\n\n**Grease Pencil**\n- [ ] Default attach point of GP data is confusing ((#21969))\n- [ ] GP ignores color management ((#50149))\n\n### Materials\n- [ ] Improve handling of linking of materials to Object/Data. Right assigning a material-less data to object the materials from object are gone too (blender/blender-addons#23805, #52484).\n- [ ] Fix EnvMap update, it can depends on many different things in the scene (#41900).\n\n### Modifiers\n- [ ] Make (at least some) generative modifiers to handle custom normals (like e.g. mirror one, see #44058).\n\n**Array Modifier**\n- [ ] Has been re-written to use bmesh, making 2.63 slower then 2.62, There are areas where speed could be improved, for full info see #30695\n- [ ] Textures from cap objects are completely ignored and no way to override them, see #33578\n\n**Boolean Modifier**\n- [ ] Boolean modifier does not preserve vertices/edges data, see #32203, #33548\n- [ ] Issues with degenerated faces, see #30447\n\n**Decimate Modifier**\n- [ ] Limit decimation along seams (UV vertex color, etc), see #32203\n\n**Explode Modifier**\n\n- [ ] Does not preserve UV maps when using Cut Edges option (#46514)\n\n**Multires Modifier**\n- [ ] Only solid draw mode uses optimized drawing\n- [ ] \"Applying Base\" gives spikes on lover levels sometimes, see #35560, #37997\n\n**Bevel Modifier**\n- [ ] Does not preserve edge custom data, see #35314.\n\n**Simple Deform Modifier**\n- [ ] The bend/taper/twist options use fixed axis, add XYZ options would be nice. #33712\n\n**Skin Modifier**\n- [ ] Skin modifier very slow in some cases, see #40770\n\n**Solidify Modifier**\n- [ ] Curves tesselation creates zero area faces which solidify doesn't handle well #52170\n\n**Remesh Modifier**\n- [ ] Mesh data at extreme distance from origin (2**24), crashes #47209<br>''Note, this is a real corner case - yet its a bug because it shouldn't crash.''\n\n### Physics\n- [ ] Allow using multiple baked caches on a single object (having different frame ranges), see #41896.\n- [ ] Bullet: High memory usage for objects that don't have scale applied (#35799)\n\n**Baking**\n\n- [ ] Generic issue: baking ignores making pointcaches when modifier preview has been disabled. Doesn't need fix - but let's keep track of this for future work.\n- [ ] Point caches do not work well with time remapping (example #35968)\n\n**Cloth**\n- [ ] Proper handling of rendered subframes without baked pointcache, for more info see (#21948)\n- [ ] Proper handling of different vertices placed at the same position with \"Soft Body Self Collision\" option turned on (see (#26956)).\n- [ ] Cloths doesn't allow preview during bake (see (#30490)).\n- [ ] Dupli-group cloth in NLA fails (#29838)\n- [ ] 'Emit from: verts' not working as expected when deforming #36237\n- [ ] Collision of hairs doesn't works properly #39219\n- [ ] Memory optimizations are possible for cloth #42577\n- [ ] Cloth pre-roll feature is totally weird and needs reconsideration #40103\n\n**Collisions**\n- [ ] Collision modifier updates it's data structure even if there are no physics that need it (can be slow), a check should be added to make sure the data is actually needed, see (#26965).\n- [ ] Force fields and collision objects are not included in DupliObjects. This is mostly a design decision (duplis being a purely visual feature), but would be nice to support at least in groups. #35264 #36300\n\n**Hair**\n- [ ] Better handling of collisions & force fields for dynamic hair\n- [ ] Wave kink direction is totally uncontrollable, probably there needs to be a way to define hair tangent direction in particle edit mode.\n- [ ] Adding hair in particle mode only uses the deformed mesh, see (#25689).\n\n**Particles**\n- [ ] Particle emission between frames is only accurate for object level emitter/parent animation, for parenting or constraints an interpolation method needs to be implemented, but before this can be done pointcache code has to get some changes too. See (#36516) for more details.\n*; Parent animation is now supported {{GitCommit|c24a23f. Similar issue still persists for non-animated parents (e.g. rigid bodies) though #39923\n- [ ] Reactor particles\n- [ ] Conversion from some old files could be better\n- [ ] Vector blur + particles being born/dying doesn't work properly, see (#23320).\n- [ ] Metaballs don't work with particles when the particle view setting isn't \"render\", see (#25794) for more info.\n- [ ] \"Constructive modifiers before particles\" is still an open issue, but some way to handle this gracefully would be really nice, see (#25838) for more info.\n- [ ] Density of particles can't be animated with animated textures, see (#28212).\n- [ ] Instanced objects do not show in particle edit mode, see (#28431).\n- [ ] Issue with ghosting particles if you don't bake first. (#28116)\n- [ ] Linked groups: Force fields and guides only work if you use \"Effector Group\" feature, set to its own group.\n- [ ] Particle Hair dynamics: stops working after using \"Add tool\". (#30557)\n- [ ] Instanced objects don't draw in Particle Edit Mode. (#31913)\n- [ ] Child particles Interpolated mode only works well for Hair, for other particles it doesn't take particle lifetime into account. (#33390)\n- [ ] Particle emission doesn't support NGons.\n- [ ] Particle Object duplication doesn't work with Mirror modifier (#34705)\n- [ ] Particle systems fail to duplicate for smoke simulation (#34705)\n- [ ] Random distribution of particles fails in specific setups (#35598)\n- [ ] Default point cache step of 10 frames fails in some cases, see #38563\n- [ ] Particles tangent rotation control by vertex group missing, see #35103\n- [ ] Texture doesn't affect grid particles #40404\n- [ ] The particle system needs to be set to 'Newtonian Physics' for texture to influence the size, and with global gravity turned off #28263\n- [ ] Multiple issues with particles rotation #32340, #44088\n- [ ] Particles hidden in viewport reappear during rendering #40463\n- [ ] Particle initial speed is not properly inherited from the parent #41305\n- [ ] Point density textures can not be used to control particles #44901\n- [ ] Particle duplication in general is rather poorly implemented (no relink of used datablocks, no duplication of psettings ID when duplicating objects, …) #45843.\n- [ ] Grid distribution only supports From Dupli Generated, but not UV. Potentially could use nearest face. #48928\n- [ ] Particles aren't spawned correctly, they are sometimes generated at the same location as other particles, or at the object's origin. See #50135 for one scenario.\n- [ ] Particle editmode could have its 'own' [X-mirror] option (and not reuse editmode option). See #53872\n\n**Rigid Body**\n- [ ] Velocities are not cached, which prevents a proper state update when cache has time gaps #50230.\n\n### Image & Video\n\n**Compositing**\n- [ ] DOF Defocus node: fStop close to 128 fails to give good results, stay away from that value! (#24534)\n- [ ] DOF node gives no realistic results as users expect, documentation needs upgrade for it.\n- [ ] Defocus node is very slow when large blur radius is needed, could be optimized somehow (mipmap, summed area table?) (#29481)\n- [ ] Defocus node does not work nicely without a camera controlling the blur radius. This makes external compositing workflows with defocus difficult. At the heart of this is a design conflict, because defocus is not a true postprocessing effect #36745\n- [ ] Fast Gauss (Gabor filter, Young/VanVliet) has bad results for edge cases. Needs image processing guru (#25543)\n- [ ] Check on DPX and ASC_CDL and (#27377)\n- [ ] Map UV makes mapped images blurry, see #31868\n- [ ] Some nodes does not preserve alpha channel replacing it with fully opaque, see #32580\n- [ ] With new compositor, on loading files a compositor doesn't start (for existing buffers), so viewers remain empty as well. #35417\n- [ ] Ghost Glare is of limited use, needs clarification and probably a more sophisticated generic lens flare alternative #30389 #36488\n- [ ] Some node inputs require a single constant value and don't work with image-based per-pixel values (#36585). This leads to confusion when nodes apparently don't work, because nothing prevents linking such variable values into constant inputs. Compositor nodes should keep track of constant values and limited inputs on the node level (also in node groups!).\n- [ ] Compositor gives unexpected results with specific curve mapping due to precision loss, see #36621\n- [ ] \"Full Sample\" merging does not work with the File Output node, sample merging happens only for render result outside compositor. Real-time editing might also be improved to deal with samples better (#36811, #39143)\n- [ ] Accumulation method in the Lens Distortion node causes artifacts on noisy input #37462\n- [ ] Compositor does not support render slots #43260\n- [ ] Scaling down produces artifacts due to lack of ellipse filtering of sampler #51070\n\n**Image formats**\n- [ ] Upgrade our DPX code to read newer or different versions, copy the ImageMagick code? (#24716)\n- [ ] No support yet to output images in user chosen color space. (#37650)", "Blender editing performance with many datablocks\nEditing scenes with many datablocks can be slow, for example adding, deleting or duplicating many objects.\n\nAdding or deleting a single object has time complexity O(N), where N is the number of objects. This is due to unique name tests, looping over all datablocks to clear all pointers, and other operations that require accessing many datablocks. In general all such operations must become O(log(N)) or O(1), along with possible access of just the other datablocks linking to it.\n\nUndo push (#60695) and dependency graph rebuild are also O(N). We are not trying to improve those as part of this task, and note these can be run once after making many edits.\n\nPractical steps to reduce time complexity would be:\n\n* Store two-way links for all (non-COW) data-blocks, so that iterating over all datablocks that link to a given datablock is fast. There are transient data structures for this, but it should become permanent. Every `id_us_min()` and `id_us_plus()` should be turned into an operation that sets the datablock pointer and creates a link in the other direction as well.\n* Extend or modify datablock lists in `Main` to support quick testing for duplicate names.\n* Change view layer collection syncing to not require looping over all objects.", "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", "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", "Boolean modifier: Self Intersection fails when mesh object is same for both operand types\nOperating system: Win10 (21H1 19043.1348)\nGraphics card: GeForce 1080Ti (496.76)\n\nLatest 3.0 (December 02, 02:20:21 - 9cec9b4d6e33)\n\nOperand type `collection` did not consider `self intersection` with certain condition.\nIt fails when mesh object is same for both operand types\n\n- Open .blend file\n- Change operand type to `Object`\n- Uncheck `Self Intersection`\n- Switch back to `Collection\n\nTest File:\n[boolean.blend](boolean.blend)\n[2021-12-03 13-50-41.mp4](2021-12-03_13-50-41.mp4)", "Regression: Attempt to move object with Copy Location (with Offset) crashes\nOperating system: Windows-10-10.0.22621-SP0 64 Bits\nGraphics card: NVIDIA GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67\n\nBroken: version: 3.4.0 Alpha\nWorked: version: 3.4.0 Alpha\n\nA consistent crash when trying to move an object with COPY LOC w/ Offset enabled.\n\n\n1. Open the attached blend file\n\n2. Move the pre-selected object in any direction, you may have to do this two or three times\n\n3. program will crash with EXCEPTION_ACCESS_VIOLATION\n\nThis is happening every time.\n\n```\nStack trace:\nblender.exe :0x00007FF73E03C510 blender::bounds::min_max<blender::VecBase<float,3> >\nblender.exe :0x00007FF73E03BD30 blender::FunctionRef<void __cdecl(blender::Bounds<blender::VecBase<float,3> > &)>::callback_fn<<lam\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\nblender.exe :0x00007FF7425212F0 blender::CacheMutex::ensure\nblender.exe :0x00007FF73E042390 BKE_mesh_minmax\nblender.exe :0x00007FF73E0409F0 BKE_mesh_boundbox_get\nblender.exe :0x00007FF73E02E940 BKE_object_boundbox_get\nblender.exe :0x00007FF73E02F410 BKE_object_dimensions_get\nblender.exe :0x00007FF73E613520 RNA_property_float_get_index\nblender.exe :0x00007FF73E235050 dtar_get_prop_val\nblender.exe :0x00007FF73E235410 evaluate_driver\nblender.exe :0x00007FF73E168590 calculate_fcurve\nblender.exe :0x00007FF73E156270 BKE_animsys_eval_driver\nblender.exe :0x00007FF73E4464F0 blender::deg::`anonymous namespace'::evaluate_node\nblender.exe :0x00007FF73E446320 blender::deg::`anonymous namespace'::deg_task_run_func\nblender.exe :0x00007FF7425175C0 tbb::internal::function_task<Task>::execute\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998CF220 tbb::recursive_mutex::scoped_lock::internal_try_acquire\ntbb.dll :0x00007FF9998C4FD0 tbb::interface7::internal::isolate_within_arena\ntbb.dll :0x00007FF9998CA120 tbb::task_scheduler_init::terminate\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\ntbb.dll :0x00007FF9998CD800 tbb::thread_bound_filter::try_process_item\nucrtbase.dll :0x00007FF9A5D192C0 recalloc\nKERNEL32.DLL :0x00007FF9A6F72690 BaseThreadInitThunk\nntdll.dll :0x00007FF9A882AA40 RtlUserThreadStart\n```\n\n" ]

[ "Copy to selected doesn't work for Object Data Properties\nOperating system: Darwin-18.5.0-x86_64-i386-64bit 64 Bits\nGraphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-12.0.23 355.11.10.50.10.103\n\nBroken: version: 2.82 (sub 7)\nWorked: (optional)\n\nCopy to selected doesn't work for Object Data Properties\n\nMake a cube, a sphere and a cylinder and move them so that they are not on top of each other.\n\nSelect the sphere and the cylinder. Go to object data properties. Change the mesh to cube. One of the two selected will change to a cube as expected. Right click and do Copy to selected, nothing happens but the other one should also change to a cube.\n" ]