I experience this error when running my app with the new rapid debugging (when running with legacy debugging all is fine):
java.lang.OutOfMemoryError: Java heap space
Unfortunately I can't post my code because the app connects to a back-end application that provides it with data via web services and it is during the import phase of around 30 tables that the app crashes.
So my question is - is it normal for the rapid debugger to use more memory than legacy? I'm trying to establish whether there is a bug in the framework or whether it's just something I'm doing in my app that is not rapid debug-friendly
java.lang.OutOfMemoryError: Java heap space
Unfortunately I can't post my code because the app connects to a back-end application that provides it with data via web services and it is during the import phase of around 30 tables that the app crashes.
So my question is - is it normal for the rapid debugger to use more memory than legacy? I'm trying to establish whether there is a bug in the framework or whether it's just something I'm doing in my app that is not rapid debug-friendly