according to comment #6, it looks like is the same bug as bug 1058303 and they just came out a patch for their issue, maybe that patch is worth to try.
according to comment #6, it looks like is the same bug as bug 1058303
and they just came out a patch for their issue, maybe that patch is worth to try.