[Jsynthlib-devel] NullPointerException when creating a new patch

[Jeff W. <jww...@ya...>]

Greetings,

I just checked out the latest code from the repository
(the version that allows changing the look and feel
without quitting the application) and I got the
following exception when trying to create a new Bass
Pod patch using the New command:
ERR> 'Unable to create this new patch.' reported.
ERR> [Exception] null
java.lang.NullPointerException
	at
core.Actions$NewPatchAction.actionPerformed(Actions.java:1138)
	at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1819)
	at
javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1872)
	at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
	at
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
	at
javax.swing.AbstractButton.doClick(AbstractButton.java:321)
	at
apple.laf.ScreenMenuItem.actionPerformed(ScreenMenuItem.java:83)
	at
java.awt.MenuItem.processActionEvent(MenuItem.java:589)
	at java.awt.MenuItem.processEvent(MenuItem.java:548)
	at
java.awt.MenuComponent.dispatchEventImpl(MenuComponent.java:285)
	at
java.awt.MenuComponent.dispatchEvent(MenuComponent.java:273)
	at
java.awt.EventQueue.dispatchEvent(EventQueue.java:458)
	at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:234)
	at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:184)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:178)
	at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
	at
java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

I haven't been able to reproduce this but I was
wondering if anyone else was noticing any strange
goings on. My system seems to be acting up lately.
JSynthLib is crashing right and left with signal
errors (i.e. SIGSEGV, SIGKILL, etc.) The same thing
happened a few months ago but it seemed to just go
away by itself. Now in the last couple of days it
seems I can't keep JSynthLib running for more than a
minute or two.

I don't know much about signal errors except that they
are unrecoverable system errors or traps and I believe
thay are unique to UNIX systems. If you're running
Windows, you're probably not having this problem. Am I
right?

I use Mac OSX but I was just wondering if any of you
who are Linux users are seeing anything like this.
Does anyone else on the project team use Mac OSX?

By the way, I never had a problem with signal errors
under version  0.18. It wasn't until after the
changeover to CAProvider that I started to have the
problem. This makes me wonder if CAProvider might be
part of the problem. And I run a number of other Java
applications, including NeoOfficeJ (which is a Mac
only version of OpenOffice ported over to Java)
without any problems.

Does anyone have any ideas?

Thanks,
Jeff


		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com