3.5 crashes when objects join #110026

New Issue

Andrew · 2023-07-12T19:42:49+02:00

Andrew commented

2023-07-12 19:42:49 +02:00

version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff1, type: release
build date: 2023-03-29, 06:36:20
platform: 'Windows-10-10.0.16299-SP0'
Graphics card: GeForce 1060 GTX 6 Gb

I0712 20:41:03.284521 12864 device.cpp:32] CUEW initialization succeeded
I0712 20:41:03.284521 12864 device.cpp:34] Found precompiled kernels
I0712 20:41:03.293520 12864 device.cpp:56] HIPEW initialization failed: Error opening HIP dynamic library
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF78A4BA3C1
Module : blender.exe
Thread : 00003240
Switching to fully guarded memory allocator.
Blender 3.5.0
Build: 2023-03-29 06:36:20 Windows release
argv[0] = F:\Programs\Blender35\blender
argv[1] = --debug
argv[2] = --debug-cycles
argv[3] = --python-expr
argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Windows\TEMP\blender\debug_logs\blender_system_info.txt')
Read prefs: C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\config\userpref.blend
Read blend: C:\Users\User\Desktop\wha\bug.blend
Writing: C:\Windows\TEMP\bug.crash.txt

Short description of error
3.5 crashes when object join

Exact steps for others to reproduce the error
Ctl+J

Also when I try export to .obj this meshes, after import .obj back in a new .blend file I see nothing. Zero polygons.

version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b, type: release build date: 2023-03-29, 06:36:20 platform: 'Windows-10-10.0.16299-SP0' Graphics card: GeForce 1060 GTX 6 Gb I0712 20:41:03.284521 12864 device.cpp:32] CUEW initialization succeeded I0712 20:41:03.284521 12864 device.cpp:34] Found precompiled kernels I0712 20:41:03.293520 12864 device.cpp:56] HIPEW initialization failed: Error opening HIP dynamic library Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF78A4BA3C1 Module : blender.exe Thread : 00003240 Switching to fully guarded memory allocator. Blender 3.5.0 Build: 2023-03-29 06:36:20 Windows release argv[0] = F:\Programs\Blender35\\blender argv[1] = --debug argv[2] = --debug-cycles argv[3] = --python-expr argv[4] = import bpy; bpy.ops.wm.sysinfo(filepath=r'C:\Windows\TEMP\blender\debug_logs\blender_system_info.txt') Read prefs: C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.5\config\userpref.blend Read blend: C:\Users\User\Desktop\wha\bug.blend Writing: C:\Windows\TEMP\bug.crash.txt **Short description of error** 3.5 crashes when object join **Exact steps for others to reproduce the error** Ctl+J Also when I try export to .obj this meshes, after import .obj back in a new .blend file I see nothing. Zero polygons.

blender_system_info.txt

23 KiB

bug.blend

863 KiB

screen.PNG

579 KiB

blender_debug_output.txt

860 B

Andrew added the

labels 2023-07-12 19:42:49 +02:00

Iliya Katushenock commented

2023-07-12 19:45:04 +02:00

Hi, thanks for report, can you attach C:\Windows\TEMP\bug.crash.txt?

Hi, thanks for report, can you attach `C:\Windows\TEMP\bug.crash.txt`?

Iliya Katushenock commented

2023-07-12 19:46:11 +02:00

Also, it make sense to check the same bug if is still in 3.6/4.0?

Andrew commented

2023-07-12 20:21:25 +02:00

Hi, thanks for report, can you attach C:\Windows\TEMP\bug.crash.txt?

Also, it make sense to check the same bug if is still in 3.6/4.0?
Looks like in 3.6 works fine. Blender 3.4 also crashes.

> Hi, thanks for report, can you attach `C:\Windows\TEMP\bug.crash.txt`? >Also, it make sense to check the same bug if is still in 3.6/4.0? Looks like in 3.6 works fine. Blender 3.4 also crashes.

bug.crash.txt

28 KiB

Jesse Yurkovich commented

2023-07-12 23:43:55 +02:00

This particular crash should have been fixed in 3.6/4.0. Please confirm on your side by using the latest 3.6 LTS from https://www.blender.org/download/

Jesse Yurkovich added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-07-12 23:44:03 +02:00

Pratik Borhade commented

2023-08-30 09:08:03 +02:00

Yes, fixed indeed: #107647
Closing.

Yes, fixed indeed: #107647 Closing.

Pratik Borhade closed this issue