Open JJAYL opened 8 years ago
Did you crop the "Recent Failure Reports:" or were there none there? We would need a minidump to be able to look into this.
@danginsburg there were none. I can check back later today and see.
@danginsburg I just checked again today and there was some here is the new information
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Family: 0x10
CPU Model: 0xa
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 3200 Mhz
6 logical processors
6 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Unsupported
SSE4a: Supported
SSE41: Unsupported
SSE42: Unsupported
AES: Unsupported
AVX: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Network Information:
Network Speed:
Operating System Version:
Ubuntu 16.04.1 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 4.4.0-36-generic
X Server Vendor: The X.Org Foundation
X Server Release: 11803000
X Window Manager: Xfwm4
Steam Runtime Version: steam-runtime-beta-release_2016-06-15
Video Card:
Driver: ATI Technologies Inc. AMD Radeon (TM) RX 460 Graphics
Driver Version: 4.5.13448 Compatibility Profile Context 16.30.3
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x1002
DeviceID: 0x67ef
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1600 x 900
Desktop Resolution: 3520 x 1080
Primary Display Size: 17.44" x 9.80" (20.00" diag)
44.3cm x 24.9cm (50.8cm diag)
Primary VRAM: 0 MB
Sound card:
Audio device: Realtek ALC892
Memory:
RAM: 3949 Mb
Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Microphone: Not set
Total Hard Disk Space Available: 229580 Mb
Largest Free Hard Disk Block: 154587 Mb
VR Headset: None detected
Recent Failure Reports:
Fri Sep 9 00:59:00 2016 GMT: file ''/tmp/dumps/crash_20160908175813_6.dmp'', upload yes: ''Discarded=1''
Fri Sep 9 07:02:56 2016 GMT: file ''/tmp/dumps/crash_20160908235934_1.dmp'', upload yes: ''Discarded=1''
Can you please attach one of those .dmp files to this bug? It doesn't appear it was uploaded to our server so I don't have access to it here. Thanks.
generated a new crash. Report
Recent Failure Reports:
Fri Sep 9 18:20:41 2016 GMT: file ''/tmp/dumps/crash_20160909111558_1.dmp'', upload yes: ''CrashID=bp-3e4966e5-e504-48a7-89b5-3e1282160909''
had to upload it as a .zip because github was complaining. Let me know if you need anything else. dumps.zip
Thanks. The crash is happening in scaleform. You didn't mention it in your report, but I see you are running with Vulkan. I presume this does not happen if you disable -vulkan? One other thing you can try is adding +r_overlap_scaleform 0 to your command line. If that fixes the problem, please let me know as it might give me a better clue what is happening.
I checked with OpenGL and it does not happen when using openGL. With -vulkan and +r_overlap_scaleform 0 it does not happen as well. Out of curiousity (and if you have time/want to) why does +r_overlap_scaleform 0 do and what do you think the issue is? Thanks for the good work!
Does this still happen with 7.00?
I just tested it. When loading up a bot match it did not crash when loading (I suspect it is due to the new pregame screen), but loading a replay to watch will still make it crash. I also tried a live game and it did not crash; it seems to have a new startup animation. Let me know if you need anything else from me. Thanks for the hard work. Also this is still running with vulkan (I think I am using the radv driver now).
Hello @JJAYL, the minidump you provided is a crash in libscaleformui_4_vulkan.so.
Yes, and like before it doesn't crash when loading the replay on OpenGL. I also tried with +r_overlap_scaleform 0, but, coincidentally, my desktop froze up. I'll try it again tonight.
I tested it again with +r_overlap_scaleform 0 and it seems to prevent the crash just like it did before 7.00 (for loading replays).
It will stay on the loading screen for about a minute before crashing. This does not seem to happen if I click on the loading screen a few times.