@NorcalScott yeah, the plugin is being pretty simplistic about data fetching atm. It is fetching all results, even though the API is technically separating those into multiple "pages", and then shoving all of them over to the plugin UI layer. Given that, I'm not surprised that it's running into some kind of memory limits or similar.
Given my day job and other responsibilities, afraid trying to optimize that won't be on my priority list any time soon. But, I'm very open to PRs if anyone wants to try contributing improvements.
(Actually, now that I say that... I do have some reason to want to try out some kind of paginated data fetching logic at some point, and this might actually be a useful real-world test case to try building...)
