Is it just me or are the daily builds temperamental? Of late since the 600+ the daily builds seem to crash on every little error. I have experienced this lesser with my code, but the code that people send me for review often has this effect. The early versions were *ROCK solid* but not it is worse than writing a null pointer assignment.
cheers,
?
[import]uid: 3826 topic_id: 17413 reply_id: 317413[/import]
I agree I always used latest stable even after being a subscriber and when
I found out latest build can be very useful I started using build 639 and I
notice a lot of crashes that latest build never experienced. I know is best
to “report” them but sometimes is not even worth it with so many different
crashes for little things [import]uid: 30314 topic_id: 17413 reply_id: 65906[/import]
Confirmed here. Build 591 is strong and would rarely crash. As for 655 Sometimes it crashes sometimes it doesnt. It definately crashes more than 591.
JM [import]uid: 39088 topic_id: 17413 reply_id: 65919[/import]
Please provide details or samples of what you talking about. Are you talking about in the simulator or on the device? We do know of a number of problems with the current daily builds but treat crashes as critical issues if it’s something that use to work before.
Having a simple example of what crashes on build 6XX vs. 591 is more helpful than a simple statement saying the “sky is falling.”
With that said, daily builds will crash more often because we are adding code that for the most part is totally untested. Hopefully those bugs are fixed after we do some testing and discover the problem or when users send us bug reports. The reason 591 is “rock solid” is because it went through the test process before release.
Hopefully the final 6XX (or 7XX) build will be rock solid when it’s released for public use because it will go through our testing process too.
Thanks,
Tom [import]uid: 7559 topic_id: 17413 reply_id: 65988[/import]
Yes I got the same issue with the latest builds as well.
The game/app will crash my tablet, Asus Transformer TF101 to dead.
The whole screen will freeze and the status bar buttons are totally unusable.
I’ll have to force restart the device every time it crash.
This is the log for the crash
11-07 22:16:48.119: I/System.out(5182): [INFO:1787]: c: Response [http=200,length=198]
11-07 22:16:48.129: I/System.out(5182): [INFO:1789]: c: Read id 1, status code 200
11-07 22:16:48.159: D/dalvikvm(5150): GC\_FOR\_ALLOC freed \<1K, 27% free 13068K/17671K, paused 26ms
11-07 22:16:48.209: D/dalvikvm(5182): GC\_CONCURRENT freed 260K, 8% free 7712K/8327K, paused 2ms+2ms
11-07 22:16:48.239: D/AlarmManager(193): Removed alarm Alarm{40c377d8 type 2 com.google.android.apps.maps} type:ELAPSED\_REALTIME\_WAKEUP
11-07 22:16:48.239: D/AlarmManager(193): Added alarm Alarm{40c33e30 type 2 com.google.android.apps.maps} type:ELAPSED\_REALTIME\_WAKEUP when: After 596523h:14m:5.0s
11-07 22:16:48.249: D/WifiService(193): releaseWifiLockLocked: WifiLock{NetworkLocationLocator type=2 binder=android.os.BinderProxy@413a5118}
11-07 22:16:51.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:16:51.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:16:52.859: D/dalvikvm(5070): GC\_EXPLICIT freed 53K, 4% free 7392K/7687K, paused 8ms+2ms
11-07 22:16:53.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:16:53.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:16:55.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:16:55.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:16:57.149: D/BatteryService(193): level:71 scale:100 status:4 health:2 present:true dock\_status:1 dock\_level:0 voltage: 7 temperature: 202 technology: Li-ion AC powered:false USB powered:false icon:17302716 invalid charger:0
11-07 22:16:57.149: D/WifiService(193): ACTION\_BATTERY\_CHANGED pluggedType: 0
11-07 22:16:57.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:16:57.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:16:59.259: I/ScreenOn(4794): Call state value: 0
11-07 22:16:59.259: I/ScreenOnService(4794): Service Running! application found: false
11-07 22:16:59.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:16:59.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:01.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:17:01.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:03.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:17:03.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:05.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:17:05.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:06.979: D/AlarmManager(193): Triggered Alarm 408c4978 ELAPSED\_REALTIME\_WAKEUP IntentSender{40cbe298: PendingIntentRecord{40bc2198 android broadcastIntent}}
11-07 22:17:07.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:17:07.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:09.319: E/gralloc(350): GetBufferLock timed out for thread 350 buffer 0x40 usage 0x33 LockState 1
11-07 22:17:09.319: D/gralloc(350): Buffer 40 locks: (tid = 138 (x1), usage = 0x1000)
11-07 22:17:09.989: W/ActivityManager(193): Timeout of broadcast BroadcastRecord{41773868 android.intent.action.TIME\_TICK} - receiver=android.os.BinderProxy@40cbea20, started 10000ms ago
11-07 22:17:09.989: W/ActivityManager(193): Receiver during timeout: BroadcastFilter{409ea028 ReceiverList{40a5af30 350 com.android.systemui/1000 remote:40cbea20}}
11-07 22:17:10.039: I/Process(193): Sending signal. PID: 350 SIG: 3
11-07 22:17:10.039: I/dalvikvm(350): threadid=4: reacting to signal 3
11-07 22:17:10.069: I/dalvikvm(350): Wrote stack traces to '/data/anr/traces.txt'
11-07 22:17:10.069: I/Process(193): Sending signal. PID: 193 SIG: 3
11-07 22:17:10.069: I/dalvikvm(193): threadid=4: reacting to signal 3
11-07 22:17:10.099: I/dalvikvm(193): Wrote stack traces to '/data/anr/traces.txt'
11-07 22:17:10.099: I/Process(193): Sending signal. PID: 381 SIG: 3
11-07 22:17:10.099: I/dalvikvm(381): threadid=4: reacting to signal 3
11-07 22:17:10.109: I/dalvikvm(381): Wrote stack traces to '/data/anr/traces.txt'
11-07 22:17:10.109: I/Process(193): Sending signal. PID: 376 SIG: 3
11-07 22:17:10.109: I/dalvikvm(376): threadid=4: reacting to signal 3
11-07 22:17:10.109: I/dalvikvm(376): Wrote stack traces to '/data/anr/traces.txt'
11-07 22:17:10.329: D/dalvikvm(193): GC\_EXPLICIT freed 861K, 39% free 18793K/30343K, paused 3ms+6ms
11-07 22:17:10.879: I/Process(193): Sending signal. PID: 5150 SIG: 3
11-07 22:17:10.879: I/dalvikvm(5150): threadid=4: reacting to signal 3
11-07 22:17:10.889: I/dalvikvm(5150): Wrote stack traces to '/data/anr/traces.txt'
11-07 22:17:10.899: I/Process(193): Sending signal. PID: 350 SIG: 9
11-07 22:17:10.899: E/ActivityManager(193): ANR in com.android.systemui
11-07 22:17:10.899: E/ActivityManager(193): Reason: Broadcast of Intent { act=android.intent.action.TIME\_TICK flg=0x40000014 (has extras) }
11-07 22:17:10.899: E/ActivityManager(193): Load: 0.15 / 0.34 / 0.68
11-07 22:17:10.899: E/ActivityManager(193): CPU usage from 5014ms to 0ms ago:
11-07 22:17:10.899: E/ActivityManager(193): 20% 90/mediaserver: 20% user + 0.1% kernel
11-07 22:17:10.899: E/ActivityManager(193): 6.1% 5150/com.falx.games.nynycoffeebakeryhd: 4.5% user + 1.5% kernel
11-07 22:17:10.899: E/ActivityManager(193): 4.3% 3/ksoftirqd/0: 0% user + 4.3% kernel
11-07 22:17:10.899: E/ActivityManager(193): 2.9% 193/system\_server: 0.3% user + 2.5% kernel / faults: 19 minor
11-07 22:17:10.899: E/ActivityManager(193): 2.1% 4890/ksoftirqd/1: 0% user + 2.1% kernel
11-07 22:17:10.899: E/ActivityManager(193): 0.3% 64/kinteractiveup: 0% user + 0.3% kernel
11-07 22:17:10.899: E/ActivityManager(193): 0.1% 100/adbd: 0% user + 0.1% kernel
11-07 22:17:10.899: E/ActivityManager(193): 0.1% 4892/kworker/1:2: 0% user + 0.1% kernel
11-07 22:17:10.899: E/ActivityManager(193): 0% 4926/wpa\_supplicant: 0% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 0.1% 5121/kworker/0:1: 0% user + 0.1% kernel
11-07 22:17:10.899: E/ActivityManager(193): +0% 5212/kworker/1:0: 0% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 16% TOTAL: 12% user + 3.1% kernel + 0.7% softirq
11-07 22:17:10.899: E/ActivityManager(193): CPU usage from 330ms to 847ms later:
11-07 22:17:10.899: E/ActivityManager(193): 21% 90/mediaserver: 21% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 21% 159/Playback Thread: 21% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 6.2% 5150/com.falx.games.nynycoffeebakeryhd: 6.2% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 3.1% 5179/Thread-13: 3.1% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 1.5% 5150/ycoffeebakeryhd: 1.5% user + 0% kernel
11-07 22:17:10.899: E/ActivityManager(193): 1.5% 5180/Thread-13: 0% user + 1.5% kernel
11-07 22:17:10.899: E/ActivityManager(193): 5.7% 193/system\_server: 0% user + 5.7% kernel
11-07 22:17:10.899: E/ActivityManager(193): 3.8% 201/SensorService: 0% user + 3.8% kernel
11-07 22:17:10.899: E/ActivityManager(193): 3.8% 204/ActivityManager: 1.9% user + 1.9% kernel
11-07 22:17:10.899: E/ActivityManager(193): 1.5% 4890/ksoftirqd/1: 0% user + 1.5% kernel
11-07 22:17:10.899: E/ActivityManager(193): 15% TOTAL: 14% user + 0.9% kernel
11-07 22:17:10.909: I/ActivityManager(193): Process com.android.systemui (pid 350) has died.
11-07 22:17:10.909: I/WindowManager(193): WIN DEATH: Window{40ac4f40 NotificationPeekWindow paused=false}
11-07 22:17:10.909: W/ActivityManager(193): Scheduling restart of crashed service com.android.systemui/.SystemUIService in 1250ms
11-07 22:17:10.909: E/InputDispatcher(193): channel '40d304b0 NotificationPanel (server)' ~ Consumer closed input channel or an error occurred. events=0x8
11-07 22:17:10.909: E/InputDispatcher(193): channel '40d304b0 NotificationPanel (server)' ~ Channel is unrecoverably broken and will be disposed!
11-07 22:17:10.909: I/WindowManager(193): WIN DEATH: Window{40b80320 RecentsPanel paused=false}
11-07 22:17:10.919: I/WindowManager(193): WIN DEATH: Window{40d304b0 NotificationPanel paused=false}
11-07 22:17:10.919: I/ActivityManager(193): Start proc com.android.systemui for restart com.android.systemui: pid=5214 uid=1000 gids={3002, 1015, 3001, 3003}
11-07 22:17:10.919: I/WindowManager(193): WIN DEATH: Window{40d4e0b0 InputMethodsPanel paused=false}
11-07 22:17:10.919: I/WindowManager(193): WIN DEATH: Window{40c4cef8 StatusBar paused=false}
11-07 22:17:10.969: D/dalvikvm(88): GC\_EXPLICIT freed 11K, 5% free 6787K/7107K, paused 3ms+2ms
11-07 22:17:10.999: D/dalvikvm(88): GC\_EXPLICIT freed \<1K, 5% free 6787K/7107K, paused 1ms+2ms
11-07 22:17:11.029: D/dalvikvm(88): GC\_EXPLICIT freed \<1K, 5% free 6787K/7107K, paused 1ms+1ms
11-07 22:17:14.359: D/AsyncChannel(193): TODO: handle sendMessage RemoteExceptionandroid.os.DeadObjectException
11-07 22:17:15.369: D/AsyncChannel(193): TODO: handle sendMessage RemoteExceptionandroid.os.DeadObjectException
11-07 22:17:15.929: W/SurfaceFlinger(87): closeGlobalTransaction timed out!
11-07 22:17:15.929: I/WindowManager(193): WIN DEATH: Window{40d90e48 CompatModePanel paused=false}
11-07 22:17:15.929: I/WindowManager(193): WINDOW DIED Window{40d304b0 NotificationPanel paused=false}
11-07 22:17:15.939: D/ShutdownThread(193): Notifying thread to start shutdown longPressBehavior=2
11-07 22:17:15.939: D/AlarmManager(193): Added alarm Alarm{40fca490 type 2 android} type:ELAPSED\_REALTIME\_WAKEUP when: After 1h:59m:59.0s
11-07 22:17:15.999: D/SystemUIService(5214): loading: class com.android.systemui.statusbar.tablet.TabletStatusBar
11-07 22:17:16.009: D/SystemUIService(5214): running: com.android.systemui.statusbar.tablet.TabletStatusBar@408ea150
11-07 22:17:16.009: I/StatusBar.HeightReceiver(5214): Resizing status bar plugged=false height=48 old=0
11-07 22:17:16.119: D/dalvikvm(5214): GC\_CONCURRENT freed 124K, 3% free 7169K/7367K, paused 3ms+3ms
11-07 22:17:16.149: D/dalvikvm(5214): GC\_FOR\_ALLOC freed 11K, 4% free 7251K/7495K, paused 20ms
11-07 22:17:16.149: I/dalvikvm-heap(5214): Grow heap (frag case) to 7.988MB for 876076-byte allocation
11-07 22:17:16.189: D/dalvikvm(5214): GC\_CONCURRENT freed 0K, 4% free 8107K/8391K, paused 2ms+3ms
11-07 22:17:16.209: D/dalvikvm(5214): GC\_FOR\_ALLOC freed 1K, 4% free 8106K/8391K, paused 20ms
11-07 22:17:16.209: I/dalvikvm-heap(5214): Grow heap (frag case) to 8.823MB for 876076-byte allocation
11-07 22:17:16.239: D/dalvikvm(5214): GC\_FOR\_ALLOC freed 0K, 4% free 8961K/9287K, paused 20ms
11-07 22:17:16.279: D/dalvikvm(5214): GC\_CONCURRENT freed 4K, 3% free 9047K/9287K, paused 1ms+2ms
[import]uid: 75843 topic_id: 17413 reply_id: 66191[/import]
Please re-read my thread about supplying example code that demonstrates the problem. Crash logs generally don’t provide any information (especially when they don’t show any information of what crashed in the Corona app).
Also be aware that you can have bugs in your code that don’t seem to cause any obvious problems and your code still runs but may be causing things to happen that you can’t track down. As we work on Corona to fix bugs and add features we come across “bugs” that haven’t been reported and fix them. This could cause code that seem to run “rock solid”, now fail. If this code runs on the simulator, you will get a run-time error. If it runs on the device it will generate an assert and cause the app to stop, hence looking like it crashed.
It’s always best to check the print logs (logcat in Android, console in iOS) for any run-time errors. The daily builds (around 600) added a run-time check that will display an error message if something generates an assert on the device. It doesn’t provide the file/line number of the error, but at least gives an indication that you have something wrong in your code. The biggest source of run-time errors (crashes) that I’ve come across is “nil” values. Trying to “insert” a nil value into a group will crash your app every time. (This is not the only case, but a pretty common example.) [import]uid: 7559 topic_id: 17413 reply_id: 66274[/import]
Ya my problem is in the simulator. Its not a really big deal it just seems tempermental. Before if I coded something wrong it would through an error in the terminal and not crash. But now it will throw an error in the terminal and crash. Like I said not a really big deal. As long as i still get an error in the terminal its all good.
Thanks, JM [import]uid: 39088 topic_id: 17413 reply_id: 66354[/import]