Receiving frequent query timeouts caused by frequent window title changes

[nicolae-stroncea]

I've been getting an increasing amount of timeouts with the message:

Console:

Mounting aw-periodusage PeriodUsage.vue:26
Mounting aw-summary
Summary.vue:22
Mounting aw-timeline TimelineInspect.vue:22
Mounting aw-sunburst Sunburst.vue:118
Mounting aw-timeline TimelineInspect.vue:22
Mounting aw-summary
Summary.vue:22
Error: "timeout of 10000ms exceeded"
exportshttp://localhost:5600/static/js/0.f288d34cc371f7d2215c.js:40:248389
ontimeouthttp://localhost:5600/static/js/0.f288d34cc371f7d2215c.js:40:249607
errorHandler Activity.vue:357

Identical issue is happening in both Chrome and Firefox. For the past hour, i've not been able to view my data because of it.

[ErikBjare]

The console output you've provided is not enough to debug this issue. Please attach full and properly formatted logs from aw-server and the JS console for the web UI.

[ErikBjare]

I'm assuming this has to do with the queries taking too long to run. Do you have a fast computer? How many events do you have in your buckets?

[nicolae-stroncea]

My computer is fairly fast. The main issue was the number of events logged in

[ErikBjare]

@nicolae-stroncea Please tell us the number of events you have in each bucket.

It really shouldn't take more than 10 seconds, perhaps you have a window title that changes unusually many times in a day? That could significantly slow down the calculation.

[nicolae-stroncea]

Watcher-afk: 55
Watcher-window:13081
Watcher-web-firefox:2964
Watcher-web-chrome:998

You're right. I looked further into watcher-window, since it has a very large number of events. Of those 13081, 10130 events are only two alternating events over a period of 4 hours:
first one is{"app": "firefox.exe", "title": "(1) Facebook - Mozilla Firefox"}(duration:
second one is: {"app": "firefox.exe", "title": "X person messaged you - Mozilla Firefox"}.

I looked further into it, and this started on the previous day. These are the last events before:
{"app": "firefox.exe", "title": "(3) YouTube - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Webpage of blog T - Mozilla Firefox"}
{"app": "firefox.exe", "title": "(1) Webpage of blog T - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Webpage of blog T - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Mozilla Firefox"}
{"app": "firefox.exe", "title": "(1) Facebook - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Y messaged Facebook Group- Mozilla Firefox"}
{"app": "firefox.exe", "title": "(1) Facebook - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Facebook - Mozilla Firefox"}
{"app": "firefox.exe", "title": "(1) Facebook - Mozilla Firefox"}
{"app": "firefox.exe", "title": "X person messaged you - Mozilla Firefox"}
{"app": "firefox.exe", "title": "(1) Facebook - Mozilla Firefox"}
{"app": "firefox.exe", "title": "X person messaged you - Mozilla Firefox"}

These are the events that took place before it stopped. It could have stopped because I closed aw-qt,
I don't remember.

50 alternating events like this(happening over 1 minute):
{"app": "firefox.exe", "title": "Person X messaged you - Mozilla Firefox"}
{"app": "firefox.exe", "title": "Facebook - Mozilla Firefox"}(not sure if the lack of (1) is important).
The final event was this:
{"app": "firefox.exe", "title": "Facebook - Mozilla Firefox"} with a duration of 3139.859 seconds.
3139 seconds later, a new event starts, and the database starts recording things normally:
{"app": "SearchUI.exe", "title": "Cortana"}

I think the bug is most likely the Facebook blinking title notification when you get a message. I've found the same problem on other days as well, but to a lesser extent.

[ErikBjare]

Ah yes, having the window title change like that is likely the cause if the issue. I'm not sure if there's a good workaround though (apart from improving query performance), what do you think @johan-bjareholt? (He won't reply in a couple of weeks as he's on vacation, unfortunately)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ErikBjare]

This should not be a problem in the latest release which has much improved queries. Closing.