Summary: | Crash when receiving a google file transfer | ||
---|---|---|---|
Product: | nice | Reporter: | Guillaume Desmottes <guillaume.desmottes> |
Component: | General | Assignee: | Youness Alaoui <youness.alaoui> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Guillaume Desmottes
2012-04-27 04:53:08 UTC
Looks like a nice crash, re-assigning. This is with libnice 0.1.1 The stack trace makes no sense, there is no reason for the source to be 0xaaaaaaaa. It is initialized to NULL and always set to NULL after being destroyed, and even if it wasn't set to NULL, it would contain a freed source, which would be a 'random' memory location, not 0xaaaaaaaa.. so my best guess is that there is memory coruption somewhere in either gabble or libnice. Since you can always reproduce this bug, could you try to get a valgrind report please, from there, we would know who is corrupting the stack? I updated to libnice 0.1.1 and gupnp-id 0.2.1 and that seems to have fixed the problem. Ah ok. It was probably caused by gupnp-igd. I don't remember any bugfix in 0.1.1 that could have caused this. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.