TCP connections alive well after Firefox is closed

According to Sysinternals TCPView, I have several TCP connections that stay open (established) well after I close and exit Firefox, I'm talking 8 hours after. Normal connections close within minutes if shutting down Firefox. I'd post a pic, but there is no option for it so here's a paste (commas instead of tabs):
process/protocol, local address, remote asddress, state
firefox.exe.7108, TCP, russ-l675,gt,rr,com.53713, dfw06s17-in-17.1e100.net:http, established
firefox.exe.7108, TCP, russ-l675,gt,rr,com.54103, 203.30.164.5:http, established
I can (and do!) manually close these connections and they don't come back until I restart FF.
Thanks!
Russ

Yes, but it's been disabled for over a week and this is still happening. Just to be sure, I will uninstall the add-ons. One of these resolves to Australia and the other to a Google server. Am I being watched? This info comes up from the "odd" IP address:
MarkMonitor is the Global Leader in Online Brand Protection.
MarkMonitor Domain Management(TM)
MarkMonitor Brand Protection(TM)
MarkMonitor AntiPiracy(TM)
MarkMonitor AntiFraud(TM)
Professional and Managed Services
Visit MarkMonitor at www.markmonitor.com
Contact us at 1 (800) 745-9229
In Europe, at +44 (0) 203 206 2220
The Data in MarkMonitor.com's WHOIS database is provided by MarkMonitor.com for information purposes, and to assist persons in obtaining information about or related to a domain name registration record. MarkMonitor.com does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail (spam); or (2) enable high volume, automated, electronic processes that apply to MarkMonitor.com (or its systems). MarkMonitor.com reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
Registrant:
DNS Admin
Google Inc.
1600 Amphitheatre Parkway
Mountain View CA 94043
US
[email protected] +1.6502530000 Fax: +1.6506188571
Domain Name: 1e100.net
Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com
Administrative Contact:
DNS Admin
Google Inc.
1600 Amphitheatre Parkway
Mountain View CA 94043 US
[email protected] +1.6502530000 Fax: +1.6506188571
Technical Contact, Zone Contact:
DNS Admin
Google Inc.
1600 Amphitheatre Parkway
Mountain View CA 94043 US
[email protected] +1.6502530000 Fax: +1.6506188571
Created on..............: 2009-09-24.
Expires on..............: 2019-09-24.
Record last updated on..: 2012-04-20.
Domain servers in listed order:
ns2.google.com
ns3.google.com
ns1.google.com
ns4.google.com
MarkMonitor is the Global Leader in Online Brand Protection.
MarkMonitor Domain Management(TM)
MarkMonitor Brand Protection(TM)
MarkMonitor AntiPiracy(TM)
MarkMonitor AntiFraud(TM)
Professional and Managed Services
Visit MarkMonitor at www.markmonitor.com
Contact us at 1 (800) 745-9229
In Europe, at +44 (0) 203 206 2220
Russ

Similar Messages

Can't open tabs from previous session (after Firefox regularly closed)?!

Regularly closed firefox 36.0.4. and shot down computer (Windows 7 Pro 64-bit).
On next start, Firefox doesn't open tabs from previous session (altought it is configured to do this) !?!?!?
I lost about 30 tabs!!
Very, very frustrating!!!
Think to finish using Firefox forever!!!!!

Don't exit Firefox! Or if you already did, don't start it back up again!
''If Firefox is running:'' Open your current Firefox settings (AKA Firefox profile) folder using either
* "3-bar" menu button > "?" button > Troubleshooting Information
* (menu bar) Help > Troubleshooting Information
* type or paste about:support in the address bar and press Enter
In the first table on the page, click the "Show Folder" button. This should launch a new window listed various files and folders. For best results, change the view to "Details".
(''If Firefox not running, get to this folder by pasting the following in the Run box on the start menu and pressing Enter:'' %APPDATA%\Mozilla\Firefox\Profiles ''and then double-click into the most recently updated semi-randomly-named folder you find there.'')
In the window that launches, scroll down and double-click into the '''sessionstore-backups''' folder. Save all files here to a safe location, such as your Documents folder, so Firefox doesn't overwrite them. We may be able to use them to recover your lost tabs.
Also, if you return to the main level of the profile folder, you may find some sessionstore files. Copy those to the safe location as well.
Could you report back on what you found?
Note: If Windows hides the .js file extension from you, you can change a setting so that you can see all file extensions (this helps when renaming files). This support article has the steps: http://support.microsoft.com/kb/865219 or http://windows.microsoft.com/en-us/windows/show-hide-file-name-extensions
The kinds of files you may find among your sessionstore-backup files are:
* recovery.js: the windows and tabs in your currently live Firefox session (or, if Firefox is closed, your last session)
* recovery.bak: a backup copy of recovery.js
* previous.js: the windows and tabs in your last Firefox session
* upgrade.js-''build_id'': the windows and tabs in the Firefox session that was live at the time of your last update

Wheres the "continue downloading after firefox is closed" " button selection to set if you decide to close Firefox

where is the select button "continue downloading after Firefox/Nightly closes

I thought resumption of the download would happen anyway if you interrupt the download. The server has to support that resumption as well, however.

How to restore a previous session after firefox closed and cleared browsing history, is still any chance to get it back there?

Accidentally shut down the pc and firefox did not come back with option restore previous session at the first screen even in History-Restory previous session is Grey. My settings are clean history after firefox is closed.
Is there any change to get back on my Tabs from previous session even the history browsing was cleaned? I would appreciate your help!

In general FireFox will behave in 1 of 3 ways when restarted after a shutdown.
1. Kill Shutdown
This happens when the FireFox process is terminated with a TerminateProcess() call or if the FireFox process crashes. It is a dirty exit, no clean-up is done. When restarted after this FireFox will show a "Well this is embarrassing" dialog with options to restore selected parts of the previous session.
2. Force Shutdown
This happens when another process asks FireFox to shutdown cleanly (such as a PC restart) by a call to ExitProcessEx() and does not ask the user for confirmation. Normally, when this type of shutdown occurs, Firefox will just restore all tabs and sessions without asking. However if Firefox is set to automatically delete history on shutdown, it can't. I suspect this is your situation. I would suggest to the FF team that deleting history should be skipped in this case, only a user shutdown should delete history.
3. User shutdown.
This is when the user tells Firefox to close down (by selecting Exit or closing all tabs etc..). Confirmation is asked to close all tabs (if enabled and more than 1 tab is open). On restart, nothing is restored.
Unfortunately, if you have auto clear history enabled, there's no way to recover the previous session. Sorry.

Installed 3.6.6 and found PLUGIN-CONTAINER.EXE-15EDC9DD.pf running in task manager allowing voices/music from some unknown web site to continually play even though firefox is closed. 3.6.6 is a major problem and also continually crashes! in English

After downloading 3.6.6, plugin-container.exe allows an unknown website to continually stream audio through my speakers, even after firefox is closed. I kill the process in task manager and it still relaunches itself. I found this file also running by search my computer PLUGIN-CONTAINER.EXE-15EDC9DD.pf in c:\Windows\Prefetch. When I kill that process, audio instantly stops. But it relaunches after 10 minutes or so. The process eats up lots of memory. I've had to restart firefox in safe mode several times as it crashed even before opening. 3.6.6 is majorly flawed and I'm running Windows XP. Time to downgrade to 3.6.4
== This happened ==
Every time Firefox opened
== I downloaded 3.6.6

After downloading 3.6.6, plugin-container.exe allows an unknown website to continually stream audio through my speakers, even after firefox is closed. I kill the process in task manager and it still relaunches itself. I found this file also running by search my computer PLUGIN-CONTAINER.EXE-15EDC9DD.pf in c:\Windows\Prefetch. When I kill that process, audio instantly stops. But it relaunches after 10 minutes or so. The process eats up lots of memory. I've had to restart firefox in safe mode several times as it crashed even before opening. 3.6.6 is majorly flawed and I'm running Windows XP. Time to downgrade to 3.6.4
== This happened ==
Every time Firefox opened
== I downloaded 3.6.6

Just updated to 8 & now I can't open any web pages & firefox is still running in the background after browser was closed. I uninstalled and reinstalled as well as disabled add-ons and plugins nothing has changed, can I downgrade back to on older version?

Just updated to 8 & now I can not open any web pages as well as firefox will not close out, it still running in the background after browser was closed. I uninstalled and reinstalled as well as disabled add-ons and plugins nothing has changed, can I downgrade back to on older version?

See "Hang at exit":
*http://kb.mozillazine.org/Firefox_hangs
See "Firefox hangs when you quit it":
*https://support.mozilla.com/kb/Firefox+hangs
A possible cause is security software (firewall) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
See:
*https://support.mozilla.com/kb/Server+not+found
*https://support.mozilla.com/kb/Firewalls

TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection's socket in SQL2008R2

Hello,
I do get the below SQL error in production environment intermittently:
TCP connection closed but a child process of SQL Server may be holding a duplicate of the connection's socket. Consider enabling the TcpAbortiveClose SQL Server registry setting and restarting SQL Server. If the problem persists, contact Technical
Support.
According to the post I search in MSDN, the above error is fixed in SQL2008R-CU6, but I have SQL2008R2-SP02 CU09 patch in production environment and the above error still occurred intermittently. I am running SQL2008R2 SP02 CU09 patch with Windows 2008R2-SP01.
I would like to know if anyone has the same error happened to their SQL environment after applied SQL2008R2-SP02 CU06 patch and later.
Any suggestion would be helpful.
Best regards,
PL.

Hello,
What happen if you apply the changes on the registry explained on the workaround section of the following article?
http://support.microsoft.com/kb/2491214
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Proper method to reset tcp connection after timeout error

I have a application that I am building that communicates with a Modbus TCP device. If a communications error occurs I would like to be able the reset the TCP communications. What I have is a control that fires a event when pushed. In this event I have a sequence that first closes the tcp connection and then opens a new connection. My applications starts and runs fine. To test the reset function I removed the ethernet cable from the device and waited of a timeout to occur. I plugged the cable back in and pushed my reset control. Occasionally the reset will occur but most times I will get a time out error at the Open TCP vi. After this, the only way I can establish communications is to exit my application, disable and then enable my network device. Then when I restart my application I have communications with my device.
Any help would be appreciated on how I should be resetting my TCP connection.
Thanks
Terry
Solved!
Go to Solution.

Terry S wrote:
I have attached a example vi (LV10) that shows just the TCP connection and Reset. An error will occur when trying to perform the open tcp in the reset event.
As written your code should be fine. There is nothing inherently wrong with it. However depending on the device you are communicating with you may be trying to reestablish the connection too quickly after you closed the connection. The device may not allow multiple connections to it and may require sometime to clean things up on its end after you close a connection. As an experiment trying waiting a short time between the TCP Close and the TCP Open. If possible you may want to try using Wireshark to see what is happening on the network. It can be useful in diagnosing what is going on.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

FMS closing the TCP connection forcibly

Hi,
I am developing an live encoder programs to publish the audio and video content to FMS. After establishing the TCP connection with FMS, when i start sending commanda and data, FMS is closing the TCP connection forcibly. Can anyone explain why is this happening?
Thanks and Regards,
Vishwanath

Hi,
If you use wireshark you can see what is happening on the wire to capture what FMS is sending (if at all) back to your live encoder program. Very very useful tool.
BTW what version of FMS are you using? Have you tried FMLE 3.2 to ensure your setup is good to go as a benchmark, this ensures you have a working FMS server ready for your own live encoder program.
I hope this helps with your debugging.

Router closes TCP connection after 30 minutes

I have recently replaced my D-Link DIR-100 router with a Cisco Linksys RV042, but unfortunately there seems to be a problem with it.
I have an external TCP connection coming in to a local service, and I therefore set up the router to redirect the incoming connection for the given port to the local PC hosting the service. This worked perfectly. I also opened the Firewall access rules to allow all data from WAN2 to be propagated through. This also worked just fine, and I can connect from the internet to the local PC, just like I could with my old router. Unfortunately this is where the simularities stop. When there is no communication on the TCP connection for more than 30 minutes then the router closes the connection automatically. This is NOT what I want. I only communicate on the TCP connection very rarely, but I do not want it closed automatically - at least not after just 30 minutes.
I did some research on line and it appears that there in some routers are a TCP connection timeout, which in the router I read about, defaulted to 1 day. This would be OK. I experimented and found that if there is communication every 30 minutes then it is not close the connection, but if there is 50minutes between communication then it closes the connection.
As I read that this timeout has to do with security I experimented with the firewall and found the following:
1. Disabling the entire router firewall fixes the problem !!!
2. Disabling just DoS has no effect (problem still exists)
3. Disabling SPI means I cannot connect at all !!! (new and much worse problem)
4. Disabling Block WAN Requests has no effect (problem still exists)
Is there a way to solve this problem without disabling the entire firewall, as that is not what I want to do. I have the system set up for Dual WAN (load balancing), and I only want to allow connections to a handful of ports on the one WAN, and block the other WAN entirely.
P.S. I was referred to the Cisco Small Business Support Community by the Cisco Home community, so I hope this is the right place.

Hi Ddb101,
This is a limitation (or feature depending on how you look at it) of the iPhone/iPod touch. 30 minutes after the device locks (usually 5 minutes of inactivity) the network turns off completely to save battery life. You can either turn autolock off globally, or some programs (mine for instance see: http://ootunes.com/app/ ) have an option that disables sleep while the app is running so the stream will keep playing... until your battery dies Only problem is with the screen on the battery actually dies even faster!
Finally, if the device is connected to a constant power source, it shouldn't actually time out. So if you have a way to plug it in, it shouldn't quit after 30 minutes on you...
hope that helps,
also, since there's a link to my site up there, and I sell the app, I should tell you that I might get money if you go to the page and end up buying my app...

Difference between closing the connection before and after committing user transaction?

          I was wondering what's the difference between closing the connection before committing
          the transaction versus closing the connection after committing the transaction?...
          for e.g....
          Scenario 1.........
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          conn.close();
          usertran.commit()
          Scenario 2...
          UserTransaction useretran;
          usertran.begin();
          Connection con = datasource.getCOnnection();
          // do bunch of stuff...
          usertran.commit()
          conn.close();
          thanks....
          Srini


Hi. As long as you're sure there's a transaction going on, and the connection
is a transaction-aware object (from a TxDataSource), either will be fine.
In the first scenario the actual semantics of the close() call are less than
normal, because we really don't close the connection or return it to the
pool until the actual transaction commits, and in the second case, we have
already taken the connection out of your service as of the commit().
The second scenario is the usual coding style. If there's ever a chance your
code will get non-transaction-aware connections, it is crucial to close
connections, and I always recommend putting the close() in a finally block
so it's guaranteed to happen.
Joe
srinivas wrote:
I was wondering what's the difference between closing the connection before committing
the transaction versus closing the connection after committing the transaction?...
for e.g....
Scenario 1......... UserTransaction useretran; usertran.begin(); Connection con =
datasource.getCOnnection(); // do bunch of stuff... conn.close(); usertran.commit()
Scenario 2... UserTransaction useretran; usertran.begin(); Connection con = datasource.getCOnnection();
// do bunch of stuff... usertran.commit() conn.close();
thanks....
Srini

Opening and closing Multiple TCP connections issues

Hi all I am having an issue with the TCP VI’s and wondering if anyone has experienced this issue.
My application is required to scan 50-100 IP addresses (statically assigned) and discover if an Ethernet device is connect at that IP address. Currently I am able to achieve this by opening a TCP connection and testing the error cluster to determine if a timeout has occurred (no timeout error means Ethernet device available at the IP address). I then ensure that the TCP connections are closed.
The issue I am have is that I require a 1 second delay between the TCP open and the TCP close which significantly slows down the process. Without the 1 second delay the vi successfully connects to the device once then fails to make any TCP connect regardless of the time delay until the PC is reset.
If anyone has any advice I would be very grateful
David Barr
P.S. I have attached a simplified section of code showing this issue
Attachments:
TCP Open close issue.vi ‏15 KB

smercurio_fc wrote:
If I understand you correctly you want the time delay to be 1 second if there's a successful connection....
While I don't have a specific answer for this problem. I want to clarify for him. I believe the issue is, what if all connections ARE there? That means you keep returning a wait of 1 second 50-100 times so It takes 50-100 seconds just to initialize. I think the user is looking for a way to check for valid connections, but do so in such a way that eliminates the need for a wait which is greatly slowing things down.
CLA, LabVIEW Versions 2010-2013

TCP connection error when sending MODBUS commands to WAGO 750-881 controller after 113655 bytes of data have been sent

Hi all,
I am new to the world of labview and am attempting to build a VI which sends commands to a 750-881 WAGO controller at periodic intervals of 10ms.
To set each of the DO's of the WAGO at once I therefore attempt to send the Modbus fc15 command every 10ms using the standard Labview TCP write module.
When I run the VI it works for about a minute before I recieve an Error 56 message telling me the TCP connection has timed out. Thinking this strange, I decided to record the number of bytes sent via the TCP connection whilst running the program. In doing so I noticed that the connection broke after exactly 113655 Bytes of data had been sent each time.
Thinking that I may have been sending too many messages I increased the While-loop delay from 10ms to 20, 100 and 200 ms but the error remained. I also tried playing with the TCP connection timeout and the TCP write timeout but neither of these had any effect on the problem.
I cannot see why this error is occuring, as the program works perfectly up untill the 113655 Bytes mark.
I have attached a screenshot of the basic VI (simply showing a MODBUS command being sent every second) and of a more advanced VI (where I am able to control each DO of the WAGO manually by setting a frequency at which the DO should switch between ON and OFF).
If anybody has any ideas on where the problems lie, or what I could do to further debug the program this would be greatly appreciated.
Solved!
Go to Solution.
Attachments:
Basic_VI.png ‏84 KB
Expanded_VI.png ‏89 KB

AvdLinden wrote:
Hi ThiCop,
Yes the error occurs after exactly 113655 bytes every time. The timeout control I would like to use is 10ms, however even increasing this to 1s or 10s does not remove the error, which leads me to believe that this is not the issue (furthermore, not adding any delay to the while loop, thus letting it run at maximum speed, has shown that the TCP connection is able to send all 113655 bytes in under 3 seconds again pointing towards the timeout control not being the issue here).
I attempted Marco's suggestion but an having difficulty translating the string returned into a readable string, (rightnow the response given is " -# + ").
As to your second suggestion, I implemented something similar where I created a sub VI to build a TCP connection, send a message and then close the connection. I now build each message and then send the string to this subVI which successfully sends the command to my application. Whilst not being the most elegant method of solving the issue, it has resolved the timeout problem meaning I am able to send as many commands as I want. So in that sense the problem has been solved.
If you still have tips on how to correctly read the TCP read output, I would however like to see if I could not get my first program to work as it is slightly more robust in terms of timing.
Modbus TCP RTU is a binary protocol, as you show in your Basic VI, where you format the data stream using byte values. So you have to interprete the returned answer accordingly with the Modbus RTU spec in hand. Now what is most likely happening is that the connection gets hung after a while since you do NOT read the data the device sends as response to your commands. The TCP/IP stack buffers those bytes and at some point the internal buffers overflow and the connection is blocked by the stack. So adding the TCP Read at strategic places (usually after each write) is the proper solution for this. Is there any reason that you didn't use the NI provided Modbus TCP library?
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

After Firefox upgrade, Windows 7 no longer allows hyperlinks in e-mails to connect. Message is "This operations has been cancelled due to restrictions in your computer."

After Firefox upgrade just a few minutes ago, Windows 7 no longer allows hyperlinks in e-mails (Outlook 2003) to connect. Message is "This operations has been cancelled due to restrictions in your computer. Please contact your system administrator."

I use Windows 7 x64 with Office 2010 and the message I get is General Failure. the URL was:..... An error occured in sending the command to the application.
This only started happening after the 3.6.14 update.

How to prevent a TCP connection being closed when the VI that opened it finishes.

Hello everyone.
I am developing an application based around servers and clients communicating over TCP in LabVIEW 2012.
When the server/client opens a TCP connection ,it launches an asynchronosly running "connection handler", to which it passes the connection reference which then takes over all the communcation. This all works fine.
However - I have a situation where a client's connection handler can be informed of another "new" server. I would like it to open the connection (to see if it is still valid) and then pass this connection reference back to the client's main code to spawn a new connection handler. This prevents me locking up the Client's main code with a long-ish timeout if the "new" server is not actually accepting connections.
The issue is that if the connection handler that opened up the connection to the "new" server is stopped, then it appears to destroy the reference that it opened. This means that the other connection handler that was merrily communcating with the "new" server has its TCP communciations closed (I get an Error code 1 on a write).
I have created an example to demonstrate the issue which should be used as follows:
1. Run server.vi - it will listen for a connection on the port specifed on its BD.
2. Run CH Launcher.vi - it will open a connection to the server and pass the TCP reference to an instance of Connection Handler.vi which it launches.
3. The Connection Handler should send data to the Server
4. Stop the CH Launcher.vi
5. The Connection Handler.vi will error.
Any suggestions would be much appreciated.
Cheers
John
Solved!
Go to Solution.
Attachments:
TCP Test.zip ‏35 KB

John_Neutron escreveu:
In my case I have changes the part of the code that opens the TCP connection to a VI that has the same lifetime as the main VI so that any connections that have been opened will only be closed automatically when the main VI stops.
And what are the effects? You are still facing the same problem or closing the connection only when the whole applicaton stops solved your problem?
Regards
Mondoni

TCP connections alive well after Firefox is closed

Similar Messages

Maybe you are looking for