# Vuforia Model Tracking crashes ML2 - rebooting the whole device **URL:** \ **Category:** Vuforia Engine\ **Tags:** vuforia\ **Created:** [September 11, 2023, 4:16pm UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530 "2023-09-11T16:16:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Tom\_LEFX](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Tom\_LEFX](https://forum.magicleap.cloud/u/Tom_LEFX)\ **Post date:** [September 11, 2023, 4:16pm UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/1 "2023-09-11T16:16:12Z")
I got Vuforia Model tracking to work on the ML2 and now I am experimenting with different model/marker ideas. One thing I did was to 3d-scan an object and then created an advanced model target from it. It actually works - the object is being identified correctly and then tracked - for a few seconds. After about 15-20 seconds, the whole headset shuts down and reboots (Magic Leap loading bar etc.) The app reports this as an error before shutdown: **Autoconnected Player "Autoconnected Player" Vuforia Engine has stopped due to an error: The operating system has dropped the camera device used by Vuforia Engine** I'm running the following specs: **ML OS:** 1.3.1 (found 1.4.0 to be highly unstable, had crashes/reboots of the device every 15-20 minutes) **ML SDK:** 1.9.0 **Vuforia Engine:** 10.17.4 **Unity** : 2022.3.5f1 ---
**Author:** ![emichals](https://avatars.discourse-cdn.com/v4/letter/e/50afbb/32.png) [@emichals](https://forum.magicleap.cloud/u/emichals)\ **Post date:** [September 14, 2023, 4:58pm UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/2 "2023-09-14T16:58:29Z")
Hi, it sounds like it might be a device or OS issue. Can you confirm this is happening only with Vuforia and no other app that uses the camera? ---
**Author:** ![ejurinsky](https://avatars.discourse-cdn.com/v4/letter/e/8e7dd6/32.png) [@ejurinsky](https://forum.magicleap.cloud/u/ejurinsky)\ **Post date:** [September 14, 2023, 5:27pm UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/3 "2023-09-14T17:27:40Z")
@Tom_LEFX can you please pull and send us logs from the device? @etucker can help with that if you do not know how. ---
**Author:** ![Tom\_LEFX](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Tom\_LEFX](https://forum.magicleap.cloud/u/Tom_LEFX)\ **Post date:** [September 18, 2023, 7:50am UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/4 "2023-09-18T07:50:59Z")
Thanks for getting back to me and sorry for the delayed response. It has been a bit busy these days. I'll check the application again today and will try to pull logs after it crashed the device. Do I need to do something in particular to get logs from the device after a full crash? Or is it just a continuous logfile anyway? ---
**Author:** ![Tom\_LEFX](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Tom\_LEFX](https://forum.magicleap.cloud/u/Tom_LEFX)\ **Post date:** [September 18, 2023, 7:52am UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/5 "2023-09-18T07:52:09Z")
So far, it only happened with the Vuforia Model tracking. Vuforia image and marker track ran fine for longer time. I also tried ML Assist and it did not crash. (at least on 1.3.1 OS - 1.4.0dev1 crashes are frequent for me with many apps) ---
**Author:** ![Tom\_LEFX](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Tom\_LEFX](https://forum.magicleap.cloud/u/Tom_LEFX)\ **Post date:** [September 18, 2023, 2:41pm UTC](https://forum.magicleap.cloud/t/vuforia-model-tracking-crashes-ml2-rebooting-the-whole-device/2530/6 "2023-09-18T14:41:59Z")
I wanted to reproduce the issues today - but suddenly the app just does not want to crash the HMD anymore. Same app, same OS - only difference: It's about 7-8 degree colder in the room than last week. Could it have been a thermal issue? I hear (from the fan noise) that the model tracking seems to be quite compute intensive.