[Django] #27766: runserver crashes because of auto-reloader (Py3 + PowerShell)
Django
-----------------------------------------+------------------------
Reporter: oTree-org | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Repro steps:
- Install Python 3.x (doesn't happen on 2.x)
- Open Windows PowerShell (only happens with PowerShell, not CMD or bash)
- `pip install django`
- `django-admin startproject foobar`
- `cd foobar`
- `python manage.py runserver`
This causes a Windows crash with a window that says: "Python has stopped
working": http://imgur.com/dOt6eKE
However, `python manage.py runserver --noreload` works fine, so it seems
related to the auto-reloader.
I have seen it happen with at least 5 people using Py3 & PowerShell, with
Windows 8 or 10, and various PC models. (Though most people seem
unaffected.)
Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also.
--
Ticket URL: <https://code.djangoproject.com/ticket/27766>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: oTree-org | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.10
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by oTree-org:
Old description:
> Repro steps:
>
> - Install Python 3.x (doesn't happen on 2.x)
> - Open Windows PowerShell (only happens with PowerShell, not CMD or bash)
> - `pip install django`
> - `django-admin startproject foobar`
> - `cd foobar`
> - `python manage.py runserver`
>
> This causes a Windows crash with a window that says: "Python has stopped
> working": http://imgur.com/dOt6eKE
>
> However, `python manage.py runserver --noreload` works fine, so it seems
> related to the auto-reloader.
>
> I have seen it happen with at least 5 people using Py3 & PowerShell, with
> Windows 8 or 10, and various PC models. (Though most people seem
> unaffected.)
>
> Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also.
New description:
Repro steps:
- Install Python 3.x (doesn't happen on 2.x)
- Open Windows PowerShell (only happens with PowerShell, not CMD or bash)
- `pip install django`
- `django-admin startproject foobar`
- `cd foobar`
- `python manage.py runserver`
This causes a Windows crash with a window that says: "Python has stopped
working": http://imgur.com/dOt6eKE
However, `python manage.py runserver --noreload` works fine, so it seems
related to the auto-reloader.
Here is the info from the Windows Event Viewer:
{{{
Faulting application name: python.exe, version: 3.5.1150.1013
Faulting module name: ucrtbase.dll, version: 10.0.14393.0
Exception code: 0xc0000005
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
}}}
I have seen it happen with at least 5 people using Py3 & PowerShell, with
Windows 8 or 10, and various PC models. (Though most people seem
unaffected.)
Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:1>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* type: Uncategorized => Bug
* component: Uncategorized => Utilities
Comment:
To accept the ticket, we need an explanation of why Django (and not, for
example, Python or PowerShell) is at fault. In similar tickets, (#27657,
#27586) no one has been able to provide that.
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:2>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:3>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 1.10
Severity: Normal | Resolution:
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by urbanit):
* status: closed => new
* resolution: needsinfo =>
Comment:
Same situation here, windows 10 pro 1607 // pyhton 3.6 // Django 1.10.5
Thanks @oTree-org for the workaround with --noreload
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:4>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
Comment:
As I said before, "To accept the ticket, we need an explanation of why
Django (and not, for example, Python or PowerShell) is at fault." Please
don't reopen the ticket without that explanation.
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:5>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by oTree-org:
Old description:
> Repro steps:
>
> - Install Python 3.x (doesn't happen on 2.x)
> - Open Windows PowerShell (only happens with PowerShell, not CMD or bash)
> - `pip install django`
> - `django-admin startproject foobar`
> - `cd foobar`
> - `python manage.py runserver`
>
> This causes a Windows crash with a window that says: "Python has stopped
> working": http://imgur.com/dOt6eKE
>
> However, `python manage.py runserver --noreload` works fine, so it seems
> related to the auto-reloader.
>
> Here is the info from the Windows Event Viewer:
>
>
> {{{
> Faulting application name: python.exe, version: 3.5.1150.1013
> Faulting module name: ucrtbase.dll, version: 10.0.14393.0
> Exception code: 0xc0000005
> Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
>
> }}}
>
> I have seen it happen with at least 5 people using Py3 & PowerShell, with
> Windows 8 or 10, and various PC models. (Though most people seem
> unaffected.)
>
>
> Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also.
New description:
@urbanit: I think this may be related:
https://youtrack.jetbrains.com/issue/PY-17069#comment=27-1804561&tab=Comments
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:6>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Description changed by oTree-org:
Old description:
> @urbanit: I think this may be related:
> https://youtrack.jetbrains.com/issue/PY-17069#comment=27-1804561&tab=Comments
New description:
Repro steps:
- Install Python 3.x (doesn't happen on 2.x)
- Open Windows PowerShell (only happens with PowerShell, not CMD or bash)
- `pip install django`
- `django-admin startproject foobar`
- `cd foobar`
- `python manage.py runserver`
This causes a Windows crash with a window that says: "Python has stopped
working": http://imgur.com/dOt6eKE
However, `python manage.py runserver --noreload` works fine, so it seems
related to the auto-reloader.
Here is the info from the Windows Event Viewer:
{{{
Faulting application name: python.exe, version: 3.5.1150.1013
Faulting module name: ucrtbase.dll, version: 10.0.14393.0
Exception code: 0xc0000005
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
}}}
I have seen it happen with at least 5 people using Py3 & PowerShell, with
Windows 8 or 10, and various PC models. (Though most people seem
unaffected.)
Occurs with Django 1.8/1.10 and Python 3.5/3.6, maybe others also.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:7>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by oTree-org):
@urbanit: I think this issue is related:
https://youtrack.jetbrains.com/issue/PY-17069#comment=27-1804561&tab=Comments
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:8>
Django
Reporter: oTree-org | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 1.10
Severity: Normal | Resolution: needsinfo
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by David O'Connor):
Same issue, with both Powershell and PyCharm. Sorry, can't confirm if the
bug lies with Django, or Powershell and Pycharm.
--
Ticket URL: <https://code.djangoproject.com/ticket/27766#comment:9>