[Various/all Distros] Numerous Performance & Rendering Issues on 390.25
Hello, NVidia team! After upgrading from 387.34 to 390.25, I am experiencing several performance and rendering issues. These were encountered in the Opera browser: [list] [.]Pictures uploaded or pasted are black ([url]https://youtu.be/IPGavbct_LI[/url])[/.] [.]Scrolling over a website is laggy ([url]https://youtu.be/vVlcdk3JrHc[/url])[/.] [.]Video playback is laggy at the beginning ([url]https://youtu.be/2Q5gIfxNhGU[/url])[/.] [.]Cycling between tabs is delayed by loading ([url]https://youtu.be/6fHKcYptYPg[/url])[/.] [/list] In addition: [list] [.]I can hear my hard drive working incessantly[/.] [/list] None of these issues occur when using version 387.34. Notes: [list] [.]I briefly tried Chrome. web.whatsapp.com was very laggy on 390.25, while being snappy and responsive on 387.34.[/.] [.]However, picture upload/paste worked in Chrome on 390.25.[/.] [/list] PC Specs: [list] [.]GeForce GTX 970[/.] [.]32 GB RAM[/.] [.]Intel i7 4790K[/.] [.]System partition: on SSD[/.] [.]/home partition: on conventional 7200 RPM HDD[/.] [.]Dualboot system with Win 10 and Linux Mint[/.] [/list] This is how far I investigated the issues before rolling back to 387. Since I cannot find a button to attach files here, I have dropboxed the report log: https://www.dropbox.com/s/2pc4j9vu6m9e8sx/nvidia-bug-report.log.gz?dl=0
Hello, NVidia team!

After upgrading from 387.34 to 390.25, I am experiencing several performance and rendering issues. These were encountered in the Opera browser:


In addition:

  • I can hear my hard drive working incessantly

None of these issues occur when using version 387.34.

Notes:
  • I briefly tried Chrome. web.whatsapp.com was very laggy on 390.25, while being snappy and responsive on 387.34.
  • However, picture upload/paste worked in Chrome on 390.25.

PC Specs:
  • GeForce GTX 970
  • 32 GB RAM
  • Intel i7 4790K
  • System partition: on SSD
  • /home partition: on conventional 7200 RPM HDD
  • Dualboot system with Win 10 and Linux Mint

This is how far I investigated the issues before rolling back to 387.

Since I cannot find a button to attach files here, I have dropboxed the report log:

https://www.dropbox.com/s/2pc4j9vu6m9e8sx/nvidia-bug-report.log.gz?dl=0

#1
Posted 02/01/2018 08:23 PM   
When using Chrome, enter chrome://gpu/ to see the state of Chrome hw accel. Might work in Opera, too but I'm not shure about that.
When using Chrome, enter chrome://gpu/ to see the state of Chrome hw accel. Might work in Opera, too but I'm not shure about that.

#2
Posted 02/02/2018 08:43 AM   
Hey generix, thanks for the suggestion! Yes, it works the same way in both browsers. I forgot to mention that I double-checked that as well during the few hours I was on version 390. Acceleration is enabled for everything except: CheckerImaging: Disabled Native GpuMemoryBuffers: Software only. Hardware acceleration disabled Rasterization: Software only. Hardware acceleration disabled This is pretty much the same I've had in the past few years. I wonder if the problem is unrelated to any browser settings? I did have a lot of uninterrupted hard drive activity while I was on 390, though I can't say for sure whether it was also rattling while I didn't have a browser open. I've been back on 387.34 since yesterday and my system runs smoothly.
Hey generix, thanks for the suggestion! Yes, it works the same way in both browsers. I forgot to mention that I double-checked that as well during the few hours I was on version 390. Acceleration is enabled for everything except:

CheckerImaging: Disabled
Native GpuMemoryBuffers: Software only. Hardware acceleration disabled
Rasterization: Software only. Hardware acceleration disabled

This is pretty much the same I've had in the past few years. I wonder if the problem is unrelated to any browser settings? I did have a lot of uninterrupted hard drive activity while I was on 390, though I can't say for sure whether it was also rattling while I didn't have a browser open.

I've been back on 387.34 since yesterday and my system runs smoothly.

#3
Posted 02/02/2018 11:22 AM   
Browser hw accel seems to be normal, then. You could use iotop to see what is thrashing the hdd. Maybe check if the shader cache in ~/.nv gets abnormal high usage.
Browser hw accel seems to be normal, then. You could use iotop to see what is thrashing the hdd. Maybe check if the shader cache in ~/.nv gets abnormal high usage.

#4
Posted 02/02/2018 12:18 PM   
I'm glad someone else has seen this too! I as well have a GTX 970 with 390.25 but I'm not seeing the excessive hard drive usage. I'm also on Mint 18.3. I'm using chromium and will sometimes get black rendered rectangles in web pages and it's very laggy when I scroll. I'm going to drop back to 390.12.
I'm glad someone else has seen this too!

I as well have a GTX 970 with 390.25 but I'm not seeing the excessive hard drive usage. I'm also on Mint 18.3.

I'm using chromium and will sometimes get black rendered rectangles in web pages and it's very laggy when I scroll. I'm going to drop back to 390.12.

#5
Posted 02/02/2018 02:06 PM   
Same problem on my MSI with a GTX970 after the upgrade to 390.12 driers. Linux ming 18.3, chrome is flaky, slow, and choppy. I've turned off hardware acceleration and seem to have things working as expected again.
Same problem on my MSI with a GTX970 after the upgrade to 390.12 driers. Linux ming 18.3, chrome is flaky, slow, and choppy. I've turned off hardware acceleration and seem to have things working as expected again.

#6
Posted 02/02/2018 06:30 PM   
Just to find similarities besides you're all using GTX 970 on Mint, are all of you also using xorg server 1.18.4?
Just to find similarities besides you're all using GTX 970 on Mint, are all of you also using xorg server 1.18.4?

#7
Posted 02/02/2018 07:13 PM   
Thanks for the further suggestions! I will try to find some time today or tomorrow to go back to 390.25 and have a look at iotop and the ~/.nv folder, and to investigate the hard disk thrashing a bit more. It's a busy end of the week here, but when I have more data, I will post back here.
Thanks for the further suggestions! I will try to find some time today or tomorrow to go back to 390.25 and have a look at iotop and the ~/.nv folder, and to investigate the hard disk thrashing a bit more. It's a busy end of the week here, but when I have more data, I will post back here.

#8
Posted 02/02/2018 07:26 PM   
In my case, yes, [i]X.Org X Server 1.18.4[/i] (which you probably knew from the log).
In my case, yes, X.Org X Server 1.18.4 (which you probably knew from the log).

#9
Posted 02/02/2018 07:34 PM   
I'm not very familiar with Xorg or the distinctions between these processes, so I'll only say that these are the processes that mint runs on my GPU: | 0 2046 G /usr/lib/xorg/Xorg 692MiB | | 0 2626 G cinnamon 213MiB |
I'm not very familiar with Xorg or the distinctions between these processes, so I'll only say that these are the processes that mint runs on my GPU:

| 0 2046 G /usr/lib/xorg/Xorg 692MiB |
| 0 2626 G cinnamon 213MiB |

#10
Posted 02/02/2018 08:50 PM   
X -version or head -n5 /var/log/Xorg.0.log
X -version
or
head -n5 /var/log/Xorg.0.log

#11
Posted 02/02/2018 09:09 PM   
Yeah, 1.18.4 (11804000) for my xorg server.
Yeah, 1.18.4 (11804000) for my xorg server.

#12
Posted 02/03/2018 03:15 AM   
Hi there, I'm very glad to see there are other people who have the same problem. I have a GTX 1060, using Mint 18.3 as well, X version 1.18.4 (using an i7 7820, 32 Gb Ram, SSD). Earlier this week I also tried Ubuntu 17.10 and XUbuntu 17.10, and they exhibit the same problem. 387.34 works perfectly, on the other hand.
Hi there,

I'm very glad to see there are other people who have the same problem. I have a GTX 1060, using Mint 18.3 as well, X version 1.18.4 (using an i7 7820, 32 Gb Ram, SSD).

Earlier this week I also tried Ubuntu 17.10 and XUbuntu 17.10, and they exhibit the same problem. 387.34 works perfectly, on the other hand.

#13
Posted 02/03/2018 07:07 PM   
I derped and made a duplicate thread: [url]https://devtalk.nvidia.com/default/topic/1029642/linux/google-chrome-and-firefox-have-bad-hw-acceleration-performance-on-390-25/[/url] Long story short, it's not just Mint that's affected, but something in how Chrome interacts with the system/driver makes the problem manifest. The same issue doesn't seem to manifest in NWJS, which is based on Chromium. For what it's worth, I did not notice the hard drive activity mentioned in the first post.
I derped and made a duplicate thread: https://devtalk.nvidia.com/default/topic/1029642/linux/google-chrome-and-firefox-have-bad-hw-acceleration-performance-on-390-25/

Long story short, it's not just Mint that's affected, but something in how Chrome interacts with the system/driver makes the problem manifest. The same issue doesn't seem to manifest in NWJS, which is based on Chromium.

For what it's worth, I did not notice the hard drive activity mentioned in the first post.

#14
Posted 02/05/2018 11:21 PM   
Same situation for me on Arch Linux with xorg 1.19.6, nvidia 390.25 and kernel 4.15.1. However not only chrome, but also my chromium browser is affected. In addition to this there is also a new bug which breaks vsync as seen on vsynctester.com this makes all video including Netflix unwatchable due to stutter (60 hz instead of correct 59.95 as before). Let me know if you experience stutter (I will be starting a new thread). Hardware is in signature.
Same situation for me on Arch Linux with xorg 1.19.6, nvidia 390.25 and kernel 4.15.1. However not only chrome, but also my chromium browser is affected.

In addition to this there is also a new bug which breaks vsync as seen on vsynctester.com this makes all video including Netflix unwatchable due to stutter (60 hz instead of correct 59.95 as before). Let me know if you experience stutter (I will be starting a new thread). Hardware is in signature.

Dell Precision M4700
Intel QM77 chipset
Core i7 3940XM (with Intel HD4000 graphics)
Nvidia Quadro K2000M (Geforce GT650m equivalent)
16 GB DDR3 1600 ram
Windows 10 Pro 1709
Arch Linux with KDE Plasma

#15
Posted 02/06/2018 08:09 PM   
Scroll To Top

Add Reply