Issue 214 in glassdb: Seaside3.0 full stack continuation has Semaphore references

Status: Accepted
Owner: [hidden email]
Labels: Type-Defect Priority-Medium GLASS-Server Version-3.0.x  
Milestone-1.0-beta.8.6

New issue 214 by [hidden email]: Seaside3.0 full stack continuation has  
Semaphore references
http://code.google.com/p/glassdb/issues/detail?id=214

In GemStone3.0, the full continuation has references to Semaphores on the  
stack, so the continuation cannot be persisted. Relatively recent  
development.

In GemStone3.0, at least the references to objects that cannot be persisted  
are easy to find with Repository>>listReferencesInMemory:

The references are from variable contexts ...

Comment #1 on issue 214 by [hidden email]: Seaside3.0 full stack  
continuation has Semaphore references
http://code.google.com/p/glassdb/issues/detail?id=214

To reproduce, run the WAExceptionFunctionalTest with a  
WARemoteDebuggingWalkbackErrorHandler

Updates:
        Status: Fixed
        Labels: Fixed-1.0-beta.8.6

Comment #2 on issue 214 by [hidden email]: Seaside3.0 full stack  
continuation has Semaphore references
http://code.google.com/p/glassdb/issues/detail?id=214

Turns out that TransientRecursionLock>>critical: had been optimized to  
store Semaphore references in a temp (instead of sending messages)  
resulting in the persistent reference to the Semaphore ... clean up that  
method and rewrite TransientSemaphore>>critical: to eliminate temp  
references there as well.


Name: Bootstrap.v3-DaleHenrichs.202
Author: DaleHenrichs
Time: 01/20/2011, 11:02:30
UUID: c326b1ae-9c76-4f05-b034-78c43241b7a5
Ancestors: Bootstrap.v3-DaleHenrichs.201