Closed Bug 924748 Opened 12 years ago Closed 12 years ago

Browser Console makes GNOME Shell crash

Categories

(DevTools :: Console, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 921966

People

(Reporter: marco, Unassigned)

Details

Copying some code in the Browser Console makes the console window grow. If you copy enough code, the window becomes so big that GNOME Shell crashes. The console would be more comfortable to use if its window didn't grow.
(In reply to Marco Castelluccio [:marco] from comment #0) > Copying some code in the Browser Console makes the console window grow. If > you copy enough code, the window becomes so big that GNOME Shell crashes. > > The console would be more comfortable to use if its window didn't grow. Which version of Firefox do you use? How do you copy code? What do you mean by "window becomes big"?
(In reply to Paul Rouget [:paul] from comment #1) > (In reply to Marco Castelluccio [:marco] from comment #0) > > Copying some code in the Browser Console makes the console window grow. If > > you copy enough code, the window becomes so big that GNOME Shell crashes. > > > > The console would be more comfortable to use if its window didn't grow. > > Which version of Firefox do you use? Nightly. > How do you copy code? What do you mean? I select the code that I want to copy from an external editor, press Ctrl+C, then focus the Browser Console and press Ctrl+V. > What do you mean by "window becomes big"? The window height goes beyond the monitor size. The crash is probably due to a GNOME Shell bug, but the height increase is annoying anyway.
Unity has a similar issue as well, window size keeps changing, but it moves towards the bottom of the screen and eventually disappears outside of the viewport. Reminds me of the old panel bug on Linux where it would move on its own.
Ouch. I wasn't aware the browser console window can grow on its own...
Priority: -- → P2
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.