crash while using PyCharm / Python3

[Daniel Wilcox]

Now as for *why* you needed to reinstall your graphics driver... did the
graphics driver get updated before the crash?  Or do we think something in
the java runtime for PyCharm ate libglx or friends?

I did find this PyCharm crash in which Java ate itself -- though didn't eat
any library files (as that is *very* special) -- going on out a limb here
maybe the crash was something like this, sans the markdown plugin:
https://github.com/nicoulaj/idea-markdown/issues/247

<snip>
7f7b38dd9000 r-xp 00000000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38dd9000-7f7b38fd8000 ---p 00015000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38fd8000-7f7b38fda000 r--p 00014000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38fda000-7f7b38fdb000 rw-p 00016000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.s</snip>

So some xcb libraries do get mapped -- but that doesn't say much really --
after all paging a library in shouldn't lead to writing to it, corrupting
it -- but copy-on-write and all that crap... so maybe.

Also from some quick reading on XCD it doesn't sound like it has anything
to do with initializing the graphics system, which is still GLX+Xlib's
job.  So whether this could even affect you at startup isn't clear to me.

https://xcb.freedesktop.org/opengl/

Late to the party but glad to hear everything worked out.  It's been
literally a decade since I worried about having working 3d graphics in
Linux, so nouveau for me.  Cheers!


On Tue, Mar 22, 2016 at 6:10 AM, Jonathan N. Little <lws4art at gmail.com>
wrote:

> Adam wrote:
>
>> Thanks, but why fix if it ain't broke?:-)
>>
>
> No reason to.
>
>
> --
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com
> --
> https://mail.python.org/mailman/listinfo/python-list
>