Posts Tagged ‘performance issues’
Thursday, May 24, 2012 @ 03:05 PM gHale
The Pilgrim Nuclear Power Station manually shut down while at reduced power during a condenser cleaning operation, a federal nuclear official said.
The condenser takes water from Cape Cod Bay and uses it to cool steam produced in the reactor to spin the turbine and generate electricity, according to officials with the Nuclear Regulatory Commission (NRC) and Entergy Nuclear, the company that owns the Plymouth, MA, plant.
During the cleaning, the condenser began to lose vacuum and they shut down the reactor shortly after 1 p.m., said NRC spokesman Neil Sheehan.
“There were no complications during the shut down,” Sheehan said.
The plant’s resident NRC inspectors responded to the facility’s control room when they learned of the event, he said.
They did not identify any safety concerns or performance issues, Sheehan said, adding they will follow the company’s efforts to troubleshoot the problem.
Plant technicians are investigating the cause of the loss of vacuum, said Entergy spokesman Rob Williams.
Once they find the cause, workers will make any necessary repairs and the plant will come back online, Williams said.
In May last year, Pilgrim experienced an automatic shutdown the NRC determined was from human error. The NRC gave the plant a “white” finding related to the May 10 unplanned shutdown, known as a scram.
In November, the plant shut down while at reduced power because a valve was inoperable. The plant shut down again in December so plant workers could repair a leaking safety relief valve that helps control steam pressure at the facility.
Despite these problems, overall the 40-year-old plant operated safely in 2011, according to the NRC.
Opponents, however, continue to argue the plant should shut down for good because of safety and environmental concerns related to its operation.
Pilgrim’s license to operate expires June 8. Entergy has asked the NRC for a 20-year extension of the license. A decision on that request is pending.
Wednesday, March 14, 2012 @ 04:03 PM gHale
Apple released version 5.1.4 of its Safari web browser for Windows and Mac OS X, which addresses more than 80 vulnerabilities, while Firefox decided to wait until they want to evaluate a bit more.
The update also includes various stability and performance improvements as well as fixes for other non-security related bugs, Apple officials said.
A majority of the security holes closed in 5.1.4 were in the WebKit browser engine used by Safari. These include several cross-site scripting (XSS), cross-origin and HTTP authentication problems, as well as numerous memory corruption bugs that could end up exploited by an attacker to cause unexpected application termination or arbitrary code execution.
In addition, a recent issue, where officials said Google bypassed Safari’s privacy controls on cookies, was also a part of the upgrade. A bug in Safari’s Private Browsing mode that allowed page visits to record in the browser history when the mode was active also underwent a fix.
On Windows systems, the browser update improves domain name validity checking in order to prevent attackers from using look-alike characters in a URL to visually spoof a legitimate domain and direct users to a malicious site. Mac OS X systems did not have this issue.
Safari 5.1.4 is available to download for Windows XP or later, and Mac OS X 10.6 and 10.7. Alternatively, Mac OS X users can upgrade to the new version via the built-in Software update function. All users should upgrade as soon as possible, Apple officials said.
Meanwhile, the Firefox team said they are postponing the release of Firefox 11, originally planned for early this week, because of a security report the team wants to evaluate to make sure the issue will not impact their code. Jonathan Nightingale, Mozilla’s Senior Director of Firefox Engineering, also gave Microsoft’s monthly Patch Tuesday security update this week as a reason to hold back.
Nightingale said there is no reason to expect any issues, but they would rather ship Firefox 11 after they evaluated the Microsoft updates as they have “interacted badly” with Firefox before. Firefox plans out releases far in advance, in accordance with the changes Mozilla enacted with its development cycle last year.
It is notable it decided to halt the release of Firefox 11 this close to the planned date. At this point, no one will say if the delay relates to Firefox’s fall at last week’s Pwn2Own contest, but the vulnerability report is coming from ZDI (Zero Day Initiative) who organized the Pwn2Own competition.