09-03-2018 08:41 AM
Here's a "me too" post.
I'm using Mojave beta and thus am aware that stuff may break and that in my case it's most probably a Mojave change - it worked on the first betas, but now on the latest beta, after vacation, it always crashes right after showing the list of images, before the thumbnails are rendered.
I'm posting this "me too" because, as stated above, the dialog to upload the crash dump is not working. I'm now curious how GoPro is really intending to fix the crash when they're not even getting the information about what crashed.
Please do fix the crash dump upload ASAP so at least you do know what's crashing, and then after you know what's crashing, then you can fix it.
Unless you already know what the problem is, and have just disabled the crash upload service.
Either way, I see other people with the exact same crash and not using Mojave 10.14. Some even using 10.12, so I'm now in doubt if this could be some issue on macOS side, introduced both on 10.13.6 official and Mojave 10.14 beta.
The App really needs to be improved. It's umbeliavable that it's easier and faster to do something directly on the iPhone than on a 3-4K powerful Mac hardware.
2018 MBP 15, Mojave beta 18A377a, Fusion 1.2, all as up-to-date as possible.
09-03-2018 08:47 AM
Thank you for the feedback, @davipt. We are submitting this in addition to the details that we have already sent to the team. Please continue to watch out for updates. Best regards!
09-04-2018 06:00 AM
One additional piece of information, but I'm still not 100% sure about this and will do some more tests later, maybe only over the weekend.
One difference for my previous usage of the app is that before I was only saving JPEG files - used the Fusion mainly to capture 1 photo/second sequences to upload to Mapillary (plus some test videos) and for Mapillary I needed a lot of space, thus JPEG was enough.
During the last weeks, on vacation, I've tried some night photos, and thus enabled the whole set of RAW + ProTune.
If I pick my files and select only the JPEGs (front and back), without the RAW companion file, the app no longer crashes, or at least it didn't the three times I tested (hence why I need to test it further).
So, simple words, the crash *may* be related to RAW photos and to the processing of the GPR files.
If anyone could also test this, it could help us all. Pick your files and dump into a folder only the JPEG files (FRONT and BACK), without the GPR files. See if the Fusion App still crashes when trying to render the thumbnails.
This test did not include the videos though, so there's still a remote chance that it may be a video that is crashing the app. Probably not because when my app crashes, it's already showing the slots for my content, and the crash is about the time the first thumbnail should appear, and most of my files are photos.
Hope this helps.
09-07-2018 07:34 AM
Appologies but it is *not* about the raw images. I can only test this more thouroughly during the weekend. This is something about load - too many media files being processed. What I did was splitting my media (just 20GB, maybe 200 pieces of media, maybe 10 videos, everything else photos, I'll confirm later) into individual days, where each day would then have maybe 30 photos and 1 or 2 videos. With these, even though the photos are RAW and have the GPR on the folder, the app worked without crashing.
What I now need to test is if there's any corrupted file that makes it crash, or if there's some kind of limit that puts too much load and crashes. Maybe something like having more than 2 videos, or more than 20 photos.
One thing I noticed is that the Fusion app takes the Mac GPU to the limit, filling up all memory and most GPU usage, to the point that macOS becomes laggy and the mouse becomes jumpy. This was unberable on my previous MBP 15 with the Intel Pro integrated GPU (the minimum hardware), and was one of the reasons that made me upgrade to the MBP 2018 (pre refresh) with the proper GPU. Still with 3K€ of machine, the machine is laggy. I've opened a bug on Apple because the system shall not be affected by any app, but I'm mentioning this because *maybe* the Fusion app is trying to process *all* media in paralel, without some kind of limited queue, and when all this media is thrown into the GPU, Mojave's new GPU "protection" may be killing the Fusion app.
Still, notice to everyone else, please try to run the app with just a couple dozen media files and see if the app handles it.
09-11-2018 09:19 AM
Continuing my saga, I can now reliably crash the app in two situations:
- trying to load hundreds of files, even if most of them are photos, crashes the app. I still suspect this is caused by the GoPro app trying to allocate too many resources on the GPU. I'm using iStats Menu, and even when just trying to generate the thumbnails, the GPU memory is 100% occupied, and the whole system is laggy - even the mouse cursor is not smooth and jumps around. Independently of GoPro pushing the GPU to the limits, macOS shall not become laggy, and probably after my initial bugreport into Apple, macOS may not be trying (and failing) to throttle the usage, and eventually somewhere it returns something unexpected to the Fusion app, and the app crashes.
The solution is to do the processing in smaller batches. Even something like a dozen videos with about a minute may take several hours to process, so just get used to the fact that post processing is gonna take days, and don't try to do everything at the same time.
- the second reason, in my case, that crashes the Fusion mac App, not related to quantity, is a video that got corrupted. While recording, the Fusion gave me an error on SD2, probably due to excessive shaking of the camera, and taking the SD card out and back in, the camera said something like "recovered video". The video is there, and it just seems to lack the thumbnail. Trying to play it on the iPhone / iPad seems to work - at least it plays the first seconds. Haven't tried to render it on the mobile. However, trying to load this video on the Fusion Mac app will make the app crash right away. I'm pretty sure it's not just the lack of the THM file that crashes it. Probably the MP4 of the second camera got corrupted at the end, maybe even got different time length than the first camera. That's okish. We just need to assume that if the camera crashes or the SD gives some error, the recording may be lost.
The solution is to pick the original files and copy them one by one (the whole group of BACK and FRNT and all extensions), and try to identify if there's a particular file that crashes the app, and ditch that file.
09-11-2018 12:32 PM - edited 09-16-2018 02:10 PM
Great input, @davipt. Thank you for sharing these helpful information on preventing Fusion Studio crashes. While importing media into the GoPro Fusion Studio app, a red bar appears at the top of the window with an error message and code displayed. The error codes specify the source of error, say if the media is too short, or if the decoder is not able to seek the beginning of a video. Do you recall ever seeing such a notification?