This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 268368 - Netbeans Hangs on "Turning on Modules" on initial launch after install
Summary: Netbeans Hangs on "Turning on Modules" on initial launch after install
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Welcome (show other bugs)
Version: 8.2
Hardware: PC Linux
: P3 normal (vote)
Assignee: Stanislav Aubrecht
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-06 04:12 UTC by chonc76
Modified: 2016-10-06 04:12 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
jstack output (20.19 KB, text/plain)
2016-10-06 04:12 UTC, chonc76
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chonc76 2016-10-06 04:12:50 UTC
Created attachment 162360 [details]
jstack output

After I installed I rebooted and launched for the first time and the Welcome screen made it to "Turning on Modules".  I have removed ~/.netbeans and ~/.cache/.netbeans after installation and rebooted the machine prior to launching netbeans for the first time. I've attached a text file with the  "jstack -F <pid>" output.  After executing the jstack command the ide loaded correctly and everything is responsive.


Relevant information:

uname -a output:

Linux downlink-1 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux



The kernel complained and repeated the following message several times:

Oct  5 20:35:50 downlink-1 kernel: [  240.300124] INFO: task java:3025 blocked for more than 120 seconds.
  3 Oct  5 20:35:50 downlink-1 kernel: [  240.300127]       Tainted: P           OE  3.19.0-32-generic #37~14.04.1-Ubuntu
  4 Oct  5 20:35:50 downlink-1 kernel: [  240.300128] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  5 Oct  5 20:35:50 downlink-1 kernel: [  240.300129] java            D ffff88085978fd20     0  3025   2753 0x00000000
  6 Oct  5 20:35:50 downlink-1 kernel: [  240.300132]  ffff88085978fd20 ffff8808553e4e80 0000000000013e80 ffff88085978ffd8
  7 Oct  5 20:35:50 downlink-1 kernel: [  240.300133]  0000000000013e80 ffff88085b84c4b0 ffff8808553e4e80 ffff88085f092000
  8 Oct  5 20:35:50 downlink-1 kernel: [  240.300135]  ffff8808553e4e80 ffff880853bf5b60 ffff880853bf5b78 ffff880853bf5b00
  9 Oct  5 20:35:50 downlink-1 kernel: [  240.300136] Call Trace:
 10 Oct  5 20:35:50 downlink-1 kernel: [  240.300142]  [<ffffffff817b2a39>] schedule+0x29/0x70
 11 Oct  5 20:35:50 downlink-1 kernel: [  240.300145]  [<ffffffff817b5865>] rwsem_down_read_failed+0xe5/0x150
 12 Oct  5 20:35:50 downlink-1 kernel: [  240.300148]  [<ffffffff8118487b>] ? lru_cache_add_active_or_unevictable+0x2b/0xa0
 13 Oct  5 20:35:50 downlink-1 kernel: [  240.300152]  [<ffffffff813b4674>] call_rwsem_down_read_failed+0x14/0x30
 14 Oct  5 20:35:50 downlink-1 kernel: [  240.300154]  [<ffffffff817b4ec4>] ? down_read+0x24/0x30
 15 Oct  5 20:35:50 downlink-1 kernel: [  240.300157]  [<ffffffff81062156>] __do_page_fault+0x486/0x5b0
 16 Oct  5 20:35:50 downlink-1 kernel: [  240.300161]  [<ffffffff810f0aba>] ? do_futex+0x10a/0x5d0
 17 Oct  5 20:35:50 downlink-1 kernel: [  240.300163]  [<ffffffff81192219>] ? vm_mmap_pgoff+0x99/0xc0
 18 Oct  5 20:35:50 downlink-1 kernel: [  240.300164]  [<ffffffff810622b1>] do_page_fault+0x31/0x70
 19 Oct  5 20:35:50 downlink-1 kernel: [  240.300166]  [<ffffffff817b8f28>] page_fault+0x28/0x30