Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug / Crash  Memory Leak
#1
Hey there,

We're using Obi 5.3,
Unity 2019.4.4f1
Windows 10

In Unity Editor it's not possible to see the memory leak in the profiler, 
only after building an exe it's possible to see it in the Task Manager.

Steps to reproduce:
1. Create a new empty scene(no need for even a camera in the room)
2. Create an empty GameObject
3. Add to the object both Components "Obi Fixed Updater" and "Obi Solver"
4. Build an exe
5. Run the exe and see its ram grows in the Task Manager

If you remove one of the components and rebuild it, it won't leak.

It's really critical to us, since it's a project that's going to be open for many hours, and with more than one solver... 
And we'd rather not having to restart it every once in a while.

I'm really out of ideas, so any help would be appreciated

Thanks Sonrisa
Reply
#2
(30-07-2020, 09:10 PM)TotahAmiti Wrote: Hey there,

We're using Obi 5.3,
Unity 2019.4.4f1
Windows 10

In Unity Editor it's not possible to see the memory leak in the profiler, 
only after building an exe it's possible to see it in the Task Manager.

Steps to reproduce:
1. Create a new empty scene(no need for even a camera in the room)
2. Create an empty GameObject
3. Add to the object both Components "Obi Fixed Updater" and "Obi Solver"
4. Build an exe
5. Run the exe and see its ram grows in the Task Manager

If you remove one of the components and rebuild it, it won't leak.

It's really critical to us, since it's a project that's going to be open for many hours, and with more than one solver... 
And we'd rather not having to restart it every once in a while.

I'm really out of ideas, so any help would be appreciated

Thanks Sonrisa

Hi there!

We've been unable to reproduce the leak, memory consumption stays constant in an executable for us. Can you provide a sample executable that reproduces this?
(you can send it to suppoort(at)virtualmethodstudio.com)

kind regards,
Reply
#3
(31-07-2020, 10:36 AM)josemendez Wrote: Hi there!

We've been unable to reproduce the leak, memory consumption stays constant in an executable for us. Can you provide a sample executable that reproduces this?
(you can send it to suppoort(at)virtualmethodstudio.com)

kind regards,

Hey, thanks Jose for your response.

Sure I will send it there.

Edit: sent it to obi(at)virtualmethodstudio.com
since it said support mail didn't exist.

Also if you can provide details where it wasn't reproduced I would love to know, we can maybe downgrade/upgrade Unity as a quick fix. Or run the server on different platform.
Reply
#4
(31-07-2020, 01:43 PM)TotahAmiti Wrote: Hey, thanks Jose for your response.

Sure I will send it there.

Edit: sent it to obi(at)virtualmethodstudio.com
since it said support mail didn't exist.

Also if you can provide details where it wasn't reproduced I would love to know, we can maybe downgrade/upgrade Unity as a quick fix. Or run the server on different platform.

Sorry, misspelled "support" in the email address.

I'm using Unity 2019.3.1f1 in macOS 10.15.4 and Windows 10. Will test your executable and get back to you asap.
Reply
#5
(31-07-2020, 03:08 PM)josemendez Wrote: Sorry, misspelled "support" in the email address.

I'm using Unity 2019.3.1f1 in macOS 10.15.4 and Windows 10. Will test your executable and get back to you asap.


Great, thanks!
Let me know if any additional details/samples are needed
Reply