NotHereToPlayGames Posted May 29, 2024 Posted May 29, 2024 1 hour ago, chermany4ever said: I kept thinking about that quasi-discussion of 'too old' hardware, I mean, we all come from there I've had two 16+ year old XP laptops die on me all within the last three months. I'm down to two XP laptops. One of them turned 20yrs old this month. ThinkPad T42. I'm kind of at the point where I kind of "want it" to die already, lol. No permanent web browser on that one, just a quick flyby to run Thorium or Supermium for a couple minutes then remove them completely. 1
chermany4ever Posted May 29, 2024 Posted May 29, 2024 28 minutes ago, NotHereToPlayGames said: I've had two 16+ year old XP laptops die on me all within the last three months. Sorry to hear that. Back in the day was advised against laptops, notebooks and so on 'cause they're difficult to repair. Never had anything like that, though today's mobile phones are almost there. I must admit everything small, thin and mobile makes me suspicious. I feel that they're designed so we can't detach from the device. I already sound like a conspiracy theorist. 2
UCyborg Posted May 30, 2024 Posted May 30, 2024 7 hours ago, chermany4ever said: After a few hours of testing the only page I'm having problems with is Google Drive. Already tried to sync my account in another window, disabling the extensions and can't solve it. The page loads and looks fine but when it finishes loading and stop, it crashes. Does anyone else have the same problem? Yes... 7 hours ago, AstroSkipper said: And you can report this problem in Thorium's issues on GitHub to inform the developer. https://github.com/Alex313031/thorium-legacy/issues/62 The issue was closed, but it wasn't solved in legacy build. 1
chermany4ever Posted May 30, 2024 Posted May 30, 2024 59 minutes ago, UCyborg said: The issue was closed, but it wasn't solved in legacy build Thank you very much UCyborg. I was about to follow Astro's advice to go to GitHub and ask around. I was also playing around a bit with the flags but what I tried only made things worse. The good, the bad and the ugly! It will be a matter of finding a way around it. I remembered when that program appeared that created a virtual disk linked to Drive and appeared in My PC. Twas super slow! But today that speeds are different... where is that Setup.exe? 1
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 5 hours ago, UCyborg said: 13 hours ago, AstroSkipper said: And you can report this problem in Thorium's issues on GitHub to inform the developer. https://github.com/Alex313031/thorium-legacy/issues/62 The issue was closed, but it wasn't solved in legacy build. As I already mentioned, I am running the Thorium version SSE2 122.0.6261.169 WINXP 32-bit. If this legacy build was not fixed, why does Google Drive work in my installation then? When I tested it, I could log into my account and access my files without any crashes. 2
UCyborg Posted May 30, 2024 Posted May 30, 2024 On a clean profile without any alterations and launching the browser without any command-line parameters/flags?
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 (edited) 30 minutes ago, UCyborg said: On a clean profile without any alterations and launching the browser without any command-line parameters/flags? No. On my fully configured profile with tons of flags. I have disabled many features I do not need and to run Thorium more smoothly. Without these configurations, Thorium does not run smoothly on my ancient machine. The main problem on my computer is the page loading behaviour of Thorium which is now bearable and ok for me after all these endless configurations. Edited May 30, 2024 by AstroSkipper Update of content 2
UCyborg Posted May 30, 2024 Posted May 30, 2024 (edited) Well, whatever the cause, the correct result is no crashing when used as-is with defaults. I noticed he has only one version of Thorium 122 for modern Windows (so no further patching of 122 from initial release), this one doesn't crash. Legacy one does, when run on Win10 or XP. Actually, it appears only Win32 flavor of legacy build crashes, Win64 legacy build is fine. And the one build for modern Windows is available only in Win64 flavor. Edited May 30, 2024 by UCyborg 3
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 (edited) 12 minutes ago, UCyborg said: Well, whatever the cause, the correct result is no crashing when used as-is with defaults. I noticed he has only one version of Thorium 122 for modern Windows, this one doesn't crash. Legacy one does, when run on Win10 or XP. Ok. The next time when I am at my XP machine I will test Google Drive on a clean profile but with the most recent Chrome XP API Adapter. Without this updated adapter, Thorium does not run well and would overtax my patience. Maybe then, I'll finally get the long-awaited crash. Edited May 30, 2024 by AstroSkipper Update of content 2
UCyborg Posted May 30, 2024 Posted May 30, 2024 The issue was first spotted 1 year ago. https://github.com/Alex313031/thorium-legacy/issues/4
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 1 hour ago, AstroSkipper said: 2 hours ago, UCyborg said: Well, whatever the cause, the correct result is no crashing when used as-is with defaults. I noticed he has only one version of Thorium 122 for modern Windows, this one doesn't crash. Legacy one does, when run on Win10 or XP. Ok. The next time when I am at my XP machine I will test Google Drive on a clean profile but with the most recent Chrome XP API Adapter. Without this updated adapter, Thorium does not run well and would overtax my patience. Maybe then, I'll finally get the long-awaited crash. Ok. On a clean profile without any further flags but with the most recent Chrome XP API Adapter, I finally get the long-awaited crash. So, you are absolutely right, the Thorium version SSE2 122.0.6261.169 WINXP 32-bit was not fixed in terms of the Google Drive bug. 2
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 (edited) 3 hours ago, UCyborg said: On a clean profile without any alterations and launching the browser without any command-line parameters/flags? 58 minutes ago, AstroSkipper said: Ok. On a clean profile without any further flags but with the most recent Chrome XP API Adapter, I finally get the long-awaited crash. So, you are absolutely right, the Thorium version SSE2 122.0.6261.169 WINXP 32-bit was not fixed in terms of the Google Drive bug. So, after some deeper tests, I found the reason why Google Drive didn't crash for me in my fully configured profile. In this profile, I use by default a mobile user agent. The mobile view of Google Drive runs without any crashes and very fast. Therefore, I didn't observe any problems there. Here is my mobile user agent string: Mozilla/5.0 (Linux; Android 9; Tablet) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.168 Mobile Safari/537.36. It can be used as a temporary or general (as Google Drive is much smoother then ) solution until the bug is fixed in the legacy build, too. Edited May 30, 2024 by AstroSkipper 3
Dixel Posted May 30, 2024 Posted May 30, 2024 I had written about user agent hacks ages ago' all can be found at my account, people just don't listen, hopefully they will listen to @AstroSkipper. Another important hack is OS bitness in user agent, always choose 32 bit OS. esp. if you're on XP 32 bit! Youtube (and the such) will serve less scripts for 32 bit OS. 4
AstroSkipper Posted May 30, 2024 Posted May 30, 2024 56 minutes ago, AstroSkipper said: So, after some deeper tests, I found the reason why Google Drive didn't crash for me in my fully configured profile. In this profile, I use by default a mobile user agent. The mobile view of Google Drive runs without any crashes and very fast. Therefore, I didn't observe any problems there. Here is my mobile user agent string: Mozilla/5.0 (Linux; Android 9; Tablet) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.6261.168 Mobile Safari/537.36. It can be used as a temporary or general (as Google Drive is much smoother then ) solution until the bug is fixed in the legacy build, too. 9 minutes ago, Dixel said: I had written about user agent hacks ages ago' all can be found at my account, people just don't listen, hopefully they will listen to @AstroSkipper. Another important hack is OS bitness in user agent, always choose 32 bit OS. esp. if you're on XP 32 bit! Youtube (and the such) will serve less scripts for 32 bit OS. Thanks, my friend! You are helpful here as you have always been. In any case, I can say that using a mobile user agent works absolutely great in Thorium. Many websites load much faster. As I am also an experienced Android user for many years, I have learnt to appreciate the advantages of websites' mobile view. I only switch to the desktop view of a certain website if necessary or desired. On such an old machine as mine, this trick leads to a very careful use of the computer resources available. Less CPU utilisation, less RAM consumption. 2
Saxon Posted May 30, 2024 Posted May 30, 2024 I'm using this one. Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 122 version is already too old and sites shove captchas down our throats. With 124 I can visit them. 2
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now