M.Y Developers support issue

And here we are again… I now get this error:

java.lang.IllegalArgumentException: Comparison method violates its general contract!
 at java.util.TimSort.mergeLo(TimSort.java:747)
 at java.util.TimSort.mergeAt(TimSort.java:483)
 at java.util.TimSort.mergeCollapse(TimSort.java:408)
 at java.util.TimSort.sort(TimSort.java:214)
 at java.util.TimSort.sort(TimSort.java:173)
 at java.util.Arrays.sort(Arrays.java:659)
 at java.util.Collections.sort(Collections.java:217)
 at org.netbeans.swing.outline.Outline.sortAndFilter(Outline.java:507)
 at org.netbeans.swing.etable.ETable.convertRowIndexToView(ETable.java:1484)
 at org.netbeans.swing.etable.ETable.tableChanged(ETable.java:1329)
 at org.netbeans.swing.outline.Outline.tableChanged(Outline.java:970)
 at org.netbeans.swing.outline.EventBroadcaster.fireTableChange(EventBroadcaster.java:221)
 at org.netbeans.swing.outline.EventBroadcaster.fireTableChange(EventBroadcaster.java:232)
 at org.netbeans.swing.outline.EventBroadcaster.treeStructureChanged(EventBroadcaster.java:427)
 at javax.swing.tree.DefaultTreeModel.fireTreeStructureChanged(DefaultTreeModel.java:580)
 at javax.swing.tree.DefaultTreeModel.nodeStructureChanged(DefaultTreeModel.java:365)
 at javax.swing.tree.DefaultTreeModel.setRoot(DefaultTreeModel.java:135)
 at org.openide.explorer.view.NodeTreeModel$1.run(NodeTreeModel.java:123)
 at org.openide.util.Mutex.doEvent(Mutex.java:1356)
 at org.openide.util.Mutex.readAccess(Mutex.java:355)
 at org.openide.explorer.view.NodeTreeModel.setNode(NodeTreeModel.java:108)
 at org.openide.explorer.view.NodeTreeModel.setNode(NodeTreeModel.java:104)
 at org.openide.explorer.view.OutlineView.synchronizeRootContext(OutlineView.java:865)
 at org.openide.explorer.view.OutlineView.lookupExplorerManager(OutlineView.java:851)
 at org.openide.explorer.view.OutlineView.addNotify(OutlineView.java:784)
 at java.awt.Container.addNotify(Container.java:2769)
 at javax.swing.JComponent.addNotify(JComponent.java:4743)
 at org.netbeans.modules.viewmodel.OutlineTable.addNotify(OutlineTable.java:1069)
 at java.awt.Container.addImpl(Container.java:1114)
 at java.awt.Container.add(Container.java:410)
 at org.netbeans.modules.debugger.ui.views.ViewModelListener$6.run(ViewModelListener.java:744)
 at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
 at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:705)
 at java.awt.EventQueue.access$000(EventQueue.java:101)
 at java.awt.EventQueue$3.run(EventQueue.java:666)
 at java.awt.EventQueue$3.run(EventQueue.java:664)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
 at java.awt.EventQueue.dispatchEvent(EventQueue.java:675)
 at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
[catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:211)
 at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128)
 at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113)
 at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105)
 at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
 

@coronarocks,

Thanks for reporting this issue. We are fixing this issue and will get back to you as soon as we can.

@schizoid2k,

Thank you for your patience. “Cannot find Java 1.7 or later” error is fixed. Please re-download and let us know if this issue persists or if you come across any problems.

Regards,

M.Y. Developers

What happened with the fix that you promised a month ago? I still get these errors:

java.lang.NullPointerException

at com.MYDevelopers.LuaDebugger.LocalsView.Model.getNumChildren(Model.java:36)

at com.MYDevelopers.LuaDebugger.LocalsView.LuaVariablesModel.getChildrenCount(LuaVariablesModel.java:114)

at org.netbeans.spi.viewmodel.Models$DelegatingTreeModel.getChildrenCount(Models.java:1836)

at org.netbeans.spi.viewmodel.Models$CompoundModel.getChildrenCount(Models.java:4439)

at org.netbeans.modules.debugger.ui.views.ViewModelListener$5.getChildrenCount(ViewModelListener.java:481)

at org.netbeans.modules.viewmodel.TreeModelHyperNode$HyperModelChildren.getModelChildren(TreeModelHyperNode.java:240)

[catch] at org.netbeans.modules.viewmodel.TreeModelNode$TreeModelChildren.run(TreeModelNode.java:1446)

at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)

at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)

 

… I just updated to 2.0 201403101706 and the error above pops up like every 3 minutes.

Seriously, you’ve had about a month to fix it, can you please do it ASAP.

Update just pushed that should solve this issue. Please let us know if it does or does not.

Regards,

M.Y. Developers

I’m on 1.7.2 and have no intention of updating. 

That particular error has not appeared but several others have…

  1. I have switched to a mac and Glider is ridiculously slow. In a file with 1000 lines it almost freezes, making it downright impossible to work. I have tried the tricks described in http://forums.coronalabs.com/topic/36050-lua-glider-issues-on-mac/ (emptying user directory, unchecking RAM storage option, scan stubs only etc) but none of it helps. I have a new MacBook Pro i5, 8Gb, Yosemite.
  2. Whenever I try to use “Clean Build” I get an error message that says “Could not launch because main.lua is missing”. Yes, I have set the main project in the Run menu and yes I have upgraded (2.1.32). It only works if I click “Clean Build” again.
  3. Another thrown exception (see below).

I started this thread several months ago and we are not getting anywhere. Seriously guys, just fix your product!!!

java.nio.channels.ClosedChannelException
    at sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:94)
    at sun.nio.ch.FileChannelImpl.read(FileChannelImpl.java:673)
    at org.mapdb.Volume$FileChannelVol.readFully(Volume.java:856)
    at org.mapdb.Volume$FileChannelVol.getLong(Volume.java:884)
Caused: java.io.IOError
    at org.mapdb.Volume$FileChannelVol.getLong(Volume.java:887)
    at org.mapdb.StoreDirect.update2(StoreDirect.java:566)
    at org.mapdb.StoreDirect.update(StoreDirect.java:553)
    at org.mapdb.EngineWrapper.update(EngineWrapper.java:69)
    at org.mapdb.AsyncWriteEngine.access$101(AsyncWriteEngine.java:77)
    at org.mapdb.AsyncWriteEngine.runWriter(AsyncWriteEngine.java:221)
    at org.mapdb.AsyncWriteEngine$WriterRunnable.run(AsyncWriteEngine.java:173)
    at java.lang.Thread.run(Thread.java:744)
Caused: java.lang.RuntimeException: Writer thread failed
    at org.mapdb.AsyncWriteEngine.checkState(AsyncWriteEngine.java:273)
    at org.mapdb.AsyncWriteEngine.get(AsyncWriteEngine.java:337)
    at org.mapdb.Caches$HashTable.get(Caches.java:342)
    at org.mapdb.EngineWrapper.get(EngineWrapper.java:64)
    at org.mapdb.BTreeMap.get(BTreeMap.java:607)
    at org.mapdb.BTreeMap.get(BTreeMap.java:601)
    at com.MYDevelopers.Database.MapDatabase.MapDBDataStore.getStringToID(MapDBDataStore.java:288)
    at com.MYDevelopers.Database.MapDatabase.MapDBDatabaseManager.compressStringInt(MapDBDatabaseManager.java:221)
    at com.MYDevelopers.Database.MapDatabase.MapDBDatabaseManager.compressString(MapDBDatabaseManager.java:230)
    at com.MYDevelopers.Database.MapDatabase.DatabaseAddressImpl.toDatabaseID(DatabaseAddressImpl.java:147)
    at com.MYDevelopers.Database.MapDatabase.DatabaseAddressImpl.<init>(DatabaseAddressImpl.java:37)
    at com.MYDevelopers.Database.MapDatabase.DatabaseAddressImpl.<init>(DatabaseAddressImpl.java:24)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.ChildrenContainerAddress.<init>(ChildrenContainerAddress.java:24)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.StaticVariableAddress.<init>(StaticVariableAddress.java:115)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.FunctionVariableAddress.<init>(FunctionVariableAddress.java:42)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.FileFunctionAddress.<init>(FileFunctionAddress.java:37)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.ProjectScope.getFileAddress(ProjectScope.java:39)
    at com.MYDevelopers.LuaVMScanner.Utils.getFileAddressFor(Utils.java:60)
    at com.MYDevelopers.LuaVMScanner.AutocompleteContextFinder.create(AutocompleteContextFinder.java:41)
    at com.MYDevelopers.LuaVMScanner.AutocompleteContextFinder.create(AutocompleteContextFinder.java:37)
    at com.MYDevelopers.LuaVMScanner.EditorTooltipPluginImpl.addOccurences(EditorTooltipPluginImpl.java:43)
    at com.MYDevelopers.LuaSupport.OccurrencesFinder.LuaOccurrencesFinderNew$1.run(LuaOccurrencesFinderNew.java:78)
    at org.netbeans.editor.GuardedDocument.runAtomicAsUser(GuardedDocument.java:351)
    at com.MYDevelopers.LuaSupport.OccurrencesFinder.LuaOccurrencesFinderNew.run(LuaOccurrencesFinderNew.java:72)
[catch] at org.netbeans.modules.csl.editor.semantic.MarkOccurrencesHighlighter.processImpl(MarkOccurrencesHighlighter.java:166)
    at org.netbeans.modules.csl.editor.semantic.MarkOccurrencesHighlighter.run(MarkOccurrencesHighlighter.java:131)
    at org.netbeans.modules.csl.editor.semantic.MarkOccurrencesHighlighter.run(MarkOccurrencesHighlighter.java:81)
    at org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:568)
    at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:744)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
 

… and here is another one that just popped up.

Given the manner in which this whole issue has been dealt with, I would like some manager at M.Y Developers explain what you are going to do in order to assure the quality of your product so that it is usable without having to turn off functionality or manually fix things constantly. There must be someone at your company that actually cares about your reputation!

java.lang.NullPointerException
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.StaticVariableAddress.resolveNameHere(StaticVariableAddress.java:406)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.FunctionScopeAddress.resolveNameHere(FunctionScopeAddress.java:52)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.StaticVariableAddress.resolveName(StaticVariableAddress.java:389)
    at com.MYDevelopers.LuaVMScanner.Utils.queryScopeForVariable(Utils.java:73)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.processNamePath(VMNavigatorPlugin.java:169)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.decorateFunction(VMNavigatorPlugin.java:183)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.scan(VMNavigatorPlugin.java:56)
    at com.MYDevelopers.LuaSupport.StructureScanner.LuaStructureScanner.scan(LuaStructureScanner.java:44)
    at org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:172)
    at org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:593)
    at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:155)
    at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:139)
    at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:206)
    at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:203)
    at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:176)
    at org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:360)
    at org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:74)
    at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:203)
Caused: org.netbeans.modules.parsing.spi.ParseException
    at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:211)
    at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:106)
[catch] at org.netbeans.modules.csl.navigation.ElementScanningTask.computeStructureRoot(ElementScanningTask.java:160)
    at org.netbeans.modules.csl.navigation.ClassMemberPanelUI$1.run(ClassMemberPanelUI.java:226)
    at org.netbeans.modules.csl.navigation.ClassMemberPanelUI$1.run(ClassMemberPanelUI.java:216)
    at org.netbeans.modules.csl.navigation.ClassMemberNavigatorSourceFactory$ProxyElementScanningTask.run(ClassMemberNavigatorSourceFactory.java:138)
    at org.netbeans.modules.csl.navigation.ClassMemberNavigatorSourceFactory$ProxyElementScanningTask.run(ClassMemberNavigatorSourceFactory.java:110)
    at org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:568)
    at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:744)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
 

Can you please respond?!

I would like a response as well. In addition to the crashes experienced by @coronarocks, we are seeing extreme performance degradation in this product. It has literally become unusable. MY Developers seem to be not caring anymore. Very disappointing.

@Coronarocks,

There have always been java incompatibilities and issues with Mac. Every new Mac version that comes out always seems to break Java and we are stuck in a race to update Glider’s packaged JVM as the updates are released. I will try repackaging the newest JVM with the Glider install asap and see if that helps the problem. 

If we do not get back to you soon enough here, you can email us at mydevelopergames@gmail.com or create an urgent ticket through our contact form. You can even send a g-chat request, we are available to chat during business hours. 

And since you have been having so many problems we would gladly refund your money and try to fix all these issues. Please send us the email you purchased Glider with. Thanks!

@ksan,

Have not heard from you specifically about the issues you have been having but it seems like an out of memory issue. Will post an update tomorrow with some more options to help fix the issue. 

Regards,

M.Y. Developers

I have created ticket as you asked me, but I don’t know what for. That was exactly what I did back in June and it was because you never gave me a sensible answer that I had to start this thread…

If you know that new Mac versions cause your product to become partly unusable, why dont you and your company make it your top priority to update your product as soon as possible instead of waiting for your customers to experience problems?

As you can see in previous posts (mine and other), there are several issues, not just the performance. Please make sure that you fix ALL of them before considering your work done. It is ok if you release them in separate versions as they get fixed, just fix them all.

@coronarocks,

We sent you an email. We have pushed an update that should fix the memory issue you are having. We try our best to fix all the issues that are reported.

@ksan,

We have pushed an update. Please re-download and try the update.

@CoronaRocks,

If you know that new Mac versions cause your product to become partly unusable, why dont you and your company make it your top priority to update your product as soon as possible instead of waiting for your customers to experience problems?

In the past we have been bitten by every major mac release and the slew of Java related bugs that comes with it. It just ends up being a frustrating waiting game to get Oracle to fix all the issues. The situation is just as frustrating for us as it is for you. 

As you can see in previous posts (mine and other), there are several issues, not just the performance. Please make sure that you fix  ALL  of them before considering your work done. It is ok if you release them in separate versions as they get fixed, just fix them all.

Actually. ALL of the stack-traces you have posted have been addressed. We cannot replicate all the issues you are having and most of these updates are a shot in the dark. If your problems still persist we can gladly give you a refund even 6 months after your purchase.

Thank  you,

M.Y. Developers

I downloaded your update (2.1.33), unchecked RAM storage and emptied the user directory. No improvement, it is still as slow as before, completely unusable. Also after about one minute the below exception occurred. Also, the problem with “Could not launch because main.lua is missing” still exists. In other words, none of the three problems that I wrote about has been fixed!

java.lang.NullPointerException
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.StaticVariableAddress.resolveNameHere(StaticVariableAddress.java:406)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.FunctionScopeAddress.resolveNameHere(FunctionScopeAddress.java:52)
    at com.MYDevelopers.LuaSupportCompiler.SymbolTable.Expressions.Address.StaticVariableAddress.resolveName(StaticVariableAddress.java:389)
    at com.MYDevelopers.LuaVMScanner.Utils.queryScopeForVariable(Utils.java:73)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.processNamePath(VMNavigatorPlugin.java:169)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.decorateFunction(VMNavigatorPlugin.java:183)
    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.scan(VMNavigatorPlugin.java:56)
    at com.MYDevelopers.LuaSupport.StructureScanner.LuaStructureScanner.scan(LuaStructureScanner.java:44)
    at org.netbeans.modules.csl.navigation.ElementScanningTask$1.run(ElementScanningTask.java:172)
    at org.netbeans.modules.parsing.impl.TaskProcessor.callUserTask(TaskProcessor.java:593)
    at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:155)
    at org.netbeans.modules.parsing.api.ParserManager$UserTaskAction.run(ParserManager.java:139)
    at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:206)
    at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:203)
    at org.netbeans.modules.masterfs.filebasedfs.utils.FileChangedManager.priorityIO(FileChangedManager.java:176)
    at org.netbeans.modules.masterfs.providers.ProvidedExtensions.priorityIO(ProvidedExtensions.java:360)
    at org.netbeans.modules.parsing.impl.Utilities.runPriorityIO(Utilities.java:74)
    at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:203)
Caused: org.netbeans.modules.parsing.spi.ParseException
    at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:211)
    at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:106)
[catch] at org.netbeans.modules.csl.navigation.ElementScanningTask.computeStructureRoot(ElementScanningTask.java:160)
    at org.netbeans.modules.csl.navigation.BreadCrumbsTask.run(BreadCrumbsTask.java:121)
    at org.netbeans.modules.csl.navigation.BreadCrumbsTask.run(BreadCrumbsTask.java:81)
    at org.netbeans.modules.parsing.impl.TaskProcessor.callParserResultTask(TaskProcessor.java:568)
    at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:744)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1423)
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
 

@Coronarocks,

How large are the files you are editing, how many lines of code? How many projects do you have opened at the same time?

To fix the could not launch error, Please go to glider options-> editor -> check “do not copy files”.

This situation reminds me of a client who was having similar issues such as yours. Glider becoming very unusable, frequent freezes, crashes, performance tanks. At the time Glider was in beta and the lua analyzer was being developed. After sending his project files we found the bug in the analyzer that was causing all of his issues. Without the code it was impossible to fix it. I suspect this is a similar problem.

We simply cannot replicate these problems on our end and without doing so we cannot fix them. You can help us by stripping your project to the bare minimum while the bug still persists and sending it to our email.

Regards,

M.Y. Developers

@coronarocks,

Have you had a chance to try the v 2.1.2 update? Are you getting this error after the update? Please let us know.

Regards,

M.Y. Developers

Hello,

No, I have not. I currently have 2.02 but when I click “Help” -> “Check for updates” it says that “Your application is up to date!”. An interesting thing is that it does so immediately after clicking the above, even when I turn of my wifi. In other words: it seems that it does not even bother to check online if there is a new version… Also, the out-of-memory error has now come back.

I want to make this perfectly clear: even if I crank up the JVM parameters for more memory, the application eventually runs out of it no matter how high I set it. This means that you most probably have a memory leak. You need to address that issue instead of telling me to turn of functionality to get rid of the thrown exceptions!

Back to the current problem: why doesn’t the “Check for updates” work and how would you suggest I update the product (as opposed to uninstalling the whole thing)?