gedit hangs (hogs CPU) on read error

Bug #280947 reported by Anton
2
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

When opening a file that gives a 'read error' gedit hangs. The window is non-responsive, but can be closed (force close), but the gedit process remains. It will use 100% CPU, and, worse, cannot be TERM'ed, KILL'ed or STOP'ped.

This happened to me twice when opening a text file on a (faulty) CD (two different CD's). The only solution I have found is a re-boot. The fact that gedit is the default for opening text files in Ubuntu does not help here (this is why it happened twice to me), although normally I have no quarrels with gedit at all.

IMHO, this situation should *NEVER* occur. Read errors, although not frequent nowadays, do happen and are no reason for your program (or system) to go insane. (I am working now with my laptop fan blaring loudly due to the CPU load. The thing is getting hot on my lap too...)

I would *expect* any process that gets read errors on a file, to catch them and give a nice, short, apologetic message to the user about not being able to read the file. Perhaps a choice like 'Ignore', or 'Abort' would be useful.

Here are the info thingies:
Description: Ubuntu 8.04.1
gedit:
  Installed: 2.22.3-0ubuntu1
My system was upgraded from Feisty (and from Gutsy, IIRC).

(I'm off for a reboot now...)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace of the hang http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Anton (feenstra) wrote : Re: [Bug 280947] Re: gedit hangs (hogs CPU) on read error

Pedro Villavicencio wrote:
> Thanks for your bug report. Please try to obtain a backtrace of the hang
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.

I just tried, but the CD that gave me the read errors (not just with
gedit, I tried less and sum as well), now is giving no errors...

So, I cannot recreate the error situation right now.

I'll try it as soon as I find a good bad CD... ;-)

--
Groetjes,

Anton
  _____________ _______________________________________________________
| | |
| _ _ ___,| K. Anton Feenstra |
| / \ / \'| | | IBIVU/Bioinformatics - Free University Amsterdam |
|( | )| | | De Boelelaan 1083A - 1081 HV Amsterdam - Netherlands |
| \_/ \_/ | | | Tel +31 20 59 87783 - Fax +31 20 59 87653 - Room P136 |
| | <email address hidden> - www.few.vu.nl/~feenstra/ |
| | "You Could Be a Shadow" (The Breeders) |
|_____________|_______________________________________________________|

Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gedit:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.