looking at the report mterry posted it looks like coming from qtubuntu-media. I'm not familiar with that code base but after having a quick look these caught my eye:
First m_service is static, so if ever more than one instance of AalMediaPlayerService is created things will brobably break. Should that be a singleton instead?
secondly, there is is connection made to m_hubPlayerSession, but it is not disconnected in
nor in the destructor ~AalMediaPlayerService() even though the (static) m_service might get descructed as it's parent is relayed to it's parent QObject class.
looking at the report mterry posted it looks like coming from qtubuntu-media. I'm not familiar with that code base but after having a quick look these caught my eye:
http:// bazaar. launchpad. net/~phablet- team/qtubuntu- media/trunk/ view/head: /src/aal/ aalmediaplayers ervice. cpp:
AalMediaPlayerS ervice: :AalMediaPlayer Service( QObject *parent): Session- >playback_ status_ changed( ).connect(
std: :bind(& AalMediaPlayerS ervice: :onPlaybackStat usChanged, this, _1));
...
m_service = this;
---
m_hubPlayer
...
First m_service is static, so if ever more than one instance of AalMediaPlayerS ervice is created things will brobably break. Should that be a singleton instead?
secondly, there is is connection made to m_hubPlayerSession, but it is not disconnected in
void ervice: :setPlayer( const std::shared_ ptr<core: :ubuntu: :media: :Player> &player) Session = player;
AalMediaPlayerS
{
m_hubPlayer
}
nor in the destructor ~AalMediaPlayer Service( ) even though the (static) m_service might get descructed as it's parent is relayed to it's parent QObject class.