#Crash Report

1 messages · Page 1 of 1 (latest)

rocky oysterBOT
#

@nimble herald uploaded a log, I get this crash when I try to import a large schematic, should I be crashing this easily?

  • Fabric 0.14.24 on 1.20.2

Recommendations:

  • Unless you know what you're doing, modifying your JVM args could have unintended side effects. It's best to use the defaults.
  • Update Fabric API from 0.90.4+1.20.2 to 0.90.7
bitter harbor
#

Can you send the schematic?

#

Interestingly Axiom is nowhere to be found in the stacktrace

nimble herald
#

Uhm can I DM it pls cos it's commercial work

bitter harbor
#

Yes DM is fine

nimble herald
#

That's odd, so is there a reason I crash so easily when doing larger stuff with Axiom?

#

Unless you know what you're doing, modifying your JVM args could have unintended side effects. It's best to use the defaults. what does this mean?

bitter harbor
#

Ignore that

bitter harbor
nimble herald
#

Oh hmmm

bitter harbor
#

@nimble herald I mainly just want to see if it can load the blueprint

nimble herald
#

Cos ofc I've already been having the crash issue since forever

#

Alr

bitter harbor
#

Could you maybe try without lithium?

nimble herald
#

Sure

nimble herald
#

After like a minute of (not responding)

bitter harbor
#

Do you normally experience these kinds of issues (unrelated to Axiom)?

nimble herald
#

No

#

As we've discussed before, I am able to do large scale things with World Edit

#

I saved the schem with WE in the first place

nimble herald
#

Oh, now the same out of memory message

#

Do I need to allocate more memory?

bitter harbor
#

Yeah I'd try doing that

nimble herald
#

How much should I be allocating? I've never messed with it before

bitter harbor
#

Try 8gb

#

Or 8192m

nimble herald
#

Wow

#

That worked

#

So it was just memory this whole time

bitter harbor
#

Guess it must have been right on the edge of using 4gb

nimble herald
#

Thanks for helping out!

bitter harbor
#

The way that I store blocks in your clipboard is a little bit inefficient in terms of memory

#

Could probably be improved by 75%, but the problem is that would slow down various other stuff for smaller regions

#

So realistically I should make it so that it uses the less memory-efficient but faster system for small regions & the more memory-efficient but slower system for large regions