View Single Post
Posts: 291 | Thanked: 398 times | Joined on Jan 2011 @ USA
#35
Originally Posted by stlpaul View Post
Sure. It's unfortunately not reproduceable by specific instructions, but out of good (bad?) luck, it just crashed the very first time I tried it after reading your message.

I opened the program, clicked a video from the main screen, clicked two related videos in a row, it showed "cannot open media source" briefly (maybe 100 milliseconds) and then crashed before I could click OK on the message. I don't remember seeing the "cannot open media source" message the last times when it was crashing, maybe it's a red herring.

When I restarted and tried the exact same behavior again, it didn't crash. I browsed probably 50 videos with no crash this time...

My general usage pattern when I encountered these crashes basically involved watching lots of related videos, several levels deep of related, going back to main menu and watching some others. Sometimes stopping or skipping ahead in videos, changing between fullscreen and windowed mode (or however you want to call the non-fullscreen mode). I browsed by category, but the crashed happened even without utilizing that feature. I did not use search at all.

Next time I'll try starting nvideo from commandline, in case it produces any interesting messages if it crashes again.

I'm using CSSU and kernel-power v49. Let me know if there's any other info I can provide that might be useful. Thanks!
Thanks very much stlpual for taking your time to provide a thorough report. I had tried to abuse the app by tapping and switching crazily using the same behavior you described above with the intention of trying to make it crash, but can't seem to make it crash. Maybe it still depends on each device configuration, I am currently running stock firmware with overclock kernel v46. From what you described the crash related to playing video with several deep related videos, which made me think that the possibility is the backend video engine may be gone out of wacked when handling fast chaning video stream or unstable network connection may play an important role here. All i can do in this situation is implementing a way to renew or reset the backend video engine object after certain number of videos has been handled in a row. The "can't not open media source" is an error produced by backend video engine which related to invalid video data, this may be the unstability or data packet loss of network, or invalid video stream. This is out of my control just like buffering or lagging.

If anyone with cssu or not run into the same problem described by stlpaul, please be kind to report it here so I can sort it out to see where the actual problem is before I release the final version.
I consider this app is my last project for n900, and also a going away gift to this community which was very supportive in every way and had produced many free great app for n900 users.

I won't be having time to involve in anything else beside my incoming baby girl at the end of this month, and this will my first time being a daddy though feeling exited but nervous as hell, so help me god...
 

The Following 3 Users Say Thank You to khuong For This Useful Post: