Looptools Gstretch crash #78313
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#78313
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce 940MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.87
Blender Version
Broken: version: 2.83.1, branch: master, commit date: 2020-06-25 09:47, hash:
blender/blender@8289fc688b
Worked: (newest version of Blender that worked as expected)
Addon Information
Name: LoopTools (4, 7, 3)
Author: Bart Crouch, Vladimir Spivak (cwolf3d)
Short description of error
Blender Force closed while I Hit "Delete Annotation Stoke After performing Gstrecth function"
Exact steps for others to reproduce the error
Added subscriber: @madani
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
I was unable to reproduce this both in current versions of Blender and 2.83.x. Are you still able to reproduce this issue and could it be that there is a step missing from the description?
Added subscriber: @ankitm
Can't redo on 797f6e1483a12fe4797e7cf9d435c042ddda40c4 and 2.83.12
macOS 10.14
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists in current versions of Blender please open a new report. Additionally, open Blender's installation directory and double click on the
blender_debug_log.cmd
. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located inC:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt
(or simply type%TEMP%
into the path bar of the Windows Explorer).