Off-Topic > Off-Topic - Tiny Core Lounge
necromancy / reborn of dillo 3.2.3
neonix:
Is it possible to modify Dillo that every webpage was opened in new window. Sometimes Dillo crush without a reason, or becouse lack of free RAM. There is also memory leak problem with this browser.
nick65go:
Maybe you could report a bug to the new developer in charge on git?
The DPI system of protocol/extension is the future for dillo (3.1+). It is a shame the developers do not cooperate between dillo/dillo-plus etc.
EDIT: "lack of free RAM", really? Maybe you did know that extensions DO RUN even if/after dillo is closed (check with top).
The new version 3.1 rc+ seems (git says) solved the problem of random crashes (because some SSL/TLS linked libs, about SNI --whatever this acronym is).
nick65go:
from https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo*.info
there are 2 versions of dillo, none of them up-to-date in TC15, as recent dillo 3.1+ of April 2024
the patched one (in Tinycore) was dillo 3.0.5, but not dillo 3.1.0-rc1 (https://dillo-browser.github.io/latest.html)
https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo-beta.tcz.info
Title: dillo-beta.tcz
Description: Dillo - the fast and light web browser
Version: 3.1 (20181005)
Change-log: 2019/07/20 v3.0.5
Current: 2020/02/10 v3.1 (neonix) TC 10.x
==
https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo.tcz.info
Title: dillo.tcz
Description: Dillo web browser
Version: 3.0.5 + patches
2020/02/20 fixed openssl-1.1.1 dependency (neonix) TC11.x
Current: 2024/04/02 Use OpenSSL 3.2 & patched for SNI support (CNK) TC14.x
FYI: for me it did not crash, in WSL2 (Windows Subsystem for Linux) for Alpine Linux.
Dies Irae:
--- Quote from: neonix on April 20, 2024, 08:52:58 AM ---Is it possible to modify Dillo that every webpage was opened in new window. Sometimes Dillo crush without a reason, or becouse lack of free RAM. There is also memory leak problem with this browser.
--- End quote ---
the usual 2 dillo in extensions by design refuse to drop cache. While i'd want this as an option, the argument is that a number of folk don't want it to drop cache when you close a tab, couse then they'd have to redownload some webpage/css file. Combined with the risk for crash, you want to run 2 instances of dillo: one, you kill regularly (if it didn't crash already), to get your ram back. The other you run for pages you actually wanted to keep open (and didn't crash your 'temp' dillo).
CNK:
I think I noticed some crashes with the dillo-beta.tcz extension on x86, which may have been some of the issues fixed since then in the 'beta' code. I haven't had any crashes with the current or previous dillo.tcz extension for x86_64 for Dillo 3.0.5.
I happened to submit the updated dillo.tcz extension just before the new release candidate for 3.1.0 came out, but before doing a new extension for that it seems sensible to wait until the full 3.1.0 release which the announcement said was expected in a few weeks. I've also reported a few bugs on the Dillo mailing list that might be fixed before then.
Since the dillo-beta.tcz extensions are for the 3.1.0 release which is hopefully happening soon, that will make them redundant so perhaps they should be removed then? I intend to build a dillo.tcz extension for x86 and x86_64 when it's fully released, unless someone else wants to do it (I checked that Neonix didn't want to before I submitted the new dillo.tcz for x86_64).
@nick65go The DPI system is supported in all the Dillo variants and versions, and is how the dillo-gopher.tcz and dillo-gemini.tcz extensions work.
@neonix If you're running out of RAM then Dillo might not be crashing but getting killed by the Linux kernel because it needs free RAM to do something else to keep the system running. I really like the cache because I use mobile broadband for my home internet, but a maximum cache size setting in Dillo would be useful in cases like yours. It's probably a fair bit of work to implement that properly though. Modern webpages that load lots of massive images expecting them to be scaled down with CSS are also a problem if RAM is limited.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version