[GH-ISSUE #39] Debugging connection was closed. Reason: Render process gone. #21

Closed
opened 2026-03-02 03:42:40 +03:00 by kerem · 8 comments
Owner

Originally created by @KingPsychopath on GitHub (Nov 29, 2022).
Original GitHub issue: https://github.com/davidarroyo1234/InstagramUnfollowers/issues/39

Summary

At larger amounts of followings(500+) on Edge and Chrome the tool appears to halt and crash.

System Environment

AMD Ryzen 5950x
RTX 3080
64GB Ram

Edge Version 107.0.1418.52 (Official build) (64-bit)

Screenshot

image

How to Reproduce

  1. Open Instagram and login to an account following more than 1000-2000 people
  2. Run code from dev terminal
  3. Wait until the amount searched approaches 1000
  4. An error should occur in terminal and the page should crash.

Suggested Fix

The ability to pause the search until root cause is found; so that unfollowers can be removed in chunks rather than in bulk.

Originally created by @KingPsychopath on GitHub (Nov 29, 2022). Original GitHub issue: https://github.com/davidarroyo1234/InstagramUnfollowers/issues/39 ### Summary At larger amounts of followings(500+) on Edge and Chrome the tool appears to halt and crash. ### System Environment AMD Ryzen 5950x RTX 3080 64GB Ram Edge Version 107.0.1418.52 (Official build) (64-bit) ### Screenshot ![image](https://user-images.githubusercontent.com/6223066/204406765-bec48415-cbee-4dee-9435-ea9c4ec208c1.png) ### How to Reproduce 1. Open Instagram and login to an account following more than 1000-2000 people 2. Run code from dev terminal 3. Wait until the amount searched approaches 1000 4. An error should occur in terminal and the page should crash. ### Suggested Fix The ability to pause the search until root cause is found; so that unfollowers can be removed in chunks rather than in bulk.
kerem closed this issue 2026-03-02 03:42:40 +03:00
Author
Owner

@tomleb3 commented on GitHub (Nov 30, 2022):

Might be a memory leak. Worth checking out.
Need to see how I can test this since I don't follow that many users on my private account.

In the meantime, if anyone else also faced this issue, please comment here and let us know so we can assess the severity of the situation.

<!-- gh-comment-id:1332283262 --> @tomleb3 commented on GitHub (Nov 30, 2022): Might be a memory leak. Worth checking out. Need to see how I can test this since I don't follow that many users on my private account. In the meantime, if anyone else also faced this issue, please comment here and let us know so we can assess the severity of the situation.
Author
Owner

@davidarroyo1234 commented on GitHub (Nov 30, 2022):

This is happening probably because its rendering 1000 user entities. This should be paginated. This same thing happen on the first version in the early dev one year ago. in console mode it was not happening because it was plain text i guess.

1 option could be to paginate 100 users per page. And optionally a search bar.

<!-- gh-comment-id:1332291859 --> @davidarroyo1234 commented on GitHub (Nov 30, 2022): This is happening probably because its rendering 1000 user entities. This should be paginated. This same thing happen on the first version in the early dev one year ago. in console mode it was not happening because it was plain text i guess. 1 option could be to paginate 100 users per page. And optionally a search bar.
Author
Owner

@tomleb3 commented on GitHub (Nov 30, 2022):

Oh I didn't know you've had this issue in the past.
But still, seems strange that a browser would struggle rendering a list of ~1k users.
Then again I might be wrong.
I'll try to reproduce somehow and see what I can find.

<!-- gh-comment-id:1332369185 --> @tomleb3 commented on GitHub (Nov 30, 2022): Oh I didn't know you've had this issue in the past. But still, seems strange that a browser would struggle rendering a list of ~1k users. Then again I might be wrong. I'll try to reproduce somehow and see what I can find.
Author
Owner

@tomleb3 commented on GitHub (Dec 4, 2022):

Was able to easily reproduce by looping through the results.
@davidarroyo1234 You were right, I guess it is too much for the browser.
Need to see how to manage this. Should be refactored with pagination/intersection-observer/tabs/etc..

In the mean time, the older version that outputs to console still works just fine for anyone who needs it.
Here's the link to that version:
github.com/davidarroyo1234/InstagramUnfollowers@84a0488a33

Note to self: Add a ref to this version in the readme as well.

<!-- gh-comment-id:1336494423 --> @tomleb3 commented on GitHub (Dec 4, 2022): Was able to easily reproduce by looping through the results. @davidarroyo1234 You were right, I guess it is too much for the browser. Need to see how to manage this. Should be refactored with pagination/intersection-observer/tabs/etc.. In the mean time, the older version that outputs to console still works just fine for anyone who needs it. Here's the link to that version: https://github.com/davidarroyo1234/InstagramUnfollowers/tree/84a0488a33c01dbb7edff70437b63cdb4d161a3f **Note to self:** Add a ref to this version in the readme as well.
Author
Owner

@davidarroyo1234 commented on GitHub (Dec 11, 2022):

@tomleb3 I'll start doing the pagination thing. Did you start something or can i start this whitout issue?

<!-- gh-comment-id:1345652429 --> @davidarroyo1234 commented on GitHub (Dec 11, 2022): @tomleb3 I'll start doing the pagination thing. Did you start something or can i start this whitout issue?
Author
Owner

@tomleb3 commented on GitHub (Dec 11, 2022):

@davidarroyo1234 Nope, you can go ahead. I thought about starting to do it recently, but couldn't find the time.

<!-- gh-comment-id:1345655511 --> @tomleb3 commented on GitHub (Dec 11, 2022): @davidarroyo1234 Nope, you can go ahead. I thought about starting to do it recently, but couldn't find the time.
Author
Owner

@davidarroyo1234 commented on GitHub (Dec 11, 2022):

o it recently, but could

NP, i was asking to not do the work twice.

<!-- gh-comment-id:1345655771 --> @davidarroyo1234 commented on GitHub (Dec 11, 2022): > o it recently, but could NP, i was asking to not do the work twice.
Author
Owner

@davidarroyo1234 commented on GitHub (Dec 30, 2022):

Summary

At larger amounts of followings(500+) on Edge and Chrome the tool appears to halt and crash.

System Environment

AMD Ryzen 5950x RTX 3080 64GB Ram

Edge Version 107.0.1418.52 (Official build) (64-bit)

Screenshot

image

How to Reproduce

  1. Open Instagram and login to an account following more than 1000-2000 people
  2. Run code from dev terminal
  3. Wait until the amount searched approaches 1000
  4. An error should occur in terminal and the page should crash.

Suggested Fix

The ability to pause the search until root cause is found; so that unfollowers can be removed in chunks rather than in bulk.

Could you please check it again with the new update? Now should not crash due the new pagination integration.

<!-- gh-comment-id:1367993679 --> @davidarroyo1234 commented on GitHub (Dec 30, 2022): > ### Summary > At larger amounts of followings(500+) on Edge and Chrome the tool appears to halt and crash. > > ### System Environment > AMD Ryzen 5950x RTX 3080 64GB Ram > > Edge Version 107.0.1418.52 (Official build) (64-bit) > > ### Screenshot > ![image](https://user-images.githubusercontent.com/6223066/204406765-bec48415-cbee-4dee-9435-ea9c4ec208c1.png) > > ### How to Reproduce > 1. Open Instagram and login to an account following more than 1000-2000 people > 2. Run code from dev terminal > 3. Wait until the amount searched approaches 1000 > 4. An error should occur in terminal and the page should crash. > > ### Suggested Fix > The ability to pause the search until root cause is found; so that unfollowers can be removed in chunks rather than in bulk. Could you please check it again with the new update? Now should not crash due the new pagination integration.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/InstagramUnfollowers#21
No description provided.