0.23.0 Bugs

Support for running, installing or compiling OpenMW

Before you submit a bug report for the first time, please read: Bug reporting guidelines
Chris
Posts: 1578
Joined: 04 Sep 2011, 08:33

Re: 0.23.0 Bugs

Post by Chris » 01 May 2013, 18:24

Zini wrote:Do we still have any developers who work on a 32 bit Linux system? If yes, does OpenMW work there? And if it doesn't, any chance we could get it git bisect'ed?
OpenMW works on 32-bit Linux here. I'm not using the packaged builds, of course, but aside from a possible memory leak, I don't have any unexpected issues.

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: 0.23.0 Bugs

Post by Zini » 01 May 2013, 19:11

Okay. Then it is a packaging issue. Nothing more I can do here from my end.

User avatar
psi29a
Posts: 4807
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.23.0 Bugs

Post by psi29a » 01 May 2013, 22:11

Someone claimed that win32 builds too had an issue (in another thread).

We need more testers on the 32-bit packages to track this down because I cannot reproduce it.

sirherrbatka says it is failing for him, I suggest we get a full and detailed dump of what is causing this.

Does it crash? Do you get a seg fault? Can you run gdb and get a back trace?

User avatar
sirherrbatka
Posts: 2157
Joined: 07 Aug 2011, 17:21

Re: 0.23.0 Bugs

Post by sirherrbatka » 02 May 2013, 08:18

It does not crash or segfault. It simply rans out of memory very fast.

User avatar
psi29a
Posts: 4807
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.23.0 Bugs

Post by psi29a » 02 May 2013, 08:36

Can you run valgrind on it? What is your process, just wondering around or do you just start it, not moving and watch mem usage go through the roof? Does the OOM killer come along and eventually kill it? Nvidia or AMD drivers or one of the open source drivers?
Last edited by psi29a on 02 May 2013, 08:40, edited 1 time in total.

User avatar
sirherrbatka
Posts: 2157
Joined: 07 Aug 2011, 17:21

Re: 0.23.0 Bugs

Post by sirherrbatka » 02 May 2013, 08:38

Binary packages are not builded with debug symbols?

User avatar
psi29a
Posts: 4807
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.23.0 Bugs

Post by psi29a » 02 May 2013, 09:02

sirherrbatka wrote:Binary packages are not builded with debug symbols?
No, they are not.. due to bug in Ogre 1.8.x from a bad assert that crashes it to desktop.

Attempts were made to fix it from scrawl to zini, but it was considered a bug in Ogre and we carried on.

User avatar
sirherrbatka
Posts: 2157
Joined: 07 Aug 2011, 17:21

Re: 0.23.0 Bugs

Post by sirherrbatka » 02 May 2013, 09:18

So no valgrind.

I use nvidia binary blob.

PS
Staying in one place seems to prohibits this issue. But I once ran out of memory without leaving the starting cell.

User avatar
psi29a
Posts: 4807
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.23.0 Bugs

Post by psi29a » 02 May 2013, 09:29

You cannot duplicate this with 64-bit deb/tar.gz ?

User avatar
sirherrbatka
Posts: 2157
Joined: 07 Aug 2011, 17:21

Re: 0.23.0 Bugs

Post by sirherrbatka » 02 May 2013, 10:21

I don't have 64 bits OS on my computers (yet).

Locked