Ask a Question
GoPro Support Hub Ask a question. Share an answer. Find a solution. Stay stoked.
Announcements
Is your GoPro gear up to date? Check to see If it is on our Update page.
GoPro Apps for Desktop
%3CLINGO-SUB%20id%3D%22lingo-sub-64352%22%20slang%3D%22en-US%22%3EGoProPushNotificationService.exe%20consumes%20all%20of%20tcp%2Fip%20resources%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-64352%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20system%20is%20a%20Windows%2010%20x64%20PC%20with%2016GB%20ram%20and%20a%20few%20Terabytes%20of%20drive%20space.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERecently%2C%20i've%20been%20having%20an%20issue%20where%20leaving%20GoPro%20Quik%20open%20for%20a%20day%20or%20so%20results%20in%20GoProPushNotification.exe%20consuming%20all%20the%20tcp%2Fip%20ports%20on%20my%20system.%20%26nbsp%3Bthe%20.exe%20is%20creating%20connections%20to%20itself%20via%20loopback.%20%26nbsp%3BOnce%20all%20tcpip%20ports%20are%20exhausted%2C%20I%20am%20no%20longer%20able%20to%20browse%20the%20internet%2C%20as%20GoProPushNotification.exe%20has%20effectively%20DoS'd%20me%20and%20consumed%20all%20tcpip%20resources.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%20Event%20log%20shows%20an%20event%204227%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Erunning%20netstat%20-anb%20to%20identify%20the%20executable%20responsible%20shows%20thousands%20of%20lines%20similiar%20to%20below%3A%3C%2FP%3E%3CP%3E%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49154%20127.0.0.1%3A49165%20ESTABLISHED%5BGoProPushNotificationService.exe%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGiven%20this%20info%2C%20killing%20the%20task%20results%20in%20me%20immediately%20being%20able%20to%20resume%20connectivity.%20%26nbsp%3BI%20have%20had%20this%20issue%20on%20numerous%20occassions%20and%20it%20is%20a%20pain.TCP%20127.0.0.1%3A49155%20127.0.0.1%3A49154%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49155%20127.0.0.1%3A49156%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49156%20127.0.0.1%3A49155%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49158%20127.0.0.1%3A49159%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49158%20127.0.0.1%3A49161%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49159%20127.0.0.1%3A49158%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49161%20127.0.0.1%3A49158%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49162%20127.0.0.1%3A49163%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49163%20127.0.0.1%3A49162%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49165%20127.0.0.1%3A49154%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49165%20127.0.0.1%3A49166%20ESTABLISHED%5BGoProPushNotificationService.exe%5DTCP%20127.0.0.1%3A49166%20127.0.0.1%3A49165%20ESTABLISHED%5BGoProPushNotificationService.exe%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-64352%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EQuik%20for%20Desktop%20-%20Windows%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Reply
Highlighted
Sightseer
Posts: 1

GoProPushNotificationService.exe consumes all of tcp/ip resources

My system is a Windows 10 x64 PC with 16GB ram and a few Terabytes of drive space.  

 

Recently, i've been having an issue where leaving GoPro Quik open for a day or so results in GoProPushNotification.exe consuming all the tcp/ip ports on my system.  the .exe is creating connections to itself via loopback.  Once all tcpip ports are exhausted, I am no longer able to browse the internet, as GoProPushNotification.exe has effectively DoS'd me and consumed all tcpip resources.

 

Windows Event log shows an event 4227

 

running netstat -anb to identify the executable responsible shows thousands of lines similiar to below:

[GoProPushNotificationService.exe]
TCP 127.0.0.1:49154 127.0.0.1:49165 ESTABLISHED
[GoProPushNotificationService.exe]

 

Given this info, killing the task results in me immediately being able to resume connectivity.  I have had this issue on numerous occassions and it is a pain.
TCP 127.0.0.1:49155 127.0.0.1:49154 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49155 127.0.0.1:49156 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49156 127.0.0.1:49155 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49158 127.0.0.1:49159 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49158 127.0.0.1:49161 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49159 127.0.0.1:49158 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49161 127.0.0.1:49158 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49162 127.0.0.1:49163 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49163 127.0.0.1:49162 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49165 127.0.0.1:49154 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49165 127.0.0.1:49166 ESTABLISHED
[GoProPushNotificationService.exe]
TCP 127.0.0.1:49166 127.0.0.1:49165 ESTABLISHED
[GoProPushNotificationService.exe]