question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

getting memory issues in latest develop branch

See original GitHub issue

It doesn’t happen every time, but quite often. URL is

kadist-ios.herokuapp.com/knews_main?channel=kadist&lang=en

logs:

2017-06-22 21:34:18.478562-0700 Jasonette[18579:5013853] libMobileGestalt MobileGestaltSupport.m:153: pid 18579 (Jasonette) does not have sandbox access for frZQaeyWLUvLjeuEK43hmg and IS NOT appropriately entitled
2017-06-22 21:34:18.478707-0700 Jasonette[18579:5013853] libMobileGestalt MobileGestalt.c:550: no access to InverseDeviceID (see <rdar://problem/11744455>)
2017-06-22 21:34:20.554422-0700 Jasonette[18579:5013853] [LayoutConstraints] _UIConstraintBasedLayoutLogUnsatisfiable is OFF
2017-06-22 21:35:54.151587-0700 Jasonette[18579:5013853] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles
2017-06-22 21:35:54.152854-0700 Jasonette[18579:5013853] [MC] Reading from public effective user settings.
2017-06-22 21:38:35.203198-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 12, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.203248-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 15, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.203337-0700 Jasonette[18579:5014658] [] nw_socket_get_input_frames recvmsg(fd 16, 1024 bytes): [57] Socket is not connected
2017-06-22 21:38:35.223385-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [22.1 54.243.158.73:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.223567-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [3.1 23.23.231.146:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.223748-0700 Jasonette[18579:5014658] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:38:35.223760-0700 Jasonette[18579:5014658] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:38:35.240330-0700 Jasonette[18579:5015095] [] nw_endpoint_handler_add_write_request [23.1 174.129.208.167:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:38:35.240828-0700 Jasonette[18579:5015095] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:13.961876-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 14, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.961935-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 15, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.961974-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 16, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962009-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 17, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962041-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 18, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.962079-0700 Jasonette[18579:5016115] [] nw_socket_get_input_frames recvmsg(fd 19, 1024 bytes): [57] Socket is not connected
2017-06-22 21:41:13.989077-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [25.1 54.243.113.132:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999319-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [31.1 54.243.113.132:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999504-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [30.1 54.243.113.132:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999629-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [28.1 54.243.113.132:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:13.999734-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [29.1 54.243.113.132:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:14.000044-0700 Jasonette[18579:5017328] [] nw_endpoint_handler_add_write_request [26.2 54.243.32.154:443 failed socket-flow (satisfied)] cannot accept write requests
2017-06-22 21:41:14.000177-0700 Jasonette[18579:5017328] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001015-0700 Jasonette[18579:5016517] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001038-0700 Jasonette[18579:5017325] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001054-0700 Jasonette[18579:5016115] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001070-0700 Jasonette[18579:5016694] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
2017-06-22 21:41:14.001083-0700 Jasonette[18579:5016102] [] tcp_connection_write_eof_block_invoke Write close callback received error: [22] Invalid argument
Message from debugger: Terminated due to memory issue

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:10 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
darenrcommented, Jun 23, 2017

thanks - just did a build and am trying, I’ll try it over the day and report back. I will also try to see in Xcode what the memory footprint is over time running it. Really appreciate you looking at this.

0reactions
gliechtensteincommented, Jun 24, 2017

great to hear, thanks for reporting!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Easier way to keep a git feature branch up to date
In order to stay on top of changes (i.e. resolve conflicts) I find I need to keep the feature branches I'm actively working...
Read more >
How to Solve Git Branching Problem | by sunil kumar sahoo
Each of us started working on different features and issue fix. ... Take the latest code (git pull) from remote develop branch; Create...
Read more >
How to perform a Git clean up of branches and commits example
Clean up Git commits​​ In this example repository, there's only one unshared commit on the master branch, but multiple on feature and develop...
Read more >
How to undo a push or merge in Git branch - Level Up Coding
With Git subversion system, merging and branching are no more scary. In this post, I will explain how to undo an accidentally pushed...
Read more >
Dementia - Symptoms and causes - Mayo Clinic
This group of symptoms with many causes affects memory, thinking and social abilities. Some symptoms may be reversible.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found