Application crashes with Android 2.3.3 update

Hi All,
My development phone(Google-Nexus One) recently received the Android 2.3.3 update and although native applications run faster my Air application is failing basic test cases.
Simply scrolling a list with TileLayout and MobileIconItemRenderer causes the application to crash. Error dialog reports the the application process has stopped responding and only option is to force close. Scrolling is very cluncky and not usable on 2.3.3(disregarding the crashing), testing the same build on Android 2.2 is fine.
Has anyone else seen performance/stability issues with Android 2.3.3 update?
Any help is much appreciated,
Cheers,
Greg

As I said, I installed a new version of Android in my smartphone, which forced me to reinstall all the applications (including the Adobe AIR), so it's the version 2.7.1.1961.
I checked other applications that depend on Adobe AIR and see that is a common problem with Adobe AIR applications and several people complain about.

Similar Messages

Applications crashing with dyld error messages: CFURLStorageSessionGetDefault

All was working fine (been told to hold off on updates so have not installed them, yet I am running 10.6.8 [10K549]). Suddenly after a reboot applications crash with the same error:
Dyld Error Message:
Symbol not found: __CFURLStorageSessionGetDefault
Referenced from: /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
Can not open Terminal. Can not open Skype (removed 2.x version, downloaded latest 5.3.59 and installed), can not run Evolution (starts, but when clicking a message same error). Attempted to install 10.6.8 bundled update (manual download), but when selected to open get yet again - the same crash error.
Was able to create a new user and same issues with that account. Any help?!

My system has a PGP encrypted disk (so no booting from CD to fix). It appears that one of Apple's AUTO updates (though I have them manually turned off!!) has screwed my system to the point of making the OS show up as a version that is not running. Due to the versioning not being right the applications crash. The verdict: rebuild.
So yeah, this *****.

Application crashes with timesten database over OCI connection

Application crashes with timesten database over OCI connection
#0 0x405e09f8 in kpudsany () from /home/oracle/TimesTen/ratingtt1121/ttoracle_home/instantclient_11_1/libclntsh.so.10.1
#1 0x405728d0 in OCIDescribeAny () from /home/oracle/TimesTen/ratingtt1121/ttoracle_home/instantclient_11_1/libclntsh.so.10.1
#2 0x43748a5a in GDBociDriver::StoredProcArgumentList () from /home/omni/library/libgfr_dboci.so
#3 0x4374e865 in GDBociDriver::StoredProcCallFormat () from /home/omni/library/libgfr_dboci.so
#4 0x4376ec9a in GDBociDriver::ExecuteStmtBind () from /home/omni/library/libgfr_dboci.so
#5 0x4376fc69 in GDBociDriver::Execute () from /home/omni/library/libgfr_dboci.so
#6 0x436ba240 in GDBstatement::Execute () from /home/omni/library/libgfr_dblayer.so
#7 0x43736106 in GDBociDriver::SetModule () from /home/omni/library/libgfr_dboci.so
#8 0x4366cb22 in GDBconnectionPool::GetConnection () from /home/omni/library/libgfr_dblayer.so
#9 0x4367a9db in GDBdriver::LoginConnectionGet () from /home/omni/library/libgfr_dblayer.so
#10 0x4373dbaa in GDBociDriver::Login () from /home/omni/library/libgfr_dboci.so
#11 0x4377380f in CreateOCIDriver () from /home/omni/library/libgfr_dboci.so
#12 0x4367bb2a in GDBdriverLoader::CreateDriver () from /home/omni/library/libgfr_dblayer.so
#13 0x436d423d in IGDBdriverMgr::GetDriverAndLogin () from /home/omni/library/libgfr_dblayer.so
#14 0x436d4da1 in IGDBdriverMgr::GetDriver () from /home/omni/library/libgfr_dblayer.so
#15 0x436a5071 in GDBserverDef::InitialLogin () from /home/omni/library/libgfr_dblayer.so
#16 0x433247cc in CcapAdbAccess::Init (this=0x9e85a88) at CcapAdbAccess.C:161
#17 0x43331c44 in CcapMain::Run (this=0x434eeb80, sdpId=2, processName=0x9dae29c "URE61_O2") at CcapMain.C:132
#18 0x080947d1 in ccap_thread (arg=0x0) at main.C:1588
#19 0x080e7bd2 in ThreadManager::WrapperRoutine (ipArg=0x9e84fc0) at ThreadManager.C:176
#20 0x0035f44a in start_thread () from /lib/libpthread.so.0
Timesten has some limitations and it says:
Describing objects with OCIDescribeAny() is supported only by name. Describing PL/SQL objects is not supported.
home/omni/library/libgfr_dblayer.so
Cloud you please tell us whit might be the reason for this

Are you able to provide exact details of the OCIDescribeAny call being made by the application (including parameter values)?
Chris

Application crash with error ntdll.dll 00018fea

Hi,
I have a problem with my app.exe build.
I attach a simple code; the Vi open and close a TDM file.
If I run this Vi in Labview works fine.
If I build the application.exe on a notebook and I run it I got "Application crash with error ntdll.dll 00018fea".
I've tried to build the Vi on another Pc Desktop with Labview and here if I run the exe it works fine.
On the two PC I have LV8.5; the build options are the same.
On the notebook I've try also to reinstall LV8.5 but I got the same error.
Can you help me?
Thanks a lot
Attachments:
open tdm.vi ‏33 KB

MicheleS wrote:
This morning I've try to put the ntdll.dll of the other PC in the notebook but the problem remain.
Never ever do that! You were very lucky that both ntdll.dll files were probably the same version so the exchange didn't do much but ntdll.dll is one of the core Windows DLLs were everything goes through that normal applications may access in Windows. A mixup in such a part because of incompatitible ntdll.dll with other system API DLLs might prevent your computer entirely from starting up even in safe mode.
You should not attempt to ever switch system DLLs between different computers. In such behaviour lays insanity. If you expect a system DLL to be corrupt attempt to do a repair installation instead. Also Windows nowadays has techniques to detect if a system DLL got corrupt and will attempt to repair it, though I guess if ntdll.dll would go belly up it's likely your computer won't even start up.
Rolf Kalbermatter
Message Edited by rolfk on 01-14-2008 08:05 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Application Crashes with Problem Event Name:BEX64 and Fault Module Name:MSVCR110.dll

After building my application in VS2012 Update 4 ,application started crashing with the below mentioned problem signature.
Problem signature:
Problem Event Name: BEX64
Application Name: App.exe
Application Version: 1.0.0.1
Application Timestamp: 52fdbd9d
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098826e
Exception Offset: 000000000006d4f9
Exception Code: c0000417
Exception Data: 0000000000000000
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: 1032
Additional Information 2: 103247eabca85d12954263c679d66e19
Additional Information 3: 7fa2
Additional Information 4: 7fa2470b0fea6279055c0db583abca71
Any help is appreciated.

Hi,
To debug this kind of issue, we recommend you to post in MSDN forum because they are more familiar with developing and debugging app:
http://social.msdn.microsoft.com/Forums/vstudio/en-US/home?category=visualstudio
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support

AIR Native Extension Application Crash on Android Emulator when Extension method is invoked

I have developed a Hello World Application using AIR Native Extension on Android Emulator and When i try to run the application its crashes. I was able to run same application sometimes back on Android Emulator on Mac. Right now I am using a Windows machine (as i dont have Mac anymore). I tried running same apk file which was compiled and running on Android emulator on Mac but it failed. Also i tried to recompile entire application from same code base but still it is failing. As far as i know Mac or windows should not play a part but still mentioning it out in the discussion. Also i tried running the application on various Android SDK version but with same results.
Following is logcat logs for Android 4.0.3.
D/gralloc_goldfish( 497): Emulator without GPU emulation detected.
I/ActivityManager(   84): Displayed air.com.deloitte.helloWorld/.AppEntry: +4s82
6ms
W/InputManagerService(   84): Starting input on non-focused client com.android.i
nternal.view.IInputMethodClient$Stub$Proxy@413e17e0 (uid=10009 pid=179)
W/ActivityManager(   84): Launch timeout has expired, giving up wake lock!
W/ActivityManager(   84): Activity idle timeout for ActivityRecord{41534258 air.
com.deloitte.helloWorld/.AppEntry}
W/NetworkManagementSocketTagger(   84): setKernelCountSet(10009, 0) failed with
errno -2
E/dalvikvm( 497): JNI ERROR (app bug): attempt to use stale local reference 0x5
d500031
W/dalvikvm( 497): JNI WARNING: 0x5d500031 is not a valid JNI reference
W/dalvikvm( 497):              in Lcom/adobe/air/customHandler;.nativeOnTouchCa
llback:(IFFFIFFZ[FI)Z (CallObjectMethodV)
I/dalvikvm( 497): "main" prio=5 tid=1 RUNNABLE
I/dalvikvm( 497):   | group="main" sCount=0 dsCount=0 obj=0x409c1460 self=0x128
10
I/dalvikvm( 497):   | sysTid=497 nice=0 sched=0/0 cgrp=default handle=107408295
2
I/dalvikvm( 497):   | schedstat=( 12139801627 5119955457 1265 ) utm=1128 stm=85
core=0
I/dalvikvm( 497):   at com.adobe.air.customHandler.nativeOnTouchCallback(Native
Method)
I/dalvikvm( 497):   at com.adobe.air.customHandler.nativeOnTouchCallback(Native
Method)
I/dalvikvm( 497):   at com.adobe.air.customHandler.handleMessage(customHandler.
java:23)
I/dalvikvm( 497):   at android.os.Handler.dispatchMessage(Handler.java:99)
I/dalvikvm( 497):   at android.os.Looper.loop(Looper.java:137)
I/dalvikvm( 497):   at android.app.ActivityThread.main(ActivityThread.java:4424
I/dalvikvm( 497):   at java.lang.reflect.Method.invokeNative(Native Method)
I/dalvikvm( 497):   at java.lang.reflect.Method.invoke(Method.java:511)
I/dalvikvm( 497):   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.r
un(ZygoteInit.java:784)
I/dalvikvm( 497):   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:
551)
I/dalvikvm( 497):   at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 497):
E/dalvikvm( 497): VM aborting
F/libc    ( 497): Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1)
I/DEBUG   (   34): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
I/DEBUG   (   34): Build fingerprint: 'generic/sdk/generic:4.0.3/MR1/237985:eng/
test-keys'
I/DEBUG   (   34): pid: 497, tid: 497 >>> air.com.deloitte.helloWorld <<<
I/DEBUG   (   34): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00
d
I/DEBUG   (   34): r0 00000000 r1 00097bd8 r2 00000000 r3 00000000
I/DEBUG   (   34): r4 deadd00d r5 40872c58 r6 0000020c r7 49622e39
I/DEBUG   (   34): r8 4084ee67 r9 4084e703 10 4084ee73 fp 4084f546
I/DEBUG   (   34): ip 00000000 sp bed6a248 lr 4080bc8f pc 4080bc8e cpsr 600
00030
I/DEBUG   (   34): d0 3f8000003f800000 d1 4b00106845834000
I/DEBUG   (   34): d2 4b0010684b000000 d3 0000000045834000
I/DEBUG   (   34): d4 0000000000000000 d5 0000000000000000
I/DEBUG   (   34): d6 0000000000000000 d7 0000106800000000
I/DEBUG   (   34): d8 3f8000003f800000 d9 0000000000100000
I/DEBUG   (   34): d10 0000000000000000 d11 0000000000000000
I/DEBUG   (   34): d12 0000000000000000 d13 0000000000000000
I/DEBUG   (   34): d14 0000000000000000 d15 0000000000000000
I/DEBUG   (   34): scr 68000012
I/DEBUG   (   34):
I/DEBUG   (   34):          #00 pc 00050c8e /system/lib/libdvm.so (dvmAbort)
I/DEBUG   (   34):          #01 pc 0004486e /system/lib/libdvm.so
I/DEBUG   (   34):          #02 pc 000451b0 /system/lib/libdvm.so
I/DEBUG   (   34):          #03 pc 0004c9a0 /system/lib/libdvm.so
I/DEBUG   (   34):          #04 pc 000e0e4a /data/data/com.adobe.air/lib/libCo
re.so
I/DEBUG   (   34):
I/DEBUG   (   34): code around pc:
I/DEBUG   (   34): 4080bc6c 34b4f8d3 ec54f7cd 26001e73 2f01f813 ...4..T.s..&...
I/DEBUG   (   34): 4080bc7c 42abb152 d0074416 4798e7f8 f7ff4c0a R..B.D.....G.L.
I/DEBUG   (   34): 4080bc8c 7026ffa7 ec4af7cd 2006490c 44794a0c ..&p..J..I. .Jy
D
I/DEBUG   (   34): 4080bc9c f7cd447a 2000eb00 ebc2f7cd 58e54b05 zD..... .....K.
X
I/DEBUG   (   34): 4080bcac 2b006c6b e7e9d1e9 deadd00d 0006234c kl.+........L#.
I/DEBUG   (   34):
I/DEBUG   (   34): code around lr:
I/DEBUG   (   34): 4080bc6c 34b4f8d3 ec54f7cd 26001e73 2f01f813 ...4..T.s..&...
I/DEBUG   (   34): 4080bc7c 42abb152 d0074416 4798e7f8 f7ff4c0a R..B.D.....G.L.
I/DEBUG   (   34): 4080bc8c 7026ffa7 ec4af7cd 2006490c 44794a0c ..&p..J..I. .Jy
D
I/DEBUG   (   34): 4080bc9c f7cd447a 2000eb00 ebc2f7cd 58e54b05 zD..... .....K.
X
I/DEBUG   (   34): 4080bcac 2b006c6b e7e9d1e9 deadd00d 0006234c kl.+........L#.
I/DEBUG   (   34):
I/DEBUG   (   34): memory map around addr deadd00d:
I/DEBUG   (   34): bed23000-bed71000 [stack]
I/DEBUG   (   34): (no map for address)
I/DEBUG   (   34): (no map above)
I/DEBUG   (   34):
I/DEBUG   (   34): stack:
I/DEBUG   (   34):     bed6a208 00000000
I/DEBUG   (   34):     bed6a20c 4001df19 /system/lib/libc.so
I/DEBUG   (   34):     bed6a210 4004770c /system/lib/libc.so
I/DEBUG   (   34):     bed6a214 4004c85c
I/DEBUG   (   34):     bed6a218 00000000
I/DEBUG   (   34):     bed6a21c 4001f121 /system/lib/libc.so
I/DEBUG   (   34):     bed6a220 4004755c /system/lib/libc.so
I/DEBUG   (   34):     bed6a224 00000000
I/DEBUG   (   34):     bed6a228 0000020c
I/DEBUG   (   34):     bed6a22c 49622e39 /data/data/com.adobe.air/lib/libCore.
so
I/DEBUG   (   34):     bed6a230 4084ee67 /system/lib/libdvm.so
I/DEBUG   (   34):     bed6a234 4001df37 /system/lib/libc.so
I/DEBUG   (   34):     bed6a238 4086df90 /system/lib/libdvm.so
I/DEBUG   (   34):     bed6a23c bed6a44b [stack]
I/DEBUG   (   34):     bed6a240 df0027ad
I/DEBUG   (   34):     bed6a244 00000000
I/DEBUG   (   34): #00 bed6a248 00000038
I/DEBUG   (   34):     bed6a24c 6c756e28
I/DEBUG   (   34):     bed6a250 0000296c
I/DEBUG   (   34):     bed6a254 00000000
I/DEBUG   (   34):     bed6a258 00000000
I/DEBUG   (   34):     bed6a25c 00000000
I/DEBUG   (   34):     bed6a260 00000000
I/DEBUG   (   34):     bed6a264 00000000
I/DEBUG   (   34):     bed6a268 00000000
I/DEBUG   (   34):     bed6a26c 00000000
I/DEBUG   (   34):     bed6a270 00000000
I/DEBUG   (   34):     bed6a274 00000000
I/DEBUG   (   34):     bed6a278 00000000
I/DEBUG   (   34):     bed6a27c 00000000
I/DEBUG   (   34):     bed6a280 00000000
I/DEBUG   (   34):     bed6a284 00000000
I/DEBUG   (   34):     bed6a288 00000000
I/DEBUG   (   34):     bed6a28c 00000000
I/DEBUG   (   34):     bed6a290 00000000
I/DEBUG   (   34):     bed6a294 00000000
I/DEBUG   (   34):     bed6a298 00000000
I/DEBUG   (   34):     bed6a29c 00000000
I/DEBUG   (   34):     bed6a2a0 00000000
I/DEBUG   (   34):     bed6a2a4 00000000
I/DEBUG   (   34):     bed6a2a8 00000000
I/DEBUG   (   34):     bed6a2ac 00000000
I/DEBUG   (   34):     bed6a2b0 00000000
I/DEBUG   (   34):     bed6a2b4 00000000
I/DEBUG   (   34):     bed6a2b8 00000000
I/DEBUG   (   34):     bed6a2bc 00000000
I/DEBUG   (   34):     bed6a2c0 00000000
I/DEBUG   (   34):     bed6a2c4 00000000
I/DEBUG   (   34):     bed6a2c8 00000000
I/DEBUG   (   34):     bed6a2cc 00000000
I/DEBUG   (   34):     bed6a2d0 00000000
I/DEBUG   (   34):     bed6a2d4 00000000
I/DEBUG   (   34):     bed6a2d8 00000000
I/DEBUG   (   34):     bed6a2dc 00000000
I/DEBUG   (   34):     bed6a2e0 00000000
I/DEBUG   (   34):     bed6a2e4 00000000
I/DEBUG   (   34):     bed6a2e8 00000000
I/DEBUG   (   34):     bed6a2ec 00000000
I/DEBUG   (   34):     bed6a2f0 00000000
I/DEBUG   (   34):     bed6a2f4 00000000
I/DEBUG   (   34):     bed6a2f8 00000000
I/DEBUG   (   34):     bed6a2fc 00000000
I/DEBUG   (   34):     bed6a300 00000000
I/DEBUG   (   34):     bed6a304 00000000
I/DEBUG   (   34):     bed6a308 00000000
I/DEBUG   (   34):     bed6a30c 00000000
I/DEBUG   (   34):     bed6a310 00000000
I/DEBUG   (   34):     bed6a314 00000000
I/DEBUG   (   34):     bed6a318 00000000
I/DEBUG   (   34):     bed6a31c 00000000
I/DEBUG   (   34):     bed6a320 00000000
I/DEBUG   (   34):     bed6a324 00000000
I/DEBUG   (   34):     bed6a328 00000000
I/DEBUG   (   34):     bed6a32c 00000000
I/DEBUG   (   34):     bed6a330 00000000
I/DEBUG   (   34):     bed6a334 00000000
I/DEBUG   (   34):     bed6a338 00000000
I/DEBUG   (   34):     bed6a33c 00000000
I/DEBUG   (   34):     bed6a340 00000000
I/DEBUG   (   34):     bed6a344 00000000
I/DEBUG   (   34):     bed6a348 00000000
I/DEBUG   (   34):     bed6a34c 00000000
I/DEBUG   (   34):     bed6a350 00000000
I/DEBUG   (   34):     bed6a354 00000000
I/DEBUG   (   34):     bed6a358 00000000
I/DEBUG   (   34):     bed6a35c 00000000
I/DEBUG   (   34):     bed6a360 00000000
I/DEBUG   (   34):     bed6a364 00000000
I/DEBUG   (   34):     bed6a368 00000000
I/DEBUG   (   34):     bed6a36c 00000000
I/DEBUG   (   34):     bed6a370 00000000
I/DEBUG   (   34):     bed6a374 00000000
I/DEBUG   (   34):     bed6a378 00000000
I/DEBUG   (   34):     bed6a37c 00000000
I/DEBUG   (   34):     bed6a380 00000000
I/DEBUG   (   34):     bed6a384 00000000
I/DEBUG   (   34):     bed6a388 00000000
I/DEBUG   (   34):     bed6a38c 00000000
I/DEBUG   (   34):     bed6a390 00000000
I/DEBUG   (   34):     bed6a394 00000000
I/DEBUG   (   34):     bed6a398 00000000
I/DEBUG   (   34):     bed6a39c 00000000
I/DEBUG   (   34):     bed6a3a0 00000000
I/DEBUG   (   34):     bed6a3a4 00000000
I/DEBUG   (   34):     bed6a3a8 00000000
I/DEBUG   (   34):     bed6a3ac 00000000
I/DEBUG   (   34):     bed6a3b0 00000000
I/DEBUG   (   34):     bed6a3b4 00000000
I/DEBUG   (   34):     bed6a3b8 00000000
I/DEBUG   (   34):     bed6a3bc 00000000
I/DEBUG   (   34):     bed6a3c0 00000000
I/DEBUG   (   34):     bed6a3c4 00000000
I/DEBUG   (   34):     bed6a3c8 00000000
I/DEBUG   (   34):     bed6a3cc 00000000
I/DEBUG   (   34):     bed6a3d0 00000000
I/DEBUG   (   34):     bed6a3d4 00000000
I/DEBUG   (   34):     bed6a3d8 00000000
I/DEBUG   (   34):     bed6a3dc 00000000
I/DEBUG   (   34):     bed6a3e0 00000000
I/DEBUG   (   34):     bed6a3e4 00000000
I/DEBUG   (   34):     bed6a3e8 00000000
I/DEBUG   (   34):     bed6a3ec 00000000
I/DEBUG   (   34):     bed6a3f0 00000000
I/DEBUG   (   34):     bed6a3f4 00000000
I/DEBUG   (   34):     bed6a3f8 00000000
I/DEBUG   (   34):     bed6a3fc 00000000
I/DEBUG   (   34):     bed6a400 00000000
I/DEBUG   (   34):     bed6a404 00000000
I/DEBUG   (   34):     bed6a408 00000000
I/DEBUG   (   34):     bed6a40c 00000000
I/DEBUG   (   34):     bed6a410 00000000
I/DEBUG   (   34):     bed6a414 00000000
I/DEBUG   (   34):     bed6a418 00000000
I/DEBUG   (   34):     bed6a41c 00000000
I/DEBUG   (   34):     bed6a420 00000000
I/DEBUG   (   34):     bed6a424 00000000
I/DEBUG   (   34):     bed6a428 00000000
I/DEBUG   (   34):     bed6a42c 00000000
I/DEBUG   (   34):     bed6a430 00000000
I/DEBUG   (   34):     bed6a434 00000000
I/DEBUG   (   34):     bed6a438 00000000
I/DEBUG   (   34):     bed6a43c 00000000
I/DEBUG   (   34):     bed6a440 00000000
I/DEBUG   (   34):     bed6a444 00000000
I/DEBUG   (   34):     bed6a448 00000000
I/DEBUG   (   34):     bed6a44c 342b19f5
I/DEBUG   (   34):     bed6a450 00000000
I/DEBUG   (   34):     bed6a454 4086df90 /system/lib/libdvm.so
I/DEBUG   (   34):     bed6a458 5d500031
I/DEBUG   (   34):     bed6a45c 407ff873 /system/lib/libdvm.so
I/DEBUG   (   34): #01 bed6a460 bed6a54c [stack]
I/DEBUG   (   34):     bed6a464 408001b5 /system/lib/libdvm.so
D/Zygote (   37): Process 497 terminated by signal (11)
I/WindowManager(   84): WIN DEATH: Window{41462cb0 SurfaceView paused=false}
I/ActivityManager(   84): Process air.com.deloitte.helloWorld (pid 497) has died
W/ActivityManager(   84): Force removing ActivityRecord{41534258 air.com.deloitt
e.helloWorld/.AppEntry}: app died, no saved state
W/NetworkManagementSocketTagger(   84): setKernelCountSet(10041, 0) failed with
errno -2
I/WindowManager(   84): WIN DEATH: Window{41590db8 SurfaceView paused=false}
I/WindowManager(   84): WIN DEATH: Window{4158b920 air.com.deloitte.helloWorld/a
ir.com.deloitte.helloWorld.AppEntry paused=false}
I/BootReceiver(   84): Copying /data/tombstones/tombstone_06 to DropBox (SYSTEM_
TOMBSTONE)
E/InputDispatcher(   84): Received spurious receive callback for unknown input c
hannel. fd=209, events=0x8
D/dalvikvm(   84): GC_FOR_ALLOC freed 928K, 13% free 11284K/12871K, paused 84ms
W/NetworkManagementSocketTagger(   84): setKernelCountSet(10009, 1) failed with
errno -2
D/dalvikvm(   84): GC_CONCURRENT freed 141K, 10% free 11601K/12871K, paused 6ms+
14ms
D/dalvikvm(   84): GC_FOR_ALLOC freed 177K, 11% free 11552K/12871K, paused 128ms
D/dalvikvm(   84): GC_FOR_ALLOC freed 128K, 10% free 11616K/12871K, paused 84ms
D/dalvikvm(   84): GC_FOR_ALLOC freed 427K, 12% free 11445K/12871K, paused 79ms
W/InputManagerService(   84): Got RemoteException sending setActive(false) notif
ication to pid 497 uid 10041
D/dalvikvm( 136): GC_FOR_ALLOC freed 5544K, 37% free 9812K/15495K, paused 47ms
D/dalvikvm( 179): GC_FOR_ALLOC freed 2416K, 21% free 17911K/22535K, paused 77ms
D/dalvikvm( 179): GC_FOR_ALLOC freed 659K, 17% free 18828K/22535K, paused 100ms
D/dalvikvm( 179): GC_CONCURRENT freed 941K, 12% free 19900K/22535K, paused 6ms+
20ms
D/dalvikvm( 179): GC_CONCURRENT freed 3259K, 18% free 18684K/22535K, paused 12m
s+23ms

I am not able to solve this yet. Is anybody else facing this this problem.

Win7 Application Crash on Print Job since Air Update to 3.0.0.4080

Hi,
first of all sorry for my bad English but I need your HELP.
A lot of my Customers have a Problem with my Application since Adobe automatically updated Air to Version 3.0.0.4080.
When starting a PrintJob on a Windows 7 Machine the Application Crashes. With Air 2.7.2 everything is fine. My only solution is to Downgrade Air to 2.7.2.
Has someone an idea how I can solve this?
Here is the crash Report on an Win 7 64Bit Machine with Service Pack 1 in German:
Protokollname: Application
Quelle:        Application Error
Datum:         14.10.2011 12:20:56
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      Gio-PC-onIMac
Beschreibung:
Name der fehlerhaften Anwendung: extato commerce.exe, Version: 0.0.0.0, Zeitstempel: 0x4e7d51b6
Name des fehlerhaften Moduls: Adobe AIR.dll, Version: 3.0.0.4080, Zeitstempel: 0x4e7d5799
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0012dabe
ID des fehlerhaften Prozesses: 0x494
Startzeit der fehlerhaften Anwendung: 0x01cc8a5abdd4e4bc
Pfad der fehlerhaften Anwendung: c:\program files (x86)\extato commerce\extato commerce.exe
Pfad des fehlerhaften Moduls: c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll
Berichtskennung: 33870ff8-f64e-11e0-8e55-001c429351d4
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-10-14T10:20:56.000000000Z" />
    <EventRecordID>8182</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Gio-PC-onIMac</Computer>
    <Security />
</System>
<EventData>
    <Data>extato commerce.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>4e7d51b6</Data>
    <Data>Adobe AIR.dll</Data>
    <Data>3.0.0.4080</Data>
    <Data>4e7d5799</Data>
    <Data>c0000005</Data>
    <Data>0012dabe</Data>
    <Data>494</Data>
    <Data>01cc8a5abdd4e4bc</Data>
    <Data>c:\program files (x86)\extato commerce\extato commerce.exe</Data>
    <Data>c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR.dll</Data>
    <Data>33870ff8-f64e-11e0-8e55-001c429351d4</Data>
</EventData>
</Event>

Hi,
Could you please open a new bug report about this issue at bugbase.adobe.com? Please include sample media, code, project or app to help us reproduce the issue. Finally, once the bug has been added, would you mind posting back with the URL so that others affected can add their votes and comments?
Thanks,
Jian
Adobe Flash Runtime team

Santa Rosa MBP Application Crashes with EXC_BAD_ACCESS (0x0001)

I am having Application crashing problems with my brand new Santa Rosa MBP that arrived today. This machine is a 2.4 GHz 17" MBP with Hi-Res Glossy display and it came with 2 GB of RAM. I upgraded it to 4 GB but this problem occurs with the original chips or the new 2 x 2 GB chips.
So far the applications that crash are Pages, Keynote, Aperture, Parallels Desktop, and iWeb. Other things I have tried are all right for now. Excerpts from the CrashReporter log of Aperture are below. All applications are crashing with an identical EXCBADACCESS (0x0001) and KERNPROTECTIONFAILURE (0x0002) at ... (this number differs for individual applications). Any ideas?
Bryan
Host Name: brycv
Date/Time: 2007-07-05 20:49:02.460 -0700
OS Version: 10.4.10 (Build 8R2232)
Report Version: 4
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Parent: WindowServer [82]
Version: 1.5.3 (1.5.3)
PID: 1196
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 <<00000000>> 0x00000000 0 + 0
1 com.apple.Aperture 0x00003149 0x1000 + 8521
2 com.apple.Aperture 0x0000323e 0x1000 + 8766
3 com.apple.Aperture 0x0000336e 0x1000 + 9070
4 com.apple.Aperture 0x0000294e 0x1000 + 6478
5 com.apple.Aperture 0x00002875 0x1000 + 6261
Thread 1:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 com.apple.ColorSync 0x915a86cf pthreadSemaphoreWait(t_pthreadSemaphore*) + 35
2 com.apple.ColorSync 0x915c2de0 CMMConvTask(void*) + 60
3 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 2:
0 libSystem.B.dylib 0x900248c7 semaphorewait_signaltrap + 7
1 libGLProgrammability.dylib 0x9418afdb glvmDoWork + 150
2 libSystem.B.dylib 0x90024227 pthreadbody + 84
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x010f7020 ebx: 0x92b217da ecx: 0x01872000 edx: 0x00000011
edi: 0xbffffbd8 esi: 0x01872000 ebp: 0xbffffc08 esp: 0xbffffbdc
ss: 0x0000001f efl: 0x00010246 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)
MacBook Pro 17" 2.4 GHz Mac OS X (10.4.10)

I am also having this problem with Adobe Bridge CS3, and QuickTime but only if I try to open a video file. It seems to be a problem when I access anything that wants to deal with the video hardware in the machine. I am planning on calling Apple tomorrow but any help would be appreciated.

Application crash with message "Hidden Wnd that Fires connection points"

Our Swing application regularly crashes with a Windows error message popup.
Title: "Hidden Wnd that Fires connection points: javaw.exe - Application Error"
Message: The instruction at "0x7c912905" referenced memory at "0xfffffff8". The memory could not be "read". Click on OK to terminate the program. Click on CANCEL to debug the program."
Our logfile contains SystemOut, SystemErr and log4j entries and shows nothing. Also no hs_err_pid is written to the file system. Google did not find anything when searching for the message box title.
Environment:
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode)
Microsoft Windows XP [Version 5.1.2600]
Does anyone have an idea what could cause such a problem?

How do I check if NIO is running non-blocking mode ? I am reusing a tcp/ip basic class (provided with my embedded interface chip) which does not mention it being either way.
I only tried in browser. I have to add code to handle the applet viewer case. it crashes in every browser I tried and has no console dump in any. I put it together quickly for a customer and did not add debugging messages in the code since it was provided and working...
Gotta go do that now.
Thanks

Adobe AIR applications compatible with Android?

As I understand that Adobe Flash is supported on Android 2.1 and 2.2 versions.
But I could not find if Adobe Air applications are also supported. Please let me know what versions are supported since in the system requirements for Adobe AIR only Windows, Mac and Linux were mentioned with no reference to Android as such.
I am new to both Android and Adobe Air so please excuse any misrepresentation in the query.
Thanks!

AIR is compatible with Android 2.2 on ARMv7 devices.

Application crashing with error *** libthread failure: _thread_setschedpar

On Solaris9 my application is crashing with this error message.
*** libthread failure: threadsetschedparam_main() fails
Application is running fine on Solaris10.
Program Stack trace at this crash is
=>[1] __lwp_kill(0x0, 0x6, 0x0, 0xfffffffffffffff8, 0x0, 0xffffffff7fffe1f9), at 0xffffffff7a9a8ebc
[2] Abort(0xffffffff7fffe2a0, 0x0, 0x3a, 0x7efefeff, 0x81010100, 0xff00), at 0xffffffff7ac094a0
[3] panic(0xffffffff7ac18768, 0xffffffff77d00000, 0x0, 0x1, 0x0, 0xffffffff7fffe519), at 0xffffffff7ac0959c
[4] ceilprio_inherit(0xff, 0x0, 0x0, 0x10533c, 0xffffffff7ac13b04, 0x0), at 0xffffffff7ac126a8
[5] mutex_lock_internal(0x0, 0x0, 0xffffffff77d00000, 0x17a50, 0xffffffff77c40400, 0x0), at 0xffffffff7ac13c5c
[6] std::basic_streambuf<char,std::char_traits<char> >::getloc(0x1005d6590, 0xffffffff7b2ceaa0, 0x1005d6580, 0x1fbf44, 0xffffffff77c40700, 0xffffffff7fffebac), at 0xffffffff7b11d49c
[7] std::basic_filebuf<char,std::char_traits<char> >::overflow(0xffffffff7b2ceaa0, 0xffffffffffffffff, 0xffffffff7b2c0608, 0x400, 0xffffffff7b2ceaa0, 0x2), at 0xffffffff7b0c47d8
[8] std::basic_filebuf<char,std::char_traits<char> >::sync(0xffffffff7b2ceaa0, 0x0, 0xffffffff77d00000, 0x1041fc, 0xffffffff7b0c46b0, 0x8), at 0xffffffff7b0c62d0
[9] std::basic_ostream<char,std::char_traits<char> >::flush(0xffffffff7b2cc920, 0xffffffff7b2cc930, 0xd338, 0xffffffff7b0c62a0, 0xffffffff7b2c0608, 0xffffffff7b2c8528), at 0xffffffff7b080e9c
[10] std::ios_base::Init::~Init(0x1, 0xffffffff7b2ced30, 0xffffffff7b2c0608, 0x790, 0x1a6914, 0x400), at 0xffffffff7b119d40
[11] __SUNW_fini_iostreams(0xff000000, 0xff000000, 0xffffffff77c00000, 0x2a640, 0xffffffff77c40180, 0x10c800), at 0xffffffff7b11a7dc
[12] __Cimpl::cplus_fini(0xffffffff7af0dc60, 0x0, 0x1, 0x104344, 0xffffffff7df47e38, 0xffffffff7b2cd288), at 0xffffffff7ae086ac
[13] __cplus_fini_at_exit(0x0, 0x0, 0xffffffff77d00000, 0x50, 0x24ff98, 0x0), at 0xffffffff7b133f30
[14] _exithandle(0x28000, 0x1004bbd38, 0x24fb10, 0x1001188e4, 0xffffffff7ffff028, 0xffffffff7aab6f78), at 0xffffffff7a926e5c
[15] exit(0x3, 0xffffffff7ffff1f8, 0xffffffff7ffff210, 0x0, 0x0, 0x100000000), at 0xffffffff7a9a9518
Can somebody tell me why this issue is occurring on Solaris9.
What could be the possible fix.
Thanks in advance.
Chaitanya Srikar

On Solaris9 my application is crashing with this error message.
*** libthread failure: threadsetschedparam_main() fails
Application is running fine on Solaris10.
Program Stack trace at this crash is
=>[1] __lwp_kill(0x0, 0x6, 0x0, 0xfffffffffffffff8, 0x0, 0xffffffff7fffe1f9), at 0xffffffff7a9a8ebc
[2] Abort(0xffffffff7fffe2a0, 0x0, 0x3a, 0x7efefeff, 0x81010100, 0xff00), at 0xffffffff7ac094a0
[3] panic(0xffffffff7ac18768, 0xffffffff77d00000, 0x0, 0x1, 0x0, 0xffffffff7fffe519), at 0xffffffff7ac0959c
[4] ceilprio_inherit(0xff, 0x0, 0x0, 0x10533c, 0xffffffff7ac13b04, 0x0), at 0xffffffff7ac126a8
[5] mutex_lock_internal(0x0, 0x0, 0xffffffff77d00000, 0x17a50, 0xffffffff77c40400, 0x0), at 0xffffffff7ac13c5c
[6] std::basic_streambuf<char,std::char_traits<char> >::getloc(0x1005d6590, 0xffffffff7b2ceaa0, 0x1005d6580, 0x1fbf44, 0xffffffff77c40700, 0xffffffff7fffebac), at 0xffffffff7b11d49c
[7] std::basic_filebuf<char,std::char_traits<char> >::overflow(0xffffffff7b2ceaa0, 0xffffffffffffffff, 0xffffffff7b2c0608, 0x400, 0xffffffff7b2ceaa0, 0x2), at 0xffffffff7b0c47d8
[8] std::basic_filebuf<char,std::char_traits<char> >::sync(0xffffffff7b2ceaa0, 0x0, 0xffffffff77d00000, 0x1041fc, 0xffffffff7b0c46b0, 0x8), at 0xffffffff7b0c62d0
[9] std::basic_ostream<char,std::char_traits<char> >::flush(0xffffffff7b2cc920, 0xffffffff7b2cc930, 0xd338, 0xffffffff7b0c62a0, 0xffffffff7b2c0608, 0xffffffff7b2c8528), at 0xffffffff7b080e9c
[10] std::ios_base::Init::~Init(0x1, 0xffffffff7b2ced30, 0xffffffff7b2c0608, 0x790, 0x1a6914, 0x400), at 0xffffffff7b119d40
[11] __SUNW_fini_iostreams(0xff000000, 0xff000000, 0xffffffff77c00000, 0x2a640, 0xffffffff77c40180, 0x10c800), at 0xffffffff7b11a7dc
[12] __Cimpl::cplus_fini(0xffffffff7af0dc60, 0x0, 0x1, 0x104344, 0xffffffff7df47e38, 0xffffffff7b2cd288), at 0xffffffff7ae086ac
[13] __cplus_fini_at_exit(0x0, 0x0, 0xffffffff77d00000, 0x50, 0x24ff98, 0x0), at 0xffffffff7b133f30
[14] _exithandle(0x28000, 0x1004bbd38, 0x24fb10, 0x1001188e4, 0xffffffff7ffff028, 0xffffffff7aab6f78), at 0xffffffff7a926e5c
[15] exit(0x3, 0xffffffff7ffff1f8, 0xffffffff7ffff210, 0x0, 0x0, 0x100000000), at 0xffffffff7a9a9518
Can somebody tell me why this issue is occurring on Solaris9.
What could be the possible fix.
Thanks in advance.
Chaitanya Srikar

Smartwatch 2 call handling crash with Android 4.4.4

Upgraded my phone (Xperia Z Ultra - 6806) to Android 4.4.4 and now the Call Handling app crashes the connection between the watch and phone whenever I try to select a contact on the watch.

Hi everyone,
I have the same issue on my xperia z ultra. the latest kitkat 4.4.4 brought this huge problem.
I contacted the Support Team and here's their response:
Greetings from Sony Xperia support.
We value the importance of your concern.
In response to your query, we would request you to perform a software repair using PC Companion (for Windows computers) in order to resolve the issue which you are facing with your handset.
Steps to perform software repair using your Windows computers and the PC Companion application:
1. Download PC Companion from http://www.sonymobile.com/in/tools/pc-companion/ , and install it on your Windows computer.
2. Turn off the phone and disconnect it from the computer.
3. Open the PC Companion application.
4. Select Start under Support Zone.
5. Select device Software Update and Start.
6. Could not find phone appears. Select Repair phone and Connect.
7. You will receive a message on PC companion that data will be lost if you will continue.
8. Tick the box to confirm that you have understood that all personal data will be lost. Then click Next. The application prepares for the update and if necessary downloads required data from the web.
9. Select your phone model manually and then click Next.
10. Depending on the model selected, you are asked to perform a few steps for the update for PC Companion to be able to update the phone software.
11. Do not connect the phone yet! Note! At this point the phone must be off and disconnected from the computer.
12. Connect the USB cable to the computer, not to the phone.
13. Xperia: While pressing and holding down the indicated button (Volume down key), connect the USB cable to the Xperia device, and keep holding and pressing down the indicated button (Volume down key) until. The update of your device has started... appears (in some cases Installing drivers appears first).
14. If you failed to follow the steps correctly the phone will turn on, and Proceed with the following steps, slide down the notification bar appear.
15. If this happens, disconnect the phone from the cable, turn it off and repeat from step 12.
16. Follow the instructions on the screen. When the repair is finished, disconnect the device and then start the device again.
17. Select Next. If the repair was successful, the message will appear that device has been successfully updated appears.
18. Select Finish.
Note: You should always back up all data before performing a software repair.
We would request you to follow the below mentioned steps in order to take backup of your phone data using PC Companion:
1. Go to Support at www.sonymobile.com to install PC Companion on a Windows computer.
2. When installed, start PC Companion on the computer.
3. Connect your phone to the computer using a USB cable.
4. Click Start under Backup & Restore.
5. Follow the on-screen instructions.
NOTE: Please take the backup of the data before going ahead with the troubleshooting steps. Sony Mobile Communications-India holds no responsibility for any data loss.
If you need any assistance or clarifications, please feel free to contact Sony Xperia Support at the Toll Free number 1800-3000-2800 (Working Timings-9:00am to 9:00pm: Mon-Sun) alternately, you can email us at [email protected]
For the latest news, information and product support please visit www.sonymobile.com/in
Thank you for contacting Sony Xperia Support.
Always looking to serve you better.
Kind Regards,
Juhi Arora
Sony Xperia Customer Services"
I am not sure that hard reset and upgrade via PC Companion will help. But I'll see what I can see.
Laters

Application crash with support.cpp line 1806

Hi,
I'm pretty desperately trying to find the cause for a crash upon starting my application.
The error message I get is: Fatal internal error: "support.cpp" line 1806.
The message comes even before the Front-Panel of the main VI opens.
The corresponding application log shows this information: .\manager\support.cpp(1806) : DAbort: Unknown Conversion
I'm using LabView 8.2.1f4 on Windows XP Pro.
However the error does not occour every time I start my program, rather it happens every once in a while, so it's really hard to find the reason why..
The application also crashes on other PCs, so I think that there is no problem with my OS.
Does anybody have any hints about what to do in such a situation?
thx,
Leo
Attachments:
TAS_VIEW2000_8.2.1f4_lbosnjak_cur.txt ‏1 KB

Ok, thx for the info.
I was wondering whether there is more info about the cause of the error (not only support.cpp and line number) but it's ok.
My application is way too large to simply debug it (>1300 VIs, and .EXE size of ~30MB) :-(
But everything is relative to the degree of annoyance the problem causes to the customers ;-)
However, I'll send an update, if It happens that I find a simple way to reproduce it or if we decide to update to LV2009.
thx,
Leo

Office 2013 applications crash with Document Information Panel open

I am using Office Professional Plus 2013 to work with documents that reside in SharePoint 2010 document libraries.
The content type(s) in that SharePoint site collection are set to automatically show the Document Information Panel when opened in Office applications. By opening any of these documents in their desktop app (via browser or Skydrive Pro), I am able
to check-out and edit content; but the check-in step always crashes the application, giving a pop-up error: "An unknown errors has caused <office program> to stop working."
By choosing to NOT automatically show the Doc Info Panel for these SharePoint documents, Office 2013 programs can handle everything just fine (editing, versioning, etc.).
If I don't auto-show the Doc Info Panel, but then manually open the panel once I get inside the program, this crashes the program in the same way as before.
If I save a local copy of a document and show the Doc Info Panel in any way (auto or manual), Office 2013 crashes.
I couldn't find any postings on this error and I don't see this incompatibility listed in the
Office 2013 known issues article and was wondering if anyone has had a similar experience?

I am having the exact same issue. I have created a Custom Site Column which is defined as a CHOICE. I do not want to put in a Default so left it blanl but field must be populated. I then put this into a Document Library Content Type.
With documents that are already been uploaded and in the Library when I pull up in Office Web Apps, I can make changes to the document but when I try to save it crashes.   Also, when I pull up document and say edit in Office Web Apps there is no
way to change information in the Document Information Panel since this does not appear.   (I forgot to mention that I required DIF to display in Content Type also).
This only happens on blank column fields when trying to save. If I do a Quick EDIT of the list and change my blank Choice columns to something(I created as radio buttons) and then go through the process it works OK and will save. Not sure
if this pertains to your issue but, I just prepopulate all columns with what the should be, when a brand new document from word, excel etc is created it is created from the Desktop version of Word Excel and when IT saves to SharePoint, I get
a message to choose information to put into properties before it actually saves.
Hope this helps a little.

Aperture v. 3.1.1 glitching and crashing with iOS 10.7.5 update?

It is crashing every time I use a brush tool or do anything too quickly in general. I just updated my mac yesterday and that is when this started. I have tried restarting my computer, checking for updates, etc.

Did you also update Aperture? Aperture 3.1.1 had a bug, that might cause crashes, when applying adjustments using MacOS X lion.
You should at least upgrade to
Aperture 3.2.4
for Aperture to run reliably with Lion, if you cannot (or don't want to) upgrade to the most recent Aperture version 3.4.2.
But before upgrading Aperture, be sure to keep a backup of your current Aperture library and to repair/rebuild the Aperture library using the Aperture Library First Aid Tools (Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library). The Aperture upgrade will upgrade your Aperture library as well, so you will not be able to open it any longer with the older Aperture version. And the upgrade may fail, if the library has problems, like inconsistencies that can be caused by crashes.
Regards
Léonie

Application crashes with Android 2.3.3 update

Similar Messages

Maybe you are looking for