BGE startGame Memory Leak #39382

New Issue

mobious · 2014-03-24T09:51:28+01:00

mobious commented

2014-03-24 09:51:28 +01:00

System Information
Windows 7 Home Premium 64-bit
ATI Mobility Radeon HD 4670

Blender Version
2.70 19e627c

Short description of error
Starting and stopping the game engine appears to leak memory when the startGame function (bge.logic.startGame) is called.

Exact steps for others to reproduce the error
Place the two attached .blend files in the same folder and open start.blend. Note the base amount of memory Blender is using. Start and stop the game engine repeatedly (by hitting P and Esc) and note how Blender's memory usage increases. An initial increase is expected after the first run since the internal player's resources are loaded, but after that there is still a steady increase in memory usage (of about 45Kb each time the game engine is started on my machine).

start.blend

other.blend

**System Information** Windows 7 Home Premium 64-bit ATI Mobility Radeon HD 4670 **Blender Version** 2.70 19e627c **Short description of error** Starting and stopping the game engine appears to leak memory when the startGame function (bge.logic.startGame) is called. **Exact steps for others to reproduce the error** Place the two attached .blend files in the same folder and open start.blend. Note the base amount of memory Blender is using. Start and stop the game engine repeatedly (by hitting P and Esc) and note how Blender's memory usage increases. An initial increase is expected after the first run since the internal player's resources are loaded, but after that there is still a steady increase in memory usage (of about 45Kb each time the game engine is started on my machine). [start.blend](https://archive.blender.org/developer/F82369/start.blend) [other.blend](https://archive.blender.org/developer/F82370/other.blend)

mobious commented

2014-03-24 09:51:28 +01:00

Changed status to: 'Open'

mobious commented

2014-03-24 09:51:28 +01:00

Added subscriber: @mobious

Mitchell Stokes commented

2014-03-25 02:13:49 +01:00

Added subscriber: @Moguri

Mitchell Stokes commented

2014-03-25 02:13:49 +01:00

The current "leak" you're showing with this file feels like noise. It is almost impossible to hunt down (valgrind reports nothing). Even if I did find and fix a leak, I don't know if it is the one you're reporting or some other small leak. Also, sometimes operating systems do some caching that can inflate usage, which can add to the noise. In other words, it would be much more useful to have a file that demonstrates a large, obvious leak, but is still simple. Otherwise, there is little chance this issue will be fixed.

I do know of a small leak when initializing the BGE Python API, but this shouldn't cause problems.

The current "leak" you're showing with this file feels like noise. It is almost impossible to hunt down (valgrind reports nothing). Even if I did find and fix a leak, I don't know if it is the one you're reporting or some other small leak. Also, sometimes operating systems do some caching that can inflate usage, which can add to the noise. In other words, it would be much more useful to have a file that demonstrates a large, obvious leak, but is still simple. Otherwise, there is little chance this issue will be fixed. I do know of a small leak when initializing the BGE Python API, but this shouldn't cause problems.

Mitchell Stokes commented

2014-03-26 08:26:12 +01:00

The current "leak" you're showing with this file feels like noise. It is almost impossible to hunt down (valgrind reports nothing). Even if I did find and fix a leak, I don't know if it is the one you're reporting or some other small leak. Also, sometimes operating systems do some caching that can inflate usage, which can add to the noise. In other words, it would be much more useful to have a file that demonstrates a large, obvious leak, but is still simple. Otherwise, there is little chance this issue will be fixed.

I do know of a small leak when initializing the BGE Python API, but this shouldn't cause problems.

The current "leak" you're showing with this file feels like noise. It is almost impossible to hunt down (valgrind reports nothing). Even if I did find and fix a leak, I don't know if it is the one you're reporting or some other small leak. Also, sometimes operating systems do some caching that can inflate usage, which can add to the noise. In other words, it would be much more useful to have a file that demonstrates a large, obvious leak, but is still simple. Otherwise, there is little chance this issue will be fixed. I do know of a small leak when initializing the BGE Python API, but this shouldn't cause problems.

Bastien Montagne commented

2014-04-02 22:05:52 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2014-04-02 22:05:52 +02:00

Bastien Montagne self-assigned this 2014-04-02 22:05:52 +02:00

Bastien Montagne commented

2014-04-02 22:05:52 +02:00

No answer since a week…

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

BGE startGame Memory Leak #39382