Blender Crashes when deselecting Name-fields #112145

New Issue

Mieke-Narjes · 2023-09-08T15:25:10+02:00

Mieke-Narjes commented

2023-09-08 15:25:10 +02:00

System Information
Operating system: Windows-10
Graphics card: NVIDIA GeForce RTX 3070

also tested on:
Operating system: Windows-11 Home - Microsoft Surface
Graphics card: - / 11th Gen Intel(R) Core(TM) i7-1185G7

Blender Version
Broken: (tested with)

version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e, type: release
version: 3.5.1, branch: blender-v3.5-release, Date: 2023-04-24 18:11, hash: e1ccd9d4a1

Worked: -

Short description of error
For a specific project, if I select any Text field that contains the name of an asset (texture, object, scene, ...) and click anywhere else within the Blender window, Blender will crash.

This error does not appear for other projects of mine or a new one.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

Open file
Navigate to Texture
Create a new Texture
Select Texture name (no need to alter the name to reproduce the error)
Click into e.g. Viewport or hit Enter

I created a copy of the problematic project, deleted all of its content and used the Blender cleanup feature to remove any remaining data blocks. Still the issue persists. Except for the missing shutdown logs due to the crash, the Debug Log doesn't show any differences to a normal file AFAIK.

Blender does NOT crash when I use "Escape" to exit the field.
To be precise, the crash happens when deselecting "Name Fields" in the outliner, the Properties Panel or similar.
This doesn't happen in Search fields or Value fields that take e.g. floats for properties like "Strength" etc.

The project (used as asset library) worked fine yesterday and as far as I'm aware no updates were installed. I tried updating my NVIDIA driver but to no avail.

Next, I'll try to copy my assets to a new file.

**System Information** Operating system: Windows-10 Graphics card: NVIDIA GeForce RTX 3070 also tested on: Operating system: Windows-11 Home - Microsoft Surface Graphics card: - / 11th Gen Intel(R) Core(TM) i7-1185G7 **Blender Version** Broken: (tested with) - version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a, type: release - version: 3.5.1, branch: blender-v3.5-release, Date: 2023-04-24 18:11, hash: e1ccd9d4a1d3 Worked: - **Short description of error** For a specific project, if I select any Text field that contains the name of an asset (texture, object, scene, ...) and click anywhere else within the Blender window, Blender will crash. This error does not appear for other projects of mine or a new one. **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible). 1. Open file 2. Navigate to Texture 3. Create a new Texture 4. Select Texture name (no need to alter the name to reproduce the error) 5. Click into e.g. Viewport or hit Enter I created a copy of the problematic project, deleted all of its content and used the Blender cleanup feature to remove any remaining data blocks. Still the issue persists. Except for the missing shutdown logs due to the crash, the Debug Log doesn't show any differences to a normal file AFAIK. Blender does NOT crash when I use "Escape" to exit the field. To be precise, the crash happens when deselecting "Name Fields" in the outliner, the Properties Panel or similar. This doesn't happen in Search fields or Value fields that take e.g. floats for properties like "Strength" etc. The project (used as asset library) worked fine yesterday and as far as I'm aware no updates were installed. I tried updating my NVIDIA driver but to no avail. Next, I'll try to copy my assets to a new file.

blender_system_info.txt

22 KiB

blender_debug_output_gpu.txt

21 KiB

blender_debug_output_gpu_glitchworkaround.txt

23 KiB

RenamingCrash.blend

1.2 MiB

blender_debug_output.txt

248 B

Mieke-Narjes added the

labels 2023-09-08 15:25:10 +02:00

Mieke-Narjes changed title from ~~Blender Crashes when deselecting Name-fields of objects~~ to Blender Crashes when deselecting Name-fields

2023-09-08 15:26:37 +02:00

Mieke-Narjes commented

2023-09-08 15:53:57 +02:00

Update:
I appended the scenes of the problematic project to a new one and so far it looks good.

Update: I appended the scenes of the problematic project to a new one and so far it looks good.

Pratik Borhade commented

2023-09-11 06:05:07 +02:00

Hi, thanks for the report. I'm not able to redo the crash locally. Call stack is not generated in attached debug-log files.
Do you have multi-monitor setup?

Hi, thanks for the report. I'm not able to redo the crash locally. Call stack is not generated in attached debug-log files. Do you have multi-monitor setup?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-09-11 06:05:16 +02:00

Mieke-Narjes commented

2023-09-11 13:19:14 +02:00

Hi Pratik, thanks for having a look.
Yes, I have 3 monitors.

Hi Pratik, thanks for having a look. Yes, I have 3 monitors.

Pratik Borhade commented

2023-09-11 14:19:44 +02:00

Thanks. Not very sure but this could be a culprit here. Can you share more details about your setup?
Do you happen to observe crash when texture name-field is on primary screen? or some secondary monitor?
Can you verify the crash when both blender windows are on same monitor?

Unfortunately crash.txt is not generated after the crash and Debug log files has not printed any relevant information.

Thanks. Not very sure but this could be a culprit here. Can you share more details about your setup? Do you happen to observe crash when `texture name-field` is on primary screen? or some secondary monitor? Can you verify the crash when both blender windows are on same monitor? - - - Unfortunately `crash.txt` is not generated after the crash and `Debug log` files has not printed any relevant information.

Mieke-Narjes commented

2023-09-11 15:16:50 +02:00

Yes, I was hoping to find some crash information but no luck with this one.

The file crashes on either monitor, if I just open it and go straight to any name field.
However, if I:

open file
add another window
and set it to "Asset Browser"

then I can edit name fileds just fine. It is important to set it to "Asset Browser" first - I tried with several other options like "Viewport", "Graph Editor" and "Image Editor" and they all crashed. After that, I can pick and choose any window I like and rename stuff without crashes.

I then figured that the "broken" file also always opens a second window in the background with the Asset Browser when launched.
I therefore closed the window and saved the File to see if it makes any difference. Sure enough, if I reopen the file now, renaming works just fine.

Also, saving a new second window with the Asset Browser doesn't cause any issues.

No idea what made this particular window so problematic - but it's gone now.
I can't tell if it is related to my local setup or some weird edge case in Blender.

Yes, I was hoping to find some crash information but no luck with this one. The file crashes on either monitor, if I just open it and go straight to any name field. However, if I: 1. open file 2. add another window 3. and set it to "Asset Browser" then I can edit name fileds just fine. It is important to set it to "Asset Browser" first - I tried with several other options like "Viewport", "Graph Editor" and "Image Editor" and they all crashed. After that, I can pick and choose any window I like and rename stuff without crashes. I then figured that the "broken" file also always opens a second window in the background with the Asset Browser when launched. I therefore closed the window and saved the File to see if it makes any difference. Sure enough, if I reopen the file now, renaming works just fine. Also, saving a new second window with the Asset Browser doesn't cause any issues. No idea what made this particular window so problematic - but it's gone now. I can't tell if it is related to my local setup or some weird edge case in Blender.

Pratik Borhade commented

2023-09-12 07:02:25 +02:00

Wait, I can actually redo the crash with your file 🙂 , I'll check.

Pratik Borhade commented

2023-09-12 07:46:06 +02:00

Crash is related to asset browser.
In your file, active_file index for asset browser is 1 and filelist is initially nullptr. which leads to crash at if ((index < 0) || (index >= filelist->filelist.entries_filtered_num)) {

Crash is related to asset browser. In your file, `active_file` index for asset browser is 1 and `filelist` is initially nullptr. which leads to crash at [if ((index < 0) || (index >= filelist->filelist.entries_filtered_num)) {](https://projects.blender.org/blender/blender/src/branch/main/source/blender/editors/space_file/filelist.cc#L2166)

Pratik Borhade added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender Crashes when deselecting Name-fields #112145