Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • B bjgf
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
  • Jira
    • Jira
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • BlueJ
  • bjgf
  • Issues
  • #2115
Closed
Open
Issue created Jul 31, 2018 by Davin McCall@davmacMaintainer

[GREENFOOT-784] Large worlds cause exception

Worlds beyond a certain size cause an exception because the inter-VM communications buffer is fixed size (around 10MB I think).

{code} Exception in thread "Thread-7" java.nio.BufferOverflowException at java.nio.Buffer.nextPutIndex(Buffer.java:521) at java.nio.DirectIntBufferS.put(DirectIntBufferS.java:297) at greenfoot.vmcomm.VMCommsSimulation.doInterVMComms(VMCommsSimulation.java:364) at greenfoot.vmcomm.VMCommsSimulation.access$000(VMCommsSimulation.java:51) at greenfoot.vmcomm.VMCommsSimulation$1.run(VMCommsSimulation.java:172) {code}

We might want to raise the current size to at least 20MB (which allows 2000x2000 and a little bit larger world size), or have a dynamic size. If we choose to have a fixed limit, whether we increase it from the current or not, there should be a suitable exception (with message) thrown by the world constructor, rather than having this internal failure.


Issue metadata

  • Issue type: Bug
  • Priority: Medium
  • Fix versions: 3.5.1
Assignee
Assign to
Time tracking