Hide Forgot
Created attachment 562025 [details] backtrace On F17 emacs-24.0.93-3.fc17.x86_64 freezes when I edit certain files (which usually contain overly long macro definitions going over multiple lines). This is quite annoying, and makes it quite hard to edit any code anymore. Attached is a backtrace of this when this happens.
This happens both on the X11 version and on -nw.
If I move my .emacs away this problem continues to exist on these files, hence it's independent of my personal emacs configuration. emacs stops reacting to C-c when frozen like this, but some Gtk UI elements continue to somewhat work. i.e. the toolbar buttons still flash if you hover with the mouse over it, but nothing happens if you click them and the window contents is never refreshed anymore.
Downgrading to emacs-23.3-9.fc16.x86_64 fixes this problem BTW.
IMO it was a mistake moving to emacs-24 for fc17. I've been compiling it from source for the last year and tested it for stability, which it unfortunately hasn't reached yet. One of the show stoppers for me is that the gdb interface is very broken, and among other problems hangs with 100% CPU usage for some files.
Lennart, do you know whether the freeze happens also with a newer pre-release version? emacs-24.0.97-1.fc17 is coming to updates-testing. Could you attach some file with such a long macro so I can try to reproduce the issue? I use the pre-release to edit C files -- also with macros -- without any freeze issues. Nevertheless, another issues occur such as that the indentation code is broken in a different way from emacs 23.
Dov, Emacs 24 contains great amount of bugs, but it is the same with Emacs 23. I have been using the development code for several months and it doesn't seem to be fundamentally broken. It has the advantage of upstream focus, so we can expect serious bugs to be fixed quickly.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
I had the same problem. I tried compiling both the latest version of emacs 24 and latest version of emacs 23, without any difference. Moving my ~/.emacs file didn't help either. But configuring with "--with-x-toolkit=motif" made a stunning difference. I've only tried a few minutes, but so far emacs is again snappy.
motif and lucid works fine, gtk2 and gtk3 freezes. I'm not entirely sure if it's the same kind of freezes as reported here though. The freezing I'm seeing now is when scrolling, and this is fixed by not using gtk2. But there are also other kinds of short freezes which happens now and then when editing for instance C++ macros, but it's not reproducable. Hopefully the other kind of freezes are also fixed by not using gtk, but I don't know yet.
Not sure if this is related but it may give some ideas. I updated from Fedora 16 -> Fedora 19 last week (clean install on new disk) After some freezes yesterday and today I now recognise that emacs freezes within seconds of me yanking some html into a perl script. If it set the buffer to Fundamental mode it doesn't freeze. Could the issue be something to do with syntax highlighting? Can anyone else duplicate this?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.