2013년 10월 29일 화요일
2013년 10월 20일 일요일
2013년 8월 29일 목요일
2013년 8월 4일 일요일
헝그리 게임
"절대로 좀비처럼 돌아다니지 않을 꺼야."
"하지만 타이머를 이식받는 것은 몹쓸짓이지."
타이머 - 헝그리 바이러스에 의해 전염된 좀비가 되기 전에 일정시간동안 재충전을 하지 않으면 사망에 이르게 되는 장치. 치매 등에 대비하여 만듦.
헝그리 바이러스 - 2002년에 활성화된 바이러스로 히딩구가 대표적이며, 5년후에 가장 많이 발병함.
"하지만 타이머를 이식받는 것은 몹쓸짓이지."
타이머 - 헝그리 바이러스에 의해 전염된 좀비가 되기 전에 일정시간동안 재충전을 하지 않으면 사망에 이르게 되는 장치. 치매 등에 대비하여 만듦.
헝그리 바이러스 - 2002년에 활성화된 바이러스로 히딩구가 대표적이며, 5년후에 가장 많이 발병함.
2013년 7월 17일 수요일
2013년 6월 18일 화요일
warned by SolidWorks that their system resources are running low
Once any single process hits 10,000 GDI Objects, it’s terminated. This is the default limit defined by Windows that a single process can reach.
There’s a registry tweak that can change this; a single process can max out at 16,384, while the system wide max for all processes is 65,536; edit the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
registry key to change the per-process limit (GDIProcessHandleQuota) to the upper limit of 16,384; set the BASE to DECIMAL. This will buy you some breathing room.
** WARNING! – I recommend only making this change if you are very comfortable editing the Windows Registry. Accidental changes to the registry can render your system inoperable, so exercise extreme caution when making any registry edits. I strongly recommend creating a Windows Restore Point prior to performing any registry edits.
++++++++++
If it’s still crashing out at only 10,996 GDIs, then the crash isn’t likely due to the GDI objects ceiling being hit since you’ve just finished raising it to 16,384. You’re likely crashing out due to the Windows heap stack running out of resources. Unfortunately there’s no easy fix for that limitation until Windows 8 perhaps…
There’s a registry tweak that can change this; a single process can max out at 16,384, while the system wide max for all processes is 65,536; edit the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\GDIProcessHandleQuota
registry key to change the per-process limit (GDIProcessHandleQuota) to the upper limit of 16,384; set the BASE to DECIMAL. This will buy you some breathing room.
** WARNING! – I recommend only making this change if you are very comfortable editing the Windows Registry. Accidental changes to the registry can render your system inoperable, so exercise extreme caution when making any registry edits. I strongly recommend creating a Windows Restore Point prior to performing any registry edits.
++++++++++
If it’s still crashing out at only 10,996 GDIs, then the crash isn’t likely due to the GDI objects ceiling being hit since you’ve just finished raising it to 16,384. You’re likely crashing out due to the Windows heap stack running out of resources. Unfortunately there’s no easy fix for that limitation until Windows 8 perhaps…
피드 구독하기:
글 (Atom)