search

Yqnn / svg-path-editor

Online editor to create and manipulate SVG paths
https://yqnn.github.io/svg-path-editor/
Apache License 2.0
4.11k stars 335 forks source link

The editor take a long time to load #77

Closed Whip closed 2 years ago

Whip commented 2 years ago

I'm not sure if its just me or happens to everyone but it takes around 5 minutes for the editor (https://yqnn.github.io/svg-path-editor/) to even start loading. It didn't used to be like this. Can this be resolved?

Yqnn commented 2 years ago

I reproduced that once in Chrome, then I just pressed refresh and it was quick again. The resources of the page are only 500 KB, so even on a slow connection it shouldn't be that long. I guess it was a sporadic issue of Github.

Apart from hosting the page somewhere else than Github, I don't think there is something to do.

Do you still face the issue ? Did you try several browsers ? Or another network ?

Whip commented 2 years ago

Okay I tried using Firefox and it loads instantly so it may be a Chrome specific issue. I also noticed in the status bar, it says "Waiting for play.google.com...". Maybe that gives you a clue.

Yqnn commented 2 years ago

It could be a Chrome plugin that is trying to load something before displaying the page.

According to that reddit post, emptying Chrome caches may resolve the issue.

Whip commented 2 years ago

Disabled all extensions and cleared all cache and cookies. Didn't work. I did find a workaround though, when its endlessly loading, if you press Enter on the URL bar again, it skips whatever it was stuck on and loads the page instantly. Maybe it helps someone.

alexandernst commented 2 years ago

I can repro this from time to time, maybe once a week. Screenshot below.

It seems that it's trying to fetch something from gstatic.com and it's taking an unusual amount of time. The weird thing is that hitting "Esc" to cancel all requests and then hitting "Enter" (while the URL bar is focused) seems to fix the issue (and then I ca't repro it for another week).

Cursor_y_Nueva_pestaña
Yqnn commented 2 years ago

It looks like there is something wrong in the service workers (needed for the PWA setup). I will investigate.

Yqnn commented 2 years ago

I've done a little fix in the PWA setup (for the record: https://stackoverflow.com/questions/55473561/angular-service-worker-ignores-relative-path ).

You may encounter the issue once more (due to PWA cache), then hopefully it should not occur anymore.