Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Crashes with 'Native' Renderer During Parameter Adjustments - Mac #792

Open
citrasusanto opened this issue Nov 24, 2024 · 2 comments
Open

Comments

@citrasusanto
Copy link

continue from #772

While using the 'Native' renderer, the app crashes when I change parameters such as dragging or changing parameter of a callout through the command editor. However the issue doesn't occur when:

  1. I use the Placement Dialog to adjust the position (top,bottom,etc)
  2. The renderer is set to LDView

I tested this behaviour in multiple devices:

  1. Mac Mini M4: The crash occurs every parameter changes
  2. VMware (Windows 11): Works fine, no crashes.
  3. Intel i3 10th Gen with integrated Intel HD Graphics (no external GPU) -Windows 11: Crashes frequently during any type of editing.
@citrasusanto citrasusanto changed the title [Issue]: App Crashes with 'Native' Renderer During Parameter Adjustments - Mac Nov 24, 2024
@trevorsandy
Copy link
Owner

Thank you for reporting this behaviour. I'll take a look.

For item .3 above:

Intel i3 10th Gen with integrated Intel HD Graphics (no external GPU) -Windows 11: Crashes frequently during any type of editing.

See #741.

the app crashes when I change parameters such as dragging or changing parameter of a callout through the command editor.

Generally, a CALLOUT does not have parameters that lend themselves to editing in the command editor. There are exceptions however such as:

0 !LPUB CALLOUT STEP_NUMBER PLACEMENT TOP LEFT PLI OUTSIDE
0 !LPUB CALLOUT ALLOC HORIZONTAL
0 !LPUB CALLOUT MARGINS 0.0500 0.5000

Here is typical CALLOUT;

0 !LPUB CALLOUT BEGIN
0 !LPUB CALLOUT STEP_NUMBER PLACEMENT TOP LEFT PLI OUTSIDE
1 16 -60 24 10 -1 0 0 0 1 0 0 0 -1 submodel-4.ldr
0 !LPUB CALLOUT POINTER BOTTOM 397.000 169.352 421.874 397.000 322.000 397.000 421.874 397.000 0.000 0.000 2
0 !LPUB CALLOUT ALLOC HORIZONTAL
0 !LPUB CALLOUT PLACEMENT TOP RIGHT ASSEM OUTSIDE OFFSET 0.4048 -0.0071
0 !LPUB CALLOUT BORDER ROUND 1 "Black" 0.031 15.000 MARGINS 0.150 0.150
0 !LPUB CALLOUT MARGINS 0.0500 0.5000
0 !LPUB CALLOUT END

Can you provide an explicit list of steps to reproduce your behaviour. For example what command(s) are you manipulating in the command editor and what exactly are your doing - e.g. dragging the lines to new location, add/removing a command, changing a command key and/or value?

I could not reproduce an AbEnd when changing for example 0 !LPUB CALLOUT ALLOC HORIZONTAL to 0 !LPUB CALLOUT ALLOC VERTICAL and clicking Redraw in the command editor.

Cheers,

@citrasusanto
Copy link
Author

citrasusanto commented Nov 30, 2024

To be honest, I'm quite confused about the error. On my Windows laptop, it's not consistent. However, here's an instance where I was able to reproduce the error. It seems to occur more frequently with the Native renderer, especially with larger files.

The error happens when I try to re-render after changing something, such as a parameter, or when I switch to another page. However, it doesn't happen every time.

I've attached the LPub3D log and details of what happens when the crash occurs. When the crash happens, the page generation stops. I can click to go to the next page, but nothing changes.
LPub3DLog-Switch between Page freeze.txt

Here what it is looks like when i re-opened again
image

CPU: i3 1005G1
GPU: Intel UHD Graphics
OS: Windows 11
Version: 2.4.8 (latest dev ops r201 don't have windows version)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: QUEUED
Development

No branches or pull requests

2 participants