A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Talk about code development, features, specific bugs, enhancements, patches, and similar things.
Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific bugs, git, the repositories, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Please post issues with specific websites, extensions, etc. in the relevant boards for those topics.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35575
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Moonchild » 2020-09-13, 21:52

The Squash wrote:
2020-09-13, 19:13
Should the people in my group choose to speak out, they shall be allowed to do so.
That is the same kind of BS answer as "it will be explained in due time or it won't" (see: Open Usage Commons/Google). If you aren't going to substantiate your claims then I will just assume it's made up. That's fine too, but at least admit it, if so. I just don't have time to waste on these kinds of games.

I'll give you a week to think about your approach to us, and whether you are going to continue to veil yourself in unverifiable vagueries or going to be transparent for a change. If you decide on the former, then please be a dear and don't come back because you will no longer have a sounding board here.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Kendo

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Kendo » 2020-09-15, 09:49

So what if it takes more than an hour to build PM.

We used to use Chromium and that took a way lot longer for a result that had less to offer!

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35575
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Moonchild » 2020-09-15, 10:15

Kendo wrote:
2020-09-15, 09:49
So what if it takes more than an hour to build PM.
On most systems, it does :)

But yes, reducing the number of parallel compilation processes will reduce memory requirements. That will not, however, overcome issues with linking libxul (because it's huge).
The basic problem is simple: computer not having enough resources to build. This is why pre-built binaries exist. Can't compile it yourself? Then use what we already built for everyone.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 4971
Joined: 2015-12-09, 15:45
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by moonbat » 2020-09-15, 10:28

Can't see the need to build it on one's own unless it's an officially unsupported platform with nobody else providing 3rd party builds or if you have to make some ultra super niche code modifications that solve a specific problem that only you have and which can't be contributed back to the codebase.

Let alone the notion that open source means you should also be able to build it by yourself.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX

User avatar
adesh
Board Warrior
Board Warrior
Posts: 1277
Joined: 2017-06-06, 07:38

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by adesh » 2020-09-15, 11:24

Off-topic:
"need" is not the word, "want" is.

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35575
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Moonchild » 2020-09-15, 11:26

Off-topic:
Can't always get what you "want". And understandably, "need" will get priority over "want".
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

User avatar
Isengrim
Board Warrior
Board Warrior
Posts: 1325
Joined: 2015-09-08, 22:54
Location: 127.0.0.1
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Isengrim » 2020-09-15, 12:09

moonbat wrote:
2020-09-15, 10:28
Let alone the notion that open source means you should also be able to build it by yourself.
Off-topic:
You should absolutely be able to build software if its source code and build tools are both freely available. That doesn't mean it has to be buildable on an underpowered machine. If you went and complained to the LineageOS folks that you can't build LineageOS on your 4 GB Windows 7 box, you'd be laughed out of the room.

Building yourself also doesn't mean you don't have to know what you're doing, or should expect a build to function 100% correctly if built with hacks and workarounds like this one. Developers must be responsible for having adequate build environments and following the build instructions as they are given.
a.k.a. Ascrod
Linux Mint 19.3 Cinnamon (64-bit), Debian Bullseye (64-bit), Windows 7 (64-bit)
"As long as there is someone who will appreciate the work involved in the creation, the effort is time well spent." ~ Tetsuzou Kamadani, Cave Story

User avatar
moonbat
Knows the dark side
Knows the dark side
Posts: 4971
Joined: 2015-12-09, 15:45
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by moonbat » 2020-09-15, 12:16

As far as I've observed, all the complaints and heated arguments about being unable to build are down to not following the hardware and/or dependency requirements that were posted. Otherwise we already have unofficial 3rd party builds like the one for Mac OS.
"One hosts to look them up, one DNS to find them and in the darkness BIND them."

Image
Linux Mint 21 Xfce x64 on HP i5-5200 laptop, 12 GB RAM.
AutoPageColor|PermissionsPlus|PMPlayer|Pure URL|RecordRewind|TextFX

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35575
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: A cheap trick to reduce memory usage building a UXP application (such as Pale Moon)

Unread post by Moonchild » 2020-09-15, 12:19

Off-topic:
Isengrim wrote:
2020-09-15, 12:09
You should absolutely be able to build software if its source code and build tools are both freely available.
Actually, that's not true. Open Source licensing never comes with a guarantee that you can build a complete product with it yourself or that it even can be compiled. Open Source licensing explicitly disclaims any fitness for any particular purpose for this reason. It is at all times released "as-is". Whether you can use it for your purposes or not falls completely outside of the Open Source scope.
We have no obligation to ensure buildability or that a third party built product performs exactly the same as an official build.
We also especially have no obligation to ensure buildability in other environments other than what is listed as the required one(s), and even that is a matter of guidelines for convenience. We try to ensure buildability in listed environments for those people who, for various reasons, can't/won't use pre-built binaries, but it's not an "absolute".
In fact, that obligation of performing exactly the same as an official build only comes into play when official branding is concerned when there's the reasonable expectation that something with the label actually does what the label implies, but that's a different topic altogether.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

Locked