Tag: chrome
-
Post Views: 10 Recently, on Ubuntu 26.04, the memory usage problem of Chrome has become more and more serious, often approaching or even more than 10GB, which makes me have to consider switching to Firefox. However, there are many pits during the migration process, especially the problem of Snap version of Firefox and the problem of unable to import passwords.…
-
Post Views: 14 In the previous ‘Ubuntu 26.04 software installation and maintenance best practices: take WeChat as an example‘In the article, I discussed the installation and daily management of software. However, in the recent practical use, I have encountered serious abnormal memory usage. 1. Trailer Pit Records: The Nightmare of Chrome High Memory Occupancy The thing is due to the…
-
Post Views: 24 Environment: Ubuntu 26.04 + Google Chrome For the official version, 60 tabs (about 50 different domain names), compared with the memory difference of the same configuration in Windows 10, gradually optimized from 2GB of no-load and 19GB of full load to a reasonable range. 1. Phenomenon: There is a huge gap between system memory 1. The original…
-
Post Views: 48 Recently I plan to join the V2EX community, but the current registration mechanism is really not very friendly to newcomers. After some research, I have compiled a complete process from purchasing tokens to smooth registration. If you are also planning to hold the token to be exempted from the invitation code to register, or you have encountered…
-
Post Views: 15 1. In the Chrome browser, open the URL mapped after modifying the hosts file, and you will be prompted: Your connection is not a private connection. There is also no option to continue to go to Advanced Expand. as shown in Figure 1 2. If you comment out the URL that modifies the hosts file mapping, enable…
-
Post Views: 17 1. Request in Altairhttps://object.local/graphql, Response: “Http Failure Response forhttps://object.local/graphql:0 unknown error”. As shown in Figure 1 2. It needs to be opened in the browser:https://object.local, and then find that the Chrome browser is safely intercepted, after selecting trust, request againhttps://object.local/graphql, the response 200. as shown in Figure 2