AstroSkipper

The main reason for the values in that stats is the fact that Windows computers have been extremely displaced by smartphones and tablets in the last 20 years. And if a normal consumer uses a notebook and, now rather rarely, a desktop computer, it will probably be a Windows 10 or 11 computer. And there, the normal user is more likely to install what they know from their mobile devices. Chrome or Chromium. The younger generation now only seems to know Windows computers from the stories of their elders. But all that doesn't make Chrome and Chromium browsers any better.

But too much time-consuming, considering that we are talking about 365 updates, as I mentioned earlier, although I am also interested in the cause of these sudden closes. After a deep research in the internet, I found out that many users suffer from this Chrome issue and have switched to Firefox as there seems to be no real solution. If this error also occurs on my Windows XP Pro SP3 + POSReady partition, I will immediately give up Thorium.

Thorium is Chrome based. Search for the string " Chrome immediately closes when starting" or similar search strings, and you will see I am not the only one. My issue is a common error in Chrome. You should actually know that as a Chrome/Chromium fan.

Both partitions were created by me in 2004. Since then, there has been no reinstallation due to a perfectly functioning imaging system. I correct all errors myself. The registry of both have been modified, cleaned and fixed by myself. The main difference between them is that I had to stop the updating of Windows XP with the last update in 2014 in one of them, and in the other, I applied the POSReady hack and performed updating until 2019. PS: I never had an infection, which had to be removed by an antimalware programme, in both Windows XP installations. And don't forget there is an undetermined probability of type II error for accepting the null hypothesis H0.

I tend to assume that my computer is such certain hardware. The reason for my assumption is that everything works in my Windows XP Pro SP3 without POSReady partition. I have never had such problems. Firefox, New Moon and also Mypal 68 work perfectly there. This partition is configured in exactly the same way as the one with Windows XP Pro SP3 + POSReady updates. Actually, my issue can only be due to a missing patch or update. And the only updates missing there are the POSReady ones.

Yep! That's why I modified my null hypothesis H0 some days ago. I tend to assume that my computer is such certain hardware.

After all my measures, and I performed many of them, I have to confirm my last null hypothesis H0. Thorium behaves unstably on my Windows XP Pro SP3 without POSReady. Sometimes, the browser opens and lasts for a few seconds or minutes, very often the browser closes during startup. There is no recognisable pattern. I also tried different combinations of command line flags. No success. The internal site chrome://metrics-internals/ doesn't provide any information on my old machine. The good thing about the story is that my Windows XP Pro SP3 without POSReady installation is now absolutely error-free and updated.

I tried it on my Windows XP Pro SP3 + POSReady installation months ago. It didn't do anything interesting, so I removed it a short time later. I should mention that RAM consumption of Thorium is not the problem on my computer. And just for clarification, this flag actually can't be a solution for my issue, as Thorium works fine without it on my Windows XP Pro SP3 + POSReady installation. But I'll give it a try anyway. Just to be sure.

Yep! Same here. I have never installed Thorium using the install batch file or the REG files provided in the downloaded archive file. BTW, these should have to be adjusted to the respective system if you want to use them. Furthermore, the REG files contain syntax errors. For me, Thorium have been running error-free on my Windows XP Pro SP3 + POSReady for months by only extracting the archive and using a batch file or loader with command line flags for starting. But on my Windows XP Pro SP3 without POSReady, it permanently crashes and behaves unstably.

Thanks for your idea! That's why I originally assumed POSReady updates were mandatory for running Thorium. Maybe, there is really an POSReady update which is urgently needed to run Thorium on my hardware. But I should mention that there are 365 updates in my archive applied after the POSReady hack. And without this hack, you can't install those updates, either. So, it does not make sense to investigate them. And I already have a perfectly working Windows XP Professional installation with all POSReady updates. All my very deep investigations lead me to modify my null hypothesis: Here is my modified null hypothesis H0: "Thorium crashes due to the lack of one or more POSReady updates under certain hardware conditions". Personally, I tend to accept H0 due to my experiences and deep investigations. Unfortunately, the probability of type II error for this decision cannot be determined again due to the too small sample size, either.

To avoid messing up my main partition, I actually wanted to test Thorium in my second partition. But there, as already reported, the browser does not work stable. It crashes all the time. But in one of its bright moments, I was at least able to open a link from a PDF file in Thorium by directly clicking onto it. The REG files from Thorium were not the solution. They contain syntax errors. I made Thorium the default browser with the help of the Default Browser 1.8 tool that @dmiranda had already recommended here. For me, this tool worked as it should.

You seem to be using the older release Thorium_122.0.6261.168_WINXP_x32. But I am usimg the most recent release Thorium_SSE2_122.0.6261.171_WINXP_x32. Did you try this one on your computer where is installed Windows XP 32-bit without POSReady updates?

@NotHereToPlayGames Which version of Thorium do you run on your Windows XP 32-bit without POSReady updates?

Let H0 be the null hypothesis "Thorium crashes due to lack of POSReady updates". H0 must be rejected due to @NotHereToPlayGames's and @Saxon's report that Thorium runs fine in their Windows XP installations without POSReady updates. Unfortunately, the probability of error for this decision cannot be determined due to the too small sample size.

We already had this disscusion here: https://msfn.org/board/topic/184051-my-browser-builds-part-4/?do=findComment&comment=1251008 And there is nothing more to add to this statement.

Just for clarification. I am not a self-proclaimed "mathematician" but just a mathematician. I have not announced anything here, but only mentioned it in passing. No more, no less. As part of my search for the cause of the spontaneous Thorium crashes, I formed a lot of hypotheses and had to unfortunately reject them. And I have investigated many things as part of my hypotheses. But so far without success.

Yep! A clean, genuine Windows XP Professional. Only the service pack SP3 and all post SP3 updates until 2014. POSReady stuff has never been applied to this partition.

Thanks for the nice compliment and for the tip! There is definitely nothing I wouldn't try to solve these crappy crashes. Strangely, Thorium works perfectly in my Windows XP SP3 POSReady installation, i.e., without any crashes. And there, these DLL files exist from the very first.

I tried both. The last try was native Thorium without anything. No extensions, no additional flags and no Chrome XP API Adapter from IDA-RE-things, following the main principle to go back to the roots if it doesn't work.

Sometimes high, sometimes low. I can't recognise any particular pattern.

That's good to know. In both systems, all runtimes have been installed.

Any ideas what can cause these sudden closings of Thorium? My hardware can't be the causer, though. Has anyone had similar problems?

I added bold and underline to be sure that everyone is asked here. This has nothing at all to do with your answer, for which I have already thanked you. You should calibrate your sensor a little. It is set too sensitively.

Thanks for replying! And yes, I know very well your opinion about POSReady updates for Windows XP. But on my computer, Thorium only works in my Windows XP system with all POSReady updates. Maybe by accident, and there is another causer for my described issue. That's all a bit strange. Are there any specific requirements for Thorium in terms of system software, especially regarding runtime libraries and so on?

Now, a question to all who are running Thorium under Windows XP Professional SP3 with all updates after SP3 but without any POSReady updates. Does Thorium work under these conditions? I have two Windows XP installations, one with and one without POSReady updates. When I start Thorium on Windows XP without POSReady updates, it crashes randomly without any messages. With crashing I mean a sudden closing of the browser without any actions by me, either directly when starting the browser or seconds respectively minutes later.