Open kenz-gelsoft opened 1 month ago
Maybe we can test with -no-remote
option whether remoting protocol affects to current problem or not.
I bet this has nothing to do with early tab crashes.
Maybe we can test with -no-remote option whether remoting protocol affects to current problem or not.
we already specified that implicitly when we do ./mach run:
~/src/gecko-dev> ./mach run
0:00.31 /boot/home/src/gecko-dev/obj-ff-dbg/dist/bin/firefox -no-remote -profile /boot/home/src/gecko-dev/obj-ff-dbg/tmp/profile-default
Try disabling forcibly. This changes build configuration, so takes hours to rebuild.
~/src/gecko-dev> git diff toolkit/moz.configure
diff --git a/toolkit/moz.configure b/toolkit/moz.configure
index a424446c7d44..0f951fe5d466 100644
--- a/toolkit/moz.configure
+++ b/toolkit/moz.configure
@@ -2624,6 +2624,7 @@ with only_when(compile_environment & target_is_windows):
@depends(toolkit)
def has_remote(toolkit):
+ return False
if toolkit in ("gtk", "windows", "cocoa"):
return True
It was not easy to disable remoting protocol. Will try another approach, or investigate other failure first.
Infomative to me
TestUDPSocket.TestUDPSocketMain
It's not intuitive, but DBus connection error could cause IPC failure?