[Digikam-devel] [Bug 188334] Crash when applying free rotation to TIF16 picture
Marcel Wiesweg
marcel.wiesweg at gmx.de
Sun Apr 12 20:01:49 BST 2009
https://bugs.kde.org/show_bug.cgi?id=188334
Marcel Wiesweg <marcel.wiesweg at gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marcel.wiesweg at gmx.de
--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de> 2009-04-12 21:01:47 ---
Excerpt from comment #1:
#6 0xffffe430 in __kernel_vsyscall ()
#7 0xb53b5990 in raise () from /lib/libc.so.6
#8 0xb53b72c8 in abort () from /lib/libc.so.6
#9 0xb55ddaf8 in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/libstdc++.so.6
#10 0xb55db445 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb55db482 in std::terminate() () from /usr/lib/libstdc++.so.6
#12 0xb55db5ba in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb55dc1a3 in operator new(unsigned int) () from /usr/lib/libstdc++.so.6
#14 0xb55dc28d in operator new[](unsigned int) () from /usr/lib/libstdc++.so.6
#15 0xb708e324 in Digikam::DImg::allocateData (this=0xab4531dc)
operator new() aborts when it fails, when it cannot allocate the memory
requested. This could be because your memory is really full including swap
space, or there is a bug somewhere eating amounts of memory.
(A large 16 bits image can eat lots of memory. Dont know about buffer needed by
free rotation)
Usually there is error output on the console which might be helpful.
Please clarify your memory situation as well.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Digikam-devel
mailing list