More > JRiver Media Center 31 for Mac

MC 31 Mac Activity Monitor Logs assistance

<< < (5/6) > >>

Maeghaus:
Brian, thanks for the logging suggestion. Jim, I have the Mac Dock auto-hide off (I think that's what you meant). I'm starting a log this afternoon (10/12/2023).

-- Tom

Maeghaus:
I created a Media Center 31 Mac log. I made additional ones, but they didn't reveal any major disk cache writing. Maybe it was the HEIC/HEIF files. I updated the Mac to Ventura 13.5.2 around the same time as MC Mac 31.0.59.

I reported that the last time I ran Media Center 31 on my Mac, the cache writing wasn't using up disk space as before. I see several reasons for that, but don't know which one corrected the problem. I'm inclined to think v.59 and restarting the Mac fixed it. I updated to MC Mac 31 v.71 this morning before running the tests. So far, I've run Media Center 31 for 90 minutes and the system is fine. I played music during the first log and opened Adobe Illustrator in the second, as a stress test along with memory hogs like Google Chrome Browser. I'm pleased the Mac is operating better.

The logs don't reproduce the problem, but I include them here for analysis. I did not upgrade to Mac OS Sonoma yet; I'm reviewing compatibility with programs I have.

-- Tom

Maeghaus:
Update on MC 31.0.71 Mac status: Left the program open after today's log tests. No issues and running fine after more than 9 hours. It seems Bob's HEIC/HEIF file analysis and the resulting bug fix solved my problems. I reported at first that it didn't work but that was before I restarted the computer.

I have an iPhone (14 Pro), and a few iOS versions ago Apple changed the preferred photo/video format to High Efficiency HEIC/HEIF, with JPG as backup. I thought I did not import HEIC/HEIF files into Media Center Mac but have all my Photos library under my MC Mac Images tab. When I did this, I don't recall but that's likely what started the disk cache writing issue in MC Mac 30 from the first build (30.0.18) back in October 2022.

I'm glad the team found out the solution. I wouldn't have realized that media formats would cause a memory write issue. That was good investigating!

-- Tom

EDIT: I just noticed that with this post I am now a World Citizen. I was a Junior Woodchuck for ten years (I only post when I have something definite to say). Going back to old threads might make me cringe but they are interesting. Learning how to edit an XML Playlist still helps. That's as close as I've gotten to programming. I leave that to you folks. -- T

bob:

--- Quote from: Maeghaus on October 12, 2023, 08:50:18 pm ---Update on MC 31.0.71 Mac status: Left the program open after today's log tests. No issues and running fine after more than 9 hours. It seems Bob's HEIC/HEIF file analysis and the resulting bug fix solved my problems. I reported at first that it didn't work but that was before I restarted the computer.

I have an iPhone (14 Pro), and a few iOS versions ago Apple changed the preferred photo/video format to High Efficiency HEIC/HEIF, with JPG as backup. I thought I did not import HEIC/HEIF files into Media Center Mac but have all my Photos library under my MC Mac Images tab. When I did this, I don't recall but that's likely what started the disk cache writing issue in MC Mac 30 from the first build (30.0.18) back in October 2022.

I'm glad the team found out the solution. I wouldn't have realized that media formats would cause a memory write issue. That was good investigating!

-- Tom

EDIT: I just noticed that with this post I am now a World Citizen. I was a Junior Woodchuck for ten years (I only post when I have something definite to say). Going back to old threads might make me cringe but they are interesting. Learning how to edit an XML Playlist still helps. That's as close as I've gotten to programming. I leave that to you folks. -- T

--- End quote ---
It's really because it ran out of system memory and was writing to swap which is on disk.

Maeghaus:
Bob, that's true. But I would like to hear the solution from your view. I am unfamiliar with what an image format and excessive memory usage have in common to cause what happened. I am always interested to learn. You mentioned a few target fixes.

-- Tom

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version