Amazon getting harder to browse with Pale Moon

[moonbat]

My uBO looks like this

I don't think it should. All those green colours indicate "manually-allow" actions that shouldn't be there.

He's using it like it's uMatrix. The correct way to troubleshoot an adblocker is to reload the problematic page and observe the logs, then turn off the filterlist that the blocking rules originated from until you can isolate the offending rule. Else 9 out of 10 times it's broken because of overzealous blocking 3rd party content in an age of CDNs. For example, if you visit a country specific Amazon site (AU in my case), they still load content from the main amazon.com and other subdomains. Some names are obvious - like you wouldn't wnt anything from amazon-adsystem.com but then the popular filterlists for uBO already take care of blocking those domains.

[CHris Hitarori]

I don't have problems logging in or ordering, but I can confirm choppy scrolling on amazon.de with Pale Moon 33.9.1 on Windows 11.

It's not the scrolling per se that's choppy, the browser window freezes sometimes for several seconds when I move it around on the screen even when the page has finished loading.

Example: https://www.amazon.de/DIGITUS-Professio ... B001GDPZ0A

On Mac OS X 10.11 El Capitan and macOS 13.x & macOS14.x everything is smooth, though.

[back2themoon]

Example: https://www.amazon.de/DIGITUS-Professio ... B001GDPZ0A

As Marty McFly would say... this is heavy!

[ron_1]

Does anybody have any idea of what I can do or try?

Is it possible that this problem is because my computer is not AVX compatible? I can't think of any other reason why some people (like me) have this problem, and others don't.

[Moonchild]

I have been using Amazon on Pale Moon without issue, even just today.
So I can't reproduce whatever your problem seems to be. Maybe there's a difference between amazon.com (which I hardly ever use since they don't ship abroad from the USA) and other domains local to Europe which I do use (amazon.se and amazon.de) but I don't think there's much difference, if any. Using an adblocker, of course, but I keep it disabled on amazon domains because they require stuff that's often blocked by filter lists for 3rd party site ad integration. If you're using an adblocker on amazon, try disabling it.

[ron_1]

If you're using an adblocker on amazon, try disabling it.

I've tried that. I've tried blocking everything, nothing, and just about everything between those two extremes. Nothing has helped.

[Night Wing]

@ ron_1

If you cannot solve the problem with Amazon, then you just might have to consider using a different browser other than Pale Moon.

[Lucio Chiappetti]

I use amazon.de twice per year to send books to firends in Germany. I used amazon.it only twice (one very recently to buy the smartcard reader <I mentioned in another thread), and never had any problem.

[Gemmaugr]

Using https://themarkup.org/blacklight (options: desktop, forced request/bypass cache) the .com site doesn't show anything amiss at all. The .de site shows canvas fingerprinting present. The .se site shows an ad tracker and canvas fingerprinting.

One could also visit all sites and compare F12 console errors, and check eMatrix for site content present. If one has a VPN, one could furthermore check the sites from Europe and US as well. I could, but I don't use or like Amazon myself.

[ron_1]

I'm thinking maybe something is wrong with my graphics, maybe? Here's the output . . . it might help to know I'm on Linux. The part that concerns me is "X: loaded: modesetting." I seem to recall something not good about "modesetting."

Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: ASUSTeK driver: i915 v: kernel arch: Gen-7.5 ports: active: VGA-1
empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:0402 class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 compositor: marco v: 1.26.2 driver:
X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: VGA-1 model: 100002487 serial: <filter> res: mode: 1920x1080
hz: 60 scale: 100% (1) dpi: 102 size: 476x267mm (18.74x10.51")
diag: 611mm (24") modes: max: 1920x1080 min: 720x400
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
drv: crocus inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.7-2 glx-v: 1.4
direct-render: yes renderer: Mesa Intel HD Graphics (HSW GT1)
device-ID: 8086:0402
Info: Tools: api: eglinfo,glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr

[Night Wing]

it might help to know I'm on Linux.

After reading your recent post I went to Amazon and had no problem getting to the site. In Amazon's search field, I typed in computers and it took me there. I surfed (browsed) lots of different computers. No problems there. No choppy scrolling either. And I too am using Linux.

At the time of this post I am still using 64 bit linux Pale Moon 33.9.1 (GTK2) running in 64 bit MX Linux 25 (Infinity) Xfce. I also had uBlock Origin 1.16.6.1 enabled for Amazon.

EDIT: If you want to see the specifications for my computer, which will also show my graphics card since I am using a desktop tower computer, just say so and I will make another post which will include them.

[back2themoon]

Amazon is overloaded. If your PC is on the lower-end, I'd avoid having multiple Amazon tabs open, especially since they update all changes immediately (basket, lists, anything really). I have a very old system. It struggles with Amazon, but it remains workable with some care.

[frostknight]

Amazon is overloaded. If your PC is on the lower-end, I'd avoid having multiple Amazon tabs open, especially since they update all changes immediately (basket, lists, anything really). I have a very old system. It struggles with Amazon, but it remains workable with some care.

I imagine adblock is part of how you can keep it working, am I right?

That's how I did when I used my X200 thinkpad and X230 one as well.

[Moonchild]

I imagine adblock is part of how you can keep it working, am I right?

I don't really think it's a big part. My workstation isn't super powerful by any stretch (but it's no museum piece, of course) and it has no real issue with Amazon, and as stated I disabled my ad blocker on amazon domains to prevent undesired blocking of amazon "ads" on amazon itself

[ron_1]

Turning on hardware acceleration with the force option also on seems to have helped a bit. After the tab has been loaded for a while (I didn't time it), no more choppiness. I'm sure I had HWA off for a reason but I can't remember what, and haven't come across any issues yet with it on.

[Night Wing]

Turning on hardware acceleration with the force option also on seems to have helped a bit. After the tab has been loaded for a while (I didn't time it), no more choppiness.

I have hardware acceleration turned off in my 64 bit linux Pale Moon 33.9.1 (GTK2) and I have no problems with Amazon.

[Gemmaugr]

To me, as a layman, it seems that only Pale Moon does Hardware Acceleration right, because I have it turned on since long ago and it's all fine.. but.. whenever I tried to turn it on with Brave or Librewolf or even TOR, or some programs like JPixel, weird black & white layers of ..topography.. encircles everything. And those layers move and shift when I press Alt or move the mouse around. Super weird. https://pasteboard.co/4G2u7skMiBVF.png

[Mæstro]

He's using it like it's uMatrix…

Haha, I use µBlock’s advanced mode like ηMatrix.
Hitherto, I have never needed tick the green box; grey has always sufficed. Globally, images are grey, but everything below is red. My regular troubleshooting routine is to greylist first-party scripts, then inline scripts, unless the rendering suggests I should permit cross-site access to CSS or even redlist all resources. This last trick can sort out overlapping text or turn a monster into legible plaintext in one click, quite useful for sites with needless JavaScript dropdown boxes, quite useful for FAQ pages. Giant SVG buttons, like on Mozilla’s site with my default settings, are the worst recurring defect for which i have not yet discovered an easy repair beyond ad hoc µBlock rules.

Else 9 out of 10 times it's broken because of overzealous blocking 3rd party content in an age of CDNs.

Traditionally, Decentraleyes could guard against this. Lately, RealityRipple’s deCDN has instead inherited this march.

I have hardware acceleration turned off in my 64 bit linux Pale Moon 33.9.1 (GTK2) and I have no problems with Amazon.

Years of experience have taught me that hardware acceleration is a good way to bake your processor while throttling anything you are trying to display and nothing else. When it is so painfully, patently bad, it leaves me to wonder why it exists.

[Moonchild]

When it is so painfully, patently bad, it leaves me to wonder why it exists.

But it isn't. Like many things on Linux, YMMV when it comes to hardware acceleration. It works and works well in many cases; in fact, using HWA should actually reduce the load on your hardware because it offloads tasks to the pieces of hardware designed specifically to handle those tasks (i.e. using the GPU in the system for graphics-specific operations like layer compositing etc.). If you notice heavier load on your system when HWA is on, then something is very obviously not right, but what the problem might be is pretty much by definition not within the browser's scope as we are just telling the graphics libraries in use what to do at a pretty high level. That's the whole point of doing it this way. Finding out what the root cause is is almost certainly distro-specific.

Disabling HWA entirely is certainly one approach, but if you feel like tinkering you can try more fine-grained ways of trying to solve whatever the O.S. doesn't like (e.g. switching from XRender to OpenGL, or just flipping off parts of HWA).

[Mæstro]

Like many things on Linux, YMMV when it comes to hardware acceleration… If you notice heavier load on your system when HWA is on, then something is very obviously not right, but what the problem might be is pretty much by definition not within the browser's scope… if you feel like tinkering you can try more fine-grained ways of trying to solve whatever the O.S. doesn't like…

My memory is vague, but I recall hardware acceleration behaving like this even in Firefox ESR in early 2019, before I discovered Pale Moon or used Linux. I can only speculate, but perhaps the usual implementations just never got along with my specific hardware. I am open in principle to tinkering with it to get it to work, in my eternal pursuit of a cooler processor, but you can see from my late posts in the add-ons section and other comments that I have already been tinkering with other things when resting from academic work.