2

我开发了一个音乐应用程序,它在 Android 之前的冰淇淋三明治上运行良好。但是自从我升级到 4.0.3 后,我开始遇到以前从未遇到过的 MediaPlayer 随机问题。例如,这是我刚刚在实例处于播放完成状态时调用 mediaPlayer.reset 得到的:

07-10 15:27:51.842: D/NuCachedSource2(13537): [setBreak]mForceBreak = 2  
07-10 15:27:51.842: I/ChromiumHTTPDataSourceSupport(13537): initiateDisconnect start  
07-10 15:27:51.852: A/libc(13537): Fatal signal 11 (SIGSEGV) at 0x00000010 (code=1)  
07-10 15:27:52.362: I/DEBUG(13536): debuggerd: 2012-07-10 15:27:52  
07-10 15:27:52.362: I/DEBUG(13536): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***  
07-10 15:27:52.362: I/DEBUG(13536): Build fingerprint: 'tmous/htc_ruby/ruby:4.0.3/IML74K/373265.3:user/release-keys'  
07-10 15:27:52.362: I/DEBUG(13536): pid: 13537, tid: 13537  >>> /system/bin/mediaserver <<<  
07-10 15:27:52.362: I/DEBUG(13536): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000010  
[...]  
07-10 15:27:52.402: I/DEBUG(13536):  scr 60000010  
07-10 15:27:52.542: I/DEBUG(13536):          #00  pc 00000010    
07-10 15:27:52.542: I/DEBUG(13536):          #01  pc 0010f70e  /system/lib/libchromium_net.so (_ZNK3net11BoundNetLog8AddEntryENS_6NetLog9EventTypeENS1_10EventPhaseERK13scoped_refptrINS1_15EventParametersEE)  
07-10 15:27:52.542: I/DEBUG(13536):          #02  pc 0010f71a  /system/lib/libchromium_net.so (_ZNK3net11BoundNetLog8EndEventENS_6NetLog9EventTypeERK13scoped_refptrINS1_15EventParametersEE)  
07-10 15:27:52.542: I/DEBUG(13536):          #03  pc 001a4458  /system/lib/libchromium_net.so (_ZN3net10URLRequest11set_contextEPNS_17URLRequestContextE)  
07-10 15:27:52.552: I/DEBUG(13536):          #04  pc 0012467e  /system/lib/libstagefright.so (_ZN7android10SfDelegate18initiateDisconnectEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #05  pc 00121ca6  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource12disconnect_lEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #06  pc 00121d04  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource10disconnectEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #07  pc 00121776  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource12breakNetworkEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #08  pc 00083b38  /system/lib/libstagefright.so (_ZN7android13AwesomePlayer12breakNetworkENS_18FORCE_BREAK_STATUSE)  
07-10 15:27:52.552: I/DEBUG(13536):          #09  pc 00086c9e  /system/lib/libstagefright.so (_ZN7android13AwesomePlayer5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #10  pc 00027e5e  /system/lib/libmediaplayerservice.so (_ZN7android17StagefrightPlayer5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #11  pc 0002304a  /system/lib/libmediaplayerservice.so (_ZN7android18MediaPlayerService6Client5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #12  pc 00041734  /system/lib/libmedia.so (_ZN7android13BnMediaPlayer10onTransactEjRKNS_6ParcelEPS1_j)  

不久之后:

07-10 15:27:55.645: W/AudioSystem(236): AudioFlinger server died!  
07-10 15:27:55.645: W/AudioSystem(236): AudioPolicyService server died!  
07-10 15:27:55.645: W/AudioSystem(13123): AudioFlinger server died!  
07-10 15:27:55.645: W/IMediaDeathNotifier(13123): media server died  
07-10 15:27:55.645: E/MediaPlayer(13123): error (100, 0)  
07-10 15:27:55.645: E/MediaPlayer(13123): error (100, 0)  
07-10 15:27:55.645: I/ServiceManager(116): service 'media.audio_flinger' died  
07-10 15:27:55.645: I/ServiceManager(116): service 'media.player' died  
07-10 15:27:55.645: I/ServiceManager(116): service 'media.camera' died  
07-10 15:27:55.645: I/ServiceManager(116): service 'media.audio_policy' died  
07-10 15:27:55.645: I/DEBUG(13536): debuggerd committing suicide to free the zombie!  
07-10 15:27:55.665: I/DEBUG(13617): debuggerd: May  2 2012 21:31:04 

有人暗示什么会导致此级别的分段错误?

谢谢。

编辑:经过进一步调查,我发现了一些简单的步骤来重现运行 Android 4.0.3 的 HTC Ruby (HTC Amaze 4G) 上的分段错误:

使用 2 个 MediaPlayer 实例:

  1. 使用第一个实例开始播放一些远程音频文件;
  2. 在第一个实例仍在播放时,使用第二个实例开始播放另一个远程音频文件;
  3. 当第一个实例完成播放时,对其调用重置。这可以。
  4. 当第二个实例完成播放时,对其调用 reset()。出乎意料的是,这会导致 Chromium 内部出现 SIGSEGV,从而导致将媒体服务器死亡错误分派到所有实例。
4

1 回答 1

0

看着那里的logcat,

07-10 15:27:52.542: I/DEBUG(13536):          #00  pc 00000010    
07-10 15:27:52.542: I/DEBUG(13536):          #01  pc 0010f70e  /system/lib/libchromium_net.so (_ZNK3net11BoundNetLog8AddEntryENS_6NetLog9EventTypeENS1_10EventPhaseERK13scoped_refptrINS1_15EventParametersEE)  
07-10 15:27:52.542: I/DEBUG(13536):          #02  pc 0010f71a  /system/lib/libchromium_net.so (_ZNK3net11BoundNetLog8EndEventENS_6NetLog9EventTypeERK13scoped_refptrINS1_15EventParametersEE)  
07-10 15:27:52.542: I/DEBUG(13536):          #03  pc 001a4458  /system/lib/libchromium_net.so (_ZN3net10URLRequest11set_contextEPNS_17URLRequestContextE)  
07-10 15:27:52.552: I/DEBUG(13536):          #04  pc 0012467e  /system/lib/libstagefright.so (_ZN7android10SfDelegate18initiateDisconnectEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #05  pc 00121ca6  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource12disconnect_lEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #06  pc 00121d04  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource10disconnectEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #07  pc 00121776  /system/lib/libstagefright.so (_ZN7android22ChromiumHTTPDataSource12breakNetworkEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #08  pc 00083b38  /system/lib/libstagefright.so (_ZN7android13AwesomePlayer12breakNetworkENS_18FORCE_BREAK_STATUSE)  
07-10 15:27:52.552: I/DEBUG(13536):          #09  pc 00086c9e  /system/lib/libstagefright.so (_ZN7android13AwesomePlayer5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #10  pc 00027e5e  /system/lib/libmediaplayerservice.so (_ZN7android17StagefrightPlayer5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #11  pc 0002304a  /system/lib/libmediaplayerservice.so (_ZN7android18MediaPlayerService6Client5resetEv)  
07-10 15:27:52.552: I/DEBUG(13536):          #12  pc 00041734  /system/lib/libmedia.so (_ZN7android13BnMediaPlayer10onTransactEjRKNS_6ParcelEPS1_j)  

这些行精确地指出了跟踪的来源,它libchromium在某个地方出现了故障,是的,使用的符号名称看起来很模糊,但它是在构建 ROM 时链接的损坏的 C++ 名称。

您从下往上读取跟踪。这就是线索,通常是最上面的#00/pc....#01/pc....如上图所示,是失败的精确点。

可能值得与您的制造商核实以查看是否有可用的更新或查看他们的 HTC 论坛以了解该问题是否已解决?

于 2012-07-10T20:50:55.587 回答