Modify ↓

Ticket #10554 (closed Bug Report - Crash: Duplicate)

Opened 15 months ago

Last modified 15 months ago

mythfrontend crashed with SIGSEGV in QMutex::lock()

Reported by: Marc Randolph <mrand@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description 

StacktraceTop:
 QMutex::lock (this=0x48000022b10d8d90) at thread/qmutex.cpp:150
 QCoreApplication::postEvent (receiver=0x16aad10, event=0x7ffa78016140, priority=0) at kernel/qcoreapplication.cpp:1281
 MythObservable::dispatch (this=0x167d340, event=...) at mythobservable.cpp:86
 MythCoreContext::dispatch (this=0x167d340, event=...) at mythcorecontext.cpp:1191
 Reconnect::run (this=<optimized out>) at backendconnectionmanager.cpp:30

Forwarding upstream from: ​https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/962981 See attachments for more complete traces.

Attachments

var.log.mythtv.mythfrontend.log.txt​ (103.0 KB) - added by Marc Randolph <mrand@…> 15 months ago.
Stacktrace.txt​ (2.1 KB) - added by Marc Randolph <mrand@…> 15 months ago.
ThreadStacktrace.txt​ (83.1 KB) - added by Marc Randolph <mrand@…> 15 months ago.
ThreadStacktrace.2.txt​ (83.1 KB) - added by Marc Randolph <mrand@…> 15 months ago.

Change History

Changed 15 months ago by Marc Randolph <mrand@…>

Changed 15 months ago by Marc Randolph <mrand@…>

Changed 15 months ago by Marc Randolph <mrand@…>

Changed 15 months ago by Marc Randolph <mrand@…>

comment:1 Changed 15 months ago by beirdo

What exactly was the user doing when this happened?

comment:2 Changed 15 months ago by beirdo

  • Status changed from new to infoneeded_new

comment:3 Changed 15 months ago by beirdo

See also #10556

comment:4 Changed 15 months ago by stuartm

  • Status changed from infoneeded_new to closed
  • Resolution set to Duplicate

Duplicate of #10359

View ↑

Add a comment

Modify Ticket

Action
as closed
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

Attachments ↑
 
Note: See TracTickets for help on using tickets.