System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92
Blender Version
Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-05-08 14:49, hash: rBce76e17584ee
Worked: (newest version of Blender that worked as expected)
Short description of error
I try to split area and Blender crashes.
Exact steps for others to reproduce the error
I can't reproduce the issue on Windows 10 with the latest commit of blender-v2.83-release. Please open Blender's installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you two files. Add them to your bug report by clicking on the upload button as shown in the screenshot below.
Window10s(64bit), GTX 1660 (Nividia Driver 445.98)
I have noticed a similar probem.
I can reproduce it with the daily build based on rBce76e17584eea6185170275250b25d9f5b80ad12, but not in my debug build. I'll investigate.
I can't reproduce this in my local release build (with or without RelWithDebInfo) either.
I'm delete all files and preference from my computer and cleanup system. I'm download blender again from here. But problem dosn't resolve. I've tried it on Linux and didn't have issues on it.
I don't know if it will help in any way but in this same time, the 2.90 (blender-2.90-76e56e2ba70f-windows64) works fine.
Yes, I know. Thanks) But problem with 2.83 ce76e17584ee, May 9 and only on Windows 10 (I've tried it on Linux and didn't have issues on it).
Actually I've returned on previous build when actual build had critical or semi-critical bug and wait for resolving.
Can't see anything suspicious even with --debug-all. Without debug symbols for the buildbot build this is difficult to diagnose. Might have to reverse engineer the build.
Build bot 2.83 (crashes)
Local release build 2.83
Build bot 2.90
Command used to create log files
.\blender.exe --debug-all -t 1 > blender_debug_log.txt
I'm setting this to confirmed, since the Windows build from buildbot definitely crash when resizing windows.
I've triggered the build bot and the current build based on rBeaee2b4119359493b87422100e913a5e1dc9a001 appears to work fine. Source of the issue from the previous build is still unclear though.
@Robert Guetzkow (rjg) If I understandyou correctly you was able to reproduce this issue in rBce76e17584eea6185170275250b25d9f5b80ad12, but not in latest master?
I think it may be safe to close then.
I tried to build rBce76e17584eea6185170275250b25d9f5b80ad12 to check myself but I wasn't really able to build correctly that specific hash.
I have experienced some weird crashes when opening on any menu, but this issue has dissappeared when I did full rebuild. Perhaps these issues are connected.
@Richard Antalik (ISS) I was only able to reproduce this with the buildbot build of rBce76e17584eea6185170275250b25d9f5b80ad12 on Windows, but not in a local build (neither debug nor release). New builds from buildbot work fine as well.
Sounds like that may be related. Were you able to identify what went wrong in your local build?
I wasn't able to identify problem. Each time I tried to open menu it would stop on exception on some weird address. I don't even remember what kind of exception it was but I think read access violation with again weird address. it showed me exact same stack trace though.
Just to check, does anybody still have an issue with the current builds from buildbot?
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.92
Blender Version
Broken: version: 2.83 (sub 16), branch: master, commit date: 2020-05-13 20:48, hash: rB71298a1da971
Worked: (newest version of Blender that worked as expected)
It is working fine, no crashes. I tested split with right click > menu and just with mouse on corners and everything is OK. Thank you. All developers are amazing.