[ubuntu-mono] [Bug 64913] Re: Memory hogging error

[Alecz20]

On Ubuntu 9.10 (f-spot 0.6.1.5)

During import 7700/172250, uses 1.8 GB of RAM  (and growing) as reported
by gnome system monitor.

I am not sure that the released fix is but it could even be a
regression.

-- 
You received this bug notification because you are a member of Ubuntu
CLI/Mono Uploaders, which is subscribed to f-spot in Ubuntu.
https://bugs.launchpad.net/bugs/64913

Title:
  Memory hogging error

Status in “f-spot” package in Ubuntu:
  Fix Released

Bug description:
  I just was trying to import pictures from my digicam (there were a lot
  of them, big pictures). I was in the midst of importing, with ~130/250
  imported, when my machine ran out of memory.

  I tried running f-spot again and with gdb this time, but it
  immediately halted. I wonder what's happening and how to get a
  backtrace of the situation...

  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGPWR, Power fail/restart.
  [Switching to Thread -1220760672 (LWP 7388)]
  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGPWR, Power fail/restart.
  [Switching to Thread -1291248736 (LWP 7392)]
  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGPWR, Power fail/restart.
  [Switching to Thread -1292301408 (LWP 7393)]
  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGXCPU, CPU time limit exceeded.
  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGXCPU, CPU time limit exceeded.
  [Switching to Thread -1220760672 (LWP 7388)]
  0xffffe410 in __kernel_vsyscall ()
  (gdb) cont
  Continuing.

  Program received signal SIGXCPU, CPU time limit exceeded.
  [Switching to Thread -1291248736 (LWP 7392)]
  0xffffe410 in __kernel_vsyscall ()
  (gdb)