Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Site Can't be Reached' when running :MarkdownPreview #22

Open
tardiobscurus opened this issue Sep 28, 2022 · 2 comments
Open

'Site Can't be Reached' when running :MarkdownPreview #22

tardiobscurus opened this issue Sep 28, 2022 · 2 comments

Comments

@tardiobscurus
Copy link

tardiobscurus commented Sep 28, 2022

versions:

live-server: @compodoc/live-server 1.2.3
pandoc: 2.9.2.1
node: v18.9.1

PS: I have done :MarkdownPreview github and other default themes; still produce the same problem. I've checked if there is an update on node-js, live-server and pandoc. Seems that node-js had some changes, but is minor line changes so no affect on that.

Whenever I run :MarkdownPreview browser shows a connection error of site not being reached (shown image below):
image

It might be from the wrong host using the preview, which is 127.0.0.1 with port 8080. If so, how would I change it in the config file - asking for a friend.

@jakesunplugged
Copy link

I get a similar error. After the initial :MarkdownPreview command, the browser loads and shows the preview. Then, after a time, I get an error saying:

Error detected while processing function 6:
line 3:
[LiveServer] <--- Last few GCs ---> [13195:0x559b799edfc0] 77584 ms: Mark-Compact 2036.8
(2090.4) -> 2030.0 (2091.6) MB, 1235.00 / 0.00 ms (average mu = 0.103, current mu = 0.010) allocation failure; scavenge might not succeed [13195:0x559b799edfc0] 78819 ms: Mark-Compact 2038.0 (2091.6) -> 2031.1 (2092.9) MB, 1222.54 / 0.00 ms (average mu = 0.059, current mu = 0.010) allocation failure; scavenge might not succeed <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

And then the browser gives the error mentioned by OP.

@jtpsh
Copy link

jtpsh commented Oct 11, 2023

I did some investigation here and found live-server starts on the current working directory (where [neo]vim was started). So, if you start [neo]vim in $HOME, live-server will watch every file under it for changes which causes lots of issues and reload non-stop. I have a fix here which restricts the root to temp mount_path: jtpsh@e64c258

Not sure if it will cause some issues but it works well for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants