DistributeDefinitions is evaluating the definitions, and this only for a large number of definitions

Clash Royale CLAN TAG#URR8PPP
I am using Mathematica 11.3 and this seems to me to be a bug. I would like, if possible, some idea on a workaround.
Here is an example of a trivial code that works as expected:
nI = 10;
(NM[#] := Print[#] ) & /@ Range[1, nI];
LaunchKernels;
DistributeDefinitions[NM];
That is, the code above generates no output, as expected.
Now, if the first line is changed to
nI = 20;
The same code leads to 40 lines being printed! From 1 to 20 two times.
For some reason, the DistributeDefinitions is forcing the definition of NM to be executed, and I do not want that to happen before I use ParallelSubmit and WaitAll. I tried this in two computers with Mathematica 11.3, any ideas on what is happening?
bugs parallelization internals
|
show 1 more comment
I am using Mathematica 11.3 and this seems to me to be a bug. I would like, if possible, some idea on a workaround.
Here is an example of a trivial code that works as expected:
nI = 10;
(NM[#] := Print[#] ) & /@ Range[1, nI];
LaunchKernels;
DistributeDefinitions[NM];
That is, the code above generates no output, as expected.
Now, if the first line is changed to
nI = 20;
The same code leads to 40 lines being printed! From 1 to 20 two times.
For some reason, the DistributeDefinitions is forcing the definition of NM to be executed, and I do not want that to happen before I use ParallelSubmit and WaitAll. I tried this in two computers with Mathematica 11.3, any ideas on what is happening?
bugs parallelization internals
2
On my machine the behaviour changes fromnI=17 to 18. If I look atDefinitions[NM], up to 17 it prints as:=-definitions, but above that it prints as=-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.
– Szabolcs
Dec 28 '18 at 20:58
2
The reason appears to be thatLanguage`ExtendedFullDefinitionswitches from usingRuleDelayedtoRuleafter 18 down-values. This causesDistributeDefinitionsto subsequently leak the evaluation.
– Lukas Lang
Dec 28 '18 at 20:58
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
1
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23
|
show 1 more comment
I am using Mathematica 11.3 and this seems to me to be a bug. I would like, if possible, some idea on a workaround.
Here is an example of a trivial code that works as expected:
nI = 10;
(NM[#] := Print[#] ) & /@ Range[1, nI];
LaunchKernels;
DistributeDefinitions[NM];
That is, the code above generates no output, as expected.
Now, if the first line is changed to
nI = 20;
The same code leads to 40 lines being printed! From 1 to 20 two times.
For some reason, the DistributeDefinitions is forcing the definition of NM to be executed, and I do not want that to happen before I use ParallelSubmit and WaitAll. I tried this in two computers with Mathematica 11.3, any ideas on what is happening?
bugs parallelization internals
I am using Mathematica 11.3 and this seems to me to be a bug. I would like, if possible, some idea on a workaround.
Here is an example of a trivial code that works as expected:
nI = 10;
(NM[#] := Print[#] ) & /@ Range[1, nI];
LaunchKernels;
DistributeDefinitions[NM];
That is, the code above generates no output, as expected.
Now, if the first line is changed to
nI = 20;
The same code leads to 40 lines being printed! From 1 to 20 two times.
For some reason, the DistributeDefinitions is forcing the definition of NM to be executed, and I do not want that to happen before I use ParallelSubmit and WaitAll. I tried this in two computers with Mathematica 11.3, any ideas on what is happening?
bugs parallelization internals
bugs parallelization internals
edited Jan 2 at 18:07
Davi Rodrigues
asked Dec 28 '18 at 20:00
Davi RodriguesDavi Rodrigues
1728
1728
2
On my machine the behaviour changes fromnI=17 to 18. If I look atDefinitions[NM], up to 17 it prints as:=-definitions, but above that it prints as=-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.
– Szabolcs
Dec 28 '18 at 20:58
2
The reason appears to be thatLanguage`ExtendedFullDefinitionswitches from usingRuleDelayedtoRuleafter 18 down-values. This causesDistributeDefinitionsto subsequently leak the evaluation.
– Lukas Lang
Dec 28 '18 at 20:58
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
1
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23
|
show 1 more comment
2
On my machine the behaviour changes fromnI=17 to 18. If I look atDefinitions[NM], up to 17 it prints as:=-definitions, but above that it prints as=-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.
– Szabolcs
Dec 28 '18 at 20:58
2
The reason appears to be thatLanguage`ExtendedFullDefinitionswitches from usingRuleDelayedtoRuleafter 18 down-values. This causesDistributeDefinitionsto subsequently leak the evaluation.
– Lukas Lang
Dec 28 '18 at 20:58
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
1
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23
2
2
On my machine the behaviour changes from
nI=17 to 18. If I look at Definitions[NM], up to 17 it prints as :=-definitions, but above that it prints as =-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.– Szabolcs
Dec 28 '18 at 20:58
On my machine the behaviour changes from
nI=17 to 18. If I look at Definitions[NM], up to 17 it prints as :=-definitions, but above that it prints as =-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.– Szabolcs
Dec 28 '18 at 20:58
2
2
The reason appears to be that
Language`ExtendedFullDefinition switches from using RuleDelayed to Rule after 18 down-values. This causes DistributeDefinitions to subsequently leak the evaluation.– Lukas Lang
Dec 28 '18 at 20:58
The reason appears to be that
Language`ExtendedFullDefinition switches from using RuleDelayed to Rule after 18 down-values. This causes DistributeDefinitions to subsequently leak the evaluation.– Lukas Lang
Dec 28 '18 at 20:58
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
1
1
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23
|
show 1 more comment
2 Answers
2
active
oldest
votes
TL;DR;
Execute the following code to fix the problem:
DistributeDefinitions;
DownValues[Parallel`Protected`DistDefs] =
DownValues[Parallel`Protected`DistDefs] /.
HoldPattern[
u : Parallel`Parallel`Private`updates =
rhs_Language`ExtendedFullDefinition
] :>
(
u = Replace[
rhs,
defs : (_HoldPattern -> _) .. :> With[
res = RuleDelayed @@@ Unevaluated@defs,
res /; True
],
4
]
);
What does this do?
As mentioned in the comments, the issue is that Language`ExtendedFullDefinition seems to change the return format at 18 down-values. This causes the subsequent manipulations of DistributeDefinitions on the returned Language`DefinitionList[…] expression to leak the evaluation of the definitions (as their r.h.s. are no longer protected by the HoldRest attribute of RuleDelayed).
The code above fixes this by wrapping the call to Language`ExtendedFullDefinition (which happens in Parallel`Protected`DistDefs) with a piece of code that replaces definitions of the form HoldPattern[…]->… with HoldPattern[…]:>…, which prevents the evaluation leak.
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions usingRulewith ones usingRuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affectDistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know
– Lukas Lang
Dec 29 '18 at 16:00
add a comment |
When dealing with a larger number of definitions my recommendation is to disable the automatic distribution of definitions with
$DistributedContexts = None
and simply redo the definitions on all parallel kernels:
nI = 20;
(NM[#] := Print[#]) & /@ Range[1, nI];
With[nI = nI, ParallelEvaluate[(NM[#] := Print[#])& /@ Range[1, nI];]]
It's faster, too.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("mathjaxEditing", function ()
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
);
);
, "mathjax-editing");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "387"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmathematica.stackexchange.com%2fquestions%2f188517%2fdistributedefinitions-is-evaluating-the-definitions-and-this-only-for-a-large-n%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
TL;DR;
Execute the following code to fix the problem:
DistributeDefinitions;
DownValues[Parallel`Protected`DistDefs] =
DownValues[Parallel`Protected`DistDefs] /.
HoldPattern[
u : Parallel`Parallel`Private`updates =
rhs_Language`ExtendedFullDefinition
] :>
(
u = Replace[
rhs,
defs : (_HoldPattern -> _) .. :> With[
res = RuleDelayed @@@ Unevaluated@defs,
res /; True
],
4
]
);
What does this do?
As mentioned in the comments, the issue is that Language`ExtendedFullDefinition seems to change the return format at 18 down-values. This causes the subsequent manipulations of DistributeDefinitions on the returned Language`DefinitionList[…] expression to leak the evaluation of the definitions (as their r.h.s. are no longer protected by the HoldRest attribute of RuleDelayed).
The code above fixes this by wrapping the call to Language`ExtendedFullDefinition (which happens in Parallel`Protected`DistDefs) with a piece of code that replaces definitions of the form HoldPattern[…]->… with HoldPattern[…]:>…, which prevents the evaluation leak.
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions usingRulewith ones usingRuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affectDistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know
– Lukas Lang
Dec 29 '18 at 16:00
add a comment |
TL;DR;
Execute the following code to fix the problem:
DistributeDefinitions;
DownValues[Parallel`Protected`DistDefs] =
DownValues[Parallel`Protected`DistDefs] /.
HoldPattern[
u : Parallel`Parallel`Private`updates =
rhs_Language`ExtendedFullDefinition
] :>
(
u = Replace[
rhs,
defs : (_HoldPattern -> _) .. :> With[
res = RuleDelayed @@@ Unevaluated@defs,
res /; True
],
4
]
);
What does this do?
As mentioned in the comments, the issue is that Language`ExtendedFullDefinition seems to change the return format at 18 down-values. This causes the subsequent manipulations of DistributeDefinitions on the returned Language`DefinitionList[…] expression to leak the evaluation of the definitions (as their r.h.s. are no longer protected by the HoldRest attribute of RuleDelayed).
The code above fixes this by wrapping the call to Language`ExtendedFullDefinition (which happens in Parallel`Protected`DistDefs) with a piece of code that replaces definitions of the form HoldPattern[…]->… with HoldPattern[…]:>…, which prevents the evaluation leak.
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions usingRulewith ones usingRuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affectDistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know
– Lukas Lang
Dec 29 '18 at 16:00
add a comment |
TL;DR;
Execute the following code to fix the problem:
DistributeDefinitions;
DownValues[Parallel`Protected`DistDefs] =
DownValues[Parallel`Protected`DistDefs] /.
HoldPattern[
u : Parallel`Parallel`Private`updates =
rhs_Language`ExtendedFullDefinition
] :>
(
u = Replace[
rhs,
defs : (_HoldPattern -> _) .. :> With[
res = RuleDelayed @@@ Unevaluated@defs,
res /; True
],
4
]
);
What does this do?
As mentioned in the comments, the issue is that Language`ExtendedFullDefinition seems to change the return format at 18 down-values. This causes the subsequent manipulations of DistributeDefinitions on the returned Language`DefinitionList[…] expression to leak the evaluation of the definitions (as their r.h.s. are no longer protected by the HoldRest attribute of RuleDelayed).
The code above fixes this by wrapping the call to Language`ExtendedFullDefinition (which happens in Parallel`Protected`DistDefs) with a piece of code that replaces definitions of the form HoldPattern[…]->… with HoldPattern[…]:>…, which prevents the evaluation leak.
TL;DR;
Execute the following code to fix the problem:
DistributeDefinitions;
DownValues[Parallel`Protected`DistDefs] =
DownValues[Parallel`Protected`DistDefs] /.
HoldPattern[
u : Parallel`Parallel`Private`updates =
rhs_Language`ExtendedFullDefinition
] :>
(
u = Replace[
rhs,
defs : (_HoldPattern -> _) .. :> With[
res = RuleDelayed @@@ Unevaluated@defs,
res /; True
],
4
]
);
What does this do?
As mentioned in the comments, the issue is that Language`ExtendedFullDefinition seems to change the return format at 18 down-values. This causes the subsequent manipulations of DistributeDefinitions on the returned Language`DefinitionList[…] expression to leak the evaluation of the definitions (as their r.h.s. are no longer protected by the HoldRest attribute of RuleDelayed).
The code above fixes this by wrapping the call to Language`ExtendedFullDefinition (which happens in Parallel`Protected`DistDefs) with a piece of code that replaces definitions of the form HoldPattern[…]->… with HoldPattern[…]:>…, which prevents the evaluation leak.
answered Dec 28 '18 at 21:40
Lukas LangLukas Lang
6,5001930
6,5001930
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions usingRulewith ones usingRuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affectDistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know
– Lukas Lang
Dec 29 '18 at 16:00
add a comment |
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions usingRulewith ones usingRuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affectDistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know
– Lukas Lang
Dec 29 '18 at 16:00
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
It worked, thanks! I think this is a terrible Mathematica bug, since no "hack" should be necessary to demand the same behaviour from nI=17 to nI=18. Although the code above works, I am worried if it will not have side effects. That is, can i simply insert it in my init.m file and always use it?
– Davi Rodrigues
Dec 29 '18 at 15:54
1
1
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions using
Rule with ones using RuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affect DistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know– Lukas Lang
Dec 29 '18 at 16:00
Yes, stuff like this is really annoying... Regarding potential side effects: As far as I can tell, the fix should be completely safe: The only thing it does is to replace the definitions using
Rule with ones using RuleDelayed, which is definitely supported (since it is what happens for less than 18 definitions). It is also a very localized modification, so it should only affect DistributeDefinitions, which is anyway half broken for more than 17 definitions. But in case you do encounter any issues, please let me know– Lukas Lang
Dec 29 '18 at 16:00
add a comment |
When dealing with a larger number of definitions my recommendation is to disable the automatic distribution of definitions with
$DistributedContexts = None
and simply redo the definitions on all parallel kernels:
nI = 20;
(NM[#] := Print[#]) & /@ Range[1, nI];
With[nI = nI, ParallelEvaluate[(NM[#] := Print[#])& /@ Range[1, nI];]]
It's faster, too.
add a comment |
When dealing with a larger number of definitions my recommendation is to disable the automatic distribution of definitions with
$DistributedContexts = None
and simply redo the definitions on all parallel kernels:
nI = 20;
(NM[#] := Print[#]) & /@ Range[1, nI];
With[nI = nI, ParallelEvaluate[(NM[#] := Print[#])& /@ Range[1, nI];]]
It's faster, too.
add a comment |
When dealing with a larger number of definitions my recommendation is to disable the automatic distribution of definitions with
$DistributedContexts = None
and simply redo the definitions on all parallel kernels:
nI = 20;
(NM[#] := Print[#]) & /@ Range[1, nI];
With[nI = nI, ParallelEvaluate[(NM[#] := Print[#])& /@ Range[1, nI];]]
It's faster, too.
When dealing with a larger number of definitions my recommendation is to disable the automatic distribution of definitions with
$DistributedContexts = None
and simply redo the definitions on all parallel kernels:
nI = 20;
(NM[#] := Print[#]) & /@ Range[1, nI];
With[nI = nI, ParallelEvaluate[(NM[#] := Print[#])& /@ Range[1, nI];]]
It's faster, too.
answered Jan 3 at 15:42
RomanRoman
36134
36134
add a comment |
add a comment |
Thanks for contributing an answer to Mathematica Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmathematica.stackexchange.com%2fquestions%2f188517%2fdistributedefinitions-is-evaluating-the-definitions-and-this-only-for-a-large-n%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
On my machine the behaviour changes from
nI=17 to 18. If I look atDefinitions[NM], up to 17 it prints as:=-definitions, but above that it prints as=-definitions. Thus the core issue may be not with the parallel tools, but with how definitions are stored.– Szabolcs
Dec 28 '18 at 20:58
2
The reason appears to be that
Language`ExtendedFullDefinitionswitches from usingRuleDelayedtoRuleafter 18 down-values. This causesDistributeDefinitionsto subsequently leak the evaluation.– Lukas Lang
Dec 28 '18 at 20:58
Can you please report this to Wolfram support?
– Szabolcs
Dec 31 '18 at 15:55
1
Thanks for the suggestion. I already sent an email to wolfram support, I am wating for their reply.
– Davi Rodrigues
Jan 1 at 16:08
OK, let us know what they said. I expect responses may be slow due to the backlog built up during the holiday season.
– Szabolcs
Jan 2 at 18:23