Okay, some of those details help. I'm still guessing a bit blindly. What kind of assets are in your scene -- modeling assets, rigs, effects? Do you have a lot of construction history, deformers, dynamics (cloth, hair, MASH), etc?
It sounds like the file itself isn't holding much data, but that there is some part of the scene that requires evaluation when it's opened. If I create a massively-dense sphere, but put a bend deformer on it, the mesh doesn't need to get stored in the scene -- it is just evaluated. If I deleted the construction history and saved it, the file would be much larger, but it would likely open with less CPU usage. (And faster, as long as the disk is faster than the CPU computation would have been.)
Maya loads itself, initializes its UI (Outliner, shelves, etc), then tries to draw the viewport, which triggers evaluation of the construction history, which can indeed take a while.
It sounds like it's either hung infinitely on your Macbook, or it's taking inconveniently long (which are the same thing when you're trying to get work done). I have a 6MB file that takes 15 seconds to open on a reasonably fast developer machine -- it would not be hard to make a scene that takes 15 minutes or longer while having a fairly small file size. If I delete the construction history in my scene, the file becomes 2GB, but only takes 10 seconds to open.
So, let's focus on some steps to move forward. Since you have an alternate computer that can open your file, you have some options. Let's do some experiments to see which ones work and might give you pieces to work from more sustainably. Make a copy of your original scene file.
- On the PC, open a copy of your scene delete the construction history. Save it out, and try opening on the Macbook. This might be a larger scene, but it may load more successfully.
- On the PC, open a copy of your scene, and export pieces into smaller Maya scene files. Try opening those on the Macbook.
- If there are some part of your scene that you won't be editing, split those out into separate files and just reference them in. Save your file with those references unloaded by default, then you load them only when you need them instead of all in one giant evaluation at file load time.
If I'm wildly wrong and it's some kind of GPU issue, we can try other things. I'm hoping it's not Mac specific, because that's not my specialty.