Maniphest T76910

Random Crashes: when saving .blend file and when opening image from image editor
Closed, DuplicateBUG

Assigned To
None
Authored By
Erick Tukuniata (erickblender)
May 20 2020, 2:20 PM
Tags
  • BF Blender
  • User Interface
Subscribers
Erick Tukuniata (erickblender)
Germano Cavalcante (mano-wii)

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 550 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 376.54

Blender Version
Broken: version: 2.90 (sub 2), branch: master, commit date: 2020-05-20 08:43, hash: rB578b0c00cacb
Worked: (newest version of Blender that worked as expected)

Short description of error
Random Crashes when saving .blend file and when opening image from image editor

Exact steps for others to reproduce the error

Scenario 1:

  • Start a new Blender project then save it, the blend file will be save but it will crash.
  • It should crash if not try again.

Scenario 2:

Open an image with image editor by:

    • doing ctrl+f10 in the outliner window
  • then click open

The problem with randoms crash i have to upload a video

Event Timeline

Erick Tukuniata (erickblender) created this task.May 20 2020, 2:20 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).EditedMay 21 2020, 11:27 PM

I cant reproduce the problem.

Can you run blender_debug-gpu.cmd that is included in the download.
After Blender closes, the logs will be in a text file which can be attached here.

Erick Tukuniata (erickblender) added a comment.May 22 2020, 1:07 PM

Here is you go:

  • With debug version

  • And with release version, not debug.
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.May 22 2020, 2:18 PM
Germano Cavalcante (mano-wii) triaged this task as High priority.
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".
Germano Cavalcante (mano-wii) added a project: User Interface.

Apparently it is not a GPU problem.
Reading Stack trace I suspect the problem is that region has an invalid memory address (in handler_region_v2d_mask_test).

@Erick Tukuniata (erickblender), which of the described scenarios did you use to generate crash.txt?
I cannot reproduce the problem, but I'm confirming it.