Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
2022/03/11 - Updated in #6 Status : Using virtual windows

------------------

While this may be difficult to understand or troubleshoot, I'll try to describe it as carefully as possible. Because of remote work, I wanted to add a Webcam to my Mac Pro 5,1 at home to handle any kind of voice or video conferencing.

I did buy the Webcam and it works fine, the system recognizes it correctly, both the microphone and the camera are plugged in and ready to use, and FaceTime works.

But after using Webcam, I realized something: the LINE app doesn't work on my Mac Pro 5,1 for voice or video calls, or to be precise, it crashes.

Yesterday I repeated the tests and finally I came to the conclusion that
1 - The problem is not related to Webcam, because Webcam works fine on other apps.
2 - With or without Webcam installed, LINE crashes the moment it make a voice/video call or receive a voice/video call using the LINE app.

Although not scientific, as a comparison, I add the USB Webcam on my 2019 MBP 16 and it works just as well, the LINE app works correctly, and as concluded earlier, it is really not related to the Webcam.

So now the problem is that my Mac Pro 5,1 can't use the LINE app to make or connect voice/video calls, and the moment it does, it crashes.

My Mac Pro 5,1 as follows.
macOS 10.15.7, RX560, system running on NVME SSD, using OpenCore (based on a package made by h9826790, but I forget which version)
LINE app is 7.7.0

I've attached a crash report, but really, it doesn't show any signs. does anyone provide some clues as to why the LINE app crashes on voice/video calls? It's possible to fix? Thanks any help.
 

Attachments

  • LINE_2022-03-09-175748_PorkdeMac-Pro.pdf
    113.9 KB · Views: 109
  • LINE_2022-03-09-175748_PorkdeMac-Pro.crash.zip
    28.8 KB · Views: 100
Last edited:

tsialex

Contributor
Jun 13, 2016
13,461
13,613
This is the reason:

Code:
Termination Signal: Termination Reason: Terminating Process:
Illegal instruction: 4

Line app is using an instruction that your Xeon don't have.
 
  • Like
Reactions: ddhhddhh2

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
This is the reason:

Code:
Termination Signal: Termination Reason: Terminating Process:
Illegal instruction: 4

Line app is using an instruction that your Xeon don't have.

I see, it looks like this is hopeless on Mac Pro 5,1, thank you very much for your help, I understand, thanks again.
 

Dayo

macrumors 68020
Dec 21, 2018
2,257
1,279
You didn't mention whether you are running the same MacOS version on both machines you tested. Your MP51 is on 10.15.7 but was the other the same?

The Illegal instruction: 4 error appears to usually result from program compilation time bugs and you might want to flag this to the developers.
 
  • Like
Reactions: ddhhddhh2

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
You didn't mention whether you are running the same MacOS version on both machines you tested. Your MP51 is on 10.15.7 but was the other the same?

The Illegal instruction: 4 error appears to usually result from program compilation time bugs and you might want to flag this to the developers.

Yes, both of my test Mac are running the same macOS, both 10.15.7. I have now provided a bug report to LINE for problem reporting, although the hardware specification of cMP is "a bit old", and given the percentage of users, it might be too much to ask the developers to find possible causes, so I wouldn't expect too much.
 

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
Current status update:
Yesterday I thought again that I wanted to test, although it may be due to LINE calling the CPU instruction set, but what if I use Virtual Windows? Since the instruction set may be virtualized, I'd like to know if it's possible.

macOS 10.15.7, Parallels Desktop 15, Windows 10, LINE 7.7.0 (Win)

After testing, making a voice/video call -> OK, answering a voice/video call -> OK, this is a really weird situation. In short, under macOS, this feature of LINE does not work, no matter if it's a CPU instruction set call or a compilation error, but with virtual windows, everything is fine.

Since virtual windows is always on whenever this cMP 5,1 is powered on, for me it's just a matter of having the LINE app always in windows, at least until LINE fixes the problem, so I can use it without too much inconvenience.

As feedback, if anyone has a similar situation, perhaps you can take a look.
 

tsialex

Contributor
Jun 13, 2016
13,461
13,613
Current status update:
Yesterday I thought again that I wanted to test, although it may be due to LINE calling the CPU instruction set, but what if I use Virtual Windows? Since the instruction set may be virtualized, I'd like to know if it's possible.

macOS 10.15.7, Parallels Desktop 15, Windows 10, LINE 7.7.0 (Win)

After testing, making a voice/video call -> OK, answering a voice/video call -> OK, this is a really weird situation. In short, under macOS, this feature of LINE does not work, no matter if it's a CPU instruction set call or a compilation error, but with virtual windows, everything is fine.

Since virtual windows is always on whenever this cMP 5,1 is powered on, for me it's just a matter of having the LINE app always in windows, at least until LINE fixes the problem, so I can use it without too much inconvenience.

As feedback, if anyone has a similar situation, perhaps you can take a look.
Windows have a broader compatibility than macOS.

Apple today supports late-2013 Mac Pro and 2014 Mac mini as the baseline - both support AVX and other instructions like RDRAND or XSAVE that MacPro5,1 Xeons simply don't have - and developers are slowly starting to make use of these instructions. Because of that, several apps don't work anymore with MacPro5,1, a famous example is VMware Fusion after Catalina.
 
  • Like
Reactions: ddhhddhh2

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
Windows have a broader compatibility than macOS.

Apple today supports late-2013 Mac Pro and 2014 Mac mini as the baseline - both support AVX and other instructions like RDRAND or XSAVE that MacPro5,1 Xeons simply don't have - and developers are slowly starting to make use of these instructions. Because of that, several apps don't work anymore with MacPro5,1, a famous example is VMware Fusion after Catalina.

Thank you for sharing, I really benefit a lot. In fact, the speed of this cMP is really not too slow, and the speed of compiling angular is even faster than the "hot" M1 air. But the incident I encountered this time, I began to seriously think about the possibility of replacing the desktop at home. I think, as long as I wait until the windows arm is completely stable on AS mac, I may be able to fully switch.
 

tsialex

Contributor
Jun 13, 2016
13,461
13,613
Thank you for sharing, I really benefit a lot. In fact, the speed of this cMP is really not too slow, and the speed of compiling angular is even faster than the "hot" M1 air. But the incident I encountered this time, I began to seriously think about the possibility of replacing the desktop at home. I think, as long as I wait until the windows arm is completely stable on AS mac, I may be able to fully switch.
Even with all the problems, my MacPro5,1 is my main Mac and will be for some time since the cost of upgrading everything is insane at the moment. It's not just cost of the Mac Pro upgrade, that I'll have to upgrade to a Mac Studio or something else, but the cost of a NAS to move all my storage, new displays and all the little things that we forget.

So, until I get at least a good NAS to move from my 5-disk eSATA box and all my internal disks, I'll be chugging on with my mid-2012 Mac Pro.
 
  • Like
Reactions: ddhhddhh2

ddhhddhh2

macrumors regular
Original poster
Jun 2, 2021
245
387
Taipei
Even with all the problems, my MacPro5,1 is my main Mac and will be for some time since the cost of upgrading everything is insane at the moment. It's not just cost of the Mac Pro upgrade, that I'll have to upgrade to a Mac Studio or something else, but the cost of a NAS to move all my storage, new displays and all the little things that we forget.

So, until I get at least a good NAS to move from my 5-disk eSATA box and all my internal disks, I'll be chugging on with my mid-2012 Mac Pro.

I have a similar situation, my cMP 5,1 has a lot of data, 3 HDDs, 1 SSD, 2 NVME, after several upgrades over the years, it looks like it's at the end of its rope.

Although the computing speed is not as fast as today's computers, but really, it's not too slow, and I have a quirk, I don't like to use my laptop as a desktop, I only use my laptop when I go to the office or outside, in the office I will use my laptop as an external monitor, as a dual screen. But at home, I mostly use the cMP, and it gives me peace of mind that I have enough memory to do a lot of multi-tasking.

I think I will probably use it until it breaks down before I replace my main desktop at home, and I still need the stability of windows, which is important to me.

But there's no denying that the new Mac Studio has a "relatively reasonable" price that reminds me of the old G3, G4, G5 days.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.