The program 'ORB-SLAM2: Current Frame' received an X Window System error.

When running the ORB-SLAM monocular system, there are visual results, but the following issues occur when it finishes running, and no results are saved.

lrl@lrl:~/ORB_SLAM2$ ./Examples/Monocular/mono_tum ./Vocabulary/ORBvoc.txt ./Examples/Monocular/TUM1.yaml /home/lrl/bag/rgbd_dataset_freiburg1_desk

ORB-SLAM2 Copyright (C) 2014-2016 Raul Mur-Artal, University of Zaragoza. This program comes with ABSOLUTELY NO WARRANTY; This is free software, and you are welcome to redistribute it under certain conditions. See LICENSE.txt.

Input sensor was set to: Monocular

Loading ORB Vocabulary. This could take a while... Vocabulary loaded!

Camera Parameters:

• fx: 517.306
• fy: 516.469
• cx: 318.643
• cy: 255.314
• k1: 0.262383
• k2: -0.953104
• k3: 1.16331
• p1: -0.005358
• p2: 0.002628
• fps: 30
• color order: RGB (ignored if grayscale)

ORB Extractor Parameters:

• Number of Features: 1000
• Scale Levels: 8
• Scale Factor: 1.2
• Initial Fast Threshold: 20
• Minimum Fast Threshold: 7

---

Start processing sequence ... Images in the sequence: 613

New Map created with 79 points Wrong initialization, reseting... System Reseting Reseting Local Mapper... done Reseting Loop Closing... done Reseting Database... done New Map created with 120 points The program 'ORB-SLAM2: Current Frame' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 690 error_code 10 request_code 149 minor_code 5) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) mono_tum: ../src/GLX/libglx.c:966: CommonMakeCurrent: 断言 "oldCtxInfo != NULL" 失败。 已中止 (核心已转储)