Created attachment 1490895 [details] Small tex file demonstrating tikz bug Description of problem: Within a tikzpicture environment, if a semicolon is omitted with more code after the omitted semicolon, upon PDF generation Texworks will spawn a pdflatex process which causes multiple CPU cores (I believe 2 per process) to jump to 100% usage. There is no way to stop the execution of these processes (that I have found) from within Texmaker; the processes have to be killed manually. This section was tested in TeXworks and, while the processing of the document did not stop, it also did not spike CPU usage, and the process could be halted from within TeXworks. Version-Release number of selected component (if applicable): 5.0.2-6.fc28 How reproducible: Always Steps to Reproduce: 1. Create a tikz picture with two items (nodes, paths, doesn't matter) 2. Omit semicolon after first item 3. Generate PDF Actual results: PDF is not generated, CPU usage spikes Expected results: Execution should halt with error Additional info: See attached file for an example of the bug.
This seems like a tikz issue, not a TexWorks one. Re-assign to Tex Live by now. And I also suggest you to report this issue upstream.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.