有时，我的应用程序被卡住，然后崩溃。
我阅读了系统日志，并在系统日志的最后几行中看到我的 Activity 出现一些“WIN DEATH”错误。
谁能告诉我原因并告诉我解决方法？
非常感谢!
这是系统日志:
08-17 08:34:00.091 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.101 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.101 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.111 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.121 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.131 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.131 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.141 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.151 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.151 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.161 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.171 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.171 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.181 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.191 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.191 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:00.211 E/WifiService( 149): ***WAPI : readNetworkVariables testing for WAPI
08-17 08:34:01.692 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.dell.launcher/.Launcher }
08-17 08:34:01.711 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:34:01.731 W/InputManagerService( 149): Ignoring hideSoftInput of: com.android.internal.view.IInputMethodClient$Stub$Proxy@46f51200
08-17 08:34:01.751 I/ActivityManager( 149): No longer want com.android.vending (pid 724): hidden #16
08-17 08:34:03.141 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.browser/.BrowserActivity bnds=[289,313][375,390] }
08-17 08:34:03.521 W/InputManagerService( 149): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@46ee34f8 (uid=10006 pid=893)
08-17 08:34:03.521 W/InputManagerService( 149): Client not active, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@46f02ef0
08-17 08:34:08.301 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW dat=http://vnexpress.net/ flg=0x10000000 cmp=com.android.browser/.BrowserActivity (has extras) }
08-17 08:34:43.361 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=http://vnexpress.net/gl/the-gioi/phan-tich/2012/08/trung-quoc-se-bi-co-lap-neu-bat-hop-tac-ve-bien-dong-1/ cmp=com.android.browser/.BrowserActivity }
08-17 08:34:43.911 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.VIEW cat=[android.intent.category.BROWSABLE] dat=http://vnexpress.net/gl/the-gioi/phan-tich/2012/08/trung-quoc-se-bi-co-lap-neu-bat-hop-tac-ve-bien-dong-1/ cmp=com.android.browser/.BrowserActivity }
08-17 08:35:06.701 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.dell.launcher/.Launcher }
08-17 08:35:06.711 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:35:06.751 W/InputManagerService( 149): Ignoring hideSoftInput of: com.android.internal.view.IInputMethodClient$Stub$Proxy@47017a48
08-17 08:35:10.341 I/ActivityManager( 149): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen }
08-17 08:35:10.361 D/StatusBar( 149): nAnimY < mStatusBarView.getHeight()
08-17 08:35:16.144 W/WindowManager( 149): Key dispatching timed out sending to i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:16.144 W/WindowManager( 149): Previous dispatch state: null
08-17 08:35:16.144 W/WindowManager( 149): Current dispatch state: {{null to Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} @ 1345167316145 lw=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} lb=android.os.BinderProxy@46e87e58 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false}}}
08-17 08:35:16.421 E/ActivityManager( 149): ANR in i3.mobile1i3.mobile1(pid: 941) (i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen)
08-17 08:35:16.421 E/ActivityManager( 149): Reason: keyDispatchingTimedOut
08-17 08:35:16.421 E/ActivityManager( 149): Load: 5.13 / 5.05 / 3.69
08-17 08:35:16.421 E/ActivityManager( 149): CPU usage from 5531ms to 13ms ago:
08-17 08:35:16.421 E/ActivityManager( 149): system_server: 2% = 1% user + 1% kernel / faults: 35 minor 19 major
08-17 08:35:16.421 E/ActivityManager( 149): android.browser: 1% = 0% user + 0% kernel / faults: 21 minor 2 major
08-17 08:35:16.421 E/ActivityManager( 149): m.android.phone: 0% = 0% user + 0% kernel / faults: 48 minor 2 major
08-17 08:35:16.421 E/ActivityManager( 149): e.process.gapps: 0% = 0% user + 0% kernel / faults: 21 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): m.dell.launcher: 0% = 0% user + 0% kernel / faults: 20 minor
08-17 08:35:16.421 E/ActivityManager( 149): events/0: 0% = 0% user + 0% kernel
08-17 08:35:16.421 E/ActivityManager( 149): auo_touchscreen: 0% = 0% user + 0% kernel
08-17 08:35:16.421 E/ActivityManager( 149): d.process.acore: 0% = 0% user + 0% kernel / faults: 23 minor
08-17 08:35:16.421 E/ActivityManager( 149): m.android.music: 0% = 0% user + 0% kernel / faults: 219 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): com.oem.lota: 0% = 0% user + 0% kernel / faults: 53 minor 1 major
08-17 08:35:16.421 E/ActivityManager( 149): ndroid.dellsync: 0% = 0% user + 0% kernel / faults: 43 minor
08-17 08:35:16.421 E/ActivityManager( 149): cpanda.aquapets: 0% = 0% user + 0% kernel / faults: 61 minor
08-17 08:35:16.421 E/ActivityManager( 149): ndroid.settings: 0% = 0% user + 0% kernel / faults: 14 minor
08-17 08:35:16.421 E/ActivityManager( 149): lite.dellstreak: 0% = 0% user + 0% kernel / faults: 25 minor
08-17 08:35:16.421 E/ActivityManager( 149): d.photos:Remote: 0% = 0% user + 0% kernel / faults: 17 minor
08-17 08:35:16.421 E/ActivityManager( 149): equicksearchbox: 0% = 0% user + 0% kernel / faults: 22 minor
08-17 08:35:16.421 E/ActivityManager( 149): TOTAL: 7% = 3% user + 3% kernel + 0% iowait
08-17 08:35:16.551 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:16.591 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:16.881 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:20.351 W/ActivityManager( 149): Launch timeout has expired, giving up wake lock!
08-17 08:35:20.361 W/ActivityManager( 149): Activity idle timeout for HistoryRecord{46e20d08 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen}
08-17 08:35:48.398 W/WindowManager( 149): Key dispatching timed out sending to i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:48.398 W/WindowManager( 149): Previous dispatch state: null
08-17 08:35:48.398 W/WindowManager( 149): Current dispatch state: {{null to Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} @ 1345167348400 lw=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false} lb=android.os.BinderProxy@46e87e58 fin=false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=false}}}
08-17 08:35:48.841 E/ActivityManager( 149): ANR in i3.mobile1i3.mobile1(pid: 941) (i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen)
08-17 08:35:48.841 E/ActivityManager( 149): Reason: keyDispatchingTimedOut
08-17 08:35:48.841 E/ActivityManager( 149): Load: 5.28 / 5.11 / 3.76
08-17 08:35:48.841 E/ActivityManager( 149): CPU usage from 32415ms to 58ms ago:
08-17 08:35:48.841 E/ActivityManager( 149): system_server: 6% = 4% user + 1% kernel / faults: 840 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): android.browser: 1% = 1% user + 0% kernel / faults: 109 minor
08-17 08:35:48.841 E/ActivityManager( 149): .oem.logservice: 1% = 1% user + 0% kernel / faults: 1378 minor
08-17 08:35:48.841 E/ActivityManager( 149): m.dell.launcher: 0% = 0% user + 0% kernel / faults: 74 minor
08-17 08:35:48.841 E/ActivityManager( 149): ndroid.settings: 0% = 0% user + 0% kernel / faults: 72 minor
08-17 08:35:48.841 E/ActivityManager( 149): mmcqd: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): sensors_daemon: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): e.process.gapps: 0% = 0% user + 0% kernel / faults: 34 minor
08-17 08:35:48.841 E/ActivityManager( 149): mmcqd: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): cpanda.aquapets: 0% = 0% user + 0% kernel / faults: 7 minor
08-17 08:35:48.841 E/ActivityManager( 149): kswapd0: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): d.process.acore: 0% = 0% user + 0% kernel / faults: 42 minor
08-17 08:35:48.841 E/ActivityManager( 149): events/0: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): kjournald: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): ksdioirqd/mmc1: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): oid.inputmethod: 0% = 0% user + 0% kernel / faults: 25 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): m.android.phone: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): equicksearchbox: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): auo_touchscreen: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): wpa_supplicant: 0% = 0% user + 0% kernel
08-17 08:35:48.841 E/ActivityManager( 149): viders.calendar: 0% = 0% user + 0% kernel / faults: 35 minor
08-17 08:35:48.841 E/ActivityManager( 149): d.process.media: 0% = 0% user + 0% kernel / faults: 18 minor
08-17 08:35:48.841 E/ActivityManager( 149): m.android.music: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): ndroid.dellsync: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): .packagechecker: 0% = 0% user + 0% kernel / faults: 20 minor
08-17 08:35:48.841 E/ActivityManager( 149): com.netgate: 0% = 0% user + 0% kernel / faults: 273 minor
08-17 08:35:48.841 E/ActivityManager( 149): .cooliris.media: 0% = 0% user + 0% kernel / faults: 25 minor
08-17 08:35:48.841 E/ActivityManager( 149): lite.dellstreak: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): ogle.android.gm: 0% = 0% user + 0% kernel / faults: 30 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): d.apps.uploader: 0% = 0% user + 0% kernel / faults: 17 minor
08-17 08:35:48.841 E/ActivityManager( 149): d.photos:Remote: 0% = 0% user + 0% kernel / faults: 1 minor
08-17 08:35:48.841 E/ActivityManager( 149): o.android.oemec: 0% = 0% user + 0% kernel / faults: 15 minor
08-17 08:35:48.841 E/ActivityManager( 149): i3.mobile1: 0% = 0% user + 0% kernel / faults: 16 minor 1 major
08-17 08:35:48.841 E/ActivityManager( 149): TOTAL: 32% = 11% user + 8% kernel + 12% iowait + 0% irq + 0% softirq
08-17 08:35:48.871 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:48.901 W/WindowManager( 149): No window to dispatch pointer action 0
08-17 08:35:49.392 W/WindowManager( 149): No window to dispatch pointer action 1
08-17 08:35:51.681 W/ActivityManager( 149): Force finishing activity i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen
08-17 08:35:51.681 I/ActivityManager( 149): Killing i3.mobile1 (pid=941): user's request
08-17 08:35:51.701 I/WindowManager( 149): WIN DEATH: Window{46e6fdb0 i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen paused=false}
08-17 08:35:51.711 I/ActivityManager( 149): Process i3.mobile1 (pid 941) has died.
08-17 08:35:51.721 I/WindowManager( 149): WIN DEATH: Window{47004958 i3.mobile1/i3.mobile.dvrremote.screen.ConnectScreen paused=true}
08-17 08:35:51.721 I/ActivityManager( 149): Start proc i3.mobile1 for activity i3.mobile1/i3.mobile.dvrremote.screen.WelcomeScreen: pid=1119 uid=10106 gids={1015, 3003}
谢谢!
最佳答案
您的应用可能由于 ANR(应用程序无响应)而被终止。当您在 UI 线程中进行一些硬处理时，可能会发生这种情况。您可以在此处阅读更多信息:http://developer.android.com/guide/practices/responsiveness.html
只有一种解决方案:将所有繁重的工作转移到后台线程中，以便 UI 线程保持响应。
关于android - Android 中的 WIN DEATH 错误？，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/13009499/
总的来说，我对ruby还比较陌生，我正在为我正在创建的对象编写一些rspec测试用例。许多测试用例都非常基础，我只是想确保正确填充和返回值。我想知道是否有办法使用循环结构来执行此操作。不必为我要测试的每个方法都设置一个assertEquals。例如:describeitem,"TestingtheItem"doit"willhaveanullvaluetostart"doitem=Item.new#HereIcoulddotheitem.name.shouldbe_nil#thenIcoulddoitem.category.shouldbe_nilendend但我想要一些方法来使用
我试图在一个项目中使用rake，如果我把所有东西都放到Rakefile中，它会很大并且很难读取/找到东西，所以我试着将每个命名空间放在lib/rake中它自己的文件中，我添加了这个到我的rake文件的顶部:Dir['#{File.dirname(__FILE__)}/lib/rake/*.rake'].map{|f|requiref}它加载文件没问题，但没有任务。我现在只有一个.rake文件作为测试，名为“servers.rake”，它看起来像这样:namespace:serverdotask:testdoputs"test"endend所以当我运行rakeserver:testid时
作为我的Rails应用程序的一部分，我编写了一个小导入程序，它从我们的LDAP系统中吸取数据并将其塞入一个用户表中。不幸的是，与LDAP相关的代码在遍历我们的32K用户时泄漏了大量内存，我一直无法弄清楚如何解决这个问题。这个问题似乎在某种程度上与LDAP库有关，因为当我删除对LDAP内容的调用时，内存使用情况会很好地稳定下来。此外，不断增加的对象是Net::BER::BerIdentifiedString和Net::BER::BerIdentifiedArray，它们都是LDAP库的一部分。当我运行导入时，内存使用量最终达到超过1GB的峰值。如果问题存在，我需要找到一些方法来更正我的代
Rails2.3可以选择随时使用RouteSet#add_configuration_file添加更多路由。是否可以在Rails3项目中做同样的事情？ 最佳答案 在config/application.rb中:config.paths.config.routes在Rails3.2(也可能是Rails3.1)中，使用:config.paths["config/routes"] 关于ruby-on-rails-Rails3中的多个路由文件，我们在StackOverflow上找到一个类似的问题
大约一年前，我决定确保每个包含非唯一文本的Flash通知都将从模块中的方法中获取文本。我这样做的最初原因是为了避免一遍又一遍地输入相同的字符串。如果我想更改措辞，我可以在一个地方轻松完成，而且一遍又一遍地重复同一件事而出现拼写错误的可能性也会降低。我最终得到的是这样的:moduleMessagesdefformat_error_messages(errors)errors.map{|attribute,message|"Error:#{attribute.to_s.titleize}#{message}."}enddeferror_message_could_not_find(obje
我需要从一个View访问多个模型。以前，我的links_controller仅用于提供以不同方式排序的链接资源。现在我想包括一个部分(我假设)显示按分数排序的顶级用户(@users=User.all.sort_by(&:score))我知道我可以将此代码插入每个链接操作并从View访问它，但这似乎不是“ruby方式”，我将需要在不久的将来访问更多模型。这可能会变得很脏，是否有针对这种情况的任何技术？注意事项:我认为我的应用程序正朝着单一格式和动态页面内容的方向发展，本质上是一个典型的网络应用程序。我知道before_filter但考虑到我希望应用程序进入的方向，这似乎很麻烦。最终从任何
我在我的项目中添加了一个系统来重置用户密码并通过电子邮件将密码发送给他，以防他忘记密码。昨天它运行良好(当我实现它时)。当我今天尝试启动服务器时，出现以下错误。=>BootingWEBrick=>Rails3.2.1applicationstartingindevelopmentonhttp://0.0.0.0:3000=>Callwith-dtodetach=>Ctrl-CtoshutdownserverExiting/Users/vinayshenoy/.rvm/gems/ruby-1.9.3-p0/gems/actionmailer-3.2.1/lib/action_mailer
刚入门rails，开始慢慢理解。有人可以解释或给我一些关于在application_controller中编码的好处或时间和原因的想法吗？有哪些用例。您如何为Rails应用程序使用应用程序Controller？我不想在那里放太多代码，因为据我了解，每个请求都会调用此Controller。这是真的？ 最佳答案 ApplicationController实际上是您应用程序中的每个其他Controller都将从中继承的类(尽管这不是强制性的)。我同意不要用太多代码弄乱它并保持干净整洁的态度，尽管在某些情况下ApplicationContr
我想向我的Controller传递一个参数，它是一个简单的复选框，但我不知道如何在模型的form_for中引入它，这是我的观点:{:id=>'go_finance'}do|f|%>Transferirde:para:Entrada:"input",:placeholder=>"Quantofoiganho?"%>Saída:"output",:placeholder=>"Quantofoigasto?"%>Nota:我想做一个额外的复选框，但我该怎么做，模型中没有一个对象，而是一个要检查的对象，以便在Controller中创建一个ifelse，如果没有检查，请帮助我，非常感谢,谢谢
我注意到像bundler这样的项目在每个specfile中执行requirespec_helper我还注意到rspec使用选项--require，它允许您在引导rspec时要求一个文件。您还可以将其添加到.rspec文件中，因此只要您运行不带参数的rspec就会添加它。使用上述方法有什么缺点可以解释为什么像bundler这样的项目选择在每个规范文件中都需要spec_helper吗？ 最佳答案 我不在Bundler上工作，所以我不能直接谈论他们的做法。并非所有项目都checkin.rspec文件。原因是这个文件，通常按照当前的惯例，只