[jitsi-dev] NPEs in MetaContactImpl


#1

Hey devs,

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Cheers,
Emil

···

23:14:41.795 SEVERE: [18] util.UtilActivator.uncaughtException().109 An uncaught exception occurred in thread=Thread[AWT-EventQueue-0,6,main] and message was: null
java.lang.NullPointerException
  at java.util.LinkedList.indexOf(LinkedList.java:402)
  at java.util.LinkedList.contains(LinkedList.java:177)
  at net.java.sip.communicator.impl.contactlist.MetaContactImpl.getContactsForOperationSet(MetaContactImpl.java:191)
  at net.java.sip.communicator.impl.gui.main.contactlist.contactsource.MetaUIContact.getContactDetailsForOperationSet(MetaUIContact.java:257)
  at net.java.sip.communicator.impl.gui.main.contactlist.contactsource.MetaUIContact.getDefaultContactDetail(MetaUIContact.java:237)
  at net.java.sip.communicator.impl.gui.main.contactlist.ContactListTreeCellRenderer.initButtonsPanel(ContactListTreeCellRenderer.java:826)
  at net.java.sip.communicator.impl.gui.main.contactlist.ContactListTreeCellRenderer.getTreeCellRendererComponent(ContactListTreeCellRenderer.java:431)
  at javax.swing.plaf.basic.BasicTreeUI$NodeDimensionsHandler.getNodeDimensions(BasicTreeUI.java:2712)
  at javax.swing.tree.AbstractLayoutCache.getNodeDimensions(AbstractLayoutCache.java:475)
  at javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.updatePreferredSize(VariableHeightLayoutCache.java:1342)
  at javax.swing.tree.VariableHeightLayoutCache$TreeStateNode.getPreferredHeight(VariableHeightLayoutCache.java:1150)
  at javax.swing.tree.VariableHeightLayoutCache.updateYLocationsFrom(VariableHeightLayoutCache.java:871)
  at javax.swing.tree.VariableHeightLayoutCache.invalidatePathBounds(VariableHeightLayoutCache.java:261)
  at net.java.sip.communicator.plugin.desktoputil.plaf.SIPCommTreeUI.selectionChanged(SIPCommTreeUI.java:244)
  at net.java.sip.communicator.impl.gui.main.contactlist.GroupNode.refreshSelection(GroupNode.java:471)
  at net.java.sip.communicator.impl.gui.main.contactlist.GroupNode.addContact(GroupNode.java:103)
  at net.java.sip.communicator.impl.gui.main.contactlist.TreeContactList.addContact(TreeContactList.java:531)
  at net.java.sip.communicator.impl.gui.main.contactlist.TreeContactList.addContact(TreeContactList.java:601)
  at net.java.sip.communicator.impl.gui.main.contactlist.TreeContactList$3.run(TreeContactList.java:590)
  at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
  at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:708)
  at java.awt.EventQueue.access$400(EventQueue.java:82)
  at java.awt.EventQueue$2.run(EventQueue.java:669)
  at java.awt.EventQueue$2.run(EventQueue.java:667)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
  at java.awt.EventQueue.dispatchEvent(EventQueue.java:678)
  at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:296)
  at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:211)
  at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:201)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:196)
  at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:188)
  at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

--
https://jitsi.org


#2

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught exceptions
instead of swallowing them...

Cheers,
Emil

Ingo


#3

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught exceptions
instead of swallowing them...

Hmmm ... I believe the one that's printing these is the UtilActivator, which has been acting as a DefaultUncaughtExceptionHandler for quite a while now.

Or are you referring to something else?

Cheers,
Emil

···

On 20.06.13, 23:20, Ingo Bauersachs wrote:

Cheers,
Emil

Ingo

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org


#4

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught

exceptions

instead of swallowing them...

Hmmm ... I believe the one that's printing these is the UtilActivator,
which has been acting as a DefaultUncaughtExceptionHandler for quite a
while now.

Or are you referring to something else?

Apparently. It was desktoputil/SwingWorker.java in commit-id
7355e2f82318b6139e6aec5ecf01d144f18a3494

Cheers,
Emil

Ingo

···

On 20.06.13, 23:20, Ingo Bauersachs wrote:


#5

OK, I see. No, I think this is different. I only saw this once now with the latest version and the exception goes to the default handler (UtilActivator) for printing.

Damencho, (sorry to ask you this twice in the same day :wink: ) but could this be related to your latest contact source changes?

Cheers,
Emil

···

On 20.06.13, 23:43, Ingo Bauersachs wrote:

On 20.06.13, 23:20, Ingo Bauersachs wrote:

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught

exceptions

instead of swallowing them...

Hmmm ... I believe the one that's printing these is the UtilActivator,
which has been acting as a DefaultUncaughtExceptionHandler for quite a
while now.

Or are you referring to something else?

Apparently. It was desktoputil/SwingWorker.java in commit-id
7355e2f82318b6139e6aec5ecf01d144f18a3494

--
https://jitsi.org


#6

Hi,

I don't think so, not even close. Actually I have seen this several
times last few months, but no way to reproduce it.

Regards
damencho

···

On Fri, Jun 21, 2013 at 12:50 AM, Emil Ivov <emcho@jitsi.org> wrote:

On 20.06.13, 23:43, Ingo Bauersachs wrote:

On 20.06.13, 23:20, Ingo Bauersachs wrote:

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught

exceptions

instead of swallowing them...

Hmmm ... I believe the one that's printing these is the UtilActivator,
which has been acting as a DefaultUncaughtExceptionHandler for quite a
while now.

Or are you referring to something else?

Apparently. It was desktoputil/SwingWorker.java in commit-id
7355e2f82318b6139e6aec5ecf01d144f18a3494

OK, I see. No, I think this is different. I only saw this once now with the
latest version and the exception goes to the default handler (UtilActivator)
for printing.

Damencho, (sorry to ask you this twice in the same day :wink: ) but could this
be related to your latest contact source changes?

Cheers,
Emil

--
https://jitsi.org

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

I also see and this one from time to time:

     [java] 10:49:54.070 SEVERE: [30]
impl.protocol.jabber.ScServiceDiscoveryManager.run().716 Error
requesting discovery info, thread ended unexpectedly
     [java] java.util.ConcurrentModificationException
     [java] at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
     [java] at java.util.HashMap$EntryIterator.next(HashMap.java:834)
     [java] at java.util.HashMap$EntryIterator.next(HashMap.java:832)
     [java] at net.java.sip.communicator.impl.contactlist.MetaContactImpl.removeCapabilities(MetaContactImpl.java:1113)
     [java] at net.java.sip.communicator.impl.contactlist.MetaContactImpl.updateCapabilities(MetaContactImpl.java:1093)
     [java] at net.java.sip.communicator.impl.contactlist.MetaContactListServiceImpl.supportedOperationSetsChanged(MetaContactListServiceImpl.java:3477)
     [java] at net.java.sip.communicator.service.protocol.AbstractOperationSetContactCapabilities.fireContactCapabilitiesEvent(AbstractOperationSetContactCapabilities.java:127)
     [java] at net.java.sip.communicator.impl.protocol.jabber.OperationSetContactCapabilitiesJabberImpl.fireContactCapabilitiesChanged(OperationSetContactCapabilitiesJabberImpl.java:529)
     [java] at net.java.sip.communicator.impl.protocol.jabber.ScServiceDiscoveryManager$DiscoveryInfoRetriever.requestDiscoveryInfo(ScServiceDiscoveryManager.java:765)
     [java] at net.java.sip.communicator.impl.protocol.jabber.ScServiceDiscoveryManager$DiscoveryInfoRetriever.run(ScServiceDiscoveryManager.java:707)
     [java] at java.lang.Thread.run(Thread.java:680)

···

On Fri, Jun 21, 2013 at 9:10 AM, Damian Minkov <damencho@jitsi.org> wrote:

Hi,

I don't think so, not even close. Actually I have seen this several
times last few months, but no way to reproduce it.

Regards
damencho

On Fri, Jun 21, 2013 at 12:50 AM, Emil Ivov <emcho@jitsi.org> wrote:

On 20.06.13, 23:43, Ingo Bauersachs wrote:

On 20.06.13, 23:20, Ingo Bauersachs wrote:

I am currently seeing tons of exception that look like the one below.

Does anyone think their changes might be related?

Partially, because I added the statement that logs the uncaught

exceptions

instead of swallowing them...

Hmmm ... I believe the one that's printing these is the UtilActivator,
which has been acting as a DefaultUncaughtExceptionHandler for quite a
while now.

Or are you referring to something else?

Apparently. It was desktoputil/SwingWorker.java in commit-id
7355e2f82318b6139e6aec5ecf01d144f18a3494

OK, I see. No, I think this is different. I only saw this once now with the
latest version and the exception goes to the default handler (UtilActivator)
for printing.

Damencho, (sorry to ask you this twice in the same day :wink: ) but could this
be related to your latest contact source changes?

Cheers,
Emil

--
https://jitsi.org

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev