nw_socket_handle_socket_event解决
http://www.bkjia.com/IOSjc/1158465.html
出现问题如下
to a parent directory scheduled for deletion
nw_endpoint_handler_start [3.1.1 14.18.245.206:80 initial path (null)]
2016-09-18 10:35:38.394 YangTao[8381:472349] 请求销毁->NWUpdatePlatRegex dealloc 耗时:0.007024049758911133
nw_endpoint_resolver_receive_report [3.1 pingma.qq.com:80 in_progress resolver (satisfied)] received child report:[3.1.1 14.18.245.206:80 initial path (null)]
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 in_progress proxy (satisfied)] received child report:[3.1.1 14.18.245.206:80 initial path (null)]
nw_connection_endpoint_report [3.1.1 14.18.245.206:80 initial path (null)] reported event path:start
nw_endpoint_handler_path_change [3.1.1 14.18.245.206:80 waiting path (satisfied)]
nw_endpoint_resolver_receive_report [3.1 pingma.qq.com:80 in_progress resolver (satisfied)] received child report:[3.1.1 14.18.245.206:80 waiting path (satisfied)]
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 in_progress proxy (satisfied)] received child report:[3.1.1 14.18.245.206:80 waiting path (satisfied)]
nw_connection_endpoint_report [3.1.1 14.18.245.206:80 waiting path (satisfied)] reported event path:satisfied
-[NWConcrete_nw_endpoint_flow startWithHandler:] [3.1.1 14.18.245.206:80 waiting socket-flow (satisfied)]
nw_endpoint_flow_setup_socket [3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)] creating socket
nw_endpoint_flow_attach_protocols [3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)]
__nwlog_err_simulate_crash simulate crash already simulated "nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available"
nw_socket_set_common_sockopts setsockopt SO_NOAPNFALLBK failed: [42] Protocol not available, dumping backtrace:
[x86_64] libnetcore-856.1.8
0 libsystem_network.dylib 0x000000010dacb80e __nw_create_backtrace_string + 123
1 libnetwork.dylib 0x000000010e155194 nw_socket_add_input_handler + 3002
2 libnetwork.dylib 0x000000010e132db8 nw_endpoint_flow_attach_protocols + 3768
3 libnetwork.dylib 0x000000010e131dd5 nw_endpoint_flow_setup_socket + 563
4 libnetwork.dylib 0x000000010e130b34 -[NWConcrete_nw_endpoint_flow startWithHandler:] + 2612
5 libnetwork.dylib 0x000000010e14bd11 nw_endpoint_handler_path_change + 1261
6 libnetwork.dylib 0x000000010e14b740 nw_endpoint_handler_start + 570
7 libnetwork.dylib 0x000000010e163003 nw_endpoint_resolver_start_next_child + 2240
8 libdispatch.dylib 0x000000
nw_endpoint_flow_attach_protocols [3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)] Attached flow protocol
nw_endpoint_resolver_receive_report [3.1 pingma.qq.com:80 in_progress resolver (satisfied)] received child report:[3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)]
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 in_progress proxy (satisfied)] received child report:[3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)]
nw_connection_endpoint_report [3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)] reported event flow:start_connect
nw_socket_handle_socket_event Event mask: 0x800
nw_socket_handle_socket_event Socket received CONNECTED event
nw_socket_setup_notsent_lowat Set TCP_NOTSENT_LOWAT(16384)
nw_endpoint_flow_protocol_connected [1.1.1 140.205.134.243:80 in_progress socket-flow (satisfied)] Output protocol connected
nw_endpoint_flow_connected_path_change [1.1.1 140.205.134.243:80 ready socket-flow (satisfied)]
nw_endpoint_flow_connected_path_change [1.1.1 140.205.134.243:80 ready socket-flow (satisfied)] Connected path is satisfied
nw_endpoint_resolver_receive_report [1.1 log.umsns.com:80 in_progress resolver (satisfied)] received child report:[1.1.1 140.205.134.243:80 ready socket-flow (satisfied)]
nw_endpoint_proxy_receive_report [1 log.umsns.com:80 in_progress proxy (satisfied)] received child report:[1.1.1 140.205.134.243:80 ready socket-flow (satisfied)]
nw_connection_endpoint_report [1.1.1 140.205.134.243:80 ready socket-flow (satisfied)] reported event flow:finish_connect
2016-09-18 10:35:38.404 YangTao[8381:472349] application:didFailToRegisterForRemoteNotificationsWithError: Error Domain=NSCocoaErrorDomain Code=3010 "remote notifications are not supported in the simulator" UserInfo={NSLocalizedDescription=remote notifications are not supported in the simulator}
nw_endpoint_proxy_receive_report [1 log.umsns.com:80 in_progress proxy (satisfied)] received child report:[1.1 log.umsns.com:80 ready resolver (satisfied)]
nw_connection_endpoint_report [1.1 log.umsns.com:80 ready resolver (satisfied)] reported event flow:finish_connect
nw_connection_endpoint_report [1 log.umsns.com:80 ready proxy (satisfied)] reported event flow:finish_connect
nw_endpoint_resolver_receive_report [1.1 log.umsns.com:80 ready resolver (satisfied)] received child report:[1.1.1 140.205.134.243:80 ready socket-flow (satisfied)]
nw_endpoint_proxy_receive_report [1 log.umsns.com:80 ready proxy (satisfied)] received child report:[1.1.1 140.205.134.243:80 ready socket-flow (satisfied)]
nw_connection_endpoint_report [1.1.1 140.205.134.243:80 ready socket-flow (satisfied)] reported event flow:changed_viability
nw_endpoint_proxy_receive_report [1 log.umsns.com:80 ready proxy (satisfied)] received child report:[1.1 log.umsns.com:80 ready resolver (satisfied)]
nw_connection_endpoint_report [1.1 log.umsns.com:80 ready resolver (satisfied)] reported event flow:changed_viability
nw_connection_endpoint_report [1 log.umsns.com:80 ready proxy (satisfied)] reported event flow:changed_viability
__tcp_connection_start_block_invoke 1 sending event TCP_CONNECTION_EVENT_CONNECTED in response to state ready and error (null)
tcp_connection_event_notify 1 event: TCP_CONNECTION_EVENT_CONNECTED, reason: nw_connection event, should deliver: true
tcp_connection_get_statistics DNS: 3ms/29ms since start, TCP: 71ms/108ms since start, TLS: 0ms/0ms since start
nw_socket_handle_socket_event Event mask: 0x800
nw_socket_handle_socket_event Socket received CONNECTED event
nw_socket_setup_notsent_lowat Set TCP_NOTSENT_LOWAT(16384)
nw_endpoint_flow_protocol_connected [3.1.1 14.18.245.206:80 in_progress socket-flow (satisfied)] Output protocol connected
nw_endpoint_flow_connected_path_change [3.1.1 14.18.245.206:80 ready socket-flow (satisfied)]
nw_endpoint_flow_connected_path_change [3.1.1 14.18.245.206:80 ready socket-flow (satisfied)] Connected path is satisfied
nw_endpoint_resolver_receive_report [3.1 pingma.qq.com:80 in_progress resolver (satisfied)] received child report:[3.1.1 14.18.245.206:80 ready socket-flow (satisfied)]
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 in_progress proxy (satisfied)] received child report:[3.1.1 14.18.245.206:80 ready socket-flow (satisfied)]
nw_connection_endpoint_report [3.1.1 14.18.245.206:80 ready socket-flow (satisfied)] reported event flow:finish_connect
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 in_progress proxy (satisfied)] received child report:[3.1 pingma.qq.com:80 ready resolver (satisfied)]
nw_connection_endpoint_report [3.1 pingma.qq.com:80 ready resolver (satisfied)] reported event flow:finish_connect
nw_connection_endpoint_report [3 pingma.qq.com:80 ready proxy (satisfied)] reported event flow:finish_connect
nw_endpoint_resolver_receive_report [3.1 pingma.qq.com:80 ready resolver (satisfied)] received child report:[3.1.1 14.18.245.206:80 ready socket-flow (satisfied)]
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 ready proxy (satisfied)] received child report:[3.1.1 14.18.245.206:80 ready socket-flow (satisfied)]
nw_connection_endpoint_report [3.1.1 14.18.245.206:80 ready socket-flow (satisfied)] reported event flow:changed_viability
nw_endpoint_proxy_receive_report [3 pingma.qq.com:80 ready proxy (satisfied)] received child report:[3.1 pingma.qq.com:80 ready resolver (satisfied)]
nw_connection_endpoint_report [3.1 pingma.qq.com:80 ready resolver (satisfied)] reported event flow:changed_viability
nw_connection_endpoint_report [3 pingma.qq.com:80 ready proxy (satisfied)] reported event flow:changed_viability
__tcp_connection_start_block_invoke 3 sending event TCP_CONNECTION_EVENT_CONNECTED in response to state ready and error (null)
tcp_connection_event_notify 3 event: TCP_CONNECTION_EVENT_CONNECTED, reason: nw_connection event, should deliver: true
tcp_connection_get_statistics DNS: 4ms/10ms since start, TCP: 17ms/35ms since start, TLS: 0ms/0ms since start
2016-09-18 10:35:47.071454 YangTao[8381:472400] subsystem: com.apple.coreanimation, category: CADebug, enable_level: 2, persist_level: 1, default_ttl: 0, info_ttl: 0, debug_ttl: 0, generate_symptoms: 0, enable_oversize: 1, privacy_setting: 0, enable_private_data: 0nw_socket_handle_socket_event解决的更多相关文章
- IE6、7下html标签间存在空白符，导致渲染后占用多余空白位置的原因及解决方法
直接上图:原因:该div包含的内容是靠后台进行print操作,输出的.如果没有输出任何内容,浏览器会默认给该空白区域添加空白符.在IE6.7下,浏览器解析渲染时,会认为空白符也是占位置的,默认其具有字 ...
- 关于解决python线上问题的几种有效技术
工作后好久没上博客园了,虽然不是很忙,但也没学生时代闲了.今天上博客园,发现好多的文章都是年终总结,想想是不是自己也应该总结下,不过现在还没想好,等想好了再写吧.今天写写自己在工作后用到的技术干货,争 ...
- DBImport V3.7版本发布及软件稳定性（自动退出问题）解决过程分享
DBImport V3.7介绍: 1:先上图,再介绍亮点功能: 主要的升级功能为: 1:增加(Truncate Table)清表再插入功能: 清掉再插,可以保证两个库的数据一致,自己很喜欢这个功能. ...
- MVVM框架从WPF移植到UWP遇到的问题和解决方法
MVVM框架从WPF移植到UWP遇到的问题和解决方法 0x00 起因 这几天开始学习UWP了,之前有WPF经验,所以总体感觉还可以,看了一些基础概念和主题,写了几个测试程序,突然想起来了前一段时间在W ...
- java中文乱码解决之道（一）-----认识字符集
沉寂了许久(大概有三个多月了吧),LZ"按捺不住"开始写博了! java编码中的中文问题是一个老生常谈的问题了,每次遇到中文乱码LZ要么是按照以前的经验修改,要么则是baidu.c ...
- XStream将java对象转换为xml时，对象字段中的下划线“_”，转换后变成了两个的解决办法
在前几天的一个项目中,由于数据库字段的命名原因 其中有两项:一项叫做"市场价格"一项叫做"商店价格" 为了便于区分,遂分别将其命名为market ...
- 懒加载session 无法打开 no session or session was closed 解决办法（完美解决）
首先说明一下,hibernate的延迟加载特性(lazy).所谓的延迟加载就是当真正需要查询数据时才执行数据加载操作.因为hibernate当中支持实体对象,外键会与实体对象关联起来.如 ...
- 使用JSONObject.fromObject的时候出现“There is a cycle in the hierarchy”异常 的解决办法
在使用JSONObject.fromObject的时候,出现“There is a cycle in the hierarchy”异常. 意思是出现了死循环,也就是Model之间有循环包含关系: ...
- iPhone Anywehre虚拟定位提示“后台服务未启动，请重新安装应用后使用”的解决方法
问题描述: iPhone越狱了,之后在Cydia中安装Anywhere虚拟定位,但是打开app提示:后台服务未启动,请重新安装应用后使用. 程序无法正常使用... 解决方法: 打开Cydia-已安装, ...
随机推荐
- win8提升winform软件的权限
在win8系统中,微软提高了系统盘文件的权限,提高了其他系统操作的权限,因此一些桌面应用程序在运行时会报一些权限错误,比如C盘文件操作权限,或注册表操作无权限等. 我之前开发过一款用笔记本一键架设无线 ...
- Spark1.3使用外部数据源时条件过滤只要是字符串类型的值均报错
CREATE TEMPORARY TABLE spark_tbls USING org.apache.spark.sql.jdbc OPTIONS ( url 'jdbc:mysql://hadoop ...
- Python-2 print
#1 print函数(python版本3.3.5): >>> help(print)Help on built-in function print in module builtin ...
- .vimrc vim 配置大全
map <F9> :call SaveInputData()<CR>func! SaveInputData() exec "tabnew" exec 'no ...
- MVC执行过程
HttpRuntime中的PR方法1,封装HttpContext2,获取HttpApplication 主要做3件事a,执行本事件时主要调用Init将Global编译得到类型,b,确保Appstart ...
- 前端学习实践笔记--JavaScript深入【2】
趁热继续再来学习一波,接下来主要介绍函数,object,数组,面向对象,new实例化. 在介绍“对象”之前,首先得梳妆打扮一番吧,那这梳妆打扮主要有两条路线,一条是淑女范(利用函数对象化),一条是邻家 ...
- 8、SQL Server 表分区
什么是表分区?表分区其实就是将一个大表分成若干个小表.表分区可以从物理上将一个大表分成几个小表,但是逻辑上还是一个表.所以当执行插入.更新等操作的时候,不需要我们去判断应该插入或更新到哪个表中.只需要 ...
- O2O迈进智能时代 百度构建“服务生态”
经历过山车式资本市场后,O2O领域正努力摆脱“低门槛”,或将迎来技术创新之争.在刚刚落幕的百度世界大会上,百度副总裁.百度糯米总经理曾良宣布:将以百度糯米.手机百度和百度地图为核心构建百度服务生态.在 ...
- java 平台 权限管理
最近在做公司内部的物流业务平台的权限管理,感触颇多.记录一下 权限管理分两部分:数据权限和操作权限. 数据权限: 这个是和用户相关的. 因为平台是多机构的,所以再考虑数据权限的时候,是按照机构来管理的 ...
- 格式化namenode，造成无法启动datanode
一个常见的问题:格式化namenode,造成无法启动datanode的问题. 问题描述: 无法启动datanode,查看日志,datanote尝试n次启动无效后,会出现这个语句 INFO ...