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
If I run test-server in one terminal and node test.js in another, I expect to immediately see "Destroying a GraultImpl` in the first terminal output. Instead, that does not get printed until I ctrl-c the javascript program.
The problem is observable in Sandstorm's proxy.js, which keeps a pipeline cap of newSession().session and calls close() on it when the proxy closes. @mrdomino noticed that this does not actually cause the websession object in the grain to be dropped immediately.
The text was updated successfully, but these errors were encountered:
It does appear, however, that the remote object does eventually get dropped due to garbage collection. If I run the following client (with node --expose-gc), then the GraultImpl does get dropped right away:
Similar to #4.
If I run
test-server
in one terminal andnode test.js
in another, I expect to immediately see "Destroying a GraultImpl` in the first terminal output. Instead, that does not get printed until I ctrl-c the javascript program.The problem is observable in Sandstorm's proxy.js, which keeps a pipeline cap of
newSession().session
and callsclose()
on it when the proxy closes. @mrdomino noticed that this does not actually cause the websession object in the grain to be dropped immediately.The text was updated successfully, but these errors were encountered: