Chessboard overlay and crash_hadler process issue since the October 5 update (SOLVED)

[Pattern]

Since the update of 5 October, I have a number of problems running the game (Before the upgrade had none of these problems).
1. I have a strange graphic effect, the screen is shaded as a chessboard.
2. During the execution of the game, the CPU of my computer overheats (This did not happen before the upgrade).
3. The game does not close. I have to kill it from the operating system.

Information about the processor:
    CPU Manufacturer: AuthenticAMD
    CPU Brand: AMD FX-8370 Eight-Core Processor
    CPU family: 0x15
    CPU model: 0x2
    Stepping CPU: 0x0
    CPU Type: 0x0
    Speed: 4000 MHz
    logical processors 8
    physical processors: 8
    HyperThreading: Unsupported
    FCMOV: Compatible
    SSE2: Compatible
    SSE3: Compatible
    SSSE3: Compatible
    SSE4a: Compatible
    SSE41: Compatible
    SSE42: Compatible
    AES: Compatible
    AVX: Compatible
    CMPXCHG16B: Compatible
    LAHF / SAHF: Compatible
    PrefetchW: Not compatible
    
Operating system version:
    Debian GNU / Linux 8.6 (jessie) (64 bits)
    Name kernel: Linux
    Kernel version: 3.16.0-4-amd64
    Editor X Server: The X.Org Foundation
    X Server version: 11604000
    X Window Manager: KWin
    Runtime version of Steam: steam-runtime-beta-release_2016-09-02
    
Graphics card:
    Controller: NVIDIA GeForce GTX Corporation 750 / PCIe / SSE2

    Driver version: 4.5.0 NVIDIA 367.44
    OpenGL version: 4.5
    Desktop color density: 24 bits per pixel
    Monitor refresh rate: 60 Hz
    Manufacturer ID: 0x10de
    Device ID: 0x1381
    Review Undetected
    Number of monitors: 1
    Number of logical video cards: 1
    Main Display Resolution: 1920 x 1080
    Desktop Resolution: 1920 x 1080
    Main Screen Size: 18.90 "x 10.63" (21.65 "Diag)
                                            48,0cm x 27,0cm (55,0cm diag)
    Main bus: 16x PCI Express
    Main VRAM memory: 2048 MB
    Supported MSAA Modes: 2x 4x 8x 16x
    
Sound card:
    Sound device: VIA VT2020
    
Memory:
    RAM: 16114 Mb

[Arc]

Post a screenshot of what you see in-game.

Also if your CPU overheats, it means it's not cooled enough, nothing more.

Judging by your other problems, you may check if your system is not blocking or interfering with the game, also verify game files in steam to prevent issues due to corrupted/missing files.

[Oh, my aching tentacles]

I'm also having the chessboard texture overlay. I've had problems with scopes being pink chessboarded before the latest update, and a weird gray square in the top left corner of my screen, since I switched my graphics card to an AMD rx 480 last month.

The pink chessboarded scopes seem to be fixed, but the gray square is still there and on the latest update I have the chessboard overlay.

http://i.imgur.com/hSKpDUK.jpg is a screenshot showing the problem.

I'm running linux with the amdgpu driver.

[Oh, my aching tentacles]

also, it appears if I switch some graphics settings (turning on/off soft particles and then hitting apply, for example), will cause that graphics reset to occur (where you hear the background noise repeat), and then my graphics are 100% fine

[Kvbev]

[Linux] Hang? on exit from crash_handler

When exiting the game (runs great by the way) steam thinks the game is still in a running state, from ps aux this appears its being caused by crash_handler. once I do a killall on crash_handler steam now shows that the game has exited. maybe crash_handler should have a timeout of some sort if it cant do what its trying to do?

Arch Linux
7870 with radeon/radeonsi drivers.
steam-native-runtime installed and steam is ran with included arch steam-native script

term output:

[kvbev@swift ~]$ ps aux | grep insur
kvbev    16867 98.7  0.1  67536 35560 ?        Rl   17:03   0:53 ./crash_handler 16849 http://crash.newworldinteractive.com/api/dumps/submit/insurgency 0 22795 -1
kvbev    16901  0.0  0.0  10760  2224 pts/0    S+   17:04   0:00 grep insur
[kvbev@swift ~]$ killall crash_handler
[kvbev@swift ~]$ ps aux | grep insur
kvbev    16969  0.0  0.0  10760  2224 pts/0    S+   17:10   0:00 grep insur
[kvbev@swift ~]$ 

[Ghost]

Same issue here.

Linux Mint 18 Sarah (Ubuntu 16.04 LTS)

[Oh, my aching tentacles]

Me too, arch without the steam-native-runtime

[KI113R L3M0NZ]

http://pastebin.com/UT8Lfq0G

[botman]

Having the same problem after getting the update. After playing for some time the game automatically exists. I noticed a process "crash_handler" uses 90-100% CPU on a single core.

OS: Ubuntu 16.04 64 bit, Unity
Kernel: 4.4.0-38-generic
CPU: AMD FX 9590 8core x 4.7GHz
RAM 16 GB 1866 MHz
Graphics: Nvidia GTX 750 1 GB DDR5
Nvidia driver version: 367.44 (Using PPA: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa )

[Goodeye]

confirm!

[Goodeye]

Checkerboard pattern after latest update

There is checkerboard pattern all over the screen now
https://s18.postimg.org/l26d4fx15/20161006192602_1.jpg

Ubuntu 16.04
Intel i7-3630QM
Nvidia 650M Mesa 11.2.0
16GB ram

[DECAFBAD]

Temporary solution: find crash_handler (hint: steam/steamapps/common/insurgency2), move it to crash_handler_actual, and run

ln -s /bin/true steam/steamapps/common/insurgency2/crash_handler

[Pattern]

I have been researching my problem. First I checked that I have the latest version of the drivers from my graphic card. Secondly I have validated the cache of the game and it found a file that can not be validated and re-download, but the checkerboard shading remains. Attach the
screenshot (the gray box in the upper left corner is the steam fps counter, ignore this). The screenshot is the same that previuos comment.
As for the other two problems (overheating CPU, and the game does not close properly) are due to a process called 'crash_handler' (insurgency is the father). This process is constantly running from the start of the game and uses 12% of the cpu, probably attached to my refrigerator actually is not the best (neither the worst), it makes that I notice an increase in speed fans and temperature. Before update It was not produced. As for what the game is not closed is also due to this process. It is the process that I have to kill to close the game.

[Zachism]

my game crashes right after it loads and hangs i have to kill it with top.. only did this after the update..

[Pinguinho]

Close the game, but continues running

In Ubuntu 14.04 64bits, when I close the game, their status remains "Running", the CPU remains high activity and the file "crash_handler" is running.

[Zachism]

it's been reported, be sure to look at post before making duplicates.