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
Hello Ray,
Warning, a coredump from this system would be immense. Or, well anyway
pretty darn large.
systemd-coredump should limit the core to 2G.
And as a first target, the journal output might have a backtrace
from which one could start looking.
Maybe running openuniverse with a memory
On Wed, 14 Apr 2021 14:04:33 + Ray Dillinger wrote:
>
> Warning, a coredump from this system would be immense. Or, well anyway
> pretty darn large. The machine has over 64G of RAM memory installed and
> openuniverse seems to expand to fill available space. I could make a VM
> with
On Wed, 14 Apr 2021 11:59:43 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Hello Ray,
> from the "Code:" line you supplied I think the segfault happens
> in create_cache_trans at ../src/mesa/state_tracker/st_cb_bitmap.c:402.
>
>
Hello Ray,
from the "Code:" line you supplied I think the segfault happens
in create_cache_trans at ../src/mesa/state_tracker/st_cb_bitmap.c:402.
https://sources.debian.org/src/mesa/20.3.5-1/src/mesa/state_tracker/st_cb_bitmap.c/#L402
But I guess this information is not enough for the
Package: openuniverse
version: 1.0beta3.1+dfsg-6.1
When I started openuniverse, it put up a window with no menu items and
no other control elements. It responded to '?' or 'H' keystrokes by
putting up a short list of keystroke shortcuts - presumably
corresponding to nonexistent menu options.
6 matches
Mail list logo