AsyncImage caching delete of images crashes app

Versions

• Python: 3.7.1
• OS: Mac OS Mojave
• Kivy: 1.10.1
• Kivy installation method: pip

Description

I am running the app locally, doing nothing more than simply opening the page where a ‘close.png’ image is used. It is placed in about 20 boxlayouts within a gridview. Then just sit and wait and get the error below.

Code and Logs

[INFO   ] [Base        ] Leaving application in progress...
 Traceback (most recent call last):
   File "/user/home/demo/main.py", line 287, in <module>
     MainApp().run()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/app.py", line 826, in run
     runTouchApp()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/base.py", line 502, in runTouchApp
     EventLoop.window.mainloop()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py", line 727, in mainloop
     self._mainloop()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/core/window/window_sdl2.py", line 460, in _mainloop
     EventLoop.idle()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/base.py", line 337, in idle
     Clock.tick()
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/clock.py", line 581, in tick
     self._process_events()
   File "kivy/_clock.pyx", line 384, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 414, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 412, in kivy._clock.CyClockBase._process_events
   File "kivy/_clock.pyx", line 167, in kivy._clock.ClockEvent.tick
   File "/user/home/anaconda/envs/kivyenv/lib/python3.7/site-packages/kivy/cache.py", line 212, in _purge_by_timeout
     lastaccess = Cache._objects[category][key]['lastaccess']
 KeyError: '<replace_path_to>/image_assets/close.png'

[OutsourcedGuru]

I’m going to demote my earlier suggestion to just:

<AsyncImage>:
    nocache: True

I’m not seeing this for standard Image objects, just AsyncImage.

The problem—when seen—varies in impact from just a WARNING in the log to an unresponsive interface to a cycling interface (as driven by nodm).

[no-response[bot]]

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don’t have the means to take action. Please reach out if you have or find the answers we need so that we can investigate further.