Error while accessing https://www.voidlinux.eu/packages/

[Hoshpak]

When I'm accessing https://www.voidlinux.eu/packages/ and use the search box on the page in qupzilla 2.0.1 it searches for a few seconds (in Chrome it shows that the browser does some get requests e.g. to https://repo.voidlinux.eu/current/musl/debug/ in the meantime) and then redirects to an error page stating "Seite konnte nicht geladen werden" (Page could not be loaded). I couldn't really figure out what happens there. The address bar shows that I'm still on the same page and I can reload the page just fine. However if I enter some search term again, the same error occurs again of course.

[lupinix]

Works fine for me, setup is QupZilla 2.0.1, QtWebEngine 5.6.1, Fedora 24.

[ghost]

I just have SSL Sertificate Error

[Hoshpak]

@lupinix That's interesting. Since the versions are the same, it seems to come down to the way the binaries or library dependencies are built rather than the code itself. I just tried accessing the page again while running qupzilla from a terminal emulator to possibly capture error output I might have missed earlier, this was the result:

<--- Last few GCs --->

   15699 ms: Scavenge 1473.0 (1517.2) -> 1473.1 (1517.2) MB, 3.1 / 0 ms (+ 0.3 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
   15737 ms: Mark-sweep 1473.1 (1517.2) -> 1473.1 (1515.2) MB, 37.2 / 5 ms (+ 5.7 ms in 7 steps since start of marking, biggest step 2.3 ms) [last resort gc].
   15768 ms: Mark-sweep 1473.1 (1515.2) -> 1473.0 (1515.2) MB, 31.0 / 4 ms [last resort gc].

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x3e34348837b1 <String[23]: http://www.voidlinux.eu>
    1: exec [native regexp.js:~85] [pc=0x38faae10629e] (this=0x2b11cd9f46b1 <JS RegExp>,k=0x1ab1cf4ef3a9 <Very long string[2970579]>)
    2: handleResponse [http://www.voidlinux.eu/assets/js/voidsearch.js:~33] [pc=0x38faae147608] (this=0x3bbad8bbe371 <an XMLHttpRequest with map 0xc856e271551>)
    3: arguments adaptor frame: 1->0

==== Details =========================...

V8 error: Allocation failed - process out of memory (CALL_AND_RETRY_LAST).  Current memory usage: 1504 MB
1   0x7f0baed071cf
2   0x7f0baed073d0
3   0x7f0baedab24f
4   0x7f0baeefbd8d
5   0x7f0baeebf599
6   0x7f0baeebfa6d
7   0x7f0baeebfb4b
8   0x7f0baf0c6b1b
9   0x38faadd09b7b

I could hardly believe it but testing again while having a watch on "free -m" running and it shows that the process is indeed using the 1.5 GB of RAM that is reported. There is still about 1GB available but I guess it hits some internal memory limit. Rendering the same page in Chromium 53 uses approximately 250 MB, the rest of the browser included.

[ghost]

@Hoshpak, you just beat me for a while. I was going to report that i have the similar error.