Panic: runtime error: invalid memory address or nil pointer dereference

Description of the problem or steps to reproduce

Some sort of race condition or some other weirdness involving tcell makes it so that micro will sometimes crash after resuming from a suspended state. I've mapped ctrl+z to the Suspend action and use it to suspend my text editors often. After switching to micro, sometimes the following occurs:

1. Start micro
2. Type something (or not)
3. Suspend micro
4. Do something random
5. Bring micro back to the foreground
6. Sometimes the error occurs, sometimes it resumes successfully (in which case, repeat from 2)

[1]  + 8807 continued  micro testfile
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x4c pc=0x20b2fc]

goroutine 9 [running]:
github.com/zyedidia/micro/cmd/micro/vendor/github.com/zyedidia/tcell.(*tScreen).PollEvent(0x0, 0x10f7bfe4, 0x0)
        /home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/vendor/github.com/zyedidia/tcell/tscreen.go:801 +0x14
main.main.func5()
        /home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/micro.go:454 +0x34
created by main.main
        /home/zbyedidia/gopath/src/github.com/zyedidia/micro/cmd/micro/micro.go:451 +0x1458

Specifications

Commit hash: af520cf (1.4.0)
OS: Windows (using WSL)
Terminal: Hyper

Start with the goroutine launched in cmd/micro/micro.go around lines 451-454 and inspect the tcell PollEvent call in vendor/github.com/zyedidia/tcell/tscreen.go:801. Reproduce the ctrl+z suspend-and-resume sequence under the reported WSL and Hyper setup; done means micro resumes without the nil-pointer panic.