It’s been a great winter for beautiful skies in south Burnaby, BC, ranging from inspiring to moody. Here’s a shot taken from Taylor Park during a one-hour ramble on south slope trails.
All posts by Paul Cipywnyk
Marauding Merganser
I watched this common merganser swim in the overflow pond and the sediment pond in the Byrne Creek artificial spawning habitat in SE Burnaby, BC. Don’t see these in Byrne that often.
After awhile I guess it had enough of being observed and flushed spectacularly, zooming right over us. I whipped my wee Canon pocket camera up and got this shot full of motion and blur, but I kinda like it!
Too bad I didn’t have a much faster DSLR at hand…
New Westminster BC Quay
Lovely sunny day for a walk along the quay.
Eagle, Wintry Skies, Crescent Beach, BC
A chilly beach walk at Crescent Beach, South Surrey, BC.
Bald Eagle
Frosty Walk along Byrne Creek, Burnaby, BC
Enjoyed a frosty loop of Byrne Creek in SE Burnaby, BC, this afternoon.
Cloud Show in South Burnaby, BC
All shot with my pocket Canon Elph 520HS from the Market Crossing parking lot during a run for groceries.
Rice Lake, North Vancouver, BC
A wee bit of snow was dusting the foliage as we took a loop around Rice Lake this afternoon.
Windows 10 Box Runtime Broker Memory Issue
My Windows 10 tower computer was feeling sluggish, and the HD light was indicating constant disk activity. New browser windows were very slow to open, and even the keyboard was noticeably slow to respond.
I fired up Task Manager (Control-Alt-Delete then click Task Manager) to see what was using the most CPU and memory.
I saw that a Windows process called Runtime Broker was using a whopping 9 GB of my 16 GB of memory, and that figure kept steadily rising. A little poking around online showed that this process controls Windows Apps and Tiles. I don’t use any Tiles. Some sites also said there was a known memory leak associated with Runtime Broker.
Some sites suggested going to Windows > Settings > System > Notifications & actions, and turning off “Show me tips about Windows.” I tried that, rebooted, and Runtime Broker still began steadily gobbling up more and more memory.
I went back to Notifications & actions and turned off all Notifications. Rebooted, and Runtime Broker has been holding steady at about 0% of CPU and 5.7 MB of memory used.
My machine feels snappy again, with new browser windows popping and the keyboard response back to normal.
So far I haven’t run into any functionality issues by turning all Notifications off, but I hope MS fixes this, because it would be nice to have some of them back.
UPDATE: Runtime Broker is now restarting itself, gradually eating up memory, shutting itself down, restarting itself…. Crazy. But at least the memory used values seem to top out at under a GB before it shuts down and restarts.
UPDATE: Seems to have settled down now…
UPDATE (12/24): Nope, has not settled down. Sigh…
Upgrading Photo Drive
I take lots of photos, so I have a second hard disk in my main computer dedicated to photos and videos. The other day I noticed that the 2 TB drive was down to only 9 GB free! That was a shock, considering that’s well less than one 32 GB card in one of my DSLRs.
Upgrade time. I had to move those 189,330 files in 2,523 folders onto a larger drive.
I have plenty of drives around that I use for backup in a couple of HD “toasters” — USB 3 docks that you can hotswap SATA drives in and out of. So I popped a 3 TB drive into a dock, and copied all those files over to it.
That done, I opened up the tower computer, pulled the old 2 TB D: drive and installed the new 3 TB drive. I used the Disk Management tools to rename the new drive to D:, so that my photo programs find it.
Worked great, and I now have nearly a TB of free space.
I have two NAS (networked attached storage) devices but use them only for backup. I like having my photos on a secondary internal HD for fast access.
Is Editing a Deadly Profession? My Latest Editors Canada Blog Post
Click here to read my latest blog post for The Editors’ Weekly, the official blog of Editors Canada, the freshly branded Editors’ Association of Canada.