Possible SoloLearn Bug, please test

Question

What happened: I ran the code I appended here and managed to escape the infinite alerts by repeatedly clicking on the HTML tab.
After that, no Web-Codes would run, until I restarted SoloLearn. I had something similar happen while executing a legit code, so this might be worth looking in to.

Can you reproduce the bug or did you experience something similar?

https://code.sololearn.com/W777881cCujD

Answer 1

...Interesting!

I've successfully​ recreated bug scenario, works exactly as you said.

Try reporting to SL with screenshot, links, description through SL support email?

[e-mail]

Answer 2

Just to clarify on behalf of @Tobi -

We all know what an infinite alert box loop is. We know what it does. We know you can't get out once you enter. We are not idiots, this is not the bug we are talking about.

What we HAVE here, is the ability to escape from the loop by repeatedly pressing on HTML tab, wherein afterwards, all web codes will not work unless you force close the app and restart SL.

Answer 3

@seamiki Not sure what you mean by rage blind. The line about reading the post more carefully should be mine to say. You were unable to recreate the issue, hence you don't know why it would worth to be looked into by the devs.

Answer 4

I sent a bug report via the in app feedback system and linked this thread. If SL needs it, we still can document the issue in detail.

Answer 5

Not a Sololearn bug... but a trap of both infinite loop and missuse of JS alert box ^^
Your code is:

var i = 1;
while (true){
alert(i++);
}

... so, you infinitly pop up an alert ( modal os window ) without leaving any time to do anything else: only solution to break this code if running is to kill the processus of the app' ( may be any internet browser ) to get back the hand :P

Answer 6

@visph: I used the loop plus alert box on purpose, because it allows us to reliably reproduce the bug of ALL web codes not working until restart.
As I said, I had this happen while working on a proper code, so the alert box lock is not necessarily the only reason for behaviour of that sort.

Answer 7

There's been a good time where they'd fixed these little quirks, but a similar problem popped up for me (engine hang, different event order) yesterday, in the latest SoloLearn.

They've been very responsive to such reports so when I get mine duplicated I'll refer also to this code.

Edit: Less vague; suggestion sent.

Answer 8

As @Visph said it's an alert box in an infinite loop.
The bug is in the code, not in the app.
A variation of this was once popular on SL as "Virus (Like First)" as it forced the user to force close the app that was continously serving alerts.
https://code.sololearn.com/W4bCmsNV6KJA/?ref=app

I wasn't able to recreate your issue, but I noticed that device's memory usage increases with the number of alerts.
The incorrect behaviour you experienced may be related to insufficient memory on the device: in that case there is very little the app creators can do, except forbidding you looping...alert... looping...alert...looping...alert...

Answer 9

@Hatsy, Read the post more carefully or at least till the end, before getting rage blind?!
Btw, Posting on behalf of @Tobi???????????