Ad blocker logs spam {filter list regex errors in syslog}
-
I enabled ad blocking by default on vivaldi 3.0.1874.32, and now my syslog is 17MB in just 7 hours. Now there are a lot of logs about an unsupported regex:
../../chromium/third_party/re2/src/re2/re2.cc:194: Error parsing '^https?:\/\/([0-9a-z\-]+\.)?(animeland|animenova|animeplus|animetoon|animewow|gamestorrent|goodanime...': invalid perl operator: (?! ../../chromium/third_party/re2/src/re2/re2.cc:799: Invalid RE2: invalid perl operator: (?!
So far, over 7 hours of no browsing (during the night) I have 16MB of additional logs compared to a pre-vivaldi 3 day.
It it possible to make this error silent at least? I tried importing the list manually and deleting the line causing issue and I could see the list is parsed and rules are ignored if there is an issue, can you make sure regex unsupported are ignored?
Thank you!
-
@Gwen-Dragon thanks, just did, issue VB-66583
-
Seeing the same in Ubuntu 18.04 with the latest Vivaldi snapshot, which I have set to use the built-in content blocker.
-
Same in Solus all up-to-date
-
Confirming in:
$ uname -a Linux sofa-example-co-uk 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/issue Ubuntu 18.04.4 LTS \n \l $ vivaldi --version Vivaldi 3.0.1874.32
And some rather impressive log counts per second...
# grep chromium/third_party/re2/src/re2/re2.cc syslog | cut -c-16 | uniq -c | tail -n40 2 May 6 11:58:34 2 May 6 11:58:40 2 May 6 11:58:44 2 May 6 11:59:02 2 May 6 11:59:04 2 May 6 11:59:11 2 May 6 11:59:26 2 May 6 11:59:34 2 May 6 11:59:38 2 May 6 11:59:44 2 May 6 12:00:04 2 May 6 12:00:18 2 May 6 12:00:19 6 May 6 12:00:27 38 May 6 12:00:28 6 May 6 12:00:29 2 May 6 12:00:31 4 May 6 12:00:33 2 May 6 12:00:34 2 May 6 12:00:44 2 May 6 12:00:46 2 May 6 12:00:47 2 May 6 12:00:51 2 May 6 12:00:59 4 May 6 12:01:00 2 May 6 12:01:04 2 May 6 12:01:10 2 May 6 12:01:11 2 May 6 12:01:22 2 May 6 12:01:23 2 May 6 12:01:34 2 May 6 12:01:44 2 May 6 12:02:04 10 May 6 12:02:18 8 May 6 12:02:19 42 May 6 12:02:20 4 May 6 12:02:21 2 May 6 12:02:33 2 May 6 12:02:34
-
Is there some temporary fix we can make until 'invalid perl operator' is resolved?
-
This is also happening very, very frequently for me. Going from ad blocking & tracking to only tracking resolved it for me (I'm using a pihole so luckily it doesn't matter).
This may seem trivial for product prioritization but I can bet that for every person that registered to send one of these reports there are many more that didn't and just stopped using the browser because their logs were being inundated.
-
@Gwen-Dragon yes Ubuntu 20 indeed. Sorry I forgot to mention it at the beginning!
-
I can confirm. I'm on Debian 10 and I'm getting these errors logged into syslog. Just noticed it two days ago because I was in there looking for something else and had to dig through a lot of anime* noise. Not sure how long it's been going on for.
Is there a workaround that doesn't involve turning off ad-block?
I noticed nod_ mentioned a bug report, VB-66583. I can't for the life of me find where I can look up bugs for Vivaldi. Seems like they would make this readily available. I found where to report a bug (oddly, I couldn't find a link to this in vivaldi.com or vivaldi.net. I had to do an internet search for it. I find this silly.
Linux box 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
Vivaldi 3.1.1929.34
-
@HuckleSmothered said in Ad blocker logs spam {filter list regex errors in syslog}:
Seems like they would make this readily available.
Nope. Vivaldi Bug list is closed. Although we do have a thread for enquiry/updates
https://forum.vivaldi.net/topic/27450/what-is-the-status-of-vb-already-reported-bug-issueI had to do an internet search for report a bug
It's under Help (in the menu).
-
@daveman1010220 said in Ad blocker logs spam {filter list regex errors in syslog}:
Is there some temporary fix we can make until 'invalid perl operator' is resolved?
If you are using rsyslogd, you can tell it to ignore those lines.
- Create /etc/rsyslog.d/20-vivaldi.conf:
# Discard messages caused by unsupperted regex (Vivaldi / Chromium) # See https://forum.vivaldi.net/post/364460 if $msg contains "invalid perl operator: (?!" then ~ & stop
- Restart rsyslogd service:
$ sudo systemctl restart rsyslog.service
Should you want to check the syntax before restarting rsyslogd, you can do that with:
$ sudo rsyslogd -N1 -f /etc/rsyslog.d/20-vivaldi.conf
Please let us know how it went. Rsyslogd syntax was changed at some point, so I'm not 100% sure that does the trick. If not, we'll figure it out
-
-