Ubuntu 20.04 LTS and BricsCAD V22

I have been working with this combination for a month now. I have had many crashes and do not know what the issue is. I am moving back to stable Ubuntu 18.04 and V20 BricsCAD.

The crashes happen when I select more than one block for editing.

from the /var/log/kern.log file, looks like a graphics issues.

May 10 07:12:29 inp1 kernel: [10181.224394] bricscad[5089]: segfault at 20 ip 00007f7927a5643c sp 00007f78ff3f4cc0 error 4 in libwxgui.so[7f7927771000+13c6000]
May 10 07:12:29 inp1 kernel: [10181.224409] Code: 83 c4 18 5b 5d c3 0f 1f 84 00 00 00 00 00 48 83 c4 18 31 c0 5b 5d c3 90 66 0f 1f 44 00 00 55 53 48 89 f5 48 89 fb 48 83 ec 08 0f 10 47 20 66 0f 2e 47 08 72 48 f2 0f 10 47 28 66 0f 2e 47 10
May 10 07:14:07 inp1 kernel: [10279.126174] bricscad[5788]: segfault at 0 ip 00007fb0c3ea8b70 sp 00007fb096514600 error 4 in libTD_Ge.so[7fb0c3e55000+630000]
May 10 07:14:07 inp1 kernel: [10279.126209] Code: ee 4c 8d 74 24 40 c6 44 24 31 00 48 c7 44 24 40 00 00 00 00 48 c7 44 24 48 00 00 00 00 c6 44 24 50 00 c6 44 24 51 00 ff 50 68 <48> 8b 4d 00 4c 89 f6 48 89 ef ff 51 68 48 83 ec 08 4c 8b 13 49 89
May 10 07:19:09 inp1 kernel: [10581.151935] bricscad[5900]: segfault at 7d0 ip 00007f65ac4cf43c sp 00007f6583e6da00 error 4 in libwxgui.so[7f65ac1ea000+13c6000]
May 10 07:19:09 inp1 kernel: [10581.151951] Code: 83 c4 18 5b 5d c3 0f 1f 84 00 00 00 00 00 48 83 c4 18 31 c0 5b 5d c3 90 66 0f 1f 44 00 00 55 53 48 89 f5 48 89 fb 48 83 ec 08 0f 10 47 20 66 0f 2e 47 08 72 48 f2 0f 10 47 28 66 0f 2e 47 10

Comments

  • I'll try apt get update, upgrade first, then report back
  • After the apt-get upgrade, BricsCAD V22 continued to crash. I'm moving back to V20 for now.

    Just an observation, but it looks like there was an added feature, when you select two block objects it gives you an arrow between the two blocks. After selecting two objects many many times, over and over again, the crash happens
  • Hello Cnut, does the crash also happen if NEARESTDISTANCE is disabled (value zero)?
  • Hello Cnut, does the crash also happen if NEARESTDISTANCE is disabled (value zero)?

    I will try this, thanks.
  • After setting NEARESTDISTANCE to zero, no crashes so far!
  • No crashes, looks like that fixed it. Thanks again for the help. That feature changed and must have been enabled by default with V22.
  • Ok, thanks Cnut, so it is clearly caused by the NEARESTDISTANCE feature. So far so good bad. Can you please enter a support request to report the crash? Then a support analyst can establish the circumstances to reproduce...
  • Ok, thanks Cnut, so it is clearly caused by the NEARESTDISTANCE feature. So far so good bad. Can you please enter a support request to report the crash? Then a support analyst can establish the circumstances to reproduce...

    Yes the crash seems to be caused by the NEARESTDISTANCE feature. After disabling NEARESTDISTANCE everything appears to be working fine.

    Sure, is there a link I can follow to the support request? I have never completed a support request.

    When the crash happened, sometimes Ubuntu 20.04.4 LTS would ask to send a crash report over the internet. Where do those go? I bet I sent 4 or 5 of them. The above /var/log/kern.log shows the offending library as libwxgui.so or libTD_Ge.so. segfault error 4. This happens when forbidden memory is being accessed. Probably an array or pointer issue.

    I will copy and paste this thread into the support request. Do they read the threads here?
    Ubuntu 20.04.4 LTS BricsCAD Pro 22.2.03 with the SDK V22.1.05.

    The crash would happen when I would select two different custom large blocks at the same time. Do this many times and crash. It seemed to be predictable.
  • Hi Cnut, the expert support analysts don't usually read the public forums. Here is the direct link to submit a support request:
    https://boa.bricsys.com/protected/support/NewSupportRequest.do
  • Hi Cnut, the expert support analysts don't usually read the public forums. Here is the direct link to submit a support request:
    https://boa.bricsys.com/protected/support/NewSupportRequest.do

    Great! Support request completed.
    I marked it as a suggestion as it is low priority for me at this point. I don't use NEARESTDISTANCE.
    I am just happy the crashes stopped. Thanks for the help!
  • No crashes, problem fixed by disabling NEARESTDISTANCE! Thanks
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!