Memory usage is still a concern. On 2.32 the app crashed on scanning
about 80 pages due to too low memory:
GLib-ERROR **: /build/buildd/glib2.0-2.24.1/glib/gmem.c:137: failed to allocate
26779794 bytes
aborting...
Aborted
I did it on a machine with 1 GB RAM, before starting Simple Scan memory
usage was 290 MB and did not start something else during scanning. After
revaluating it on a machine with 4 GB i noticed that the saving process
to PDF will always take another bunch of MB on the RAM, but it won't
free it after finishing! This means that every saving will increase that
amount of RAM usage and you can't get rid of without restarting Simple
Scan. How comes that?
The main problem with high memory usage is that users will loose all
there scans when no free RAM is left (as my case shows it's not too hard
to reach that point). There should be some sort of checking on the
amount of free RAM and when it get's too low users should get a warning,
so that they can save there scans before crashing. Of course this means
that there need to be enough RAM for the saving process.
** Also affects: simple-scan (Ubuntu)
Importance: Undecided
Status: New
--
Reduce memory usage
https://bugs.launchpad.net/bugs/525441
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
