search

Mobiperf / MobiPerf

New MobiPerf Repository
http://mobiperf.com
Other
87 stars 62 forks source link

App crash #102

Closed quietbamboo closed 12 years ago

quietbamboo commented 12 years ago

Bug found.

I've run MobiPerf this morning. I'm running it with Android 2.3.3, with WiFi access.

Attached is the debug.txt (output of adb logcat *:s 'Mobiperf') and bugreport.txt (output of adb bugreport).

What I've done is, first run an UDP down experiment (the result says PRR 0.0, so not sucessful?), then run an UDP up experiment (the results says experiment has failed, I'm not sure why). Then I go to results tab and also looked at the system logs. Then the app crashes.

I'm not exactly sure the cause of the crash, but I think it is NOT caused by this exception "java.lang.RuntimeException: No google account found" since I've observed the app working fine while producing it.

The file attachments are in the email. Search for "debug.txt" or "bugreport.txt" in your emails.

mdwelsh commented 12 years ago

Yeah, there's a known problem with switching between these views. It's been hard to isolate... Is this crash consistently repeatable? On Sep 22, 2012 9:44 AM, "Junxian Huang" notifications@github.com wrote:

Bug found.

I've run MobiPerf this morning. I'm running it with Android 2.3.3, with WiFi access.

Attached is the debug.txt (output of adb logcat *:s 'Mobiperf') and bugreport.txt (output of adb bugreport).

What I've done is, first run an UDP down experiment (the result says PRR 0.0, so not sucessful?), then run an UDP up experiment (the results says experiment has failed, I'm not sure why). Then I go to results tab and also looked at the system logs. Then the app crashes.

I'm not exactly sure the cause of the crash, but I think it is NOT caused by this exception "java.lang.RuntimeException: No google account found" since I've observed the app working fine while producing it.

The file attachments are in the email. Search for "debug.txt" or "bugreport.txt" in your emails.

— Reply to this email directly or view it on GitHubhttps://github.com/Mobiperf/MobiPerf/issues/102.

quietbamboo commented 12 years ago

It's not consistently repeatable. Hopefully, from my debug.txt and bugreport.txt, we can find some clue of what's happening during that crash.

ghost commented 12 years ago

Attachments at: https://gist.github.com/3776713

ghost commented 12 years ago

09-22 12:11:43.368 127 132 I am_crash: [1108,com.mobiperf.speedometer,572998,java.lang.IllegalStateException,The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. [in ListView(2131361792, class android.widget.ListView) with Adapter(class android.widget.ArrayAdapter)],ListView.java,1573]

Seems pertinent.

mdwelsh commented 12 years ago

Yes, this is the bug I've been trying to nail down. I'll keep working on it.

On Mon, Sep 24, 2012 at 9:10 AM, Dominic Hamon notifications@github.comwrote:

09-22 12:11:43.368 127 132 I am_crash: [1108,com.mobiperf.speedometer,572998,java.lang.IllegalStateException,The content of the adapter has changed but ListView did not receive a notification. Make sure the content of your adapter is not modified from a background thread, but only from the UI thread. [in ListView(2131361792, class android.widget.ListView) with Adapter(class android.widget.ArrayAdapter)],ListView.java,1573]

Seems pertinent.

— Reply to this email directly or view it on GitHubhttps://github.com/Mobiperf/MobiPerf/issues/102#issuecomment-8824408.

ghost commented 12 years ago

If this is the same as #85, we should probably close it.