[Hugin-devs] [Bug 1316967] Re: Maximum TIFF file size 4GB

[Christoph Spiel]

This is not an Enblend (or Enfuse)
problem.  Both applications rely on the Vigra
library for I/O of images of _any_ format, i.e.
the functions described in
https://ukoethe.github.io/vigra/doc/vigra/group__VigraImpex.html
This is in fact one of the main reasons to use
an imaging library as e.g. Vigra.

You could ask the Vigra developers for
integration of BigTIFF into Vigra or even supply
the necessary patch yourself.

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1316967

Title:
  Maximum TIFF file size 4GB

Status in Enblend:
  New

Bug description:
  Hi there!

  After running for 2 days the enblend binary that I compiled myself
  from the enblend sources revision 1049 failed with this error:

  enblend: info: writing final output
  enblend: error: Maximum TIFF file size exceeded

  enblend: an exception occured
  enblend: 
  Postcondition violation!
  exportImage(): Unable to write TIFF data.
  (/build/buildd/libvigraimpex-1.9.0+dfsg/src/impex/tiff.cxx:811)

  enblend: info: remove invalid output image x1.tif
  ===

  I've used these parameters:  --compression=LZW --verbose
  --output=x1.tif

  The output pixel dimensions would have been 119598 * 17362 =
  2076460476 which is still well within the 2^31 pixel count limit =
  2147483648

  In the bug report #685105 I've mentioned that I've run into this problem 
before, and back then Jeff Hungerford (hungerf3) told me:
  If you are seeing that error, either the TIFF library you linked against 
doesn't support bigTIFF, or for some reason it decided to only use the old 
format.

  It would be very kind of you if you could guide my way how to compile
  enblend (and libtiff?) in a way that enblend will not fail when the
  output exceeds 4GB in file size.

  Or is there maybe a way to use another output format then tif to
  workaround this problem? (With Gimp I like to use png for images that
  are too big for 4GB tif, it has the same problem of failing to save
  4GB tiffs for me)

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1316967/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp

[Hugin-devs] [Bug 1318207] [NEW] segfault on exit if built against wxwidgets3.0

[Andreas Metzler]

Public bug reported:

Hello,

hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
against wxwidgets3.0 (instead of 2.8):


Program received signal SIGSEGV, Segmentation fault.
0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
(gdb) bt
#0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#1  0xf64b9343 in __cxa_finalize ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
#4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#6  0xf649fa6b in __libc_start_main ()
   from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#7  0x080f5b10 in _start ()


Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
Program received signal SIGSEGV, Segmentation fault.
0x0031 in ?? ()
(gdb) bt
#0  0x0031 in ?? ()
#1  0x741c121f in ?? ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
at cxa_finalize.c:56
#3  0x74154723 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
#4  0x7fffe210 in ?? ()
#5  0x77debf3a in _dl_fini () at dl-fini.c:252
Backtrace stopped: frame did not save the PC

cu Andreas

** Affects: hugin
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1318207

Title:
  segfault on exit if built against wxwidgets3.0

Status in Hugin - Panorama Tools GUI:
  New

Bug description:
  Hello,

  hugin 2014.0.0 rc2 segfaults when I exit the program if I build hugin
  against wxwidgets3.0 (instead of 2.8):

  
  Program received signal SIGSEGV, Segmentation fault.
  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  (gdb) bt
  #0  0xf698e517 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #1  0xf64b9343 in __cxa_finalize ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #2  0xf6913983 in ?? () from /usr/lib/i386-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #3  0xf7febdcc in ?? () from /lib/ld-linux.so.2
  #4  0xf64b8fb1 in ?? () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #5  0xf64b900d in exit () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #6  0xf649fa6b in __libc_start_main ()
 from /lib/i386-linux-gnu/i686/cmov/libc.so.6
  #7  0x080f5b10 in _start ()
  

  Olly Betts  got a diffferent bt in https://bugs.debian.org/746528:
  Program received signal SIGSEGV, Segmentation fault.
  0x0031 in ?? ()
  (gdb) bt
  #0  0x0031 in ?? ()
  #1  0x741c121f in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #2  0x729d4f2f in __cxa_finalize (d=0x74456fc0)
  at cxa_finalize.c:56
  #3  0x74154723 in ?? ()
 from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_adv-3.0.so.0
  #4  0x7fffe210 in ?? ()
  #5  0x77debf3a in _dl_fini () at dl-fini.c:252
  Backtrace stopped: frame did not save the PC

  cu Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/hugin/+bug/1318207/+subscriptions

___
Mailing list: https://launchpad.net/~hugin-devs
Post to : hugin-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~hugin-devs
More help   : https://help.launchpad.net/ListHelp