Website freezes when i click on wallpaper preview about themer HOT 12 CLOSED

Thanks for the heads up, @UraniumR —can you tell me which OS and browser you are using?

from themer.

I've got a Ryzen 5 1600 and 16gb of 3200MHz ram underclocked to 3100 for stability reasons with my mobo for now

from themer.

Thanks for the heads up, @UraniumR —can you tell me which OS and browser you are using?

im using : 
Windows 10 OS Version 1803 (Build 17134.1130)
Browser : Vivaldi ( 2.11.1811.52 (Stable channel) (64-bit) )

from themer.

Thanks for that information. Downloading a Windows VM now to see if I can reproduce the issue.

Do you mind sending the full URL where you see the problem, @UraniumR ?

from themer.

@UraniumR still no luck in reproducing the issue on my end—I've added some error tracking through Sentry in hopes that the issue will surface in the wild and give me a clue as to what's going on.

In the meantime, if you run into it again, let me know. As much detail as possible would be most helpful (URL, series of actions taken before opening up the wallpaper preview, any browser extensions you have installed, etc.).

from themer.

Oh, i just went to check out the website , and i have found that the problem have been resolved.
It told me themer have been updated , so i suppose that the last update fixed the problem.
Thanks <3

from themer.

Thanks for the update, @UraniumR !

from themer.

@mjswensen Can we re-open this? I'm running into it on my end.
NixOS 20.03, Chromium browser

from themer.

Yep, @itshaydendev . Can you tell me which wallpaper triggers the issue? I have some theories.

from themer.

All except triangles burst and shirts

from themer.

Thank you! Do you mind me asking how much RAM you have and how fast your CPU is? My best bet right now is that this is a performance issue with inserting a complex SVG into the DOM.

from themer.

Hi folks, I just released an update that converts all wallpaper packages to use PNG format (via canvas) rather than SVG. Since I've never been able to reproduce this issue, I'm hoping that between the format change, using blob URLs rather than data: URLs, and better wrapping of the URL in a useEffect hook, this problem goes away... but please feel free to reopen if not!

from themer.