Thorium

[NotHereToPlayGames]

11 minutes ago, 66cats said:

Supermium runs, but is unusable (nearly freezes with 100% CPU usage -- as advertised, win32 mentioned it needs 2 cores min.)

Ah, I somehow missed that.  I've only tried Supermium (and Thorium) on a single-core ThinkPad T42, WinXP x86 SP3, Pentium M 745.

It's the only real (bare metal) XP that I've not upgraged.

[AstroSkipper]

23 minutes ago, 66cats said:

Specs: XP 32 SP3, Core Solo T1350@1.86GHz, 4GB installed RAM

You should use the version Thorium_SSE3_122.0.6261.168_WINXP_x32.zip as your CPU supports the SSE3 instruction set at maximum. You can use the SSE2 version, too but I would try the SSE3 one first.

[66cats]

12 minutes ago, AstroSkipper said:

use the version

I was totally off, downloaded from /thorium-win, rather than /thorium-legacy (xp builds are there). Actually posting from it now.

It's *nearly* usable, possibly still syncing. 

BTW, haven't tried the latest Supermium build, i think the one i tried is 121. 

[AstroSkipper]

As a technically interested person and die-hard Windows XP Professional 32-bit enthusiast , I installed Thorium on my very old and very weak computer for testing purposes only. 

My hardware and OS specs are: Windows XP Professional SP3 with  all updates after SP3 and additionally all POSReady updates, an Intel Pentium 4 Northwood 2.80 GHz CPU (single core, 32 Bit), 1.5 GB SD-RAM and a NVIDIA GeForce 6200 graphic card.

I am using the version Thorium_SSE2_122.0.6261.168_WINXP_x32 in portable mode. Nothing has been installed to avoid any compromising of my system.  It was hard to adjust the browser settings and flags to load pages as it actually should be. I am using the extension uBlock Origin as I do in all my browsers to filter and block all crap. However, uBlock Origin had to be exactly adjusted to not interfere negatively the loading of websites. I will test Thorium for a while to see how it behaves on my very weak Windows XP computer. But in any case, I am also interested in experiences from other users with Thorium on old 32-bit computers. 

Edited May 1, 2024 by AstroSkipper
Update of content

[Klemper]

Fellas, with all respect, I think it's too early to even think of old single core systems. I'm experiencing terrible memory leaks Dave wrote about, and that on a 2014 laptop with 8GB!

We need to wait when @win32fixes the leak and only then he might probably give the patch to the Thorium guy.

[66cats]

3 minutes ago, AstroSkipper said:

I am using the version Thorium_SSE2_122.0.6261.168_WINXP_x32

I'm trying the same, but in "go and write to the registry & wherever else you want" mode. Just installed the latest Supermium, pretty dramatic difference between the two (on a single core): Thorium's painfully slow but usable, Supermium pegs the CPU at 100% (just like the previous version) & has to be killed with Task Manager (which also freezes, so rebooting now). 

 

1 hour ago, NotHereToPlayGames said:

I've only tried Supermium (and Thorium) on a single-core

That explains it. 

[AstroSkipper]

Can anyone tell me why Thorium is trying to connect via UDP to the address 239.255.255.250 using the port 1900 almost every minute? My Windows 10 Firewall Control is blocking and logging this connection, fortunately.  I performed a WHOIS check and got this information:

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#
 

NetRange:       224.0.0.0 - 239.255.255.255
CIDR:           224.0.0.0/4
NetName:        MCAST-NET
NetHandle:      NET-224-0-0-0-1
Parent:          ()
NetType:        IANA Special Use
OriginAS:       
Organization:   Internet Assigned Numbers Authority (IANA)
RegDate:        1991-05-22
Updated:        2013-08-30
Comment:        Addresses starting with a number between 224 and 239 are used for IP multicast.  IP multicast is a technology for efficiently sending the same content to multiple destinations.  It is commonly used for distributing financial information and video streams, among other things.
Comment:        
Comment:        A full list of IPv4 multicast assignments can be found at:
Comment:        
Comment:        http://www.iana.org/assignments/multicast-addresses
Comment:        
Comment:        A document describing the policies for assigning multicast addresses can be found at:
Comment:        http://datatracker.ietf.org/doc/rfc5771
Ref:            https://rdap.arin.net/registry/ip/224.0.0.0
 

 
OrgName:        Internet Assigned Numbers Authority
OrgId:          IANA
Address:        12025 Waterfront Drive
Address:        Suite 300
City:           Los Angeles
StateProv:      CA
PostalCode:     90292
Country:        US
RegDate:        
Updated:        2012-08-31
Ref:            https://rdap.arin.net/registry/entity/IANA
 

OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   ICANN
OrgAbusePhone:  +1-310-301-5820 
OrgAbuseEmail:  abuse@iana.org
OrgAbuseRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN
 
OrgTechHandle: IANA-IP-ARIN
OrgTechName:   ICANN
OrgTechPhone:  +1-310-301-5820 
OrgTechEmail:  abuse@iana.org
OrgTechRef:    https://rdap.arin.net/registry/entity/IANA-IP-ARIN
 

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2024, American Registry for Internet Numbers, Ltd.
#

It seems to be somehow related to multicast. Can this be turned off in Thorium?  

Edited May 1, 2024 by AstroSkipper
Update of content

[66cats]

17 minutes ago, AstroSkipper said:

Can anyone tell me why Thorium is trying to connect via UDP to the address 239.255.255.25

Know next to nothing about this, but i think it's just Windows networking (not Thorium). Close Thorium & every every browser, start scanning -- should see 239.255.255.255 popping up. Or not. Is networking enabled on your box?

[nicolaasjan]

20 minutes ago, AstroSkipper said:

Can anyone tell me why Thorium is trying to connect via UDP to the address 239.255.255.250 using the port 1900 almost every minute?

Thorium doesn't do it here, because I have UPnP service disabled.

Why Thorium needs it, I don't know.

(Google search)

https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol

https://forum.vivaldi.net/topic/43299/why-is-vivaldi-connecting-to-239-255-255-250-port-1900-udp-ssdp-and-requires-it/3

[AstroSkipper]

2 minutes ago, 66cats said:

Know next to nothing about this, but i think it's just Windows networking (not Thorium). Close Thorium & every every browser, start scanning -- should see 239.255.255.255 popping up. Or not. Is networking enabled on your box?

No. It is indeed Thorium trying to connect to this address. To be more precise it is the process thorium.exe.

[AstroSkipper]

6 minutes ago, nicolaasjan said:

Thorium doesn't do it here, because I have UPnP service disabled.

Why Thorium needs it, I don't know.

(Google search)

https://en.wikipedia.org/wiki/Simple_Service_Discovery_Protocol

https://forum.vivaldi.net/topic/43299/why-is-vivaldi-connecting-to-239-255-255-250-port-1900-udp-ssdp-and-requires-it/3

 

6 minutes ago, AstroSkipper said:

11 minutes ago, 66cats said:

Know next to nothing about this, but i think it's just Windows networking (not Thorium). Close Thorium & every every browser, start scanning -- should see 239.255.255.255 popping up. Or not. Is networking enabled on your box?

No. It is indeed Thorium trying to connect to this address. To be more precise it is the process thorium.exe.

Disabling the flag #media-route-dial-provider seems to be the solution I found by checking all available Thorium flags. 

[NotHereToPlayGames]

Disable QUIC protocol for one.  But some of the other multicast UDP connections may "require" an UNGOOGLED version of Thorium.

[NotHereToPlayGames]

Just now, AstroSkipper said:

Disabling the flag #media-route-dial-provider 

I was going to suggest that one also but it's not in v114 and I cannot access Thorium or Supermium at work.

[nicolaasjan]

Thorium is apparently looking for Google Chromecast devices.

[AstroSkipper]

7 minutes ago, NotHereToPlayGames said:

8 minutes ago, AstroSkipper said:

Disabling the flag #media-route-dial-provider 

I was going to suggest that one also but it's not in v114 and I cannot access Thorium or Supermium at work.

Yep! This one did the trick. No more entries in my firewall log.  I just found this by accident, and its description made me prick up my ears:

Quote

Allow cast device discovery with DIAL protocol

Enable/Disable the browser discovery of the DIAL support cast device.It sends a discovery SSDP message every 120 seconds – Mac, Windows, Linux, ChromeOS, Fuchsia, Lacros

#media-route-dial-provider