On Thu, Apr 14, 2011 at 08:40:12AM -0000, Didier Roche wrote:
> Sure, can you upload to core dump in case we can have a look
What's the best way to share it with you? I'm not keen to attach publicly
it in Launchpad as it could contain personal data.
> The other bug mentioned by David is a global valgrind run for compiz and
> we only track the Nux mem leak fix in it.
OK, so since this bug occurs without unity, it's a separate issue.
> On the --replace where older compiz process doesn't stop, there is no
> bug tracking it. We just experienced that within the team (and should
> not impact normal users as compiz is only restarted by gnome-session
> after a crash). Sam had a look at it last week IIRC without founding
> particular evidence of the issue (and we are prioritizing other more
> "main usage" bugs).
On Thu, Apr 14, 2011 at 08:40:12AM -0000, Didier Roche wrote:
> Sure, can you upload to core dump in case we can have a look
What's the best way to share it with you? I'm not keen to attach publicly
it in Launchpad as it could contain personal data.
> The other bug mentioned by David is a global valgrind run for compiz and
> we only track the Nux mem leak fix in it.
OK, so since this bug occurs without unity, it's a separate issue.
> On the --replace where older compiz process doesn't stop, there is no
> bug tracking it. We just experienced that within the team (and should
> not impact normal users as compiz is only restarted by gnome-session
> after a crash). Sam had a look at it last week IIRC without founding
> particular evidence of the issue (and we are prioritizing other more
> "main usage" bugs).
I will file a bug about this then.
--
- mdz