You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then in separate terminal I start loading mojo with requests
for i (`seq 10000`);do \
curl -s --data-binary @/usr/share/webkitgtk-1.0/images/urlIcon.png \
'http://localhost:3000/foo?ab=x.png&size=1200,1200'; \
done
Then I switch to another terminal and attentively look at memory usage via htop utility... and both "virtual" and "resident" memory are very slowly but constantly increasing.
I have created test plan in apache-jmeter which leads to the same results, but a little bit faster
$cpanm --info Mojolicious
SRI/Mojolicious-3.87.tar.gz
#perl -v
This is perl 5, version 16, subversion 2 (v5.16.2) built for x86_64-linux-thread-multi
(with 22 registered patches, see perl -V for more detail)
Copyright 1987-2012, Larry Wall
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
The text was updated successfully, but these errors were encountered:
I've been able to reduce the leak to a minimal test case, so far it does look like a Perl (or Encode) bug.
use 5.16.0;
use Encode 'find_encoding';
my $encoding = find_encoding 'UTF-8';
my $invalid = "\x89";
for (1 .. 100000000) {
say $_;
eval { $encoding->decode($invalid, 1); 1 };
}
Hello! I'm not sure, but it really looks like memory leak in Mojo.
The demo application is:
I start it in command-line via:
Then in separate terminal I start loading mojo with requests
Then I switch to another terminal and attentively look at memory usage via htop utility... and both "virtual" and "resident" memory are very slowly but constantly increasing.
I have created test plan in apache-jmeter which leads to the same results, but a little bit faster
The software versions are:
The text was updated successfully, but these errors were encountered: