Mixing
Piston application crashes after a few minutes with a memory allocation error
I've developed a maze game using Piston in Rust in order to teach myself graphics/UI programming. The game mostly works fine, but when I run it with a large maze (e.g. 120 x 72 rectangles), the game crashes with a memory allocation error after a couple minutes.
A reduced example is as follows:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
if let Some(_args) = event.render_args() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
}
When I run this, I get a memory allocation error, followed by a process abort:
$ time cargo run --release
Compiling maze v0.1.0 (/home/isaac/prog/rust/test-maze)
Finished release [optimized] target(s) in 5.28s
Running `target/release/maze`
memory allocation of 7927496704 bytes failedAborted (core dumped)
real 2m24.317s
user 1m29.515s
sys 0m3.644s
Running it in the debugger, I get the following backtrace:
(gdb) backtrace
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff71e1801 in __GI_abort () at abort.c:79
#2 0x0000555555708fc7 in std::sys::unix::abort_internal () at src/libstd/sys/unix/mod.rs:157
#3 0x000055555570419d in rust_oom () at src/libstd/alloc.rs:211
#4 0x0000555555717f37 in alloc::alloc::handle_alloc_error () at src/liballoc/alloc.rs:224
#5 0x00005555556eaf7d in <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T, I>>::spec_extend ()
#6 0x00005555556e64aa in <gfx_core::handle::Manager<R>>::extend ()
#7 0x00005555556da204 in <gfx_device_gl::Device as gfx_core::Device>::pin_submitted_resources ()
#8 0x000055555559d654 in <gfx::encoder::Encoder<R, C>>::flush ()
#9 0x000055555558f8af in maze::main ()
#10 0x000055555558bb73 in std::rt::lang_start::{{closure}} ()
#11 0x0000555555704913 in std::rt::lang_start_internal::{{closure}} () at src/libstd/rt.rs:49
#12 std::panicking::try::do_call () at src/libstd/panicking.rs:297
#13 0x000055555570927a in __rust_maybe_catch_panic () at src/libpanic_unwind/lib.rs:92
#14 0x0000555555705466 in std::panicking::try () at src/libstd/panicking.rs:276
#15 std::panic::catch_unwind () at src/libstd/panic.rs:388
#16 std::rt::lang_start_internal () at src/libstd/rt.rs:48
#17 0x000055555558fae2 in main ()
I am using Ubuntu Linux 18.04.
Should my program be written differently to prevent this problem? Is there something wrong with Piston?
rust out-of-memory rust-piston
edited Jan 2 at 16:38
Shepmaster
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
add a comment |
I've developed a maze game using Piston in Rust in order to teach myself graphics/UI programming. The game mostly works fine, but when I run it with a large maze (e.g. 120 x 72 rectangles), the game crashes with a memory allocation error after a couple minutes.
A reduced example is as follows:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
if let Some(_args) = event.render_args() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
}
When I run this, I get a memory allocation error, followed by a process abort:
$ time cargo run --release
Compiling maze v0.1.0 (/home/isaac/prog/rust/test-maze)
Finished release [optimized] target(s) in 5.28s
Running `target/release/maze`
memory allocation of 7927496704 bytes failedAborted (core dumped)
real 2m24.317s
user 1m29.515s
sys 0m3.644s
Running it in the debugger, I get the following backtrace:
(gdb) backtrace
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff71e1801 in __GI_abort () at abort.c:79
#2 0x0000555555708fc7 in std::sys::unix::abort_internal () at src/libstd/sys/unix/mod.rs:157
#3 0x000055555570419d in rust_oom () at src/libstd/alloc.rs:211
#4 0x0000555555717f37 in alloc::alloc::handle_alloc_error () at src/liballoc/alloc.rs:224
#5 0x00005555556eaf7d in <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T, I>>::spec_extend ()
#6 0x00005555556e64aa in <gfx_core::handle::Manager<R>>::extend ()
#7 0x00005555556da204 in <gfx_device_gl::Device as gfx_core::Device>::pin_submitted_resources ()
#8 0x000055555559d654 in <gfx::encoder::Encoder<R, C>>::flush ()
#9 0x000055555558f8af in maze::main ()
#10 0x000055555558bb73 in std::rt::lang_start::{{closure}} ()
#11 0x0000555555704913 in std::rt::lang_start_internal::{{closure}} () at src/libstd/rt.rs:49
#12 std::panicking::try::do_call () at src/libstd/panicking.rs:297
#13 0x000055555570927a in __rust_maybe_catch_panic () at src/libpanic_unwind/lib.rs:92
#14 0x0000555555705466 in std::panicking::try () at src/libstd/panicking.rs:276
#15 std::panic::catch_unwind () at src/libstd/panic.rs:388
#16 std::rt::lang_start_internal () at src/libstd/rt.rs:48
#17 0x000055555558fae2 in main ()
I am using Ubuntu Linux 18.04.
Should my program be written differently to prevent this problem? Is there something wrong with Piston?
rust out-of-memory rust-piston
edited Jan 2 at 16:38
Shepmaster
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
add a comment |
I've developed a maze game using Piston in Rust in order to teach myself graphics/UI programming. The game mostly works fine, but when I run it with a large maze (e.g. 120 x 72 rectangles), the game crashes with a memory allocation error after a couple minutes.
A reduced example is as follows:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
if let Some(_args) = event.render_args() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
}
When I run this, I get a memory allocation error, followed by a process abort:
$ time cargo run --release
Compiling maze v0.1.0 (/home/isaac/prog/rust/test-maze)
Finished release [optimized] target(s) in 5.28s
Running `target/release/maze`
memory allocation of 7927496704 bytes failedAborted (core dumped)
real 2m24.317s
user 1m29.515s
sys 0m3.644s
Running it in the debugger, I get the following backtrace:
(gdb) backtrace
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff71e1801 in __GI_abort () at abort.c:79
#2 0x0000555555708fc7 in std::sys::unix::abort_internal () at src/libstd/sys/unix/mod.rs:157
#3 0x000055555570419d in rust_oom () at src/libstd/alloc.rs:211
#4 0x0000555555717f37 in alloc::alloc::handle_alloc_error () at src/liballoc/alloc.rs:224
#5 0x00005555556eaf7d in <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T, I>>::spec_extend ()
#6 0x00005555556e64aa in <gfx_core::handle::Manager<R>>::extend ()
#7 0x00005555556da204 in <gfx_device_gl::Device as gfx_core::Device>::pin_submitted_resources ()
#8 0x000055555559d654 in <gfx::encoder::Encoder<R, C>>::flush ()
#9 0x000055555558f8af in maze::main ()
#10 0x000055555558bb73 in std::rt::lang_start::{{closure}} ()
#11 0x0000555555704913 in std::rt::lang_start_internal::{{closure}} () at src/libstd/rt.rs:49
#12 std::panicking::try::do_call () at src/libstd/panicking.rs:297
#13 0x000055555570927a in __rust_maybe_catch_panic () at src/libpanic_unwind/lib.rs:92
#14 0x0000555555705466 in std::panicking::try () at src/libstd/panicking.rs:276
#15 std::panic::catch_unwind () at src/libstd/panic.rs:388
#16 std::rt::lang_start_internal () at src/libstd/rt.rs:48
#17 0x000055555558fae2 in main ()
I am using Ubuntu Linux 18.04.
Should my program be written differently to prevent this problem? Is there something wrong with Piston?
rust out-of-memory rust-piston
edited Jan 2 at 16:38
Shepmaster
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
I've developed a maze game using Piston in Rust in order to teach myself graphics/UI programming. The game mostly works fine, but when I run it with a large maze (e.g. 120 x 72 rectangles), the game crashes with a memory allocation error after a couple minutes.
A reduced example is as follows:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
if let Some(_args) = event.render_args() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
}
When I run this, I get a memory allocation error, followed by a process abort:
$ time cargo run --release
Compiling maze v0.1.0 (/home/isaac/prog/rust/test-maze)
Finished release [optimized] target(s) in 5.28s
Running `target/release/maze`
memory allocation of 7927496704 bytes failedAborted (core dumped)
real 2m24.317s
user 1m29.515s
sys 0m3.644s
Running it in the debugger, I get the following backtrace:
(gdb) backtrace
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007ffff71e1801 in __GI_abort () at abort.c:79
#2 0x0000555555708fc7 in std::sys::unix::abort_internal () at src/libstd/sys/unix/mod.rs:157
#3 0x000055555570419d in rust_oom () at src/libstd/alloc.rs:211
#4 0x0000555555717f37 in alloc::alloc::handle_alloc_error () at src/liballoc/alloc.rs:224
#5 0x00005555556eaf7d in <alloc::vec::Vec<T> as alloc::vec::SpecExtend<T, I>>::spec_extend ()
#6 0x00005555556e64aa in <gfx_core::handle::Manager<R>>::extend ()
#7 0x00005555556da204 in <gfx_device_gl::Device as gfx_core::Device>::pin_submitted_resources ()
#8 0x000055555559d654 in <gfx::encoder::Encoder<R, C>>::flush ()
#9 0x000055555558f8af in maze::main ()
#10 0x000055555558bb73 in std::rt::lang_start::{{closure}} ()
#11 0x0000555555704913 in std::rt::lang_start_internal::{{closure}} () at src/libstd/rt.rs:49
#12 std::panicking::try::do_call () at src/libstd/panicking.rs:297
#13 0x000055555570927a in __rust_maybe_catch_panic () at src/libpanic_unwind/lib.rs:92
#14 0x0000555555705466 in std::panicking::try () at src/libstd/panicking.rs:276
#15 std::panic::catch_unwind () at src/libstd/panic.rs:388
#16 std::rt::lang_start_internal () at src/libstd/rt.rs:48
#17 0x000055555558fae2 in main ()
I am using Ubuntu Linux 18.04.
Should my program be written differently to prevent this problem? Is there something wrong with Piston?
rust out-of-memory rust-piston
rust out-of-memory rust-piston
edited Jan 2 at 16:38
Shepmaster
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
edited Jan 2 at 16:38
Shepmaster
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
edited Jan 2 at 16:38
Shepmaster
158k15322464
edited Jan 2 at 16:38
Shepmaster
158k15322464
edited Jan 2 at 16:38
Shepmaster
158k15322464
158k15322464
asked Jan 2 at 2:46
isaacgisaacg
288212
asked Jan 2 at 2:46
isaacgisaacg
288212
asked Jan 2 at 2:46
isaacgisaacg
288212
288212
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The problem is located here:
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
Instead, one should use this:
while let Some(event) = window.next() {
It turns out that window.next() runs some cleanup steps that events.next(&mut window) omits, and these cleanup steps free the relevant memory. As far as I can tell, the documentation makes no mention of this, and the examples use both patterns without indicating the difference.
This cleanup is mentioned in the comments here, as was pointed out by Tiriosaurus on reddit.
answered Jan 2 at 17:14
isaacgisaacg
288212
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
add a comment |
That's about an 8 GB allocation it's doing; way too large to be reasonable. 8 GB is probably related to your system RAM. One half, equal or double to it, depending on your system setup.
The problem has to be in the loop and it has to be small. The loop isn't very big, is it? Which is the nice thing about small examples. It looks like it was the event code. I have no idea why.
Here's a version that does not appear to have a memory leak:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
while let Some(event) = window.next() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
edited Jan 2 at 17:16
Shepmaster
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000664%2fpiston-application-crashes-after-a-few-minutes-with-a-memory-allocation-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem is located here:
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
Instead, one should use this:
while let Some(event) = window.next() {
It turns out that window.next() runs some cleanup steps that events.next(&mut window) omits, and these cleanup steps free the relevant memory. As far as I can tell, the documentation makes no mention of this, and the examples use both patterns without indicating the difference.
This cleanup is mentioned in the comments here, as was pointed out by Tiriosaurus on reddit.
answered Jan 2 at 17:14
isaacgisaacg
288212
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
add a comment |
The problem is located here:
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
Instead, one should use this:
while let Some(event) = window.next() {
It turns out that window.next() runs some cleanup steps that events.next(&mut window) omits, and these cleanup steps free the relevant memory. As far as I can tell, the documentation makes no mention of this, and the examples use both patterns without indicating the difference.
This cleanup is mentioned in the comments here, as was pointed out by Tiriosaurus on reddit.
answered Jan 2 at 17:14
isaacgisaacg
288212
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
add a comment |
The problem is located here:
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
Instead, one should use this:
while let Some(event) = window.next() {
It turns out that window.next() runs some cleanup steps that events.next(&mut window) omits, and these cleanup steps free the relevant memory. As far as I can tell, the documentation makes no mention of this, and the examples use both patterns without indicating the difference.
This cleanup is mentioned in the comments here, as was pointed out by Tiriosaurus on reddit.
answered Jan 2 at 17:14
isaacgisaacg
288212
The problem is located here:
let mut events = Events::new(EventSettings::new());
while let Some(event) = events.next(&mut window) {
Instead, one should use this:
while let Some(event) = window.next() {
It turns out that window.next() runs some cleanup steps that events.next(&mut window) omits, and these cleanup steps free the relevant memory. As far as I can tell, the documentation makes no mention of this, and the examples use both patterns without indicating the difference.
This cleanup is mentioned in the comments here, as was pointed out by Tiriosaurus on reddit.
answered Jan 2 at 17:14
isaacgisaacg
288212
answered Jan 2 at 17:14
isaacgisaacg
288212
answered Jan 2 at 17:14
isaacgisaacg
288212
answered Jan 2 at 17:14
isaacgisaacg
288212
288212
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
add a comment |
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
2
2
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
See also Piston issue #1174. This is... pretty sloppy and embarrassing for their project it seems.
– Shepmaster
Jan 2 at 17:17
add a comment |
That's about an 8 GB allocation it's doing; way too large to be reasonable. 8 GB is probably related to your system RAM. One half, equal or double to it, depending on your system setup.
The problem has to be in the loop and it has to be small. The loop isn't very big, is it? Which is the nice thing about small examples. It looks like it was the event code. I have no idea why.
Here's a version that does not appear to have a memory leak:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
while let Some(event) = window.next() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
edited Jan 2 at 17:16
Shepmaster
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
add a comment |
That's about an 8 GB allocation it's doing; way too large to be reasonable. 8 GB is probably related to your system RAM. One half, equal or double to it, depending on your system setup.
The problem has to be in the loop and it has to be small. The loop isn't very big, is it? Which is the nice thing about small examples. It looks like it was the event code. I have no idea why.
Here's a version that does not appear to have a memory leak:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
while let Some(event) = window.next() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
edited Jan 2 at 17:16
Shepmaster
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
add a comment |
That's about an 8 GB allocation it's doing; way too large to be reasonable. 8 GB is probably related to your system RAM. One half, equal or double to it, depending on your system setup.
The problem has to be in the loop and it has to be small. The loop isn't very big, is it? Which is the nice thing about small examples. It looks like it was the event code. I have no idea why.
Here's a version that does not appear to have a memory leak:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
while let Some(event) = window.next() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
edited Jan 2 at 17:16
Shepmaster
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
That's about an 8 GB allocation it's doing; way too large to be reasonable. 8 GB is probably related to your system RAM. One half, equal or double to it, depending on your system setup.
The problem has to be in the loop and it has to be small. The loop isn't very big, is it? Which is the nice thing about small examples. It looks like it was the event code. I have no idea why.
Here's a version that does not appear to have a memory leak:
extern crate graphics;
extern crate opengl_graphics;
extern crate piston;
extern crate piston_window;
use opengl_graphics::OpenGL;
use piston::event_loop::*;
use piston::input::*;
use piston_window::{PistonWindow, WindowSettings};
const BLACK: [f32; 4] = [0.0, 0.0, 0.0, 1.0];
const WHITE: [f32; 4] = [1.0, 1.0, 1.0, 1.0];
fn main() {
let opengl = OpenGL::V3_2;
let mut window: PistonWindow = WindowSettings::new("maze", [800, 600])
.opengl(opengl)
.exit_on_esc(true)
.build()
.unwrap();
while let Some(event) = window.next() {
window.draw_2d(&event, |c, gl| {
graphics::clear(BLACK, gl);
for _row in 0..72 {
for _col in 0..120 {
let color = WHITE;
let box_rect =
graphics::rectangle::rectangle_by_corners(0.0, 0.0, 10.0, 10.0);
graphics::rectangle(color, box_rect, c.transform, gl);
}
}
});
}
}
edited Jan 2 at 17:16
Shepmaster
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
edited Jan 2 at 17:16
Shepmaster
158k15322464
edited Jan 2 at 17:16
Shepmaster
158k15322464
edited Jan 2 at 17:16
Shepmaster
158k15322464
158k15322464
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
answered Jan 2 at 3:08
Zan LynxZan Lynx
41k663110
41k663110
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
add a comment |
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
Thanks - I was pointed to the same conclusion and posted it at about the same time.
– isaacg
Jan 2 at 17:16
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54000664%2fpiston-application-crashes-after-a-few-minutes-with-a-memory-allocation-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
