SOLVED

Error 4 and page shutdown on Debian Buster following latest update.

%3CLINGO-SUB%20id%3D%22lingo-sub-2830360%22%20slang%3D%22en-US%22%3EError%204%20and%20page%20shutdown%20on%20Debian%20Buster%20following%20latest%20update.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2830360%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20anybody%20else%20seeing%20this%20problem.%26nbsp%3B%20Some%20pages%2C%20I've%20yet%20to%20work%20out%20any%20pattern%2C%20are%20half-rendering%20then%20the%20page%20is%20closed%20and%20the%20'Error%204'%20message%20displayed.%26nbsp%3B%20This%20happens%20repeatedly%20when%20retrying%20on%20the%20same%20page%20but%20subsequently%20does%20not%20always%20re-occur%20if%20the%20browser%20is%20closed%20and%20restarted.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20has%20started%20happening%20from%20the%20last%20Dev%20update%20a%20few%20days%20ago%20for%20me.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENot%20too%20worried%20as%20these%20things%20come%20and%20go%20but%20since%20I've%20recently%20updated%20to%20Buster%20I%20thought%20I'd%20check%20with%20other%20Debian%20users%20to%20see%20if%20anybody%20experiences%20the%20same.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2839088%22%20slang%3D%22en-US%22%3ERe%3A%20Error%204%20and%20page%20shutdown%20on%20Debian%20Buster%20following%20latest%20update.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2839088%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20there!%20Just%20wanted%20to%20confirm%20that%20we%20haven't%20seen%20any%20other%20reports%20of%20this%20coming%20in%2C%20but%20I'm%20keeping%20an%20eye%20out%20for%20anything%20similar%20in%20case%20it's%20something%20other%20than%20the%20distro%20contributing%20to%20this%20one.%20If%20you%20haven't%20already%2C%20can%20you%20submit%20feedback%20in%20browser%20so%20our%20team%20will%20be%20better%20able%20to%20correlate%20this%20if%20we%20start%20seeing%20more%20reports%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3E%3CI%3EAlex%20Rowell%20(she%2Fher)%3CBR%20%2F%3ECommunity%20Manager%20-%20Microsoft%20Edge%3CBR%20%2F%3EJoin%20us%20on%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D2170823%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETwitter%3C%2FA%3E%2C%20or%20over%20on%20Reddit%20in%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D2170824%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Er%2FMicrosoftEdge%3C%2FA%3E%20or%20%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2F%3Flinkid%3D2170926%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Er%2Fedge%3C%2FA%3E%3C%2FI%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2839685%22%20slang%3D%22en-US%22%3ERe%3A%20Error%204%20and%20page%20shutdown%20on%20Debian%20Buster%20following%20latest%20update.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2839685%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Alex%20-%20I%20haven't%20sent%20feedback%20so%20I'll%20fire%20it%20up%20and%20do%20so.%26nbsp%3B%20I'm%20sure%20it%20will%20probably%20be%20specific%20to%20my%20OS%20setup%20which%20is%20long%20overdue%20for%20a%20clean%20and%20scrape.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECheers.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

Is anybody else seeing this problem.  Some pages, I've yet to work out any pattern, are half-rendering then the page is closed and the 'Error 4' message displayed.  This happens repeatedly when retrying on the same page but subsequently does not always re-occur if the browser is closed and restarted. 

 

This has started happening from the last Dev update a few days ago for me. 


Not too worried as these things come and go but since I've recently updated to Buster I thought I'd check with other Debian users to see if anybody experiences the same.

 

Cheers.

4 Replies
best response confirmed by YizAKat (New Contributor)
Solution

Hey there! Just wanted to confirm that we haven't seen any other reports of this coming in, but I'm keeping an eye out for anything similar in case it's something other than the distro contributing to this one. If you haven't already, can you submit feedback in browser so our team will be better able to correlate this if we start seeing more reports?

 

Thanks!

Alex Rowell (she/her)
Community Manager - Microsoft Edge
Join us on Twitter, or over on Reddit in r/MicrosoftEdge or r/edge

Thanks Alex - I haven't sent feedback so I'll fire it up and do so.  I'm sure it will probably be specific to my OS setup which is long overdue for a clean and scrape.

 

Cheers.

Hey there! Just wanted to confirm we've now seen a couple reports of Debian users getting this error and I'm following up with the team for investigation. If you don't mind dropping your OS setup here I'd appreciate it, I'll pass it directly to the team! =)

@Alexandra-R 

‎14 Oct 2021 08:54 PM

Dev channel update to 96.0.1043.1 is live

  • Fixed an issue where new tabs sometimes immediately crash as soon as they’re opened.

Isn't the answer to the question? I've experienced the Error 4 at random recently. I've seen the annoying  message even hours before upgrading Edge yesterday. BTW. I've started reporting about that logically unexplained phenomena from October the 5th. I'm very keen to find out if the fix was the bullseye hit I was waiting for.

 

Regards,

--
MS Edge Dev 96.0.1043.1-1
Debian Bullseye GNU/Linux 5.10.70-1, X.org 1.20.11, IceWM 2.1.2
Nvidia GeForce GTX 650, Driver 460.91.03, systemd 247 (247.3-6)