Discussion:
[Gwyddion-users] Gwyddio.exe:55824 GLIb-error
Andrés Muñiz Piniella
2015-06-23 08:58:48 UTC
Permalink
Hello,

This might be my computer not having enough resources.

I have a 4096 px image from Park XE-100 AFM I set a mask on one image and
as I duplicate it to do another mask the gwyddion stops working when I save
it.

Message is:
Gwyddion.exe:55824 GLib-ERROR**:../glib/gmemc:168:failed to allocate
536870912 bytes


The main issue I have is that it corrupts the saved copy and drops from a
131Mb file to a 0Kb file. Losing very little information but If it happens
after a lot of data analyis it could be a problem. At the moment I
cautiously save my work with save as...

I am using windows 7 32 bit. 4GB (2.68 GB usable) CPU E5-2630 @ 2.30 GHz
--
Andrés Muñiz-Piniella
David Nečas (Yeti)
2015-06-23 09:39:19 UTC
Permalink
Post by Andrés Muñiz Piniella
This might be my computer not having enough resources.
Most likely.
Post by Andrés Muñiz Piniella
I have a 4096 px image from Park XE-100 AFM I set a mask on one image and
as I duplicate it to do another mask the gwyddion stops working when I save
it.
This means at least 0.5 GB of data in memory. During saving, it will
essentially double...
Post by Andrés Muñiz Piniella
Gwyddion.exe:55824 GLib-ERROR**:../glib/gmemc:168:failed to allocate
536870912 bytes
The main issue I have is that it corrupts the saved copy and drops from a
131Mb file to a 0Kb file. Losing very little information but If it happens
after a lot of data analyis it could be a problem. At the moment I
cautiously save my work with save as...
I will try to make sure that the file is only overwritten successfully
and otherwise the old version is kept intact. However, the program
termination with insufficient memory does not seem to be fixable
(without changing library APIs, i.e. not practically fixable).

Regards,

Yeti
Andrés Muñiz Piniella
2015-06-23 12:17:00 UTC
Permalink
Post by Andrés Muñiz Piniella
Post by Andrés Muñiz Piniella
The main issue I have is that it corrupts the saved copy and drops
from a
Post by Andrés Muñiz Piniella
131Mb file to a 0Kb file. Losing very little information but If it
happens
Post by Andrés Muñiz Piniella
after a lot of data analyis it could be a problem. At the moment I
cautiously save my work with save as...
I will try to make sure that the file is only overwritten successfully
and otherwise the old version is kept intact. However, the program
termination with insufficient memory does not seem to be fixable
(without changing library APIs, i.e. not practically fixable).
Keeping old version intact is good enough for me. I can use a bigger computer or reduce the use of other programs.

I am guessing that using commandline or pygwy will not make the resources significantly less?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
David Nečas (Yeti)
2015-06-23 12:38:27 UTC
Permalink
Post by Andrés Muñiz Piniella
I am guessing that using commandline or pygwy will not make the
resources significantly less?
Well, a standalone pygwy script (a) does not remember any undo
information (b) does not display anything. This conserves some memory.
I cannot tell if it will help in your case or not.

Generally, if you work with huge data, use 64bit Gwyddion on a machine
with a decent RAM size – 12 or 16 GB should be relatiely commonplace
nowadays. Also note that the size of anything in Gwyddion files and the
file itsef is a 32bit quantity, i.e. it can never exceed approximately 4
GB.

Regards,

Yeti

Loading...