Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- geek96boolean10 April 2017
- kfrajer April 2017
PVector causing memory usage
Using VisualVM, I found that the largest consumer of memory appears to be PVectors. As per my previous topic, my animation rendering sketch draws nearly 200 boxes per frame, and a single animation sequence could be as many as 200k frames. This means I rapidly hit the memory usage limit, even after adjusting Processing to allow up to 8GB of memory to be allocated.
The following image is of a sketch's heap that simply involves drawing a box every draw() call.
Now imagine that 200x as bad. The dip is the GC working; unfortunately, it can't quite keep up with the full sketch.
Is anyone having this sort of issue?
It appears that this isn't the only contributor of memory use, but it accounts for the largest portion.
(Actual sketch data)
This is really bad.
Answers
Currently exploring a possible fault on my end.
My bad; no problem here.
Thxs for the update!
Kf