. A 150-foot section of Kalifornsky Beach Road near Kasilof was damaged in the magnitude 7.1 earthquake that struck Southcentral Alaska at 1:30 a.m. Sunday. (Photo courtesy of Jenny Neyman, KDLL Kenai)Though one lane of Kalifornsky Beach Road was still open to traffic Sunday afternoon, many drivers heading between Kenai and Kasilof stopped of their own volition. They wanted to see the gaping cracks in the pavement that occurred when a magnitude 7.1 earthquake hit Southcentral Alaska around 1:30 that morning.James Benson, of Soldotna, and his daughter, Ali, were part of the steady stream of people marveling at the shattered road. “Yeah, we had to come out here and check it out,” Benson remarked. A crack runs about 150 feet through the northbound lane, spidering into fissures that extend laterally down into the snowy marshland off the side of the road. The force of the quake split the road near its center, and the shoulder side of the northbound lane sloughed away and sank up to a foot and a half. The fissures measure as little as inches across to more than a foot wide, with depths up to about 10 feet.The Alaska Department of Transportation and Public Facilities closed the northbound lane and marked the area with caution signs and cones Sunday morning. Spokesperson Shannon McCarthy said DOT plans to send a work crew Monday morning. She explained, “We’re going to have our maintenance crews get in there and make a temporary fix tomorrow so we can open it to two-lane traffic. What they’ll do is they’ll grind up the broken-up pavement and they’ll bring in D1, which is a type of gravel, and smooth it out so that both lanes are usable.”Crews will repave the road after the weather warms up this summer. During the temporary repairs, one lane of traffic will remain open as much as possible.On Sunday, drivers were getting through the one-lane section without the help of flaggers, though most stopped on the shoulder of the road anyway to take a closer look. Cameraphones were at the ready to snap pictures of the cracks, and a drone camera buzzed overhead. Smalltalk was all on the same subject — the earthquake.Deb Hartley, of Soldotna, had just finished walking the family dog when her husband, Rick, shouted to her as the shaking started. Hartley recalled, “I just walked in the house and all of a sudden he goes, grab the TV because it hit not 30 seconds after. I’ve got the dog in one hand and I’m holding the TV. But we didn’t lose anything. There was no damage to the house, so it was great.”James Benson takes pictures of his daughter Ali, posing in a crack in the pavement of the northbound lane of Kalifornsky Beach Road on Sunday afternoon. The Alaska Department of Transportation and Public Facilities will start repairing the road Monday. (Photo courtesy of Jenny Neyman, KDLL Kenai.)10-year-old Ali Benson was posing for pictures for her dad to send to her grandmother. James Benson joked that, “This is what Alaskans do for fun.” Ali was marking the occasion by taking home a few keepsakes, clutching a grimy chunk of asphalt under each arm, one with bits of yellow centerline paint still showing. James called it her “souvenir from her first earthquake she remembers.”Ali slept through half the earthquake until her dad woke her up.“I grabbed her and we just headed for the front door, kind of half in, half out of the house,” James said.James remembers being in Fairbanks when a magnitude 7.9 quake jolted Interior Alaska in November 2002. He said, “It was almost fun, but this one last night was violent. Our house was moving 3 feet. We were bouncing going down the hall.”McCarthy said the damage to K-Beach Road is similar to the cracking that occurred on the Richardson and Glenn highways in the 2002 quake. “Our roads, because they’re made to be stiff, when an earthquake comes along they’re like any other structure, they can be susceptible to movement. It can happen on literally any road, if you have a big enough quake with enough movement, it can occur almost anywhere,” she explained.DOT crews were busy throughout the night checking bridges on the Kenai Peninsula, in Anchorage and the Matanuska-Susitna area, and again Sunday during the light of day.McCarthy explained “They’re looking for anything unusual, anything that happened that’s new that would indicate a problem. Bridges are engineered specifically to take this kind of abuse from an earthquake but we want to let people know that we do inspect within 24 hours of an event.”McCarthy said that all bridges passed inspection.
Broken Malwarebytes update causes high RAM and CPU usage by Martin Brinkmann on January 28, 2018 in Internet – Last Update: January 28, 2018 – 44 commentsUsers of Malwarebytes, a popular security solution for Windows, reported on Saturday that the software’s RAM usage and CPU utilization was going through the roof.One user published a screenshot that showed the Malwarebytes Service process using more than 19 Gigabytes of RAM, and others soon chimed in and revealed that Malwarebytes used a lot of RAM and CPU on their devices as well.Some users reported even that some protective modules, Web Protection and Real-Time Protection would not turn on anymoreMalwarebytes Premium and Premium Trial versions on all supported versions of Windows were affected the most. It is unclear at this point in time whether Malwarebytes Free systems were affected as well.Affected users ran Malwarebytes Premium version 22.214.171.1243 with component package 1.0.262 and update package 126.96.36.1998.Tip: You can verify the program, component and update package versions by going to Settings > About in the Malwarebytes application.Malwarebytes released an update shortly after first reports appeared on the company forum. Update package 1.0.3799 was distributed through the application’s automatic update system. It turned out however that the update did not resolve the issue for users.Malwarebytes users experienced high RAM and CPU usage even after installation of the update on their devices and rebooting the machines.Malwarebytes issued another patch, which updated the update package to version 1.0.3803. This time, users reported that the patch seems to have fixed the issue on their machines.It needs to be noted that it is required to restart the system after update installation. Restarting Malwarebytes won’t do the trick. Some users reported that they had to restart the computer multiple times.Malwarebytes staff suggests that users turn of Web Protection, run a check for updates and restart the PC afterward if the issue is not resolved automatically.Malwarebytes CEO Marcin Kleczynski published an official statement on the issue on the Malwarebytes forum. Kleczynski explained that a malformed protection update caused the issue. The client could not process it correctly which caused the high resource usage on customer devices and protection issues.In short: make sure that the update package version is at least version 1.0.3803. If it is not, check for updates to install the most recent update package version and restart the computer afterwards to complete the installation.Closing WordsSome users thought that Malwarebytes had been compromised, especially since some protective modules would not stay on or could not be turned on at all. Malwarebytes reacted quickly to the issue but it still took them two tries to get it right.Now You: Were you affected by the issue? (via Neowin)SummaryArticle NameBorked Malwarebytes update causes high RAM and CPU usageDescriptionUsers of Malwarebytes, a popular security solution for Windows, reported on Saturday that the software’s RAM usage and CPU utilization was going through the roof.Author Martin BrinkmannPublisher Ghacks Technology NewsLogo Advertisement