[Galaxy Note 4 Q&A, Help & Troubleshooting] jult:
I'm running the latest eRobot rom using H-vitamin kernel, android MM on Exynos N910C.

Everything works smooth and fast, but when I start the YouTube app and then as soon as I press the playbutton it immediately drops out and reboots.

Here's what aLogrec catches of that moment;

10-14 23:45:52.745 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:52.750 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:53.735 4845 4845 D StatusBar.NetworkController: refreshViews connected={ wifi } level=1 combinedSignalIconId=0x7f02070d/com.android.systemui:drawable/stat_sys_wifi_signal_3 mobileLabel=Hi wifiLabel="Vlinderbos" emergencyOnly=false combinedLabel="Vlinderbos" mAirplaneMode=false mDataActivity=0 mPhoneSignalIconId=0x7f020610/com.android.systemui:drawable/stat_sys_signal_1_auto_rotate mQSPhoneSignalIconId=0x7f0201b6/com.android.systemui:drawable/ic_qs_signal_1 mDataDirectionIconId=0x0/(null) mDataSignalIconId=0x7f020610/com.android.systemui:drawable/stat_sys_signal_1_auto_rotate mDataTypeIconId=0x7f0204c1/com.android.systemui:drawable/stat_sys_data_connected_4g mQSDataTypeIconId=0x7f0201bc/com.android.systemui:drawable/ic_qs_signal_4g mNoSimIconId=0x0/(null) mWifiIconId=0x7f02070d/com.android.systemui:drawable/stat_sys_wifi_signal_3 mQSWifiIconId=0x7f0203ca/com.android.systemui:drawable/qs_tile_wifi_signal_3 mWifiActivityIconId=0x7f0206c3/com.android.systemui:drawable/stat_sys_signal_inout mBluetoothTetherIconId=0x7f0206ec/com.android.systemui:drawable/stat_sys_tether_bluetooth
10-14 23:45:53.735 4845 4845 D StatusBar.NetworkController: refreshNwBoosterIndicator - setNWBoosterIndicators(false)
10-14 23:45:53.740 4845 4845 D StatusBar.NetworkController: refreshNwBoosterInd--------- beginning of system
10-14 23:46:32.585 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{cf5961f 6440:com.samsung.android.coreapps/5011}
10-14 23:46:32.600 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{cf5961f 6440:com.samsung.android.coreapps/5011}
10-14 23:46:32.615 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{44e1034 6454:com.sec.android.app.mt/1000}
10-14 23:46:32.905 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{4b8968a 6514:com.sec.android.app.sbrowser/u0a98}
10-14 23:46:32.920 3880 5801 V BroadcastQueue: [foreground] Process cur broadcast BroadcastRecord{5ec152d u-1 android.intent.action.SIM_STATE_CHANGED qIdx=2}, state= (APP_RECEIVE) DELIVERED for app ProcessRecord{93254fb 6534:com.sec.modem.settings/1000}
10-14 23:46:32.945

And that's pretty much useless, because when I press play it also stops logging anything! I've looked at errors and stuff out of the ordinary when the YouTube app starts, but there's nothing there that doesn't look normal.

It looks as if video-starting tries to grab a part of memory or cache or GPU that's broken. Any ideas?