2021-09-11, 22:31
Hello,
I've noticed an issue where Kodi 19.1 (under Windows 10) will crash when I search for an add-on and the full name isn't matched. I was searching for "Watchedlist" and Kodi crashed each time if I typed in "watched" and pressed enter on the virtual keyboard. This is repeatable and the program crashes each time when I try it with other keywords like "Arctic" as a search for "Arctic Zephyr" for example. I did a search on the forums and it does not appear this has been reported.
1. Version of Kodi: 1.1.0 GIT:20210508-85e05228b4
2. Windows Version: Windows 10 Pro 20H2 (10.0.19042.1165)
3. CPU/Architecture: AMD Ryzen 7 1700X, 3400 MHz
4. RAM amount: 16 GB
5. Detailed Instructions to reproduce the Problem: Enter "add-ons" from menu, enter "search", then type in a word. If the word does not fully match an add-on name, Kodi will crash
6. Details of all devices relevant to the problem: Not applicable
7. FULL Debug Log (see Section 3 below.): Here you go. The stacktrace file has this as its contents if you need it:
Thread 30848 (process 31804)
# 0
I can send the dump file too if you need that.
Thanks,
TD
I've noticed an issue where Kodi 19.1 (under Windows 10) will crash when I search for an add-on and the full name isn't matched. I was searching for "Watchedlist" and Kodi crashed each time if I typed in "watched" and pressed enter on the virtual keyboard. This is repeatable and the program crashes each time when I try it with other keywords like "Arctic" as a search for "Arctic Zephyr" for example. I did a search on the forums and it does not appear this has been reported.
1. Version of Kodi: 1.1.0 GIT:20210508-85e05228b4
2. Windows Version: Windows 10 Pro 20H2 (10.0.19042.1165)
3. CPU/Architecture: AMD Ryzen 7 1700X, 3400 MHz
4. RAM amount: 16 GB
5. Detailed Instructions to reproduce the Problem: Enter "add-ons" from menu, enter "search", then type in a word. If the word does not fully match an add-on name, Kodi will crash
6. Details of all devices relevant to the problem: Not applicable
7. FULL Debug Log (see Section 3 below.): Here you go. The stacktrace file has this as its contents if you need it:
Thread 30848 (process 31804)
# 0
I can send the dump file too if you need that.
Thanks,
TD