On 5/26/21 8:01 PM, Bernhard Übelacker wrote: > Testing in a VM with a more reasonable 6GB apparently does not provoke >> the crash. > > I fear the issue might also be specific to the graphics library > because the crash happens in nouveau_dri.so. > Therefore a VM might not show this issue. > I defer to your expertise. I'm not really familiar with how the graphics libraries and graphics drivers work with the software, so you're way more likely to be right.
> >> ... and openuniverse seems to expand to fill available space. > > That would be a memory leak I guess. > Then the backtrace would be really not that interesting. > ??? I can't reproduce that now. It still crashes after a while but it doesn't expand to fill available space. Did something else get fixed that might affect it? >> ... but checking screenshots of it online I see many UI elements that >> simply are not present when I start it. > > I guess the gui needs a libglui, which is not "yet" > packaged for debian (see #801858). > I think that's a showstopper bug for OpenUniverse. It renders the program useless, even if it weren't crashing. I'm surprised to find it outside of the "Sid" distribution if it doesn't have that. > > But while writing this email, I got my hands on a nouveau capable laptop. > There I found openuniverse also crashing if I leave it some time alone, > at the very exact instruction [1]. Oh good. I mean, not good that it's crashing, but good that the crash can be reliably reproduced outside of my peculiar configuration. If other people are seeing it too, it means I haven't done something that puts my machine into a failure-prone configuration that I'll never figure out. > I tried to record with rr, but this forces the driver to software mode, > therefore the issue then does not show up. Hum, that's interesting. Now I need to go read man pages. Thank you for looking into it. Bear
