Gzdoom just hard crashed for the second time

[Rowsol]

I used 4.3.3 for what seemed like years with no issues aside from mods erroring out, showing the crash log as a result.
Since updating to 4.7.1 I've now had 2 random freezes. I wait about 10 seconds and the program closes out, no prompt or anything.
They are rare. I've put in probably 20 hours, so I'd guess it's about once per 10 hours of play.
I've looked at my mod list and nothing jumps out as I'm using all the same stuff I always have.
If the freezes could be reproduced I would have something to go on.
Does gzdoom have a way of logging things like this?

[Kappes Buur]

When no crash report is generated then you have the option to generate a logfile with the

Code: Select all

+logfile logfilename.txt

command to get at least some information. I have this included in the autoexec.cfg file. However, I do not know if this happens for others, this only records the apps section. for example:

Code: Select all

Log started: 2022-02-11 15:19:31
GZDoom version g4.8pre-127-g0d8d4a2ad
M_LoadDefaults: Load system defaults.
Using program directory for storage
W_Init: Init WADfiles.
 adding D:/DOOM/ENGINES/GZDOOM/gzdoom-4.8/gzdoom-x64-g4.8pre-127/gzdoom.pk3, 667 lumps
 adding D:/DOOM/ENGINES/GZDOOM/gzdoom-4.8/gzdoom-x64-g4.8pre-127/game_support.pk3, 2514 lumps
 adding D:/PWAD_EDITING/IWADS/DOOM2.WAD, 2919 lumps
 adding D:/DOOM/ENGINES/GZDOOM/gzdoom-4.8/gzdoom-x64-g4.8pre-127/lights.pk3, 7 lumps
 adding D:/DOOM/ENGINES/GZDOOM/gzdoom-4.8/gzdoom-x64-g4.8pre-127/brightmaps.pk3, 499 lumps
 adding D:/DOOM/ENGINES/GZDOOM/gzdoom-4.8/gzdoom-x64-g4.8pre-127/game_widescreen_gfx.pk3, 214 lumps
 adding D:/IWADS/bmplus_spritefix.pk3, 2962 lumps
 adding D:/IWADS/bmplus_textures.pk3, 303 lumps
 adding D:/OBSIDIAN/MAPS_GZDoom/2021-2-16-2047_raging_death_and_grief.wad, 1351 lumps
sv_cheats will be changed for next game.
Log stopped: 2022-02-11 15:19:31

To complete the logfile I also run a bat file with this:

Code: Select all

D:\DOOM\ENGINES\GZDOOM\gzdoom-4.8\gzdoom-x64-g4.8pre-127\gzdoom.exe -iwad DOOM2.WAD -FILE %1 ..\Beautiful_Doom_716.pk3 +logfile run.txt

to record what GZDoom is doing, which gives me this:

Code: Select all

Log started: 2022-02-11 15:19:31
I_Init: Setting up machine state.
CPU speed: 3693 MHz
CPU Vendor ID: AuthenticAMD
  Name: AMD Ryzen 5 5600X 6-Core Processor 
  Family 25 (25), Model 33, Stepping 0
  Features: SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX AVX2 F16C FMA3 BMI1 BMI2 HyperThreading
V_Init: allocate screen.
S_Init: Setting up sound.
I_InitSound: Initializing OpenAL
  Opened device OpenAL Soft on Speakers (High Definition Audio Device)
  EFX enabled
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
script parsing took 109.66 ms
R_Init: Init Doom refresh subsystem.
DecalLibrary: Load decals.
Adding dehacked patch 2021-2-16-2047_raging_death_and_grief.wad:DEHACKED
Patch installed
M_Init: Init menus.
P_Init: Init Playloop state.
ParseSBarInfo: Loading custom status bar definition.
D_CheckNetGame: Checking network game status.
player 1 of 1 (1 nodes)
I_InitInput
I_StartupMouse
I_StartupKeyboard
I_StartupXInput
I_StartupRawPS2
I_StartupDirectInputJoystick
Vulkan device: NVIDIA GeForce GTX 660
Vulkan device type: discrete gpu
Vulkan version: 1.2.175 (api) 472.48.0 (driver)
Vulkan extensions: VK_KHR_16bit_storage VK_KHR_8bit_storage VK_KHR_bind_memory2 VK_KHR_buffer_device_address VK_KHR_copy_commands2 VK_KHR_create_renderpass2 VK_KHR_dedicated_allocation VK_KHR_depth_stencil_resolve VK_KHR_descriptor_update_template VK_KHR_device_group VK_KHR_draw_indirect_count VK_KHR_driver_properties VK_KHR_external_fence VK_KHR_external_fence_win32 VK_KHR_external_memory VK_KHR_external_memory_win32 VK_KHR_external_semaphore VK_KHR_external_semaphore_win32 VK_KHR_get_memory_requirements2 VK_KHR_image_format_list VK_KHR_imageless_framebuffer VK_KHR_maintenance1 VK_KHR_maintenance2 VK_KHR_maintenance3 VK_KHR_multiview VK_KHR_pipeline_executable_properties VK_KHR_push_descriptor VK_KHR_relaxed_block_layout VK_KHR_sampler_mirror_clamp_to_edge VK_KHR_sampler_ycbcr_conversion VK_KHR_separate_depth_stencil_layouts VK_KHR_shader_clock VK_KHR_shader_draw_parameters VK_KHR_shader_float16_int8 VK_KHR_shader_float_controls VK_KHR_shader_non_semantic_info VK_KHR_shader_subgroup_extended_types VK_KHR_shader_terminate_invocation VK_KHR_spirv_1_4 VK_KHR_storage_buffer_storage_class VK_KHR_swapchain VK_KHR_swapchain_mutable_format VK_KHR_synchronization2 VK_KHR_timeline_semaphore VK_KHR_uniform_buffer_standard_layout VK_KHR_variable_pointers VK_KHR_win32_keyed_mutex VK_KHR_workgroup_memory_explicit_layout VK_KHR_zero_initialize_workgroup_memory VK_EXT_4444_formats VK_EXT_buffer_device_address VK_EXT_calibrated_timestamps VK_EXT_color_write_enable VK_EXT_conditional_rendering VK_EXT_custom_border_color VK_EXT_depth_clip_enable VK_EXT_depth_range_unrestricted VK_EXT_descriptor_indexing VK_EXT_discard_rectangles VK_EXT_extended_dynamic_state VK_EXT_extended_dynamic_state2 VK_EXT_external_memory_host VK_EXT_full_screen_exclusive VK_EXT_hdr_metadata VK_EXT_host_query_reset VK_EXT_image_robustness VK_EXT_index_type_uint8 VK_EXT_inline_uniform_block VK_EXT_line_rasterization VK_EXT_memory_budget VK_EXT_memory_priority VK_EXT_pci_bus_info VK_EXT_pipeline_creation_cache_control VK_EXT_pipeline_creation_feedback VK_EXT_private_data VK_EXT_provoking_vertex VK_EXT_robustness2 VK_EXT_scalar_block_layout VK_EXT_separate_stencil_usage VK_EXT_shader_demote_to_helper_invocation VK_EXT_shader_subgroup_ballot VK_EXT_shader_subgroup_vote VK_EXT_subgroup_size_control VK_EXT_texel_buffer_alignment VK_EXT_tooling_info VK_EXT_transform_feedback VK_EXT_vertex_attribute_divisor VK_EXT_vertex_input_dynamic_state VK_EXT_ycbcr_image_arrays VK_NV_acquire_winrt_display VK_NV_dedicated_allocation VK_NV_dedicated_allocation_image_aliasing VK_NV_device_diagnostic_checkpoints VK_NV_device_diagnostics_config VK_NV_device_generated_commands VK_NV_external_memory VK_NV_external_memory_win32 VK_NV_inherited_viewport_scissor VK_NV_shader_sm_builtins VK_NV_shader_subgroup_partitioned VK_NV_win32_keyed_mutex VK_NVX_multiview_per_view_attributes
Max. texture size: 16384
Max. uniform buffer range: 65536
Min. uniform buffer offset alignment: 256
Resolution: 1920 x 1051

----------------------------------------

MAP01 - Pain

Give that a try.

[Enjay]

and, if you use a launcher, there is probably a way to add the instruction to the command line within the launcher. I use this all the time:

[Rowsol]

Okay, thanks for the help. I got the log to show up by creating a shortcut to the exe and adding that argument to the target line. Maybe there should be an easier way of doing this, like say an option in gzdoom itself.