Stuart Henderson writes:
> So it's the usual "software assumes it has the whole machine" problem,
> so the crash is easier to hit when you have lots of RAM.
>
> I think we should cap that based on rlimit rather than hardcoding to
> a fixed value in the config file, and probably also set to max
Problems arise in 2.73 and get worse in 2.74, when upgrading to 2.74, it will
affect OpenBSD.
Em 21 de setembro de 2022 13:59:03 BRT, Stuart Henderson
escreveu:
>On 2022/09/21 13:47, Marco Aurélio wrote:
>> That's not the tip of the iceberg, there are numerous issues, now there's
>> the
On 2022/09/21 13:47, Marco Aurélio wrote:
> That's not the tip of the iceberg, there are numerous issues, now there's the
> problem with glib 2.74, which affects gimp and other software that uses glib!
OpenBSD doesn't use glib 2.74 yet.
That's not the tip of the iceberg, there are numerous issues, now there's the
problem with glib 2.74, which affects gimp and other software that uses glib!
https://github.com/void-linux/void-packages/issues/39393
https://github.com/void-linux/void-packages/issues/39390
Em 21 de setembro de
597 undo_size = gimp_get_physical_memory_size ();
Any software which does this is written by stupid people.
I have tried to push back against this, but it keeps happening.
The only way the ports community will ever fix this general problem
which keeps being repeated, is by finding a way to
On 2022/09/20 16:54, Nam Nguyen wrote:
> Marc Espie writes:
>
> > Note that gimp itself has some control over memory used
> > under various circumstances in its Preferences.
> >
> > I haven't seen any indication that authors in this thread
> > are even aware those parameters exist.
>
> Here is a
On Tue, 20 Sep 2022 06:56:20 -0600
"Theo de Raadt" wrote:
> Stuart Henderson wrote:
>
> > On 2022/09/20 14:07, Marc Espie wrote:
> > > Note that gimp itself has some control over memory used
> > > under various circumstances in its Preferences.
> > >
> > > I haven't seen any indication that
Marc Espie writes:
> Note that gimp itself has some control over memory used
> under various circumstances in its Preferences.
>
> I haven't seen any indication that authors in this thread
> are even aware those parameters exist.
Here is a fresh diff providing conservative upper limits for
Stuart Henderson wrote:
> On 2022/09/20 14:07, Marc Espie wrote:
> > Note that gimp itself has some control over memory used
> > under various circumstances in its Preferences.
> >
> > I haven't seen any indication that authors in this thread
> > are even aware those parameters exist.
>
>
On 2022/09/20 14:07, Marc Espie wrote:
> Note that gimp itself has some control over memory used
> under various circumstances in its Preferences.
>
> I haven't seen any indication that authors in this thread
> are even aware those parameters exist.
Probably not because users shouldn't have to
Note that gimp itself has some control over memory used
under various circumstances in its Preferences.
I haven't seen any indication that authors in this thread
are even aware those parameters exist.
On Tue, Sep 20, 2022 at 10:02:17AM +0100, Stuart Henderson wrote:
> On 2022/09/19 12:40, Nam Nguyen wrote:
> > >> 2. shift+s to resize
> > >> 3. resize image with corners
> > >> 4. gimp crashes
> > >
> > > I'm using the default datasize-cur limit for "staff" (4GB) and haven't
> > > been able to
On 2022/09/19 12:40, Nam Nguyen wrote:
> >> 2. shift+s to resize
> >> 3. resize image with corners
> >> 4. gimp crashes
> >
> > I'm using the default datasize-cur limit for "staff" (4GB) and haven't
> > been able to provoke it into crashing by doing this yet (tried it with a
> > 8590x6000 TIFF).
Stuart Henderson writes:
> On 2022/09/18 21:23, Nam Nguyen wrote:
>> Laurence Tratt writes:
>>
>> > I'm not a heavy user of gimp, but I've noticed it segfaulting regularly
>> > (e.g. when saving, adjusting colours) whenever I've tried using it in the
>> > last couple of weeks or more. Having
On 2022/09/18 21:23, Nam Nguyen wrote:
> Laurence Tratt writes:
>
> > I'm not a heavy user of gimp, but I've noticed it segfaulting regularly
> > (e.g. when saving, adjusting colours) whenever I've tried using it in the
> > last couple of weeks or more. Having updated my amd64 snapshot + packages
Nam Nguyen writes:
> The solution is to bump resource limits. It might be nice to include a
> MESSAGE or README as in games/dolphin/pkg/README
Here is a diff to give users a hint. With default resource limits, gimp
will crash on operations like resizing due to memory-hungry
graphics/babl. This
Laurence Tratt writes:
> I'm not a heavy user of gimp, but I've noticed it segfaulting regularly
> (e.g. when saving, adjusting colours) whenever I've tried using it in the
> last couple of weeks or more. Having updated my amd64 snapshot + packages
> this morning to I'm still seeing problems.
I'm not a heavy user of gimp, but I've noticed it segfaulting regularly
(e.g. when saving, adjusting colours) whenever I've tried using it in the
last couple of weeks or more. Having updated my amd64 snapshot + packages
this morning to I'm still seeing problems. Here's an example backtrace from
18 matches
Mail list logo
