Roon search stopped working for certain keywords after the 2.0 update. (ref#ORQX42)

Support
1

Affected Product

Roon

Roon Issue Category

Interface & Usability

Description of Issue

roon search stopped working for some keywords after updating to 2.0.

Roon Server Platform

Windows

Roon Server Specifications

Windows 11 latest version
13900K
32G Ram

Home Network Details

Wi-Fi

Screenshot

related logs:

12/03 15:09:50 Debug: UI-NAV: search / terms: Xenoblade Chronicles  / mode:  / bookmarkdata: 
12/03 15:09:50 Debug: GMS: done saving nav stack
12/03 15:09:52 Trace: [search] instant search event expired. Event source: ENTER_PRESSED
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/ojwoaaaa.512.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/ojwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/jmwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/imwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/nmwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/mmwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/lmwoaaaa.256.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/ojwoaaaa.128.jpg
12/03 15:09:52 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/pjwoaaaa.128.jpg
12/03 15:09:52 Debug: [easyhttp] [12] GET to http://127.0.0.1:9330/image/imwoaaaa.256.jpg returned after 11 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Debug: [easyhttp] [17] GET to http://127.0.0.1:9330/image/pjwoaaaa.128.jpg returned after 9 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Debug: [easyhttp] [9] GET to http://127.0.0.1:9330/image/ojwoaaaa.512.jpg returned after 15 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Debug: [easyhttp] [15] GET to http://127.0.0.1:9330/image/lmwoaaaa.256.jpg returned after 11 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Debug: [easyhttp] [14] GET to http://127.0.0.1:9330/image/mmwoaaaa.256.jpg returned after 11 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Debug: [easyhttp] [11] GET to http://127.0.0.1:9330/image/jmwoaaaa.256.jpg returned after 12 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/imwoaaaa.256.jpg etag=8ecedd8b89cc712f2990f5ba3036bd65789e3fed expiration=12/5/2023 8:53:51 AM
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/lmwoaaaa.256.jpg etag=ab836f10d7232b1d9508b3ea69efe9efb955e5f3 expiration=12/5/2023 8:53:52 AM
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/pjwoaaaa.128.jpg etag=55bc2cbf8bc18d2a4be5103e8b706f08eba44b79 expiration=12/5/2023 8:53:51 AM
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/ojwoaaaa.512.jpg etag=ea21769f7d55bd196c741f787a579b33310b7baa expiration=12/5/2023 8:53:51 AM
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/mmwoaaaa.256.jpg etag=9b9ae8116e8abdef5a9272012397ca1b7b117a1d expiration=12/5/2023 8:53:51 AM
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/jmwoaaaa.256.jpg etag=112c039fafd342d363b79d7f26caf98c6bb20af6 expiration=12/5/2023 8:53:51 AM
12/03 15:09:52 Debug: [easyhttp] [16] GET to http://127.0.0.1:9330/image/ojwoaaaa.128.jpg returned after 502 ms, status code: 200, request body size: 0 B
12/03 15:09:52 Info:   ==> 200
12/03 15:09:52 Trace: [broo/images] caching http://127.0.0.1:9330/image/ojwoaaaa.128.jpg etag=ea21769f7d55bd196c741f787a579b33310b7baa expiration=12/5/2023 11:09:52 PM
12/03 15:09:52 Warn: AddTopLevel: popup_search(3034)
12/03 15:09:53 Debug: [easyhttp] [10] GET to http://127.0.0.1:9330/image/ojwoaaaa.256.jpg returned after 608 ms, status code: 200, request body size: 0 B
12/03 15:09:53 Info:   ==> 200
12/03 15:09:53 Trace: [broo/images] caching http://127.0.0.1:9330/image/ojwoaaaa.256.jpg etag=ea21769f7d55bd196c741f787a579b33310b7baa expiration=12/5/2023 11:09:53 PM
12/03 15:09:53 Debug: [easyhttp] [13] GET to http://127.0.0.1:9330/image/nmwoaaaa.256.jpg returned after 965 ms, status code: 200, request body size: 0 B
12/03 15:09:53 Info:   ==> 200
12/03 15:09:53 Trace: [broo/images] caching http://127.0.0.1:9330/image/nmwoaaaa.256.jpg etag=d3b56f00d3f772b618c23db75912ac07d63b9134 expiration=12/5/2023 11:09:54 PM
12/03 15:09:54 Info: EASYHTTP FETCH http://127.0.0.1:9330/image/pjwoaaaa.256.jpg
12/03 15:09:54 Debug: [easyhttp] [18] GET to http://127.0.0.1:9330/image/pjwoaaaa.256.jpg returned after 648 ms, status code: 200, request body size: 0 B
12/03 15:09:54 Info:   ==> 200
12/03 15:09:55 Trace: [broo/images] caching http://127.0.0.1:9330/image/pjwoaaaa.256.jpg etag=55bc2cbf8bc18d2a4be5103e8b706f08eba44b79 expiration=12/5/2023 11:09:54 PM
12/03 15:09:58 Trace: [search] instant search event expired. Event source: ENTER_PRESSED
12/03 15:09:58 Debug: UI-FWD: mode: unifiedsearch
12/03 15:09:58 Debug: GMS: saving nav stack
12/03 15:09:58 Debug: UI-NAV: search / terms: Xenoblade / mode:  / bookmarkdata: 
12/03 15:09:58 Debug: GMS: done saving nav stack
12/03 15:09:59 Trace: [search] instant search event expired. Event source: ENTER_PRESSED
12/03 15:10:00 Info: [stats] 2102884mb Virtual, 316mb Physical, 63mb Managed, 1235 Handles, 49 Threads
12/03 15:10:01 Trace: [search] instant search event expired. Event source: ENTER_PRESSED
12/03 15:10:06 Debug: UI-FWD: mode: settings
3

Try rebooting the network and PC and see if that helps.

4

no, it doesn’t. i’ve tried rebooting, reinstalling the server/client, using different clients, and a few other things, but no luck

i’ve also tried different keywords, and i think i’ve come to the conclusion that it’s probably related to some memory cap you’ve set in search. this appears to be the case since only those keywords that could match albums with tons of cds eventually result like this. for example, i have this “Xenoblade Trinity Box” ,a collection of 20 cds. when i try to search for “xenoblade,” i get a “can’t connect to roon search” error. however, when i search for “xenoblade chronicles,” there’s no error, but i don’t see this album in the results. this is true for other albums that contain 20 or more cds.

if you need any more logs or tests from my end, i’m happy to help.

5

I’m a fellow user like yourself. Although, Xenoblade search works for me, but I don’t have that album in my library. However, I have other 20+ CD albums in my library and title keyword searches bring them up with no issue.

My large album sets are Identified by Roon, so if you have large sets which are Unidentified, that may be a trigger.

Support is Mon-Fri so they will probably check in then and can let you know if they want/need logs.

6

i’ve recently rebuilt my entire roon database from scratch (didn’t restore any backups). interestingly enough, before i merged my huge anthologies and collections (with 100+ CDs each), the search function worked perfectly fine. but after i merged those albums, the search function has been glitching since.

Cannot search for David Bowie - Support - Roon Labs Community

also, it seems like others have had similar experiences in the above topic and we can safely assume that the search function is currently experiencing issues for some unknown reasons. i believe the roon dev team needs to conduct comprehensive testing to address this issue, since the search function is so vital for large music collections in roon.

7

Hi @Google,

Thank you for the report and we’re sorry to hear that you’re experiencing frustrating symptoms around search.

Development is investigating this issue directly in the attached thread. Please follow this thread and post there if you have any new symptoms. There are efforts behind the scenes to isolate and resolve performance issues in search. Roon search worsened after last server update build 1353 - #47 by connor