simple-scan-team team mailing list archive

[Michael Nagel <ubuntu@xxxxxxxxxxxxxxxxx>]

Hi VanillaMozilla, I understand your frustration, and while none of the
status seems perfect I will set this to invalid -- not to say that it
was not a real problem or valid criticism, but to make it dissapear from
bug lists and to give as the chance to concentrate on issues that still
require our attention.

Best Regards

** Changed in: simple-scan
       Status: Incomplete => Invalid

** Changed in: simple-scan (Ubuntu)
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Simple
Scan Development Team, which is the registrant for Simple Scan.
https://bugs.launchpad.net/bugs/763775

Title:
  Simple Scan apparently creates bad .png file, causes memory leak

Status in Simple Scan:
  Invalid
Status in “simple-scan” package in Ubuntu:
  Invalid

Bug description:
  Steps to duplicate:
  1. Scan a CD at 1200 dpi resolution.
  2. Stop the scan when it has covered the CD, by pressing the button.
  3. Crop the image.
  4. Save as a .png file.

  Results:
  1. .png file is 19.7 MB.
  2. ImageJ (v. 1.44c) gives "out of memory" message.  (Default memory on Ubuntu is 512, I believe.)
  3. ImageJ for Windows (v. 1.34s) attempts to load the file for a few minutes, then displays nothing.  I made 840 MB available to ImageJ on another computer.  It errored out (rather than giving an out-of-memory error).  The actual image size, loaded from the .jpg file, is only 240 MB.
  4. IrfanView (v. 3.99) for Windows XP immediately jumps to 1 GB virtual memory, then rapidly begins to increase memory use without limit.  At that point IrfanView cannot be terminated with Task Manager (EndProcess), and computer must be restarted with Task Manager.

  Note:  as a first step to verify, it might be a good idea double check
  by testing on a computer with more memory.  Mine had 1 GB, which
  should be ample, but it's easy to fool yourself.  In particular,
  ImageJ is usually explicit if it runs out of memory; also, there is
  plenty of perfectly swap space available.  I'm pretty sure this is not
  just an out of memory error, but it wouldn't hurt to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/763775/+subscriptions