Simple Scanner problem - endless scanning

Glider (IDE)
#1

Hi,

I am experiencing problems with the Simple Scanner when editing my lua project through the IDE. The project has around 60 .lua files and most of them are less than 300 lines long, many are even under 100 lines of code.

It seems the scanner is stuck and the glider process will use a lot of CPU resources with all the expected side effects of that. Eventually the progress numbers might increase over time but even after an hour it just keeps going and going…

I can’t abort the scanning by clicking the “x” next to the scanner. The only thing that helps is to restart glider. But unfortunately the same problem will be back after a while.

I am using LuaGliderv19 201302132200 on a Mac and have set “Scanner Detail Level” to “Scan Only Current File + requires” - pretty much everything else is on default settings.

Any suggestions?

Thanks,

Danz

#2

Hello Danz,

Thank you for the report. We are going to rewrite some of the scheduling code that may be causing this problem.

Regards,

M.Y. Developers

#3

I am also having the same issue actually :frowning: Can you guys provide a time-frame for a potential fix?

Cheers guys,

Rich

#4

I’m having the same issue.  It also gets stuck when “Generating Projects View” - it’ll get stuck on the last project e.g. 12/13.

#5

Same problem here.

I’ve got the scanner set to the minimum level (stubs only? I can’t remember what the option is called).

I can’t even load glider anymore without it going into what seems to be an infinite scanning loop that brings my PC to its knees.

Immensely frustrating.

:frowning:

#6

@Danz,

I am using LuaGliderv19 201302132200 on a Mac and have set “Scanner Detail Level” to “Scan Only Current File + requires” - pretty much everything else is on default settings.

Do you have RAM storage enabled? How many files do you currently have opened in the editor?

@bdq,

I’m having the same issue.  It also gets stuck when “Generating Projects View” - it’ll get stuck on the last project e.g. 12/13.

Does this problem also have the CPU thrashing as poppingchicken is reporting?

@poppingchicken,

Did this problem occur suddenly or did you notice a gradual slowdown leading to this problem. How many files do you currently have open in the editor? Does the scanning stall at a particular file or project?

Regards,

M.Y. Developers

#7

Guys,

In my instance, it will also kill the CPU.  It doesn’t seem to always start the scanning when I start up Glider, and the number of things that it’s scanning isn’t always the same - but in every case it seems to get stuck on the penultimate thing.  i.e. 14/15, 189,190, etc…

Hope this helps

Rich

#8

Hi guys,

Yes, RAM storage is enabled. The problem can come up with 20 or with 4 files open - does not matter. It also seems to be random when it appears. Sometimes I can have Glider open for 1-2 hours without problems, sometimes the issue comes up a few minutes after starting.

Let me know if you need anything else to narrow this one down, this bug is a pain  :blink:

Thanks,

Danz

#9

Ditto on these same symptoms - massive CPU and RAM usage, hard to describe when or why it happens, usually if Glider is left open for a long time, and notice Scanner tasks never actually finish.

Can upload logs if it helps when it occurs again.

#10

It started a few weeks ago, but I’ve been away on holiday and haven’t reported it until now.

I don’t know if it was caused by an update.

Glider was working well, and then the problem suddenly appeared, and never went away.

I only have 4 small files open in the editor.

It gets stuck with “Opening Projects” being displayed in the bottom-right status bar.

It says “Opening Main Window” in the bottom-left corner.

#11

I have seen something strange with the CPU and Lua Glider.  I was looking at Activity Monitor and the CPU jumped from like 20% to 150% then to 20% then to 160% then … kept oscillating between normalish and huge values in ‘an instant’.  Sometimes the program works OK in this state but other times it would crash (it crashed twice on Saturday).

The scanning problems go away when I only open one project at a time, or at least it hasn’t happened in the past couple of days since I tried only having one open project.  It might be worth noting that when it was happening, I had the project I was working on open, which had the widget candy library in it.  The other project I had open was the widget candy sample app (so I could reference things in it).  Maybe glider is getting stuck in some kind of infinite loop in a case like this.  Not sure if that’s possible but …

Anyway, I have a macbook pro with an SSD and 16GB of ram so … yeah it should be able to handle whatever normal activity is thrown at it so whatever the scanner is doing is probably pathological.

I do keep uploading logs when this happens, though I’m not sure what you do with them … i.e. how you know what the issue I was experiencing was.  You should add a ‘comment’ field to the Lua Glider logs upload dialog so I can say why I’m uploading the logs.

Product Version: LuaGliderv19 201302132200

Java: 1.7.0_40; Java HotSpot™ 64-Bit Server VM 24.0-b56

Runtime: Java™ SE Runtime Environment 1.7.0_40-b43

System: Mac OS X version 10.7.5 running on x86_64; UTF-8; en_US
(luagliderv19)       

#12

Possibly related error info (I mistakenly posted these in another thread before, oops)

Product Version:  LuaGliderv19 201302132200

Java:  1.7.0_40; Java HotSpot™ 64-Bit Server VM 24.0-b56

Runtime:  Java™ SE Runtime Environment 1.7.0_40-b43

System:  Mac OS X version 10.7.5 running on x86_64; UTF-8; en_US
(luagliderv19)       

 

java.lang.NullPointerException

    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.convertItem(VMNavigatorPlugin.java:86)

    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.convertItem(VMNavigatorPlugin.java:68)

    at com.MYDevelopers.LuaVMScanner.VMNavigatorPlugin.decorateFunction(VMNavigatorPlugin.java:203)

    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:584)

    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:201)

    at org.netbeans.modules.parsing.impl.TaskProcessor$2.call(TaskProcessor.java:198)

    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:198)

Caused: org.netbeans.modules.parsing.spi.ParseException

    at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:206)

    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$2.run(ClassMemberPanelUI.java:204)

    at org.netbeans.modules.csl.navigation.ClassMemberPanelUI$2.run(ClassMemberPanelUI.java:194)

    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:559)

    at org.netbeans.modules.parsing.impl.TaskProcessor$CompilationJob.run(TaskProcessor.java:735)

    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

    at java.util.concurrent.FutureTask.run(FutureTask.java:262)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

    at java.lang.Thread.run(Thread.java:724)

#13

Some more information:

When glider finally lets me start editing my code, it works nicely, except that the bottom right part of the screen has:

“Background scanning of projects… 100%”

When I click the progress bar, it says it is scanning C:\Program Files.

I don’t have any of my code in C:\Program Files.

I’m not sure why glider thinks it needs to spend ages scanning that location.

When I go to close glider, if that scanning hasn’t finished yet, glider will ask me if I want to stop the background scan (even if the progress bar has displayed “100%” for a long time).

#14

Hello Danz,

Thank you for the report. We are going to rewrite some of the scheduling code that may be causing this problem.

Regards,

M.Y. Developers

#15

Hello poppichicken,

it is very strange that glider is trying to scan program files. Have you by any chance have opened a project folder inside program files that does not have a main.lua file? 

Regards,

M.Y. Developers

#16

Good lord, how embarassing!

Yes, for some reason I had Program Files listed in the Projects window.

I have no idea why it was in there (I must have opened it by mistake), but anyway, I closed the Program Files “project” and that problem is now solved.

HOWEVER, the scanner is now stuck. It says “Simple Scanner(2/35)”.

I have 12 projects listed in the Projects window - they are chapters from a Corona training course, so they don’t contain very many files, and certainly no large files.

Glider is totally stuck and has to be killed using Task Manager.

:frowning:

[EDIT] I managed to re-load Glider. I was able to close all of the projects (except the one I’m working on).

When I opened main.lua of that project, it scanned all the way through in a few seconds, and then I could carry on.

#17

When I had only one project open it didn’t seem to have the scanner problem for several days.  However, this morning it was scanning, i tried to stop the scan but it ended up freezing and i had to force kill it.  I tried restarting but when glider opened only the main.lua file window was showing (i had floated the code window).  Then I closed that to see if the main window was behind it or something.  There were no windows.  I had to force kill it again and restart it.  At some point I managed to upload logs.  Now when I open Lua Glider there are no windows at all shown.  I can see the menu items in the top bar of my mac for glider but nothing else.  If I try to go to Window -> Projects it lets me select that but no window comes up.  Help?

The mac os x console has this to say about it:

10/14/13 8:57:05.749 AM [0x0-0x2a02a0].Lua Glider v19: Oct 14 08:57:05 MacBook-Pro.local java[13929] <Error>: CGContextSetBaseCTM: invalid context 0x0
10/14/13 8:57:06.012 AM java: CGContextGetCTM: invalid context 0x0
10/14/13 8:57:06.012 AM java: CGContextSetBaseCTM: invalid context 0x0
10/14/13 8:57:06.012 AM [0x0-0x2a02a0].Lua Glider v19: Oct 14 08:57:06 MacBook-Pro.local java[13929] <Error>: CGContextGetCTM: invalid context 0x0
10/14/13 8:57:06.012 AM [0x0-0x2a02a0].Lua Glider v19: Oct 14 08:57:06 MacBook-Pro.local java[13929] <Error>: CGContextSetBaseCTM: invalid context 0x0
 

Product Version: LuaGliderv19 201302132200

Java: 1.7.0_40; Java HotSpot™ 64-Bit Server VM 24.0-b56
Runtime: Java™ SE Runtime Environment 1.7.0_40-b43
System: Mac OS X version 10.7.5 running on x86_64; UTF-8; en_US

(luagliderv19)

#18

Following up - Glider is now totally unuseable for me.  It goes into spinning ball of death mode within seconds of opening it.  So I deleted the Library/Application Support/luagliderv19 directory, moved the application to trash, and re-downloaded the installer.  I re-installed and it said five updates are available.  I applied the updates, and then it went into spinning beachball of death mode (note I have a macbook pro with an SSD and 16gb of ram).  So I had to force kill it.  Then I started it again and within a few seconds, spinning death.  I’ve uploaded the logs and am emailing you the mac os x crash report.

#19

I am using the Glider trial, and whilst there are parts of it I love, I too am experiencing this very same issue.

I have updated the trial to all latest versions of plugins etc.

iMac i7 OSX 10.8.5 with 12gb memory.

Any hope on an imminent fix?

#20

Hello All,

We think we are on to a possible cause for this error. We ask that when you upload logs via help-> upload logs after relaunching Glider to help us gather more data.

Thanks for your help!

Regards,

M.Y. Developers