Tested in chrome #64.0.3282.119,Stable #64.03282.140 & Canary #66.0.3339.0 on Ubuntu 14.04 & 16.04 and not able to reproduce the issue.Please find the screen shots for your reference.

@huishaodj: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once in latest builds of chrome and let us know the observations and provide the crash id from chrome://crashes of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 808741.png 32.3 KB

	808741.png 32.3 KB View Download

Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested and found: "The mouse wheel slowly sliding will not collapse, but the rapid slide will collapse."
I export the bookmark and restore the default settings, re-import the bookmark the same problem.

Deleted: simplescreenrecorder-2018-02-06_16.33.24.mp4 1.3 MB

	simplescreenrecorder-2018-02-06_16.33.24.mp4 1.3 MB View Download

Thanks for the update! unfortunately i am unable to reproduce the issue. Could you please provide the crash id from chrome://crashes which would help us to triage the issue further.

Thanks in Advance.

I have this crash as well in Chromium 64.0.3282.140 on Ubuntu 14.04 64-bit (using Ubuntu's Chromium build from the repositories) in the Unity desktop environment using proprietary nvidia driver at version 361.45.18.

I have attached a simple bookmarks file that can be used to reproduce this crash. In my limited tests it appears the nesting of folders is necessary for the crash to appear.
Once imported, in the bookmarks bar open the folder "Bookmarks bar" -> "test test" and then rapidly scroll back and forth through the large list using the mouse wheel. In my tests I could pretty much always reproduce the crash after no more than a few dozen seconds of scrolling. I have included a screenshot of how the directory structure should look like in the bookmarks bar.

In four of the crashes I took a backtrace with gdb, it was always the same:
#0  0x00005555583c50a6 in AsLocatedEvent () at ../../ui/events/event.cc:300
#1  0x00005555590e775a in DispatchMouseEvent () at ../../ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc:1775
#2  0x00005555590e874f in DispatchEvent () at ../../ui/views/widget/desktop_aura/desktop_window_tree_host_x11.cc:2099
#3  0x00005555590e8aa0 in non-virtual thunk to views::DesktopWindowTreeHostX11::DispatchEvent(_XEvent* const&) () at ../../base/trace_event/trace_event.h:1094
#4  0x00005555583bcf13 in DispatchEvent () at ../../ui/events/platform/platform_event_source.cc:93
#5  0x0000555558752373 in ui::X11EventSource::ExtractCookieDataDispatchEvent(_XEvent*) () at ../../ui/events/platform/x11/x11_event_source.cc:238
#6  0x000055555875231d in ui::X11EventSource::DispatchXEvents() () at ../../ui/events/platform/x11/x11_event_source.cc:138
#7  0x000055555875511c in ui::(anonymous namespace)::XSourceDispatch(_GSource*, int (*)(void*), void*) () at ../../ui/events/platform/x11/x11_event_source_glib.cc:41
#8  0x00007ffff54bece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x00007ffff54bf048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007ffff54bf0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x0000555557da5545 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () at ../../base/message_loop/message_pump_glib.cc:305
#12 0x0000555557dc5f94 in Run () at ../../base/run_loop.cc:114
#13 0x0000555557cbe808 in MainMessageLoopRun () at ../../chrome/browser/chrome_browser_main.cc:1939
#14 0x0000555556903f24 in RunMainMessageLoopParts () at ../../content/browser/browser_main_loop.cc:1199
#15 0x0000555556906c32 in Run () at ../../content/browser/browser_main_runner.cc:140
#16 0x00005555569000d6 in BrowserMain () at ../../content/browser/browser_main.cc:46
#17 0x0000555557a6b392 in Run () at ../../content/app/content_main_runner.cc:705
#18 0x0000555557a757c6 in Main () at ../../services/service_manager/embedder/main.cc:456
#19 0x0000555557a6a3b1 in content::ContentMain(content::ContentMainParams const&) () at ../../content/app/content_main.cc:19
#20 0x00005555561751bc in ChromeMain () at ../../chrome/app/chrome_main.cc:130
#21 0x00007ffff16c3f45 in __libc_start_main (main=0x555556175120 <main>, argc=2, argv=0x7fffffffde38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffde28)
    at libc-start.c:287
#22 0x0000555556175025 in _start ()

Note that as I'm using Chromium I'm unable to use Chrome's crash reporting system. If you need additional debug information feel free to tell me how to obtain that and I will post it if possible.
A few days ago I had a crash that was also triggered on a mouse event (it might have been related to the context menu on a website), so this crash might be more general and not limited to bookmarks, I don't have a backtrace of that crash available though.

I have been unable to reproduce this crash on a VirtualBox VM with Ubuntu 14.04 (3D acceleration enabled, tried using Unity and LXDE desktop environments) and a VM with Windows 7 (3D acceleration disabled).

Deleted: bookmarks.html 7.5 KB

bookmarks.html 7.5 KB View Download

Deleted: bookmarks-bar.png 6.6 KB

	bookmarks-bar.png 6.6 KB View Download

I tried official Chromium build 520842 where I could reproduce this issue. However on the very recent 535981 I was unable to reproduce.
I performed the following bisect:
$ python bisect-builds.py --use-local-cache -a linux64 -g 535981 -b 520842 --verify-range

Result:
> You are probably looking for a change made after 527021 (known bad), but no later than 527025 (first known good).
> CHANGELOG URL:
>   https://chromium.googlesource.com/chromium/src/+log/2613496a226cffa857b104bb79cf0e8ee834825a..bfdecad144812f52f0094c6f0ccdb8bb0bf1cad3

So it's probably the revert in https://chromium.googlesource.com/chromium/src/+/bfdecad144812f52f0094c6f0ccdb8bb0bf1cad3 which fixed this. Unfortunately the revert commit mentions issue 794140 which is private.
The change which triggers the crash comes from  issue 707406 .
Assuming the relanding https://chromium.googlesource.com/chromium/src.git/+/e46169bf03375205b6cf62cde0d68ff88c80ab14 is included in revision 535981, that commit has fixed the crash.
So please backport that commit to M64 or at least revert 53549f0a1c27b29c88511bf330ecc428006c77ed.

Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!