Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than ["path/to/blender.exe"] #109435

New Issue

Closed

opened 2023-06-28 11:56:02 +02:00 by Tristan-Languebien · 3 comments

Tristan-Languebien commented

2023-06-28 11:56:02 +02:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender crashes when calling ArgumentParser.parse_args() if sys.argv is anything other than ["path/to/blender.exe"]
I discovered this bug while trying to run a script using the exec() function. Any script that uses argparse makes blender crash.

Exact steps for others to reproduce the error
You can run this code

import argparse
import sys
import bpy

sys.argv = [bpy.app.binary_path]
sys.argv.append("--some_arg") # Comment this line and everything works fine

parser = argparse.ArgumentParser()
args = parser.parse_args()

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.18 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender crashes when calling `ArgumentParser.parse_args()` if `sys.argv` is anything other than `["path/to/blender.exe"]` I discovered this bug while trying to run a script using the `exec()` function. Any script that uses argparse makes blender crash. **Exact steps for others to reproduce the error** You can run this code ```Py import argparse import sys import bpy sys.argv = [bpy.app.binary_path] sys.argv.append("--some_arg") # Comment this line and everything works fine parser = argparse.ArgumentParser() args = parser.parse_args() ```

Tristan-Languebien added the

labels 2023-06-28 11:56:03 +02:00

Iliya Katushenock added the

label 2023-06-28 11:58:57 +02:00

YimingWu commented

2023-06-28 14:34:48 +02:00

Member

Huh I can crash it from text editor but not from python console in blender. Interesting.

if ran in python console args would just be Namespace()

>>> import argparse
>>> import sys
>>> import bpy
>>> sys.argv = [bpy.app.binary_path]
>>> parser = argparse.ArgumentParser()
>>> args = parser.parse_args()
>>> 
>>> args
Namespace()

Huh I can crash it from text editor but not from python console in blender. Interesting. if ran in python console `args` would just be `Namespace()` ```python >>> import argparse >>> import sys >>> import bpy >>> sys.argv = [bpy.app.binary_path] >>> parser = argparse.ArgumentParser() >>> args = parser.parse_args() >>> >>> args Namespace() ```

YimingWu added

and removed

labels 2023-06-28 14:36:12 +02:00

Mateusz Grzeliński commented

2023-07-12 21:49:28 +02:00

Member

I noticed some python events can shutdown blender. In console the error is caucht (but notice that executing it twice with arrow up causes sytax error. What?). So we probably have 2 bugs here.

>>> exit(1)
Traceback (most recent call last):
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\console_python.py", line 150, in execute
    is_multiline = console.push(line_exec)
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 258, in push
    more = self.runsource(source, self.filename)
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 74, in runsource
    self.runcode(code)
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 90, in runcode
    exec(code, self.locals)
  File "<blender_console>", line 1, in <module>
  File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\_sitebuiltins.py", line 26, in __call__
    raise SystemExit(code)
SystemExit: 1

>>> exit(1)
  File "<blender_console>", line 1
    exit(1)
           ^
SyntaxError: multiple statements found while compiling a single statement

Executing exit(123) in text editor in shutsdown blender with error code 123. That is actually pretty funny :)

The behaviour that you see is python library argparse "raising" an error by calling exit(2).
I will try to fix it, but it will take ma long-ish time.

I noticed some python events can shutdown blender. In console the error is caucht (but notice that executing it twice with arrow up causes sytax error. What?). So we probably have 2 bugs here. ```python >>> exit(1) Traceback (most recent call last): File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\scripts\modules\console_python.py", line 150, in execute is_multiline = console.push(line_exec) File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 258, in push more = self.runsource(source, self.filename) File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 74, in runsource self.runcode(code) File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\code.py", line 90, in runcode exec(code, self.locals) File "<blender_console>", line 1, in <module> File "C:\Program Files\Blender Foundation\Blender 3.3\3.3\python\lib\_sitebuiltins.py", line 26, in __call__ raise SystemExit(code) SystemExit: 1 >>> exit(1) File "<blender_console>", line 1 exit(1) ^ SyntaxError: multiple statements found while compiling a single statement ``` Executing `exit(123)` in text editor in shutsdown blender with error code 123. That is actually pretty funny :) The behaviour that you see is python library `argparse` "raising" an error by calling exit(2). I will try to fix it, but it will take ma long-ish time.

Campbell Barton referenced this issue from a commit

2024-01-16 07:19:27 +01:00

PyAPI: handle sys.exit() from the Python console

Campbell Barton commented

2024-01-16 07:24:52 +01:00

Owner

Calls to sys.exit will exit Blender, this isn't a crash but as this report shows, it can seem like a crash.

The argparse module is part of Python, in general if Python's own modules call sys.exit() this is not something Blender prevents.

If you want to override this you can sub-class argparse.ArgumentParser and an alternative exit method (see its documentation).

So I wouldn't consider this a bug.

The issue you mentioned with the Python console showing a stack trace then a syntax error for further input is a bug since the input from the previous command isn't cleared. Fixed: 489408e8d3.

Calls to sys.exit will exit Blender, this isn't a crash but as this report shows, it can seem like a crash. The `argparse` module is part of Python, in general if Python's own modules call sys.exit() this is not something Blender prevents. If you want to override this you can sub-class `argparse.ArgumentParser` and an alternative exit method (see its documentation). So I wouldn't consider this a bug. ---- The issue you mentioned with the Python console showing a stack trace then a syntax error for further input is a bug since the input from the previous command isn't cleared. Fixed: 489408e8d37a35b19d08354f880d00f85422d591.

Campbell Barton closed this issue

2024-01-16 07:24:56 +01:00

Blender Bot added

and removed

labels 2024-01-16 07:24:58 +01:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

4 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#109435

No description provided.