CoherentUI Crash Nvidia 358.16 (Fedora 23)

I am getting CoherentUI hanging during play with the Nvidia 358.16 Linux driver. The issue is not present on the 352.63 driver, however since Fedora has updated their GCC version to 5.3, this driver is unusable.

Is there an update for CoherentUI coming in the pipeline to resolve these issues again?

Does it make a difference if you use --software-ui or not? Just wondering.
Also since you are saying it just hangs, there is probably no crash report in the logs, but could you take a look in ~/.local/Uber Entertainment/Planetary Annihilation/log anyway to see if there is maybe a hint as to what is breaking? It probably just stops at a certain line, right?

When I say hang, the Coherent process is going into a zombie state

Softwareui mode doesn't crash, however is does behave oddly, selecting units doesn't always work, and mouse dragging gestures don't seem to work


Here is the last few lines of the log

Code:

22:34:23.311] INFO [COUI] Argument conversion failed: Wrong type - expected Integer, got Null while converting argument 0 for handler panel.messageById
[22:34:23.765] INFO setMusic /Music/Music_Planet_Load_Tropical
[22:34:23.817] INFO handleLandingZones
[22:34:23.817] INFO {"landing_zones":[{"position":[103,-345,273],"planet_index":1,"radius":72.900001525878906},{"position":[-377,-125,213],"planet_index":1,"radius":72.900001525878906},{"position":[-43,-31,-410],"planet_index":2,"radius":64.799995422363281},{"position":[27,-370,-118],"planet_index":2,"radius":64.799995422363281}]}
[22:34:24.396] INFO [COUI] PID: 20405 | 20753 12:34:24.295197 [20405:20753:WARNING:accelerated_surface_linux_coherent.cc(256)] could not update shared memory image
[22:34:24.526] INFO ClientWorld::updateObservability - Updating [40878]
[22:34:24.538] INFO updateObservability visible hidden mesh 0 0 0
[22:34:24.539] INFO ClientWorld::updateObservability - Updating [40878]
[22:34:24.553] INFO updateObservability visible hidden mesh 0 0 0
[22:34:24.583] ERROR [JS/player_guide] bundle://boot/boot.js:37160: Uncaught TypeError: Cannot read property 'resolve' of undefined
[22:34:24.583] ERROR [JS/player_guide] bundle://boot/boot.js:37160: Uncaught TypeError: Cannot read property 'resolve' of undefined
[22:34:24.675] INFO [COUI] PID: 20405 | 20405 12:34:24.648648 [20405:20405:ERROR:(0)] Not implemented reached in void content::GpuVideoDecodeAccelerator::Initialize(media::VideoCodecProfile, IPC::Message*)HW video decode acceleration not available.
[22:34:34.721] INFO [COUI] PID: 20405 | 20420 12:34:34.670788 [20405:20420:WARNING:gpu_process_host.cc(483)] GPU process crash detected!
[22:34:35.314] ERROR processSaveResult received unexpected save result.
[22:34:39.741] INFO [COUI] PID: 20405 | 20420 12:34:39.698888 [20405:20420:WARNING:gpu_process_host.cc(483)] GPU process crash detected!
[22:34:45.457] INFO sendLandingLocationSelected
[22:34:45.935] INFO [COUI] PID: 20405 | 20420 12:34:45.889409 [20405:20420:WARNING:gpu_process_host.cc(483)] GPU process crash detected!
[22:34:45.935] INFO [COUI] PID: 20405 | 20420 12:34:45.889447 [20405:20420:ERROR:gpu_process_host.cc(511)] GPU process crash limit reached!Rendering will stop on all hardware accelerated pages!

Hello,

I got exactly the same issue.
Today I upgraded my Fedora 22, part of a large upgrade I had xorg-x11-drv-nvidia-1:358.16-1.fc22.x86_64.

Using the 358 driver, PA was really unstable, the ui froze after 5 min into a game, making it completely unplayable.

I then tried with the --software-ui option.
Knowing this mode is not working well on my system :
- no green bullets on top of mex.
- no icons unzooming units.
- black sreen exiting the gui to main menu

However in this mode the ui was not freezing compared to 358.

Finally I downgraded the nvidia driver to a previous version 346, PA is now working fine again with these drivers.
Note : It looks to work as well with 352.

I wanted to open a bug on the tracker but I could not do it (not the credentials for doing it).

I guess, Linux users will have the same issue as soon as they will upgrade to the Nvidia 358 drivers whatever the distribution.

Next driver update might fix is again of course.
I tried to reproduce it with my Kubuntu 14.04 and the xorg-edgers PPA (and friends) but couldn't get it to work in the first place.

I have looked at Nvidia forum, in order to see if 358.16 has similar errors reported. But it seems not.
Should I report a bug to nvidia forum about PA ? To be honest I'm not sure it will help because it is really specific.
What is your opinion about that ?

Yeah, I'm not sure if it will help them track it down if they don't have a code sample triggering it. (If the bug is in the drivers of course, but seems likely). But it obviously won't hurt to post a bug report of course.

You could even post on the Coherent Labs forums as well. They are quite helpful. I looked there for mentions of the 358 drivers, but didn't see any.

I have just posted on the coherent forum.
https://forums.coherent-labs.com/index.php?topic=1043.0

Hopefully it will help.

I've no such issue here on ArchLinux with said driver version. How are you two launching the game?

Launching the game with the steam runtime.

Seems to be identified :
https://devtalk.nvidia.com/default/topic/899924/steam-random-crash-nvidia-358-16-related-/#4770032

So, had and luck with v361.18 (beta)?