|
Lopatir wrote: who was the braniac that decided separate processes was a good idea???
Citibank's online chat support feature loads via AJAX calls made on the main thread, instead of in the background. In firefox (one process) this locks up your entire browser until the POS loads (which must be in a colo on the Moon, considering how long it takes...)
In Chrome however, only the tab for Citibank locks up, so you can do something else while the page pulls its head out its...
Their online chat support is also on a different server, and uses cross-site scripting (BLOCKED!) to pass account information (REALLY!?) So unless you allow XSS, the support monkeys can't see any of your account information, and can't help you. Bravo. Bravo.
So, multiple processes helps to shield the user from terrible (or even malicious) website design. Ever see one of those pages that has an alert() loop? With multiple processes you can kill that one tab without losing whatever else you have open.
Obviously there are other features and improvements that could be made to mitigate all of these problems in a single process browser... But the more commonly used ones don't seem to offer this out of the box.
|
|
|
|
|
Lopatir wrote: Getting time to ditch chrome for edge as secondary browser, the edge is actually improving while chrome is for all it's updates is still stuck where it was 5 years ago
That's true. Even I have started using Edge as my secondary browser, ff being default. Edge has its issues but it's definitely improving while Chrome just seems too slow.
One thing though, I still prefer Chrome developer tool over ff for web development and Edge, I strictly use for browsing only. 
Piyush K Singh
|
|
|
|
|
Seconded that. Yesterday I tried Edge since MS advertised that it supports ABP now, and it turned out to be a pleasant experience. I am using it now.
Google chrome has transformed from from a lightweight browser into a big mess of tangled processes. It spawns almost ten processes which is named chrome, and two processes which is named crash handler, even though I only opened three tabs. You would think that they did this to handle crash better, but no, when one tab is not responding, the entirely of chrome stopped responding. Also it hogs CPU and RAM.
I can't understand why such a huge company makes such an amateur mistake. Maybe they don't have capable programmers to begin with, instead they have people who are good at marketing and advertising.
Oh yeah, let's not forget their faulty Google Drive for Desktop.
|
|
|
|
|
Google self driving car also crashed recently.
Google is the new ms:
1. rush incomplete and faulty crap to market,
2. skip fixing simple stuff, instead concentrate solely on adding more shiny bling bloat,
3. remove popular features that could allow people to have control or even worse adjust default settings,
4. open customer feedback portals and expert message boards, and ignore absolutely everything on them,
5. suggest people should always load upgrades to be relevant and enjoy the new [useless] bling
.. force updates by removing options to ignore them - ref item 1 for schedule
Sin tack ear lol
Pressing the "Any" key may be continuate
|
|
|
|
|
They're not accessing the same window, each tab will be its own GUI window that the process for that tab will interact with, with the title-bar, tab selectors etc belonging to the parent app, but the area inside the tab will belong to the child process. Think of browser tabs like a Multi Document Interface where each document is always maximised to the size of the parent browser process.
|
|
|
|
|
Well this goes against my understanding. You have a main browser window which as you say has title bars and all that stuff, a child control/window (tab selector), and each tab will be its own window as well (probably chrome then another child for its client area). How on earth do you get another process to provide the rendering/message pump etc. to that?
Regards,
Rob Philpott.
|
|
|
|
|
|
Thanks for the link, but I'm not sufficiently interested to go through that!
Regards,
Rob Philpott.
|
|
|
|
|
It was a kind of joke, but I would risk here an answer now, even it is clearly a programming answer...
In Windows, SetParent[^] can set the parent window even if it is from a different process...
So technically it is an easy problem - all you need is to pass a HWND to the new (child) process and you are done...
It is clear that in the case of Chrome the main process is different - in behaviour - from the others (even it is the same exe)... Hit Shift+Esc in Chrome and you will get a list o all the processes it is running... You can see that the one labeled 'Browser' can not be closed...This is the manager process...
Now that you know all this, go and write a CP article about!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: SetParent[^] can set the parent window even if it is from a different process...
Right, it's time for a career change! That seems to go completely against the whole point of a protected operating system. If I was drunk in the pub, a £50 bet would be looming. I will investigate this further.
I think I found my answer here though: Chromium Blog: Multi-process Architecture[^]
The browser process creates many renderer processes, each responsible for rendering web pages. The renderer processes contain all the complex logic for handling HTML, JavaScript, CSS, images, and so on. We achieve this using the open source WebKit rendering engine, which is also used by Apple's Safari web browser. Each renderer process is run in a sandbox, which means it has almost no direct access to your disk, network, or display. All interactions with web apps, including user input events and screen painting, must go through the browser process.
Regards,
Rob Philpott.
|
|
|
|
|
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --type=renderer --enable-features="*AutofillCreditCardSigninPromo<AutofillCreditCardSigninPromo,AutomaticTabDiscarding<AutomaticTabDiscarding,BlockSmallPluginContent<PluginPowerSaverTiny,DocumentWriteEvaluator<DisallowFetchForDocWrittenScriptsInMainFrame,MaterialDesignUserManager<MaterialDesignUserManager,NonValidatingReloadOnNormalReload<NonValidatingReloadOnNormalReload,OverrideYouTubeFlashEmbed<Override YouTube Flash emed,*PreconnectMore<PreconnectMore,*TranslateUI2016Q2<TranslateUI2016Q2" --disable-features=MetricsReporting<MetricsAndCrashSampling,PointerEvent<PointerEvent,SSLPostQuantumExperiment<SSLPostQuantum,UpdateRendererPriorityOnStartup<UpdateRendererPriorityOnStartup --force-fieldtrials="*AppBannerTriggering/Control/*AutofillCreditCardSigninPromo/Default/*AutomaticTabDiscarding/Enabled_Once_10-gen2/CaptivePortalInterstitial/Enabled/*ChildAccountDetection/Disabled/*ChromeChannelStable/Enabled/*ClientSideDetectionModel/Model0/*DisallowFetchForDocWrittenScriptsInMainFrame/DocumentWriteEvaluatorGroup/EnableWin32kLockDownMimeTypes/PPAPILockdown_Enabled/ExtensionDeveloperModeWarning/Enabled/*GFE/Default/*GoogleBrandedContextMenu/default/InstanceID/Enabled/MaterialDesignDownloads/Enabled/MaterialDesignUserManager/Enabled/MetricsAndCrashSampling/OutOfReportingSample/*NetworkQualityEstimator/Enabled/*NonValidatingReloadOnNormalReload/Enabled2/*OfferUploadCreditCards/Enabled/*OmniboxBundledExperimentV1/StandardR7/*Override YouTube Flash emed/YouTubeFlashRewrite/*PasswordBranding/Disabled/*PasswordGeneration/Disabled/*PasswordManagerSettingsMigration/Enable/*PluginPowerSaverTiny/Enabled2/*PreconnectMore/Default/*QUIC/EnabledNoId/ReportCertificateErrors/ShowAndPossiblySend/SHA1IdentityUIWarning/Enabled/SHA1ToolbarUIJanuary2016/Warning/SHA1ToolbarUIJanuary2017/Error/*SRTPromptFieldTrial/BiMonthlyPrompt/SSLCommonNameMismatchHandling/Enabled/*SSLPostQuantum/disabled/*SafeBrowsingIncidentReportingService/Default/SafeBrowsingUnverifiedDownloads/DisableByParameterMostSbTypes2/*SafeBrowsingUpdateFrequency/Default/*SignInPasswordPromo/Default/*StrictSecureCookies/Default/TranslateUI2016Q2/DefaultTranslateUI2016Q2/*TriggeredResetFieldTrial/On/*UMA-Dynamic-Uniformity-Trial/Group6/*UMA-Population-Restrict/normal/*UMA-Uniformity-Trial-1-Percent/group_47/*UMA-Uniformity-Trial-10-Percent/group_07/*UMA-Uniformity-Trial-100-Percent/group_01/*UMA-Uniformity-Trial-20-Percent/group_02/*UMA-Uniformity-Trial-5-Percent/group_02/*UMA-Uniformity-Trial-50-Percent/default/WebBluetoothBlacklist/BlacklistUpdate1/*WebFontsInterventionV2/Default/" --primordial-pipe-token=40FD41B8257D2C6E312516F374A00749 --lang=en-US --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --blink-settings=disallowFetchForDocWrittenScriptsInMainFrame=false,disallowFetchForDocWrittenScriptsInMainFrameOnSlowConnections=false --enable-pinch --device-scale-factor=1.1041666269302368 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553 --mojo-application-channel-token=40FD41B8257D2C6E312516F374A00749 --channel="4860.1284.267757369\20359401" --mojo-platform-channel-handle=17672 /prefetch:1
Marc
|
|
|
|
|
HOLY CRAP!
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I don't know if it's holy, but for sure it's /redacted/.
DURA LEX, SED LEX
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
They still use command line arguments!? That's so 1970's! I thought Google would be more modern than that. 
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
Hah hah. They used command line argument to send info to those child processes?
|
|
|
|
|
Judas H. Priest. 
Software Zen: delete this;
|
|
|
|
|
"Command-line arguments are limited to 32,768 characters[*], and we're gonna use them all, dammit!!"
-- Google, probably
[*] Isn't that still the case? I haven't had a need to look in decades...
|
|
|
|
|
If you ever wanted insight into the mind of a linux coder...
"There are three kinds of lies: lies, damned lies and statistics."
- Benjamin Disraeli
|
|
|
|
|
Whatever else, have you ever had a look how many Chrome processes are sometimes running, even with only 1 or 2 tabs open?
I currently have 13 processes for 3 tabs.
|
|
|
|
|
Brady Kelly wrote: I currently have 13 processes for 3 tabs.
3 tabs = 3 processes
+1 for main windows
+9 for extensions (each extension runs in a separated process)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
|
Well, this is all news to me, this SetParent() spanning processes.
I downloaded that project, and the browser opened in a separate window, not as a child of the winform. I am going to remain a skeptic until I see this properly.
Regards,
Rob Philpott.
|
|
|
|
|
Replace the exename from "iexplore" to the full path of calc.exe; once you have the handle you can set a new parent to the window. The new parent-window of the mainform does not have to be part of the application, it just needs to be an existing window handle.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Genius Eddy! I am now going to work out how to utilize this madness!
[edit: you're a y, not an ie, humble apologies]
Regards,
Rob Philpott.
|
|
|
|
|
Rob Philpott wrote: Genius Eddy!
Wasn't my idea to build Windows that way, but yes, great OS at some points.
One way would be by wrapping functionality (and ui) inside a new standalone-application, and launch that instead of a thread. Makes debugging easier 
Or a way to hook some extra functionality inside an existing application.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
