[MetinSeven_com]

Hi,

Whenever I'm rendering images (render size mostly 1600 x 1200 pixels) and use a number of other programs, such as Outlook and IE, Maxwell can have the tendency to suddenly crash after a while, regardless of which scene I'm rendering. This might be a memory allocation / management problem, I don't know about that, but I've got 2 GB RAM.

Cheers,

Metin

[Polyxo]

It propably sounds silly, but I encounter Maxwell-crashes, when M~R initializes a render while another program e.g. Mozilla is on top. As soon as I drag the browser-window to my second screen, all works fine.

I also have 2GB RAM.

Holger

[MetinSeven_com]

It feels like a memory management problem: whenever the -hd option is not used and too much memory is being allocated by other software, Maxwell becomes unstable?

[tom]

Metin, there were 2 similar problems reported here and I got their scenes and tested by myself here on different machines and I can't reproduce any crash they reported. So this is probably about your hardware/OS and other software configurations. So, I have to move this thread out of bug section since it has no exact definition of a reproducable crash.
Thank you for your understanding...

[MetinSeven_com]

Hi Tom,

That's ok, but please don't completely remove it. In stead move it to the Maxwell render section then, because it is a good thing the Maxwell developers triple-check the Maxwell renderer's memory management and know about crashes after rendering for a while and while using other software. A lot of users will need to use other software and if Maxwell is a fully stable entity with its own efficient memory allocation it shouldn't be affecting Maxwell when you're using other software and different configurations.

Cheers,

Metin

[Ric_535]

i only have 512 mb ram yet i have NEVER had maxwell crash during a render (now ive done it. its gonna crash on me next time DOH! , i always set the priority to below normal

PS - during maxwell renders i am usually rendering in C4D

[RonB]

I am on Lightwave and experience crashes after too many starts and stops for adjusting textures etc. How many is too many? I don't have a clue, but it seems that's the only thing I can put my finger on. I have had 3 scenes crash well into the render, say a few hours. I checked everything I can think of...models, textures, isolated points etc., all good...then restart and it renders fine??!! What I have gotten into doing now is restart after more than a couple adjustments...I still get anxious though.

[aitraaz]

Metin, there were 2 similar problems reported here and I got their scenes and tested by myself here on different machines and I can't reproduce any crash they reported. So this is probably about your hardware/OS and other software configurations. So, I have to move this thread out of bug section since it has no exact definition of a reproducable crash.
Thank you for your understanding...

ah ah ah....per ardua ad astra, eh, mate?

[jdp]

...per aspera ad astra

[MetinSeven_com]

Hee, waarom gaan jullie ineens in je eigen taal babbelen, hm?

[sms]

I recently encountered the same problem when I rendered an image at 3000 x 1500 resolution without the -hd option activated.

Maxwell allocated 680 MB for the render, I have 1.3 GB of RAM and did nothing else in the meantime that could eventually slow down rendering time

Then it rendered for a few hours and then Maxwell crashes. I was trying to resume the render after the crash but after a few minutes of rendering it crashes again. I think it must be a memory management problem, because when I rendered the same scene at 2000 x 1000 resolution it worked fine.

[manolito33]

I work with 1 gb ram and the same, if I reduce the resolution then work fine.