Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DoD][Mac/Linux] Crash in CreateDebrisWallPuff #1447

Open
danielfpferreira opened this issue Dec 22, 2013 · 4 comments
Open

[DoD][Mac/Linux] Crash in CreateDebrisWallPuff #1447

danielfpferreira opened this issue Dec 22, 2013 · 4 comments

Comments

@danielfpferreira
Copy link

Hi I've been having recurring crashes in-game, in DoD 1.3, for a few days

Steps to reproduce:

  1. enter a an online server
  2. play for a while
  3. crashes after a few minutes, usually between 10 to 45 minutes

CPU and GPU temperatures are normal, around 40ºC

Is someone experiencing the same problem?
Any ideas how to solve it?

Please help. Thank you

latest CrashID=bp-cfdd50cb-1964-44da-b677-ae0242131221

Game Version:

Protocol version 48
Exe version 1.1.2.6/Stdio (dod)
Exe build: 13:14:09 Aug 29 2013 (6153)

System info:

Processor Information:
    Vendor:  GenuineIntel
    CPU Family:  0x6
    CPU Model:  0xf
    CPU Stepping:  0x6
    CPU Type:  0x0
    Speed:  1667 Mhz
    2 logical processors
    2 physical processors
    HyperThreading:  Unsupported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Unsupported
    SSE42:  Unsupported
    
Network Information:
    Network Speed:  

Video Card:
    Driver:  NVIDIA Corporation GeForce Go 7600/PCIe/SSE2

    Driver Version:  2.1.2 NVIDIA 304.116
    OpenGL Version: 2.1
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x10de
    DeviceID:  0x398
    Number of Monitors:  1
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1280 x 800
    Desktop Resolution: 1280 x 800
    Primary Display Size: 13.03" x 8.15"  (15.35" diag)
                                            33.1cm x 20.7cm  (39.0cm diag)
    Primary Bus: PCI Express 16x
    Primary VRAM Not Detected
    Supported MSAA Modes:  2x 4x 8x 16x 
    
Sound card:
    Audio device: Realtek ALC883

Memory:
    RAM:  3007 Mb
    
Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF8
    Microphone:  Not set
    Total Hard Disk Space Available:  46297 Mb
    Largest Free Hard Disk Block:  2829 Mb
    
Installed software:
    
Recent Failure Reports:
    Tue Dec 17 22:25:34 2013 GMT: file ''/tmp/dumps/crash_20131217222528_2.dmp'', upload yes: ''CrashID=bp-1e7037cd-5882-4b90-9b80-c6d702131217''
    Tue Dec 17 22:25:35 2013 GMT: file ''/tmp/dumps/assert_20131217222528_4.dmp'', upload yes: ''CrashID=bp-57edf174-b4d1-4074-b61b-239d42131217''
    Thu Dec 19 22:12:49 2013 GMT: file ''/tmp/dumps/crash_20131219220732_1.dmp'', upload yes: ''CrashID=bp-74893305-8865-47cf-80b8-671672131219''
    Thu Dec 19 23:14:02 2013 GMT: file ''/tmp/dumps/crash_20131219223427_1.dmp'', upload yes: ''CrashID=bp-59398f7c-8209-411a-acf9-11d422131219''
    Thu Dec 19 23:26:22 2013 GMT: file ''/tmp/dumps/crash_20131219231431_1.dmp'', upload yes: ''CrashID=bp-a676b950-72b2-41cd-8d22-c8b922131219''
    Fri Dec 20 00:06:25 2013 GMT: file ''/tmp/dumps/crash_20131219232627_1.dmp'', upload yes: ''CrashID=bp-e206d98f-2b4d-4a93-84de-0ce242131219''
    Fri Dec 20 00:16:10 2013 GMT: file ''/tmp/dumps/crash_20131220000625_1.dmp'', upload yes: ''CrashID=bp-507f154b-efcc-4ff4-a261-a19042131219''
    Fri Dec 20 18:30:39 2013 GMT: file ''/tmp/dumps/assert_20131220182608_1.dmp'', upload yes: ''CrashID=bp-901b5f61-6600-44d0-8c70-24fe72131220''
    Sat Dec 21 22:42:42 2013 GMT: file ''/tmp/dumps/crash_20131221220641_1.dmp'', upload yes: ''CrashID=bp-77908ba6-1e59-4ae1-932b-2076a2131221''
    Sat Dec 21 22:54:40 2013 GMT: file ''/tmp/dumps/assert_20131221224959_1.dmp'', upload yes: ''CrashID=bp-47fc43e7-cdfe-4f79-9882-f13032131221''
    Sat Dec 21 23:36:51 2013 GMT: file ''/tmp/dumps/crash_20131221233236_1.dmp'', upload yes: ''CrashID=bp-4ecb59b6-07ca-4381-8469-2183a2131221''
    Sun Dec 22 00:05:09 2013 GMT: file ''/tmp/dumps/crash_20131221234532_1.dmp'', upload yes: ''CrashID=bp-9f388c65-834d-43d3-ad38-257f22131221''
@SeekingJustice
Copy link

Yes, I have been experiencing the exact same issue. Maybe someone can make sense of the below output.

SPECS: running Debian OS, NFO servers sys_ticrate 10000 -pingboost2 + Shrikebots

Uploading dump (in-process) [proxy '']
/tmp/dumps/crash_20131225062945_1.dmp
success = no
error: Failed to open/read local data from file/application
./exec_dodfunservers.run: line 255: 21566 Segmentation fault (core dumped) $HL_CMD

warning: Could not load shared library symbols for linux-gate.so.1.
Do you need "set solib-search-path" or "set sysroot"?
email debug.log to linux@valvesoftware.com
Wed Dec 25 06:29:47 CST 2013: Server Quit

@danielfpferreira
Copy link
Author

I searched a bit and my crashes seem to be similar or related to this ValveSoftware/steam-for-linux#2327

Definitely the same problem

Backtrace:

Program received signal SIGSEGV, Segmentation fault.
CreateDebrisWallPuff (origin=..., vVelocity=..., vColor=..., iPuff=3)
at ../dod/cl_dll/tri.cpp:734
734 ../dod/cl_dll/tri.cpp: No such file or directory.
(gdb) backtrace
#0 CreateDebrisWallPuff (origin=..., vVelocity=..., vColor=..., iPuff=3)
at ../dod/cl_dll/tri.cpp:734
#1 0xef5ec2a1 in EV_BasicPuff (pTrace=0xffffd360, scale=2.20000005)
at ../dod/cl_dll/ev_hldm.cpp:641
#2 0xef5f04f0 in EV_HLDM_GunshotDecalTrace (pTrace=0xffffd360,
vecSrc=, vecEnd=, iBulletType=16,
decalName=) at ../dod/cl_dll/ev_hldm.cpp:528
#3 0xef5f0c22 in EV_HLDM_DecalGunshot (vecEnd=0xffffd414, vecSrc=0xffffd498,
iBulletType=16, pTrace=0xffffd360) at ../dod/cl_dll/ev_hldm.cpp:1526
#4 EV_HLDM_FireBullets (idx=27, forward=0xffffd4c8, right=0xffffd4bc,
up=0xffffd4b0, cShots=2, vecSrc=0xffffd498, vecDirShooting=0xffffd4a4,
vecSpread=0xffffd4d4, iBulletType=16, iTracerFreq=3,
tracerCount=0xef724808 <tracerCount+104>, flDistance=8192)
at ../dod/cl_dll/ev_hldm.cpp:1695
#5 0xef5f230e in EV_FireMG42 (args=0xf7519434 <cl+1761268>)
at ../dod/cl_dll/ev_hldm.cpp:2031
#6 0xf68a671d in CL_FireEvents () at ../engine/cl_parsefn.c:743
#7 0xf6835d08 in _Host_Frame (time=0.0417026132) at ../engine/host.c:1441
#8 0xf6836142 in Host_Frame (time=0.0417026132, iState=1,
stateInfo=0xffffd63c) at ../engine/host.c:1522
#9 0xf6862654 in CEngine::Frame (this=0xf6a79a80 <g_Engine>)
at ../engine/sys_engine.cpp:245
#10 0xf6860133 in RunListenServer (instance=0x0, basedir=0x804b220 "/home/danii/.local/share/Steam/SteamApps/common/Half-Life/.",
cmdline=0x804e920 "/home/danii/.local/share/Steam/SteamApps/common/Half-Life/./hl_linux -game dod -dev -steam",
postRestartCmdLineArgs=0x804d360 main::szNewCommandParams "",
launcherFactory=0x8049350 <CreateInterfaceLocal(char const*, int*)>,
filesystemFactory=0xf7fc9ad0 <CreateInterface(char const*, int*)>)
at ../engine/sys_dll2.cpp:946
#11 0x08048d67 in main (argc=5, argv=0xffffd874)
at ../launcher/launcher.cpp:439

@kisak-valve kisak-valve changed the title [DoD][Linux] Recurring crashes after a while in-game [DoD][Mac/Linux] Crash in CreateDebrisWallPuff Apr 27, 2017
@SamVanheer
Copy link

Based on the reports i read here and in the other issue at steam-for-linux and given the code in that function, i can only assume that the particle manager is running out of memory and is returning null for a new particle, causing the code to try to access invalid memory.

If anyone encounters this issue again, please run the game with +developer 2 -condebug at the command line. When the game crashes, check Half-Life/qconsole.log for this message:
Particleman is out of memory, too many particles

If you see this as one of the last lines, it means the particle system ran out of memory and returned null.

Note that qconsole.log will contain all console text and is not cleared automatically. Make sure to disable condebug and remove the file so it does not consume too much disk space.

@SamVanheer
Copy link

@mikela-valve Maybe the effects code should gracefully handle out of memory issues to avoid crashes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants