Page MenuHome
Create Task
Maniphest T76283

"Not Responding" upon trying to do anything on Big files
Closed, ArchivedPublic
Actions

Description

System Information
My Powerspec PC INFO
Device Speifications
Device Name: CurtisAMay-PC
Processor: Intel(R) Core(TM) i3-4340 CPU @ 3.60GHz 3.60GHz
Graphics: Intel(R) HD Graphics 4600
Installed RAM: 4.00 GB (3.83 GB usable)
Device ID: F7193C75-337F-44BE-A446-4A125F371E44
Product ID: 00330 80000 00000 AA039
System Type: 64-bit operating system - x64 based processor
Pen & Touch: No pen and touch is available for this display

Windows Specifications
Edition: Windows 10 Pro
Version: 1909
Installed On: 2/22/2020
OS Build: 18363.778

Support
Manufacturer: Micro Electronics Inc.
Phone: (614) 850-3670
Website: https://www.microcenter.com

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: rB375c7dc4caf4
Worked: (optional)

Short description of error "NOT RESPONDING"

Exact steps for others to reproduce the error
Every time I try to do anything to add to or change, duplicate, move, call up a menu, the program shows "NOT RESPONDING" and then it takes about a minute or five to complete the action. Sometimes the program goes whitish, and sometimes the program goes black, and sometimes the program blinks off and back on

Log_Cabin19.blend1 GBDownload

Log_Cabin19.blend11 GBDownload

Event Timeline

Curtis May (akcamay) created this task.May 1 2020, 3:00 AM
Ankit Meel (ankitm) renamed this task from Not Responding to "Not Responding" upon trying to do anything on Big files.May 1 2020, 8:21 AM
Ankit Meel (ankitm) added a subscriber: Ankit Meel (ankitm).EditedMay 2 2020, 10:44 AM

Installed RAM: 4.00 GB (3.83 GB usable)

4 GB is the minimum requirement as per https://www.blender.org/download/requirements/
If the same file works fine on a PC with more RAM, I think it's not a bug.
same if smaller files work on yours.

Ankit Meel (ankitm) closed this task as Archived.May 2 2020, 12:51 PM
Ankit Meel (ankitm) claimed this task.

with low RAM, I suggest using smaller files, and closing other memory intensive tasks.
If the issue persists, do comment. We'd reopen the task.