Import obj + new UVMap + go to object mode, blender closes #106909

New Issue

Closed

opened 2023-04-13 16:08:45 +02:00 by Antonio Puentes · 10 comments

Antonio Puentes commented

2023-04-13 16:08:45 +02:00

System Information
Operating system: Linux-6.2.10-1-MANJARO-x86_64-with-glibc2.37 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03

Blender Version
Broken: version: 3.5.1 Release Candidate, branch: blender-v3.5-release, commit date: 2023-04-06 02:25, hash: 1bd46a46d15a
Worked: 3.3lts and 3.6 Alpha

Short description of error
Import obj file + new UVMap + go to object mode blender closes

Exact steps for others to reproduce the error

Import any obj file.
Delete UVMap.
In edit mode select all and press U (unwrap) > project from view.
Go to object mode.
Blender closes.

**System Information** Operating system: Linux-6.2.10-1-MANJARO-x86_64-with-glibc2.37 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 530.41.03 **Blender Version** Broken: version: 3.5.1 Release Candidate, branch: blender-v3.5-release, commit date: 2023-04-06 02:25, hash: `1bd46a46d15a` Worked: 3.3lts and 3.6 Alpha **Short description of error** Import obj file + new UVMap + go to object mode blender closes **Exact steps for others to reproduce the error** - Import any obj file. - Delete UVMap. - In edit mode select all and press U (unwrap) > project from view. - Go to object mode. - Blender closes.

obj_uv_stack_trce.txt

32 KiB

untitled.obj

957 B

Antonio Puentes added the

labels 2023-04-13 16:08:46 +02:00

Iliya Katushenock added

and removed

labels 2023-04-13 16:43:41 +02:00

Philipp Oeser commented

2023-04-14 11:38:46 +02:00

Member

Cannot repro here from those steps.
Does this also happen with the official 3.5.0 release? (or just the 3.5.1 candidate?)

Cannot repro here from those steps. Does this also happen with the official 3.5.0 release? (or just the 3.5.1 candidate?)

Antonio Puentes commented

2023-04-14 11:59:07 +02:00

Author

No, in version 3.5.0 release the same error does not occur.

No, in version 3.5.0 release the same error does not occur.

Philipp Oeser commented

2023-04-14 12:18:29 +02:00

Member

Then that is probably because of 268d826 (and fixed again with 3681ed377b which is already on the backport list #106258, will double-check)

Then that is probably because of 268d826 (and fixed again with 3681ed377b which is already on the backport list #106258, will double-check)

Philipp Oeser commented

2023-04-14 13:43:18 +02:00

Member

Then that is probably because of 268d826 (and fixed again with 3681ed377b which is already on the backport list #106258, will double-check)

Just like I said, cherry-picking 3681ed377b onto current blender-v3.5-release fixes the crash, so there is really no point in having this task open, all the backports from #106258 just have to be done [which will probably be real soon].

Will close, thx reporting anyways.

> Then that is probably because of 268d826 (and fixed again with 3681ed377b which is already on the backport list #106258, will double-check) Just like I said, cherry-picking 3681ed377b onto current `blender-v3.5-release` fixes the crash, so there is really no point in having this task open, all the backports from #106258 just have to be done [which will probably be real soon]. Will close, thx reporting anyways.

Philipp Oeser closed this issue

2023-04-14 13:43:20 +02:00

Blender Bot added

and removed

labels 2023-04-14 13:43:40 +02:00

Iliya Katushenock commented

2023-04-14 13:44:52 +02:00

Member

@lichtwerk i added my stack trace from 3.6 debug build (13.04)

@lichtwerk i added my stack trace from 3.6 debug build (13.04)

Philipp Oeser commented

2023-04-14 14:14:00 +02:00

Member

@lichtwerk i added my stack trace from 3.6 debug build (13.04)

@mod_moder : cant get it to crash in 3.6 [not even debug], can you re-check?

> @lichtwerk i added my stack trace from 3.6 debug build (13.04) @mod_moder : cant get it to crash in 3.6 [not even debug], can you re-check?

Iliya Katushenock commented

2023-04-14 14:21:03 +02:00

Member

@lichtwerk True, yes, there is no crash in the release. Seems like unsafe behavior since debugging crashes
Now I building today's debugging.
Also, to make sure, is it a legacy import or a new one?

@lichtwerk True, yes, there is no crash in the release. Seems like unsafe behavior since debugging crashes Now I building today's debugging. Also, to make sure, is it a legacy import or a new one?

Philipp Oeser commented

2023-04-14 14:30:13 +02:00

Member

@lichtwerk True, yes, there is no crash in the release. Seems like unsafe behavior since debugging crashes
Now I building today's debugging.
Also, to make sure, is it a legacy import or a new one?

I used the new importer

> @lichtwerk True, yes, there is no crash in the release. Seems like unsafe behavior since debugging crashes > Now I building today's debugging. > Also, to make sure, is it a legacy import or a new one? I used the new importer

Iliya Katushenock commented

2023-04-14 14:43:30 +02:00

Member

@lichtwerk I imported the example cube with the old and new importers. Saved this in release 3.6. Opened this in debug 3.6, repository state 1-2 hours ago. And I get a crash when I try to U-unwrap for both cubes (after removing the uv map).
I could open this as a new report as it seems like it's just a different issue with the same data.

@lichtwerk I imported the example cube with the old and new importers. Saved this in release 3.6. Opened this in debug 3.6, repository state 1-2 hours ago. And I get a crash when I try to U-unwrap for both cubes (after removing the uv map). I could open this as a new report as it seems like it's just a different issue with the same data.

untitled.blend

850 KiB

Philipp Oeser commented

2023-04-14 15:57:12 +02:00

Member

@lichtwerk I imported the example cube with the old and new importers. Saved this in release 3.6. Opened this in debug 3.6, repository state 1-2 hours ago. And I get a crash when I try to U-unwrap for both cubes (after removing the uv map).
I could open this as a new report as it seems like it's just a different issue with the same data.

That assert you can just trigger with the default cube, remove UVMap, U > Unwrap...
(no OBJ import needed at all...)
But yeah, feel free to open a report for this

> @lichtwerk I imported the example cube with the old and new importers. Saved this in release 3.6. Opened this in debug 3.6, repository state 1-2 hours ago. And I get a crash when I try to U-unwrap for both cubes (after removing the uv map). > I could open this as a new report as it seems like it's just a different issue with the same data. That assert you can just trigger with the default cube, remove UVMap, U > Unwrap... (no OBJ import needed at all...) But yeah, feel free to open a report for this

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#106909

No description provided.