Error: Process Player crashed with trace

[L40S38]

Hello.
When I tried to watch the data recorded with Pupil Capture in Pupil Player on my Windows PC , I encountered the error below.
(my version is v3.5.1)

Traceback (most recent call last):
  File "surface_tracker\surface_offline.py", line 86, in update_location
TypeError: 'NoneType' object is not subscriptable

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "launchables\player.py", line 722, in player
  File "surface_tracker\surface_tracker_offline.py", line 289, in recent_events
  File "surface_tracker\surface_tracker.py", line 432, in recent_events
  File "surface_tracker\surface_tracker_offline.py", line 372, in _update_surface_locations
  File "surface_tracker\surface_offline.py", line 90, in update_location
  File "surface_tracker\surface_offline.py", line 196, in _recalculate_location_cache
  File "surface_tracker\background_tasks.py", line 140, in background_data_processor
  File "background_helper.py", line 49, in __init__
  File "multiprocessing\process.py", line 105, in start
  File "multiprocessing\context.py", line 322, in _Popen
  File "PyInstaller\hooks\rthooks\pyi_rth_multiprocessing.py", line 72, in __init__
  File "multiprocessing\popen_spawn_win32.py", line 65, in __init__
  File "multiprocessing\reduction.py", line 60, in dump
BrokenPipeError: [Errno 32] Broken pipe

player - [INFO] launchables.player: Process shutting down.

The list of things I tried to fix this error is below:
・Reinstall pupil labs
・Shutdown and Restart the PC
・Shutdown the other applications as many as possible when I launch Pupil Player
・Replay the sample record data on https://github.com/pupil-labs/pupil-tutorials/blob/master/01_load_exported_data_and_visualize_pupillometry.ipynb (It was suceeded, but I still encounter errors with other data)

In addition, I would like to replay the data that was viewable using Pupil Player on another Windows PC but suddenly became unviewable on my PC, so it is more likely that the problem is with the settings on the PC rather than with the data.