search

erlang / rebar3

Erlang build tool that makes it easy to compile and test Erlang applications and releases.
http://www.rebar3.org
Apache License 2.0
1.7k stars 518 forks source link

While running dialyzer with rebar3，it consumes too much memory #2906

Closed williamweicode closed 3 months ago

williamweicode commented 3 months ago

While running dialyzer with rebar3，it consumes too much memory

image

===> Analyzing applications... ===> Compiling gpb ===> Compiling rebar3_gpb_plugin Rebar3 report version 3.22.1 generated at 2024-07-23T06:31:10+00:00 Please submit this along with your issue at https://github.com/erlang/rebar3/issues (and feel free to edit out private information, if any) Task: dialyzer Entered as: dialyzer Operating System: x86_64-pc-linux-gnu ERTS: Erlang/OTP 26 [erts-14.2] [source] [64-bit] [smp:16:16] [ds:16:16:10] [async-threads:1] [jit:ns] Root Directory: /opt/erlang/26.2 Library directory: /opt/erlang/26.2/lib Loaded Applications: bbmustache: 1.12.2 certifi: 2.11.0 cf: 0.3.1 common_test: 1.26 compiler: 8.4.1 crypto: 5.4 cth_readable: 1.5.1 dialyzer: 5.1.2 edoc: 1.2.1 erlware_commons: 1.6.0 eunit: 2.9 eunit_formatters: 0.5.0 getopt: 1.0.2 inets: 9.1 kernel: 9.2 providers: 1.9.0 public_key: 1.15 relx: 4.8.0 sasl: 4.2.1 snmp: 5.15 ssl_verify_fun: 1.1.6 stdlib: 5.2 syntax_tools: 3.1 tools: 3.6

Escript path: /home///***/rebar3 Providers: app_discovery as clean clean compile compile compile cover ct deps dialyzer do edoc escriptize eunit get-deps help install install_deps list lock new path pkgs release relup report repos shell state tar tree unlock update upgrade upgrade upgrade vendor version xref

rebar config: {dialyzer, [ {base_plt_apps, [erts, crypto, kernel, stdlib, mnesia, inets, runtime_tools, eunit]}, {warnings, [error_handling, unknown, no_return, no_unused]}, {plt_apps, all_deps} ]}.

cmd: ./rebar3 dialyzer --incremental

ferd commented 3 months ago

Dialyzer is implemented as part of the regular Erlang/OTP distribution at https://github.com/erlang/otp

We only call out to that code and can't do much about its memory usage.

Is the problem that you've run it in standalone mode and the version in rebar3 specifically uses more RAM, or is the complaint at Dialyzer in general?

williamweicode commented 3 months ago

It's Dialyzer's problem, I close this issue. Thanks!