Opened 5 years ago

Closed 5 years ago

#11245 closed bug (duplicate)

Media addon server crashes at boot

Reported by: edglex Owned by: axeld
Priority: normal Milestone: R1
Component: Servers/media_addon_server Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #9804
Has a Patch: no Platform: x86

Description

Crashes inside MultiAudioAddOn::_LoadSettings() after every boot.

Perhaps this is due to something else I have installed recently?

Hrev 57853

Attachments (5)

media_addon_server-650-debug-15-09-2014-10-21-55.report (23.0 KB ) - added by edglex 5 years ago.
media_addon_server-3634-debug-15-09-2014-10-56-12.report (9.2 KB ) - added by edglex 5 years ago.
message output (1) (5.0 KB ) - added by edglex 5 years ago.
message output (2) (1.1 KB ) - added by edglex 5 years ago.
message-4113-debug-15-09-2014-11-01-48.report (19.6 KB ) - added by edglex 5 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 by edglex, 5 years ago

Platform: Allx86

comment:2 by edglex, 5 years ago

Milestone: R1/alpha5R1

comment:3 by edglex, 5 years ago

When running /boot/system/servers/media_addon_server manually I get a different crash, (see attached). The debugger has a "Stop reason" (where does this information come from?) of "System time source got wrong node ID" which sounds similar to 11228, but the stack trace is completely different. Restarting from the button in media preferences gives a crash the same as in the original report.

Last edited 5 years ago by edglex (previous) (diff)

comment:4 by edglex, 5 years ago

Tried "message ~/config/settings/Media/multi_audio_settings" at PulkoMandys suggestion and at first got the attached (1), but second time it crashed out (output (2) and debug report again attached).

Last edited 5 years ago by edglex (previous) (diff)

by edglex, 5 years ago

Attachment: message output (1) added

by edglex, 5 years ago

Attachment: message output (2) added

comment:5 by edglex, 5 years ago

Moving the settings file made everything work again, so I guess it was a corrupt file.

So BMessage should have better checks for sane input I guess?

comment:6 by waddlesplash, 5 years ago

Blocking: 9804 added
Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.