Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Bug Reporting => [Max] Resolved Bugs => Topic started by: adamadam on 2016-11-30, 17:18:52

Title: Internal error - Bad Allocation
Post by: adamadam on 2016-11-30, 17:18:52

Error report from clipboard:

===== Error(3) =====
Internal error. Please report it at https://corona-renderer.com/link/2001:
Bad allocation
Wanted to allocate: 346MB
Used virtual memory: 47013MB
Total virtual memory: 47018MB

Stack trace:
 6 Corona::preAssert  0x7ff9bacc8540
 5 Corona::coronaMalloc  0x7ff9bacc9510
 4 Corona::PropertyDescriptor::getNth  0x7ff9a5ccc9b0
 3 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 2 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 1 Corona::IFrameBuffer::ExrStats::fromString  0x7ff9a5dbfca0
 0 CanAutoDefer  0x7ff9baa57aa0


This popped up at render time. It's possible it's something else than Corona because my whole system is flaking out (Photoshop just took about 5mins to launch after first crashing out) but I'm still reporting it because the error box asked me to :)

Windows 10, Max 2017, Corona 1.5 hotfix 2

Title: Re: Internal error - Bad Allocation
Post by: Ondra on 2016-11-30, 17:56:09

well... you are out of RAM ;) even though not all RAM is currently being used, it is already allocated (also including page file). One solution would be to increase page file. But I would like to see the scene to determine why so much RAM was allocated without it being used. It may be also other process in windows... if it happens again, you can try displaying column "commit size" in task manager to see which application took all your RAM.

Title: Re: Internal error - Bad Allocation
Post by: adamadam on 2016-11-30, 18:05:04

0_o

I've not seen the commit size thing before.

If it happens again (seems OK for now) I'll send scene and more details.

Thanks Ondra.

Title: Re: Internal error - Bad Allocation
Post by: Ondra on 2016-11-30, 18:43:54

it is visible in the task manager window (*thank you* for screenshotting correct tab of task manager ;)) - either though you have only 11.6/32 GB of memory used (which means that the operating system decided to keep 11.6 GB of data in the physical RAM because some application touched it recently), you have 45.9/45.9 commited. This means that applications requested to use 46GB RAM total (but did not actually get to using it, which is why the memory usage is lower).

Title: Re: Internal error - Bad Allocation
Post by: Ondra on 2017-03-21, 15:45:22

ok, let us know if you have more info, I am moving this to resolved in mean time