INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Crash  (Read 4033 times)

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Crash
« on: December 04, 2019, 12:16:48 am »

HI,
I recently had to replace the harddrive on my 2009 iMac. 
After a restore from an old Time Machine backup from 2016 and an update its now back to High Sierra and I reinstalled the most recent build of MC 25 from JRiver site,  Purchase key installed fine.  But now the app crashes upon startup.  Not even enough time to activate logging.
I pulled over the JRiver docs from a recent backup (MC 23, 24 & 25) but no change.

Any suggestions?

Thanks. J
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71338
  • Where did I put my teeth?
Re: Crash
« Reply #1 on: December 04, 2019, 07:11:50 am »

Turn off auto-import.

Make sure you're using the latest build from the top of this board.
Logged

normd

  • Recent member
  • *
  • Posts: 31
Re: Crash
« Reply #2 on: December 08, 2019, 03:42:49 pm »

Why turn off auto=import? It seems to me that is a key feature of the program.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7363
  • The color of Spring...
Re: Crash
« Reply #3 on: December 08, 2019, 03:56:42 pm »

Because if it stops crashing after turning off auto-import, chances are you have bad files, which are causing the crashes.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

normd

  • Recent member
  • *
  • Posts: 31
Re: Crash
« Reply #4 on: December 08, 2019, 04:41:31 pm »

That seems exactly to be my problem. I am trying to load in a bunch of new music and I was experiencing crashes so bad I had to manually restore my library. Any suggestions on how to identify a "bad file"?
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Crash
« Reply #5 on: December 08, 2019, 06:36:10 pm »

Any suggestions on how to identify a "bad file"?

Turn on logging in MC, if you can before a crash happens. The log will shows which file was being imported when MC crashed. If you can't turn on logging before a crash, move the most recent files you added to a location Auto Import doesn't watch, then run MC and turn on logging. Then move the files back, or use the "Import a Single folder" function to try to import the suspect files, and if you get a crash, restart MC and look at the logs.

There are also tools to identify and fix corrupted audio files. Google "check audio files for corruption" or similar. Just be careful about which solution you select, if using a third-party tool.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #6 on: December 11, 2019, 02:45:31 am »

I never stated anything about auto-import.  It was crashing within seconds of startup, without enough time to change any settings.

Since my original posting, I had several issues going on with the Mac so I wiped it clean and installed a fresh OS instead of using the time-machine restore as before.

I've now reinstalled MC with the most recent stable build.  Same problem, but now it takes a few more seconds before crashing.
If the app didn't crash before my reinstall, why would a corrupt file cause out after a reinstall?

I'm assuming the SMART functions of MC are automatically connecting to my NAS and loading the music library stored there, am I correect? 
Again, the same NAS library is currently loaded in my MacBook Pro.  It loads and plays fine, no crashing.   

Because I am unable to get the app to stay up enough time to turn on logging nor turn off auto import, I have attached a text version of the info provided in the Apple crash report if it helps.

Thanks. J
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7363
  • The color of Spring...
Re: Crash
« Reply #7 on: December 11, 2019, 02:54:08 am »

Those type of crashes have been happening lately, mostly due to issues with trying to get MC notarized for macOS Catalina and Xcode 11 causing issues.

Looks like the latest build was "downgraded" to 25.0.113 because of all those issues: https://yabb.jriver.com/interact/index.php/topic,123301.0.html

If you're running Catalina, do mind the known issues part.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2023 Update (23H2) 64-bit + Ubuntu 24.04 LTS Noble Numbat 64-bit | Windows 11 2023 Update (23H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/256GB NVMe SSD)
JRiver Media Center 32 (Windows + Linux) | Topping D50s DAC | Edifier R2000DB Bookshelf Speakers

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #8 on: December 11, 2019, 03:03:06 am »

Was able to move fast enough to turn off auto import and turn on logging.  Attached is the log.  I don't see anything regarding specific files.

Also, I don't know if this is related at all, but when I added MC to the approved list for Accessibility in System Prefs/Privacy.  Next to the MC logo where the app name list, it has "package installer" in place of Media Center 25.
Logged

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #9 on: December 11, 2019, 03:04:46 am »

Not on Catalina.  This iMac 2009 only supported up to High Sierra.
Logged

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #10 on: December 11, 2019, 03:13:56 am »

Just installed MC 25 .113 and immediately before even opening the app, my still open window System Pefs Accessibility changed the app name from "package installer" to Media Center 25 but alas...it just crashed again.

J
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Crash
« Reply #11 on: December 11, 2019, 06:48:11 pm »

I am no longer a Mac user so I don't look at Mac logs usually. But I did this time.

The System Info file looks truncated. But maybe that is normal on a Mac.

There is no mention of a crash in either the Log.txt or Previous log.txt files. Did MC really crash, or just stop responding?

It appears that you have imported files from a DLNA Server rather than using a URI to a NAS/File Server, or a mapped drive or resource. This is not recommended.

Worse, it appears that the IP Address of your NAS/File Server changed between the Log.txt and Previous log.txt files, which means MC would have been trying to fix broken links to point to the new IP Address. You really should use IP Address Reservation in your router for the NAS/File Server if you haven't already. I could be wrong in my conclusion that the IP Address is changing, but it looks like it.

I don't see anything regarding specific files.

How about all of these records, from the Previous log.txt file, which was when Auto Import was still turned on?

0039336: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/124686.wav Mode: 0  Track: 0
0039336: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/124687.flac Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/124688.flac Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/124689.wav Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/124690.flac Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/128613.m4a Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/128614.flac Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/122749.m4a Mode: 0  Track: 0
0039337: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/128615.flac Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/150451.flac Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/128616.flac Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/128617.flac Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/122751.m4a Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/122753.m4a Mode: 0  Track: 0
0039338: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/122754.flac Mode: 0  Track: 0
0039339: 123145414729728: Database: CMediaDatabase::RemoveFileAbsolute: Filename: http://10.0.0.25:50002/m/NDLNA/122755.flac Mode: 0  Track: 0

Those are references to files on a DLNA Server, being served to MC.

Again, the Previous log.txt file appears truncated, with no reference to a crash. It just died in the midst of an overwhelming number of "RemoveFileAbsolute" records.

I think you need to explain a lot more about the network and hardware environment you have in place.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #12 on: December 15, 2019, 05:22:51 pm »

I'm starting to think a change in my NAS could be the causing an issue.   I think they did an update a couple of says ago.  I've noticed when I view my audio files via the Yamaha Music Cast app, the files are organized differently. Now when viewing files by artist, the artist names are subgrouped/folfered alphabetically by first leteer in name.  Where as before it was just an alphabetical list of artists.
And now MC on my MacBook Pro is crashing on startup as well. Though neither are set to Auto Update the library. 

Am I correct in thinking the SMART function of MC auto updates the libraries of network attached DLNA devices?

My network setup is:
- MC running on either iMac (mid 2009) or MacBook Pro (mid 2012) (wired)
- Netgear R8500 router (DLNA management is disabled as it screwed with functionality) (wired)
- Synology NAS DSJ280 (wired)
- Yamaha - R3070 amp + RN303 amp X 6 (all wired)

all controlled by either iPhone or iPad running either the Music Cast app, JRiver remote app or both.

All functioned harmoniously til last week.  Audirvana crashes as well.  Only the Music Cast app functions as before.

If the NAS has reorganized the way it organizes the files, is that enough of a game changer to cause the MC crash?  Or is the large quantity of changes overwhelming MC?

PS - I've held off on installing the  recent MC update as I didn't want to put more in the mix.  Please inform if this could solve the issue and I will update. 

Thanks J
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Crash
« Reply #13 on: December 15, 2019, 07:09:58 pm »

It appears that you have imported files from a DLNA Server rather than using a URI to a NAS/File Server, or a mapped drive or resource. This is not recommended.

It sounds like you are running a DLNA Server on your Synology NAS. That's fine, in that it allows you to connect the Music Cast App to that DLNA Server and play music directly. In that situation, MC isn't involved. Of course, if you had MC set up as a DLNA Server, the Music Cast App could probably connect to that instead of the NAS DLNA Server, and you will get better results.

But it sounds like you also have MC connecting to the NAS DLNA Server, and as above, that is not recommended. You should be pointing MC to the drives on the NAS and importing files directly from there. Now with a NAS DLNA update, things are broken, and not just MC.  If you hadn't had MC connecting to the NAS DLNA Server, MC would not have broken.

Post an image of your MC installation similar to the one I have below, which shows my MC installation connected to a BubbleUPnP Server running on my phone. That should confirm how you have MC configured, at least regarding the connection you are using.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #14 on: December 22, 2019, 01:42:25 pm »

OK.  So after installing the most recent MC 25 update, I restarted my iMac with Ethernet turned off.  MC didn't crash and I was able to delete the dynamic library then created a new library and pointed MC to the drives on the NAS as you suggested.  MC didn't crash but the entire library was duped, two of every track listed in file view.   MC was finding the DLNA server on my network and adding it on its own.  So I reconfigured the import options and deleted the directions to the three files on the NAS drives.   
MC played fine, found my zones etc.  (though it did yet again delete a good 40 minutes worth of a playing now I curated in the action window.   Double clicked the first track to start play (in View Playing Now) and the entire Playing Now playlist I curated vanished except for the first track which I clicked on.  And for some reason the recent Saved Playing Nows playlist hadn't been saving for about as long as I worked on creating it.  My most recent saved time was 40 minutes ago when I had a mere two tracks added.)

So I decided to try quitting MC and restart, perhaps the playing now list would reappear.  No luck, and now again, MC crashed about 30 seconds in.

As of this moment, I restarted MC and it has stayed up for the entire time Ive created this post... SO I don't know what the deal is.

I had to act fast in order to get the windows and grab a screenshot before MC crashed, and I notice the total number of files it states are in the DLNA server is not correct, its half that.  And there total size is not correct.  Its as if the server is almost empty.  And as of now 15 minutes past, still the size hasn't changed.

See attached shot.

Regards, J

'
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Crash
« Reply #15 on: December 22, 2019, 05:01:36 pm »

Oh Wow. So many issues from that one post. Some bullet points. Sorry, I'm going to be a bit harsh, as this is basic MC functionality that you don't seem to understand.

You may have deleted the Dynamic Library (CazatonikServ), but your image shows that it has re-appeared and you have loaded it again. Just because the Dynamic Library, which is the DLNA Server on your NAS, appears, doesn't mean you have to load it. Don't do that. The only way MC could have found your existing Zones, as you state it did, was if you had loaded the DLNA Server Library again, which had all you settings still in it.

Dynamic Libraries are supposed to re-appear when they are visible on the network, generally. There is no need to delete them. Just don't load them.

If you delete a Dynamic Library I expected that MC wouldn't show it again, excluding it in the future. I wasn't willing to test that on my system. But it seems that the Dynamic Library from your NAS has re-appeared. Maybe it does re-appear if it was the last Library you had open, and you had MC opening the last used Library on startup. Make sure that the setting "Options > Startup > Library > Always load default Library" is ticked so that the "Main" Library gets opened when you start MC. At least for now.

Removing folders to import from the Dynamic Library from the DLNA Server on your NAS as your image shows will do nothing, as MC isn't loading files from folders. It is loading files from the DLNA Server.

You said you "created a new library and pointed MC to the drives on the NAS". Where is it in that image? I only see the default Main Library, and the Dynamic Library from the DLNA Server on your NAS. Maybe you deleted the new Library you created instead of the Dynamic Library as you said.

I don't know why the entire Library was duped when you create your new Library, but given the other issues in play here, I suspect that you included two paths to the same files on the NAS, which will result in duplication of every track. If you added NAS folders to import from into the Auto Import settings in the CazatonikServ Library, then you effectively told MC to import all files from the DLNA Server, plus import all files from the NAS folders, which would, of course, duplicate every file.

Now if you have set the Main Library to load at MC startup, as above, make sure that Auto Import in the Main Library only points to each Base Path location on the NAS once. So if, for example, you have a drive of say "M:\" mapped to the location of "\NAS Name\Music" on the NAS, and all your music is under that location, just enter "M:\" as the folder to import from. You could also just put the URI address of "\NAS Name\Music" in Auto Import, and that would work fine. Just don't put both in there. If you have multiple locations on the NAS that have music stored in them, and they don't overlap, then put those multiple locations into Auto Import.

As you are now using the Main Library, rather than the Dynamic Library as previously, you will need to do all your setup in that Library again, including all your Zones, Custom Views (you could export those from the old Library and import then into the Main Library though), and so on. Is this a big problem? Do you have a lot of custom setup?



It is not Best Practice to spend 40 minutes building a Playing Now list of files to play. It is Best Practice to build a normal Playlist, which will be saved as you go, and then just add that Playlist to Playing Now when you are ready to start listening. If you want to listen as you build, just build a small Playlist first and add that to Playing Now, start playback, then build another Playlist to Add to Playing Now later when it is ready. Playing Now can easily and unintentionally be cleared depending on settings and how you use it.

However, you said that you curated this Playlist in the Action Window, which means that you were actually building a normal Playlist, and not building a list in Playing Now. Then you double-clicked on the first track in your new, probably unnamed, Playlist. Then MC loaded just the first track from your Playlist into Playing Now, and played it.

It sounds like you have the "Options > General > Behaviour > Double click" setting set to "Replace Playing Now (single)", so MC did just that. Change that setting to "Add to Playing Now (play now)", or something more appropriate. However, even with that setting set to "Replace Playing Now (single)", if you were actually working in Playing Now to add tracks to play, and double-clicked on the first file, MC would not have cleared Playing Now except for the first track. It would have started playing the first track and left all other following tracks. So I don't know what you did.

If you had double-clicked on the new Playlist you just created, even with the above "Replace Playing Now (single)" setting, MC would have loaded the whole Playlist into Playing Now and started playback.

The "Recent Playing Now's" Smartlist is only updated under certain conditions, such as when you replace a list in Playing Now with a new Playlist. But you weren't working in Playing Now anyway, so naturally there were no "Recent Playing Now's" to go back to and reload. There was, however, the new Playlist you were building in the Action Window. That would still have been there, ready to reload. It just probably had the default name of "New Playlist" because you didn't even realise that you were building a new Playlist. Do you see Playlists called "New Playlist" appear from time to time, and wonder where they have come from?

If the total number of files you have is actually around 33,363, then the 66,726 shown is the number of files MC saw when it had imported all files twice, as above. That number might not get refreshed until you reload the Library, although I think it does if you refresh the View. Or more likely you took that screenshot after deleting the NAS folders from the Auto Import configuration, but before you saved the changes and ran Auto Import. Nothing wrong there.

The "total size" as you call it, shown as "13.5MB in library", is not the size of all your media files, it is the size of the MC Library files. That is, the size of all the *.jmd and other files that make up the MC Library, which is an index of all the media files you have. Nothing wrong there.



I was going to say I don't know why the MC screen was frozen, but it appears that you have deleted that post, so I assume that it wasn't really frozen, but was just taking some time to update the Library from the NAS or something.

I think I covered everything.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

dichotomous1

  • Junior Woodchuck
  • **
  • Posts: 50
Re: Crash
« Reply #16 on: August 07, 2020, 11:59:51 pm »

I'm only just seeing this last response and to be honest, haven't even finished reading the post nor will.  Because the possibility of any helpful or intelligent content is cancelled out by the downright ignorant and rude suggestion as to what "best practices" are in regard to someone else's time prioritization, particularly a paying customer.  This is about software functioning properly, not how one chooses to utilize said software.  Not to mention said software has for years now contained buttons that have simply never functioned (ie one example off hand: changing skin color option on a Mac)  Perhaps consideration of critical thinking best practices is in order.   Seriously, check your ego.
Logged

RoderickGI

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 8186
Re: Crash
« Reply #17 on: August 08, 2020, 06:52:07 am »

 ;)  Good on you. "Cut off your nose to spite your face."

I said I was going to be harsh. You don't like it, fine. There was nothing nasty in my post, just facts and clarifications. Maybe a few queries.

If you bought a car, do you think it would be a good decision to drive it around everywhere in reverse, complain about visibility and top speed, and the defend that decision by saying how you choose to use the car shouldn't matter, it just should work?

Just for clarity, you don't pay me, and neither does JRiver. I'm just a user like you, and I was helping for free. Nothing. Nada. You aren't my paying customer. My ego is fine. Very healthy thanks.

Seriously, read through the thread from the beginning. You might understand the information flow better.
Logged
What specific version of MC you are running:MC27.0.27 @ Oct 27, 2020 and updating regularly Jim!                        MC Release Notes: https://wiki.jriver.com/index.php/Release_Notes
What OS(s) and Version you are running:     Windows 10 Pro 64bit Version 2004 (OS Build 19041.572).
The JRMark score of the PC with an issue:    JRMark (version 26.0.52 64 bit): 3419
Important relevant info about your environment:     
  Using the HTPC as a MC Server & a Workstation as a MC Client plus some DLNA clients.
  Running JRiver for Android, JRemote2, Gizmo, & MO 4Media on a Sony Xperia XZ Premium Android 9.
  Playing video out to a Sony 65" TV connected via HDMI, playing digital audio out via motherboard sound card, PCIe TV tuner

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 71338
  • Where did I put my teeth?
Re: Crash
« Reply #18 on: August 08, 2020, 07:03:08 am »

Not on Catalina.  This iMac 2009 only supported up to High Sierra.
This could be the root of your problem.  Apple is unfriendly in its inattention to backward compatibility.

I'm giving you a break from the forum for a few days.  You've resisted advice and been generally ungrateful for the considerable help you were given.

Personal remarks are very unwelcome.
Logged
Pages: [1]   Go Up