wedeploy / cli

64%

master: 57%

LAST BUILD ON BRANCH memory-consumption

branch: memory-consumption

CHANGE BRANCH

x

Reset

• memory-consumption
• 0.4.0
• 1.7
• 2.3.x
• 276
• 3.0-nova
• 809-create-menus
• MDL-52990-email-themes
• NewSwagger
• api
• backend-otf
• charset-support
• containers-install
• desenv
• develop
• docs
• fix-deploy-failure
• fixes
• greenkeeper-karma-mocha-reporter-1.2.0
• improve-error-reporting
• issue23
• jag/mobile-header
• lint-settings
• master
• newlit
• npm-stuff
• pathmatch
• reducing-code-complexity
• run
• run-draft
• tc-sudo-travis
• terry
• tmp-run
• type
• update_measures
• v1.0.0-alpha-18
• v1.0.0-alpha-19
• v1.0.0-alpha-20
• v1.0.0-alpha-21
• v1.0.0-alpha-22
• v1.0.0-alpha-24
• v1.0.0-alpha-25
• v1.0.0-alpha.10
• v1.0.0-alpha.11
• v1.0.0-alpha.12
• v1.0.0-alpha.13
• v1.0.0-alpha.14
• v1.0.0-alpha.15
• v1.0.0-alpha.16
• v1.0.0-alpha.17
• v1.0.0-alpha.5
• v1.0.0-alpha.6
• v1.0.0-alpha.7
• v1.0.0-alpha.8
• v1.0.0-alpha.9
• v1.3.0
• v2.0.5
• version_features

Tentative fix for high memory consumption

From the reproduction case, I gathered that the issue might come from
the very long macro expansions chain that is involved in the generation
of picklers and unpicklers.

My idea to fix this issue is to consider only dependencies from a tree
to a symbol if and only if at least one of them is not synthetic.

A tree is considered synthetic iff its position if not a range (this
seems to be the criterion used in scalac).