Bug 1117711 - Crash caught under valgrind
Summary: Crash caught under valgrind
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-mission-control
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-09 08:56 UTC by Tim Waugh
Modified: 2014-09-08 16:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-08 16:30:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
valgrind-mission-control-5-21883.log (3.14 KB, text/plain)
2014-07-09 08:56 UTC, Tim Waugh 		no flags Details
View All

Description Tim Waugh 2014-07-09 08:56:00 UTC 
Created attachment 916678 [details]
valgrind-mission-control-5-21883.log

Description of problem:
While running telepathy-mission-control under valgrind in order to find out why it occasionally dies, I caught this crash.

Version-Release number of selected component (if applicable):
telepathy-mission-control-5.16.1-1.fc20

How reproducible:
Rare but enough to be annoying.

Additional info:
(sorry this is filed late)
Comment 1 Peter Robinson 2014-08-29 18:55:07 UTC 
Tim can you test against telepathy-mission-control-5.16.3-1.fc20 please?
Comment 2 Tim Waugh 2014-09-01 11:16:22 UTC 
I'm running F21 at the moment, where it doesn't seem to happen, but I'll try catching it in F20.
Comment 3 Tim Waugh 2014-09-08 14:35:37 UTC 
FWIW, it doesn't happen in F21 with telepathy-mission-control-5.16.3-1.fc21.x86_64.
Comment 4 Peter Robinson 2014-09-08 16:30:33 UTC 
(In reply to Tim Waugh from comment #3)
> FWIW, it doesn't happen in F21 with
> telepathy-mission-control-5.16.3-1.fc21.x86_64.

OK, will close off, reopen if it starts again with 5.16.3
Note You need to log in before you can comment on or make changes to this bug.