Redmine leaks memory over 1G, YAML
|Resolution:||Cant reproduce||Affected version:||1.2.2|
It isn't very difficult to find memory leaks in Redmine. Sadly everything that remotely points to a solution - the port of Redmine to 1.9.2 for example - looks abandoned.
Still these leaks make Redmine in practice unusable.
#1 Updated by Etienne Massip about 6 years ago
- Category changed from Rails support to Ruby support
- Resolution set to Invalid
I don't remember having heard or seen of such an issue in forum.
I close this issue since this is a Ruby issue, not a Redmine one.
Finally, the port of Redmine to Ruby 1.9 (#4050) is not abandoned.
#6 Updated by Stefan de Konink about 6 years ago
About your application's environment
Ruby version 1.8.7 (i686-linux)
RubyGems version 1.8.10
Rack version 1.1
Rails version 2.3.14
Active Record version 2.3.14
Active Resource version 2.3.14
Action Mailer version 2.3.14
Active Support version 2.3.14
Application root /var/lib/redmine
Database adapter postgresql
Database schema version 20110511000000
About your Redmine plugins
Contacts plugin 1.1.5
Redmine Backlogs master branch (unstable)
#8 Updated by Stefan de Konink about 6 years ago
- File valgrind.txt added
Since valgrind really gives a gazzilion lines of output. I specifically ask you to look at the last part; syck_parse for example.
For us it is so easy to reproduce... that I really have to abort at the 3rd request or so otherwise ruby goes above 1GB of memory.
#9 Updated by Jean-Philippe Lang about 6 years ago
==3546== LEAK SUMMARY: ==3546== definitely lost: 74,748 bytes in 858 blocks ==3546== indirectly lost: 6,028 bytes in 137 blocks ==3546== possibly lost: 2,402,632 bytes in 103,591 blocks ==3546== still reachable: 256,202,523 bytes in 4,673,369 blocks ==3546== suppressed: 0 bytes in 0 blocks
74KB lost / 256MB still reachable ?
#12 Updated by Jean-Philippe Lang about 6 years ago
- Priority changed from Urgent to Normal
- Resolution changed from Invalid to Cant reproduce
My point is that this valgrind log doesn't illustrate the problem you described (1GB after 3 clicks). Anyway, this is not happening to everyone so there must be something else than this flaw in ruby1.8.7.
Feel free to post additional information that would help in reproducing your problem.