I just discovered it is due to motion blur which is on, which is supposed to only affect camera view, but is actually affecting all viewport movements in eevee next.
That tooltip is outdated,…
This is the same as #117128. Fixed by 8954099042.
Ah... I forgot Linux crash logs don't include debug symbols. 🙁 Thank you anyway.
We'll have to assume it's the same issue as #117082. Closing this as a duplicate then.
Can you post the crash report? https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#crash-log
That stack trace is really weird:
blender.exe :0x00007FF7B17F9810 Freestyle::FEdgeInternal::SVertexIterator::operator*
blender.exe :0x00007FF7B1FA0A50 blender::draw::detail…@PratikPB2123 I'm not sure if it's the same issue. This user seems to be able to use EEVEE Next and only crashes on certain circumstances, while the issue you linked seems to happen any time…
I've moved process_frame_timings to end_frame and added calls to begin/end_frame in DRW_gpu_context_enable/disable_ex.
It seems to be working fine, but I have no idea if there's any…
I've tried to use stringstream.rdbuf() but it turned out to be massively slow, so while now it's using std::cout, I think we will have to keep the string conversion.