| 1 |
Something
feels
broken.
So
@GoogleFrog
last
night
I
witnessed
another
hard
lockup
on
loading
a
game.
Again
it
loaded
fine
when
I
reset
computer
and
re-entered
the
match.
|
1 |
Something
feels
broken.
So
@GoogleFrog
last
night
I
witnessed
another
hard
lockup
on
loading
a
game
following
earlier
game.
Again
it
loaded
fine
when
I
reset
computer
and
re-entered
the
match.
|
| 2 |
\n
|
2 |
\n
|
| 3 |
Here is the (hopefully) relevant portion of the infolog again: [url=https://pastebin.com/y8gRcL9t]https://pastebin.com/y8gRcL9t[/url]
|
3 |
Here is the (hopefully) relevant portion of the infolog again: [url=https://pastebin.com/y8gRcL9t]https://pastebin.com/y8gRcL9t[/url]
|
| 4 |
\n
|
4 |
\n
|
| 5 |
It's not related to the old manually needing to delete files or directories is it? If so I should give that a shot since I never do it unless I'm told to.
|
5 |
It's not related to the old manually needing to delete files or directories is it? If so I should give that a shot since I never do it unless I'm told to.
|
| 6 |
\n
|
6 |
\n
|
| 7 |
Of course the issue could be something other than Zero-K. But I see nothing in 'journalctl -b -1' which captures system level errors. I do have mumble open at the same time. Next time I will check the problem is not being caused by my trying to change workspace whilst the game is loading (not that that should cause hard lockup).
|
7 |
Of course the issue could be something other than Zero-K. But I see nothing in 'journalctl -b -1' which captures system level errors. I do have mumble open at the same time. Next time I will check the problem is not being caused by my trying to change workspace whilst the game is loading (not that that should cause hard lockup).
|
Massive jam at start / memleaks on linux