closing this bug then - if you can replicate it again then pls reopen
** Changed in: tracker (Ubuntu)
Status: Incomplete => Invalid
--
trackerd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/147430
You received this bug notification because you are a member of Ubu
I can't reproduce it at all.
It's extremely unlikely that there wasn't any free memory when it
crashed. I couldn't even use up the 1.5GB of RAM, much less the 2GB of
swap, when I tried to.
--
trackerd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/147430
You received thi
are you able to reliably replicate this crash?
if so does it crash on same word "0500cdt"?
normally a crash (in g_array_sized_new) there is an out of memory thing
- can you try and replicate and keep an eye on free ram pls and get back
to me
** Changed in: tracker (Ubuntu)
Status: New =>
** Visibility changed to: Public
--
trackerd crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/147430
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
