New issue
Advanced search Search tips
Starred by 4 users
Status: Duplicate
Merged: issue 36151
Owner: ----
Closed: Feb 2010
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment
detaching a tab crash
Reported by bugabu...@gmail.com, Feb 20 2010 Back to list
Chrome Version       : 5.0.334.0 (39541) Ubuntu
URLs (if applicable) : any
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4:
Firefox 3.x:
IE 7:
IE 8:

What steps will reproduce the problem?
1. open chromium
2. open a few tabs
3. detach a tab to be a new window

What is the expected result?
to move the tab to a new window

What happens instead?
chromium closes

Please provide any additional information below. Attach a screenshot if
possible.

 
Comment 1 by f...@sofaraway.org, Feb 20 2010
Mergedinto: 36151
Status: Duplicate
This has always worked fine for me, up to the point I enabled desktop effects in KDE. 
Chromium slows down as soon as a tab becomes detached and crashes afterwards. When I 
restart Chromium, I get two windows: my original window and a window with the detached 
tab.

On the console, I see this error:

The program 'chromium' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 33338 error_code 3 request_code 137 minor_code 6)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
I also have this problem but it only started happening after changing to the new 
"nouveau" driver in fedora.  I don't have effects enabled (they don't work in the 
nouveau driver)
Comment 4 by chris.sh...@cox.net, Jul 10 2010
I have this problem both with "nouveau" and with "vesa".
5.0.375.99 beta

For me, this is not technically a crash, but it makes X unusable.  If I switch to a tty console, wait 2 minutes for it to appear, kill chrome, and return to X, all is fine.
Project Member Comment 5 by bugdroid1@chromium.org, Oct 12 2012
Labels: Restrict-AddIssueComment-Commit
Mergedinto: chromium:36151
This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.
Project Member Comment 6 by bugdroid1@chromium.org, Mar 11 2013
Labels: -Area-Undefined
Sign in to add a comment