New Contributor
New ContributorIt's all in the attached problem report, but it's Quartus Prime Pro 25.3/109 on Ubuntu 22. Maybe the device doesn't show up there, it is the Agilex 5 Premium Devkit, ES version. The problem report contains a stack trace which might be useful to find a bug, but the problem itself is not reproducible and I have not seen it before.
Super ContributorSince it is not reproducible for now, can you update the report stack trace when it is duplicate from your side?
We shall close this temporally until you manage to duplicate it.
New ContributorSure, if and when it happens I'll update. In general though, it does happen that Quartus crashes in various situations. When it does, it throws up a dialog encouraging the user to "tell us what happened" or something along those lines. Presumably the intention is that the report is supposed to help the developers perfect the product. Should that be taken seriously? And if so, is this the right forum for those reports?
Super ContributorYes, having the report will help the developer debug the issue. Usually, being able to duplicate the issue makes it easier to narrow down the root cause. If the issue cannot be duplicated, the developer will need the report to see what can be done.
In terms of severity, it depends: if this internal error does not occur very often and does not block development or production, I would consider the severity to be low for now. If it does block development or production, then the severity would be high.
Don't worry, this is the right forum to report bugs.
Thanks, Kenny
