Sorry for the late reply. I have informed this issue to our support team and it might be a RAM issue.
It would be helpful if you could upload your backup file, the marginpkg format.
Regarding this issue, if you wish to let us have a look of your mnpkg file, please send an email with your file to service@marginnote.com , with “To QSD” as title and paste the website of this post in the body.
As the export works from us here, my personal guess is that the chip of your device cannot withstand such great data process so it crushed. As suggested before, it could be an RAM issue.
What I could only suggest here is to turn your iPad off and on again and do not open other software while exporting this. Perhaps by doing this your export can be successful.
Also, we would be very appreciated if in the future you could send us only the Notebook you encountered some error, rather than the entire backup. To do this, please open your Notebook, click the share button (at top) and choose “Export Marginnote Backup File”.
BTW: the exported outline looks completely broken. The excerpts are all cut etc.
Did something change in the recent version?
I have used Outline until now to generate my own compiled version of a book… I can’t go back in version now
Hi. Could you specifically identify the exact Notebook with which you encounter a trouble?
Again, we would appreciate it if you could send us the exact backup file (you can export it just above where you export in PDF Format). It is currently difficult to identify the exact file among your 6GB total backup… .
Also, it might be helpful if you could try to dragging rect to select the cards you wish to export
I will open a different thread. This is a further bug/unexpected behavior/feature regression with the newest version I can reproduce and provide a video for. @QSD_Support-Team
Considering the original issue; iOS kills the app because it reaches the maximum allowable amount of memory in use by a single process (as indicated by JetsamEvent with “per-process-limit”). If I calculated correctly (at 4 KiB page size), from the above page count it is about 1.9 GB of memory in use on a 3 GB iPad 8 system.
I am not convinced that this behavior is expected or not a bug.
No worries, I am quite patient.
I want to continue cooperating with you so I can either find the issue or help you fix a bug or two.
Currently I am experiencing trouble with exporting “Automatisierungstechnik”, the app crashes with the original issue. No restarts or closing of apps helps.
Hi.
We feel very sorry about this crush and I will try to extract the Automatisierungstechnik file to our specialists shortly to see if we could do anything about it. I will also forward your theory of Jetsam Event.
Meanwhile, could you still use this Notebook?
Before getting feedback from our specialists, my personal suggestion at this moment could only be trying to seperate the Notebook into two or more notebooks. Quite annoying though, I know :(, but currently this is the only advice I could have.
Still you could try to follow the instruction above to export some cards to other Notebook.
Our export uses graphics card texture rendering to generate a PDF from zero. So it is quite RAM-consumable for a very large project, and there are indeed issues on some devices with relatively smaller RAM. It is recommended to use Mac for exporting big Notebook, or our service team can always help you export your files if you wish.
For this weakness, we are currently looking for commercial export module procurement to deal with this issue and we have made some progress. But it requires time to negotiate and handover. Therefore there are uncertainties of when this problem can be solved.
We feel extraordinary sorry for the inconvenience we have caused for your study, and so much thanks for you pointing out this issue to us.
Right now I could still only suggest splitting up the notebook as above. Please do get in touch with us if you further meet any problem or have any advice about our software.