Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 10539 by [email protected]: Linux: crash in
AutocompleteEditViewGtk::EmphasizeURLComponents
http://code.google.com/p/chromium/issues/detail?id=10539
Chrome Version: 2.0.175.0 (Developer Build 13652)
This issue is Linux specific.
What steps will reproduce the problem?
1. Start chromium on Linux.
2. Type (or copy and paste) a Japanese character (e.g., U+3042 Japanese
hiragana letter 'あ') on the omnibox.
3. Press enter.
4. Type the character 'あ' on the omnibox again.
5. Select 'あ/' from auto complete pop up using cursor keys.
6. Then (re)select 'Google Search for あ' from the pop up using cursor
keys.
What is the expected result?
An emphasized (black) string 'あ' is shown on the omnibox.
What happens instead?
Chromium crashes.
[22878:22878:4436099468917:FATAL:app/chrome_dll_main.cc(162)] Gtk:
Incorrect line byte index 1 falls in the middle of a UTF-8 character; this
will crash the text buffer. Byte indexes must refer to the start of a
character.
Trace/breakpoint trap
Please provide any additional information below. Attach a screenshot if
possible.
Crash trace:
$ gdb ./chrome
...
[New Thread 0xb384db90 (LWP 19335)]
[19322:19322:4425246744456:FATAL:app/chrome_dll_main.cc(162)] Gtk:
Incorrect line byte index 1 falls in the middle of a UTF-8 character; this
will crash the text buffer. Byte indexes must refer to the start of a
character.
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 0xb7117700 (LWP 19322)]
DebugUtil::BreakDebugger () at
/home/yusukes/chromium/src/base/debug_util_posix.cc:109
109 }
(gdb) bt
#0 DebugUtil::BreakDebugger () at
/home/yusukes/chromium/src/base/debug_util_posix.cc:109
#1 0x083eb138 in ~LogMessage (this=0xbfc5f150) at
/home/yusukes/chromium/src/base/logging.cc:521
#2 0x080597ac in GLibLogHandler (log_domain=0xb7d43d97 "Gtk",
log_level=G_LOG_LEVEL_WARNING,
message=0xb8aca30 "Incorrect line byte index 1 falls in the middle of a
UTF-8 character; this will crash the text buffer. Byte indexes must refer
to the start of a character.", userdata=0x0) at app/chrome_dll_main.cc:162
#3 0xb771259f in g_logv () from /usr/lib/libglib-2.0.so.0
#4 0xb7712946 in g_log () from /usr/lib/libglib-2.0.so.0
#5 0xb7c4e181 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#6 0xb7c4ec11 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
#7 0xb7c417d9 in gtk_text_buffer_get_iter_at_line_index () from
/usr/lib/libgtk-x11-2.0.so.0
#8 0x0836e522 in AutocompleteEditViewGtk::EmphasizeURLComponents
(this=0xb4e8c08) at browser/autocomplete/autocomplete_edit_view_gtk.cc:522
(snip)
#54 0x08059cbe in main (argc=1, argv=0xbfc61444) at
app/chrome_exe_main_gtk.cc:33
(gdb) up
#8 0x0836e522 in AutocompleteEditViewGtk::EmphasizeURLComponents
(this=0xb4e8c08) at browser/autocomplete/autocomplete_edit_view_gtk.cc:522
522 parts.host.end());
(gdb) list
517
518 // We've found a host name, give it more emphasis.
519 gtk_text_buffer_get_iter_at_line_index(text_buffer_, &start, 0,
520 parts.host.begin);
521 gtk_text_buffer_get_iter_at_line_index(text_buffer_, &end, 0,
522 parts.host.end());
523 gtk_text_buffer_remove_all_tags(text_buffer_, &start, &end);
524 }
525
526 // Emphasize the scheme for security UI display purposes (if
necessary).
I've create a change which fixes this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
