- 
          
 - 
                Notifications
    
You must be signed in to change notification settings  - Fork 33.7k
 
src: distinguish env stopping flags #45907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     Merged
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    | 
           Review requested: 
  | 
    
              
                    addaleax
  
              
              requested changes
              
                  
                    Dec 19, 2022 
                  
              
              
            
            
ac5ee86    to
    c7b4297      
    Compare
  
    `Environment::FreeEnvironment` creates a `DisallowJavascriptExecutionScope`, so the flag `Environment::can_call_into_js()` should also be set as `false`. As `Environment::can_call_into_js_` is a simple boolean flag, it should not be accessed off-threads.
c7b4297    to
    3d49eed      
    Compare
  
    
              
                    addaleax
  
              
              approved these changes
              
                  
                    Jan 5, 2023 
                  
              
              
            
            
              
                    mcollina
  
              
              approved these changes
              
                  
                    Jan 8, 2023 
                  
              
              
            
            
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've spent a bit of time trying to figure out those lines of code.
I'd be more comfortable with an added test for this change, but I agree it might be very hard to check.
  This was referenced Jan 11, 2023 
      
      
        
      
      
  
    19 tasks
  
| 
           Landed in bb40507  | 
    
  This was referenced Jan 15, 2023 
      
    
  RafaelGSS 
      pushed a commit
        to RafaelGSS/node
      that referenced
      this pull request
    
      Jan 17, 2023 
    
    
      
  
    
      
    
  
`Environment::FreeEnvironment` creates a `DisallowJavascriptExecutionScope`, so the flag `Environment::can_call_into_js()` should also be set as `false`. As `Environment::can_call_into_js_` is a simple boolean flag, it should not be accessed off-threads. PR-URL: nodejs#45907 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
    
  RafaelGSS 
      pushed a commit
      that referenced
      this pull request
    
      Jan 20, 2023 
    
    
      
  
    
      
    
  
`Environment::FreeEnvironment` creates a `DisallowJavascriptExecutionScope`, so the flag `Environment::can_call_into_js()` should also be set as `false`. As `Environment::can_call_into_js_` is a simple boolean flag, it should not be accessed off-threads. PR-URL: #45907 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
      
     Merged
  
    
  juanarbol 
      pushed a commit
      that referenced
      this pull request
    
      Jan 26, 2023 
    
    
      
  
    
      
    
  
`Environment::FreeEnvironment` creates a `DisallowJavascriptExecutionScope`, so the flag `Environment::can_call_into_js()` should also be set as `false`. As `Environment::can_call_into_js_` is a simple boolean flag, it should not be accessed off-threads. PR-URL: #45907 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
      
     Merged
  
    
  juanarbol 
      pushed a commit
      that referenced
      this pull request
    
      Jan 31, 2023 
    
    
      
  
    
      
    
  
`Environment::FreeEnvironment` creates a `DisallowJavascriptExecutionScope`, so the flag `Environment::can_call_into_js()` should also be set as `false`. As `Environment::can_call_into_js_` is a simple boolean flag, it should not be accessed off-threads. PR-URL: #45907 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Currently,
!env->can_call_into_js()andenv->is_stopping()have different semantics by their names. Theis_stopping()flag implies!env->can_call_into_js().However, this implication is not enforced in
Environment::FreeEnvironment.Environment::FreeEnvironmentcreates aDisallowJavascriptExecutionScope, the flagEnvironment::can_call_into_js()needs to be set asfalse.As
Environment::can_call_into_js_is a simple boolean flag, it should not be accessed off-thread. This also fixes an issue that the flagEnvironment::can_call_into_js_is been modified inEnvironment::ExitEnv, which may be called from other threads.