Open renatop7 opened 5 years ago
Same here Any solutions?
Oh my gosh, this is happening to me too! Experienced it on the exact same day @renatop7 did, ironically enough. I thought I was going crazy. The whole internet connection went to crap after running ionic serve. Had to fall back to ng serve
, but not after having to restart my computer.
What happens if you try npx ng serve --host=0.0.0.0
?
What happens if you try
npx ng serve --host=0.0.0.0
?
Works just like npx ng serve
Hi all
I get a segmentation fault (core dumped) error every time I try to run ionic after switching branches in my current repository or after stopping the current server.
I get the following result:
`➜ diningcity-assistant git:(issue-2381) ionic serve
ng run app:serve --host=localhost --port=8100 [INFO] Waiting for connectivity with ng... [INFO] Waiting for connectivity with ng... [1] 177 segmentation fault (core dumped) ionic serve`
Doing npx ng serve does not solve it and I get errors as well.
What's really strange is that it works well the first time, it's only after trying to start the server a second time afterwards that it breaks.
For additional information I have found that shutting down the WSL instance and re-starting it is the only way I found to run it again, so I have to do it every single time:
wsl.exe -t ubuntu
Description:
When I try to use
ionic serve
I get the following output:If I use
npx ng serve
it works and I can load my app on my browser.One strange thing is that when I use
ionic serve
it breaks my WSL instance, I can no longer connect to the internet through the terminal, for example, if I try to install some package the connection hangs and never downloads it, until it finally times out.It even mess with my Windows internet connection and I have to restart the WSL container to make it work normally again, it feels like some kind of proxy is acting.
Output:
ionic serve --verbose
My
ionic info
:Other Information:
Win10 - Version 1809