I've attached a poll to this thread and its the title says really in that I'm wondering how widespread this issue is.
You go to the top right and click the red 'Close' button, Edge responds by bringing up the expected 'Do you want to close all tabs' window, you click 'Close all' and......... nothing happens.
You then have to either use task manager to close Edge or close each tab individually.
Have you experienced this ?
Quite a few times
Thanks Cliff.
I thought I'd run the poll to get an idea how common this issue was. I've just posted on the MS developer site, which was prompted by MS seemingly brushing somebody off who was reporting similar. Coincidently Edge failed to close while on the MS site and so I grabbed a camera and filmed it
If anyone wants to add a 'me too' or a comment then that would be great.
Edge failing to respond to command. Video attached. - Microsoft Edge Development
I commented on both threads telling the Edge Dev team, what they should already know:I have also had to kill Edge using Task Manager many times
Not good Edge team, not good at all.
Time to take it seriously, and startlooking at the Reliability History uploads.
Just because you can't reproduce it on your systems, doesn't mean it isn't common on others.
That's great, thanks Cliff
Reproduced it first time I tried (use chrome as default browser on this pc). Windows 10 AU with all updates.
I have noticed that its not necessary to use Task manger closing tabs one by one closes edge when final tab is closed, but close all seems to be broken.
Did some testing on VM fresh windows 10 AU with updates problem doesn't occur every time its more like 20%.
After more testing it seems that closing tabs one by one behaves strange too sometimes closing one tab closes all other tabs, sometimes closing tab leaves phantom tab with search field.
As I've said in another thread. Pretty much anyone that uses Edge regularly and closes the browser regularly (funny, but I don't find myself closing the browser very often) will see this problem.
It seems to be related to javascript errors on some pages. So, if you visit the same sites that have errors (they don't always display themselves, you have to open the F-12 tools and look at the console to see them), then you will have the problem more frequently.
It's definitely a bug
I've actually had the issue occur with just two tabs of 'windowssh blog' open. Definitely a bug that needs sorting, and sorting fast.
Has happened to me many times. I've had it happen since before Win 10 went "live" last year. The Edge in the preview versions did/do the same thing.
I was going to ask whether anyone had noticed that this seems to have stopped happening. I then went and checked the status on the reported problem and guess what FIXED. Yay. Well done Microsoft.
