Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.5.0a5
Issue ID
913620
Regression
Yes
100% reproducible crash on drag and drop on Windows
1) Open editor built from latest trunk (f6f6d6bff5c6)
2) Drag a skinned mesh renderer into the scene view.
3) Boom!
> Unity.exe!core::StringStorageDefault<char>::assign(const char * str, unsigned __int64 strLen) Line 92 C++
Unity.exe!DragAndDrop::FetchDataFromDrag(IDataObject * data) Line 248 C++
Unity.exe!WindowsDropTargetImpl::UnderstandsData(IDataObject * dataObject) Line 33 C++
Unity.exe!CDropTarget::DragEnter(IDataObject * pDataObject, unsigned long grfKeyState, _POINTL pt, unsigned long * pdwEffect) Line 426 C++
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
drjfgi
Sep 01, 2017 13:23
crashes for me on a range on drag and drops
Several times a day
looking on the net such crashes have been happening for over a year.
Why does it take so long for them to fix something that is so fundamental?