Why was MediaProvider killed???

[ydcho]

If any text is inserted into MediaStore, can kill MediaProvider??

When I changed a file name in recording program, sometimes It killed Media Provider..

So recording program restarted and the file is not playable..

I saw the log like this...


09-01 14:49:12.392: VERBOSE/AudioSystem(1209): getOutput() read 1 from cache for stream 1
09-01 14:49:12.392: VERBOSE/AudioSystem(1209): [ 09-01 14:49:12.462 12912:0x3279 F/unknown ]
09-01 14:49:12.392: VERBOSE/AudioSystem(1209): stack corruption detected: aborted
09-01 14:49:12.472: INFO/ActivityManager(1209): Process android.process.media (pid 12912) has died.
09-01 14:49:12.472: INFO/ActivityManager(1209): Killing app com.android.soundrecorder (pid 13495) because provider com.android.providers.media.MediaProvider is in dying process android.process.media
09-01 14:49:12.482: INFO/WindowManager(1209): WIN DEATH: Window{2fab5308 com.android.soundrecorder/com.android.soundrecorder.RecordingFileListView paused=false}
09-01 14:49:12.482: INFO/WindowManager(1209): WIN DEATH: Window{2fa39700 com.android.soundrecorder/com.android.soundrecorder.SoundRecorder paused=false}
09-01 14:49:12.482: INFO/ActivityManager(1209): Process com.android.soundrecorder (pid 13495) has died.
09-01 14:49:12.482: INFO/WindowManager(1209): WIN DEATH: Window{2fd50020 com.android.soundrecorder/com.android.soundrecorder.RecordingFileListView paused=false}
09-01 14:49:12.722: INFO/ActivityManager(1209): Start proc com.android.soundrecorder for activity com.android.soundrecorder/.SoundRecorder: pid=13755 uid=10074 gids={1015}
09-01 14:49:12.752: INFO/UsageStats(1209): Unexpected resume of com.android.soundrecorder while already resumed in com.android.soundrecorder
09-01 14:49:12.802: VERBOSE/SoundRecorder(13755): onCreate() called
09-01 14:49:12.802: DEBUG/FROCS(13755): Get Max Heap : 25165824