You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The editor allows you to generate notes with a pretty long description but on subsequent load of the plan, the program crashes.
I've been using masterplan like a white board for jotting notes and ended up with a note that is pretty long. I've made a minimal reproducing case here, this is the note I was using, verbatim just replaced the description with a repeating character sequence.
Thank you for the report - I can't reproduce this on my machine. I'm guessing it might be that MasterPlan creates a GPU texture to handle text rendering, and your machine's GPU might not be able to create a texture large enough to handle the text, thereby creating this crash. Can you tell me your OS and GPU? Also, can you try (after backing up your plan file) editing your plan to change the rectangle height ("H") from 4096 to 960, or something similar?
Thanks, I gave that shot but to no avail. I tried reducing the width, height to (960, 960) and more conservatively to (128, 128) and it continues to fail to start up.
Exceeding GPU VRAM sounds plausible as I am using a fairly dated laptop to run Masterplan. Specs are as follows
Processor Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz 2.40 GHz
Installed RAM 8.00 GB (7.87 GB usable)
Edition Windows 10 Home
Version 20H2
OS build 19042.1645
Experience Windows Feature Experience Pack 120.2212.4170.0
GPU Intel(R) HD Graphics 520
VRAM 128MB
Shared Mem 4030MB
The editor allows you to generate notes with a pretty long description but on subsequent load of the plan, the program crashes.
I've been using masterplan like a white board for jotting notes and ended up with a note that is pretty long. I've made a minimal reproducing case here, this is the note I was using, verbatim just replaced the description with a repeating character sequence.
The log file is
The text was updated successfully, but these errors were encountered: