Screen tearing after exiting fullscreen video/applications

I’m using the i3 Community edition, and whenever I enter a fullscreen application, and then exit it again, I get screen tearing, but only after exiting fullscreen, not while in fullscreen mode, and not if I enter fullscreen again (though, of course, it’s still there if I exit a second time).

I’ve had this problem for a while, but always just dealt with it by resetting the refresh rate using the MATE Display settings GUI. Now, that doesn’t appear to do anything, and isn’t working, so I’d like to figure out what’s causing this and, hopefully, solve it, since currently the only way I know (which is far from being the only way, I’m sure, since I know very little about configuring X rendering) is to restart X.

I’m using optimus-manager, so here’s my config and my inxi output:

inxi
System:
  Kernel: 5.8.6-1-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=fcc2a441-7571-4004-82a2-99fa8b35ece1 rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: i3 4.18.2 info: i3bar dm: LightDM 1.30.0 Distro: Manjaro Linux 
Machine:
  Type: Laptop System: Dell product: Inspiron 15 7000 Gaming v: N/A 
  serial: <filter> Chassis: type: 10 serial: <filter> 
  Mobo: Dell model: 065C71 v: A00 serial: <filter> UEFI: Dell v: 1.11.0 
  date: 12/04/2019 
Battery:
  ID-1: BAT0 charge: 47.2 Wh condition: 57.3/74.0 Wh (77%) volts: 12.9/11.1 
  model: Samsung SDI DELL 0GFJ676 type: Li-ion serial: <filter> 
  status: Charging 
CPU:
  Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP 
  arch: Kaby Lake family: 6 model-id: 9E (158) stepping: 9 microcode: D6 
  L2 cache: 6144 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 44817 
  Speed: 900 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 926 2: 900 3: 954 
  4: 956 5: 979 6: 996 7: 984 8: 994 
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
  Type: l1tf 
  mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
  Type: meltdown mitigation: PTI 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, 
  IBRS_FW, STIBP: conditional, RSB filling 
  Type: srbds mitigation: Microcode 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel 
  bus ID: 00:02.0 chip ID: 8086:591b 
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] vendor: Dell 
  driver: nvidia v: 450.66 alternate: nouveau,nvidia_drm bus ID: 01:00.0 
  chip ID: 10de:1c8c 
  Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo 
  bus ID: 1-12:3 chip ID: 0c45:6a06 
  Display: x11 server: X.Org 1.20.8 driver: intel display ID: :0 screens: 1 
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
  s-diag: 582mm (22.9") 
  Monitor-1: eDP1 res: 1920x1080 hz: 60 dpi: 143 size: 340x190mm (13.4x7.5") 
  diag: 389mm (15.3") 
  OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.1.7 
  direct render: Yes 
Audio:
  Device-1: Intel CM238 HD Audio vendor: Dell driver: snd_hda_intel v: kernel 
  bus ID: 00:1f.3 chip ID: 8086:a171 
  Sound Server: ALSA v: k5.8.6-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Dell driver: r8169 v: kernel port: d000 bus ID: 02:00.0 
  chip ID: 10ec:8168 
  IF: enp2s0 state: down mac: <filter> 
  Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel port: d000 
  bus ID: 03:00.0 chip ID: 8086:3165 
  IF: wlp3s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 1.03 TiB used: 114.46 GiB (10.9%) 
  SMART Message: Required tool smartctl not installed. Check --recommends 
  ID-1: /dev/sda vendor: Toshiba model: THNSNK128GVN8 M.2 2280 128GB 
  size: 119.24 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  serial: <filter> rev: 4101 scheme: GPT 
  ID-2: /dev/sdb vendor: Western Digital model: WD10JPVX-75JC3T0 
  size: 931.51 GiB block size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s 
  rotation: 5400 rpm serial: <filter> rev: 1A03 scheme: GPT 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
  v: 3.0 port: f060 bus ID: 00:17.0 chip ID: 8086.282a rev: 31 
Partition:
  ID-1: / raw size: 30.00 GiB size: 29.40 GiB (98.01%) used: 20.63 GiB (70.2%) 
  fs: ext4 dev: /dev/sda4 
  ID-2: /home raw size: 232.83 GiB size: 228.17 GiB (98.00%) 
  used: 93.77 GiB (41.1%) fs: ext4 dev: /dev/sdb3 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 8.27 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 42.0 C mobo: 43.0 C sodimm: 39.0 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 215 Uptime: 19m Memory: 15.38 GiB used: 1.72 GiB (11.2%) 
  Init: systemd v: 246 Compilers: gcc: 10.2.0 clang: 10.0.1 Packages: 1628 
  pacman: 1622 lib: 372 snap: 6 Shell: Bash v: 5.0.18 running in: urxvtd 
  inxi: 3.1.05 
optimus-manager config
[intel]
DRI=3
accel=xna
driver=intel
modeset=no
tearfree=yes

[nvidia]
DPI=
PAT=yes
allow_external_gpus=no
ignore_abi=no
modeset=yes
options=triple_buffer

[optimus]
auto_logout=yes
pci_power_control=yes
pci_remove=no
pci_reset=no
startup_auto_battery_mode=intel
startup_auto_extpower_mode=nvidia
startup_mode=intel
switching=none

Try this:
https://wiki.archlinux.org/index.php/intel_graphics#Tearing

The tearing doesn’t seem to be specific to any one kind of acceleration and I wasn’t using SNA to begin with, but I switched to SNA and tried it anyway. Didn’t work.

Do you experience the tearing on an nvidia-driven or an integrated gpu driven display?

When using Intel graphics. I’m not actually sure if I’ve tested for it using NVIDIA graphics, but since I’m on a laptop, I don’t see using dedicated graphics full time as a viable solution, given the power draw.

Anyone have any other troubleshooting suggestions? Like I said, I’m kind of at a loss, and this is a pretty annoying issue.